Where can I find PMDG 737 FMC airways and waypoints in MSFS?

In Microsoft Flight Simulator, obtain PMDG 737 FMC airways and waypoints from an IFR flight planner or current en-route chart, then enter them on the CDU RTE pages. The aircraft accepts only data in its own navigation database, so use the same AIRAC cycle for the planner, charts and PMDG 737.

Where can I find PMDG 737 FMC airways and waypoints?

Use an IFR flight planner to generate the route and current charts to confirm its airway connections, procedures and restrictions. The PMDG CDU is not an airway catalogue: it displays and validates identifiers after you enter or import them, but it does not provide a practical list of every available route.

On an en-route chart, an airway is the labelled track joining published fixes or radio aids. The airway name might resemble J60, UL9 or T123; its entry and exit points are separate waypoint identifiers.

If your route was generated with SimBrief, our PMDG 737 SimBrief import workflow explains how to request, load and verify the plan without manually retyping the entire route.

How do I read an FMC route string?

A normal en-route segment follows the pattern ENTRY FIX – AIRWAY – EXIT FIX. The entry fix tells the FMC where to join the airway, while the exit fix tells it how much of that airway to insert.

• DCT means direct. Do not type DCT into the VIA column; enter the next waypoint in the TO column and the CDU will create a direct leg.
• SIDs and STARs are procedures, not airways. Select them through DEP/ARR rather than copying every procedure fix into the route pages.
• Speed and level groups are not waypoints. Entries representing cruise speed, flight level or other briefing data do not belong in a VIA or TO field.
• Coordinates require the correct Boeing format. Do not paste a planner’s display label and assume the FMC will translate it.

What does a route label such as MISM-430 mean?

MISM-430 is not enough by itself to identify a standard PMDG airway or waypoint. A hyphenated item may be a planner-specific label, custom position, airport-related annotation or export artefact rather than the identifier stored in the FMC database.

Check the route’s detailed waypoint table for the item’s coordinates and type. If it represents a published fix, use its actual database identifier; if it represents a coordinate, create an accurately defined user waypoint; if it is only an annotation, do not enter it into the route.

How do I enter an airway route in the PMDG 737 FMC?

Enter the airports and procedures first, then build the en-route section through the CDU’s RTE pages using each airway and its exit waypoint.

1. Check the navigation cycle. Open the FMC IDENT page and compare its AIRAC cycle or effective dates with the planner that generated the route. A mismatch only causes trouble when a relevant fix, airway or procedure changed, but matching cycles removes that uncertainty.
2. Enter the airports. Put the departure airport in ORIGIN and the arrival airport in DEST. Use the recognised ICAO or navigation-database identifier, not a three-letter passenger-facing IATA code.
3. Select the departure. Open DEP/ARR and choose the runway, SID and transition when known. The SID transition or final procedure fix often becomes the entry point for the first airway.
4. Establish the first en-route fix. On the next RTE page, place the first direct waypoint in the TO column if the selected departure has not already supplied it.
5. Enter the airway and exit. Type the airway designator into the next VIA field, then put the required exit fix in the corresponding TO field. The FMC inserts the intermediate airway waypoints automatically.
6. Repeat the VIA/TO pattern. Each new airway must connect to the route’s existing endpoint. If it does not, recheck the connecting fix rather than trying alternative fields at random.
7. Select the arrival. Choose the STAR, transition and approach through DEP/ARR. Avoid manually entering a transition fix that the procedure has already added.
8. Activate and inspect the route. Select ACTIVATE when displayed, press EXEC, and review every LEGS page. Use the navigation display to look for gaps, loops, doubled-back legs and implausibly sharp turns.

A mistake we see constantly is entering an airway before the route contains a valid entry fix. The preceding waypoint and requested exit must both lie on the database’s coded airway segment.

Once the route itself is valid, our complete Boeing 737 FMC set-up sequence covers position initialisation, performance data, take-off entries and the final route checks.

Where do PMDG 737 waypoints come from?

