CHI04CA286 · Cessna C-150J
Cessna C-150J · Accident: overrun during landing
From Green Castle Airport (IA24) to an unrecorded destination
Event
- NTSB case
- CHI04CA286
- 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 C-150J
- Aircraft type
- Cessna C-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
- N61111
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Green Castle Airport (IA24), Oxford, IATo 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
- 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
- Overrun
- 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 › Aborted landing, not performed
- Pilot in command › Proper glidepath, not attained
- Pilot in command › Proper touchdown point, exceeded
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 damaged when it overran the runway, struck a road embankment, and nosed over. The student pilot stated that he was practicing landings and was performing a simulated emergency landing when the accident happened. He stated that when he was on the downwind leg of the traffic pattern he reduced the engine power to idle. He stated that he turned toward the runway, and applied 40 degrees of flaps. He stated that he touched down about 3/4 of the way down the runway and applied full braking action. He stated that the airplane became airborne again after cresting the uphill grade of the runway and then the airplane "quickly settled back down." He stated that he was about 75 feet from the end of the runway at this point and attempted to turn the airplane to the left to avoid hitting the roadway at the end of the runway. He stated that the airplane went straight ahead striking the road embankment and nosed over on it's top. The student pilot listed no failures relating to the airplane or systems.
Probable cause
The student pilot's failure to attain a proper glidepath which resulted in exceeding the proper touchdown point. An additional cause was his failure to abort the landing. The embankment was a factor.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI04CA286
- Event ID
- 20041028X01716
- Case number
- CHI04CA286
- 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, 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: 5f741731b3b0d40cec89133484b9416e18c7fc34c67cff37e56332c2100fd4fb; retrieved 2026-09-22T06:40:27.608Z.