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-04.29.24

Airborne-NextGen-04.30.24

Airborne-Unlimited-05.01.24 Airborne-AffordableFlyers--05.02.24

Airborne-Unlimited-05.03.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

ANN's Daily Aero-Term (05.01.24): Say Altitude

Say Altitude Used by ATC to ascertain an aircraft's specific altitude/flight level. When the aircraft is climbing or descending, the pilot should state the indicated altitude round>[...]

ANN's Daily Aero-Linx (05.01.24)

Aero Linx: European Air Law Association (EALA) EALA was established in 1988 with the aim to promote the study of European air law and to provide an open forum for those with an int>[...]

Classic Aero-TV: Korean War Hero Twice Reborn

From 2023 (YouTube Version): The Life, Death, Life, Death, and Life of a Glorious Warbird In 1981, business-owner Jim Tobul and his father purchased a Chance-Vought F4U Corsair. Mo>[...]

Airborne 04.29.24: EAA B-25 Rides, Textron 2024, G700 Deliveries

Also: USCG Retires MH-65 Dolphins, Irish Aviation Authority, NATCA Warns FAA, Diamond DA42 AD This summer, history enthusiasts will have a unique opportunity to experience World Wa>[...]

Airborne Affordable Flyers 05.02.24: Bobby Bailey, SPRG Report Cards, Skydive!

Also: WACO Kitchen Bails, French SportPlane Mfr to FL, Dynon-Advance Flight Systems, Innovation Preview Bobby Bailey, a bit of a fixture in sport aviation circles for his work with>[...]

blog comments powered by Disqus



Advertisement

Advertisement

Podcasts

Advertisement

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