On the evening of September 21, 2017, a DJI Phantom 4 collided with a UH-60M Black Hawk helicopter about 300 feet over the water, a mile east of Midland Beach, Staten Island. The drone was destroyed and the helicopter was damaged. Nobody was hurt.
In short
- The NTSB found the cause was the drone pilot's failure to see and avoid the helicopter "due to his intentional flight beyond visual line of sight."
- It named a contributing factor: "the sUAS pilot's incomplete knowledge of the regulations and safe operating practices."
- The lesson is two rules: keep the drone in sight, and give way to crewed aircraft.
What the NTSB found
| Finding | NTSB wording |
|---|---|
| Probable cause | "the failure of the sUAS pilot to see and avoid the helicopter due to his intentional flight beyond visual line of sight" |
| Contributing factor | "the sUAS pilot's incomplete knowledge of the regulations and safe operating practices" |
| Damage | "The helicopter received minor damage, and the sUAS was destroyed." |
The key word is intentional. This wasn't a flyaway. The drone was flown out of sight on purpose, so nobody at the controls could see the helicopter coming.
The rules behind it
| Rule | What it says |
|---|---|
| Visual line of sight (14 CFR 107.31) | You or your visual observer must be able to see the drone throughout the flight, well enough to know where it is and to see and avoid other aircraft. |
| Right of way (14 CFR 107.37) | Your drone must yield to all other aircraft and can't pass close enough to create a collision hazard. |
The camera feed on your controller doesn't count as line of sight. It shows what's in front of the drone, not what's coming at it.
Keep it from being you
- Keep the drone where you can see it with your own eyes, or use a visual observer who can.
- Assume low-flying aircraft are nearby around shorelines, harbors, hospitals, highways and city edges. Helicopters work at drone altitudes.
- If you hear or see an aircraft, descend and give way. Don't wait to see which way it turns.
- Know the rules before the job, not after. The NTSB listed incomplete knowledge of the rules as a factor. Recurrent training exists for this.
How AYNA helps
- A signed pre-flight checklist for every flight, time-stamped and tied to the mission, so you can show what you checked and when.
- Recurrent training tracked for every pilot, with reminders before it comes due, alongside certificates, aircraft registrations, Remote ID and flight records, all checked against Part 107.
- A GO/NO-GO call before you commit. Meridian, AYNA's mission-planning agent, helps you weigh a mission's risk (crew, aircraft, location, weather and airspace) and gives a clear GO/NO-GO call. You mark the risk assessment complete on the mission, and the final call stays with the pilot in command. Sometimes the right call is not to fly.
- The business side too. AYNA One runs your storefront, bookings and Stripe payments, so the platform that keeps you ready also brings in the work.