FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN17LA104 · Beech D55

14 Feb 2017 · Columbus, OH, United States

Beech D55 · Accident: loss of engine power (partial) during takeoff

From Bolton Field (TZR) to Bolton Field (TZR)

Report a problem

Event

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

Beech D55

Aircraft type
Beechcraft 55
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
N88EB
Operator
Unknown
Onboard fatalities
Unknown
Route
From Bolton Field (TZR), Columbus, OHTo Bolton Field (TZR), Columbus, OH
Aircraft age
About 49 years (built 1968)
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
Takeoff
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
Loss of engine power (partial)
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

  • Not determined › Not determined

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

NTSB narrative

The two multiengine-rated pilots departed in the multiengine airplane for a local personal flight in gusting crosswinds. The left seat pilot reported that he wanted to get current on his takeoffs and landings and that he performed the taxi and takeoff procedure. During the climbout, the left engine began to lose power. The left seat pilot gave the right seat pilot control of the airplane, and the right seat pilot conducted the landing. The left main landing gear struck the runway hard, which resulted in the collapse of the gear. A postaccident examination of the left engine and the fuel system revealed no anomalies that would have prevented normal operation.

Probable cause

The partial loss of left engine power during takeoff and initial climb, which led to a hard landing in gusting crosswind conditions. The reason for the loss of engine power could not be determined because postaccident examination of the left engine revealed no anomalies that would have precluded normal operation.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN17LA104
Event ID
20170221X02735
Case number
CEN17LA104
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: c3ff161216b5f9d820bbb387d83db19104d054b71d7b0cf6e29b6680bc3299bb; retrieved 2026-09-16T05:01:03.491Z.