Safety Rapporteur Report George Donohue Summary Observations 7 - - PDF document

safety rapporteur report
SMART_READER_LITE
LIVE PREVIEW

Safety Rapporteur Report George Donohue Summary Observations 7 - - PDF document

Safety Rapporteur Report George Donohue Summary Observations 7 papers: 1 European, 1 Joint, 5 US Need for EARLY Safety Analysis Historical Analysis Required for Hypothesis Confirmation Analysis Prioritization Methodology is


slide-1
SLIDE 1

Safety Rapporteur Report

George Donohue

slide-2
SLIDE 2

Summary Observations

  • 7 papers: 1 European, 1 Joint, 5 US
  • Need for EARLY Safety Analysis
  • Historical Analysis Required for Hypothesis Confirmation
  • Analysis Prioritization Methodology is Required to Proceed from

System CONOPS to Qualitative Fault Tree/Hazard Analysis to Quantitative Analysis

  • Quantitative Analysis is Required to Provide System Specifications for

New Technology and Procedures

  • Quantitative Analysis will Develop Validated Models that provide both

Normalization and Quantitative Safety Metrics for System Monitoring

  • We have a Shortage of Trained Safety Analysts to deal with large

number of Issues to be Addressed

  • Example Analysis Presented for New En-Route System Concept,

UAV’s in the NAS, Wake Vortex Encounter and Runway Incursion Severity

slide-3
SLIDE 3

Safety Needs

  • Recent accidents involving ATM
  • Increasing traffic (capacity)
  • Advanced systems (2012; 2017; 2025)
  • Keep ATM safe
  • Anticipate & Resolve Problems
  • Learn before accidents occur

Barry Kirwan, EEC

slide-4
SLIDE 4

Guiding Principles

  • ATM must become a

learning organization

  • ATM must have suitable

methods with which to anticipate and protect itself against risks

  • Safety must be built in

at the early stages of ATM system design, right through to implementation

  • ATM must improve

safety in key risk areas

  • ATM must be sure that

the systems it is developing will deliver the required safety levels

  • ATM must retain its

‘High Reliability’ status and its ‘safe culture’

  • The above collaboration

should be achieved effectively and cost- efficiently

Barry Kirwan, EEC

slide-5
SLIDE 5

Safety Methods

  • Toolbox of 30+ methods (FAA + Eurocontrol + ANSPs):

– Hazard and human error identification – Representation in fault and event trees – Quantification of events & human errors; evidence from incidents/simulations – Analysis of dependence and common mode failures – Evaluation of uncertainty, sensitivity, and risk impact – Determination of safety requirements – Documentation for re-usability

  • Need more Analysts Trained to use these tools
Plan: Do 1. Then do as appropriate. 1.6 Issue delegation instruction 1.6.1 Decide on appropriate instruction Plan: Do 1. Then do 2 if
  • required. Then do 3 to 5
in order. 1.6.2 Instruct pilot to 'Remain behind' 1.6.2.1 Ensure applicability conditions are met/maintained|| 1.6.2.2 Issue instruction(s) to ensure applicability conditions are met|| 1.6.2.3 Issue 'remain behind' instruction|| 1.6.2.4 Receive pilot readback|| 1.6.2.5 Click mouse button A over delegated a/c|| Plan: Do 1 throughout. Then do 2 if required. Then do 3 to 6 in order. 1.6.3 Instruct pilot 'Heading then remain behind' 1.6.3.1 Ensure applicability conditions are met/maintained|| 1.6.3.2 Issue instruction(s) to ensure applicability conditions are met|| 1.6.3.3 Issue 'heading then remain behind' instruction|| 1.6.3.4 Receive pilot readback|| 1.6.3.5 Click mouse button A over delegated a/c|| 1.6.3.6 Receive 'pilot resuming' report|| Plan: Do 1 throughout. Then do 2 if required. Then do 3 to 5 in order. 1.6.4 Instruct pilot to 'Merge behind' 1.6.4.1 Ensure applicability conditions are met/maintained|| 1.6.4.2 Issue instruction(s) to ensure applicability conditions are met|| 1.6.4.3 Issue 'merge behind' instruction|| 1.6.4.4 Receive pilot readback|| 1.6.4.5 Click mouse button A over delegated a/c|| Plan: Do 1 throughout. Then do 2 if required. Then do 3 to 6 in order. 1.6.5 Instruct pilot 'Heading then merge behind' 1.6.5.1 Ensure applicability conditions are met/maintained|| 1.6.5.2 Issue instruction(s) to ensure applicability conditions are met|| 1.6.5.3 Issue 'heading then merge behind' instruction|| 1.6.5.4 Receive pilot readback|| 1.6.5.5 Click mouse button A over delegated a/c|| 1.6.5.6 Receive pilot's merging distance report||

S elect H F Issu e (e.g . “R eco ve ry fro m F ailu re”)

W h at if? L ikely Im pact S afegu ards A ction