The PMDG 737 reads airports, named fixes, radio aids, airways and procedures from its own loaded navigation database. A planner or chart tells you what should be entered; it cannot make an absent identifier appear in the aircraft.

The PMDG database can differ from the data used by the MSFS World Map. An airport may therefore exist as scenery, and even appear in the World Map planner, while its identifier or procedures are missing or different in the PMDG FMC.

Can I enter a waypoint that is not in the database?

You can create some user-defined positions using supported Boeing formats, including charted latitude-and-longitude points, place-bearing-distance points and along-track fixes. Use the exact charted position rather than an approximation.

A user waypoint does not repair missing navigation data. It will not add an airway connection, SID, STAR, runway or airport record, so a missing published fix should normally be resolved by correcting the identifier or AIRAC mismatch.

Why does the PMDG FMC show NOT IN DATABASE?

NOT IN DATABASE means the FMC cannot find the entered identifier in its loaded navigation data. Typing errors and AIRAC mismatches are the usual causes; an airway rejected in the VIA field more often indicates that it does not connect to the preceding route fix.

Use this troubleshooting order:

1. Check the exact characters. Look for confusion between letters and numbers, copied punctuation, or an airway entered in a TO field.
2. Compare AIRAC cycles. Check the PMDG IDENT page against the cycle stated by the planner or route export.
3. Verify the connection. Confirm that the route’s preceding fix, airway and requested exit appear together on the same-cycle chart.
4. Resolve duplicate identifiers. Select the candidate with coordinates in the correct country or route region.
5. Regenerate or rebuild the route. After changing navigation data, reload the aircraft or simulator as required and create the route again. An already loaded route may retain invalid legs.

Updating the PMDG aircraft software and updating its navigation database are separate tasks. A newer aircraft build does not by itself guarantee newer waypoints, airways or procedures.

Why is my PMDG 737 airport not in the database?

A PMDG 737 airport-not-in-database error usually means the wrong identifier was entered or the airport is absent from the aircraft’s navigation cycle. Start by replacing a three-letter IATA code with the recognised ICAO or database location identifier.

If the identifier is correct, compare AIRAC cycles and confirm that the airport is represented in aviation navigation data, not merely as MSFS scenery. Small, private, renamed or newly added fields may lack an FMC airport record or published procedures.

You cannot turn a custom coordinate into a full origin or destination airport. For a simulator flight to an uncoded field, use a suitable coded airport or en-route point for planning and continue visually to the field, accepting that the FMC will not provide its runways, approaches or terminal procedures.

How do I delete a route discontinuity in the PMDG 737?

Close a PMDG 737 route discontinuity by moving the first valid waypoint below the gap into the empty discontinuity line, then executing the modification. Do this only when the chart or clearance defines a continuous route.

1. Open the LEGS page. Find the route discontinuity and identify the first waypoint shown below it.
2. Confirm that the connection is intended. Compare the previous leg and next waypoint with the selected SID, STAR, approach or ATC clearance.
3. Copy the next waypoint. Press its line-select key to place that waypoint in the scratchpad.
4. Insert it at the gap. Line-select the waypoint into the empty line at the discontinuity.
5. Review and execute. Check the resulting track and distance, then press EXEC if the connection is correct.

Do not remove every discontinuity automatically. One following a VECTOR or manual-termination leg may be intentional because ATC is expected to provide a heading or later clearance. Joining the legs blindly can command an unrealistic turn back towards the next fix.

Can the MSFS World Map send a route to the PMDG 737 FMC?

A route created in the MSFS World Map is not guaranteed to populate the PMDG 737 FMC because the native simulator plan and the aircraft’s flight-management route are separate data flows.

Depending on the installed PMDG build and platform, the aircraft may offer a supported route-request, import or company-route facility. Import availability and its controls can vary, but the checks do not: compare the loaded route with the briefing, inspect the LEGS pages and resolve every unexpected discontinuity before flight.

MSFS ATC may continue following the native World Map plan even when the PMDG FMC contains a different route. If you intend to use native ATC, keep the World Map plan and FMC route aligned rather than assuming one has overwritten the other.