Learn what an FS2004 AIR file stores, how it works with aircraft.cfg, and how to edit flight dynamics safely without breaking the aircraft.
An .AIR file in Microsoft Flight Simulator 2004 (FS9) is a binary data file used by an aircraft's flight model. It stores aerodynamic and engine lookup tables that influence lift, drag, stability, control response and performance. FS2004 combines those records with aircraft.cfg; neither file alone defines the complete behaviour.
What data is stored in an FS2004 AIR file?
The AIR file contains numbered binary records rather than readable configuration lines. Depending on the aircraft and engine type, those records can include:
- Lift, drag and pitching-moment coefficient tables.
- Stability derivatives affecting pitch, roll and yaw behaviour.
- Control-surface response data and related aerodynamic coefficients.
- Engine or propeller performance tables used at different speeds, altitudes and operating conditions.
- Legacy flight-model values that have no direct equivalent in
aircraft.cfg.
It does not contain the visible 3D model, textures, panel or sounds. Our component-by-component overview of an FS2004 aircraft explains how the AIR file fits alongside those other files.
How does the AIR file affect FS2004 flight dynamics?
FS2004 reads the AIR tables as inputs to its flight-dynamics calculations, combining them with the aircraft's weight, centre of gravity, geometry, controls and atmospheric conditions.
For example, changing a drag table can alter acceleration, descent rate and maximum speed. Adjusting lift or pitching-moment data can change stall behaviour, trim requirements and longitudinal stability. Engine-table changes may affect thrust or power as altitude, Mach number or RPM varies.
These effects interact. A stronger engine does not guarantee the expected climb rate if drag, weight or propeller efficiency is wrong, and an apparently small stability change can produce persistent pitch oscillation. The AIR file should therefore be treated as one half of a matched flight model, not as an independent performance preset.
How does FS2004 find the correct AIR file?
Each aircraft variation identifies its AIR file through the sim= entry in the relevant [fltsim.x] section of aircraft.cfg.
If the entry says sim=MyAircraft, FS2004 looks for MyAircraft.air in that aircraft's folder, normally beneath [FS2004 folder]\Aircraft\. The extension is omitted from the sim= line. Multiple liveries usually point to the same AIR file.
Renaming an AIR file without updating sim=, or copying an aircraft.cfg that names a different file, prevents FS2004 from loading that aircraft configuration correctly. A mistake we see constantly is editing the most obvious AIR file in a folder without first checking which filename the active [fltsim.x] entry actually references.
AIR file versus aircraft.cfg
The AIR file supplies binary coefficient tables, while aircraft.cfg supplies readable aircraft definitions and many scalar tuning values.
| File | Format | Typical responsibilities |
|---|---|---|
AircraftName.air | Binary records | Aerodynamic coefficient tables, stability data and engine-performance lookup tables |
aircraft.cfg | Plain text | Aircraft variations, dimensions, mass and balance, contact points, fuel, engine placement, controls, effects and numerous flight-model settings |
Some values represented in older AIR records also have aircraft.cfg equivalents. The configuration entry commonly overrides the corresponding legacy value, but this is parameter-specific; not every AIR record has a text-based replacement. Editing both copies at once makes it difficult to tell which value FS2004 is using.
How can I edit an FS2004 AIR file safely?
Edit an AIR file only with an AIR-aware tool, keep its matching aircraft.cfg beside it, and test one controlled change at a time.
- Identify the active file. Check the selected variation's
sim=line rather than assuming that every AIR file in the folder is used. - Back up the complete aircraft folder. At minimum, preserve untouched copies of both the AIR file and
aircraft.cfg. - Use a suitable editor. The official FS2004 SDK pack containing FSEdit provides Microsoft's aircraft-editing tools. Do not open and resave an AIR file as ordinary text.
- Establish a repeatable baseline. Record fuel, gross weight, centre of gravity, weather, altitude and realism settings before comparing results.
- Change one parameter family. Work on lift, drag, stability or engine performance separately. Our practical tutorial on tuning FS2004 aerodynamic parameters provides useful background for this process.
- Reload and test the aircraft. Select another aircraft and return to the edited one, or restart FS2004, so the flight model is loaded again. Check trim, stalls, climb, cruise and landing behaviour rather than testing only maximum speed.
Why did my AIR file change have no effect?
An AIR edit usually appears ineffective because FS2004 loaded a different file, retained the previous model in memory or obtained the relevant value from aircraft.cfg.
- Wrong AIR file: verify the exact basename specified by
sim=. - Configuration override: search
aircraft.cfgfor a corresponding flight-model or engine setting. - Aircraft not reloaded: switch aircraft or restart FS2004 after saving the edit.
- Test conditions changed: weight, centre of gravity, weather and realism settings can conceal or exaggerate a small adjustment.
- Custom gauge or module logic: some complex add-ons calculate parts of their engine or control behaviour outside the standard AIR tables.
Do not substitute an arbitrary AIR file merely because the source aircraft looks similar. Its aerodynamic tables must agree with the recipient's geometry, weight, inertia and engine definitions. An example Boeing 727 dynamics package pairing a tuned AIR file with aircraft.cfg demonstrates why flight-dynamics replacements are normally distributed as matched files.