FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA13FA131 · Cessna T337C

13 Feb 2013 · New Smyrna Beach, FL, United States

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

From New Smyrna Beach Municipal Airport (EVB) to New Smyrna Beach Municipal Airport (EVB)

Report a problem

Event

NTSB case
ERA13FA131
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 T337C

Aircraft type
Cessna 337
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
N2576S
Operator
Unknown
Onboard fatalities
Unknown
Route
From New Smyrna Beach Municipal Airport (EVB), New Smyrna Beach, FLTo New Smyrna Beach Municipal Airport (EVB), New Smyrna Beach, FL
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)
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Tree(s)
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 power plant
  • Aircraft › Aircraft systems
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

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

NTSB narrative

Shortly after taking off on the test flight, the pilot transmitted "mayday mayday" over the control tower's radio frequency. According to eyewitnesses, the airplane was in a left-wing-down attitude when it impacted a tree, power lines, and then another tree before coming to rest in a pasture. A review of data downloaded from the engine data monitor revealed that the rear engine exhibited erratic fuel flow beginning 2 days before the accident and continuing through the accident flight. Further, the engine data monitor indicated that the rear engine's propeller was under low-to-no power with a low pitch angle at the time of impact. The front engine exhibited no abnormalities or malfunctions, and the investigation found no other anomalies that would have precluded normal operation of the airplane.

During postaccident examination, the engine-driven fuel pump was removed and bench tested where it exhibited fuel flow higher than manufacturer guidelines with low fuel pressure. In order to meet bench test standards, an adjustment equal to three turns of the adjustment screw was made. The fuel pump then operated normally and was placed back on the engine; however, the engine still did not attain full power. Further examination revealed potential debris between the throttle assembly's brass and stainless steel plates. After removal of the debris and reassembly of the throttle assembly, it operated within the normal range. Although the source of the debris could not be definitively determined, it likely originated in either in the fuel or a fuel tank.

Maintenance records indicate that two days before the accident, the fuel pump was removed, repaired, and reinstalled after work was completed on the rear fuel selector valve. After the pump was reinstalled, the mechanic adjusted the continuous flow fuel injection system using the airplane's JPI engine monitor system and an external low pressure gauge to set the takeoff fuel flow; he then refueled the plane from containers in which he had stored the fuel in order to service the fuel pump. The following day, the pilot and the mechanic again adjusted the fuel pump's fuel flow after conducting an unsatisfactory engine run-up . After the adjustment, the run-up appeared to be normal. Directives from the engine's manufacturer recommended using a Model 20 ATM-C Porta Test Unit or equivalent to ensure the fuel injection system meets all pressure and flow specifications. Using a JPI engine monitor and an external gauge would have given inaccurate results without a properly calibrated fuel pump, and the mechanic's recalibration of the engine-driven fuel pump's adjustment screw would have only masked the debris issue within the throttle assembly.

Further, review of the manufacturer's approved engine-out emergency procedures indicated that with a rear engine failure, the propeller should be immediately feathered and the landing gear retracted after obstacle clearance. Therefore, even with a loss of rear engine power, the airplane's operating manual indicated that the airplane would have been able to climb at least 275 feet per minute with one engine, assuming the required pilot inputs were made. Had those single-engine climb performance conditions been met, the airplane likely would have been able to, at a minimum, maintain altitude until a safe landing could have been accomplished. However, as the rear propeller was found with a low pitch angle and the landing gear was found in the down and locked position after the accident, the airplane had not been configured for maximum single-engine performance as outlined in the engine-out procedures.

Probable cause

Maintenance personnel's failure to follow procedures and published directives in calibrating the continuous flow fuel system and failure to accurately diagnose debris in the throttle assembly, resulting in a loss of power in one engine. Contributing to the accident was the pilot's failure to comply with published engine out procedures, which resulted in an off-airport landing and subsequent impact with a tree and the ground.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA13FA131
Event ID
20130213X43319
Case number
ERA13FA131
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: 30316adb9624df80667e4b7b5129e06e5730774a118a4480cf7e1d391d3baac1; retrieved 2026-09-14T15:52:57.927Z.