Airbus AS 350 B2 and Unknown UNKNOWN mid-air collision near Los Angeles, California, December 5, 2019
On December 5, 2019 at about 3:15 am local time, 2 aircraft, Airbus AS 350 B2 (N71HD) and Unknown UNKNOWN (UNK), were involved in a mid-air collision near Los Angeles, California. No one was hurt; 3 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
an inflight collision with a hard object of polycarbonate construction, with size and features consistent with that of a small UAS (drone).
an inflight collision with a hard object of polycarbonate construction, with size and features consistent with that of a small UAS (drone).
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- December 5, 2019 · about 3:15 am local time
- Place
- Los Angeles, California · map
- Type
- Incident · mid-air collision
- Injuries
- No one was hurt; 3 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft 1
- Airbus AS 350 B2 No Series, built 2004
- Registration
- N71HD · registry record · serial 3849
- Damage
- Minor damage
- Flight
- Aerial observation flight · general aviation rules (Part 91)
- Aircraft 2
- Unknown UNKNOWN
- Registration
- UNK · no longer on the register · serial unk
- Damage
- Not recorded
- Flight
- Flight · rules the NTSB did not record
The NTSB's narrative for the Airbus AS 350 B2 final · quoted from the NTSB record
The helicopter was operating under the provisions of 14 CFR Part 91 as an electronic news gathering flight, under visual flight rules, within Class G airspace. The pilot heard a noise which he first thought might be a bird strike, and made a precautionary landing. Post flight examination led the pilot and operator to believe they collided with a drone. A search by ground and electronic methods did not locate a drone. Laboratory examinations indicated that the shape and dimensions of the damage to the horizontal stabilizer were consistent with the configuration and dimensions of many popular small drones. A small mark inside the larger round dent was consistent with the propeller shaft diameter of common small drones. Infrared examination revealed material transfer of polycarbonate polymer, which is a commonly used construction material of small drones. Although many items which could come in contact with the helicopter as ground FOD, are manufactured of polycarbonate (e.g. safety glasses, light lenses), the shape and configuration of the indentations and scuffs were very consistent with a small drone. The reported collision occurred in Class G airspace, but higher than the 14 CFR Part 107 regulatory maximum of 400 feet agl for small drones. A provision in Part 107 allows for operations above 400 feet if the drone is within 400 feet laterally of a tall structure. Downtown Los Angeles was approximately ¼ mile away from the collision site, therefore, although the altitude and location are not authorized for drones without a waiver, it is not inconceivable that a drone operator could have been operating near the tall buildings, and deviated or exceeded the lateral requirements. Although no drone was located, preventing complete certainty, all the available evidence was consistent with a collision with a small UAS.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The NTSB's narrative for the Unknown UNKNOWN final · quoted from the NTSB record
The helicopter was operating under the provisions of 14 CFR Part 91 as an electronic news gathering flight, under visual flight rules, within Class G airspace. The pilot heard a noise which he first thought might be a bird strike, and made a precautionary landing. Post flight examination led the pilot and operator to believe they collided with a drone. A search by ground and electronic methods did not locate a drone. Laboratory examinations indicated that the shape and dimensions of the damage to the horizontal stabilizer were consistent with the configuration and dimensions of many popular small drones. A small mark inside the larger round dent was consistent with the propeller shaft diameter of common small drones. Infrared examination revealed material transfer of polycarbonate polymer, which is a commonly used construction material of small drones. Although many items which could come in contact with the helicopter as ground FOD, are manufactured of polycarbonate (e.g. safety glasses, light lenses), the shape and configuration of the indentations and scuffs were very consistent with a small drone. The reported collision occurred in Class G airspace, but higher than the 14 CFR Part 107 regulatory maximum of 400 feet agl for small drones. A provision in Part 107 allows for operations above 400 feet if the drone is within 400 feet laterally of a tall structure. Downtown Los Angeles was approximately ¼ mile away from the collision site, therefore, although the altitude and location are not authorized for drones without a waiver, it is not inconceivable that a drone operator could have been operating near the tall buildings, and deviated or exceeded the lateral requirements. Although no drone was located, preventing complete certainty, all the available evidence was consistent with a collision with a small UAS.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record for the Airbus AS 350 B2 from the NTSB's investigation tables, in plain English
What happened, in order
- Midair collision during enroute defining event
The NTSB's findings
- cause Environmental issues › Physical environment › Object/animal/substance › Aircraft › Effect on equipment
- Aircraft › Aircraft structures › Empennage structure › Horizontal stabilizer › Damaged/degraded
The aircraft
- Seats: 6
- Landing gear: fixed
- Operator: Helinet Aviation Services Llc
The flight
- Departed from: KBUR Burbank CA
- Destination: Los Angeles CA
Weather at the time
- Light: night
- Temperature: 0°F (-18°C), dew point 0°F (-18°C)
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 2 |
The factual record for the Unknown UNKNOWN from the NTSB's investigation tables, in plain English
What happened, in order
- Midair collision during enroute defining event
The NTSB's findings
- cause Not determined › Not determined › (general) › (general) › Unknown/Not determined
The aircraft
- Landing gear: fixed
- Not recorded
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.