PBN development in France Introduction Situation in a pre-PBN context DGAC adherence to the PBN applications Future developments to be considered Conclusion

PBN development in France Introduction (1/3) Development of RNAV procedures based on operational needs but, sometimes, not fully standardised principles Implementation of RNAV procedures in Paris TMA (since 1992 with RWY28 eastbound SIDs in Charles de Gaulle… MOSUD arrival in 1997…DOMUS and VASPO arrivals) Reinforcement of RNAV procedures in Paris TMA in 2001 (predicated on “B-RNAV+”), then in Montpellier, Lyon.

PBN development in France Montpellier departures 13L/31R (B-RNAV+)

PBN development in France Introduction (3/3) Procedures developed as “B-RNAV+” applications BRNAV + additional requirements (temporary provisions included in AIP GEN 1.5-2 and ENR 1.5-4/ October 2001), « B-RNAV+ » procedures must be above MRVA and developed in a radar environment Operational directive issued by our flights standards (N° 2001/1 5 September 2001) wrt « Basic Area navigation (B-RNAV) in terminal area». Regulatory framework well defined... But French In order to prevent this kind of situation, integrated initiative driven by Eurocontrol for standardisation of RNAV in TMA The PBN offers a general, global and awaited standardisation for RNAV operations Avant-dernier point : Regulation changed to prevent development of thos not standardised

PBN development in France DGAC adherence to the PBN applications (1/7) – En-route and TMA En-route : RNAV 5 (B-RNAV) One of the applications described and standardised a long time ago B-RNAV in ECAC since 23d April 1998 (FL245 then FL115 in France) Great benefits provided extension questioned TMA : RNAV 1 (P-RNAV) Safety (harmonisation being one of the objectives) Noise abatement… Possible applications below MSA/AMSR Possible applications above MSA/AMSR Conventional Procedures (non RNAV) OR Conventional Procedures (non RNAV) OR RNAV procedures with P-RNAV capability P-RNAV capability OR RNAV procedures (en-route-criteria design) with B-RNAV capability

Nice departures 04L/R P-RNAV SID INITIAL P-RNAV SID VISUAL APPROACH (helicopters)

PBN development in France DGAC adherence to the PBN applications (3/7) – En-route and TMA Approach French decree dated July, 24th, 2007 already refers PBN applications (RNP 4, Basic-RNP 1, RNP APCH and RNP AR APCH, RNAV 10, RNAV 5, RNAV 1 and 2). Once AMC20-16 available, transition to PBN terms Implementation plans (AIC) : LOCATION IMPLEMENTATION DATE DETAILS Nice Côte d’Azur (LFMN) March 2008 Departures Montpellier Méditerranée (LFMT) 2d quarter of 2008 - Replacement of “B-RNAV+” - Later, modification of RWY13 arrival Lyon-Saint Exupéry (LFLL) 2d or 3d quarter of 2008 Beauvais-Tillé (LFOB) South departures Figari Sud Corse (LFKF) Departure to LFKB Toulouse-Blagnac (LFBO) Between last quarter of 2008 and first half of 2009 SID 32, STAR14 Paris (LFPG, LFPO, LFPB)

PBN development in France DGAC adherence to the PBN applications (4/7) – Approach RNP APCH : Paris CDG assessment by Air France Lateral and vertical deviations at A/P disconnection 95 % box Vertical deviation (°) Assessment since 2002 with more than 7000 approaches Lateral deviation (m) RNP 0.1 Data provided by Air France

PBN development in France DGAC adherence to the PBN applications (5/7) – Approach RNP APCH Published procedures Saint Pierre RWY08 et RWY26 Lyon-Bron RWY12 Lille-Lesquin RWY08 Cayenne RWY08 et 26 Limoges RWY04 Brest RWY08 Hyeres RWY05 Melun RWY29 Biarritz RWY09 Calvi RWY18 Procedures being or yet studied (to be published) Perpignan RWY15 - Fort de France RWY27 et 09… Besançon (Hélicopters) - Clermont-Ferrand RWY26 Saint Denis Gillot RWY12 et 30 - Deauville RWY12 Saint Pierre Pierrefonds RWY15 Nuku Hiva Tikehau Rangiroa Pointe-à-Pitre le Raizet RWY29 Figari RWY23 et 05

PBN development in France DGAC adherence to the PBN applications (6/7) – Approach Other developments foreseen : RNP APCH with baro VNAV and RNP AR RNP APCH with baro VNAV : implication of DCS (Flight standards) in the development of the future Acceptable Means of Compliance (AMC 20 XX) Revision of the vertical navigation performance specification of the PBN possibly needed ESARR 4 compliant safety case to be concluded this year by Eurocontrol? Working group to begin studies with DCS and DAST (regulator) after validation of the French ANSP, DSNA, of its involvement for this application In line with the European Convergence Implementation Plan (ECIP) and navigation strategy RNP AR Flight Operational Safety Assessment under the auspices of Eurocontrol DGAC, Eurocontrol, Air France, Airbus, Thales involved Objective is to demonstrate the TLS Perform an overall analysis : aircraft + crew procedures + design Analysis will focus on Normal, abnormal procedures, aircraft outages (FMS, A/P…), possible crew errors (altimeter setting), infrastructure outages,…

PBN development in France DGAC adherence to the PBN applications (7/7) – Approach Other developments foreseen : RNP APCH with baro VNAV and RNP AR RNP APCH with baro VNAV : Bastia as the assessment aerodrome (Current procedure below)

PBN development in France Future developments to be considered (1/1) Other developments will be necessary PBN to standardise GNSS approaches with vertical guidance APV/SBAS based on EGNOS of particular interest for France Systematic publication of APV/EGNOS approaches where RNP APCH are or are to be implemented (ECIP objective) Very important in a the challenging context of the 36th ICAO assembly decisions (July 2007) “all instrument runway ends should have an approach procedure with vertical guidance (APV), either as the primary approach or as a back-up for precision approaches by 2016 with intermediate milestones as follows: 30 per cent by 2010, 70 per cent by 2014.”

PBN development in France Conclusion DGAC in line with the will to standardise RNAV applications through the PBN PBN implementation plan in place by 2009 Some PBN applications already implemented Consistent with Eurocontrol navigation strategy DGAC, through its experts, to support future developments of PBN