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.

Problems with FlightPlans

Featured Replies

I loaded the flight KSFOEDDF ( San Fran to Frankfurt ) into the CDU as explained in theAngleOfAttack video.( using FSX Deluxe and Windows XP )By doing same using the FlightPlan KSFOEGGL I get the error message "Not in database" ( from the CDU )I also notice that there are different files in the Flight Plans.Some with file extension RTE and some with file extension R2File !What are the differences and above all: how do I enter the flight plans in the CDU as I didwith KSFOEDDF ?I appreciate your help.Thank youRobi77

The NOT IN DATABASE message means just that, a fix is not in the navdata. Not entering lat/lon waypoints is a common error, also trying to enter or exit an airway from a fix not on the airway. I can't even guess what your problem might be because you didn't provide the flightplan. There are two different formats used by pmdg. I think the .rte format is the more common.

Dan Downs KCRP

  • Author
The NOT IN DATABASE message means just that, a fix is not in the navdata. Not entering lat/lon waypoints is a common error, also trying to enter or exit an airway from a fix not on the airway. I can't even guess what your problem might be because you didn't provide the flightplan. There are two different formats used by pmdg. I think the .rte format is the more common.
Actually I made a typo mistake.It should say KSFOEGLL.Like I said before when using the included flight planKSFOEDDF everything works as shown in the video.When I try to use the KSFOEGLL flight plan I am having problems for whatever reasons.I cannot enterKSFOEGLL into route on the CDU without getting error messages "Not in database".I also noticed that the file names in the Flight Plan folder are different.KSFOEDDF vs KSFOEGLL001Thanks for your helpRobi77

Can't help without knowing what creates the error message. The latest in flightaware for KSFO-EGLL is SFO8 SFO RBL PASST GEG J517 LETRM J517 YMM 6330N 10000W 6600N 09000W NCAB 6730N 08000W 6800N 07000W CANEL SF 6500N 04000W 6300N 03000W 6100N 02000W ERAKA UP58 SUPIT UN590 GOW UN615 LAKEY NUGRA BNN1B. What is the plan you are trying to use?

Dan Downs KCRP

I believe you have to add the coroute as it is written in the flightplans folder - just enter what is before the .rte so you would enter KSFOEGLL001 rather than leave the 001 off.Be careful with COL in the AOA flightplan as it does show up as in S.America on occassion so check the routing on the ND in plan view before commiting it. I wondered why it came up with a fuel error lol.The AOA livery is on the AOA website if you want the fsx one as well as the fs9 one on the dvd.John Ellison

The NOT IN DATABASE message means just that, a fix is not in the navdata. Not entering lat/lon waypoints is a common error, also trying to enter or exit an airway from a fix not on the airway. I can't even guess what your problem might be because you didn't provide the flightplan. There are two different formats used by pmdg. I think the .rte format is the more common.
Dan,Just for added information:Today on Navigraph forum it was found (by Jan-Paul ) that when keying in airways/waypoints on the route page .. waypoints that are 4 characters give "not in database" with PMDG 737/747.Same waypoint entered via Co-route or via Legs page enters without an error.At first it was thought to be an Airac / Navdata problem.

Best Regards,

Vaughan Martell  PP-ASEL KDTW

Thanks Vaughan, I have not run into that. I spend most my time in US airspace (five char fix names). I am with you on this, if it is a valid fix name you'd expect it to work on the RTE page. Son of a gun.

Dan Downs KCRP

Dan,Same for me on US airspace.I always enter a CO-Route and then modify via the Legs page.So, maybe this 4 character "not in database" during Route entry applies to more PMDG products than just the 747/737 now.And, maybe PMDG could fix it for their PMDG 737 NG V2 if it shows the same thing now in Beta testing (hint, hint).They could also check that routes are not limited to like eg 100 waypoints (some European plans have a huge number of waypoints in their procedures SID/STAR) and fix any other FMC problems previously reported like for SID/STARs / ARINC stuff as it is related to Navigraph procedures problems / calculations.

Best Regards,

Vaughan Martell  PP-ASEL KDTW

I use FSBuild to prepare a plan and export it to both FS9 and the PMDG FMC CO_ROUTE function for import (I have the 736.737,738, 739.). It has in its database less than five letter waypoints as well. Some of these are actually local airport wayponts that could be flyover or flyby types and even position limiting (soft) waypoints.Five letter waypoints are supposed to be unique and filed with ICAO as far as I know. The "local" waypoints are not bound by this ICAO definition and are bound to airport procedures only (SIDs and STARs and IAPs). The problem with "local" waypoints is that the label may not be unique on a global scale.

Ron,This is a different problem.With PMDG a 4 letter waypoint can be keyed in on the legs page ok.The FMC will also accept a 4 letter waypoint in the flight plan loaded via CO-Route.But, you cannot enter the 4 letter waypoint on the RTE Page of the FMC ... like as an exit waypoint from an airway.PMDG FMC error "not in database" .. will come up..

Best Regards,

Vaughan Martell  PP-ASEL KDTW

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.