Fix FS2004 crashes when approaching an add-on airport by isolating bad BGLs, duplicate AFCADs, AI traffic, mesh conflicts and memory limits.
FS2004 usually crashes near an add-on airport because a faulty or incompatible BGL, duplicate AFCAD, bad scenery object, or AI aircraft loads as you enter the area. Disable the airport first; if the crash stops, re-enable its files in small groups, then check scenery priority, dependencies, duplicate airport files and memory use.
Common causes of airport approach crashes
A repeatable crash at roughly the same distance from one airport normally points to something being loaded in that scenery cell, rather than a general FS2004 stability problem.
- Damaged or incompatible scenery files: a malformed airport, object-library, placement or texture file can cause a crash to desktop. Files compiled for a different simulator or scenery version can also be incompatible.
- Duplicate airport definitions: two active AFCAD-style BGLs may define the same airport, approaches or navaids. Duplicates more often produce misplaced runways and confused AI traffic, but some combinations can trigger crashes.
- Object-library problems: a missing library usually leaves objects absent, whereas a corrupt or mismatched library can crash FS2004 when the affected model is requested.
- AI aircraft: a faulty AI model, repaint or traffic package may load only when a scheduled aircraft appears near the destination.
- Terrain conflicts: local mesh, flatten, exclude or landclass files can clash at the airport boundary, particularly when the failure occurs from one arrival direction.
- Memory exhaustion: FS2004 is a 32-bit application. A detailed airport combined with complex aircraft, AI traffic, clouds and overlapping scenery can exhaust its available address space.
What does the crash pattern reveal?
The conditions under which the crash occurs are often more useful than the crash message itself.
| Crash pattern | Most likely area | Best first test |
|---|---|---|
| Every approach with the add-on active | Airport BGL, model, texture or dependency | Disable the airport in the Scenery Library |
| Only from one direction | Nearby placement file, terrain tile, mesh or flatten | Disable regional scenery and mesh around the airport |
| Only at a certain time | Scheduled AI aircraft or night texture | Set AI to zero and test at midday |
| Only with heavy traffic | AI model, repaint or traffic BGL | Set both airline and general-aviation AI sliders to zero |
| Only with a complex aircraft or bad weather | Memory pressure or an aircraft gauge | Use a default aircraft, fair weather and lower scenery settings |
| Even after the airport is disabled | Global mesh, AI, overwritten default file or saved-flight problem | Create a fresh flight under controlled conditions |
How do I find the faulty FS2004 scenery file?
The safest method is to prove which scenery area causes the crash, then narrow it down without deleting anything.
- Back up the package. Copy its complete folder to a location outside FS2004. Record any files the installer placed elsewhere, especially in global scenery or texture folders.
- Create a controlled test. Start far enough from the airport to reproduce the approach, using a default aircraft, fair weather, midday conditions and zero AI traffic. Restart FS2004 between major tests.
- Disable the airport. Untick its area in the Scenery Library, restart the simulator and repeat the same approach. If the default airport works, the package or one of its interactions is responsible. Check the correct FS2004 scenery folder, activation and priority procedure before editing files.
- Remove competing airport definitions. Search all active add-on scenery folders for files referring to the airport ICAO code. Many AFCAD files include that code in their name, but naming is not universal. Move suspected duplicates outside the simulator rather than deleting them. Scenery priority does not make two conflicting AFCADs safe; keep the airport definition intended for the installed scenery. Our AFCAD inspection and editing workflow explains how to examine an airport without overwriting the stock data.
- Verify the package and dependencies. Confirm that it is the FS2004 edition and install any required object libraries exactly as documented. Re-extracting a clean copy can repair an incomplete download. Do not solve a missing dependency by dumping unrelated libraries and textures into global folders.
- Isolate the BGLs. If the package still crashes, move half of its
.bglfiles from the activeSceneryfolder into a temporary folder, restart and test. Repeat with the failing half until a file or small group is identified. Several BGLs may depend on one another, so treat the result as a suspect set rather than immediately deleting the last file. - Test nearby terrain separately. Disable local mesh, landclass and regional scenery one package at a time. Direction-dependent crashes are especially suspicious. Use our guidance for diagnosing terrain mesh, flatten and elevation conflicts rather than changing every scenery layer at once.
What if FS2004 crashes only with AI traffic?
If setting both AI traffic categories to zero stops the crash, the airport scenery may be innocent.
Restore traffic packages in groups and repeat the same flight at the same simulated time. A scheduled aircraft may enter the area or receive a parking assignment just before the crash. Concentrate on recently added AI models, repaints and traffic BGLs, especially packages used only at that airport.
A time-specific failure can also involve night textures. Test the same approach in daylight with AI disabled; then enable AI while keeping the time unchanged. That separates scheduled traffic from day-and-night scenery behaviour.
Could FS2004 be running out of memory?
A high-detail airport can be the trigger for a memory crash even when none of its files is defective.
This is likely when the airport works with a default aircraft and low traffic but fails with a complex cockpit, dense AI, heavy clouds or several overlapping regional packages. FS2004 may close without displaying a clear out-of-memory warning.
- Use any lower-resolution texture option supplied with the airport.
- Reduce AI traffic, scenery complexity, autogen and cloud load.
- Disable overlapping scenery that is not needed for the flight.
- Avoid repeatedly changing aircraft and locations during the test; restart FS2004 for a clean comparison.
If lowering demand only moves the crash point closer to the airport, suspect memory pressure. If it always fails at precisely the same point regardless of settings, a specific scenery, terrain or AI file remains more likely.
Reinstalling FS2004 is the last resort
Do not reinstall the whole simulator when the default airport works after the add-on is disabled.
An airport installer may have overwritten files outside its own folder, in which case unticking its Scenery Library entry is not a complete removal. Restore known-good backups or follow our safe add-on removal and rollback process. Repair or reinstall FS2004 only if default scenery continues to crash after all add-on files and overwritten components have been removed.