Edit FS2004 aircraft flight dynamics safely using aircraft.cfg, AIR files and FSEdit, with testing steps and fixes for ignored or broken changes.
To edit aircraft flight dynamics in FS2004, make a backup, change the appropriate values in aircraft.cfg, and use an FS2004-compatible AIR-file editor such as Microsoft’s FSEdit for data stored in the binary .air file. Alter one variable at a time, reload the aircraft, and compare repeatable tests at identical weight, fuel, weather and realism settings.
What is an FS2004 flight editor, and which file does it edit?
An FS2004 flight editor is a tool used to modify the data from which the simulator calculates an aircraft’s performance and handling.
Here, flight means the aircraft flight model, not a saved flight or route. Editing a VFR flight plan in a .pln file changes where you fly; it does not change lift, drag, stability or engine performance. Saved .flt files are separate as well.
| File or tool | Purpose | When to use it |
|---|---|---|
aircraft.cfg | Defines geometry, mass, centre of gravity, moments of inertia, control scalars, engines, propellers, flaps and landing gear | Start here for most performance, balance and control-response fixes |
.air file | Contains binary aerodynamic records and tables, including data used for lift, drag and pitching behaviour | Use when credible physical data and configuration values cannot produce the required aerodynamic behaviour |
FSEdit and SDK documentation | Microsoft’s aircraft-editing tools and definitions for FS2004 | Obtain them from the FS2004 SDK pack containing the official editing tools |
.mdl file | Provides the visible model and animations | Not normally edited to change flight dynamics, although its visual geometry can expose mismatched contact points or control animations |
The FS9 flight-dynamics engine reads aircraft.cfg and the selected AIR file together. Under the active repaint’s [fltsim.x] section, sim=MyAircraft tells FS2004 to load MyAircraft.air from that aircraft folder. A mistake we see repeatedly is editing an AIR file that the active sim= entry does not reference.
How do I edit and test FS2004 flight dynamics safely?
The safest method is to build a separate test aircraft, establish a measured baseline and change only one related value or table per test cycle.
- Back up the complete aircraft folder. FS2004 normally keeps each installed aircraft beneath its main
Aircraftdirectory. Store the untouched backup outside that directory so FS2004 does not try to load it as another aircraft. - Create a separate test copy. Copy the working folder into the
Aircraftdirectory and give everytitle=entry in itsaircraft.cfga unique name. Titles must be unique across the installation; changing only the folder name is not enough. Our aircraft.cfg backup and syntax checklist covers safe text editing in more detail. - Identify the active AIR file. Find the
[fltsim.x]section for the variation you intend to test and read itssim=value. Make file extensions visible in Windows and do not rename the AIR file unless you update the matching entry. - Record an unchanged baseline. Fix the fuel load, payload, centre of gravity, weather, realism settings and aircraft configuration. Record measurable results such as clean and landing-configuration stall speeds, climb time through a fixed altitude band, stabilised cruise speed, engine indications and fuel flow.
- Correct physical data in aircraft.cfg first. Use a plain-text editor, retain the established section names and spellings, and use a full stop as the decimal separator. Check each parameter’s units in FS2004 documentation rather than assuming that similar-looking entries use the same units.
- Edit AIR records only when necessary. A
.airfile is binary and must not be saved through a text editor. Use a tool compatible with FS2004, retain an untouched copy outside the working folder, and keep a written log of every record and value changed. - Force the aircraft to reload. Load a different aircraft and then reselect the test model. Restart FS2004 if AIR-file changes still appear to be cached.
- Repeat the same test. Reject or revert an unsuccessful change rather than hiding it with unrelated scalars. Once thrust, drag, lift and control effectiveness are all changed together, the source of a new problem becomes difficult to isolate.
Which values should I change to fix the flight model?
Fix geometry, weight, balance and powerplant data before using tuning scalars or reshaping AIR-file coefficient tables.
| Observed problem | Check first | Common mistake |
|---|---|---|
| Controls are too sensitive or too weak | Control-surface geometry, centre of gravity, indicated airspeed and effectiveness values in [flight_tuning] | Changing wing dimensions or all three control axes together |
| Aircraft oscillates or feels unnaturally stable | CG position, moments of inertia, stability scalars and the relevant aerodynamic derivatives | Testing with the autopilot or a stability-assistance gauge still commanding the controls |
| Trim is badly wrong | CG, wing and tail incidence, pitching-moment data and tail geometry | Using extreme elevator effectiveness to conceal a balance or pitching-moment error |
| Stall speed or stall break is wrong | Test weight, wing area, flap configuration and AIR-file lift, drag and pitching-moment curves | Editing only [reference speeds]; those values do not reconstruct the aerodynamic stall |
| Cruise or maximum speed is wrong | Engine output, propeller data where applicable, parasite drag and induced drag | Increasing or reducing power without checking the resulting climb performance and fuel flow |
| Climb rate is wrong | Weight, power or thrust, propeller efficiency, drag and the airspeed flown during the test | Increasing lift alone, which can damage stall and cruise behaviour without correcting excess power |
| Aircraft sinks, floats or bounces on the runway | [contact_points], static pitch, static height, damping and CG position | Using aerodynamic scalars to disguise landing-gear geometry; use the contact-point diagnosis and correction procedure instead |
The configuration sections most often involved are [airplane_geometry], [flight_tuning], [weight_and_balance], [GeneralEngineData], the section for the installed engine type, [propeller], flap sections and [contact_points]. Their effects overlap: extra thrust may repair one climb figure while creating excessive cruise speed, for example.
Move into coefficient tables only after the aircraft’s dimensions, weights, balance and powerplant data are credible. Our technical tutorial on FS2004 aerodynamic coefficients and their interactions provides the deeper background needed for AIR-record work.
Can I copy flight dynamics from another aircraft?
A donor flight model is a sensible starting point only when the aircraft have closely comparable geometry, mass distribution, engine type, control arrangement and performance.
The AIR file and aircraft.cfg work as a pair. Copying an unrelated AIR file may produce believable cruise numbers while leaving the stall, trim, inertia, propeller response or stability badly wrong. If a donor must be used, transfer one system at a time and validate it across the operating envelope.
Can FSEdit fix a fly-by-wire aircraft?
FSEdit can change the underlying FS2004 airframe, but it cannot by itself reproduce a complete fly-by-wire control law.
Complex FS2004 add-ons may use XML or compiled gauges and modules to modify control inputs, trim or engine commands. Those systems can mask changes made in aircraft.cfg or the AIR file, so test the model with its intended systems active. FlyByWire-branded aircraft packages made for modern Microsoft Flight Simulator use a different package and flight-model architecture and cannot be transplanted into FS2004.
Why are my Flight Editor changes ignored, and how do I fix them?
Ignored edits usually mean FS2004 loaded another file, retained the aircraft in memory, rejected malformed data or had its behaviour overridden by add-on logic.
- Wrong AIR file: compare the edited filename with the exact
sim=value under the active[fltsim.x]entry. - Wrong aircraft copy: verify the selected menu title and the timestamp of the file inside the folder FS2004 actually loads.
- Duplicate titles: every
title=value in the test copy must be unique, including liveries you are not actively testing. - Shared repaint: variations in one aircraft folder usually share the same configuration and AIR file. A dynamics change therefore affects every repaint pointing to those files.
- Protected installation folder: legacy FS2004 installations under a protected Windows directory may have writes blocked or redirected. Reopen the edited file and confirm that the value and modification time really changed.
- Invalid syntax or units: misspelt keys, misplaced entries, comma decimal separators or incorrect unit conversions can be ignored or produce misleading behaviour without a useful error message.
- Aircraft still cached: select another model or restart the simulator after AIR-file work.
- Autopilot or gauge logic: disconnect automatic control systems and check whether custom gauges are replacing engine, trim or control commands.
- Incompatible editor: an editor designed for another simulator may misread or damage FS2004 AIR records. Restore the backup and use an FS2004-aware tool.
What should I do if the edited aircraft disappears from FS2004?
An aircraft that vanishes from the selection menu usually has a damaged configuration file, a duplicate title or a missing AIR file.
Restore the backup first. Then check that the file is still named aircraft.cfg rather than aircraft.cfg.txt, that its [fltsim.x] sections remain intact, that each title= is unique and that every sim= entry points to an AIR file present in the same aircraft folder.
How do I judge whether the edited flight model is accurate?
Judge an edited model against repeatable performance points and behaviour across several speeds, not by how convincing it feels during one circuit.
Compare stalls at the same weight and configuration, climb at the same indicated airspeed and power setting, and cruise only after altitude, speed and engine indications have stabilised. Test take-off, low-speed control, trim, stability, descent and landing as well as the headline cruise figure.
Keep indicated, calibrated and true airspeed separate when comparing simulator results with published data. Real aircraft figures may assume a specific weight, pressure altitude, temperature, configuration or measurement method. Forcing one number to match under different conditions can make the rest of the model less accurate.
FS2004 also has limitations in its aerodynamic, propeller and ground-friction modelling. Prefer a model that behaves consistently across its useful envelope over one tuned to hit a single published value at the expense of stalls, trim or climb.
Does this flight-editing method apply to FSX or modern Microsoft Flight Simulator?
This procedure and the FSEdit references are specifically for Microsoft Flight Simulator 2004, also known as FS9.
FSX retained a broadly related aircraft.cfg and AIR-file structure, but parameter support and tools differ, so an FS2004 model should not be assumed to transfer unchanged. Prepar3D versions also have their own differences. Microsoft Flight Simulator 2020 and 2024 use package-based configuration files and newer flight-model systems; FS2004 FSEdit is not an appropriate editor for them.