PBN to XLS - · PDF fileARINC-424 • The requirements for each FMS may be different. The...
Transcript of PBN to XLS - · PDF fileARINC-424 • The requirements for each FMS may be different. The...
Agenda01 Involved Parties 03 An example – RNP 1 transition to GLS
approach
02 Coding of PBN Procedures 04 Problems & Solutions
The Involved Parties
January 31, 2017PBN to XLS - A Data House Perspective4
• The aircraft manufacturer, examples:
• Airbus
• Boeing
• Embraer
• Canadair
• Define the functional requirements of the FMS
• Define the avionics suite
• Define the user interaction
The Involved Parties
January 31, 2017PBN to XLS - A Data House Perspective5
• The avionics manufacturer, examples:
• Honeywell
• GE Aviation
• Thales
• Rockwell Collins
• Design the avionics suite
• Define the requirements of the FMS
• Build the Database packing tool
The Involved Parties
January 31, 2017PBN to XLS - A Data House Perspective6
• The data house, example:
• Lido
• Jeppesen
• NavBlue
• Code the data required by the avionics manufacturer
• The data is coded according the industry standard ARINC-424
• The requirements for each FMS may be different
The Involved Parties
January 31, 2017PBN to XLS - A Data House Perspective7
• The datahouses typically produce charts in addition to data
• Paper charts
• Electronic solutions
Coding of PBN Procedures
January 31, 2017PBN to XLS - A Data House Perspective9
• When PBN was introduced, it caused confusion.
• A new way of designing procedures
• Implementation of Navigation Specifications
Coding of PBN Procedures
January 31, 2017PBN to XLS - A Data House Perspective10
• No changes in ARINC 424 specification with ICAO PBN Manual implementation
• Except
• The PBN Navigation Specification was introduced in
ARINC 424-21
• Coding rules for
• LPV (SBAS based approaches)
• RNP AR (SAAAR at the time)
• GLS
• RF leg
• RNP values
where introduced before the ICAO PBN Manual was released.
Example – PBN transition to GLS Approach in Zurich
January 31, 2017PBN to XLS - A Data House Perspective12
Example – PBN transition to GLS Approach in Zurich
January 31, 2017PBN to XLS - A Data House Perspective13
• The segment between the IF and the FAP is
curved, coded with an RF leg
• The transition is coded to the FAP
Example – PBN transition to GLS Approach in Zurich
January 31, 2017PBN to XLS - A Data House Perspective14
• No vertical angle is published outside the FAP
• The segment between the IF and the FAP is “level”
• Same minimum altitude constraints apply at the IF
and the FAP
Example – PBN transition to GLS Approach in Zurich
January 31, 2017PBN to XLS - A Data House Perspective15
Problems & Solutions
January 31, 2017PBN to XLS - A Data House Perspective18
Short-term:
In the tailored data for the aircrafts performing the demo flights, it was possible to extend the transition to the FAP, violating the ARINC 424 requirement.
Only possible in tailoring, NOT for standard procedures!
Problems & Solutions
January 31, 2017PBN to XLS - A Data House Perspective19
Long-term:
Modify ARINC 424 rules, difficult as certified airborne software possibly needs changes, or
prohibit such procedure design, which might not be desired.
Problems & Solutions
January 31, 2017PBN to XLS - A Data House Perspective20
Long-term:
Modify ARINC 424 rules, difficult as certified airborne software possibly needs changes, or
prohibit such procedure design, which might not be desired.
Problems & Solutions
January 31, 2017PBN to XLS - A Data House Perspective21
• Transition from performance to geometric descend
path
• Typically occurs at the FAF
• Different aircraft FMS calculate the transition
differently
Backup
January 31, 2017PBN to XLS - A Data House Perspective23
Backup
Example with Skyguide original source
Example – PBN transition to GLS Approach in Zurich
January 31, 2017PBN to XLS - A Data House Perspective24
Example – PBN transition to GLS Approach in Zurich
January 31, 2017PBN to XLS - A Data House Perspective25
• The segment between the IF and the FAP is
curved, coded with an RF leg
• The transition is coded to the FAP