FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN19LA090 · Beech 400 A

11 Feb 2019 · Richmond, IN, United States

Stein's Aircraft Services Beech 400 A · Accident: runway excursion during landing

From Waukesha County Airport (UES) to Richmond Municipal Airport (RID)

Report a problem

Event

NTSB case
CEN19LA090
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
Unknown
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

Beech 400 A

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
N750TA
Onboard fatalities
Unknown
Route
From Waukesha County Airport (UES), Waukesha, WITo Richmond Municipal Airport (RID), Richmond, IN
Aircraft age
About 20 years (built 1999)
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
Defining eventThe 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
Runway excursion
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 › Aircraft oper/perf/capability
  • Personnel issues › Task performance

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

NTSB narrative

The flight crew was approaching the destination airport on an instrument flight rules cross-country flight in instrument meteorological conditions. The captain stated that, after visually acquiring the runway environment during the approach, he saw that the runway "had a very light coating of snow," but he chose to continue the approach and apply full thrust reversers and braking after touchdown. The cockpit voice recorder revealed that the first officer advised the captain that the airplane was high while on final approach. The airplane crossed the runway threshold at 150 knots, touched down about 3,100 ft along the 5,502-ft-long runway at 125 knots, continued down the remaining runway, through an antenna array, and across a road before coming to rest about 750 ft beyond the paved surface. The airplane's landing approach reference speed (Vref) was between 110 and 114 knots. On a dry runway with calm wind conditions, the airplane required between about 3,200 ft and 3,500 ft runway stopping distance after touchdown; on a runway contaminated with wet or compacted snow, this distance increased to 5,300 ft. Although the captain reported that the engines shut down without his input following the accident, images from the accident site showed that the nose landing gear collapsed, deforming the surrounding structure, which included the area of the throttle quadrant. It is likely that the collapsed structure impacted the throttle quadrant and resulted in the engine shutdown. The captain reported that there were no other mechanical malfunctions or anomalies with the airplane. The captain and first officer conducted a preflight inspection of the airplane and checked the weather several times on the morning of the flight. The captain reported that the weather conditions were improving, and he did not recall seeing any new NOTAMs regarding runway conditions. The pilots' decision to continue the unstable approach and landing to the snow-covered runway despite that the distance available was inadequate resulted in the runway overrun; however, given the airplane's excessive approach speed and touchdown point over halfway down the runway, it is likely that the crew would have been unable to stop the airplane on the remaining runway even if it had been uncontaminated.

Probable cause

The flight crew's decision to continue an unstable approach under conditions that exceeded the airplane's landing performance capabilities, which resulted in a runway overrun and impact with terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN19LA090
Event ID
20190211X15851
Case number
CEN19LA090
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 16e16c73077201985deaf892e1bbd2c744f1c76860f63e19b94fa16cfe934d5f; retrieved 2026-09-16T08:35:30.360Z.