avia.wikisort.org - Event

The 2007 San Francisco International Airport runway incursion occurred around 1:36 p.m. PDT on May 26, 2007 when SkyWest Airlines (operating as United Express) Flight 5741, an Embraer EMB 120 Brasilia turboprop aircraft, nearly collided with Republic Airways (operating as Frontier Airlines) Flight 4912, an Embraer 170 Regional Jet, at the intersection of Runways 1L and 28R at San Francisco International Airport (SFO).[1]

2007 San Francisco International Airport runway incursion
Republic Airlines Flight 4912 · SkyWest Airlines Flight 5741

Incident
Date	May 26, 2007 (2007-05-26)
Summary	Runway incursion due to ATC error
Site	San Francisco International Airport, California, US 37.62072°N 122.37452°W / 37.62072; -122.37452
Total injuries	0
Total survivors	27 (all)
First aircraft
The Embraer 170 Regional Jet aircraft involved in the incursion.
Type	Embraer 170 Regional Jet
Operator	Republic Airlines (o/a Frontier Airlines)
IATA flight No.	YX4912
ICAO flight No.	RPA4912
Call sign	BRICKYARD 4912
Registration	N872RW
Passengers	11
Crew	4
Second aircraft
The Embraer EMB 120 Brasilia turboprop aircraft involved in the incursion.
Type	Embraer EMB 120 Brasilia
Operator	SkyWest Airlines (o/a United Express)
ICAO flight No.	SKW5741
Call sign	SKYWEST 5741
Registration	N232SW
Passengers	9
Crew	3

There were no injuries to occupants and no damage to either aircraft.[2]^: 6[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]

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 Airlines 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 Airlines aircraft was cleared for takeoff.[3][2]^: 3 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 Airlines flight lifted off and overflew it. The initial FAA tower report estimated that the aircraft missed colliding by 300 feet (91 m), but the SkyWest crew estimated the distance as 30 ft (9.1 m) to 50 ft (15 m).[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][7] Of the previous 15 runway incursions at SFO between 2001 and 2007, none had been more serious than Category C,[8] which is defined as a situation in which "[s]eparation decreases but there is ample time and distance to avoid a potential collision."[7]

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]^: 6[2]^: 2 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][9]

SFO and AMASS

Runway safety and prevention of runway incursions has been a priority concern for both the FAA and NTSB;[7][10][11][12] it has been on the NTSB's annual list of "Most Wanted Improvements" continuously since 1990.[13][14][15]

The Airport Movement Area Safety System (AMASS) is an airport surveillance radar system that is designed to detect potential runway conflicts and alert controllers.[16] 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.[17][16] 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.[18] The NTSB believes that AMASS is insufficient to prevent runway incursions.[19]

Aftermath

In the end, N872RW continued to fly before it began operating under Delta Express. The EMB-120 involved would later be transferred to Menard Inc. under the registration of N957M. In 2018, the aircraft was stored.

See also

• Runway incursion
• 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 SFO in 2017

References

---