I fly C208 with WT G1000 , Set CDI to LOC1 and set the correct Frq. and CRS. The ILS information is displayed in G1000 . Then I set APR and the LOC/GS is armed in FMA at DME 8nm. but when the LOC move to center , the LOC still arm , it didn’t established and via ILS to fly…
what happe ? Is this problem in WT G1000 or C208 ?
You have to be below the glideslope when you catch the localizer, otherwise the system won’t work right. Otherwise, the autopilot would potentially have to enter a steep dive to intercept the GS from above, which wouldn’t be safe.
The GS dot (or diamond) was visible (at the right? And moved downwards? And then past center without locking GS? And your were stable and level moving straight towards the runway when the GS dot past the horizon?
Flying the C 172 with CM 1000, had everything set up and armed approach mode, it was below glidepath and within 20 degrees of ILS heading, and it sailed right on by like the LOC wasn’t even there. There was a LOC and GS beam, but it wouldn’t lock on it. Act’s like the approach mode is not working at all. Hand flew the ILS following the glide slope. and LOC
1 Like
What airport/runway?
Same here. C172/G1000. Active NAV or HDG mode. Below GS, less than 20degr, arming LOC. Activating LOC1, correct freq., LOC just does not get activated.
1 Like
Is this the same bug I see in the TBM930 on the G3000 - where it most times just fails to turn onto the localiser, even when correctly set up and the arrival is flown correctly?
The workaround for me is to cycle the NAV selector (on the TBM it’s from VOR1 to VOR2 to FMS and back to the active VOR1 - haven’t checked the G1000) and it is important to do this AFTER the localiser becomes active and the APR mode is selected.
Then it finds the localiser every time.
It’s been like this for ages in the G3000, reported many times since release, and still never fixed.
I don’t understand what other people are doing when they are flying that they don’t also report this issue. It can’t just be me as it’s survived many updates. This is the first time I have seen anyone else report it.
Let me know it this workaround help you.
Obviously it’s not a solution and this needs fixed. It’s very flakey at present, and I have almost hit mountains in foggy landings such as Interlaken due to the bug.
Just used the WT G1000 in the Baron 56 on an RNAV approach and the GS diamond was constantly indicating full above the GS. Even though entry alt was 2700 and I was at 2500.
Hi all,
Our Garmin units still use completely stock autopilot, nav, and flight plan systems. So any issues you are seeing with ILS or RNAV approaches are going to be sim related.
As we work this year on moving our units into the sim, we will also be working on bringing the same improvements in those areas that we made on the CJ4 into the sim as well, so everything can have the same navigational accuracy.
-Matt
3 Likes
OK good to know where the problem lies. I have reported this to Zendesk several times over several months, but they still haven’t fixed it.
So over the next few months are you saying that you will be replacing increasing amounts of the Asobo systems so these bugs will disappear as a matter of course?
Yeah, over the course of the year we will be bringing the Garmins to the sim as well as working on the underlying flight plan and navigation system, amongst other things.
-Matt