While the Laminar Research (LR) G1000 does not include an ADF it does allow the use of NDB overlay procedures (as the real G1000 does too). For example KHEG in Florida the NDB-A procedure can be selected from the proc menu on the G1000, however the EGTK airport has a NDB 01 procedure in real life and showing in Navigraph charts, however that does not appear at all so cannot be selected in the LR G1000.
I have a Navigraph sub and the data is up to date.
Hi,
I have checked it and I confirm the missing data. We must ask, but I´m pretty sure that this has something to do with the missed approach part, which doesn´t follow the runway heading. There are special coding rules, and it is possible that this missed approach “offset” is the reason why this cannot be coded, and therefore, it is missing from the data.
I will ask Jeppesen and inform you here when we receive an answer.
Thank you
Richard
Thank you Richard for the update
However, I have checked with real world pilots who have a G1000 without an ADF receiver, they tell me they can load the NDB 01 overlay procedure at EGTK in their G1000 so presume that Jepp do have navdata for this
I also have a Garmin official DA42 G1000 simulator, I enclose a screenshot showing the procedure
Regards
Mark
Hi Mark,
I believe you and I’m with you. I also don’t see a reason why thos approach is missing. We will ask Jeppesen.
Cheers
Richard
Hi Richard
Any update on this please?
thanks
Regards
Mark
Hi Mark,
I´m sorry, I have forgotten to answer.
Yes, we have still received the answer from Jeppesen, and as a short (technical) summary of this answer:
Jeppesen has moved this procedure to a new ARINC424 version for the primary records. The reason for this movement is the DME part of this NDB. The DME is biased (with the ILS DME IOXF), which means the zero range reading is not at the transmitting antenna site. That can´t be coded any longer in our ARINC424 version, which we currently use, and therefore, they have removed it.
Bad news, I know, but here’s the good news. In 2026, we are planning to start a migration project to use a newer ARINC424 version, which should bring back this approach. The timeline is complicated because we utilize this source data across all our apps, making the testing component essential.
What I can offer temporarily is to add the NDB 01/19 manually in the meantime. It will not be part of the upcoming cycle 2512, but I suppose I can do this for 2513.
I hope this is a good compromise until we are finished with the migration project by 2026.
Cheers,
Richard
Thank you Richard for the analysis and explanation
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.