NTSB: Multiple data sources lost in Northwest A320 over-flight

Washington DC
Source:
This story is sourced from Pro
See more Pro news »

New information released by the US National Transportation Safey Board (NTSB) yesterday regarding a Northwest Airlines Airbus A320 that was out of radio communication for more than an hour and overflew its destination shows that three independent sources of data on the event were lost or mishandled.

After the event pilots told investigators they were using personal laptops on the 21 October flight from San Diego to Minneapolis.

Missing were 17 of the 30 minutes captured by the Flight 188's cockpit voice recorder (CVR). According to the NTSB, the CVR was activated three additional times after the aircraft's engines were shut down in Minneapolis at 2120h that evening.

Investigators say the aircraft was powered up at 2154h, 2305h and again at 0203h the next morning. When power is turned on, the CVRs begin recording at the start of the 30 minute window. The recorders will power down automatically five minutes later if the engines are not started, which was the case that evening.

"It appears the airplane's electrical network was re-energized three separate times after the engine was shutdown, before the CVR was removed or deactivated," said the NTSB's cockpit voice recorder specialist in a factual report issued 16 December. "Each time, the CVR started and recorded 5 minutes, causing more than half of the recording to be overwritten."

Airline officials will typically deactivate the CVR circuit breaker as soon as possible to preserve data. Northwest Airlines assistant chief pilot, Todd Luebke, the first airline official to board the plane when it landed in Minneapolis, recalled a complicated scenario in the cockpit as FBI, federal air marshals and TSA officials boarded the aircraft first to evaluate potential criminal or terrorist activity.

"While we never want to interfere with the duties of other agencies, this delay prevents the CVR circuit breakers from being pulled in a timely fashion and in this case, it was at least a causal factor in the flight documents being gathered," writes Luebke in his 6 November statement.

The extra 17 minutes of data would have included discussions held from the time the aircraft had descended below 11,000ft on approach to the airport. In the remaining 13 minutues, which began when the aircraft was below 1,000ft for landing, investigators noted that "discernable" conversations were "related to the operation the airplane" and did not include a discussion of the communications blackout.

As to the missing flight documents, which include the flight plan, the pilots in their statements mentioned that they thought that Luebke had gathered the paperwork when he entered the cockpit or that it was discarded. However, Luebke reported that he did not "see any signs of the flight paperwork which would have been my reminder" to retain the documents.

"To my surprise (the pilots) had nearly completed their post-flight duties including flight bags packed", Luebke says of his entry to the cockpit. "I don't know if the crew retained (the paperwork) or due to their distraught state discarded them as we normally do on domestic, uneventful flights." Luebke notes that, per regulation, the documents only need to be kept for international flights or for accident flights.

Earlier in the flight, the first officer had deleted the eight ACARS messages that dispatchers had sent to the crew in an attempt to get them to contact air traffic controllers.

"After they were back in radio contact, the (first officer) said he went to 'pull up' (automatic terminal information service) info and noticed there were several messages on the lower screen," the NTSB states in its documentation of the first officer interview. "All he saw were the headings of the messages which said 'contact ATC' or 'ATC is looking for you'. The (first officer) said he inadvertently pushed the 'delete all' button which erased all the messages." ACARS messages are retained by service provider, Arinc, however.

Northwest in its response to the incident began "targeted discussions" of the events emphasizing corrective messages, according to the carrier's submission to the NTSB. The effort does not appear to include address errors in retaining the data.-