Vous êtes sur la page 1sur 30

Implementing RNP, Toulouse October 4 and 5 2005

Presented by:

Capt. Michel BRANDT


Deputy Vice President Flight
Operations Support & Services

Airbus RNP Operations


Contents

Î RNP Enroute and in Terminal Area

Î RNAV in approach

Î RNP SAAAR

ÎRNP<0.3 Certification

ÎOperational Evaluation/Approval
© AIRBUS 2005 S.A.S. All rights reserved. Confidential and proprietary document.

Î International Standardization

Î Conclusion

Airbus RNP Operations 2 Implementing RNP, October 4-5 2005


RNP RNAV Enroute and in Terminal Area
RNP Enroute

RNP 10 in oceanic and


Q-1
Q-7
remote area:
Q-3 • With time limitation in IRS ONLY for
Q- Q-9 aircraft without GPS
5
Q-11 • No time limitation with GPS
RNP 4 (2) in oceanic and
remote area:
• GPS required
Q-13 RNP Enroute continental:
© AIRBUS 2005 S.A.S. All rights reserved. Confidential and proprietary document.

• European B-RNAV (5 NM accuracy)


• US RNAV routes (Q-routes) 2 NM
accuracy
Source FAA

All Airbus with an FMS


can fly these routes
Airbus RNP Operations 4 Implementing RNP, October 4-5 2005
RNAV in Terminal Area

RNAV Instrument procedures


requiring P-RNAV Capability
(1 NM accuracy)
z Compliance with JAA TGL 10

US RNAV SIDs and STARS


• Type A (2 NM accuracy)
• Type B (1 NM accuracy)
• Compliance with
© AIRBUS 2005 S.A.S. All rights reserved. Confidential and proprietary document.

FAA AC 90 -100

zBoth TGL 10 and AC 90-100 have


Airworthiness and
Operational requirements

Airbus RNP Operations 5 Implementing RNP, October 4-5 2005


RNAV in Terminal Area

All Airbus with an FMS


comply with the airworthiness
requirements of TGL 10 and
AC 90-100
© AIRBUS 2005 S.A.S. All rights reserved. Confidential and proprietary document.

Airbus RNP Operations 6 Implementing RNP, October 4-5 2005


RNAV in Terminal Area

z The radio navaid infrastructure supports the required


Navigation Accuracy level
– It is not the Operator’s duty to verify the adequacy of radio navaid
coverage
– Inadequate radio navaid coverage should be notified by NOTAM or
on the instrument procedure chart ⇒ GPS required
 GPS acceptable if TSO C 129A certified
– All Airbus with GPS comply
© AIRBUS 2005 S.A.S. All rights reserved. Confidential and proprietary document.

 Single or Dual RNAV system


– Single system acceptable, unless flight path below area MSA
or/and (?) no radar coverage (TGL 10)
– Should be stated on the instrument procedure chart

Airbus RNP Operations 7 Implementing RNP, October 4-5 2005


RNAV in Terminal Area

z Operational Approval:
Aircraft capability
– Stated in the AFM Navigation Database
Crew documentation validation was the main
– OPS Manual based on FCOM challenge to deploy P-RNAV.
– MEL The main database providers
Crew training are now ED76/D0200A
– RNAV system knowledge compliant
© AIRBUS 2005 S.A.S. All rights reserved. Confidential and proprietary document.

– Briefing on RNP RNAV


Navigation database integrity
– Approved database suppliers
– Operator’s validation

Airbus RNP Operations 8 Implementing RNP, October 4-5 2005


RNAV in approach
RNAV in approach

z RNAV (GNSS) “Sensor related”


z RNP RNAV “Performance related”
– RNP 0.3,
– Straight final segment
z DA as low as 250 ft AGL
with FINAL APP mode
(LNAV/VNAV ) guidance
© AIRBUS 2005 S.A.S. All rights reserved. Confidential and proprietary document.

A large part of the Airbus world fleets can


fly instrument approach procedures
published under ICAO PANS OPS (or
TERPS) criteria.
A lot of destinations could benefit from the
implementation of such procedures.
Airbus RNP Operations 10 Implementing RNP, October 4-5 2005
The Advantages of RNAV Approaches

FACF FAF SDF [MAP]


[RW27]

IF CF
TF CF
TF

[MAP]
[RW27]

MDA
DA
© AIRBUS 2005 S.A.S. All rights reserved. Confidential and proprietary document.

-3°

