Hi, SBRJ RNP F 20L shows the 3 degree approach starting 3.6nm before RJ941 but shows the 3 degree approach hitting ground at the MAP wpt RJ941, see pic:
whereas it should be at the runway threshold as shown correctly in RNP E as follows:-
I also noted in the Navdata for RNP F (I use prosim 737), 700 ft is inserted as an altitude restriction at RJ941, but this is in fact the MDA (and not part of the 3 degree approach) and you would normally pass below this altitude if you reached 700 ft before RJ941 with runway visual at that point.
Further info on this, attached is the local DECEA chart for the same approach RNP F 20L, you can see firstly that the 3 degree glide path starts from RJ107 and not a little afterwards as per Navigraph, and the glide path is clearly shown going down to MDA 700ft at RJ941, also different from Navigraph which shows a glide path going down to the ground at RJ941 sbrj_rnp-f-rwy-20l_iac_20211230.pdf (668.1 KB)
We shall investigate. Navigraph cannot change the charts, but if we can confirm the issue, we can surely pass on the feedback to our data provider, Jeppesen!
Good news! We have received news that Jeppesen will update this chart in cycle 2412!
However, there are some things to keep in mind when it comes to the actual navigation data and therefore likely the chart updates. To directly quote Jeppesen:
This procedure is a bit tricky due to the fact that the procedure title indicates a runway to which the pilot would fly, as if it’s a straight-in; however only circling minima are provided.
Our aviation technical and regulatory standards team evaluated the procedure source and determined that we needed to code this as a point-in-space using source provided VNAV, and use MDA for the MAP altitude. This type of procedure design is very similar to a helicopter point-in-space procedure where the missed approach is really a point in space followed by maneuvering to the helipad (or in this case to the fixed wing runway 20L).
