FlyByWire A32NX RNP approach support explained: what works in MSFS, vertical-guidance limits, RNP AR caveats and essential setup checks.
Partly. In Microsoft Flight Simulator, the FlyByWire A32NX can load and laterally fly many RNAV (GNSS)/RNP approaches when the navigation data and leg coding are compatible. That is not blanket support for every RNP operation: vertical guidance, LPV capability, curved legs and RNP AR procedures must each be verified rather than assumed.
What RNP support does the A32NX provide?
For an ordinary RNP APCH procedure, the dependable capability is database loading and managed lateral guidance; vertical coupling depends on the approach type and the avionics implemented in your installed A32NX build.
Charts may label these procedures RNAV (GNSS), RNP or RNP APCH. The minima line matters more than the title because LNAV, LNAV/VNAV and LPV each demand different guidance. Our guide to RNP approach types and flying techniques explains those distinctions in detail.
| Procedure or minima | What to expect in the A32NX | Practical decision |
|---|---|---|
| RNP APCH with LNAV minima | Database route and managed lateral tracking are normally usable if every leg is drawn correctly. | Follow the charted altitudes and use selected FPA when no coupled vertical mode is available. |
| LNAV/VNAV minima | These require valid barometric vertical guidance, not merely a magenta descent profile. | Use these minima only when the appropriate final approach mode arms and captures, with the FMA confirming it. |
| LPV minima | LPV requires suitable SBAS/SLS-style approach guidance. Loading the procedure does not prove that guidance exists. | Do not use LPV minima unless the installed build presents and correctly captures the required guidance. |
| RNP AR | This can involve low RNP values, radius-to-fix turns and specialised missed-approach coding. | Do not assume full RNP AR capability just because the flight plan draws a continuous line. |
How do I fly an RNP approach in the FlyByWire A32NX?
Load the procedure through the MCDU, compare it with the chart, and decide before descent whether you have lateral-only guidance or a valid coupled vertical mode.
- Select the approach and transition. Choose the runway procedure and the correct initial approach fix in the MCDU. An incorrect transition can produce loops, sharp intercepts or an apparent discontinuity.
- Inspect every leg. Step through the flight plan and compare fixes, altitude constraints and turn direction with the chart. Never remove a discontinuity blindly; it may represent radar vectors or a deliberate break in the published procedure.
- Check navigation accuracy. Confirm
GPS PRIMARYand review the required and estimated navigation accuracy where displayed. AGPS PRIMARY LOSTmessage or inadequate accuracy means the expected RNP performance is not available. - Prepare the approach data. Enter the applicable weather, pressure and minima on the approach performance page. Activating the MCDU approach phase manages approach speeds; it does not itself arm RNP lateral or vertical guidance.
- Monitor the FMA. Use NAV for the lateral path. If supported final approach guidance arms and captures, verify the announced modes on the Flight Mode Annunciator. The FMA—not the magenta line—is the authoritative indication of what the autopilot is doing.
- Use FPA when vertical coupling is unavailable. Respect each published altitude, calculate the descent point and select the charted flight-path angle. FPA is generally more suitable than V/S for a constant-angle non-precision approach.
- Apply the correct minima. Continue visually or go around at the applicable DA or MDA. An RNP approach does not automatically provide autoland capability.
Why will the A32NX follow the RNP route but not descend?
The usual cause is that managed descent and final approach vertical guidance are being treated as the same function when they are not.
DES mode can manage the arrival profile towards the approach, but it does not guarantee a coupled glidepath for every RNAV or RNP procedure. Our explanation of A32NX VNAV and managed-descent limitations covers that distinction.
- No vertical mode appears: fly the published vertical profile with selected FPA and use minima appropriate to the guidance actually available.
- The aircraft remains level: check that an altitude constraint or selected FCU altitude is not preventing descent.
- The approach will not capture: confirm the aircraft is correctly positioned, at the required altitude and established on a sensible intercept.
- The path has gaps or strange turns: recheck the selected transition and navigation data. Do not rely on an incorrectly coded procedure.
- APPR phase is active but nothing captures: remember that MCDU approach-phase activation controls speed scheduling; it is separate from pressing the FCU APPR pushbutton and from capturing an approach mode.
The flyPad option for calculated ILS signals does not create RNP or LPV guidance. Our explanation of what calculated ILS signals actually do shows why that setting cannot turn an RNAV procedure into an ILS.
Can the A32NX fly RNP AR approaches?
Treat RNP AR as unsupported unless your exact A32NX build, navigation data and procedure have documented support for every required leg and guidance function.
RNP AR is not simply a tighter version of an ordinary RNAV approach. A procedure may rely on curved RF legs, demanding containment values and a precisely coded missed approach. A line that looks correct on the Navigation Display is not proof that the simulated aircraft can monitor and fly the complete procedure accurately.
For normal MSFS operations, choose a conventional RNP APCH with LNAV minima when only lateral guidance is assured. Choose LNAV/VNAV or LPV minima only when the corresponding vertical guidance is genuinely available and confirmed on the FMA.