FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN20LA017 · SOCATA TB 30 EPSILON

1 Nov 2019 · Kalamazoo, MI, United States

SOCATA TB 30 EPSILON · Accident en route

From Kalamazoo/Battle Creek International Airport (AZO) to Battle Creek Executive Airport at Kellogg Field (BTL)

Report a problem

Event

NTSB case
CEN20LA017
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
Visual Meteorological Cond

SOCATA TB 30 EPSILON

Aircraft type
Socata TB-30
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
N50TB
Operator
Unknown
Onboard fatalities
Unknown
Route
From Kalamazoo/Battle Creek International Airport (AZO), Kalamazoo, MITo Battle Creek Executive Airport at Kellogg Field (BTL), Battle Creek, MI
Aircraft age
About 34 years (built 1985)
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
En route · climb to cruise
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
Unknown or undetermined
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
  • Aircraft › Aircraft power plant
  • Environmental issues › Physical environment
  • Not determined › Not determined
  • 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 that, during the takeoff roll, the engine noise and airplane acceleration were normal; however, as the airplane climbed through 300 to 400 ft above ground level, the engine began to lose power, and the airplane could not maintain altitude. The pilot said that as the airplane neared the ground, he attempted to reduce the descent rate by flaring as much as possible, but the airplane stalled and impacted the ground with a “great deal of force” and slid to a stop, resulting in substantial damage to the left wing. Postaccident examination revealed no fuel in the fuel supply line leading to the engine for undetermined reasons. No other anomalies were noted during the examination, but a comprehensive engine exam was not performed, and the reason for the loss of engine power was not determined.

Probable cause

A total loss of engine power for undetermined reasons, which resulted in an aerodynamic stall during the pilot’s attempted forced landing at low altitude and impact with terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN20LA017
Event ID
20191102X74138
Case number
CEN20LA017
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: bd2444484188906ce9877f1cd4de46f9a0afa085664e1ef4c572675a996522f8; retrieved 2026-09-16T10:32:36.915Z.