colombian pbn implementation: el dorado case study · colombian pbn implementation: el dorado case...
TRANSCRIPT
Colombian PBN implementation:El Dorado case studySDM WORKSHOP ON PBN
XAVIER OUTTERSSME & PROJECT MANAGERNAVBLUE SAS
19.10.2017
Electronic Flight Bag
Databases
Avionics
- ROPS+
- FlySmart+- Charts+- Mission+
- Navigation+- Airport+
PILOTS
Dispatch
Crew management
Pre-flight
- N’Flight Planning- N’Tracking- N’Performance- N’RAIM
- N’Crew- N’RAIDOThe picture can't be displayed.
DISPATCHERS
- ADOC- AODB
Post-flight
- AIRFASE- ANALYTICS
FLIGHT OPS ENG.
Airport
Airspace
- ELISE by NAVBLUE
- GNSS by NAVBLUE
- DESIGN by NAVBLUE
- ASSESS by NAVBLUE
ANSP & Airports
Consulting
- YourOps
NAVBLUE is a services company, wholly owned by Airbus, dedicated to Flight Operations & Air Traffic Management Solutions.
03 Challenges and lessons learnt
02 KPIs, solutions, expected benefits
01 Project Overview
Project OverviewCHAPTER 01
5
PAX numbers within Latin American region grew 23% from 2012-2016
Bogota PAX grew more than 60% in only 6 years… with a 15% increase of airport operations
6
Project ObjectivesInternational Cooperation Agreement to Redesign the Airspace & Optimize Airside Capacity at Bogota El Dorado Airport
To position Bogotá El Dorado international airport as one of the most efficient international terminals in Latin America by increasing its capacity and airspace efficiency through: Introduction of PBN Reduction of aircraft separation within the TMA Implementation of independent and simultaneous parallel
runways operations Improvement of ground operations Update of regulations & operations manuals Enhancement of ATC capability with theoretical & practical
On-The-Job Training (OJT)
7
Bogota urgently needed an airspace turnaround
• ATCOs vector ~100% of arriving aircrafts (high workload)
• Encounter/dispersed flows
• Inefficient use of runways
• Holding patterns
• Bottleneck at VOR
• Limited access to RWY 31L/R
8
Bogota’s ATCOs constantly outperform their own limits!
Reference Day 09/10/2015
9
• Uneven sectors work balance (North Sector taking most of the load)
• Excessive radio comms. due the 100% vectoring of arrivals.
• Job dissatisfaction
• Increased workload due to continuous traffic increase within TMA
TMA workload needed to be balanced
KPIs, solutions, expected benefits CHAPTER 02
11
Desired outcome and solution matrix (1/2)
• Matrix matching existing situation against a desired outcome.
• Identified solutions matching any combination of safety, capacity, efficiency, environment, or access factors.
• First two main items required GAP / Solutions to increase capacity and user RNAV to improve access and efficiency within Bogota TMA
12
Desired outcome and solution matrix (1/2)
• Further desired outcome items looked to balance ATC sector workload and reduce complexity by implementing RNAV SIDs and STARs.
• Simultaneous independent approaches to balance capacity.
• Design facilitated CCO and CDO operations, and balanced city-pair flows.
• Radio transmissions dropped significantly reducing both ATC and crew workload.
SKBO TMA - PBN Expected Benefits
• Increase in airspace capacity (simulation runs):
o RNW13: 92 ops per hour (29.2% increase)
o RNW31: 68 ops per hour (126% increase)
• Reduction in ATCOs workload (60% less communications per aircraft)
• Flexibilization of restricted military airspace
• Reduced workload for pilots.
• Expected financial efficiencies for up to US100M/year
Bogota CONOPSRunway 13
14
• Independent trajectories with altitude separation
• Reduced ATCO workload due to repeatable trajectories and predicted trajectory distances.
• Reduces crew workload based on strategic coding of trajectories in NavDB.
• Reduced ATCO intervention• Improved safety
Point of Merge System
• All aircraft sent direct AMVES (point merge).
• Better traffic management compared to sending aircraft to previous VOR due to specifically designed RNAV system.
• Non-RNAV aircraft vectored to VOR to complete conventional procedure.
• Appropriate management of reduced separation down to 3nm.
15
EDR CONOPSRunway 31
• Altitude separation• Reduced ATCO/ crew
workload• Reduced ATCO
intervention• Improved safety
16
17
• Reduced span of control for each individual sector.
• Balanced workload across sectors based on inbound and outbound flow demands.
• Fewer conflicts to manage
• Reduced ATCO workload
• Reduced ATCO intervention
New TMA Sectors
Challenges and lessons learntCHAPTER 03
19
CONOPS– Reference Day 09/10/2015 + 40% Traffic
Design• Access to RWY 31 for both RNP and non-
RNP capable aircraft = RNP AR trajectories + RNAV Visual published by Authority.
• Non-RNAV aircraft within the TMA = Kept selected non-RNAV SID’s and STARs published at lower altitudes + conventional ILS from BOG-VOR. NOTAM published that RNAV SIDs and STARs must be filed as a first requirement.
• Fast Track Project = KoM to Implementation in two years. Only way is for all stakeholders to be aligned with main scope and objective
•Jet Vs Turboprop = Trajectories designed considering faster aircraft overcoming slower aircraft.
20
ATC Training• Change a “20-year” with a “new” way of
working = Only way is with ATC to be part of the design, undergo and appropriate training, and commit to change.
• Knowledge transfer process (both ways) = understanding PBN benefits, allowing technology to help achieve goals, and trust that all parties (ATC, Operators, Regulators) are committed to success.
• Achieve change via training = tailored training program including simulations for all area and tower controllers, and On the Job Training to accompany ATC during initial implementation of operations.
Project Challenges and Lessons Learnt
Stakeholders• Successful public-private collaboration =
Identify people that “don’t believe” and lead them to understand and then to “believe”. Commitment from all stakeholders is a must for the success of such a big project.
• Coming up with a final design = Discuss options separately with each stakeholder, then identify and resolve as best as possible items that don’t match. Solutions may not match all stakeholder “wants”, but an initial design can only be made better in time.
• Airspace needs to be shared by everyone.
21
Military Flexible Use of Airspace (FUA)• Use of Military airspace = Military forces
wishing to share exclusive use of airspace when not in use for the benefit of the overall commercial aviation industry.
• Military – Civil aviation FUA Letter of Agreement = Designed under international guidelines to ensure an appropriate agreement between both parties on how / when to use the mentioned airspace.
• Orderly FUA = Specific RNAV trajectories designed to be used by qualified commercial aircraft. Trajectories reduce overall arrival track miles, or allow use of airspace during adverse weather in other TMA Areas.
Project Challenges and Lessons Learnt
© AIRBUS S.A.S. ALL RIGHTS RESERVED. CONFIDENTIAL AND PROPRIETARY DOCUMENT. THIS DOCUMENT AND ALL INFORMATION CONTAINED HEREIN IS THE SOLE PROPERTY OF AIRBUS. 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. AIRBUS, ITS LOGO, A300, A310, A318, A319, A320, A321, A330, A340, A350,
A380, A400M ARE REGISTERED TRADEMARKS.
ContactXAVIER [email protected]: +33 776329054