CEN21LA119 · Cessna 172
Cessna 172 · Accident: low altitude operation/event while maneuvering
From Garfield County Regional Airport (KRIL) to an unrecorded destination
Event
- NTSB case
- CEN21LA119
- 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
- Event fatalities
- Unknown
- 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
Cessna 172
- Aircraft type
- Cessna 172
- Category
- Airplane
- 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
- N4376Q
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Garfield County Regional Airport (KRIL), Rifle, COTo not recorded
- Aircraft age
- About 50 years (built 1971)
- 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
- Maneuvering · low-altitude flying
- 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
- Low altitude operation/event
- 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
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Environmental issues › Physical environment
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was conducting a local sightseeing flight when the airplane impacted high-tension transmission wires. The airplane came to rest about 600 ft past the wires, and the upper 2-foot section of the vertical stabilizer and rudder were separated and located about 100 ft from the wires.
Postaccident examination revealed no malfunctions or anomalies of the airplane or engine that would have precluded normal operation. The circumstances of the accident are consistent with the pilot’s failure to avoid powerlines while flying at low altitude.
Probable cause
The pilot’s failure to avoid powerlines while flying at low altitude.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN21LA119
- Event ID
- 20210201102580
- Case number
- CEN21LA119
- 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: investigation status, cause areas. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 0e33f7f6826167cb2fb802e9c890dbba2dc77fbf5d97e42030e164ae8fb4fa92; retrieved 2026-09-16T13:35:21.479Z.