2007 San Francisco International Airport runway incursion
Template:Short description Template:Use mdy dates Script error: No such module "Infobox".Template:Template otherScript error: No such module "Check for unknown parameters". The 2007 San Francisco International Airport runway incursion occurred around 1:36 p.m. PDT on May 26, 2007, when SkyWest Airlines Flight 5741, an Embraer EMB 120 Brasilia turboprop aircraft, nearly collided with Republic Airways Flight 4912, an Embraer 170 Regional Jet, at the intersection of Runways 1L and 28R at San Francisco International Airport (SFO).[1]
There were no injuries to occupants and no damage to either aircraft.[2]Template:Rp[3] Federal Aviation Administration officials described the runway incursion as the most serious incident of its kind in at least a decade, and the National Transportation Safety Board carried out an investigation into the incident.[4][5][6]
Aircraft
The first aircraft involved was an Embraer ERJ 170-100SU, registered as N872RW, MSN 17000143, that was manufactured in 2006. It was equipped with two General Electric CF34-8E5 engines.[7][8]
The second aircraft involved was an Embraer EMB-120ER Brasilia, registered as N232SW, MSN 120306.[9]
Incident
The SkyWest aircraft was arriving at SFO after a flight from Modesto, California, and was cleared to land on Runway 28R. At the same time, the Republic Airways aircraft, bound for Los Angeles, was instructed to taxi into position and hold on the intersecting Runway 1L. As the landing SkyWest aircraft passed the runway threshold, the Republic Airways aircraft was cleared for takeoff.[3][2]Template:Rp Local procedures and FAA Order 7110.65 require the local controller to wait until the landing aircraft has passed through the intersection before clearing an aircraft for takeoff on one of the intersecting runways.
Approximately 27 seconds later the Airport Movement Area Safety System issued an aural warning of an imminent collision, and the local controller instructed the SkyWest aircraft to stop, transmitting, "uh, sky-, skywest uhh fifty seven forty one HOLD HOLD HOLD." The SkyWest aircraft stopped in the intersection of Runways 1L and 28R, while the Republic Airways flight lifted off and overflew it. The initial FAA tower report estimated that the aircraft missed colliding by Script error: No such module "convert"., but the SkyWest crew estimated the distance as Script error: No such module "convert"..[3]
Investigation
The Federal Aviation Administration (FAA) classified the incident as a Category A runway incursion, the most serious type. Category A events are those in which "[s]eparation decreases and participants take extreme action to narrowly avoid a collision, or the event results in a collision."[4][10] Of the previous 15 runway incursions at SFO between 2001 and 2007, none had been more serious than Category C,[11] which is defined as a situation in which "[s]eparation decreases but there is ample time and distance to avoid a potential collision."[10]
Commenting on the seriousness of the incident, National Transportation Safety Board (NTSB) spokesman Ted Lopatkiewicz noted that "We investigate probably just a handful (of incursions) a year."[4] The NTSB's investigation was completed in November 2007, concluding that the controller had failed to provide adequate separation between the two aircraft.[2]Template:Rp[2]Template:Rp FAA spokesman Ian Gregor said, "This wasn't a procedural issue, this was caused by a good controller with a lot of experience making a mistake," adding that since the incursion the controller, who had over 20 years of experience, was recertified.[4][12]
SFO and AMASS
Script error: No such module "Labelled list hatnote". Runway safety and prevention of runway incursions has been a priority concern for both the FAA and NTSB;[10][13][14][15] it has been on the NTSB's annual list of "Most Wanted Improvements" continuously since 1990.[16][17][18]
The Airport Movement Area Safety System (AMASS) is an airport surveillance radar system that is designed to detect potential runway conflicts and alert controllers.[19] SFO was selected by the FAA for the first test installation of the AMASS system, where it became operational in June 2001 before its rollout to 40 airports around the U.S.[20][19] AMASS is designed to provide an alert 15 seconds before aircraft reach the conflict point. The system performed as designed in the incident at SFO,[3] though it did not alert in time to prevent the runway incursion.[21] The NTSB believes that AMASS is insufficient to prevent runway incursions.[22]
See also
Script error: No such module "Side box".
- 2005 Logan Airport runway incursion - A narrowly avoided runway incursion at Boston, Massachusetts caused by ATC error
- Air Canada Flight 759 - A narrowly avoided runway incursion at San Francisco International Airport in 2017
References
<templatestyles src="Reflist/styles.css" />
- ↑ Script error: No such module "citation/CS1".
- ↑ a b c d Script error: No such module "citation/CS1".
- ↑ a b c d Script error: No such module "citation/CS1".
- ↑ a b c d Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ a b c Script error: No such module "citation/CS1".
- ↑ Inside Bay Area – Serious runway incursions rare in area Template:Webarchive
- ↑ Script error: No such module "citation/CS1".
- ↑ FAA – Office of Runway Safety – Runway Safety Home Template:Webarchive
- ↑ runway incursion
- ↑ Script error: No such module "citation/CS1".
- ↑ House Transportation and Infrastructure Committee : Press Release :: Aviation Subcommittee Holds Hearing on NTSB Safety Priorities Template:Webarchive
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ a b Script error: No such module "citation/CS1".
- ↑ Committee on Transportation and Infrastructure, House of Representatives
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
Script error: No such module "Check for unknown parameters".
Template:United Airlines Holdings Template:Aviation accidents and incidents in 2007 Template:Aviation accidents and incidents in the United States in the 2000s
- Pages with script errors
- Pages with broken file links
- Runway incursions
- Aviation accidents and incidents involving the Embraer E-Jet family
- Accidents and incidents involving the Embraer EMB 120 Brasilia
- San Francisco International Airport
- Aviation accidents and incidents in the United States in 2007
- Aviation accidents and incidents caused by air traffic controller error
- Airliner accidents and incidents in California
- 2007 in California
- May 2007 in the United States
- United Airlines accidents and incidents