Hi guys, trying to fly the RNP-AR 13L into JFK using the Ini A350 in MSFS24 (everything up to date). It looks like the RNP-AR chart is missing from the OIS and the MSFS24 flight planner. From the FMS I can select the RNAV (RNP) 13L, which corresponds to the LIDO chart for the RNP-AR approach. That said, even then, the vertical profile is a bit of a rollercoaster. The incorrect FMA (LOC/GS) has been raised separately with Inibuilds.
Correct chart attached is from my own LIDO application.
Hi,
I assume your LIDO chart is an airline-specific one (tailored) because I don’t find these charts in the FAA chart database, nor in MSFS2024 (which also uses the LIDO charts).
Cheers
Richard
Hi Richard,
This appears to have been the case for a while. Here’s a Reddit thread from a year ago, showing the same thing:
The approach was pioneered by Jetblue, presumably for their crew’s safety margins and operational efficiencies in marginal weather, but is now a common procedure, for which many airlines are approved.
My observation was that what’s actually coded in the FMS is the RNP-AR procedure. Those waypoints don’t match the RNAV-Z, the VOR (GPS), or any other approach. It’s the RNP-AR coding, just without the chart. And the slightly odd vertical coding which makes it impossible to fly.
Hi,
I can only compare it with the FAA, and you don´t have a specific chart for this AR approach here, so it is not published officially for all airlines.
You don´t find the RNP 13L AR in the default Lido charts in MSFS2024 too, what is also a indication, that this chart is airlines specific:
So, it still seems like a tailored chart for AR-certified airlines/crews.
The second question about the vertical path:
I have also checked the coding directly in the A350 database, and I assume it is more of an A350 issue than a navdata issue. Here is what we offer in their database:
When I compare the legs page from your screenshot with what we offer in the database, it’s slightly different. So it seems they calculate the path themselves and/or exclude the altitude constraints. Please report this to Inibuilds so that they can re-check their internal coding.
Thank you,
Richard
