DCA20IA034 · Airbus AS 350 B2
Helinet Aviation Services Airbus AS 350 B2 and Unknown · Incident: midair collision en route
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- DCA20IA034
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Incident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Aircraft 1 · Airbus AS 350 B2
- Aircraft type
- Airbus AS-350
- Category
- Helicopter
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N71HD
- Operator
- Helinet Aviation Services
- Onboard fatalities
- Unknown
- Route
- From Hollywood Burbank/Bob Hope Airport (KBUR), Burbank, CATo Los Angeles, CA
- Aircraft age
- About 15 years (built 2004)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- En route
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Midair collision
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Aircraft 2 · Unknown
- Category
- Helicopter
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- UNK
- Operator
- unk
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Unknown
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- En route
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Midair collision
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Not recorded
Cause areas
- Environmental issues › Physical environment
- Not determined › Not determined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
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.
Probable cause
an inflight collision with a hard object of polycarbonate construction, with size and features consistent with that of a small UAS (drone).
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DCA20IA034
- Event ID
- 20191205X95005
- Case number
- DCA20IA034
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2019-12-05.
- API snapshot SHA-256: 382b6e79fe825547902983c8902002492eb2d817aaab688dc9f5390bd55c6ba4; retrieved 2026-09-13T18:34:11.732Z.