NTSB: Drone Pilot Caused Crash
A drone pilot crashed his Phantom 4 small unmanned aircraft system into a U.S. Army helicopter in September because he was flying it out of his line of sight, the National Transportation Safety Board concluded today.
The drone pilot was a hobbyist, not a commercial operator who had passed an airman’s knowledge test to be certified by the Federal Aviation Administration. The accident occurred 2.5 miles from where he was operating the controls.
The Army pilot, whose Black Hawk helicopter was part of a presidential movement to New York for a United Nations meeting, saw the drone and tried to avoid it but didn’t have enough time.
In addition to flying beyond line of sight, the drone pilot was operating during official night conditions, in an area regularly used by helicopters and in restricted airspace. This demonstrated a “lack of understanding of the potential hazard of collision with other aircraft,” the NTSB report said.
The agency also criticized the drone pilot’s use of a mobile application with limited capability for alerting pilots to temporary flight restrictions. “Sole reliance on advisory functions of a non-certified app is not sufficient to ensure that correct airspace information is obtained,” the report said. The pilot also did not have Internet access on his mobile device to check for TFRs before the flight.
The operator didn’t know he had crashed until the agency contacted him. “The sUAS pilot reported that he lost signal with the aircraft and assumed it would return home as programmed,” the NTSB said. “After waiting about 30 minutes, he assumed it had experienced a malfunction and crashed in the water.”
The pilot purchased another drone five days after the accident.