How do I calculate A320 landing distance in a simulator?
To calculate Airbus A320 landing distance in a flight simulator, begin with a dry, level, still-air baseline for your expected landing weight and landing configuration, then adjust for wind, runway condition, slope, elevation, temperature, braking setup and touchdown point. Compare that corrected figure with the runway's landing distance available, not simply the charted runway length.
What figures do you need before you calculate A320 landing distance?
You need six inputs before any A320 landing-distance figure means much: expected landing weight, exact flap configuration, runway, weather, deceleration method and touchdown point.
- Expected landing weight: use your estimated weight at touchdown, not take-off weight.
- Landing configuration: an A320 in CONF FULL will not use the same distance as CONF 3.
- Runway data: use LDA, plus slope, elevation and surface condition.
- Wind and temperature: headwind helps, tailwind hurts, and hot/high conditions reduce stopping margin.
- Braking plan: autobrake setting or manual braking, reverse thrust use, and normal spoiler deployment.
- Touchdown plan: aim for the touchdown zone; landing long adds distance metre for metre.
If you are flying in Microsoft Flight Simulator, our guide to setting up the A320 MCDU/FMS for the right runway and arrival helps you load the approach and performance basics before you work out the stop.
Do not mix sources. Real-aircraft A320 tables, airline tools and simulator add-ons do not all model the same braking, tyre friction and reverse-thrust behaviour, so use data that belongs to the A320 you are actually flying.
Do you use runway length or LDA?
Use LDA. The full runway may include a displaced threshold or pavement you cannot count on for landing, so the planning number is the landing distance available from the threshold you will actually cross.
How to calculate A320 landing distance in a simulator
The reliable method is to start with a base landing figure for your exact aeroplane model or add-on, then only make conservative corrections.
- Set the expected landing weight. Work from your predicted weight at destination, including any fuel you expect to burn during approach, holding or a missed approach.
- Choose the real landing configuration. If you plan to land in CONF FULL, calculate with FULL. If operational reasons mean CONF 3, use CONF 3 numbers and expect more runway.
- Take a dry-runway baseline. The best source is the add-on's own EFB, FMS or manual. If it has no landing-performance page, use a repeatable dry, level, no-wind baseline for that specific add-on rather than guessing from another A320.
- Add runway and weather penalties. Increase the figure for wet or contaminated runway, any tailwind, downhill slope, high-elevation airfields and hot conditions. Do not spend all the benefit of a headwind; treat it as a bonus, not a licence to use a marginal runway.
- Add any long-touchdown distance. If you touch down 250 metres beyond the planned point, add at least 250 metres to the runway you need. Float is runway used, full stop.
- Add operating margin. Treat the calculation as a minimum stopping figure, not a target. If the runway length only just matches the number, it is not a comfortable landing plan.
- Compare the result with LDA. If the margin is slim, change something before descent: lighter landing weight, a different runway, lower tailwind component, a different flap choice if appropriate, or a diversion.
A stable final matters as much as the arithmetic. If you arrive fast or high, the landing-distance plan is already broken. For MSFS 2024, our guide to flying a stable ILS approach shows how to reach the threshold on speed and on profile.
What changes A320 landing distance the most?
In flight simulation, speed, touchdown point and runway state usually move the number far more than people expect.
| Factor | Why it matters | Practical rule |
|---|---|---|
| Approach speed | Extra speed means much more kinetic energy to lose after touchdown. | Do not plan from a fast approach. Even a small speed excess can add a noticeable amount to the rollout. |
| Touchdown point | Runway used in the flare cannot be recovered by braking harder. | Add late-touchdown distance metre for metre. |
| Runway condition | Wet or contaminated surfaces reduce braking effectiveness. | Be markedly conservative or choose a longer runway. |
| Wind | Tailwind raises groundspeed at touchdown. | Treat any tailwind as a major penalty on shorter runways. |
| Configuration | CONF FULL and CONF 3 do not stop the same way. | Use figures for the exact flap setting you will fly. |
| Deceleration devices | Spoilers, wheel braking and reversers all affect rollout. | Any forgotten spoiler arm or weak brake application makes the plan optimistic. |
Which mistakes make simmers underestimate A320 landing distance?
The common mistake is assuming the A320 will always save the day with autobrake and reverse thrust.
- Using runway length instead of LDA. Total concrete is not the planning number.
- Using dry figures for a wet runway. This is one of the quickest ways to arrive short on margin.
- Ignoring a small tailwind. Five knots of tailwind can matter more than people think because it raises groundspeed, not indicated speed.
- Counting on reverse thrust to rescue a float. Reverse helps after touchdown, but it cannot give back runway lost in the flare.
- Landing in the wrong configuration. CONF 3 planned like CONF FULL is a bad trap.
- Touching down long after a float. A320 rollouts that look poor in the sim are often long landings, not weak brakes.
- Forgetting spoilers or autobrake logic. If ground spoilers do not deploy, stopping distance will be much worse than planned.
- Trying to rescue an unstable approach. If you are not on speed, on path and likely to land in the touchdown zone, the right fix is to go around correctly in the A320, not force it on.
Crosswind changes the touchdown technique too. In windy conditions, our guide to handling a crosswind landing in a flight simulator helps you avoid drift, side-load and the long float that often follows a poor de-crab.
How much safety margin should you add?
You should add enough margin that a normal landing still leaves obvious runway spare, because simulator flight models and braking friction vary between A320 add-ons.
We do not recommend planning to use 100 per cent of the calculated figure. If your add-on already gives both a raw landing distance and a more conservative required distance, use the conservative one. If it gives only a bare stopping figure, add your own buffer and be stricter still on wet, downhill, tailwind or short-runway arrivals.
A mistake we see constantly is borrowing landing figures from a different A320 model altogether. That makes the calculation look precise when it is not.
What if your A320 add-on gives no landing performance data?
If your A320 add-on has no landing-performance page, build a baseline for that add-on and keep it conservative.
- Pick a dry, level runway with plenty of spare length.
- Fix the variables: one landing weight, one flap configuration, one autobrake or braking technique, and nil wind.
- Fly a properly stable approach and touch down in the touchdown zone at the correct speed.
- Measure touchdown-to-stop distance, not threshold-to-stop distance.
- Repeat and keep the longest good run as your dry baseline for that weight and configuration.
- Add margins for anything worse: wet runway, tailwind, slope, hotter weather or a runway where you know you tend to float.
That will not turn the add-on into a certified performance tool, but it gives you a consistent planning method for your own simulator flying.