FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI99LA087 · Socata TB 9 TAMPICO TB 9 TAMPI

6 Feb 1999 · Cahokia, IL, United States

Socata TB 9 TAMPICO TB 9 TAMPI · Accident: overrun during takeoff

From Decatur Airport (DEC) to St Louis Downtown Airport (CPS)

Report a problem

Event

NTSB case
CHI99LA087
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

Socata TB 9 TAMPICO TB 9 TAMPI

Aircraft type
Socata TB-9
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
N544PC
Operator
Unknown
Onboard fatalities
Unknown
Route
From Decatur Airport (DEC), Decatur, ILTo St Louis Downtown Airport (CPS)
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
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 › Planning/decision, improper

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

NTSB narrative

The newly certificated private pilot was cleared for a touch and go. The controller then stated '...make this a full stop I'll call your departure roll.' The pilot stated he did not understand what the controller meant, but he did not question the clearance. He stated he intended on making a full stop and turning off onto the taxiway. When nearing the end of the runway the controller cleared the pilot for takeoff. The pilot applied power then realized he did not have sufficient runway remaining for a takeoff. He reduced power, but the airplane continued off the end of the runway where it contacted a hole in the terrain. The ATC Handbook states the phraseology 'stop-and-go' should be used for spacing and sequencing traffic.

Probable cause

the pilot's improper decision to initiate the takeoff with insufficient runway remaining. A factor associated with the accident was pilot's failure to obtain clarification from the controller regarding the clearance.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI99LA087
Event ID
20001205X00133
Case number
CHI99LA087
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: 29dada0091cd3be7e5bcef24d43ac14b5d5395156c75d132c415950fa80c7824; retrieved 2026-09-22T15:54:45.101Z.