runway incursion

{{short description|Aviation incident involving the improper presence of an entity on a runway}}

{{Distinguish|Runway excursion}}

{{Worldwide|date=January 2024|2=US}}

{{Use dmy dates|date=September 2024}}

File:2007 San Francisco International Airport runway incursion.png.]]

A runway incursion is an aviation incident involving improper positioning of vehicles or people on any airport runway or its protected area. When an incursion involves an active runway being used by arriving or departing aircraft, the potential for a collision hazard or instrument landing system (ILS) interference can exist. At present, various runway safety technologies and processes are commonly employed to reduce the risk and potential consequences of such an event.

Definition

The internationally-accepted definition of a runway incursion is:{{Cite book|title=Procedures for Air Navigation Services – Air Traffic Management (Doc 4444)|publisher=International Civil Aviation Organization|isbn=978-92-9258-081-0|edition=Sixteenth|publication-date=10 November 2016|pages=Ch.1 p15|chapter=|year=2016}}

{{Blockquote|text=Any occurrence at an aerodrome involving the incorrect presence of an aircraft, vehicle or person on the protected area of a surface designated for the landing and take off of aircraft.|author=International Civil Aviation Organization (ICAO).|source=PANS-OPS Doc 4444, Ch.1|title=}}

In the United States, the FAA classifies runway incursions into 3 types, with 5 levels of severity:{{Cite web|title=Runway Incursions|url=https://www.faa.gov/airports/runway_safety/resources/runway_incursions/|access-date=2021-05-28|website=www.faa.gov|language=en-us}}

class="wikitable"

! colspan="2" |Runway incursion type

Operational incident

|Action of an air traffic controller that results in less than required minimum separation between two or more aircraft, or between an aircraft and obstacles (vehicles, equipment, personnel) on runways or clearing an aircraft to takeoff or land on a closed runway.

Pilot deviation

|Action of a pilot that violates any Federal Aviation Regulation, example: a pilot crosses a runway without a clearance while en route to an airport gate.

Vehicle/pedestrian deviation

|Pedestrians or vehicles entering any portion of the airport movement areas (runways/taxiways) without authorization from air traffic control.

colspan="2" |Runway incursion severity (descending order)
style="text-align: center; background: purple; color: white;" | Accident

|An incursion that resulted in a collision.

style="text-align: center; background: red; color: white;" | Category A

|A serious incident in which a collision was narrowly avoided.

style="text-align: center; background: #ff9100; color: white;" | Category B

|An incident in which separation decreases and there is a significant potential for collision, which may result in a time critical corrective/evasive response to avoid a collision.

style="text-align: center; background: #948d00; color: white;" | Category C

|An incident characterized by ample time and/or distance to avoid a collision.

style="text-align: center; background: grey; color: white;" | Category D

|Incident that meets the definition of runway incursion such as incorrect presence of a single vehicle/person/aircraft on the protected area of a surface designated for the landing and takeoff of aircraft but with no immediate safety consequences.

Analysis

File:Runway incursion between Korean Air Lines Flight 36 and Air China Flight 9018 (1999).oga

Formal study of runway incursions began in the 1980s, following several high-profile near misses and fatal collisions of airliners operating on airport surfaces. One of the earliest reports on the topic was published in 1986 by the American National Transportation Safety Board (NTSB), titled Runway Incursions at Controlled Airports in the United States. Citing examples like the Tenerife airport disaster and the 1972 Chicago–O'Hare runway collision, a special investigation was opened "to investigate selected runway incursions to determine their underlying causes and to recommend appropriate remedial actions."{{Cite book|url=https://www.ntsb.gov/safety/safety-studies/Documents/SIR8601.pdf|title=Runway Incursions at Controlled Airports in the United States|publisher=National Transportation Safety Board|volume=SIR-86-01|location=Washington, D.C.|publication-date=6 May 1986|access-date=2021-05-28}}{{rp|1}} After detailed examination of 26 incursion incidents occurring in 1985, investigators compiled a list of conclusions and safety recommendations. Among their findings were a need for clearer airport signage, improved controller supervision, and revised training procedures for aircrews and controllers. Despite the valuable data generated by the investigation, the NTSB conceded that, at the time, "the magnitude of the runway incursion problem could not be measured because of both incomplete reporting and follow-up investigations by the FAA."{{rp|33}}

Two years later in 1988, the Federal Aviation Administration issued its own report, Reducing Runway Incursions, with the purpose of establishing an integrated program for runway incursion reduction. Its general recommendations included:{{Cite book|url=https://www.ntsb.gov/investigations/AccidentReports/Reports/AAR9105.pdf|title=Aircraft Accident Report: Northwest Airlines Flights 1482 and 299 – AAR-91-05|publisher=National Transportation Safety Board|location=Washington, D.C.|publication-date=25 June 1991}}{{rp|44–45}}

  • Establish a steering committee on runway incursion reduction
  • Accelerate development and field deployment of Airport Movement Area Safety System technology
  • Emphasize the analysis of pilot-related causal factors

In January 1991, the FAA published the first edition of its biennial Runway Incursion Plan (now known as the National Runway Safety Plan). The document introduced organizational and legislative reforms alongside new initiatives to leverage research on human factors, design, technological innovation, and professional development.{{rp|45–46}} In August 1992, however, a US General Accounting Office (GAO) congressional testimony criticized the agency's budgeting, delayed implementation, and inadequate reporting of the initiatives, especially its rollout of ASDE-3 radar and Traffic Collision Avoidance System (TCAS) technologies.{{Cite book|last=Mead|first=Kenneth M.|url=https://www.gao.gov/assets/t-rced-92-90.pdf|title=Additional Actions Needed for Three Safety Programs|work=Testimony Before the Subcommittee on Aviation, Committee on Public Works and Transportation – US House of Representatives|publisher=United States General Accounting Office|location=Washington, D.C.|publication-date=4 August 1992|access-date=2021-05-28}}

Despite newfound emphasis on runway incursion prevention, another fatal accident occurred on 3 December 1990, when eight people were killed after two Northwest Airlines flights collided in fog at Detroit Metropolitan Airport. The NTSB determined the accident's probable cause to be pilot error due to communication errors, inadequate crew resource management (CRM), and disorientation exacerbated by deficient airfield geometry.{{rp|79}} Additionally, the NTSB recommended stricter airport certification requirements under 14 CFR Part 139 in the areas of lighting and conspicuous markings/signage.{{rp|80}}

In 2000, research into incursions at uncontrolled and non-towered airports was conducted by the Aviation Safety Reporting System based on data gathered by interviewing pilots who had experienced a runway incursion. Interviews lasted around 45 minutes to 1 hour, and the data was de-identified for FAA use in developing safety measures.{{Cite journal|title=Reports Needed for ASRS Study|url=https://asrs.arc.nasa.gov/publications/callback/cb_253.htm|journal=Callback – NASA's Monthly ASRS Bulletin|publisher=NASA|issue=253|access-date=2021-05-28}}

In 2005, the FAA assisted ICAO in its creation of a formal, internationally-accepted definition of a runway incursion. The new verbiage was first added to the fourteenth edition of PANS-OPS Doc 4444, but it was not until 1 October 2007, that the FAA finally adopted the ICAO definition. Previously, the FAA had maintained that an incursion only included incidents in which a potential traffic conflict existed. An event without a potential conflict– such as an unauthorized aircraft crossing an empty runway– had been defined as a 'surface incident'.{{cite web|last=Takemoto|first=Paul|date=1 October 2007|title=Fact Sheet – FAA Adopts ICAO Definition for Runway Incursions|url=http://www.faa.gov/news/fact_sheets/news_story.cfm?newsId=9612|url-status=dead|work=Federal Aviation Administration|accessdate=16 October 2019|archiveurl=https://web.archive.org/web/20071009153522/http://www.faa.gov/news/fact_sheets/news_story.cfm?newsId=9612|archivedate=9 October 2007}}

As of 2017, the last fatal runway incursion accident involving a U.S. Federal Aviation Regulations Part 121 air carrier was in 2006.{{cite web |last1=Werfelman |first1=Linda |title=Tracking Runway Incursions |url=https://flightsafety.org/asw-article/tracking-runway-incursions/ |website=Flight Safety Foundation |access-date=20 November 2022 |date=19 October 2017}}

Between 2011 and 2017, 12,857 runway incursions were reported in the United States. Between October 2016 and September 2017, 1,341 were reported. Of these, six were placed in the most serious categories A and B. Four of these were considered ATC incidents, and two were "pilot deviations". Of the 1,341 incidents, 66 percent were caused by pilot deviation, 17 percent were vehicle/pedestrian incidents, 16 percent were air traffic control (ATC) incidents, and 1 percent were "other".

An FAA study of the year ending September 2016, found that of 361 runway incursions attributed to pilot deviation, 27 percent resulted from "pilot failed to hold short of runway as instructed", and 14.7 percent from "pilot failed to hold short of runway". 5 percent of pilot deviations were classified as the pilot failing to comply with an ATC clearance. In 3.4 percent of deviations, the pilot departed without a departure clearance.

The NASA Aviation Safety Reporting Service (ASRS) received 11,168 reports of runway incursions between January 2012 to August 2017, at a rate of approximately 2000 per year. More than 40 percent of reports were filed by general aviation pilots, and 36 percent by air carrier pilots. Factors included situational awareness, communication breakdown, confusion, and distraction.

Technology

The Airport Surface Detection Equipment, Model X (ASDE-X) and the Airport Movement Area Safety System (AMASS) are computerized systems that are intended to alert air traffic controllers to the potential for a runway incursion.

The Honeywell Runway Awareness and Advisory System alerts pilots to the potential for a runway incursion.

List

=List of runway collision accidents with fatalities=

{{Incomplete list|date=November 2024}}

class="wikitable sortable"
DateAccidentFatalitiesInjuriesAircraft/vehiclesAirportReports
2024-01-022024 Haneda Airport runway collision518Airbus A350-900 and De Havilland Canada Dash 8-Q300Haneda Airport, Tokyo[https://jtsb.mlit.go.jp/aircraft/rep-acci/keika20241225-JA722A_JA13XJ.pdf interim] (in Japanese)
2022-11-18

|LATAM Airlines Perú Flight 2213

|3

|40

|Airbus A320neo and airport crash tender

|Jorge Chávez International Airport, Lima

|[https://cdn.www.gob.pe/uploads/document/file/5209692/INFORME%20FINAL%20ACCIDENTE%20DE%20AVIACI%C3%93N%20N%C2%B0%20008-2022.pdf?v=1696022058 final] (in Spanish)

2014-10-20

|Unijet Flight 074P

|4

|1

|Dassault Falcon 50 and snowplow

|Vnukovo International Airport, Moscow

|[https://mak-iac.org/upload/iblock/e12/Final_Report_eng_F-GLSA.pdf final] (in English)

[https://mak-iac.org/upload/iblock/194/Final_Report_rus_F-GLSA.pdf final] (in Russian)

2001-10-082001 Linate Airport runway collision1184McDonnell Douglas MD-87 and Cessna Citation CJ2Linate Airport, Milan[https://web.archive.org/web/20170523101005/http://www.havkom.se/assets/reports/Swedish/FINALREPORTA-1-04Linate.pdf final]
1996-11-19United Express Flight 5925140Beechcraft 1900 and Beechcraft King AirQuincy Regional Airport, Quincy, Illinois[https://www.ntsb.gov/investigations/AccidentReports/Reports/AAR9704.pdf final]
1994-11-22

|1994 St. Louis Airport collision

|2

|8

|McDonnell Douglas MD-82 and Cessna 441

|St. Louis Lambert International Airport, Bridgeton, Missouri

|

1991-02-011991 Los Angeles runway collision35{{efn|name="fatality footnote"|One passenger initially survived the crash, but died 31 days later. The NTSB final report lists 34 fatal injuries, because at that time only deaths within 3 days of an accident count as fatal injuries.}}29Boeing 737-300 and Fairchild Swearingen MetrolinerLos Angeles International Airport, Los Angeles[https://www.ntsb.gov/investigations/AccidentReports/Reports/AAR9108.pdf final]
1990-12-03

|1990 Wayne County Airport runway collision

|8

|10

|McDonnell Douglas DC-9-14 and Boeing 727-200 Advanced

|Detroit Metropolitan Wayne County Airport, Metro Detroit

|[https://www.ntsb.gov/investigations/AccidentReports/Reports/AAR9105.pdf final]

1984-10-11

|Aeroflot Flight 3352

|178

|2

|Tupolev Tu-154B-1 and maintenance vehicles

|Omsk Airport, Omsk

|

1983-12-20

|Ozark Air Lines Flight 650

|1

|2

|McDonnell Douglas DC-9-31 and snowplow

|Sioux Falls Regional Airport, Sioux Falls

|[https://www.ntsb.gov/investigations/AccidentReports/Reports/AAR8501S.pdf final]

1983-12-071983 Madrid Airport runway collision9330Boeing 727-200 and McDonnell Douglas DC-9-32Madrid–Barajas Airport, Madrid[https://www.transportes.gob.es/recursos_mfom/pdf/E1B8DECA-3E15-4ADA-8760-903046830B83/14257/1983_043_044_A_English.pdf final]
1982-08-14

|1982 Sukhumi Dranda Airport runway collision

|11

|Unspecified

|Tupolev Tu-134A and Let L-410M Turbolet

|Sukhumi Babushara Airport, Sukhumi

1978-02-11

|Pacific Western Airlines Flight 314

|43

|≥5

|Boeing 737-200 and snowplow{{efn|name="lack of collision footnote"|The aircraft and the snowplow did not make contact, but the 737 crashed while performing an evasive go-around manoeuvre due to inadvertent thrust reverser deployment.}}

|Cranbrook/Canadian Rockies International Airport, Cranbrook

|[https://web.archive.org/web/20140519113553/http://lessonslearned.faa.gov/PWA314/Cranbrook_B737_AccidentReport.pdf final]

1977-03-27Tenerife airport disaster58361Boeing 747-100 and Boeing 747-200Los Rodeos Airport, Tenerife[https://www.transportes.gob.es/organos-colegiados/ciaiac/publicaciones/informes-relevantes/accidente-ocurrido-el-27-de-marzo-de-1977-aeronaves-boeing-747-matricula-ph-buf-de-klm-y-aeronave-boeing-747-matricula-n736pa-de-panam-en-el-aeropuerto-de-los-rodeos-tenerife-islas-canarias final] (in Spanish)
[https://www.faasafety.gov/files/gslac/courses/content/232/1081/finaldutchreport.pdf final] (in English)
1974-04-18

|Court Line Flight 95

|1

|1

|BAC One-Eleven and Piper PA-23 Aztec

|London Luton Airport, Luton

|[http://www.aaib.gov.uk/publications/formal_reports/3_1975_g_ayde_and_g_axmj.cfm final]

1972-12-20

|1972 Chicago–O'Hare runway collision

|10

|17

|McDonnell Douglas DC-9-31 and Convair CV-880

|O'Hare International Airport, Chicago

|[https://ntsb.gov/investigations/AccidentReports/Reports/AAR7315.pdf final]

1936-06-24

|Carlos Gardel death

|17

|6

|Two Ford Trimotors

|Olaya Herrera Airport

|

=Category A runway incursion incidents=

==United States==

{{See also|List of US aircraft near-miss incidents since 2023}}

The following table lists Category A runway incursion incidents in the United States since 2001.{{cite web|url=https://www.asias.faa.gov/apex/f?p=100:28|title=FAA Runway Safety Office - Runway Incursions (RWS)|publisher=FAA|accessdate=2024-11-07}} This table only includes incidents in which all involving planes were operating under FAR Part 121 and Part 129, and were investigated by both FAA and NTSB. Note that the Category rank of Air Canada Flight 759 incident in 2017 was "N/A" according to the FAA Runway Safety database, so it is not in the following table.{{cite web|url=https://www.asias.faa.gov/apex/f?p=100:30:::NO::AP_BRIEF_RPT_VAR:AUS-M-2023%2F02%2F04-0001-OI-001|title=RWS Batch Brief|publisher=FAA}}

class="wikitable sortable"
DateAirportFlightsAircraftClosest proximityRefs
2023-02-04Austin–Bergstrom International Airport, Austin, TXSouthwest Airlines Flight 708 and FedEx Express Flight 1432Boeing 737-700 and Boeing 767-300ERF150 to 170 feet (46 to 52 meters)[https://www.ntsb.gov/investigations/AccidentReports/Reports/AIR2402.pdf NTSB]
[https://data.ntsb.gov/Docket/?NTSBNumber=DCA23FA149 docket]
[https://www.asias.faa.gov/apex/f?p=100:30:::NO::AP_BRIEF_RPT_VAR:AUS-M-2023%2F02%2F04-0001-OI-001 FAA]
2017-02-15San Francisco International Airport, San Francisco, CACompass Airlines Flight 6081 and Virgin America Flight 920ERJ 170-200 and Airbus A320-214Vertical: about 125 feet (38m)[https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/94762/pdf NTSB]
[https://data.ntsb.gov/Docket?ProjectID=94762 docket]
[https://www.asias.faa.gov/apex/f?p=100:30:::NO::AP_BRIEF_RPT_VAR:SFO-M-2017%2F02%2F15-0007-1 FAA]
2015-02-17O'Hare International Airport, Chicago, ILAmerican Eagle Flight 3084 and United Express Flight 3710Embraer ERJ-145LR and Bombardier CL-600-2C10Between center: about 94 feet (29m)
Between wingtips: 20 to 30 feet (6 to 9 meters)
[https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/90743/pdf NTSB]
[https://data.ntsb.gov/Docket?ProjectID=90743 docket]
[https://www.asias.faa.gov/apex/f?p=100:30:::NO::AP_BRIEF_RPT_VAR:PGLTORD15004 FAA]
2011-08-08O'Hare International Airport, Chicago, ILChautauqua Airlines Flight 5021 and Trans States Airlines Flight 3367Embraer ERJ-135 and Embraer ERJ-145Vertical: within 125 feet (38m)
Horizontal: within 350 feet (107m)
[https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/81436/pdf NTSB]
[https://data.ntsb.gov/Docket?ProjectID=81436 docket]
[https://www.asias.faa.gov/apex/f?p=100:30:::NO::AP_BRIEF_RPT_VAR:ORDT11E014 FAA]
2007-07-11Fort Lauderdale-Hollywood Airport, Fort Lauderdale, FLUnited Airlines Flight 1544 and Delta Air Lines Flight 1489Airbus A320 and Boeing 757Lateral: 230 feet (70m)[https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/66190/pdf NTSB]
[https://www.asias.faa.gov/apex/f?p=100:30:::NO::AP_BRIEF_RPT_VAR:PSOTFLL07005 FAA]
2007-05-26San Francisco International Airport, San Francisco, CARepublic Airlines Flight 4912 and Skywest Airlines Flight 5741Embraer 170 and Embraer 120Tower's estimate: 300 feet
Skywest crew's estimate: 30 to 50 feet
RPA4912 crew's estimate: 150 feet
[https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/65865/pdf NTSB]
[https://www.asias.faa.gov/apex/f?p=100:30:::NO::AP_BRIEF_RPT_VAR:SFOT07E001 FAA]
2006-03-21O'Hare International Airport, Chicago, ILLufthansa Flight 437 and Chautauqua Flight 7826Airbus A319 and Embraer ERJ 145EP100 feet (30m)[https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/63376/pdf NTSB]
[https://www.asias.faa.gov/apex/f?p=100:30:::NO::AP_BRIEF_RPT_VAR:ORDT06E004 FAA]
2005-06-09General Edward Lawrence Logan International Airport, Boston, MAAer Lingus Flight 132 and US Airways Flight 1170Airbus A330-301 and Boeing 737-300171 feet (52m)[https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/61662/pdf NTSB]
[https://data.ntsb.gov/Docket?ProjectID=61662 docket]
[https://www.asias.faa.gov/apex/f?p=100:30:::NO::AP_BRIEF_RPT_VAR:BOST05E002 FAA]

See also

Footnotes

{{notelist}}

References

{{reflist}}