• Approach on runway axis


• Final descent at a constant Flight Path Angle to a DA
• Stabilized approach leading 50 ft above runway threshold
• Accuracy of navigation
Airbus RNP Operations 11 Implementing RNP, October 4-5 2005
The Advantages of RNAV Approaches

FACF FAF [RW27]

IF TF TF

[RW27]
• All Airbus with an FMS and
GPS are capable to fly such
RNAV Approaches
-3°
Since mid-80’s, Airbus
promotes a constant slope
NPA rather than step-down
© AIRBUS 2005 S.A.S. All rights reserved. Confidential and proprietary document.

(“dive and drive”) procedures


This is in line with the CDFA
concept (NPA OPS-41)
• All Airbus with FMS 2 can
fly in addition RF legs

Airbus RNP Operations 12 Implementing RNP, October 4-5 2005


RNAV in Approach - Operational Approval

z GenericApproval for RNP 0.3 RNAV or RNAV(GNSS)


(PANS OPS)
 Crew Procedures
– FCOM SOP
Dispatch Requirements
 Crew Training
– Briefing on RNP RNAV
– Navigation system knowledge (known by all Airbus pilots)
– Use of RNAV navigation system (known by all Airbus pilots)
© AIRBUS 2005 S.A.S. All rights reserved. Confidential and proprietary document.

„ Training on FINAL APP mode


Documentation update
Navigation Database
Navigation Database Integrity validation by the Operators

must be clarified by EASA


AMC 20 XZ
Airbus RNP Operations 13 Implementing RNP, October 4-5 2005
RNAV in Approach

z It
is now time to take benefit of Airbus aircraft
RNAV capabilities in approach
z “PANS OPS” straight in RNP 0.3 RNAV or RNAV(GNSS)
approaches can easily be implemented:
Deletion of circling procedures
Deletion of “old style” NPAs
Access to new destinations
© AIRBUS 2005 S.A.S. All rights reserved. Confidential and proprietary document.

Airbus RNP Operations 14 Implementing RNP, October 4-5 2005


RNP SAAAR
RNP SAAAR - Background

z Onmany destinations, opportunities exist in Approach, and


Missed Approach
– For Lower RNP values
– For Curved Approaches / Missed Approaches
Opportunities provided to Operators satisfying SAAAR
(Special Aircrew and Aircraft Authorization Required)
RNP RNAV or Containment Based RNAV
procedures
© AIRBUS 2005 S.A.S. All rights reserved. Confidential and proprietary document.

– Links RNAV airspace design to Aircraft Performance

2 x RNP ROC based on VEB

Airbus RNP Operations 16 Implementing RNP, October 4-5 2005


RNP SAAAR - Background

z RNP SAAAR benefits:


Reduce minima
More efficient and Predictable Air Traffic Management:
– De-conflicting adjacent airports
– Better access to simultaneous parallel runway or converging
runway approaches
Optimize noise abatement procedures in sensitive areas
© AIRBUS 2005 S.A.S. All rights reserved. Confidential and proprietary document.

Airbus RNP Operations 17 Implementing RNP, October 4-5 2005


RNP<0.3 Single Aisle Certification

zTo anticipate Airbus customers’ needs:


Target RNP 0.1
A318, A319, A320 have been certified for RNP
as low as 0.15 with Honeywell FMS 2
Demonstrations are in progress for other
aircraft types and/or FMS vendors
© AIRBUS 2005 S.A.S. All rights reserved. Confidential and proprietary document.

Airbus RNP Operations 18 Implementing RNP, October 4-5 2005


RNP SAAAR constraints

z RNP SAAAR constraints:


Operational evaluation of each instrument procedure
Special flight crew training
Specific operational approval
National Authorities need to approve FAA SAAAR
criteria or develop their own criteria
© AIRBUS 2005 S.A.S. All rights reserved. Confidential and proprietary document.

Airbus RNP Operations 19 Implementing RNP, October 4-5 2005


RNP SAAAR Project

AIRBUS
RNAV-RNP< 0.3
Approach Procedure
Certification with
Designer
EASA/FAA

• Aircraft performance AIRLINE • Approach design


© AIRBUS 2005 S.A.S. All rights reserved. Confidential and proprietary document.

• Fly-ability checks Operational Approval • Approach charts


• Flight crew procedures with the support of • Nav. Database coding
• Crew training Airbus and the • Nav. Database integrity
• Documentation Procedure • Procedure maintenance
Designer

