FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA10LA376 · Beech K35

26 Jul 2010 · Philadelphia, MS, United States

Beech K35 · Accident: powerplant system/component malfunction/failure during landing

From Monroe County Airport (M40) to Barrett Field (MS96)

Report a problem

Event

NTSB case
ERA10LA376
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 K35

Aircraft type
Beechcraft 35
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
N6035E
Operator
Jon P. Grubs · private individual
Onboard fatalities
Unknown
Route
From Monroe County Airport (M40), Monroe, MSTo Barrett Field (MS96), Philadelphia, MS
Aircraft age
Not recorded
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
Powerplant system/component malfunction/failure
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 power plant
  • Not determined › Not determined

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

NTSB narrative

The pilot reported that the airplane touched down on the first third of the 4,000-foot-long asphalt runway. After touchdown he was unable to move the throttle control forward or back. He applied brake pressure; however, the airplane departed the end of the runway and struck a moving vehicle before stopping upright on a road. Postaccident examination of the airframe and engine, which included the throttle control, did not reveal evidence of mechanical malfunctions. There were no known witnesses to the landing and the airplane's touchdown point on the runway could not be determined. The reason for the throttle malfunction could not be determined.

Probable cause

A throttle control malfunction during landing for undetermined reasons, resulting in a runway overrun.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA10LA376
Event ID
20100726X04919
Case number
ERA10LA376
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: 3e5e8d51f27afe6f824d8d95a9b8aa52021b5a3015992269170bff7b427b468f; retrieved 2026-09-15T14:45:21.656Z.