FAA Pins Blame For SAN Runway Incursion On Controller | 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-06.23.25

Airborne-NextGen-06.24.25

AirborneUnlimited-06.25.25

Airborne-AffordableFlyers-06.26.25

AirborneUnlimited-06.27.25

Tue, Jan 29, 2008

FAA Pins Blame For SAN Runway Incursion On Controller

Agency Asserts Incident Did Not Compromise Safety

The Federal Aviation Administration has completed its second look at a recent runway incursion incident at San Diego International Airport/Lindbergh Field, and placed the blame on a mistake by an air traffic controller.

As ANN reported, on the evening of January 16 a Hawker Siddeley corporate jet had just landed, and was preparing to taxi clear of the airport's only runway. But a brief mechanical issue required it to stop, still on the runway.

The controller, meanwhile, didn't immediately notice the stop, and cleared Southwest Flight 1626 for takeoff on the same runway. As the Boeing 737 sped toward the smaller jet, the controller noticed the runway wasn't clear, and called for the Southwest crew to abort the takeoff. The crew decided it was too late to safely bring the jet to a stop, and continued the takeoff.

FAA spokesman Ian Gregor says the 737 came within 2,500 feet of the Hawker, 500 feet closer than previously acknowledged. He told the San Diego Union tribune, "There was no collision hazard because Southwest took off a half-mile from where the (other plane) was."

Despite the fact the smaller jet essentially eliminated part of the runway's safety margin for the departing 737, Gregor had stated last week the FAA did not consider the incident a safety breach. The National Air Traffic Controllers Association accused the agency of a cover-up... and the FAA responded by saying it was taking a deeper look.

Now, Gregor says the FAA is continuing its review.

NATCA's San Diego-area chapter president, Melvin Davis, told the Union-Tribune the incident should have raised a red flag with the FAA from the start, and was a symptom of short-staffing which has forced controllers to work overtime. Both the FAA and the union have described the controller, who was not identified, as a longtime employee with a good safety record. The union said he's been working six-day weeks.

NATCA, which is prohibited by law from striking over its contract dispute with the FAA, has responded by working to discredit the FAA among travelers and lawmakers.

Rep. Bob Filner, D-San Diego, is now requesting a congressional investigation into the incursion incident, the first at Lindbergh since late 2003.

FMI: www.san.org, www.natca.org

Advertisement

More News

Airborne 06.30.25: US v ADS-B Misuse, Nat’l STOL Fire, Volocopter Resumes

Also: Netherlands Donates 18 F16s, 2 737s Collide On Ramp, E-7 Wedgetail Cut, AgEagle's 100th In S Korea The Pilot and Aircraft Privacy Act was introduced in the House by Represent>[...]

NTSB Prelim: Piper PA-23

Pilot Also Reported That Due To A Fuel Leak, The Auxiliary Fuel Tanks Were Not Used On June 4, 2025, at 13:41 eastern daylight time, a Piper PA-23, N2109P, was substantially damage>[...]

ANN FAQ: Submit a News Story!

Have A Story That NEEDS To Be Featured On Aero-News? Here’s How To Submit A Story To Our Team Some of the greatest new stories ANN has ever covered have been submitted by our>[...]

Classic Aero-TV: One Man’s Vietnam

From 2023 (YouTube Edition): Reflections on War’s Collective Lessons and Cyclical Nature The exigencies of war ought be colorblind. Inane social-constructs the likes of racis>[...]

Klyde Morris (06.30.25)

What Goes Around, May Yet Come Back Around, Klyde FMI: www.klydemorris.com>[...]

blog comments powered by Disqus



Advertisement

Advertisement

Podcasts

Advertisement

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