DOCSLIB.ORG

Runway Safety

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Runway Safety Federal Aviation Administration Runway Safety Presented to: RASG – Pan America Meeting By: James white, Deputy Director Airport Safety and Standards, FAA Date: November, 2009 Reducing Safety Surface Operations Risk Factors Minimal separation and rapid pace High-speed operations with little margin for error Complex environment Low visibility in poor weather Combination of Factors Minimizes Safety Margin Federal Aviation 2 2 November 2009 Administration All Categories of Runway Incursions Rate est. 1200 18.08* as Runway Incursions Airport1,000,000 per Operations of 09/30/09 1009 Runway IncursionRate 18.0 1000 892 951 816 779 17.23 16.0 800 14.57 14.0 600 13.34 12.36 12.0 400 10.0 200 0 FY05 FY06 FY07 FY08 FY09 63.01 61.13 61.15 58.56 52.59 Airport Operations (millions) * Rates are based on Estimated Tower Operations Federal Aviation 3 3 November 2009 Administration Category A&B Runway Incursions 0.600 Category A&BRunway IncursionRate 60 Runway Incursions Airport1,000,000 per Operations 0.507 0.460 0.500 50 0.427 0.392 0.400 40 Rate est. 0.228 * 31 as of 09/30/09 29 Performance Reference = 0.300 0.472 * 30 24 25 0.200 20 12 0.100 10 0.000 0 FY05 FY06 FY07 FY08 FY09 63.01 61.13 61.15 58.56 52.59 Airport Operations (millions) * Rates are based on Estimated Tower Operations Federal Aviation 4 4 November 2009 Administration ParticipationParticipation inin RSATsRSATs Federal Aviation 5 5 November 2009 Administration ParticipationParticipation inin RSATsRSATs The preliminary inspection of the movement area includes: 1. Identifying non-standard marking, lighting, and signs. 2. Examining problem intersections for potentially confusing visual aids. 3. Review any past RSAT recommendations related to pilot visual aids for proper implementation. Federal Aviation 6 6 November 2009 Administration During the airfield tour, the Team noted that when exiting Runway 2 onto Taxiway Bravo, a destination sign blocked a taxiway direction sign for Taxiway November. N Federal Aviation 7 7 SGFNovember 2009 Administration Some pilots mistakenly believe that the takeoff end of Runway 3 is straight ahead. Taxiway Echo straight ahead is a dead end at Combat Air Museum and Army National Guard area. Southwest Left turn to Runway 3. Federal Aviation 8 8 FOENovember 2009 Administration Recommendation – Highlight the taxiway centerline from Alpha around the corner towards Runway 3 and install a surface painted destination sign for Runway 3. Southwest Federal Aviation 9 9 FOENovember 2009 Administration Recommendation Implemented Federal Aviation 10 10 FOENovember 2009 Administration pConduct recurrent ground vehicle training, especially for seasonal procedures. Federal Aviation 11 11 November 2009 Administration Runway Safety Initiatives •FAA Call to Action - Reducing Runway Incursions •Enhanced and Alternative Airport Markings •New Airfield Lighting Systems and Sources •Runway End Safety Areas (RESAs) •Engineered Material Arresting Systems (EMAS) •Wildlife Hazard Mitigation •Safety Management Systems (SMS) •FAA Airport Technology R&D Federal Aviation 12 12 November 2009 Administration New Airport Markings Enhanced Taxiway Centerline Surface Holding Position Signs http://www.faa.gov/airports_airtraffic/airports/airport_safety/signs_marking/ Federal Aviation 13 13 November 2009 Administration Runway Status Lights (RWSL) Configurations Runway Entrance Lights (RELs) Takeoff Hold Lights (THLs) Federal Aviation 14 14 November 2009 Administration RWSL – Runway Entrance Lights (RELs) Alternating • Yellow and Green • Old Standard New Standard Federal Aviation 15 15 November 2009 Administration RWSL – Take-Off Hold Lights (THLs) Alternating • Yellow and Green • Old Standard New Standard Federal Aviation 16 16 November 2009 Administration RWSL Installation Plan • RWSL will be installed at 22 ASDE-X airports • Contract awarded fall 2008 • FAA owns, operates, and maintains entire system • Complete installations end of 2012. Federal Aviation 17 17 November 2009 Administration RUNWAY SAFETY AREAS • RSAs HAVE EMERGED AS ONE OF THE MOST IMPORTANT INVESTMENTS AT OUR AIRPORTS. Federal Aviation 18 18 November 2009 Administration LESSONS LEARNED • BURBANK, CALIFORNIA Federal Aviation 19 19 November 2009 Administration Burbank EMAS Federal Aviation 20 20 November 2009 Administration Successful EMAS Capture Courtesy: ESCO EMAS capture of a Boeing 747 at JFK International Airport, NY January 2005 Federal Aviation 21 21 November 2009 Administration Successful EMAS Capture EMAS capture of a Falcon 900 at Greenville Downtown Airport, SC July 17, 2006 Federal Aviation 22 22 November 2009 Administration Wildlife Hazard Mitigation Federal Aviation 23 23 November 2009 Administration WildlifeWildlife HazardHazard MitigationMitigation R&DR&D (RPD(RPD 150)150)‏‏ •• Purpose:Purpose: ReduceReduce WildlifeWildlife StrikeStrike RiskRisk toto AircraftAircraft Federal Aviation 24 24 November 2009 Administration Wildlife Hazard Management • When air carrier experiences a multiple bird strike, engine ingestion, or damaging collision with wildlife other than birds, airport must do a Wildlife Hazard Assessment. • If required then must develop a Wildlife Hazard Management Plan Federal Aviation 25 25 November 2009 Administration Wildlife Hazard Management Plan • Provide measures to alleviate or eliminate wildlife hazards. • Identify persons who have authority for implementing the plan. • Priorities for needed habitat modification. • Identification of resources for the plan. • Procedures to be followed during air carrier operations. • Wildlife control measures. Federal Aviation 26 26 November 2009 Administration Wildlife Hazard Mitigation • Habitat modification – Grass height, – Type of grass, – Harrassment • Effigies – Relocation • Wildlife alerting system – Portable radar – Airport GIS overlay • DNA analysis at Smithsonian • Strike database (wildlife-mitigation.tc.faa.gov) Federal Aviation 27 27 November 2009 Administration AvianAvian RadarRadar Examples of Commercial Systems Federal Aviation 28 28 November 2009 Administration Deployment of Avian Radars • Seattle – SEA TAC Airport – Permanent Installation completed June 2007 • Oak Harbor – Whidbey NAS – AR-1 installed February 2009 • New York – JFK Airport – AR-1 and AR-2 deployed Summer 2009 • Boston Logan – Negotiating for Merlin radar installation Fall 2009 • Chicago – ORD – AR-1 and AR-2 deployed Summer 2009, 2009 Federal Aviation 29 29 November 2009 Administration Aircraft Rescue and Firefighting • Ongoing research • New large aircraft mock-up • Extendable reach turret • Penetrating nozzle Federal Aviation 30 30 November 2009 Administration Fire Research Mock-up Section Federal Aviation 31 31 November 2009 Administration ARFF – Penetrating Nozzles Federal Aviation 32 32 November 2009 Administration ARFF – High Reach Extendible Turret (HRET) Current Generation • 2nd level penetration possible, however, vehicle will be too close to burning aircraft and aircraft must be level. • Penetrating nozzle should be as close to 90 deg. to skin as possible. • Penetrating nozzle should be in-line with boom arm. Federal Aviation 33 33 November 2009 Administration Next Generation High Reach Extendible Turret (HRET) Update: • Live Fire Testing – 80% Complete • Timed system deployment – Completed • Boom oscillation testing – Mechanical problems during preliminary testing – fixed & upgraded by OEM – Schedule for completion 3/09. • Standoff distance during piercing operations - Completed Federal Aviation 34 34 November 2009 Administration National Pavement Test Facility • Pavement test machine Federal Aviation 35 35 November 2009 Administration NAPTF Test Vehicle Instrumented Test Track at the NAPTF, FAA Technical Center Federal Aviation 36 36 November 2009 Administration CC5 Gear Configuration Federal Aviation 37 37 November 2009 Administration Federal Aviation Automated FOD DetectionAdministration Why is the FAA Interested? “It has become clearer that this was a unique accident caused by a one-off chance of a piece of metal lying on the runway“. -Concorde crash Presented to: RASG – Pan America Meeting preliminary report By: James white, Deputy Director Airport Safety and Standards, FAA Date: November, 2009 Automated FOD Detection Available Technologies: • QinetiQ – Tarsier Radar – Providence, RI (PVD) – Milimeter Wave Radar – Mounted on Rigid Towers • Stratech – iFerret – Chicago O’Hare (ORD) – High Resolution Camera – Mounted on Rigid Towers • X-Sight – FODetect – Boston Logan (BOS) – High Resolution Camera and Millimeter Wave Radar – Mounted on Airport Lighting Fixtures • Trex Enterprises – FOD Finder – Chicago Midway (MDW) – Milimeter Wave Radar and Infrared Cameras – Mounted on roof of Airport Vehicle Federal Aviation 39 39 November 2009 Administration Federal Aviation Automated FOD DetectionAdministration QinetiQ – Tarsier Radar, Providence, RI Presented to: RASG – Pan America Meeting By: James white, Deputy Director Airport Safety and Standards, FAA Date: November, 2009 Automated FOD Detection XSight - FODetect Federal Aviation 41 41 November 2009 Administration Tarsier Camera in operation Federal Aviation 42 42 November 2009 Administration Tarsier Camera in operation Federal Aviation 43 43 November 2009 Administration Example FOD finds by the QinetiQ system Federal Aviation 44 44 November 2009 Administration FOD Detection Radar • R&D evaluation completed 2009 • FOD performance specification issued September 2009. Federal Aviation 45 45 November 2009 Administration.
Load more

