FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA25LA043 · Cessna 310K

9 Nov 2024 · Alcoa, TN, United States

Cessna 310K · Accident: loss of control on ground while taxiing

From H10 · St Louis, MO to an unrecorded destination

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.

Event

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

Cessna 310K

Aircraft type
Cessna 310
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
N143MG
Operator
Unknown
Onboard fatalities
Unknown
Route Possible conflict
From H10 · St Louis, MOTo not recorded
Aircraft age
About 59 years (built 1965)
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
Taxi · from runway
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 on ground
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

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

NTSB narrative

The pilot reported that his approach and landing were normal. After exiting the runway, while on a taxiway, the airplane “swerved to the right and seemed to accelerate.” Unable to control braking and steering, the airplane departed the taxiway to the right and proceeded through a steep depression before colliding with a wind sensor pole. The pilot secured the airplane and was met by first responders. The airplane’s right wing and fuselage were substantially damaged during the accident sequence. Postaccident examination of the airplane revealed that the brass splined bushing on the left engine throttle control shaft was stripped, which resulted in an uncontrollable, full power application to that engine. The wheel brakes were examined and no anomalies were found; the brakes held the airplane in place with the left engine at full power during a test run.

Probable cause

The failure of the left engine throttle control shaft bushing during taxi, resulting in a full asymmetric power condition and a taxiway excursion.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA25LA043
Event ID
20241112195478
Case number
ERA25LA043
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: 88fce1db40a9064c925e3f255ee5dded8b548c2ae22cba6a5f7e26cad49626a0; retrieved 2026-09-16T19:28:03.561Z.