CrossWiseRanger Posted September 7, 2016 Posted September 7, 2016 When calling ATC "Inbound", sometimes they will answer with "Fly heading ### for ##." How do you input that heading and distance into the CDU or TAD to make a new Waypoint / Steerpoint which is offset from your current positon? I understand how to do an offset from Bullseye. Thanks. VR with Oculus Rift preferred flying method.
DirtyFret Posted September 7, 2016 Posted September 7, 2016 Try creating a overhead markpoint and then doing a offset on that. Press MK on the CDU panel as soon as you hear the call (creates a overhead markpoint) -> AAP page select to OTHER -> press OSET FSK -> Enter the Markpoint letter into the scratchpad for the overhead markpoint and into L3 -> enter MH/DIS onto R5 -> press R6 to create the offset waypoint. Let me know if it works. 2 [sIGPIC]http://forums.eagle.ru/signaturepics/sigpic109142_3.gif[/sIGPIC] PewPew, "Stick 'em with the pointy end" "Vasilissa the Beautiful" HD Cockpit
Gliptal Posted September 7, 2016 Posted September 7, 2016 Faster way instead of using the CDU OFFSET page: create an overhead MK, hook it, and use the TAD cursor (you'll have to cycle the mode).
CrossWiseRanger Posted September 7, 2016 Author Posted September 7, 2016 DirtyFret, your the ace. That works and was what looking for. Thanks. VR with Oculus Rift preferred flying method.
ICS_Vortex Posted September 8, 2016 Posted September 8, 2016 Faster way instead of using the CDU OFFSET page: create an overhead MK, hook it, and use the TAD cursor (you'll have to cycle the mode). In this way, you won't be able to set heading and distance accurately. And it can probably take too more time than using CDU. PC: i9-10850K ~5.2GHz / Asus Rog Strix H490 Gaming, Asus GTX1080 Rog Strix Gaming OC, HyperX Fury RGB 32Gb RAM 3200MHz, SSD 512Gb, HDD 1Tb, Windows 10 x64. 2 x Samsung Curved 32" VirpilControls software engineer
Gliptal Posted September 8, 2016 Posted September 8, 2016 In this way, you won't be able to set heading and distance accurately. And it can probably take too more time than using CDU.A bit of imprecision is hardly relevant, since you're just flying to an approach point. You shouldn't be following the ATC anyway, not in its current implementation. If you're VFR the approach point is mostly useless, if you're IFR you should be more reliant on TACAN and ILS than WPs and the TAD. Remember the HUD is not sanctioned for IFR conditions.
ICS_Vortex Posted September 8, 2016 Posted September 8, 2016 A bit of imprecision is hardly relevant, since you're just flying to an approach point. You shouldn't be following the ATC anyway, not in its current implementation. If you're VFR the approach point is mostly useless, if you're IFR you should be more reliant on TACAN and ILS than WPs and the TAD. Remember the HUD is not sanctioned for IFR conditions. i use VFR when it's possible. Simple schema. First, to central point of airfield, then to 3rd turn, or from central airfield point to 1st turn and to 3rd. But we're talking about cdu offset, not about approach;) Also, we can use offset not only for approach:) PC: i9-10850K ~5.2GHz / Asus Rog Strix H490 Gaming, Asus GTX1080 Rog Strix Gaming OC, HyperX Fury RGB 32Gb RAM 3200MHz, SSD 512Gb, HDD 1Tb, Windows 10 x64. 2 x Samsung Curved 32" VirpilControls software engineer
Gliptal Posted September 8, 2016 Posted September 8, 2016 You're right, I interpreted the OP's question as being strictly about the approach point.
ICS_Vortex Posted September 8, 2016 Posted September 8, 2016 The thing is that we can get offset from any point, you've stored in CDU. I had some practice to build flight plans, using offset :) PC: i9-10850K ~5.2GHz / Asus Rog Strix H490 Gaming, Asus GTX1080 Rog Strix Gaming OC, HyperX Fury RGB 32Gb RAM 3200MHz, SSD 512Gb, HDD 1Tb, Windows 10 x64. 2 x Samsung Curved 32" VirpilControls software engineer
Recommended Posts