|
Does Avidyne have any plans to align their IFD/FMS Arinc 424 data coding to Jepp chart naming?
I have queried Jeppesen about the difference in naming between their charts and IAPs in the IFD navdata (RNP on the chart vs RNAV in navdata). Europe has pretty much completed migration to the PBN RNP naming standard, and Jeppesen charts reflect this. However, these approaches are still all called RNAV in the IFD navdata.
Here is their reply: All displays of data are controlled by the FMS manufacturers. Until they are able to 'read' and display an RNP title procedure which would be coded with an Hxx instead of an Rxx, we will have to maintain Rxx coding. Rxx and Hxx are the coded procedures types. Currently we can use - based on FMS capabilities - Rxx only.
Arinc 424 NDB says: ---------------------------------- Route Type R indicates a procedue titled RNAV, e.g., RNAV (GPS) or RNAV (RNP). Route Type H indicates a procedure titled RNP. The Route Types H and R are coded to differentiate between the approach procedure titles published in state source. The words in brackets will not be considered for the coding of the Route Type. While according to the PBN manual there is no RNAV approach specification, many approaches are still published using an RNAV title. Additionally, there are still non PBN RNAV approaches published, e.g., VOR/DME RNAV. The following old titles will be coded with a Route Type R: RNAV (GPS) RWY 09 RNAV (GNSS) RWY 09 RNAV (RNP) RWY 09 The following new titles will be coded with Route Type H: RNP RWY 09 RNP RWY 09 (AR) ----------------------------
Just to be clear, this is not a big deal at the moment. But given Avidyne's delay implementing RF legs, it does make one wonder if international requirements are given much priority and being implemented in a timely way.
-------------
Vince
|