The FAA has constructed a Flight Risk Assessment Tool (FRAT) that is user-friendly and free to use online. One of the ...

Per flight data recorder data, the Black Hawk’s last recorded altitude was 278 feet. Earlier in the flight, Lobach reported an altitude of 300 feet, while Eaves about 40 seconds later indicated ...

Homendy also indicated that Flight 5342 saw the Black Hawk in the moments before the collision. “Yes, there was an indication, and that is, we see a pitch up of the aircraft.

The Army has said the Black Hawk crew was highly experienced, and accustomed to the crowded skies around the nation's capital. The helicopter was on a check flight that night when the pilot was ...

A preliminary analysis of the flight data and voice recorder on board a Black Hawk helicopter leading up to the collision with a commercial flight over Washington, DC, on January 29, indicated the ...

The Black Hawk helicopter may have been flying with “bad data” and didn’t hear all air traffic control instructions before colliding with a passenger plane, officials said.

A U.S. Army Black Hawk crew may not have heard critical air traffic control messages instructing it to fly behind the commercial regional jet it ultimately collided with midair at Reagan National ...

The National Transportation Safety Board on Friday afternoon is set to release additional details on the Jan. 29 midair collision near Reagan National Airport.

The NTSB said Army Black Hawk crew may not have heard a message to "pass behind" the D.C.-bound passenger plane before the Jan. 29 midair crash over the Potomac River.

National Transportation Safety Board Chairwoman Jennifer Homendy told reporters that the recording from the Black Hawk helicopter cockpit suggested an incomplete radio transmission may have left ...

A three-person Army Black Hawk helicopter crew may not have received accurate altitude readings in their cockpit or an important transmission from air traffic control before the deadly crash with ...