Airbus RNP Operations 20 Implementing RNP, October 4-5 2005


Navigation Database Validation

Procedure design Charts

Data Supplier ARINC 424 “master” file Operator validation


and crew check
Approved Suppliers

FMS Database Processing Packed Data


Approved Suppliers
© AIRBUS 2005 S.A.S. All rights reserved. Confidential and proprietary document.

FMS

Airbus RNP Operations 21 Implementing RNP, October 4-5 2005


RNP SAAAR - Airbus Deliverables

z RNP
0.3 SAAAR Capability and Operational
Compliance Document, or the Airworthiness
Compliance Document for RNP<0.3
Aims to be used by Operators to support operational
approval
Provides all relevant information for safe operation of RNP
SAAAR
Summarizes:
© AIRBUS 2005 S.A.S. All rights reserved. Confidential and proprietary document.

– Airworthiness Assessment
– Assumptions & Limitations that should be considered in the
operational evaluation
– Assumptions & Limitations that should be considered for the
instrument approach procedure design

Airbus RNP Operations 22 Implementing RNP, October 4-5 2005


International Standardisation
Current Situation and Perspectives
International standardisation - Current situation and perspectives

ƒ Instrument procedures design criteria:


¾ICAO RNP RNAV Procedure (PANS OPS) available for
RNP 0.3
- ICAO RNP SORSG meetings:
¾Objective : to standardize a new approach type for RNP < 0.3

ƒ Aircraft airworthiness and operational requirements:


¾EASA (European Aviation Safety Agency) aims at
© AIRBUS 2005 S.A.S. All rights reserved. Confidential and proprietary document.

standardisation across European countries and


harmonization with FAA
- AMC20-XZ in progress

AIRBUS intent is to be compliant with AMC 20 XZ

Airbus RNP Operations 24 Implementing RNP, October 4-5 2005


International standardisation - Current situation and perspectives

z Area where EASA-FAA harmonisation is urgently needed:


Understanding of the overall safety objectives
– ED75/DO236 Airworthiness Criteria
– Use of operational mitigation means to reach the required
objective
Clarification
on the line of demarcation between the
airworthiness approval and operational approval
Methods for the assessment of operational mitigation means
© AIRBUS 2005 S.A.S. All rights reserved. Confidential and proprietary document.

Demonstration methods for Flight Technical Error assessment


– How the engine failure needs to be taken into account in the
performance demonstration

Airbus RNP Operations 25 Implementing RNP, October 4-5 2005


Conclusions

9 A large part of the Airbus fleet has the capacity to benefit


from cost-effective RNAV(GNSS) or RNP RNAV approach
implementation

9 Airbus is already involved in RNP SAAAR projects with


several Airlines

9 Airbus will anticipate the future developments of RNP RNAV


Operations, and other approach and landing means, to
© AIRBUS 2005 S.A.S. All rights reserved. Confidential and proprietary document.

optimize the Airbus aircraft capabilities through R&T projects


such as Optimal (www.optimal.isdefe.es)

Airbus RNP Operations 26 Implementing RNP, October 4-5 2005


Conclusions

For authorities and airspace administrations:

9 Deploy in priority P-RNAV and RNAV(GNSS) or RNP 0.3


RNAV straight-in (PAN OPS)

9 RNP SAAAR (or equivalent) to be used only when an


operational benefit can be achieved

9 Develop ICAO standards similar to SAAAR, harmonized with


© AIRBUS 2005 S.A.S. All rights reserved. Confidential and proprietary document.

FAA “Public” SAAAR

9 Harmonize regulations between Europe and USA

Airbus RNP Operations 27 Implementing RNP, October 4-5 2005


© AIRBUS 2005 S.A.S. All rights reserved. Confidential and proprietary document.

Airbus RNP Operations


Questions ?

28
Implementing RNP, October 4-5 2005
This document and all information contained herein is the sole
property of AIRBUS S.A.S. No intellectual property rights are
granted by the delivery of this document or the disclosure of
its content. This document shall not be reproduced or
disclosed to a third party without the express written consent
of AIRBUS S.A.S. This document and its content shall not be
used for any purpose other than that for which it is supplied.

The statements made herein do not constitute an offer. They


are based on the mentioned assumptions and are expressed
in good faith. Where the supporting grounds for these
statements are not shown, AIRBUS S.A.S. will be pleased to
explain the basis thereof.

AN EADS JOINT COMPANY


WITH BAE SYSTEMS