FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA98LA167 · North American T-28B

21 May 1998 · Spartanburg, SC, United States

North American T-28B · Accident: overrun during landing

From Greenville Downtown Airport (GMU) to Spartanburg Downtown Memorial Airport (SPA)

Report a problem

Event

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

North American T-28B

Aircraft type
North American T-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
N944RJ
Operator
Unknown
Onboard fatalities
Unknown
Route
From Greenville Downtown Airport (GMU), Greenville, SCTo Spartanburg Downtown Memorial Airport (SPA)
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
Landing · landing roll
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 › Brakes(normal), delayed
  • Pilot in command › Distance/speed, misjudged
  • Pilot in command › In-flight planning/decision, inadequate

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

NTSB narrative

The pilot was contracted to transport tissue from Spartanburg, to Charleston, South Carolina. Before departure on the positioning flight, he was advised by Flight Service Station of a severe thunderstorm watch covering South Carolina; and a thunderstorm was east of Greer, moving east and deteriorating. While taxiing to takeoff, he was advised the thunderstorm appeared to be over the destination airport and Greer Approach Control advised him that the thunderstorm was over the destination airport. The flight continued and during the approach, rain increased in intensity as reported by the pilot and a line service employee on the airport. The pilot stated that he landed about one-quarter of the way down the 5,203-foot-long runway but did not apply the brakes until the 1/2 way point. The airplane rolled off the departure end of the runway, down an embankment, and came to rest against a guardrail. Postcrash examination of the brakes revealed no evidence of preimpact failure or malfunction. The pilot was the sole pilot of an on-demand air taxi operation.

Probable cause

The pilot's misjudgment of speed and distance, and his delay in the use of brakes. Contributing to the accident was a thunderstorm, a wet runway, the pilot's self-induced pressure, and his inadequate inflight planning/decision.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA98LA167
Event ID
20001211X10161
Case number
MIA98LA167
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. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1998-05-22.
  • API snapshot SHA-256: b74adc6c6a664989a55399a571840b1bd415d153fc00aa4e998f00481c897782; retrieved 2026-09-22T17:45:44.429Z.