FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN15CA074 · Cessna 150L

16 Nov 2014 · New Buffalo, MN, United States Possible conflict

Cessna 150L · Accident: loss of control on ground during landing

From Flying Cloud Airport (FCM) to FCE · Buffalo, MN

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
CEN15CA074
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 150L

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
N6985G
Onboard fatalities
Unknown
Route
From Flying Cloud Airport (FCM), Eden Prairie, MNTo FCE · Buffalo, 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
Landing
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
Loss of control on ground
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision

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

NTSB narrative

The airplane veered off the runway during landing while on an instructional flight with a student pilot and a flight instructor. During the landing, the airplane's left main landing gear wheel contacted snow on the runway, which resulted in the airplane veering into a snowbank along the runway edge and impacting the ground with the right wing. The airplane sustained substantial damage when the right wing contacted the ground. The flight instructor reported that there was no mechanical malfunction/failure with the airplane that would have precluded normal airplane operation.

Probable cause

The student pilot's failure to maintain directional control and the flight instructor's delayed remedial action during landing. Contributing was the snow on the runway surface.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN15CA074
Event ID
20141209X70253
Case number
CEN15CA074
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: e681d01e1aedc51e8bc4d230e46dda8481e94aa3d8c76e084b2c85c42020d0b6; retrieved 2026-09-16T01:58:29.157Z.