CHI03LA158 · Cessna 152
St Charles Flying Service Cessna 152 · Accident: overrun during takeoff
From 6M06 · Owensville, MO to 3SQ · St. Charles, MO
Event
- NTSB case
- CHI03LA158
- 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 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
- N68778
- Operator
- St. Charles Flying Service
- Onboard fatalities
- Unknown
- Route
- From 6M06 · Owensville, MOTo 3SQ · St. Charles, MO
- 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
- 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 takeoff, delayed
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 sustained substantial damage when it impacted a fence and a ditch after overrunning the runway on takeoff. The pilot reported he taxied the airplane onto the runway centerline and applied full power to the airplane's engine while holding the brakes. The pilot noted he released the brakes and the airplane began to roll. The pilot stated the airplane would not lift-off before 1/2 to 3/4 of the runway was used. The pilot reported he decided to execute an aborted takeoff and reduced engine power to idle and applied brakes. The pilot noted the airplane overran the end of the runway where it impacted a barbwire fence and a ditch. The pilot reported the airplane's loaded weight and center of gravity were within the performance limitations of the airplane at the time of the accident flight. The airplanes weight and balance was calculated using information obtained from data given by the pilot and the airplane was found to be within performance limitations.
Probable cause
The pilots delayed attempt to perform an aborted takeoff and subsequent overrun. Contributing factors to the accident were the fence and the ditch.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI03LA158
- Event ID
- 20030612X00862
- Case number
- CHI03LA158
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2003-06-02.
- API snapshot SHA-256: c0663232b678cf8a2cd12fc794b9ef7ac86a33ccfe8bcd518a6eeebfccd3de7a; retrieved 2026-09-22T09:12:45.219Z.