Comair 5191 flight crew failed to use available cues to determine location during takeoff

Citation

(2008), "Comair 5191 flight crew failed to use available cues to determine location during takeoff", Aircraft Engineering and Aerospace Technology, Vol. 80 No. 1. https://doi.org/10.1108/aeat.2008.12780aab.010

Comair 5191 flight crew failed to use available cues to determine location during takeoff

Comair 5191 flight crew failed to use available cues to determine location during takeoff

The National Transportation Safety Board (NTSB) recently determined the probable cause of the Comair flight 5191 accident in Lexington, Kentucky was the flight crew's failure to use available cues and aids to identify the aeroplane's location on the airport surface during taxi and their failure to cross check and verify that the aeroplane was on the correct runway before takeoff. Contributing to this accident were the flight crew's non- pertinent conversation during taxi, which resulted in loss of positional awareness and the Federal Aviation Administration's failure to require that all runway crossings be authorised only by specific air traffic control clearances.

“This accident was caused by poor human performance,” said NTSB Chairman Mark V. Rosenker. “Forty- nine lives could have been saved if the flightcrew had been concentrating on the important task of operating the aeroplane in a safe manner.”

On 27 August 2006, about 6:07 a.m., Comair flight 5191, a Bombardier CRJ- 100, (N431CA) crashed upon takeoff from Blue Grass Airport in Lexington, Kentucky. The flight crew was instructed to take off from runway 22, an air carrier runway that is 7,003ft long. Instead, the flight crew lined up the aeroplane on runway 26, a 3,501ft long runway, and began the takeoff roll. Runway 26 crosses runway 22 about 700ft south of the runway 22 threshold. Of the 47 passengers and three crewmembers onboard, 49 were fatally injured and one (the first officer) received serious injuries. Impact forces and a postcrash fire destroyed the aeroplane.

As a result of this accident, the safety Board made the following recommendations: to the Federal Aviation Administration:

^• Require that all 14 Code of Federal Regulations (CFR) Part 91K, 121, and 135 operators establish procedures requiring all crewmembers on the flight deck to positively confirm and cross check the aeroplane's location at the assigned departure runway before crossing the hold short line for takeoff.

^• Require that all CFR Part 91K, 121, and 135 operators install on their aircraft cockpit moving map displays or an automatic system that alerts pilots when a takeoff is attempted on a taxiway or a runway other than the one intended.

^• Require that all airports certified under 14 CFR Part 139 implement enhanced taxiway centreline markings and surface painted holding position signs at all runway entrances.

^• Prohibit the issuance of a takeoff clearance during an aeroplane's taxi to its departure runway until after the aeroplane has crossed all intersecting runways.

^• Revise Federal Aviation Administration Order 7110.65, “Air Traffic Control,” to indicate that controllers should refrain from performing administrative tasks, such as the traffic count, when moving aircraft are in the controller's area of responsibility.

The Safety Board reiterated two previously issued recommendations to the FAA: amend 14 CFR Section 91.129(i) to require that all runway crossings be authorised only by specific air traffic control clearance, and ensure that US pilots, US personnel assigned to move aircraft, and pilots operating under 14 CFR Part 129 receive adequate notification of the change.

Amend Federal Aviation Administration Order 7110.65, “Air Traffic Control,” to require that, when aircraft need to cross multiple runways, air traffic controllers an issue explicit crossing instruction for each runway after the previous runway has been crossed.

Previously issued recommendations to the FAA resulting from this accident include: require that all 14 CFR Part 121 operators establish procedures requiring all crewmembers on the flight deck to positively confirm and cross-check the aeroplane's location at the assigned departure runway before crossing the hold-short line for takeoff.

Require that all 14 CFR Part 121 operators provide specific guidance to pilots on the runway lighting requirements for takeoff operations at night.

Work with the National Air Traffic Controllers Association to reduce the potential for controller fatigue by revising controller work-scheduling policies and practices to provide rest periods that are long enough for controllers to obtain sufficient restorative sleep and by modifying shift rotations to minimise disrupted sleep patterns, accumulation of sleep debt, and decrease cognitive performance.

Develop a fatigue awareness and countermeasures training program for controllers and for personnel who are involved in the scheduling of controllers for operational duty that will address the incidence of fatigue in the controller workforce, causes of fatigue, effects of fatigue on controller performance and safety, and the importance of using personal strategies to minimise fatigue. This training should be provided in a format that promotes retention, and recurrent training should be provided at regular intervals.

Require all air traffic controllers to complete instructor-led initial and recurrent training in resource management skills that will improve controller judgement, vigilance, and safety awareness.

Earlier this year, the Board issued the following recommendation to the National Air Traffic Controller Association: work with the Federal Aviation Administration to reduce the potential for controller fatigue by revising controller work-scheduling policies and practices to provide rest periods that are long enough for controllers to obtain sufficient restorative sleep and by modifying shift rotations to minimise disrupted sleep patterns, accumulation of sleep debt, and decreased cognitive performance.

A synopsis of the Board's report, including the probable cause and recommendations, is available on the NTSB's, web site: www.ntsb.gov, under “Board Meetings”.