Find the correct Airbus A319 landing speed, typical VAPP range, MCDU method, wind correction, flap effects and common simulator mistakes.
For an Airbus A319, use the calculated VAPP shown on the MCDU PERF APPR page, not a fixed landing speed. For many normal landings it is roughly 125–140 KIAS, with 130–135 common, but weight, flap setting, wind and failures change it. Fly VAPP on final; touchdown speed becomes lower through the flare.
In our Aviation & Real-World Flying context, “landing speed” normally means the indicated approach speed flown on final and across the threshold. It does not mean groundspeed, and the aircraft does not have a separate speed that must be held all the way to wheel contact.
What is a typical Airbus A319 approach speed?
A normally loaded A319 in landing configuration will often have a VAPP in the 125–140 KIAS region. A light aircraft in calm conditions may be near the lower end, while increased landing weight, CONF 3, wind correction or an abnormal configuration can push it higher.
| Speed | Meaning | How to use it |
|---|---|---|
| VLS | Lowest selectable speed calculated for the aircraft’s weight and configuration | Do not treat it as the normal final-approach target |
| VAPP | Approach speed incorporating the applicable correction above VLS | Use this as the normal final-approach target |
| Managed target | The live speed target displayed on the PFD | It may rise above entered VAPP because of the Airbus ground-speed-mini function |
| Groundspeed | Speed over the ground after wind is considered | Do not use it as the pitch-and-thrust target |
The A319 uses the same broad approach-speed principles as the rest of the A320 family. Our explanation of how weight, wind and flap configuration alter Airbus approach speed covers that shared logic in more detail.
How do I find the correct A319 VAPP?
Use landing weight, the intended flap configuration and the destination weather to obtain VAPP from the aircraft’s approved data or correctly modelled FMGS.
- Determine landing weight. Use the predicted gross weight at destination, or calculate zero-fuel weight plus expected landing fuel. Do not use take-off weight.
- Choose the landing configuration. CONF FULL is the normal choice; use CONF 3 only when operational planning, runway performance and the applicable procedure support it.
- Complete PERF APPR. Enter the destination QNH, temperature, runway wind and minima. Select the planned landing configuration where the aircraft or add-on provides that option.
- Read and cross-check VAPP. Confirm that the result is plausible for the weight and configuration. An unexpectedly low or high value usually points to incorrect weight, wind or flap data.
- Fly the indicated target. With managed speed and autothrust operating normally, follow the PFD target. Otherwise use the selected speed required by the aircraft procedure or simulation model.
For the underlying relationship between weight, configuration and reference speed, see the wider method for calculating an aircraft’s correct landing speed. Landing-distance assessment remains a separate task: the right VAPP does not by itself prove that a wet, contaminated, short or tailwind runway is suitable.
How should wind affect A319 landing speed?
Wind changes the correction applied to VLS and has an even larger effect on groundspeed and runway distance. Airbus procedures commonly base the approach correction partly on the headwind component, with limits and minimum corrections defined by the applicable operational data.
- Headwind: usually reduces groundspeed for a given KIAS, although the calculated or managed target may include a wind additive.
- Tailwind: increases groundspeed and landing distance. Do not subtract an improvised amount from VAPP.
- Crosswind: does not justify adding the entire crosswind component to the approach speed.
- Gusts: enter the reported runway wind correctly and use the calculated correction. Avoid stacking a large manual gust additive on top of one already produced by the FMGS.
Why does managed speed sometimes rise above VAPP?
The Airbus ground-speed-mini function can command a speed above the entered VAPP when the sensed headwind is stronger than the wind entered for approach. This protects the aircraft’s energy if that extra headwind disappears near the ground. Add-on fidelity varies, so basic simulator aircraft may hold a static target instead.
Should I land the A319 in CONF FULL or CONF 3?
Use CONF FULL for a normal landing unless the operating procedure or performance calculation calls for CONF 3. CONF 3 normally gives a higher VLS and VAPP, less drag and more landing-distance requirement, so changing configuration means recalculating the target rather than retaining the old speed.
Abnormal flap or slat configurations require their own procedure and may produce a substantially higher approach speed. The ordinary 125–140-knot range is not suitable for those cases.
Which A319 landing-speed mistakes cause trouble?
The most common error is choosing a familiar number such as 130 knots before checking weight and configuration.
- Using groundspeed: fly KIAS from the PFD, not the GPS groundspeed figure.
- Confusing VLS with VAPP: VLS is a lower limit, while VAPP is the normal target.
- Carrying unnecessary extra speed: even several surplus knots can lengthen the flare and consume valuable runway.
- Using take-off weight: approach speed must reflect predicted landing weight after fuel burn.
- Ignoring configuration changes: selecting CONF 3 or responding to a flap fault requires a new speed.
- Forcing the target back to static VAPP: a higher managed target may be the expected ground-speed-mini response rather than an error.
- Using normal figures when overweight: review how excess Airbus landing weight changes speed and runway performance instead of guessing an additive.
What if the simulator does not calculate VAPP?
If the simulated A319 cannot calculate VAPP reliably, use the speed table or performance method supplied with that specific aircraft model. Do not assume every A319 add-on models the same weight, FMGS logic or aerodynamic data.
A structured A319/A320/A321 descent and landing flow can help prevent missed approach entries and configuration steps in older simulators. For an actual aircraft operation, only approved performance data, the applicable flight manuals and company procedures should determine the landing speed; the typical range given here is not operational performance data.