Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Cessna Citation Longitude VNAV Question

Featured Replies

Hey guys, several times I have done some flight plans and have pulled them up to fly them in the Longitude but for some reason the VNAV gives no information.  Can someone tell me what I'm doing wrong and why I'm not getting the VNAV information.  The flight plans are IFR.  Sometimes I don't use a departure procedure but usually end with an ILS or RNAV approach.  Sometimes I get the information sometimes I don't.  Not sure if it is my fault in how the flight plan is set up or what.  I use LITTLNAVMAP to do my flight plans.  Would appreciate your input.  Almost exclusively fly the Longitude and really like the VNAV when it is working.  Thanks for your help.

Several things come to mind:

  • After reaching your cruise altitude, check the approach plate for the MDA just prior to the GS or GP (glide slope or glide path).  This would be the minimum descent altitude in the approach prior to the final descent to the runway.  SET THIS as your next altitude in the AP preset (such as 2500').  Make sure VNAV is turned on.
  • Make sure that your cruising altitude/flight level is showing up correctly in your flight plan.  For instance, if you're cruising at FL430 but upcoming waypoints indicate FL570, etc. you've definitely got a problem.  Enter the proper level in the next plan WP and the remaining should fall in line.
  • Make sure that VNAV is actually active in the g5000.  Click the touchscreen button for VNAV and verify it is on.  It should indicate the time to TOD (top of descent) and the name of the waypoint for that descent.

Randall Rocke

  • Author

Thanks for the help.  Sometimes I notice that there is no altitude listed in any of the waypoints throughout the route.  Sometime it's just frustrating.  BTW, notice your from Columbus, Ohio.  I live on the west side.  Near Galloway.

The g5000 is set up for VNAV climb (not just VNAV descent) in combination with the AT (auto-throttle).  Be sue to set your planned cruise altitude in your flight plan before importing.  Sometimes, this doesn't import correctly (that's why I always check).  If needed, I enter my planned flight level in the g5000 at the first waypoint that I plan to be at cruising altitude.

All of the following WPs will populate with this altitude.  After you change the Altitude preset to the MDA for your approach (and VNAV is active), waypoints after the TOD (Top of Descent) will populate with new altitudes.  Also SIDs and/or STARS included in the FP will populate with altitudes.

WATCH OUT: if you add an approach to your FP while in-flight you may need to delete the previous destination, as it will now be an inappropriate waypoint.  In order for everything to work (especially VNAV) it must all connect in-order.

Yes, I'm in Columbus - north part of the city.

Randall Rocke

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.