CEN13CA272 · Cessna 172M
Cessna 172M · Accident: controlled flight into terrain/object (CFIT) on approach
From Thief River Falls, MN to Thief River Falls, MN
Event
- NTSB case
- CEN13CA272
- 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
Cessna 172M
- 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
- N1820V
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Thief River Falls, MNTo Thief River Falls, MN
- 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
- Approach
- 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
- Controlled flight into terrain/object (CFIT)
- 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
- Substantial
Cause areas
- Personnel issues › Psychological
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During the local flight, the pilot noted that the air was getting a little choppy and that he had to increase the wind correction angle in order to fly a normal heading. The pilot flew a normal downwind approach to the airstrip, but the wind correction angle was very large. He aborted the landing and did a full-power climb to a safe altitude. He said that he then elected to land on the east-west blacktop road right in front of the farm rather than the airstrip, which ran north-south. He circled due to traffic on the road and was concentrating on possible traffic as he approached to land. Soon thereafter, the pilot saw wires directly ahead, and he heard the airplane strike a wire; he applied full power, but the airplane descended and impacted a ditch on the right side and nosed over. The airplane sustained substantial wing damage during the nose over. The pilot reported that there were no mechanical malfunctions with the airplane that would have precluded normal operation.
Probable cause
The pilot’s failure to maintain clearance from the power line while on approach to landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN13CA272
- Event ID
- 20130513X13436
- Case number
- CEN13CA272
- 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. 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: a06bd4058523c79aea8e5169d068bda50e913b77032ecc331427c15f8f83e6a9; retrieved 2026-09-15T21:31:59.094Z.