FS2004 engines start switched off when a cold-and-dark default flight or add-on state loads. Identify the cause and restore a normal running start.
FS2004 usually starts your engines switched off because it is loading a default flight saved after shutdown, or a replacement FLTSIM.FLT configured for a cold-and-dark cockpit. Save a new default flight with the engines running. If only one add-on is affected, change that aircraft’s panel-state setting instead.
Why does FS2004 remember an engines-off state?
FS2004 stores aircraft, engine and cockpit conditions in its default flight, rather than rebuilding every flight with the engines running. If that flight was saved after shutdown, its next flight can inherit the same state.
A common cause is a modified FLTSIM.FLT, normally found under the simulator’s Flights\Other folder. If the behaviour began after installing a replacement default-flight file designed to create a dark cockpit, the switched-off engines are intentional.
| Symptom | Likely cause | Best fix |
|---|---|---|
| Most aircraft start shut down | Cold-and-dark default flight | Save a new running default flight |
Problem began after replacing FLTSIM.FLT | Modified startup template | Restore the backed-up original |
| Only one add-on is affected | Aircraft-specific panel state | Select its ready-to-fly state |
| Engines start and immediately stop | Mixture, condition lever or hardware axis at cut-off | Correct the control position or assignment |
How do I make FS2004 start with engines running?
Create and save a new default flight after starting a standard FS2004 aircraft.
- Load a default aircraft. Using a stock aircraft separates a global FS2004 setting from add-on-specific logic.
- Prepare the controls. Apply the parking brake, close the throttle and set the mixture appropriately for the aircraft.
- Start the engines. Press
Ctrl+Eand wait for all engines to stabilise. - Save the flight. Use FS2004’s Save Flight command, give the flight a recognisable name and select the option to make it the default flight.
- Restart FS2004. Load the normal startup flight and confirm that the engines remain running.
The saved flight also records the aircraft, airport, position, weather and other supported cockpit states. Set those as you want them before making it the default; otherwise FS2004 may open at an unwanted location or in unsuitable weather.
If you manually replaced FLTSIM.FLT, close FS2004 and restore the original backup in Flights\Other. Back up the modified file first rather than deleting it permanently.
Why does only one add-on aircraft start cold and dark?
An aircraft-specific state loader is the likely cause when stock aircraft start normally but one add-on remains shut down. More detailed aircraft often reconstruct their electrical, fuel and engine states through custom gauges after the flight has loaded.
Look on the aircraft’s panel, configuration utility or aircraft menu for a state labelled ready to fly, engines running, turnaround or cold and dark. The wording varies between add-ons. If no running state is provided, follow the aircraft’s own checklist; our FS2004 cold-and-dark starting guidance covers the simulator-level controls without replacing an add-on’s required procedure.
Why will Ctrl+E not start the engines?
On default FS2004 aircraft, Ctrl+E should normally perform an automatic start, so failure points to fuel, controls, failures or custom add-on logic.
- Check fuel quantity and selectors. A saved flight can retain empty tanks or a closed selector.
- Check mixture and condition controls. Piston mixture at idle cut-off and turbine fuel or condition levers at cut-off will prevent sustained operation.
- Inspect hardware axes. A throttle quadrant can immediately overwrite the keyboard command, especially if a mixture or condition-lever axis is assigned incorrectly.
- Clear active failures. A saved engine or fuel-system failure may load again with the flight.
- Respect add-on procedures. Some complex panels bypass FS2004’s automatic start and require their own battery, fuel-pump, ignition and starter sequence.
If an engine lights and then dies, check the mixture, fuel-cut-off and assigned hardware axes first. That pattern usually means the simulator received the start command correctly but another control immediately removed the fuel supply.