BFO93LA152 · Piper PA-28
Piper PA-28 · Accident: on ground/water collision with object during takeoff
From I11 to 3SQ · ST CHARLES, MO
Event
- NTSB case
- BFO93LA152
- 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
Piper PA-28
- Aircraft type
- Piper PA-28
- 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
- N56975
- Operator
- Arthur Chuck
- Onboard fatalities
- Unknown
- Route
- From I11To 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 · rejected 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
- On ground/water collision with object
- 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
- Pilot in command › Directional control, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
ACCORDING TO THE PILOT, AS THE AIRPLANE WAS ACCELERATING FOR TAKEOFF, IT BECAME AIRBORNE BRIEFLY, THEN IT SETTLED BACK ONTO THE RUNWAY. HE REPORTED THAT HE ABORTED THE TAKEOFF, BUT THE AIRPLANE EXITED THE END OF THE RUNWAY. ACCORDING TO THE FAA, THE PILOT WAS TAKING OFF FOR THE FIRST TIME WITH A PASSENGER AT THIS AIRPORT AND WAS NOT USING FLAPS. REPORTEDLY, THE PILOT STATED THAT HE DID NOT HAVE ENOUGH AIRSPEED TO CONTINUE THE TAKEOFF, SO HE ABORTED THE TAKEOFF ABOUT TWO-THIRDS OF THE WAY DOWN THE 2000 FOOT LONG RUNWAY. THE AIRPLANE THEN VEERED TO THE LEFT AND STRUCK THE RUNWAY LIGHTS. THE PILOT REPORTED THAT THERE WAS NO MECHANICAL MALFUNCTION, AND THE ACCIDENT COULD HAVE BEEN PREVENTED IF THE RUNWAY WAS LONGER AND A SHORTFIELD TAKEOFF WAS EXECUTED.
Probable cause
THE PILOT'S DELAY IN ABORTING THE TAKEOFF, AND HIS FAILURE TO MAINTAIN DIRECTIONAL CONTROL DURING THE ABORTED TAKEOFF.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record BFO93LA152
- Event ID
- 20001211X13329
- Case number
- BFO93LA152
- 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: e031f5850ec3952c5ed733198738065645009bee9b1d109fdd9c68ed0e49ac34; retrieved 2026-09-23T01:40:43.935Z.