Today I created a flight to KLUK. However, LNM said there was an error in the runway assignments. Looking at the airport diagram, I see that runways 21R/3R are no longer on the diagram but still show up in LNM.

After posting the above, I checked and found that the runway was closed on July 1, 2024.

Edited August 8, 20241 yr by loop_n_roll

59 minutes ago, loop_n_roll said:

Today I created a flight to KLUK. However, LNM said there was an error in the runway assignments. Looking at the airport diagram, I see that runways 21R/3R are no longer on the diagram but still show up in LNM.

After posting the above, I checked and found that the runway was closed on July 1, 2024.

I think this section from the LNM FAQ applies and might help:

Quote

An airport looks wrong, has runways pointing in the wrong direction, or its name is misspelled

Little Navmap does not maintain airports. It just reads the airport data from the simulator scenery library and shows what it finds there. I cannot update airports.

The following are scenery or add-on issues:

1. Aprons are over sized or at the wrong position: Some add-on developers misuse apron polygons for other purposes like parking lots or flattening. MSFS seems to have automatically generated apron polygons which can be wrong. This is not a bug in Little Navmap which reads these structures as is.
2. Taxiway signs are missing or wrong: This is an issue with the stock airport scenery or an add-on.
3. Runways pointing into the wrong direction, e.g. runway 27 pointing to 90 east: This is an issue with the airport scenery or an add-on having wrong runway designators.
4. Runway in procedures do not match the runways of the airport: This happens since runways are renamed because of magnetic drift from time to time. As a result an older add-on might not match the latest navdata update.
5. Airport names are misspelled. This is a scenery problem.
6. Country, state, province, city or airport name is wrong or missing: Completeness of administrative information depends on simulator or airport add-on. Administrative data is often missing or wrong for X-Plane airports. Country information is completely missing in MSFS. Other simulators might provide only obsolete data.

What can you do in general:

1. Look for an add-on airport which corrects the issue if it is a stock airport.
2. Contact the add-on developer and ask him to fix the issue if it is an add-on airport.

MSFS:

1. Use the MSFS development tools to create a corrected version of the airport.

X-Plane:

1. Check the Scenery Gateway if there is already an updated version of the airport.
2. File a bug report at the Scenery Gateway.
3. Use WED to correct the issue and optionally upload your changes to the Scenery Gateway.

Alex

To be more precise:

1. Navigraph navdata was probably updated (your did not tell me if you use it nor did you tell me what simulator you use, so I have to guess) and shows new, renamed or closed runways.
2. Airports (stock or add-on) are loaded by LNM from the simulator data and were not updated and still have the runways open.

Alex