FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN18FA011 · Cessna 172M M

13 Oct 2017 · Ramsey, MN, United States

Cessna 172M M · Accident: low altitude operation/event while maneuvering

From Princeton Municipal Airport (PNM) to Princeton Municipal Airport (PNM)

Report a problem

Event

NTSB case
CEN18FA011
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
2 · 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 M

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
N7CF
Operator
Unknown
Onboard fatalities
Unknown
Route
From Princeton Municipal Airport (PNM), Princeton, MNTo Princeton Municipal Airport (PNM), Princeton, MN
Aircraft age
About 42 years (built 1975)
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

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Physical environment
  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

After takeoff, the pilot proceeded south until reaching the Mississippi River when he proceeded to fly along the river at a low altitude. As the airplane approached a bend in the river, the pilot entered a shallow left turn to follow the river. The airplane subsequently struck power lines spanning the river that were located about 200 yards beyond the bend. Ground-based video footage and witness statements indicated that the airplane was at or below the height of the trees lining both sides of the river shortly before encountering the power lines. One witness initially thought that the pilot intended to fly under the power lines due to the low altitude of the airplane. Several witnesses also noted that the sound of the engine seemed normal and steady before the accident. A post-recovery examination of the airplane did not reveal any anomalies consistent with a preimpact failure or malfunction.

The power lines were below the level the trees on either side of the river. Red aerial marker balls were installed on the power lines at the time of the accident. Weather conditions were good at the time of the accident; however, the sun was about 9° above the horizon and aligned with the river. It is likely that the position of the sun in relation to the power lines hindered the pilot's ability to identify the hazard as he navigated the bend in the river at low altitude. In addition, the location of the power lines relative to the river bend minimized the reaction time to avoid the lines.

FAA regulations prohibit operation of an aircraft less than 500 feet above the surface in uncongested areas unless approaching to land or taking off, and at least 1,000 feet from obstacles in congested areas. They also prohibit operations in a reckless manner that endanger the life or property of another. Based on the available information, the airplane was less than 100 feet above the river and within 400 feet of the residences located along the river during the final portion of the flight.

The pilot's flight instructor described the pilot as "reckless" because of his habit of low-level flying.

While the location of the bend in the river and the position of the sun relative to the power lines may have hindered the pilot's ability to see and avoid the lines, it was the pilot's decision to operate the airplane along the river at a low altitude contrary to applicable regulations and safety of flight considerations that caused the accident.

Probable cause

The pilot's decision to fly along the river at a low altitude contrary to applicable regulations and safety of flight considerations which resulted in the impact with the power lines. Contributing to the accident was the pilot's inability to see the and avoid the power lines due to their proximity to a bend in the river and the position of the sun at the time of the accident.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN18FA011
Event ID
20171013X22853
Case number
CEN18FA011
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: 14557d6c5179a74f3b17e1ac439390ac26a1c920448d3d1554d68d7972821236; retrieved 2026-09-15T06:21:17.891Z.