NOTAMs, Signage Proper At LEX, Airport Says

Gemini Sparkle

Key Takeaways:

  • The airport board defends its safety measures, claiming construction NOTAMs, signage, and airport configuration were proper and obvious to pilots.
  • The board asserts the Comair crew should have noticed their error and aborted, alleging they lacked full attention, and notes hundreds of preceding flights navigated the airport correctly.
  • Crucial evidence, including cockpit voice and flight data recorder information, along with the full tower-flight exchange, remains unreleased by the NTSB and FAA.
See a mistake? Contact us.

The airport board admits that construction work was underway but it claims that NOTAMs were properly created and distributed and that signs leading to Runway 22, the main 7,000-foot runway that the flight had been cleared to, met all standards and that configuration of the taxiways and runways at the Airport were safe, open and obvious to any pilots exercising ordinary care. The airport board further alleges that the Comair crew should have noticed they were on the wrong runway in time to abort the takeoff. The statement also points out that hundreds of flights, including two airliners that immediately preceded Flight 5191, had no trouble getting to the right runway in the week prior to the accident. The defense also claims the crew didnt have its full attention on the tasks at hand while taxiing, an allegation that could become clearer when some crucial evidence is released by the FAA and NTSB. The NTSB hasnt released the cockpit voice and flight data recorder information yet (despite numerous requests by the media) and, while it has confirmed that the lone air traffic controller on duty that morning cleared the flight to the correct runway, the FAA hasnt released the full exchange between the tower and Flight 5191.

Sign-up for newsletters & special offers!

Get the latest stories & special offers delivered directly to your inbox

SUBSCRIBE

Please support AVweb.

It looks like you’re using an ad blocker. Ads keep AVweb free and fund our reporting.
Please whitelist AVweb or continue with ads enabled.