FS2004 overspeed warning at every altitude? Learn how IAS, Mach and the barber pole set the limit, plus how to diagnose false add-on warnings.
FS2004 shows an overspeed warning whenever the aircraft exceeds its configured maximum indicated airspeed or maximum Mach number. Altitude does not cancel the limit: at lower levels IAS usually governs, while higher up the Mach limit can trigger the warning at a lower IAS. Slow below the barber pole.
Which speed triggers the FS2004 overspeed warning?
FS2004 normally compares the aircraft’s speed with its maximum indicated airspeed and maximum Mach limits, not with true airspeed or GPS groundspeed. The applicable limit depends on the aircraft and flight level.
| Speed reading | What it represents | Does it set the overspeed limit? |
|---|---|---|
| IAS or KIAS | Airspeed indicated on the cockpit instrument | Yes, usually at lower and middle altitudes |
| Mach | Speed relative to the local speed of sound | Yes, often the controlling limit at high altitude |
| TAS | Actual speed through the air mass | No, not directly |
| Groundspeed | Speed over the ground, including wind effect | No |
On panels that model it correctly, the red-and-white barber pole marks the maximum permitted speed and moves as the Mach limit becomes restrictive. Our explanations of why IAS and Mach are different and how the barber pole changes with altitude cover those relationships in more detail.
Why is the listed cruise speed too fast in IAS mode?
The cruise speed shown in an aircraft description is not necessarily an IAS target. Jet cruise figures are commonly expressed as true airspeed or Mach, while an autopilot in IAS mode interprets its selected value as indicated knots.
A mistake we see constantly is entering the advertised cruise-speed figure directly into the IAS selector. That can exceed the IAS limit down low and the Mach limit higher up, producing an FS2004 overspeed warning at every altitude. Use the aircraft’s normal IAS or Mach schedule and remain below the barber pole instead.
How do I clear an overspeed warning in FS2004?
Reduce energy smoothly until both IAS and Mach are below their respective limits.
- Reduce thrust or the selected autothrottle speed. If the autopilot is commanding an excessive IAS or Mach value, correct that selection rather than fighting it manually.
- Stop accelerating in a descent. Level the aircraft gradually or reduce the descent rate; use the speed brake if the aircraft permits it.
- Watch both IAS and Mach. At altitude, a modest-looking IAS can still represent excessive Mach.
- Keep a margin below the barber pole. Instrument rounding, turbulence and small autopilot corrections can repeatedly cross the threshold if flown exactly on the limit.
- Do not deploy gear or flaps as an emergency brake above their limits. Those components have separate maximum extension speeds.
For the wider operational context, see our guidance on what an overspeed alert means and how to respond.
Why does the warning begin at a lower IAS higher up?
The warning begins at a lower indicated speed aloft because the aircraft reaches its maximum Mach number before reaching its maximum indicated airspeed. This is normal behaviour for jets.
As altitude increases, the same IAS corresponds to a higher true airspeed and generally a higher Mach number. Once the aircraft reaches the crossover point, Mach becomes the controlling limit. If the autopilot offers separate IAS and Mach modes, use the mode and target appropriate to that phase of flight rather than carrying a high IAS target into the cruise.
What if the warning appears below the barber pole?
A warning far below the expected limit usually points to an aircraft configuration or panel-gauge problem, particularly when it affects only one downloaded aircraft.
- Only one aircraft is affected: its maximum IAS or Mach value may be incorrect, or its flight-model and panel files may come from different versions of the add-on.
- Only one cockpit panel is affected: a custom overspeed gauge may use its own thresholds. Compare its light or sound with FS2004’s standard overspeed indication.
- The warning is only a few knots below the mark: allow more margin. Gauge rounding, gusts and a moving Mach limit can account for a small apparent discrepancy.
- Every aircraft is affected: verify that you are reading IAS rather than TAS or groundspeed, then test an unmodified default aircraft in a fresh flight. If the default aircraft behaves normally, the base simulator is not the cause.
Should I edit the aircraft.cfg file?
Edit the configuration only when an add-on’s speed limits are demonstrably wrong. In many FS2004 aircraft, the relevant entries appear under [Reference Speeds] as max_indicated_speed and max_mach.
Back up the original file and restore the values supplied for that specific flight model rather than increasing them merely to silence the warning. A custom panel gauge may contain independent warning logic, so changing aircraft.cfg will not fix every case.