Learn why FSX ATC assigns the wrong altitude, how to fix flight-plan and altimeter errors, and what to do when a clearance is unsafe.
In FSX and FSX: Steam Edition, ATC usually assigns the “wrong” altitude because it follows the active flight plan and simplified terrain and approach logic, not full real-world SID, STAR or vectoring-altitude data. If ATC says you are high or low, an incorrect altimeter setting is more likely than a bad clearance.
Is the clearance wrong, or is the altimeter wrong?
An unsuitable clearance and an altitude-reporting mismatch are separate problems, and the symptoms usually reveal which one you have.
| What happens | Likely cause | What to check |
|---|---|---|
| ATC assigns an unexpected cruise altitude | The active FSX flight plan contains that altitude, or an older plan remains loaded | Open the Flight Planner and verify the loaded plan’s cruising altitude |
| ATC repeatedly says you are above or below the assigned altitude | Incorrect barometric pressure, a custom gauge that did not update, or an autopilot capture error | Reset the altimeter and compare the primary and standby instruments |
| The assigned altitude looks wrong relative to the ground | Confusion between MSL and AGL | FSX ATC clearances are expressed as altitude above mean sea level, not height above the terrain |
| ATC descends the aircraft too early or vectors it towards high ground | Simplified approach and terrain logic, sometimes made worse by conflicting scenery | Check terrain clearance independently and do not continue an unsafe descent |
| ATC ignores the altitude entered in an FMC | Built-in ATC reads the active FSX flight plan, not the add-on FMC | Load a matching FSX IFR plan |
Below the applicable transition altitude, use the local pressure setting reported by ATIS or ATC. The default B command resets the altimeter, while standard pressure should be used at flight levels where required. Some complex add-on aircraft use custom gauges that may need to be adjusted separately.
Our explanation of pressure, altitude and simplified simulator ATC logic covers why a correct-looking cockpit indication can still disagree with the controller.
Why FSX chooses an unsuitable altitude
FSX bases its IFR altitude instructions on the loaded plan, its internal airway and airport data, and a comparatively rigid climb-and-descent sequence.
- Filed cruise altitude: ATC normally works towards the cruising altitude stored in the active plan. Changing an FMC or GPS entry alone does not change that plan.
- Intermediate clearances: An initial altitude after take-off may be a temporary restriction rather than the final cruise level. Wait for the next clearance unless terrain or aircraft performance makes the instruction unsuitable.
- Simplified procedure handling: Default ATC does not reproduce every published minimum vectoring altitude, SID, STAR or altitude restriction.
- Rigid descent sequencing: The controller may keep an aircraft high too long, descend it early, or issue repeated changes near the destination.
- Scenery conflicts: Duplicate or incompatible airport scenery can produce disagreements over airport position, runway use or elevation.
How do I correct a wrong FSX ATC altitude?
Correct the active flight plan first, then check pressure settings and request an in-flight altitude change if necessary.
- Verify the loaded plan. Confirm that it is IFR and that its cruising altitude is suitable for the route, terrain, aircraft and direction of flight. Our guide to setting and loading an FSX flight plan explains which plan values built-in ATC actually uses.
- Remember that clearances use MSL. At an airport 2,000 feet above sea level, an assignment of 3,000 feet provides only about 1,000 feet above the airport.
- Set the altimeter correctly. Obtain the local setting from ATIS or ATC, or use
Bwith a default aircraft. Recheck it after entering a new pressure region or if weather changes abruptly. - Request a different altitude. Use the higher- or lower-altitude request in the ATC window when that option is available. Do not simply select another autopilot altitude and expect ATC to accept it.
- Plan the descent yourself. Treat FSX ATC’s descent calls as instructions from a limited simulator system, not as proof that terrain clearance or an ideal vertical profile is guaranteed. Our gate-to-gate FSX procedure shows how to prepare for late or awkward descent clearances.
If ATC continues reporting an altitude error after resetting the pressure, confirm that the autopilot has actually captured the selected altitude rather than remaining in vertical-speed mode. With add-on aircraft, also check whether the primary display and standby altimeter show the same value.
Can FSX ATC assign an unsafe low altitude?
Yes. FSX ATC can issue a descent or vector that provides inadequate terrain clearance, particularly in mountainous areas or around airports modified by add-on scenery.
Do not follow a virtual clearance into terrain. Stop the descent, maintain a safe altitude and request a higher level if the ATC menu permits it. If the controller cannot provide a usable clearance, cancel the simulated IFR service and continue using your own safe routing and approach plan. See our focused advice on handling low ATC altitude assignments.
If the problem occurs at only one airport, test without overlapping airport scenery and compare the airport elevation shown in FSX with the value used by your charts or flight plan.
Will FSX ATC follow an FMC, SID or STAR?
No. Default FSX ATC does not read an add-on aircraft’s FMC or honour SID and STAR altitude constraints as a real controller would.
You can place many procedure waypoints into an FSX-compatible flight plan, but ATC may still issue its own vectors and altitude changes. For the least conflict, keep the route and cruise altitude in the FMC consistent with the active FSX IFR plan, then monitor terrain and procedure restrictions yourself.