FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA11FA458 · Cessna 310Q

17 Aug 2011 · Tupelo, MS, United States

Cessna 310Q · Accident: loss of engine power (partial) during initial climb

From Tupelo Regional Airport (TUP) to Marion County Rankin Fite Airport (HAB)

Report a problem

Event

NTSB case
ERA11FA458
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
1 · 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

Cessna 310Q

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
N444YM
Operator
Unknown
Onboard fatalities
Unknown
Route
From Tupelo Regional Airport (TUP), Tupelo, MSTo Marion County Rankin Fite Airport (HAB), Hamilton, AL
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
Initial climb
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

  • Aircraft › Aircraft oper/perf/capability
  • Aircraft › Aircraft propeller/rotor
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

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

NTSB narrative

The airplane had just undergone an annual inspection, at which time the left engine’s number two cylinder was replaced. In order to facilitate the cylinder replacement, the B-nut attaching the fuel supply hose to the engine’s manifold valve was removed and reinstalled. A postmaintenance engine ground run was performed, and no discrepancies were noted.

The airplane was cleared to depart from runway 36 with an easterly departure. Witnesses observed the airplane roll down the runway, liftoff, and at an estimated altitude of 300 to 500 feet above the runway, about mid-field, witnesses observed the airplane turn to the left on a west heading and descend. Witnesses heard a loss of engine power just before the turn. The airplane impacted the adjacent main road, and all three of the landing gear separated. The airplane struck a vehicle and a tree before its nose section impacted the base of a 3-foot diameter tree in the front yard of a house and then came to a stop. Postaccident propeller examination revealed that both propellers were in a low pitch position; the right propeller impacted while operating at high power, and the left was operating with low power or was windmilling at time of impact.

The on-site wreckage examination found that the B-nut connecting the fuel supply hose to the manifold valve on top of the left engine had backed off about a quarter turn. The B-nut was tightened, and both engines were test run after the accident; no abnormalities that would have prevented normal operation were found. Both engines produced production-rated power. After completion of the left engine test run, the B-nut between the fuel supply hose and the manifold valve was set at finger-tight torque. A wire was attached to loosen the B-nut during the engine run, and a stop was in place to limit the rotation. The engine was started and set at full throttle and the B-nut was loosened to slightly over a quarter turn. When the B-nut was loosened, the engine immediately lost power. It is likely that the B-nut had been tightened sufficiently to maintain torque during the ground run; however, the vibration of extended engine operation during takeoff led the B-nut to back off, resulting in the loss of power in the left engine.

From the position where the witnesses reported hearing the airplane lose engine power, about half the runway (or about 3,200 feet) remained. In addition, an open field was located past the departure end of that runway. However, the airplane turned left after the loss of engine power, which was contrary to the departure instructions and contrary to the safest option for an emergency landing (the remaining runway or the open field). Further, the propeller blades were in the low pitch position, indicating that the pilot didn’t perform the engine failure checklist, which stated that the propeller should be feathered. Thus, it is likely that the pilot was delayed in his reaction to the sudden loss of thrust from the left engine and could not maintain airspeed or straight ahead flight.

Probable cause

The pilot’s delayed reaction in performing the engine failure procedures and his failure to maintain adequate airspeed, which resulted in a loss of airplane control. Contributing to the accident was maintenance personnel’s improper torquing of the B-nut between the fuel supply hose and the manifold valve.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA11FA458
Event ID
20110817X02017
Case number
ERA11FA458
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: 419cfa5e9f6091c70b9a186464fd88acd182931911f35ad0475346e39bfaaf75; retrieved 2026-09-13T21:43:31.147Z.