Federal Aviation Administration Runway Safety Action Team 2014 Gary A. Palm ATM Teterboro ATCT

2 Federal Aviation Administration Runway Safety Action Team 2011 VIDEO

3 Federal Aviation Administration Runway Safety Action Team 2011 INCIDENTS Year# of incidents

4 Federal Aviation Administration Runway Safety Action Team 2011 HOT SPOTS

5 Federal Aviation Administration Runway Safety Action Team 2011 RUNWAY 6 & TAXIWAY G

6 Federal Aviation Administration Runway Safety Action Team 2011 RUNWAY 1 & TAXIWAY Q

7 Federal Aviation Administration Runway Safety Action Team 2011 RUNWAY 1 & RUNWAY 6

8 Federal Aviation Administration Runway Safety Action Team 2011 RUNWAY 19 & TAXIWAY L

9 Federal Aviation Administration Runway Safety Action Team 2011 RUNWAY 1 & TAXIWAY B

10 Federal Aviation Administration Runway Safety Action Team INCIDENT Incident # 001 (2/27/13) Aircraft issued taxi instructions for runway 24 and instructed to hold short of runway 19. Pilot readback all instructions correctly. During taxi aircraft crossed runway 19 and a Sabreliner on short final was sent around.

11 Federal Aviation Administration Runway Safety Action Team INCIDENT Incident # 002 (2/08/13) After landing runway 06, NXXX, a Hawker Jet was instructed to turn left on Bravo Taxiway and hold short of runway 01. Pilot readback all instructions correctly. Instead pilot turned onto runway 01 in front of an aircraft that was cleared for takeoff.

12 Federal Aviation Administration Runway Safety Action Team INCIDENT Incident # 003 Class ‘Bravo’ Pilot Deviation. N/A to TEB operations.

13 Federal Aviation Administration Runway Safety Action Team INCIDENT Incident # 004 (6/03/13) After landing runway 06, a Challenger, was issued taxi instructions to turn left on taxiway Bravo and hold short of runway 01. Pilot readback all instructions correctly. The aircraft complied with the left turn onto Bravo taxiway but crossed the hold short lines for runway 01. Aircraft stopped at the runway edge line.

14 Federal Aviation Administration Runway Safety Action Team INCIDENT Incident #5 (9/05/13) Aircraft issued taxi instructions for runway 24 and instructed to hold short of runway 19 at taxiway Quebec. Pilot readback all taxi instructions correctly. During taxi pilot taxied past Quebec then crossed runway 24. Traffic was on departure roll for runway 24 and was issued a cancellation of takeoff clearance. 14

15 Federal Aviation Administration Runway Safety Action Team Causal Factors  Incident #001 –#1 Vehicle left Rwy Environment –#2 Operator assumed it was ok to re-enter the Rwy w/o authorization or verification.  Incident #002 –#1- Insufficient training –#2 Failure to check radio equipment operations.  Incident #003 –#1 Hearing what you are expecting or anticipating.  Incident #004 –#1 Anticipation –#2 Awareness!! –#3 Inattentiveness –#4 Training

16 Federal Aviation Administration Runway Safety Action Team Causal Factors Causal Factors (Possible): ALL INCIDENTS > CRM > Crew briefing (pre-flight) > Awareness Or….distracted, unfamiliar, equipment issues or combinations (links in the chain). Statistics do not include incidents that were anticipated and stopped by controllers (or PICs). No one asked for assistance. 16

17 Federal Aviation Administration Runway Safety Action Team 2011 PRIOR YEAR R.S.A.P. & ACCOMPLISHMENTS 1.Reviewed “Hot Spot” locations and redefined as necessary In agreement with PANYNJ (L/19) “Hot Spot” was eliminated and the remaining three redrawn 2.Reduce/eliminate Runway Crossings Completed review of vehicle crossing with PANYNJ Operations PANYNJ implemented new procedures defining vehicle routes and priorities for crossing runways 2010 LOA also established new holding point procedures. Vehicles must not approach runways prior to receiving authorization from ATC Estimated 60% runway crossings have been eliminated ***2013 ZERO VEHICLE INCIDENTS

18 Federal Aviation Administration Runway Safety Action Team 2011 R.S.A.P Objectives 1.Improve Emergency Response and Communication Procedures ATC and Port Authority PD and FD meeting to discuss and outline objectives. Action plan includes interdepartmental collaboration to fully develop a clear understanding of relevant agencies’ needs during emergency responses. Improve communication and information sharing.

19 Federal Aviation Administration Runway Safety Action Team RSAP Results  Monthly meetings with ARFF.  Monthly emergency exercises are conducted.  Critiques of exercises.  Improved communications & phraseology.  No incidents involving emergency equipment or personnel.  Still working on personnel orientation meetings. 19

20 Federal Aviation Administration Runway Safety Action Team RSAP Objectives  Continue efforts to reduce vehicle runway crossings and sustain zero incident base- line.  (re-configure taxi Bravo, add Perimeter road)  Continue efforts to improve emergency response operations through personnel orientation exchanges.  Develop & add to Tower Training Simulator: unexpected vehicle/aircraft operations. 20

21 Federal Aviation Administration Runway Safety Action Team 2011 Conclusion Overall, significant incidents have fallen; whether by improved procedures, airport design, training or awareness however, we must continue to strive for and MAINTAIN a ZERO incident(s) goal. Your input is a vitally important catalyst for change. Take action, submit ideas, report issues and never assume someone else will take corrective measures or fix the problem. COMMENTS AND QUESTIONS……………..