No TOD nor BOD during RNAV flight

:wave: Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.

2 tags are required: One for platform, and one for aircraft.

Are you using Developer Mode or made changes in it?

Not using Developer Mode

Have you disabled/removed all your mods and addons? If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the Community Support section.

Which aircraft are you reporting an issue about? (Please also add the proper tag for it)

DA 62, Cessna 172 with G1000

Which aircraft version are you experiencing this issue on? (You can find this listed in the Content Manager under the Aircraft Name)

Current DA62 and current Cessna 172 with G1000

Brief description of the issue:

This is more a G1000 issue. Nothing happens when I click the VNAV button. TOD and BOD do not appear on the MFD.

Provide Screenshot(s)/video(s) of the issue encountered:

Detailed steps to reproduce the issue encountered:

Fly the DA 62 to 10000 ft with autopilot on. Set the altitude bug to 1600 (Runway RNAV 6 at KISP). Click the VNAV button. Nothing happens. VPath does not appear on the PFD,. TOD and BOD do not appear on the MFD map. When near KISP, the APR button is also dead requiring a VFR approach/landing. Same results with the cessna 172 with G1000.

PC specs and/or peripheral set up if relevant:

Build Version # when you first started experiencing this issue:

As of the most recent update. Today’s date: 3-Apr-2024.

:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?


Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video: NA

Did you set the altitude at the RWY waypoint in the Flight Plan of the G1000?

As Casual is describing, check your flight plan. You need to have an attitude constraint at some future waypoint to which the avionics can calculate a decent path.

1 Like

We’ve moved your topic into the User Support Hub.

The Bug Reporting Hub is for posting suspected or confirmed bugs that other users are able to reproduce without duplicating an existing bug report. Using the template or providing all the relevant information about your bug and sim setup is required in order to provide valuable information, feedback, and replication steps to our test team.

If you are not sure if your issue is a bug or need further input from the community, please use the User Support Hub category. If the community can replicate your issue, first search the Bug category to see if there’s an existing topic. If it already exists, contribute to that report. Duplicate bug reports will be closed.

If you believe it is a new report and no duplicate exists, then create a new bug topic using the provided topic template.

All issues caused by or involving third-party addons/mods should be reported to the third-party developer. Assure that no addons/mods are used when reporting issues in Bug Reports.

The other piece to this is if you want a ToD and BoD or runway 16, the easiest way is to use PROCedures and load a Visual Approach and select STRAIGHT transition.

Assuming you are not too close, the NXi will generate a leg with a three mile final and a calculated GP after FINAL waypoin, which you couple to AP using APR mode. And it will have a ToD /BoD from your current altitude if you’re higher than required.

If you still want an RNAV guidance, then you have to select and load an RNAV approach corresponding to RWY16 and Activate it. That will calculate a leg to the IAF and provide you with ToD/BoD if you’re higher than the IAF intercept altitude.

Hi Casual and Big,
Thanx for the prompt response. I have not input the altitude myself, but I believe the altitude is set in the RNAV setup in the aircraft. The flight plan shows 600 ft at 2 miles (if i’m reading it correctly and I may not be). I set the RNAV approach on the G1000. I am pretty much a beginner, so it is possible I’m missing something. On the other hand I had nothing but RNAV success and no problem with TOD BOD until these recent flight sim updates.

Please show your flight plan on the MFD. Also, did you ACTIVATE the Approach? This will generate a ToD.

I highly recommend you watch tutorials on the G1000 or give the manual a quick glance around the alt hold and VNAV modes. There are a tons on variables here and it’s very unlikely we will be able to guess what’s happening. 9/10 times it’s user error.

Would that be the functional equivalent of an LPV approach, from the FAF to the threshold? Minus the other parts of an LPV approach, of course.

Kinda. Not that I’m very conversant in the differences, (other than altitude is calculated at GPS height differences based on position, not baro alt), the biggest delta is how you choose to transition into the Approach.

A Straight sends you right to the IAF from present position which puts you up at a 3 mile approach ending at a final with a calculated GP. That’s sort of like any RNAV approach where you’re cleared to the IAF directly from present position.

A Vector assumes ATC will vector you to the IAF. I’ll check again to be sure, but I believe it also generates a linear Course to Fix leg extending from Final that you can intercept manually.

Because it’s a calculated GP, there are no Obstacle offsets. Just like any handflown VFR approach, you’re still responsible for what may intersect with that GP.

The GP is standard 3 degree, so you may see disagreement cross-checking with PAPI/VASI if the latter’s a steeper angle.

Just like any other IAP, you’ll have needle guidance in the PFD on approach and Final.

1 Like

Hi All, Recently I did several flights using waas/LPV on the DA62, the Cessna 172 G1000, and on the Baron G58. I did my normal preflight setup, selecting the RNAV approach (different airports) and in every case I did get the TOD and the BOD. Descents started at TOD and finished properly at BOD. The APR button then worked properly right down to the runway. I have no explanation other than there’s magic in the air. Thank you for your insights and tips. All is well and I don’t know why.