How do I calculate A320 landing distance in a simulator?
Calculate A320 landing distance in a simulator using LDA, landing weight, wind, runway condition and the correct add-on performance tool.
Calculate A320 landing distance with the aircraft-specific EFB or performance calculator for your exact add-on. Enter predicted landing weight, runway LDA, wind, temperature, pressure, slope, surface condition, flap configuration and braking assumptions. Compare the tool’s required landing distance—not ground roll—with LDA, retaining a clear operational margin.
This is simulator guidance within our Aviation & Real-World Flying coverage. It applies to A320 add-ons in Microsoft Flight Simulator 2020 and 2024, X-Plane, Prepar3D and FSX, but their figures are not interchangeable. Never replace approved aircraft, airport and operator data for a real flight with results from a consumer simulator.
What is a typical Airbus A320 landing distance?
About 1,500–2,000 metres (4,900–6,600 feet) of LDA is a useful broad simulator-planning expectation for many dry A320 landings near sea level, but it is not a reusable performance figure.
A light aircraft in calm conditions may need less. A high landing weight, tailwind, wet surface, downhill slope or elevated airport can push the requirement beyond that range. The A320ceo, A320neo, engine variants and different add-on flight models can also produce different answers.
Do not confuse runway required with the distance observed after touchdown. Published and calculated landing distances commonly include an airborne segment from a defined threshold-crossing height, while ground roll begins only when the wheels touch.
Which landing-distance figure should you compare with LDA?
Compare the calculator’s documented required or factored landing distance with the landing distance available for the chosen runway direction.
| Figure | Meaning | Correct use |
|---|---|---|
| LDA | Landing distance available from the landing threshold. It excludes clearways, stopways and pavement before a displaced threshold. | Use this as the available distance, not total runway length or TORA. |
| Actual or unfactored distance | The modelled distance under the method’s stated assumptions, often from a defined screen height to a full stop. | Do not treat it as an operational runway requirement unless the documentation explicitly permits that comparison. |
| Required or factored distance | A distance to which the method’s prescribed margin or factor has been applied. | Use it for the LDA comparison when all inputs and assumptions match the intended landing. |
| Ground roll | Distance from touchdown to a full stop. | Do not compare it directly with LDA because it omits the airborne distance before touchdown. |
Labels vary between add-ons. If an EFB shows both actual and required values, read its documentation before choosing one. An MCDU approach page may calculate or display VAPP without calculating runway required.
How do I use an A320 landing performance calculator?
Use one calculator built for the exact aircraft model, then make its aircraft, runway and deceleration assumptions match the landing you intend to fly.
- Select the correct aircraft data. Confirm the A320 variant, engine option and add-on. Do not transfer a result between a ceo and neo, or between two developers’ aircraft, simply because both are labelled A320.
- Find the directional LDA. Select the actual landing runway and account for displaced thresholds. Keep metres and feet consistent throughout the calculation.
- Enter predicted landing weight. Use zero-fuel weight plus the fuel expected to remain at touchdown, not take-off weight. Check maximum landing weight separately; enough runway does not make an overweight landing structurally acceptable. Fenix users can follow our explanation of obtaining predicted landing weight and VAPP from the aircraft.
- Enter the arrival weather. Supply wind, temperature and QNH, airport elevation or pressure altitude exactly as requested. If the calculator wants a headwind or tailwind component, do not enter the full reported wind when it crosses the runway.
- Set the runway condition. Choose dry, wet or the offered contaminant or runway condition code. A runway that looks wet in the simulator may not use the same friction assumption as the calculator.
- Match the landing configuration. Select CONF FULL or CONF 3 and enter VAPP only if requested. CONF 3 normally produces a higher approach speed and a longer result. Our guide to how weight, flap and wind affect A320 landing speed explains why VAPP is not one fixed number.
- Match the stopping assumptions. Select the intended braking method, spoiler availability and reverse-thrust setting. Some calculations assume maximum wheel braking or give no credit for reverse, regardless of the autobrake selected in the cockpit.
- Include simulated failures. Apply any available penalty for an inoperative reverser, spoiler fault, braking limitation or other relevant abnormal condition.
- Read the output definition. Use required or factored distance when the tool identifies it as the LDA-comparison figure. Do not silently substitute ground roll or an unfactored result.
- Calculate the spare distance. Use
runway margin = LDA − required landing distance. A negative result means the runway is unsuitable under the entered assumptions; a very small positive result leaves little tolerance for modelling or flying differences.
What changes A320 landing distance most?
Groundspeed, touchdown point and runway condition usually create the largest differences between the calculated distance and the rollout seen in a simulator.
| Factor | Effect on the landing | Practical response |
|---|---|---|
| Excess VAPP or threshold speed | Increases the energy that brakes, drag and reverse must remove. Kinetic energy rises approximately with the square of speed. | Use the calculated VAPP and do not add a second gust correction manually. |
| Tailwind | Raises groundspeed for the same indicated airspeed. | Enter the along-runway component and recalculate after a runway or wind change. |
| Long flare or late touchdown | Consumes runway before effective wheel braking begins. | Any extra touchdown distance is lost almost metre for metre; reverse thrust cannot recover it. |
| Wet or contaminated runway | Reduces wheel-braking effectiveness and changes the valid performance method. | Never reuse a dry-runway result for rain, standing water, snow or ice. |
| Higher landing weight | Increases kinetic energy and brake-energy demand. | Recalculate after extended holding, diversion changes or a large difference from planned landing fuel. |
| CONF 3 rather than FULL | Normally means a higher VAPP and more runway required. | Calculate both configurations when distance is limiting instead of assuming the difference is small. |
| Downhill slope or high elevation | A downhill runway resists deceleration; elevation and temperature raise true airspeed for a given indicated speed. | Enter slope, elevation, pressure and temperature using the calculator’s stated units and sign convention. |
| Spoiler, brake or reverse mismatch | Changes wheel loading and deceleration from the calculated assumptions. | Arm the spoilers, select the planned braking mode and verify that throttle or brake hardware is calibrated correctly. |
Can an A320 land at Gibraltar?
An A320 can use Gibraltar in suitable conditions, but its roughly 1,777-metre overall runway length must not be mistaken for the LDA available in each direction.
Use the declared LDA corresponding to the threshold represented by your scenery and navigation data. Displaced thresholds can make it shorter than the physical runway, and simulator airport data may not reproduce every real-world change consistently.
Gibraltar leaves less room for a fast approach, tailwind or long float than a typical long commercial runway. Wind and turbulence can also make touchdown accuracy harder even when the calculated distance fits. Treat the terrain and approach geometry as handling concerns alongside, not replacements for, the landing-distance calculation.
How much landing-distance margin should you retain?
Use the calculator’s required or factored result when its definition is clear, then retain visible spare runway rather than planning to stop at the exact end of the LDA.
Do not add an arbitrary percentage when the output already includes a prescribed factor, as that can double-count the margin. Conversely, if the tool supplies only a bare actual distance and documents no factor, the result does not establish an operational runway requirement.
A positive margin of only a few metres proves the subtraction, not the landing. Simulator tyre friction, spoiler logic, brake modelling and reverse effectiveness vary by add-on, while a slightly fast or long touchdown can consume the apparent spare distance. Choose a longer runway, a more favourable wind direction, lower landing weight or an approved alternative configuration when the result is marginal.
Why does the calculated distance not match the simulator rollout?
A mismatch usually means that the calculator’s definitions or assumptions differ from the conditions and technique actually flown.
- Wrong figure: ground roll was compared with LDA, or an actual distance was mistaken for a factored requirement.
- Wrong units: pounds were entered as kilograms, feet as metres, or temperature and pressure formats were misread.
- Reversed signs: a tailwind was entered as a headwind or the calculator’s uphill and downhill slope convention was misunderstood.
- Weather mismatch: live or injected simulator weather differed from the values used during planning.
- Duplicate wind additive: VAPP already included the wind correction and the same additive was applied again through selected speed.
- Long touchdown: the threshold crossing was correct, but the flare carried the aircraft beyond the touchdown point assumed by the calculation.
- Different deceleration: spoilers did not deploy, braking began late, the autobrake selection changed or the calculator assumed different reverse credit.
- Control-binding interference: brake assistance, a noisy brake axis or poor throttle calibration applied unintended braking or prevented idle and reverse operation.
- Different aircraft model: the figures came from another A320 variant or add-on with different aerodynamic and ground-friction modelling.
The calculation assumes a stable approach and normal touchdown. Our practical guide to configuring, flaring and stopping the A320 in Microsoft Flight Simulator covers the flying technique that determines how much runway is actually consumed.
What if the A320 add-on has no performance calculator?
Without aircraft-specific performance data, you can create a conservative empirical baseline for that add-on, but it remains a simulator reference rather than real-aircraft data.
- Choose controlled conditions. Use a long, dry, level runway with negligible wind and repeatable weather.
- Fix the variables. Keep landing weight, configuration, VAPP, threshold-crossing height, touchdown aim point and braking technique unchanged.
- Fly several stable approaches. Discard fast, high or long landings rather than allowing poor technique to distort the baseline.
- Measure threshold to full stop. If the simulator records only touchdown-to-stop ground roll, do not compare that value directly with LDA.
- Keep the longest representative result. The shortest rollout is not a sensible planning baseline. Add conservative spare distance for normal variation.
- Repeat for other weights and configurations. Do not extrapolate a dry result to wet, snow-covered or icy surfaces with an invented correction.
When should you recalculate or go around?
Recalculate after any material change to runway, wind, surface condition, landing weight, flap configuration, braking assumption or aircraft system status.
The original result also stops being dependable when the aircraft is fast, high, unstable or unlikely to touch down in the intended zone. Do not force the landing because the pre-descent figures showed spare runway; fly the appropriate A320 go-around sequence in the simulator, stabilise the situation and calculate again.