FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA24FA308 · Beech B-60

19 Jul 2024 · Vienna Center, OH, United States

Beech B-60 · Accident: loss of control in flight on approach

From Plattsburgh International Airport (PBG) to John Glenn Columbus International Airport (CMH)

Report a problem

Event

NTSB case
ERA24FA308
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
3 · 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 B-60

Aircraft type
Beechcraft B-60
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
N23553
Operator
Unknown
Onboard fatalities
Unknown
Route
From Plattsburgh International Airport (PBG), Plattsburgh, NYTo John Glenn Columbus International Airport (CMH), Columbus, OH
Aircraft age
About 47 years (built 1977)
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 go-around
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 control in flight
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Aircraft › Aircraft systems
  • Aircraft › Fluids/miscellaneous hardware
  • Personnel issues › Task performance

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

NTSB narrative

During the cruise portion of the cross-country flight, the pilot/owner informed air traffic control that the airplane’s left engine had lost power and he could not maintain altitude. The controller offered information on a nearby airport; however, the pilot requested, and then proceeded to, an airport farther away with a 9,003-ft-long runway. After twice circling the approach end of the runway to the left while descending, the pilot proceeded down the runway well above a normal glidepath. A witness reported that the airplane never touched down, and track data showed that the airplane’s ground speed increased while over the runway. Airport surveillance video showed the airplane pitch up and to the left at the departure end of the runway. It continued into a left, descending turn until it impacted the ground about ¼ mile west of the departure end of the runway. Given this information, it is most likely that the pilot was unsuccessful in achieving an appropriate altitude and airspeed, which likely resulted in the pilot performing a single-engine go-around. During the subsequent climb and maneuvering, he lost control of the airplane, which resulted in an uncontrolled descent and impact with terrain. The wreckage was destroyed by impact forces and a postimpact fire. The left engine’s propeller blades were feathered and showed no indications of powered rotation at impact, while the right engine’s propeller blades showed damage signatures consistent with powered rotation at impact. A postaccident examination of the left engine revealed severe detonation damage of the No. 4 cylinder piston. Further examination of the left engine fuel servo revealed a significant amount of sand-like contamination in the servo inlet filter, which matched the properties of polyethylene terephthalate (PET), which is a thermoplastic polymer of the polyester family commonly found in fuel system components. The examination of the right engine fuel servo revealed that it was also contaminated with the same substance. The right engine’s spark plugs and one of its cylinders also displayed signatures consistent with a lean fuel to air ratio. Given this evidence, it is likely that the engines were operating with unpredictable fuel to air ratios due to the fuel system contamination, which likely contributed to the detonation in the left engine and pilot’s description that the engine lost power. The investigation was unable to determine how or when the PET was introduced into the fuel system due to the postimpact fire damage.

Probable cause

The pilot’s loss of airplane control during a single-engine go-around. Also contributing to the accident was fuel system contamination, which resulted in detonation and a total loss of left engine power.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA24FA308
Event ID
20240720194723
Case number
ERA24FA308
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, 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: 22adadab8895e123ed810c2d22c495085ceebec3c0351a3ddfaeb8af820bb1a9; retrieved 2026-09-15T08:24:42.520Z.