CHI00LA202 · Cessna 152
Cessna 152 · Accident: loss of control on ground/water during landing
From Grand Forks International Airport (GFK) to Y37
Event
- NTSB case
- CHI00LA202
- 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
- 0
- 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 152
- Aircraft type
- Cessna 152
- 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
- N69066
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Grand Forks International Airport (GFK), Grand Forks, NDTo Y37
- 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
- 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 on ground/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
During landing rollout the aircraft departed the prepared runway surface to the left side and nosed-over. The pilot reported that during landing rollout the left brake had locked up and he could not control the aircraft with opposite rudder and/or braking. Post-accident investigation revealed black tire-skid marks, deposited from the right main and nose landing gear, leading up to the wreckage of the aircraft. The brakes, tires, and wheel assemblies were inspected and no anomalies were found. An operational test of the brake system was conducted and no anomalies were noted. No anomalies were found with the aircraft or its flight control systems that would preclude the normal operation of the aircraft.
Probable cause
directional control not being maintained by the pilot during landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI00LA202
- Event ID
- 20001212X21393
- Case number
- CHI00LA202
- 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: 4e41113b3306d7e8121b05c52e0f092a46ee8d8d3689d73dbcb936760d21c1e7; retrieved 2026-09-22T12:41:41.256Z.