Hi, I want to start this topic to discuss the issues of the currently being used format and what has to be implemented on the new NG2.0Some things that are very important: - Full support of ARINC-424, especially RF-Legs (Radius to FIX), AF-Legs (ARC to FIX), CF-Legs (Course to FIX) - Enhanced RNAV / RNP Capabilties: The FMC should be able to support RNP Procedures (Approach, SID/STAR, ENROUTE (Curved RNP-Airways) - Coding of a vertical VNAV Path e.g. -3.00

Hi, I want to start this topic to discuss the issues of the currently being used format and what has to be implemented on the new NG2.0Some things that are very important: - Full support of ARINC-424, especially RF-Legs (Radius to FIX), AF-Legs (ARC to FIX), CF-Legs (Course to FIX) - Enhanced RNAV / RNP Capabilties: The FMC should be able to support RNP Procedures (Approach, SID/STAR, ENROUTE (Curved RNP-Airways) - Coding of a vertical VNAV Path e.g. -3.00

Your link starts with..."This document is an unpublished work. Copyright 2009 Honeywell International Inc. All rights reservedThis document and all information and expression contained herein are the property of Honeywell International Inc., and is provided tothe recipient in confidence on a

I hope as well for an full ARINC424 Support!!More complex (other than DCT-to-DCT) RNAV-Procedures are at this stage totally unable to fly with PMDG-Products.The EAG (Navigraph) can supply a worldwide coverage of ARINC424 coded procedures.I hope PMDG will implement the whole set, and not just only TF-Legs or such simple things.

Just wanted to ask if there are any news on this topic especially regarding RF-Legs. As I am working for a Navigation Data Provider in real life, we see an huge increase of Procedures that are coded with RF-Legs.For those who don't kown what a RF-Leg is:An RF-Leg connects two Navigation Database fixes with a specific radius that is based on a center fix. This is very similar to an DME ARC around a VOR. Jan-Paul