ERA21LA316 · SOCATA TBM-700 C2
SOCATA TBM-700 C2 · Accident: runway excursion during landing
From West Michigan Regional Airport (BIV) to an unrecorded destination
Event
- NTSB case
- ERA21LA316
- 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
- Event fatalities
- Unknown
- 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
- Visual Meteorological Cond
SOCATA TBM-700 C2
- Aircraft type
- Socata TBM-700
- 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
- N48UM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From West Michigan Regional Airport (BIV), Holland, MITo not recorded
- Aircraft age
- About 17 years (built 2004)
- 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
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot stated his visual approach to landing was “uncomfortably fast.” The airplane crossed over the threshold about 30 to 40 knots above the approach speed recommended in the Pilot’s Information Manual (PIM). He applied brakes, but the runway was wet and slick. Unable to stop on the remaining runway, the pilot attempted to abort the landing by moving the throttle from beta to full, but the throttle “stuck.” The airplane subsequently overran the runway and came to rest about 325 ft past the end of the runway. The engine mounts and left wing sustained substantial damage.
Examination of the airplane revealed all engine and flight controls were intact from the cockpit controls to their respective control surfaces and functioned normally. In addition, examination of the brakes revealed no anomalies. The throttle lever had no binding and operated smoothly through its full range of motion. The flaps were found in the takeoff position, not in the landing position as they should have been for landing.
Postaccident examination of the wreckage revealed no evidence of preimpact mechanical malfunctions or failures that would have precluded normal operation.
According to the PIM, when configured correctly and using the recommended approach speed of 80 knots, the landing distance on a wet runway would have been about 2,700 ft of the 3,700 ft available.
Probable cause
The pilot’s decision to continue an unstable approach, which resulted in a runway excursion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA21LA316
- Event ID
- 20210804103631
- Case number
- ERA21LA316
- 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, coordinates, cause areas. 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: 33b3bdc08ab7bb7faf2e6c5039cede4968e6c4da882728acf0e3693af3b088cf; retrieved 2026-09-16T14:22:47.302Z.