FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW95LA321 · Piper PA-28R-201

28 Jul 1995 · San Antonio, TX, United States

Piper PA-28R-201 · Accident: overrun during takeoff

From Stinson Municipal Airport (SSF) to an unrecorded destination

Report a problem

Event

NTSB case
FTW95LA321
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-28R-201

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
N36085
Operator
Unknown
Onboard fatalities
Unknown
Route
From Stinson Municipal Airport (SSF)To 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
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
Destroyed

Cause areas

  • Dual student › Aborted takeoff, delayed

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

NTSB narrative

The private pilot dual student reported that a short field landing was executed. During the subsequent takeoff, 'I retracted the flaps and then applied full power, we started the takeoff roll waiting for the airspeed to increase, the airplane lifted off, but we were unable to achieve a positive rate of climb so I decided to abort the takeoff.' The flight nstructor reported that during takeoff, the student 'unexpectedly retarded the throttle...landed...and began to apply the brakes in accordance with the normal training procedures.' He further stated that 'within 1 to 2 seconds after landing, I applied full brakes as well. After a few more seconds, it was apparent that we were not slowing down enough to stop by the end of the runway. Under the circumstances, the best decision was to maintain control of the airplane and go straight off the end of the runway.' The aircraft subsequently impacted a fence beyond the departure end of the runway. The left fuel tank ruptured during the collision with the fence and the airplane caught fire and burned.

Probable cause

The dual student's delay in aborting the takeoff. A factor was the flight instructor's inadequate supervision.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW95LA321
Event ID
20001207X03974
Case number
FTW95LA321
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: 03d49d33b6fcff56b96bcbfbdd241ddbcdeaa9f8332a1ac90e8374bd5d6c0a72; retrieved 2026-09-21T13:10:31.218Z.