S elect n ext H F Is su e (e.g . “S taffin g an d O rg an isatio n ”)

  • Brainstorm What Ifs
  • A n alys e L ikely Im p act &
S afeg u ards fo r each W h at if

A n alyse all o th e r co lum n s fo r e ach W h at if

Barry Kirwan, EEC

slide-6
SLIDE 6

Safety in Design

  • EEC therefore carries out concept

exploration and preliminary design

  • EEC research suggests that 50%

50%

  • f accidents have their roots in the
  • f accidents have their roots in the

design phase design phase

  • EEC has a safety policy, and safety

plans for sector tools, traffic flow, and airport research areas

  • Safety activities are ongoing for

each project in these areas

  • Integrative project is ongoing to

determine safety levels for the integrated vision for 2012

Barry Kirwan, EEC

slide-7
SLIDE 7

Historical Analysis for Hypothesis/Model Validation

Paramete r Description Estimate Standard Error α Intercept

  • 17.00

0.57

β0 Logarithm of operations

1.97 0.09

β1 Logarithm of weather index

  • 0.68

0.08

γ 2002 yearly dummy variable for 2002

  • 0.08

0.03

β2 Log of Airfield/Airspace Delay

0.33 0.03

β3 Log of Arrival Delay

0.04 0.03

β4 Log of Downstream Congestion

  • 0.15

0.04

γ 2001 Yearly dummy variable for 2001

0.22 0.03

Scale

0.264

∑ ∑

+ + + + =

k k k ij j j i i i

D Factor WI OP γ β β β α λ ) ln( ) ln( ) ln( ) ln(

1

Analysis of Daily OE Count: Tower OE

Mark Hansen, UC/B

slide-8
SLIDE 8

Process for New WV CONOPS Analysis Prioritization

Hazard Analysis Model A Model B

. . .

Initial Scenario Ranking Quantitative Analysis Safety Metrics Not Modeled 1 2 3 n-1 n Qualitative Analysis Quantitative Modeling

. . .

Concepts of Operations

Conops Team Safety Analysis Team

John Shortle, GMU

slide-9
SLIDE 9

Safety Assessment for New En-Route System Concept (AAC)

Fault Analysis Concept Definition Fault Identification Safety Calculation Fault Management Design

unresolved fault resolved fault NOMINAL STATE HARDWARE FAULT HARDWARE FAULT MASKING DEFINED NON-NOMINAL STATE SINGLE AC FAULT (TYPE 1) MULTI-AC FAULT (TYPE 2) SINGLE AC MODE TRANSITION RECONFIGURATION Mission Failure Rate λf Rate of Critical Miss Distance Conflicts λ crit λk Rate of Class k Non-conformance events Tk
  • Avg. duration
  • f non-conformance
P[TCAS fails|TSAFE fails] P[TSAFE fails] γ k βk EVENT TYPE k (N event types) P[fault correction fails]αk 1.0E-14 1.0E-12 1.0E-11 1.0E-10 1.0E-09 1.0E-08 1.0E-07 1.0E-06 1.0E-05 1.0E-04 1.0E-03 1.0E-02 1.0E-01 1.0E-00 ACCIDENT RATE (PER FLIGHT HR) λ = 0.005 λcrit = 0.00166 α= 0.10 β=0.01∗ γ=0.1* τcrit= 0.0111 k=1

John Andrews, MIT/LL

slide-10
SLIDE 10

1.0E-06 0.00001 0.0001 0.001 0.01 1.0 10. 100. 1000. 10000 100,000 1,000,000 10,000,000 1.0E-08 1.0E-07 0.1 100,000,000 goal

Safety Assessment

(AAC_B_03e-1)

AAC TCAS TSAFE visual Pcoll P[critical miss] Rate of fault Rate of collisions to be resolved Rate of Type k faults Rate of collisions due to specified fault type

John Andrews, MIT/LL

slide-11
SLIDE 11

See-and-avoid system Aircraft dynamic model Pilot response model

Manned Aircraft

TCAS

UAV Safety Analysis Simulation Components

UAV dynamic model

UAV

TCAS Pilot response model Visual acquisition

= areas of planned growth

Comm Comm

James Kuchar, MIT/LL

slide-12
SLIDE 12

WV encounter Probability Can Be Computed Using Aircraft and WV Stochastic Models

  • Two Phase WV Decay and Propagation Model (2P2)

combined with Aircraft Arrival Flight Track Deviation Model (3 DOF)

  • Effects of Cross Wind and Cross Wind Variance can be

evaluated

  • Encounter Probability and Severity can be Computed for

any mixture of Aircraft Types

Yue Xie, GMU

slide-13
SLIDE 13

Severity of Runway Incursions

  • Safety Analysis is moving from just Event

Counting to Modeling Events and Assessing Severity of Events

Kim Cardosi, Volpe

slide-14
SLIDE 14
slide-15
SLIDE 15

Congratulations “S/V Esprit” The Best Boat Won

From the “S/V Ana G”