FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA90LA057 · Beech 400

17 Jan 1990 · West Point, MS, United States

Sara Lee Beech 400 · Accident: undershoot on approach

From 4R4 · Fairhope, AL to an unrecorded destination

Report a problem

Event

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

Beech 400

Aircraft type
Beechcraft 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
N3121B
Operator
Sara Lee
Onboard fatalities
Unknown
Route
From 4R4 · Fairhope, ALTo 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
Approach · VFR pattern final
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
Undershoot
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 › Airspeed, misjudged
  • Pilot in command › Altitude, misjudged
  • Pilot in command › Distance, misjudged
  • Pilot in command › Proper touchdown point, not attained

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

NTSB narrative

THE PLT STATED THE APCH TO LAND WAS NORMAL UNTIL THE ACFT WAS ABOUT 150 TO 200 FT AGL ON FINAL APCH. HE EASED THE POWER BACK TO FLT IDLE ANTICIPATING A PERFECT LANDING. AS THE ENGS SPOOLED DOWN, HE REALIZED THE ACFT WAS SETTLING QUICKLY, SO HE STARTED ADDING POWER. HOWEVER, THE ACFT TOUCHED DOWN ON AN EMBANKMENT ABOUT 6 FT SHORT OF THE RUNWAY, DAMAGING THE LEFT MAIN GEAR. THE ACFT THEN TRAVELED ONTO THE RWY, VEERED LEFT & SLID OFF THE RWY WITH THE RGT MAIN GEAR DAMAGED. SPARKS IGNITED THE GRASS, BUT THE FIRE DID NOT REACH THE ACFT.

Probable cause

THE PILOT MISJUDGED DISTANCE, SPEED, AND ALTITUDE ON FINAL APPROACH, AND FAILED TO ATTAIN THE PROPER TOUCHDOWN POINT FOR LANDING.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA90LA057
Event ID
20001212X22459
Case number
MIA90LA057
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: 603818b39b0a0d797ab6737b7df457288f6acaf0bd0b35e0ee514af9d416c64c; retrieved 2026-09-23T06:51:11.626Z.