How do you handle an overweight A320 landing in a sim?
An Airbus A320 overweight landing occurs when the aircraft touches down above the maximum landing weight published for that exact variant. In a flight simulator, treat it as an abnormal, performance-limited landing: confirm the weight, follow the applicable procedure, calculate runway performance, fly a stable approach, and account for post-landing checks.
For our Aviation & Real-World Flying readers, the key distinction is that maximum landing weight, or MLW, is a certified structural limit rather than the weight at which the aircraft suddenly becomes uncontrollable. Landing above it increases approach speed, stopping distance, brake energy and structural loads.
What makes an Airbus A320 overweight for landing?
The A320 is overweight when its actual gross weight at touchdown exceeds the MLW for that aircraft variant and certified weight option. MLW is not the same as maximum take-off weight or maximum zero fuel weight.
A useful approximation is landing weight equals zero fuel weight plus the fuel remaining at touchdown. Check both the predicted destination weight and the actual gross weight; a loading-tool synchronisation error, incorrect zero fuel weight or pounds-versus-kilograms mix-up can create a false result. Fenix users can follow our explanation of checking predicted landing weight and VAPP.
Do not copy a generic MLW from another A320. The A320ceo, A320neo and individual certified weight options can have different limits, while simplified aircraft may not model those limits faithfully.
Should you burn fuel before an overweight landing?
Burn fuel only when delaying the landing is operationally safe and will produce a worthwhile reduction in weight. The A320 family has no normal fuel-jettison capability, so airborne weight reduction generally means holding or taking a longer route.
| Situation | Sensible simulator decision | Reason |
|---|---|---|
| No urgent fault, adequate fuel and suitable weather | Consider holding or diverting to reach MLW | A lighter landing reduces speed, distance and brake energy |
| Smoke, fire, serious failure or other immediate emergency | Land at the nearest suitable runway | Removing the immediate hazard takes priority over MLW |
| Weather deteriorating or fuel reserves becoming limiting | Do not keep holding solely to reach MLW | The delay can create a more serious problem than the overweight landing |
An overweight landing is therefore a risk decision, not an automatic instruction to hold. In real operations the commander, dispatch and maintenance organisation use approved operator procedures; a home simulator should reproduce that logic rather than inventing a fuel-burn target.
How should you fly an overweight A320 landing?
In a simulator, prepare the landing using the actual weight and the limitations supplied with that specific A320 model.
- Confirm the excess. Compare actual and predicted landing weight with the correct MLW. Check that the aircraft, MCDU and loading application agree on zero fuel weight, fuel and units.
- Choose the safest runway. Favour adequate length, favourable wind and the best available surface condition. Calculate with the expected touchdown weight, runway slope, elevation, wind, contamination and braking assumptions; our guide to calculating A320 landing distance from the conditions covers that performance work.
- Use the approved configuration. Follow any overweight-landing procedure supplied by the add-on or simulated operator. Do not assume one flap setting, autobrake selection or autoland limit applies to every A320 variant.
- Set a valid approach speed. Accurate weight, wind and approach data are essential for a valid VAPP. Higher weight already raises VLS, so manually reducing speed to shorten the landing is unsafe. If a performance tool refuses to calculate above MLW, do not extrapolate its figures and call them approved.
- Configure early. Extra speed means extra energy. Extend gear and flap early enough to become stable without rushing configuration near the runway, while respecting flap and gear speed limits.
- Touch down in the normal zone. Fly a normal, controlled flare and avoid floating in pursuit of a very soft touchdown. Confirm spoilers deploy, use the planned braking and reverse thrust, and keep directional control.
- Go around if necessary. Excess weight is never a reason to continue an unstable, fast or long approach. Use the proper A320 go-around sequence and reassess the runway, weather and aircraft state.
Do not assume an autoland is permitted simply because the simulated autopilot remains engaged. Automatic-landing weight limits and the depth with which they are modelled vary, so check the documentation for the aircraft being flown.
Does an overweight landing always damage the A320?
An overweight landing does not automatically damage the A320, but it places the aircraft outside its normal certified landing limit and requires maintenance assessment in real operations. The required inspection depends on the landing weight, recorded loads, touchdown severity and approved maintenance instructions.
A hard landing and an overweight landing are separate events. An aircraft can land hard below MLW, while an overweight aircraft can touch down smoothly yet still require the event to be recorded and assessed. There is no universal vertical-speed number that proves an A320 is undamaged.
After landing in a detailed simulator, check brake temperatures, allow cooling when necessary and review any maintenance or failure messages provided by the add-on. Simplified aircraft may accept the landing without consequence; that reflects limited simulation depth, not proof that the procedure was safe.
Common overweight-landing mistakes
- Comparing landing weight with MTOW instead of MLW.
- Using the MLW from a different A320 variant or weight option.
- Lowering VAPP manually to compensate for limited runway length.
- Holding to burn fuel despite an urgent fault, poor weather or threatened reserves.
- Trusting a green simulator calculation that does not support above-limit weights.
- Floating beyond the touchdown zone while trying to produce a soft landing.
- Continuing an unstable approach because a go-around will also be heavy.