2014 Top 5 Safety Priorities Blind Spot and Sector Coordination Tony Licu Head of Safety Unit EUROCONTROL Network Manager Mike Edwards Director Homefield.

Slides:



Advertisements
Similar presentations
Its Good To Squawk! Why YOU should always Squawk Mode C.
Advertisements

1 PHARE Operational Scenarios J-P. Nicolaon, Operational Task Force Chairman EUROCONTROL Experimental Centre.
1 Managed Airspace or Free Flight by Steve Zerkowitz Assistant Director Infrastructure Europe IATA.
7 tasks identified Flight Arrival Interaction Detection Resolution Planning Resolution Implementation Monitoring Other Trajectory Changes Co-ordination.
1 The role of human in ATM automation: a key issue Alain Printemps head of DNA/CENA.
Conflict Detection and Resolution
Page 1 CARE/ASAS Activity 3: ASM workshop Brétigny, 19 December 2001 Autonomous Aircraft OHA CARE-ASAS Activity 3: ASM Autonomous Aircraft OHA.
Page 1 CARE/ASAS Activity 3: ASM workshop Brétigny, 19 December 2001 Autonomous Aircraft OSED CARE-ASAS Activity 3: ASM Autonomous Aircraft OSED.
ICAO European Regional Runway Safety Seminar Amsterdam, The Netherlands 8 March 2012 ir. Job Brüggen, LVNL safety manager The global voice of ATM.
- European CDM - To benefit from the animation settings contained within this presentation we suggest you view using the slide show option. To start the.
Top 5 ATM Operational Safety Priorities
Introduction The Traffic Alert and Collision Avoidance System (TCAS) is an airborne system that interrogates transponders in other aircraft. From the replies.
Leading Teams.
An Introduction to Threat and Error Management 1.
Traffic Processing Sequence — Tactical and Strategic Investigation of all the facts pertaining to the Air Traffic Services tactical and strategic traffic.
Applications from packages I to III
HCI in Safety-Critical Applications: ATC Systems Aslan Neishaboori.
Functional Assessment Observation Form Tutorial
Risk Management Infection prevention and control (IP&C) professionals have, amongst other things, duty to identify unsafe and hazardous IP&C practices.
Root Cause Analysis: Why? Why? Why?
The air traffic controller’s perspective on runway excursion hazards and mitigation options Session 2 Presentation 3.
24 October 2002 ICAO NAM/CAR/SAM RUNWAY SAFETY/INCURSION CONFERENCE 1 Retrospective Human Factors Analysis of US Runway Incursions (Focus: Air Traffic.
NAV CANADA AT A GLANCE NAV CANADA is the non-share capital, private corporation which owns and operates Canada’s civil air navigation service (ANS). It.
Traffic Alert and Collision Avoidance System TCAS
TCAS Basics Capt Craig Hinkley. 2 TCAS HISTORY  Two planes collided over the Grand Canyon  Alternative airborne version using transponders.
Page 1 CARE/ASAS Activity 3: ASM workshop Brétigny, 19 December 2001 Time-Based Sequencing OHA CARE-ASAS Activity 3: ASM Time-Based Sequencing OHA.
ASSTAR Oceanic Applications by Nico de Gelder, NLR ASSTAR User Forum #1 4 April 2006, Roma.
Runway Incursion Avoidance
Study Continuous Climb Operations
FSF Mediterranean: 5 th International Conference “Aviation Safety Performance: Can it be Measured?” Session 1: Challenges Facing Aviation Safety EUROCONTROL.
ASSTAR User Forum #1 Rome 4th April 2006 ASAS-TN2 Second Workshop ASSTAR Safety Approach and Preliminary Issues Dr Giuseppe GRANIERO, SICTA
ASAS-TN Second Workshop, 6-8 October 2003, MalmöSlide 1 Airborne Surveillance Applications included in ‘Package I’ Francis Casaux CARE/ASAS manager.
An Automated Airspace Concept for the Next Generation Air Traffic Control System Todd Farley, David McNally, Heinz Erzberger, Russ Paielli SAE Aerospace.
Situational Awareness Numerous aircraft and operational displays, when combined with effective and efficient communications and facilities, provide Air.
Takeoffs and Landings Traffic pattern collision avoidance And.
Mitigating Culture: Human Error in the Operational ATC World Anthony Smoker RAeS Human Factors Group Mitigating Human Error Conference 15 th October 2003.
RECITE A PRAYER…(15 SECONDS). ATM TOPIC 1. INTRODUCTION TO AIR TRAFFIC MANAGEMENT,TYPE OF CONTROL AREAS & FLIGHT PLAN 2. AERODROME CONTROL 3. AREA CONTROL.
Lecture 10: Traffic alert and Collision Avoidance System (TCAS)
Safety Management in Europe European Organisation for the Safety of Air Navigation Dr. Erik Merckx EUROCONTROL Directorate ATM Programmes Head of Business.
Hazard Identification
Altitude Deviations STEADES In-depth analysis Giancarlo Buono Regional Director, Safety and Flight Operations, Europe.
Glasgow 12 September 20061/22DEEP BLUE CONSULTING AND RESEARCH | CLAUDIA FUSAI ASAS-TN2 Controllers situational awareness issues.
“ A location on an aerodrome movement area with a history or potential risk of collision or runway incursion, and where heightened attention by pilots/drivers.
Discussions Summary ASSTAR - Crossing & Passing session.
Trainings to Avoid Deviations and Incursions. Trainings to Avoid Deviations and Incursions A Big Training Challenge Looking for a Solution.
Low Level Flying And Special Use Airspace Capt John Withelder.
ASAS Crossing and Passing Applications in Radar Airspace (operational concept and operational procedure) Jean-Marc Loscos, Bernard Hasquenoph, Claude Chamayou.
4 th Workshop, Amsterdam, 23 rd -25 th April 2007 ASAS-SEP Applications Airborne Implementation Overall Architectural Considerations.
1 Roma, 3-5 April 2006 – ASAS TN2, 2 nd Workshop, Session 1 – When ASAS meets ACAS When ASAS meets ACAS Thierry Arino (Sofréavia, IAPA Project Manager)
The air traffic controller’s perspective on runway incursion hazards and mitigation options Session 2 Presentation 1.
(Enhanced) Traffic Collision Avoidance System
Page 1 July 28, 2003 Richmond Facility ATN 2003 IEE London Raytheon Integrated Data Link–RIDL
PST Human Factors Jan Shaw Manchester Royal Infirmary CMFT.
Lecture 10: Traffic alert and Collision Avoidance System (TCAS)
Lecture 10: Traffic alert and Collision Avoidance System (TCAS)
Situational Awareness Airport Safety Week Case Study Situational Awareness – Case Study Location: Ramp Area Scenario  A staff member walked behind.
Patuxent River Navy Flying Club Bi-Monthly Safety Briefing October 11, 2016 Dave Kirk PRNFC Safety Officer.
Safety Nets: Primary or Secondary Defenses? Does it Matter?
2017 Safety Forum Runway Incursion scenarios
DJ de Nysschen Wonderboom Air Traffic Control
ASSTAR Oceanic Session Summary
Workshop on preparations for ANConf/12 − ASBU methodology
The air traffic controller’s perspective on runway incursion hazards and mitigation options Session 2 Presentation 1.
The air traffic controller’s perspective on runway excursion hazards and mitigation options Session 3 Presentation 1.
NBAA Single Pilot Working Group
NBAA Single Pilot Working Group
The air traffic controller’s perspective on runway incursion hazards and mitigation options Session 3 Presentation 3.
Root Cause Analysis: Why? Why? Why?
The air traffic controller’s perspective on runway excursion hazards and mitigation options Session 2 Presentation 3.
Workshop on preparations for ANConf/12 − ASBU methodology
Presentation transcript:

2014 Top 5 Safety Priorities Blind Spot and Sector Coordination Tony Licu Head of Safety Unit EUROCONTROL Network Manager Mike Edwards Director Homefield Consultancy

2 Top 5 NDOP – Landing Without Clearance

PUTTING IT INTO CONTEXT For every 1 million flights in European airspace there are around 150 losses of prescribed separation. Each flight receives around 15 executive instructions in the En- Route environment. 1 loss of separation per 100,000 instructions. Primary contributory factor Pilot 60% ATC 30% Dual 10% 1 loss of separation involving ATC factor per 250,000 instructions June 2014 Airborne Conflict Safety Forum3

INEFFICIENT CONFLICT DETECTION OF THE CLOSEST AIRCRAFT Losses of Separation in the En-Route environment sometimes involve a controller “blind spot”. These typically involve either a climb and descent clearance given in consideration of another aircraft or a constraint but not taking into account the aircraft in the immediate proximity. Airborne Conflict Safety Forum June

Generic Scenarios from analysed cases Attention Grabber e.g. Immediate response to a pilot request; Requirement to meet constraints e.g. sector exit levels; No conflict detection due to aircraft not following Flight Plan route e.g. Direct routing to Waypoint clearances; Solving a potential future conflict and not seeing the resultant immediate conflict; Distraction e.g. focussing attention elsewhere. June 2014 Airborne Conflict Safety Forum5 Outcomes Loss of Separation with Executive controller working both aircraft Loss of Separation with Executive controller working one aircraft Loss of Separation with Executive controller working neither aircraft

Barriers that if available and deployed could Prevent the occurrence of a Loss of Separation due to inefficient detection of conflict with the closest aircraft. Mitigate the consequences of a Loss of Separation due to inefficient detection of conflict with the closest aircraft. June 2014Airborne Conflict Safety Forum6

Prevention Barriers June 2014Airborne Conflict Safety Forum PB1 Routine Structured Scanning PB2 Tactically updated Flight Data Display (Direct Waypoint routings) PB3 Proactive Colleagues (Team Resource Management) PB4 Short Term Probe (What if) PB5 Separation Alert Tool (Predictive) PB6 Defensive Controlling (Keep it simple) PB7 Data Block Clarity Brightness/Reduction/Dynamics (Unhide) 7

Mitigation Barriers June 2014Airborne Conflict Safety Forum MB1 Colleague Warning MB2 Pilot Alert (including TCAS TA) MB3 Short Term Conflict Alert MB4 TCAS RA 8

Conclusions 65% of the actual events involved a controller focussing attention on the resolution of a future potential conflict and not taking into account a closer aircraft and the resultant actual conflict. This may support the concept of layered filtering. Some aircraft are filtered out as “Job Done”. There may also be some lessons with regard to less “aggressive” and more defensive controlling. 60% of the actual events involved Flight Data displays that were either not updated or were not capable of being updated to highlight a conflict. 80% of these events also involved an aircraft that was not following its Flight Plan route but was on a direct routing to a Waypoint. This may indicate a need for ANSPs to focus on providing Flight Data to better support controllers in the detection of potential conflicts. June 2014Airborne Conflict Safety Forum9

Conclusions cont’d 30% of actual events involved an immediate response to a pilot request for climb or descent. This may indicate a need to educate controllers with regard to the limitations of attention and to reinforce scanning techniques. 30% of actual events involved a controller focusing attention on a requirement for an aircraft to be at a specific level by the sector boundary. This would appear to have a similar root to the first bullet – living in the future. June 2014Airborne Conflict Safety Forum10 30% of actual events involved a controller having his attention distracted elsewhere and either making a rushed, ill-considered decision or not monitoring his primary display. 30% of actual events involved a split of sectors less than 10 minutes beforehand. A further 12% of events occurred during a sector split or handover/takeover.

Barriers strength Barrier: Proactive Colleague (TRM) has the potential to prevent all losses of separation. Apart from training, this is a cost free barrier. This barrier failed in all of the actual events. The traditional recommendation would involve awareness campaigns on vigilance and professional challenge. Without a knowledge of how this is done on a day to day basis, we cannot make any tangible advance. Barrier: Pilot query (including TCAS derived information) has the potential to reduce the severity of all loses of separation. Apart from training, this barrier is cost free. Barrier: Short Term Probe (What if) has the potential to be an effective barrier against all but events involving controller distraction, whereby the controller would not consider its use. This may have prevented over 70% of the actual event studied June 2014Airborne Conflict Safety Forum11

Barriers strength cont’d Barrier: Updated Flight Data Display (direct to waypoint) could be an effective barrier in all but one situation i.e. controller distraction. This may have prevented over 60% of the actual events studied. Barrier: TCAS Resolution Advisory also has the potential to mitigate the severity of all loses of separation. It resolved or was available to resolve the actual mid-air collision risk in 87.5% of the events. June 2014 Airborne Conflict Safety Forum12

CONFLICT DETECTION WITH ADJACENT SECTORS Losses of Separation in the En-Route environment sometimes involve “inadequate coordination” of clearance with an adjacent sector. These often involve either an early transfer of control to or from the neighbouring sector and either a lack of coordination or misunderstood coordination. June 2014 Airborne Conflict Safety Forum13

Generic Scenarios from actual events Incorrect entry into an adjacent sector after correct co-ordination Incorrect entry into an adjacent sector after incorrect/incomplete/misunderstood co-ordination. Incorrect entry into an adjacent sector after no co-ordination Incorrect entry into an adjacent sector after failure to apply Standing Agreements/Procedures Airborne Conflict Safety ForumJune Barriers - Similar to Barriers identified in Blind spot Study Pro active Colleagues (TRM) What If/Probe tools MTCA / Separation Tools Defensive Controlling – Keep it simple Airspace Incursion tools

Conclusions 68% of actual loss of separation events involved either or both of a failure to correctly apply standard procedures or a failure to coordinate with the relevant sector. The Preventative barriers: Predictive Separation Alert Tool and Airspace Intruder Alert have between them the potential prevent all losses of separation of this type. The Preventative barrier: Proactive Colleague (TRM) has the potential to prevent the causal chain or to stop the potential conflict early. 60% of actual loss of separation events involved an adjacent ACC. Some of them are in the Oceanic environment and most of them indicate areas where communication between ACCs could be improved. 50% of actual loss of separation events involved situations in which the executive controller of the sector was only talking to one of the aircraft. Just over a third of these events involved the early transfer of communication of aircraft away from the sector frequency, but an equal number involved the late transfer or call of aircraft coming into the sector. Airborne Conflict Safety ForumJune

50% of actual loss of separation events involved the early transfer of traffic within the sector to another sector, and hence losing immediate communication and control of that aircraft. This may be partially due to a “filtering out” methodology employed by controllers. “I’m not going to do anything more with this aircraft so I may as well transfer it to the next frequency, job done”. It is suggested that ANSPs and controllers need to consider how the early transfer of communication could increase the potential for undesired outcomes and increase the task of recovery.  33% of actual loss of separation events involved an incorrect plan and more than half of those events (57%) then involved a failure to monitor the incorrect plan. Once a plan is put into operation there is often a “job done” attitude, which results in a lack of monitoring the plan. This was also apparent in the Top 5 “Controller Blind Spots “study. This reinforces the suggestion that an emphasis on Routine Structured Scanning of both radar and flight data would be beneficial. June 2014Airborne Conflict Safety Forum16 Conclusions cont’d

 36% of events occurred when the executive controller of the sector was not in communication with either aircraft. It is clearly an undesired state for a loss of separation to occur between two aircraft within a sector, neither of which is in communication with that sector. The majority of these events (64%) involved the early transfer of communication of an aircraft still in that airspace together with an airspace intruder.  The study identified 40 different contributing factors that were Causal i.e. part of the factor chain that caused the event. This does not include a myriad of contextual factors.  Practical application of the Safety II approach and System safety thinking may provide a greater understanding of these types of events. For example, the actual events studied show little or no evidence of effective controller or pilot/controller Team Resource Management and yet these proactive safety aids must be present when it goes right. June 2014Airborne Conflict Safety Forum17

Top 5 Safety Priorities18 Questions?