How do I calculate A320 landing distance in a simulator?
Calculate A320 landing distance using weight, wind, runway condition, configuration and LDA, with clear margins and fixes for common sim errors.
Calculate A320 landing distance with the performance calculator or EFB supplied for your exact add-on. Enter predicted landing weight, LDA, wind, temperature, pressure altitude, slope, runway condition, flap configuration and braking assumptions. Use the tool’s required distance, not a generic formula, and confirm it is comfortably below the runway’s LDA.
This method applies to A320 add-ons in Microsoft Flight Simulator, X-Plane, Prepar3D and FSX, but their figures are not interchangeable. Each product models tyre friction, spoilers, braking and reverse thrust differently. Simulator results must never replace approved aircraft and operator data for real-world flying.
Which landing-distance figure should you use?
Use the required or operational landing distance for your exact A320 model, provided its assumptions match the planned landing.
Start with the add-on’s own EFB, performance calculator or manual. Do not borrow a figure from another developer’s A320, or assume A320ceo and A320neo data are interchangeable. An MCDU approach page may provide VAPP and store weather data without calculating the runway distance required.
| Figure | What it means | How to use it |
|---|---|---|
| LDA | Landing distance available from the landing threshold. It excludes any stopway, clearway and unusable pavement before a displaced threshold. | Compare the required landing distance with this figure, not the physical runway length or TORA. |
| Actual or unfactored distance | A modelled minimum under stated assumptions, often from threshold crossing to a full stop. | Do not treat it as the final runway requirement unless the documentation explicitly says to do so. |
| Required or factored distance | A distance incorporating the performance method’s prescribed operational margin. | Use this for the LDA comparison when every input and assumption matches. |
| Ground roll | Distance from touchdown to a full stop. | Never compare it directly with LDA because it omits the airborne distance between the threshold and touchdown. |
What inputs do you need?
A meaningful A320 landing calculation needs the aircraft’s predicted state at landing and the conditions for the runway actually being used.
- Predicted landing weight: use zero-fuel weight plus the fuel expected to remain at landing, not take-off weight. Check maximum landing weight separately; adequate runway does not make an overweight landing structurally acceptable.
- Approach speed: use the calculated VAPP for the selected configuration and wind correction. Do not substitute VLS or add the gust correction twice.
- Runway data: enter the correct runway, LDA, elevation and slope. Follow the calculator’s slope sign convention rather than assuming positive means uphill.
- Weather: use runway wind component, outside air temperature and either QNH or pressure altitude as requested. Do not enter the full reported wind as a headwind when it is crossing the runway.
- Runway condition: select dry, wet or the specific contaminant offered by the tool. A visually wet simulator runway may not have the same friction assumptions as the performance calculator.
- Landing configuration: select CONF FULL or CONF 3 exactly as planned. CONF 3 normally carries a higher approach speed and usually needs more distance.
- Deceleration assumptions: match the planned autobrake or manual braking, spoiler availability and reverse-thrust credit. Some performance methods do not credit reverse thrust.
- Abnormal conditions: include any simulated system failure, inoperative reverser or other item offered by the calculator.
For the Fenix aircraft, our explanation of finding predicted A320 landing weight and VAPP covers the two inputs most often entered incorrectly. For weather, use our guide to extracting runway wind and gusts from a METAR, then resolve that wind into the component requested by the calculator.
How do you calculate A320 landing distance step by step?
The reliable process is to let one aircraft-specific tool calculate the interacting penalties, then compare its correctly identified output with LDA.
- Select the correct aircraft data. Confirm the A320 variant, engine option and add-on match the performance source.
- Record the runway’s LDA. Check the landing direction and displaced threshold. Keep all distances in consistent units.
- Update the landing conditions. Use the forecast or simulated conditions expected at arrival, then recalculate if the runway, wind or surface state changes.
- Enter the predicted aircraft state. Supply landing weight, VAPP if requested, flap configuration and any relevant system status.
- Match the stopping method. Select the autobrake or manual-braking assumption and reverse setting the tool expects. Do not calculate with strong braking and then fly a gentler plan.
- Read the output label carefully. If both unfactored and required distances are shown, use the required figure. If the label is ambiguous, consult the add-on documentation and treat it conservatively.
- Calculate the remaining margin. Use
runway margin = LDA − required landing distance. A negative result or a calculator warning means the runway is unsuitable under those assumptions. - Resolve a thin margin before descent. Choose a longer or more favourable runway, reduce landing weight where practical, wait for better conditions, or compare an approved alternative configuration. CONF FULL is normally the better configuration when stopping distance is limiting.
Can you use a simple landing-distance formula?
No universal formula can reliably replace A320 performance data because weight, speed, runway friction, wind, slope and braking interact rather than producing one fixed correction.
The underlying physics still explains why speed errors are costly: kinetic energy rises with the square of groundspeed. A tailwind, excess VAPP or fast threshold crossing therefore adds more stopping work than its small indicated-speed difference suggests. Apply only the correction tables supplied with the exact performance source; do not stack invented percentages onto an integrated calculator result.
What changes A320 landing distance the most?
Touchdown groundspeed, touchdown point and runway condition usually create the largest difference between the calculated figure and the rollout seen in the simulator.
| Factor | Effect | Practical response |
|---|---|---|
| Excess approach speed | Raises the energy that the brakes, drag and reverse thrust must remove. | Cross the threshold at the calculated speed rather than planning for braking to recover a fast approach. |
| Tailwind | Raises groundspeed at a given indicated airspeed. | Enter the along-runway component and treat even a modest tailwind seriously on a short runway. |
| Long touchdown | Consumes usable runway before wheel braking can contribute. | Any excess touchdown distance is lost approximately metre for metre. Reverse thrust cannot recover it. |
| Wet or contaminated surface | Reduces wheel-braking effectiveness and may alter the permitted assumptions. | Use the exact condition offered by the tool; do not reuse a dry-runway result. |
| Landing weight | Increases kinetic energy and brake-energy demand. | Recalculate after holding, diversion changes or any large fuel difference from the flight plan. |
| CONF 3 instead of FULL | Normally increases VAPP and required runway. | Calculate both configurations rather than assuming the difference is negligible. |
| Downhill slope and high density altitude | A downhill runway resists deceleration, while hot and high conditions increase true airspeed for a given indicated speed. | Enter slope, temperature and pressure data exactly as requested. |
| Spoilers, brakes and reverse | Ground spoilers dump lift and improve wheel loading; braking and reverse then provide deceleration. | Arm and verify the planned systems. Never assume reverse will rescue missing spoilers or a long float. |
How much landing-distance margin should you add?
Use the conservative required distance supplied by the performance method, and do not add or remove arbitrary percentages without knowing what that output already includes.
If the EFB supplies both actual and required figures, the required figure normally contains the applicable margin. Adding another factor may double-count it. If it supplies only a bare stopping distance, use the source’s prescribed factor; when no factor is documented, do not treat a marginal runway as acceptable.
Simulator friction and braking behaviour vary between add-ons, so we recommend leaving obvious runway spare rather than planning to consume the entire LDA. A stronger autobrake setting may improve the result, but relying on maximum manual braking or uncredited reverse thrust is not a sound substitute for margin.
What if the A320 add-on has no performance calculator?
Without aircraft-specific data, you can build a conservative empirical baseline for that add-on, but it is only a simulator reference and not real-aircraft performance data.
- Choose controlled conditions. Use a long, dry runway with negligible slope, nil wind and repeatable weather.
- Fix every variable. Set one landing weight, configuration, VAPP and braking technique.
- Fly a stable threshold crossing. Use the same crossing height, speed and touchdown aim point on every run.
- Measure the correct distance. Record threshold crossing to full stop. If you can measure only touchdown-to-stop ground roll, separately include the airborne distance before comparing the result with LDA.
- Repeat valid runs. Discard unstable approaches and keep the longest representative result rather than the shortest.
- Build separate baselines. Repeat for the weights and configurations you use, then add a conservative buffer.
Do not extrapolate a dry-runway test to standing water, snow or ice. Simulator surface-friction models are not consistent enough for a homemade contamination correction to be dependable.
Why does the calculated distance not match the simulator rollout?
A mismatch usually means the tool’s assumptions did not match the aircraft, weather or touchdown that was actually flown.
- Wrong output definition: ground roll was compared with LDA, or an unfactored result was mistaken for required distance.
- Incorrect units or signs: pounds were entered as kilograms, feet as metres, or a tailwind and runway slope were entered with the wrong sign.
- Different weather: the simulator’s injected wind or runway state did not match the planning data.
- Speed correction entered twice: VAPP already included a wind additive, then the same additive was applied again with selected speed.
- Long flare: the aircraft crossed the threshold correctly but floated beyond the touchdown point assumed by the calculation.
- Deceleration mismatch: spoilers failed to deploy, the autobrake selection changed, manual braking was delayed, or the performance tool assumed different reverse-thrust credit.
- Different aircraft model: data from another A320 variant or add-on were used because the name looked close enough.
Our broader guide to A320 approach configuration, touchdown and deceleration in Microsoft Flight Simulator explains how the flying technique affects the runway actually used.
When should you recalculate or go around?
Recalculate whenever the runway, wind, runway condition, landing weight, flap configuration or braking assumption changes materially.
The calculation also stops being valid if the approach is fast, high, unstable or unlikely to touch down in the intended touchdown zone. Do not force the landing because the original numbers showed spare runway; use the correct A320 go-around procedure for a simulator approach and reassess the landing plan.