More Blue Grass Runway Confusion | 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

Sat, Nov 25, 2006

More Blue Grass Runway Confusion

Controllers Warn Saratoga Before Takeoff On Wrong Runway

The FAA says another aircraft nearly departed the wrong runway at Lexington's Blue Grass Airport on November 9.

In an eerie repeat of the Comair Flight 5191 tragedy, a Piper Saratoga cleared for takeoff on the airport's longer runway 22 lined up instead on runway 26. One of the two tower controllers on duty alerted the pilot, who then taxied to the correct runway and made a safe departure.

The controller handling the flight filed a report using NASA's Aviation Safety Reporting System (ASRS). ASRS is a safety improvement program allowing those involved to anonymously report incidents without fear of FAA enforcement action.

A copy of that report was subsequently released by the National Air Traffic Controllers Association (NATCA). A NATCA spokesman says the incident highlights the value of having two controllers on duty.

Earlier this summer Comair Flight 5191 attempted to depart runway 26 after cleared for departure on 22. That attempt ended in disaster as the regional jet crashed off the departure end the runway killing 49 of the 50 people aboard. There was only one controller on duty the morning of that accident.

FAA rules at the time required more than one duty controller, but staffing shortages at Blue Grass led management to ignore that mandate for overnight hours when traffic was typically light. NATCA made much of the fact in the media following the accident suggesting had two controllers been on duty it might not have occurred.

Runway 26 was closed at the time of the Comair accident which happened before dawn on August 27. There were several taxiway and runway construction projects underway that may have led to the crew's confusion. Construction on runway 26 has since been completed and that runway is operational.

An FAA spokesperson told the Louisville Courier-Journal the agency won't formally investigate, but it would like to understand the incident. The NTSB says it will look into the situation as part of its larger Flight 5191 investigation.

The airport's managers say the FAA recently inspected its runway and taxiway signage and markings finding them all in compliance with federal standards.

FMI: www.faa.gov

Advertisement

More News

ANN's Daily Aero-Linx (05.02.24)

Aero Linx: Model Aeronautical Association of Australia MAAA clubs are about fun flying, camaraderie and community. For over 75 years, the MAAA has been Australia’s largest fl>[...]

ANN's Daily Aero-Term (05.02.24): Touchdown Zone Lighting

Touchdown Zone Lighting Two rows of transverse light bars located symmetrically about the runway centerline normally at 100 foot intervals. The basic system extends 3,000 feet alon>[...]

Aero-News: Quote of the Day (05.02.24)

“Discovery and innovation are central to our mission at Virgin Galactic. We’re excited to build on our successful record of facilitating scientific experiments in subor>[...]

ANN FAQ: Contributing To Aero-TV

How To Get A Story On Aero-TV News/Feature Programming How do I submit a story idea or lead to Aero-TV? If you would like to submit a story idea or lead, please contact Jim Campbel>[...]

NTSB Final Report: Cirrus Design Corp SR20

Student Pilot Reported That During Rotation, “All Of A Sudden The Back Of The Plane Kicked To The Right..." Analysis: The student pilot reported that during rotation, “>[...]

blog comments powered by Disqus



Advertisement

Advertisement

Podcasts

Advertisement

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