Black Box From DC Air Disaster Reveals Head-Turning ‘Discrepancy’

Black Box From DC Air Disaster Reveals Head-Turning ‘Discrepancy’

Investigators analyzing the black box data from the recent aircraft crash have uncovered a critical discrepancy that may provide key insights into the cause of the devastating collision.

Early findings from the inquiry into the fatal accident involving an American Airlines CRJ-700 jet and a U.S. Army Black Hawk helicopter near Washington, D.C.—which claimed 67 lives—indicate a notable difference in altitude at the time of impact, as reported by DailyMail.com.

The jet’s flight recorder registered an altitude of approximately 325 feet, while control tower data suggested the helicopter was flying at 200 feet. This 125-foot discrepancy is now under close scrutiny by the National Transportation Safety Board (NTSB) as part of its investigation into the tragic event.

Authorities are considering multiple factors that could have led to the conflicting altitude readings. These include possible reporting errors, whether the helicopter exceeded its designated 200-foot altitude restriction, and the potential impact of the crew’s night-vision goggles on situational awareness.

Air traffic control warnings issued to both aircraft, along with the plane’s last-second evasive maneuvers, are being reviewed to gain a clearer understanding of the circumstances leading up to the crash.

“That’s what our job is, to figure that out,” NTSB member Todd Inman stated, according to DailyMail.com, displaying some frustration when pressed by reporters about the altitude inconsistency. He noted that within the NTSB, there were differing opinions on whether the discrepancy should have been disclosed before more details were available, as reported by the outlet.

Investigators are working to align the varying altitude readings with information from the helicopter’s black box, though its analysis has been delayed due to water damage sustained when it fell into the Potomac River.

“We currently don’t have the readout from the Black Hawk, so we cannot provide information about the altitude at which the helicopter was flying,” Inman explained. He further remarked that “obviously an impact occurred, and I would say when an impact occurs, that is typically where the altitude of both aircraft were at the moment.”

Addressing the emotional toll of the tragedy, Inman reflected on interactions with victims’ families: “Some wanted to give us hugs. Some are just mad and angry,” he said. “They are just all hurt. And they still want answers, and we want to give them answers.”

“Our job is to find the facts,” he continued. “More importantly, our job is to make sure this tragedy doesn’t happen again – regardless of what anyone may be saying.”

Brice Banning, the NTSB investigator in charge, acknowledged the complexity of the situation. “This is a complex investigation,” he said. “There are a lot of pieces here. Our team is working hard to gather this data.”

Banning also described the final moments captured by the aircraft’s two black boxes, which recorded both cockpit audio and flight data.

“The crew had a verbal reaction,” Banning informed reporters, adding that the flight data recorder indicated “the airplane beginning to increase its pitch.”

“Sounds of impact were audible about one second later, followed by the end of the recording,” he concluded.

Emergency responders confirmed on Sunday that 55 of the 67 victims from the crash—America’s deadliest since 2001—had been identified. Officials are preparing for a “lifting operation” on Monday to recover the wreckage from the river.

Although comprehensive investigations typically take a year or more, authorities expect the NTSB to release a preliminary report within the next 30 days.

A firefighter present at the scene told reporter Brian Entin that he and his colleagues were “emotionally wiped out” after witnessing the devastation firsthand. He described the water as “actually very clear” and recounted how, with the aid of flashlights, they “saw horrible things when they arrived.”

Subscribe to Lib Fails

Don’t miss out on the latest issues. Sign up now to get access to the library of members-only issues.
jamie@example.com
Subscribe