FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI03LA216 · Cessna 172H

18 Jul 2003 · Isle, MN, United States

Cessna 172H · Accident: loss of control in flight during initial climb

From Isle Private Airport (MY72) to Isle Private Airport (MY72)

Report a problem

Event

NTSB case
CHI03LA216
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
1 · 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 172H

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
N1606F
Operator
Unknown
Onboard fatalities
Unknown
Route
From Isle Private Airport (MY72), Isle, MNTo Isle Private Airport (MY72)
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
Initial climb
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
Loss of control in flight
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
Stall; Tree(s)
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 › Airspeed, inadequate

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane was substantially damaged when it impacted trees and terrain during initial climb from a grass airstrip. The pilot attempted to depart with full fuel and three passengers on a local flight. A passenger aboard the airplane stated that the airplane banked to the right and then descended into the trees during the climb. Visual meteorological conditions prevailed at the time of the accident with an approximate density altitude of 2,339 feet mean sea level and 50 percent humidity. Damage to the airplane was consistent with a nose-down, low-speed impact. Examination of the wreckage revealed no anomalies with the flight control system and engine. The airplane was not equipped with shoulder harnesses, and the seat belts possessed stitching, which was not consistent with a manufactured product. The right rear passenger seat belt stitching separated at the lower attach point.

Probable cause

The pilot's failure to maintain adequate airspeed which resulted in a stall. The trees, high density altitude, and the soft field were additional factors.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI03LA216
Event ID
20030722X01163
Case number
CHI03LA216
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
  • 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, coordinates. 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: 085673e05d9d331f72ed3ab3a073e1b78db510235b8d2da4e9e90537d86be18d; retrieved 2026-09-20T19:02:13.175Z.
  • Corrected after a review of the NTSB narrative, which states these values explicitly: damage. The narrative states "The airplane was substantially damaged when it impacted trees and terrain during initial climb from a grass airstrip."