DEN03LA018 · Enstrom F-28C
Enstrom F-28C · Accident: in flight collision with object during landing
From 2V2 · Longmont, CO to Morrison, CO
Event
- NTSB case
- DEN03LA018
- 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
- Accident
- 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
Enstrom F-28C
- Aircraft type
- Enstrom F-28
- 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
- N552CS
- Operator
- David Copp
- Onboard fatalities
- Unknown
- Route
- From 2V2 · Longmont, COTo Morrison, CO
- 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
- 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
- Landing
- First occurrenceThe 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
- In flight collision with object
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Wire, transmission
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command › Clearance, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot said his helicopter was approaching a landing area, located just east of a restaurant, from the south, in night visual meteorological conditions. During the approach, the pilot could not see the lighted flag on top of the restaurant, thus he could not determine the wind direction or velocity for landing. He executed a go around and began maneuvering so that he could approach the landing area from the east. The pilot said that at the "northern most point of the go around, a tail rotor strike was felt." The tail rotor struck telephone lines along the north side of a road. The pilot immediately put the helicopter down hard into a ditch alongside the road, breaking the left skid, crushing the right skid and fuselage upward, bending and twisting the main rotor blades, and bending the tail rotor blades. An examination of the helicopter's systems revealed no anomalies.
Probable cause
the pilot not maintaining clearance from the telephone lines during landing. Factors contributing to the accident were the pilot not being able to see the telephone lines, the low altitude, and the dark night.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN03LA018
- Event ID
- 20021203X05550
- Case number
- DEN03LA018
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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 2002-11-23.
- API snapshot SHA-256: 5c5d93b1fb1c06e791ccae4d24ef3941c4275cb5536903bd75e4ec7a10542c7e; retrieved 2026-09-21T19:34:30.759Z.