Approach mode not working
-
ILS set up, all switches correct, Nav mode selected, ILS mode selected, LOC and glideslope both active and showing on display. But when I press approach in the autopilot, the Hawk veers away. Tried this multiple times at different airport all with same result. Is this a bug or am I doing something wrong?
-
What airport is that? I'd like to give it a try.
My problem is that I can't get the g/s to activate at all. The red flag stays up - and the g/s indicator never moves - even though the DME (and localiser) work fine.
Does your red flag disappear?
-
@adamski_nz
I landed at KBOS, I think RW34. No flag, the GS and localiser both were working and moving. But when I pressed the approach button on the ipad the Hawk veers away. Tried it at several airports all with same result. I suspect this is a bug and hope JF will fix this at the next update? -
While the actual real world Hawk does have an ILS reciever, it has no autopilot... The ILS reciever is intended to provide visual guidance only to the pilot, for manually tracking both the localizer and glideslope during an ILS approach. So, having the APR autopilot mode fully functional would actually not be very realistic... JF has provided a limited autopilot anyway for convenience, to reduce the pilots workload for maintaining cruise altitude and following a VOR/GPS course. I personally think that a fully functional APR mode would actually detract from the immersion, and the challenge of learning to fly this aircraft.
-
@retiredman93231
I agree with you, but query why there is an Approach button on the autopilot menu of the Hawk ipad. If the G/S and localiser displays are advisory only then it would be best if the Approach button on the ipad is removed. Pressing it is causing the aircraft to do strange things. -
I agree as far as ILS and the autopilot goes - but in my case, the glideslope indicator doesn't move at all, so I can't even "follow the needle" whilst flying manually.
I certainly wouldn't expect the Hawk to do full autoland(s), but the two indicators should work, should they not?
I'll try KBOS to see what I get. In my test flights, I was using the tutorial/Leeming approach.
ARRRGH!!! My mistake!!!! I've been having the Navigation MODE selector set to "TACAN" the whole time. OMG I feel so stupid!!!!
-
So to clarify... frequencies are entered via the TACAN code for that frequency ?
I'm a little confused as actual TACSNS aren't currently supported in MSFS.
THNX.