Fix an airport missing from the X-Plane 12 G1000 by checking its identifier, nearest-airport filters, navdata, scenery conflicts and damaged files.
An airport is usually missing from X-Plane 12's G1000 because the wrong identifier is being entered, a nearest-airport filter hides it, installed navigation data is stale or malformed, or custom scenery defines it incorrectly. Test the ICAO or local code in a stock G1000 aircraft, then isolate navdata and scenery.
X-Plane keeps airport layouts, instrument procedures, navigation aids and visible scenery in different data layers. Seeing a runway outside the aircraft does not prove that the G1000 has a valid airport identifier or procedure record for it.
What does missing mean in the G1000?
The exact symptom identifies which setting or data layer needs attention.
| Symptom | Likely cause | What to check |
|---|---|---|
| Airport is absent only from the moving map | Map range, detail or declutter settings | Search for it with Direct-To rather than relying on the map symbol |
| Direct-To finds it, but the NRST page does not | Nearest-airport runway filters | Minimum runway length and permitted surface types |
| Airport is found, but no approaches appear | No published procedures or missing CIFP procedure data | The installed navigation-data cycle and whether the real airport has procedures |
| Airport is absent from Direct-To and X-Plane's airport selector | Wrong identifier, incomplete airport data or damaged installation | The airport's X-Plane identifier and default or custom scenery files |
| Airport works in a stock aircraft only | Aircraft-specific avionics or database | The add-on aircraft's own data installation |
How do I restore a missing G1000 airport?
Work through these checks in order so that you change only the layer responsible for the problem.
- Confirm the identifier. Search for the airport in X-Plane's Flight Configuration airport selector and note the code X-Plane displays. Enter that code in the G1000. An IATA code or airport name is not a reliable substitute for an ICAO, FAA or local identifier, and renamed airports may still use an older code in the installed data.
- Use Direct-To as the test. A map symbol can disappear because of range or decluttering while the airport remains searchable. Enter the complete identifier through Direct-To; our guide to stock G1000 Direct-To and flight-plan entry controls covers the relevant controls.
- Test a stock aircraft. Load the included Cessna 172 G1000 and repeat the search. If it works there, the airport is not missing from X-Plane itself. The original aircraft is using custom avionics, separate navdata or an aircraft-specific configuration.
- Check nearest-airport criteria. If Direct-To finds the airport but NRST does not, reduce the minimum runway length and permit all runway surfaces where those options are exposed. Short grass strips and seaplane bases are commonly excluded by these filters.
- Temporarily disable custom navdata. Quit X-Plane, back up the root-level
Custom Datafolder and rename it to something such asCustom Data.disabled. Restart X-Plane and test the stock G1000. If the airport returns, reinstall one complete navigation-data set at the correct folder level; do not merge files from different cycles. Restore the original folder name if the test makes no difference. - Isolate airport scenery. Temporarily move only the custom packages covering that airport outside
Custom Scenery, then restart X-Plane. An old package can contain an incorrect airport ID or override a newer default airport definition. Check our instructions for checking X-Plane 12 scenery folder structure and package priority before changingscenery_packs.ini. - Read the loading log. After closing X-Plane, inspect
Log.txtin the main simulator folder for errors mentioningapt.dat, navigation data or CIFP files. If default files are damaged, use the X-Plane installer or the platform's file-verification function. Our instructions for repairing or restoring X-Plane's default scenery files cover the scenery side without requiring a complete reinstall.
An expired navigation cycle does not automatically make airports disappear. Updating helps when the airport is new, has changed identifier or gained procedures since the installed cycle; it is not the first fix for an established airport that has always worked.
Why can I see the airport but not its approaches?
An airport record and its instrument procedures are separate data.
If Direct-To recognises the airport but the PROC page lists no approaches, the airport itself is not missing. It may have no published instrument procedures, the installed cycle may pre-date them, or the CIFP procedure files may be incomplete. A runway-number mismatch between old scenery and newer navdata can also produce confusing procedure or runway selections.
Install a single, internally consistent navigation-data cycle and restart X-Plane. Do not copy individual procedure files between cycles, and do not expect updating scenery alone to add an approach.
Can custom scenery add the missing airport?
A correctly authored airport definition can add basic location and runway information, but visual scenery alone cannot create a complete G1000 navigation entry.
Buildings, taxiways and textures do not supply instrument procedures. An airport also needs a valid identifier and airport record, while approaches require matching navigation procedure data. Our overview of what airport scenery editors can and cannot change explains this boundary.
If the field is genuinely new, private or absent from X-Plane's database, use updated airport data or a correctly authored airport package. A user waypoint or nearby fix can serve as a temporary destination, but it will not create an airport facility, runway selection, NRST entry or instrument approach in the G1000.