FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL86FA020 · Hawker Siddeley DH 125-400A DH 125-400

7 Nov 1985 · Sparta, TN, United States

Hardee'S Food System Hawker Siddeley DH 125-400A DH 125-400 · Accident: overrun during landing

From Rocky Mount Wilson Regional Airport (RWI) to Upper Cumberland Regional Airport (SRB)

Report a problem

Event

NTSB case
ATL86FA020
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
Instrument Meteorological Cond

Hawker Siddeley DH 125-400A DH 125-400

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
N100HF
Onboard fatalities
Unknown
Route
From Rocky Mount Wilson Regional Airport (RWI), Rocky Mount, NCTo Upper Cumberland Regional Airport (SRB), Sparta, TN
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

  • Aircraft performance, hydroplaning condition › Water
  • Airport facilities, runway/landing area condition › Foreign substance covered
  • Airport personnel › Information, not identified
  • Airport personnel › Runway maintenance, inadequate
  • Airport personnel › Unsafe/hazardous condition warning, not issued
  • Pilot in command › Brakes(normal), delayed
  • Terrain condition › Wet

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

NTSB narrative

TEN MINUTES PRIOR TO LANDING HEAVY RAIN FELL ON AIRPORT.ACFT MAD NORMAL TOUCHDOWN,SPOILERS & LIFT DUMP ACTIVATED.PIC DELAYED BRAKE APPLICATION AS USUAL AND DID NOT GET THRUST LEVERS IN IDLE.AFTER ACFT PASSED MID-FIELD TAXIWAY PIC REPORTED BRAKES BECAME INEFFECTIVE.ACFT HYDROPLANED ON WATER-COVERED RUNWAY AND OVERRAN DEPARTURE END,DOWN AND EMBANKMENT, & HIT A DITCH.RUNWAY HAD AN OFF CENTER CROWN, GRASS WAS ABOUT TWO FEET TALL AT RUNWAY EDGE, AND A DAM HAD FORMED FROM PREVIOUSLY CUT GRASS WHICH PREVENTED WATER DRAINAGE.AIRPORT MANAGER SAID HE WAS NOT AWARE WATER WOULD STAND ON RUNWAY.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record ATL86FA020
Event ID
20001214X38170
Case number
ATL86FA020
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: cfcfcc5c7d8275a3a91ba14ab4ec5bf1faf32409f29b8daa4ff9f1a0f7767a86; retrieved 2026-09-21T17:06:46.920Z.