Jarek1983 Posted August 6, 2019 Report Share Posted August 6, 2019 Hello! During my last flight I got wrong altitude for the destination field for FMS LTE (shown on the screeshot 355ft for UU14). My destination was U14 in Utah with field elevation of a tad over 5000ft. Something wrong with my flight plan or a database issue? Seems like a database issue, hence the wrong code for the destination aiport and the field was not visible on the synthetic vision. Thanks for your thoughts! Best, Jarek Quote Link to comment Share on other sites More sharing options...
rjb4000 Posted August 7, 2019 Report Share Posted August 7, 2019 I don't know the answer to your question, but I'm curious how you got your Nav 2 standby frequency to be 0.00! Quote Link to comment Share on other sites More sharing options...
Jarek1983 Posted August 7, 2019 Author Report Share Posted August 7, 2019 14 minutes ago, rjb4000 said: I don't know the answer to your question, but I'm curious how you got your Nav 2 standby frequency to be 0.00! I have no idea I bought this module a couple of days ago and I guess I did not use nav 2 yet and it must have been 0.00 out of the box Quote Link to comment Share on other sites More sharing options...
EGT Posted October 22, 2019 Report Share Posted October 22, 2019 (edited) There are some bugs with the G1000. I'm not sure HotStart's or LR's. For example, if you enter "KJFK" it should only enter 4 characters, but the display shows "KJFKA" and tries to search waypoints, not airports. This is a bug. I've also found it necessary to clear the flight plan, enter the route, then tell it to use the FMS for pressurization schedule before it shows the correct destination and elevation. I think it should do this as soon as the destination is selected. Edited October 22, 2019 by EGT Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.