Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

February 6, 1999 · Socata TB 9 Tampico TB 9 Tampi · N544PC

Cahokia, IL

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
February 6, 1999
Injury Outcomes
No injuries (1 uninjured)
Location
Cahokia, IL
Aircraft
Socata TB 9 Tampico TB 9 Tampi
Tail Number
N544PC
Injuries
None
Aircraft Damage
Substantial
NTSB Number
CHI99LA087

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.

NTSB 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.

Full Narrative

On February 6, 1999, at 1541 central standard time, a Socata TB 9 Tampico, N544PC, operated by a newly certificated private pilot collided with a hole in the terrain after overrunning the runway during an aborted takeoff. The private pilot was operating on Runway 30R (3,800'x75') at the St. Louis Downtown-Parks Airport, Cahokia, Illinois, at the time of the accident. The pilot was not injured. The airplane was substantially damaged. The 14 CFR Part 91 solo instructional local flight was operating in visual meteorological conditions without a flight plan. The flight originated from the St. Louis Downtown-Parks Airport, Cahokia, Illinois. The pilot stated that upon returning from a cross country flight he requested a touch and go landing. The air traffic control tower controller cleared him for a touch and go. While on short final the controller then stated that she would call the roll- out. The pilot stated that he was not sure what this meant, but since the controller was busy, and he was taught not to interrupt controllers, he continued the landing. The pilot stated that during his landing roll he heard another airplane being cleared for a touch and go on the same runway so he decided to taxi off the runway. He stated that when nearing the end of the runway at a speed of about 25 knots, he received a transmission from the tower clearing him to takeoff. The pilot reported that as a student he was "...taught to trust ATC [air traffic control] - to do as instructed. So I proceeded to give the plane power and communicated to tower, Parks 44 clear to take-off." He stated he soon realized that there was "...no way I could safely take off - I just didn't have enough runway to take off." The pilot reported that he reduced the power and applied the brakes; however, the airplane continued off the end of the runway into the grass. He stated that as the airplane slowed it veered to the left at which point the left wing tipped, scraping the ground. The right main gear then contacted a hole and the right wing lowered to contact with the terrain. According to the transcript of ATC communications, the pilot was initially cleared to fly a left base for runway 30L. This clearance was later changed instructing the pilot to fly a right base for runway 30R. The controller then cleared N544PC for a touch and go and to make right closed traffic. The next transmission received from the controller was "parks forty four make this a full stop I'll call your departure roll." The pilot responded, "parks forty four is going to make this a full stop and you call my departure roll." The controller then stated, "parks forty four you can keep rolling ah runway three zero right cleared for takeoff." The pilot responded, "three zero left ah three zero right cleared for takeoff parks forty four." Chapter 3, Section 8, of the Air Traffic Control Handbook (Order 7110.65L) states, "Establish the sequence of arriving and departing aircraft by requiring them to adjust flight or ground operation, as necessary, to achieve proper spacing." An example of the phraseology to be used is "CLEARED: TOUCH-AND-GO or STOP- AND-GO or LOW APPROACH." The pilot reported, "Upon reflection I know that even though tower instructed me to take-off I should have went with what I felt to be the correct thing to do. I should have taxied off the runway then communicated to tower my reasons for doing so."

Flight

Event TypeAccident
Event Time15:41 CST
Nearest AirportSt. Louis Downtown-Parks (0nm)
Runway30R
Runway Length3990 ft
Runway Width75 ft
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftSocata TB 9 Tampico TB 9 Tampi
Tail NumberN544PC
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320 · Reciprocating · 160
Seats4

People & Injuries

Injury SummaryNo injuries (1 uninjured)
Fatal0
Serious0
Minor0
Uninjured1
Total1
Crew 1Age 22 · Second Class

Conditions

ConditionsVMC
LightDaylight
Wind40° @ 11 kt
Visibility10 sm
CeilingBroken clouds 7500 ft
Temperature / Dew Point54 / 37 C
Altimeter30.00 inHg
Observation Time21:42
Weather SourceWFAC

Appendix: Source Data