FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA97LA088 · Learjet LR35

27 Feb 1997 · Greenville, SC, United States

Learjet LR35 · Accident: overrun during landing

From Hartsfield Jackson Atlanta International Airport (ATL) to Greenville Downtown Airport (GMU)

Report a problem

Event

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

Learjet LR35

Aircraft type
Learjet LR35
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
N440HM
Operator
Unknown
Onboard fatalities
Unknown
Route
From Hartsfield Jackson Atlanta International Airport (ATL), Atlanta, GATo Greenville Downtown Airport (GMU)
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
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

  • Pilot in command › Touchdown, improper

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

NTSB narrative

The pilot-in-command stated he was cleared for an ILS approach. He had to use spoilers to intercept the glideslope. The landing was extended at the outer marker as the airspeed was slowed through 200 knots. As the airspeed decreased the spoilers were retracted and the flaps were extended to 20-degrees. The airplane was drifting to the right and flaps were lowered to 40-degrees as the drift was corrected. The airplane floated and touched down long. The spoilers, and brakes were applied as well as full reverse. There was no braking due to hydroplaning. Examination of the crash site revealed the airplane went off the end of the runway, skidded through 200 feet of sod, vaulted off a 25 foot embankment, skidded across a road, and collided with a ditch.

Probable cause

The pilot-in-command's failure to achieve the proper touchdown point on a known wet runway, resulting in a subsequent overrun and on ground collision with a ditch.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA97LA088
Event ID
20001208X07442
Case number
MIA97LA088
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: efbb6663769f07770b609434c46e977e1b77022473f350e191f937851141c7bc; retrieved 2026-09-21T21:30:09.359Z.