Recommended publications
  • Human-In-The-Loop Simulation of an Integrated Ground Movement Safety System
    MTR 05W0000074 MITRE TECHNICAL REPORT Human-in-the-Loop Simulation of an Integrated Ground Movement Safety System September 2005 Dr. Peter M. Moertl This is the copyright work of The MITRE Corporation and was produced for the U.S. Government under Contract Number DTFA01-01-C-00001 and is subject to Federal Aviation Administration Acquisition Management System Clause 3.5-13, Rights in Data-General, Alt. III and Alt. IV (Oct., 1996). Sponsor: Federal Aviation Administration Contract No.: DTFA01-01-C-00001 Dept. No.: F053 Project No.: 0205F110-DW Approved for public release; distribution unlimited. The contents of this material reflect the views of the author and/or the Director of the Center for Advanced Aviation System Development. Neither the Federal Aviation Administration nor the Department of Transportation makes any warranty or guarantee, or promise, expressed or implied, concerning the content or accuracy of the views expressed herein ©2005 The MITRE Corporation. All Rights Reserved. Center for Advanced Aviation System Development McLean, Virginia MITRE Department Approval: Urmila C. Hiremath Associate Program Manager ATM/CNS Research Computing Capability MITRE Project Approval: Edward C. Hahn Outcome Leader Aviation Safety ii Abstract This document describes a human-in-the-loop simulation evaluating the effectiveness of an integrated ground movement safety system for improved runway safety. The evaluated ground movement safety system contained technologies to enhance pilot awareness as well as warn pilots about runway safety risks and had been proposed by Andrews, Dorfman, Estes, Jones, and Olmos (2005). Strengths and limitations of this integrated system as well as possibilities to address these limitations were determined.
    [Show full text]
  • SANDOR Safe Airport Navigation Demonstrator
    Doc.nr.: KDC/2010/0065 Version: 1.0 Date: 20 okt 2010 SANDOR Safe Airport Navigation DemonstratOR Summary Safety on the airport surface is of great importance to the Schiphol operation. In order to keep safety at a high level for now and in the future when traffic numbers grow, it is necessary to improve the ATM system with respect to the ground operation. In 2007 the KDC study “Increased ground handling capacity” was conducted. The focus of that study was to solve hot-sports in the traffic flow during good visibility conditions. Low visibility conditions were only briefly discussed. So although an in- depth research was not conducted, it concluded that synthetic vision applications could improve the situational awareness of the cockpit crew and therefore could improve safety. In this project several applications and tools to improve the surface operation have been researched. The starting point was a runway safety analysis which was performed for the years 2007-2009 to learn what is important for the current ground operation at Schiphol. The cases that were studied led to ten different types of runway incursions. Using an identified formula for the potential gravity of runway incursions at Schiphol which was developed by the project team, it was decided that the potentially most dangerous situations are: - line-up without ATC clearance - taxiing on an active runway without ATC clearance - vehicle on the runway without ATC clearance Besides the runway incursion analysis a complete list was compiled of what kind of tools in the area of Advanced Surface Movement Guidance and Control Systems (A-SMGCS) have already been invented, developed or are even being deployed internationally.
    [Show full text]
  • Notice Federal Aviation Administration
    U.S. DEPARTMENT OF TRANSPORTATION N JO 7210.842 NOTICE FEDERAL AVIATION ADMINISTRATION Air Traffic Organization Policy Effective Date: March 29, 2013 Cancellation Date: March 28, 2014 SUBJ: Guidance for the Use of Runway Status Lights (RWSL) Light System 1. Purpose of This Notice. This notice provides guidance to the air traffic manager (ATM) and/or front line manager (FLM) concerning the operations and periodic check of the RWSL system. A new paragraph will not be added to FAA Order JO 7210.3 until after all testing is complete. 2. Audience. This notice applies to the Air Traffic Organization (ATO) Terminal Services Units at the following airport: Orlando International Airport (MCO). Airports that are not currently conducting RWSL testing but that may begin testing RWSL, are as follows: George Bush Intercontinental/Houston Airport (IAH); Phoenix Sky Harbor International Airport (PHX); Washington Dulles International Airport (IAD); Minneapolis-St. Paul International/Wold-Chamberlain Airport (MSP); Charlotte/Douglas International Airport (CLT); Fort Lauderdale/Hollywood International Airport (FLL); Seattle-Tacoma International Airport (SEA); Detroit Metropolitan Wayne County Airport (DTW); Baltimore/Washington International Thurgood Marshall Airport (BWI); Chicago O'Hare International Airport (ORD); McCarran International Airport (LAS); San Francisco International Airport (SFO), and LaGuardia Airport (LGA). 3. Where Can I Find This Notice? This notice is available on the MyFAA employee Web site at https://employees.faa.gov/tools_resources/orders_notices/ and on the air traffic publications Web site at http://www.faa.gov/air_traffic/publications. 4. Explanation of Policy Change. This notice cancels N JO 7210.812, Guidance for the Use of Runway Status Lights (RWSL) Light System at Orlando, FL, Airport (MCO), effective May 4, 2012.
    [Show full text]
  • Controller and Pilot Error in Airport Operations: a Review of Previous Research and Analysis of Safety Data
    Controller and Pilot Error in Airport Operations: A Review of Previous Research and Analysis of Safety Data DOT/FAA/AR-00/51 DOT-VNTSC-FAA-00-21 Office of Aviation Research Washington, DC20591 Kim Cardosi, Ph.D. Alan Yost U.S. Department ofTransportation Research and Special Programs Administration John A. Voipe National Transportation Systems Center Cambridge, MA 02142-1093 Final Report January 2001 This document is available to the public through the National Technical Information Service, Springfield, Virginia 22161 O U.S. Department ofTransportation Federal Aviation Administration NOTICE This document is disseminated under the sponsorship of the Department of Transportation in the interest of information exchange. The United States Government assumes no liability for its contents or use thereof. NOTICE The United States Government does not endorse products or manufacturers. Trade or manufacturers' names appear herein solely because they are considered essential to the objective of this report. Form Approved REPORT DOCUMENTATION PAGE OMB No. 0704-0188 PuMcreporting burden torttnscollection ol information 6 estimated to average 1tourperresponse, mduolrigffw timeforreviewing ensawr^sourceSjMlJier^andmamtainttigirte data neeoWa^amptetirnaxlrenewrathecoDedOTolW SendMrmwrtsreoarSr^fts burden estimate oranyotheri olthiscoQecSon ofinformation, inctuanasuggestionsforr (hisburden, toWashington Headquarters Services, Directorate forInformation Operators andRep^ 1204, Arlmgton, VA 22202-4302, and toBte &$M Ol M and Budaet PapeworgReftrtonProject (0704-01B8). WaslfoSon. PC 20503. _ 1. AGENCY USE ONLY (Leave blank) 2. REPORT DATE 3.REPORTTYPE AND DATES COVERED January 2001 Final Report January 1997 -June 1999 4. TITLE AND SUBTITLE 5. FUNDING NUMBERS Controllerand Pilot Errorin AirportOperations: A Review ofPreviousResearch and Analysis of SafetyData FA1L1/A1112 6. AUTHOR(S) Kim Cardosi. Ph.D„ Alan Yost 7.
    [Show full text]
  • Pilot Evaluations of Runway Status Light System
    / NASA Technical Memorandum 4727 Pilot Evaluations of Runway Status Light System Steven D. Young, Robert W. Wills, and R. Marshall Smith October 1996 NASA Technical Memorandum 4727 Pilot Evaluations of Runway Status Light System Steven D. Young, Robert W. Wills, and R. Marshall Smith Langley Research Center • Hampton, Virginia National Aeronautics and Space Administration Langley Research Center • Hampton, Virginia 23681-0001 October 1996 The use of trademarks or names of manufacturers in this report is for accurate reporting and does not constitute an official endorsement, either expressed or implied, of such products or manufacturers by the National Aeronautics and Space Administration. Acknowledgments The authors would like to thank Vern Edwards of the Federal Avia- tion Administration, Robert Rudis of the Volpe National Transporta- tion Systems Center, Jerry Wright of the Air Line Pilots Association, and the LaRC flight simulation laboratory staff for their help in this investigation. Without their efforts, this project could not have been completed. Available electronically at the following URL address: http://techreports.larc.nasa.gov/Itrs/ltrs.html Printed copies available from the following: NASA Center for AeroSpace Information National Technical Information Service (NTIS) 800 Elkridge Landing Road 5285 Port Royal Road Linthicum Heights, MD 21090-2934 Springfield, VA 22161-2171 (301) 621-0390 (703) 487-4650 Contents Abbreviations ...................................................................... v Abstract ..........................................................................
    [Show full text]
  • Timing Is Everything
    AIRPORTOPS hen the U.S. Federal Aviation that airport surface detection equipment, If the deployment repeats the success Administration (FAA) awards model X (ASDE-X) — a surface surveil- of systems already tested at Dallas-Fort a contract in late 2008 to lance system designed to identify and Worth (DFW) and San Diego inter- install runway status lights display traffic and, in enhanced versions, national airports, one result will be a W(RWSL) at 22 major U.S. airports1 in automatically alert air traffic control compelling case for updating interna- 2009–2011, the worldwide aviation com- (ATC) to imminent ground collisions — tional standards to add RWSL to existing munity will be anxious to hear about the has proved to be a key enabler. defenses against the human errors and new system’s effectiveness in preventing “We have an approval and a com- other causes of runway incursions. runway incursions. From 2001 to Febru- mitment of capital to go out and invest Saves So Far ary 2008, the FAA spent US$25.8 million hundreds of millions of dollars in get- The FAA cites two occurrences in 2008, to complete its research, development ting RWSL to these airports,” said Jaime both at DFW, as prime examples of and operational evaluation of RWSL. Figueroa, field demonstration manager, RWSL providing safety-critical situation- Available technology did not enable surface technology assessment, FAA al awareness quickly enough to prevent a a nation wide deployment in the mid- Air Traffic Organization (ATO) Opera- runway collision with complete inde- 1990s — the last time the FAA studied tions Planning.
    [Show full text]
  • Runway Status Lights Information
    Runway Status Lights Information What Are Runway Status Lights? Runway Status Lights (RWSL) are a series of red in-pavement lights that warn pilots of high-speed aircraft or vehicles on runways. They operate independently of Air Traffic Control. Runway Status Lights have two states: ON (lights are illuminated red) and OFF (lights are off) and are switched automatically based on information from the airport surface surveillance systems. RWSL will improve airport safety by indicating when it is unsafe to enter, cross, or takeoff from a runway. The RWSL system has two types of lights. Runway Entrance Lights (RELs) are installed at taxiways and Takeoff Hold Lights (THLs) on runways. Runway Entrance Lights Runway Entrance Lights (RELs) are a series of red in-pavement lights spaced evenly along the taxiway centerline from the taxiway hold line to the runway edge. One REL is placed before the hold line and one REL is placed near the runway centerline. RELs are directed toward the runway hold line and are oriented to be visible only to pilots entering or crossing the runway from that location. RELs that are ON (illuminated red) indicate that the runway ahead is not safe to enter or cross. Pilots should remain clear of a runway when RELs along their taxi route are illuminated. Lights that are off convey no meaning. The system is not, at any time, intended to convey approval or clearance to proceed into a runway. Pilots remain obligated to comply with all ATC clearances, except when compliance would require crossing illuminated red RELs. In such a case, the crews should hold short of the runway for RELs, contact ATC, and await further instructions.
    [Show full text]
  • Safety Bulletin Caution on Use of Runway Status Lights in the US
    Safety Bulletin 17SAB09 25 October 2017 Caution on use of Runway Status Lights in the US This Safety Bulletin is a reprint from our Member Association, ALPA-I, issued Safety Alert Bulletin 2017-02. BACKGROUND The Federal Aviation Administration (FAA) issued a Safety Alert for Operators (SAFO) 17011 on September 28, 2017, to ensure that aircraft operators, pilots and airport personnel are aware of the installation, meaning and use of Runway Status Lights (RWSLs). RWSLs are fully automated systems of red lights that are designed to aid in preventing runway incursions and ground collisions. The RWSL system integrates airport lighting equipment with approach and surface surveillance radar systems to provide aircraft and vehicle crews a visual cue indicating when it is unsafe to enter/cross or begin/continue takeoff on the runway. According to the FAA, there have been several instances at airports equipped with RWSLs in which flight crews have failed to stop after receiving a clearance by Air Traffic Control while these red lights were lit. Illuminated RWSLs mean that flight crews/vehicle operators must stop or remain stopped, immediately inform ATC that the RWSLs are lit, and request further directions. The RWSL system operates independently and controllers do not have any indication when the lights are illuminated. Failure to comply with the instructions to stop when indicated by RWSLs may result in a high-risk collision event. RWSLs are presently installed and operating at these locations: Orlando (MCO), Phoenix (PHX), Houston Inter- continental (IAH), Baltimore-Washington (BWI), Las Vegas (LAS), Charlotte-Douglas (CLT), Los Angeles (LAX), Seattle-Tacoma (SEA), Chicago O’Hare (ORD), Washington Dulles (IAD), LaGuardia (LGA), New York (JFK), Minneapolis-St.
    [Show full text]
  • The Philippines' State Runway Safety Programme
    THE PHILIPPINES’ STATE RUNWAY SAFETY PROGRAMME CIVIL AVIATION AUTHORITY OF THE PHILIPPINES A Component of the STATE SAFETY PROGRAMME FOR PHILIPPINE CIVIL AVIATION Edition 1.0 April 2014 THE PHILIPPINES’ STATE RUNWAY SAFETY PROGRAMME A component of the STATE SAFETY PROGRAMME FOR PHILIPPINE CIVIL AVIATION CONTENTS Page Contents i Amendment Record iii Foreword iv Part 1 INTRODUCTION 1 1.1 General 1 1.2 ICAO Runway Incursion Definition 1 1.3 Runway Incursion Severity Classifications 2 1.4 Factors Considered in Severity Categorization 3 Part 2 RUNWAY SAFETY PROGRAMME STRUCTURE 5 2.1 Runway Safety Office (Office of Runway Safety) 5 2.2 Runway Safety Programme Officers 5 2.3 Local Runway Safety Teams (LRST) 7 2.4 Local Runway Safety Programmes 7 2.5 Significant Activities of the Runway Safety Office 8 2.6 Other Initiatives 8 2.6.1 Runway Safety Educational Materials 8 2.6.2 Runway Safety Reviews 8 2.6.3 Airport Infrastructure and Information 9 2.6.4 Human Factors and Training Initiatives 9 2.6.6 Improving the Safety Culture 10 2.6.7 Changes in Procedures 10 2.6.8 New Technology 11 Part 3 LOCAL RUNWAY SAFETY TEAM 12 3.1 Background 12 3.2 Goals of the Local Runway Safety Team 12 3.3 Terms of Reference 13 3.4 Hot Spots 14 3.5 Action Items 15 3.6 Responsibility for Tasks Associated with Action Items 15 3.7 Effectiveness of Completed Action Items 15 3.8 Education and Awareness 15 3.9 Memorandum Circular AC for LRSTs 16 i Part 4 AIRPORT OPERATIONS 18 4.1 Annex 14 Provisions 18 4.2 Runway Strip Maintenance Programme 18 4.3 Pavement Maintenance 18 4.4
    [Show full text]
  • Human Factors Assessment of Runway Status Lights and Final Approach Runway Occupancy Signal FAA Operational Evaluations at Dallas Ft
    Eighth USA/Europe Air Traffic Management Research and Development Seminar (ATM2009) Human Factors Assessment of Runway Status Lights and Final Approach Runway Occupancy Signal FAA Operational Evaluations at Dallas Ft. Worth and San Diego International Airports Maria Picardi Kuffner Captain Robert Perkins Human Factors Specialist Air Safety Coordinator - Canada MIT Lincoln Laboratory Air Line Pilots Association, International Lexington, MA, USA Ottawa, ON, Canada [email protected] [email protected] Abstract— Runway incursions have been a persistent problem in airport operations for decades, both in the I. INTRODUCTION - RUNWAY INCURSION PROBLEM National Airspace System (NAS) and worldwide. The In descending order of causation, errors committed by pilots, deadliest accident in the history of commercial aviation controllers, or vehicle operators - often because their occurred at Tenerife Airport in the Canary Islands. As situational awareness is lost – result in runway incursions. commercial airliners become larger and airports more Recent Federal Aviation Administration (FAA) data (see congested the potential for major accidents on the airport figure 1) summarizes and analyzes the patterns and trends in surface is expected to increase. Runway Status Lights runway incursions [1]. The data indicate that the most severe (RWSL) have shown promise in precluding this runway incursions can develop quickly and without warning potentiality through demonstrated operational suitability from perfectly safe and routine traffic situations on the airport and measured reductions in runway incursions as cited surface. Severe runway incursions leave little time for independently in an audit by the US Inspector General. corrective action such as a tower controller responding to a RWSL will be deployed to 22 airports in the near future.
    [Show full text]
  • Preventing Runway Collisions
    HindThe ability or opportunity to understand and judge an event or experience after it has occuredight24 PREVENTING EUROCONTROL RUNWAY COLLISION WHAT I HAVE TRIED TO DO by Tzvetomir Blajev A RUNWAY INCURSION, AND NOT PEEING IN YOUR PANTS by Professor Sidney Dekker LEARNING FROM EXPERIENCE by Captain Ed Pooley Winter 2016 Winter HindSight 24 WINTER 2016 6 11 25 What I Learning from Return of have tried experience the JEDI to do Runway incursion That was close, Runway prevention how did that clear a Safety II approach happen? 42 46 53 TABLE OF CONTENTS 4 DG’S KEYNOTE FROM THE BRIEFING ROOM 20 Hold Position! EDITORIAL by Captain Conor Nolan 6 What I have tried to do by Tzvetomir Blajev 22 Runway collision prevention – a first for Europe! by Jean-Marc Flon, Thomas Tritscher & Arnaud Guihard 8 A runway incursion, and not peeing in your pants by Professor Sidney Dekker 25 Understanding of runway safety, you must: return of the JEDI by Dr Anne Issac VIEW FROM ABOVE 29 What goes up must come down by Maciej Szczukowski 11 Learning from experience 32 FAA update by James Fee by Captain Ed Pooley 34 Runway safety II by Jim Krieger CASE STUDY 36 RWY AHEAD by Libor Kurzweil 40 A simple idea – no wind, no clearance, no runway collision! 15 The Missed Opportunity by Bengt Collin by Patrick Legrand 17 Comment 1 Radu Cioponea 18 Comment 2 Captain Ed Pooley 42 Runway clear by Captain David Charles & Captain Andrew Elbert 19 Comment 3 Mike Edwards 46 Runway incursion prevention – a Safety II approach by Maria Lundahl 36 CONTACT US RWY AHEAD The success of this publication depends very much on you.
    [Show full text]
  • Runway Status Lights (RWSL)
    Aerodrome & Ground Environment Briefing Leaflet 16AGEBL01 6 July 2016 Runway Status Lights (RWSL) INTRODUCTION The aim of this Briefing Leaflet is to introduce the core elements of Runway Status Lights (RWSL) as they have been deployed and identify the operational considerations relevant to flight crews. This leaflet has been assembled with information from the FAA, EUROCONTROL and the JCAB. RWSL is an automated system that provides advisory information for flight crews and airport vehicle drivers to indicate if it is unsafe to enter, cross or takeoff from a runway. The system has been implemented on certain runways at a number of busy airports in the United States and Japan and is being implemented at Paris Charles de Gaulle (CDG) airport in France. Designed to reduce the number of runway incursions, the system is comprised of Runway Entrance Lights (RELs) and Takeoff Hold Lights (THLs). The RWSL increases pilot and vehicle operators’ situational awareness by directly providing runway occupancy status through the autonomous illumination of in-pavement lights on runways and taxiways. The concept of operations relies on the ability to warn at least one of the aircraft or vehicles in a conflict scenario and in some cases, provide additional warnings to everyone involved for increased safety. RWSL is designed to be compatible with existing procedures at airports. States implementing RWSLs are working together to ensure harmonization of those procedures specifically relating to RWSL. In addition, provi- sions to be included in the ICAO PANS ATM document will provide international guidance on the harmonization of the RWSL procedures, referred to by ICAO as autonomous runway incursion warning systems (ARIWS), will become applicable in November 2016.
    [Show full text]