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-Unlimited-04.23.24

Airborne-Unlimited-04.24.24 Airborne-FltTraining-04.25.24

Airborne-Unlimited-04.26.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-Term (04.28.24): Airport Marking Aids

Airport Marking Aids Markings used on runway and taxiway surfaces to identify a specific runway, a runway threshold, a centerline, a hold line, etc. A runway should be marked in ac>[...]

Aero-News: Quote of the Day (04.28.24)

"It is extremely difficult, if not impossible, for manned aircraft to see a drone while conducting crop-enhancing and other aerial applications at low altitudes and high speeds. We>[...]

ANN's Daily Aero-Linx (04.28.24)

Aero Linx: The Skyhawk Association The Skyhawk Association is a non-profit organization founded by former Skyhawk Pilots which is open to anyone with an affinity for the A-4 Skyhaw>[...]

Aero-News: Quote of the Day (04.29.24)

“The T-54A benefits from an active Beechcraft King Air assembly line in Wichita, Kansas, where all required METS avionics and interior modifications are installed on the line>[...]

ANN's Daily Aero-Linx (04.29.24)

Aero Linx: Aerostar Owners Association The Association offers the Aerostar Owner a unique opportunity to tap an invaluable source of information concerning the care and feeding of >[...]

blog comments powered by Disqus



Advertisement

Advertisement

Podcasts

Advertisement

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