NTSB Investigating Runway Incursion At SFO | Aero-News Network
Aero-News Network
RSS icon RSS feed
podcast icon MP3 podcast
Subscribe Aero-News e-mail Newsletter Subscribe

Airborne Unlimited -- Most Recent Daily Episodes

Episode Date

Airborne-Monday

Airborne-Tuesday

Airborne-Wednesday Airborne-Thursday

Airborne-Friday

Airborne On YouTube

Airborne-Unlimited-05.20.24

Airborne-NextGen-05.21.24

Airborne-Unlimited-05.15.24 Airborne-AffordableFlyers-05.16.24

Airborne-Unlimited-05.17.24

Mon, Jun 11, 2007

NTSB Investigating Runway Incursion At SFO

FAA Calls Incident An "Operational Error"

The National Transportation Safety Board is investigating a runway incursion at San Francisco International Airport two weeks ago, in which two Embraer regional aircraft may have come within 50 feet of each other on intersecting runways.

On May 26, about 1:30 pm, a controller cleared SkyWest Airlines flight 5741, an Embraer 120 Brasilia turboprop (type shown above), to land on runway 28R. Apparently forgetting about the arriving airplane, the same controller then cleared Republic Airlines flight 4912, an Embraer 170, to take off from runway 1L, which intersects runway 28R, according to the NTSB.

After the SkyWest airliner touched down, the Airport Movement Area Safety System (AMASS) sounded in the tower, and the controller told the SkyWest flight crew to "Hold, Hold, Hold" in an attempt to stop the aircraft short of runway 1L. The SkyWest crew applied maximum braking -- that resulted in the airplane stopping in the middle of runway 1L. 

Realizing the aircraft was traveling too fast to stop, the captain of Republic Airlines flight 4912 took control of the aircraft from the first officer, and initiated an immediate takeoff.

According to the crew of SkyWest 5741, the Republic Airlines aircraft (type shown below) overflew theirs by 30 to 50 feet. "The initial FAA tower report estimated the aircraft missed colliding by 300 feet," the NTSB report states.

Following the incident, the controller involved -- certified as an SFO controller since 1999 -- was decertified and required to complete additional training. The controller has since been recertified by SFO management.

The Federal Aviation Administration has categorized the incident as an operational error.

FMI: Read The Preliminary Report

Advertisement

More News

Samson Sky Hits the Wind Tunnel

Improvements Stack as Brand Readies for Mass Production Samson Sky updated followers on its flying car progress, describing some of the travails of the wind tunnel as they get clos>[...]

ANN's Daily Aero-Term (05.22.24): LAHSO

LAHSO An acronym for “Land and Hold Short Operation.” These operations include landing and holding short of an intersecting runway, a taxiway, a predetermined point, or>[...]

Aero-FAQ: Dave Juwel's Aviation Marketing Stories -- ITBOA BNITBOB

Dave Juwel's Aviation Marketing Stories ITBOA BNITBOB ... what does that mean? It's not gibberish, it's a lengthy acronym for "In The Business Of Aviation ... But Not In The Busine>[...]

ANN's Daily Aero-Linx (05.19.24)

Aero Linx: Space Medicine Association (SMA) The Space Medicine Branch was founded in 1951 as the first constituent organization of the Aerospace Medical Association (AsMA). In 2006>[...]

ANN's Daily Aero-Term (05.19.24): Back-Taxi

Back-Taxi A term used by air traffic controllers to taxi an aircraft on the runway opposite to the traffic flow. The aircraft may be instructed to back-taxi to the beginning of the>[...]

blog comments powered by Disqus



Advertisement

Advertisement

Podcasts

Advertisement

© 2007 - 2024 Web Development & Design by Pauli Systems, LC