FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI01LA311 · Cessna 150M

9 Sept 2001 · South St. Paul, MN, United States

Cessna 150M · Accident: in flight collision with terrain/water during takeoff

From South St Paul Municipal Airport/Richard E Fleming Field (SGS) to an unrecorded destination

Report a problem

Event

NTSB case
CHI01LA311
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 150M

Aircraft type
Cessna 150
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
N6142K
Operator
Unknown
Onboard fatalities
Unknown
Route
From South St Paul Municipal Airport/Richard E Fleming Field (SGS), South St. Paul, MNTo not recorded
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
Takeoff
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 terrain/water
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 › Directional control, not maintained

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

NTSB narrative

The airplane sustained substantial damage during takeoff when it settled back to the runway and veered off the left side of the runway. The solo student pilot was intending to practice takeoffs and landings. The pilot reported he initiated the takeoff. After normal lift off and climb to approximately 20 feet AGL, the aircraft drifted to the left and struck the ground at the left edge of the runway. The aircraft ran off of the runway onto the grass paralleling the runway until the nose landing gear folded and the aircraft stopped. The pilot reported there were no problems with the flight controls or aircraft The inspection of the airplane revealed no airworthiness issues. The student pilot had a total of 18 flight hours.

Probable cause

The student pilot failed to maintain directional control. A factor was his lack of total flight experience.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI01LA311
Event ID
20010910X01913
Case number
CHI01LA311
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: 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: ea0bfa613107fea807cbec86ce1be6afd7d3e61767967f319d88cf8ead20491f; retrieved 2026-09-22T11:34:29.774Z.