Cessna T337C accident near New Smyrna Beach, Florida, February 13, 2013
On February 13, 2013 at about 6:14 pm local time, a Cessna T337C, registered N2576S, was destroyed in an accident during initial climb near New Smyrna Beach, Florida (New Smyrna Beach Municipal Air airport). It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).
Preview. This page is not yet listed for search engines.
The NTSB's probable cause their words, unchanged
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.
Source: NTSB aviation accident database, copy made October 4, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- February 13, 2013 · about 6:14 pm local time
- Place
- New Smyrna Beach, Florida · New Smyrna Beach Municipal Air · map
- Type
- Accident
- Injuries
- 1 person was killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna T337C · all T337Cs on the register
- Registration
- N2576S · no longer on the register · serial 337-0876
- Damage
- Destroyed
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Loss of engine power (partial) during initial climb defining event
- Off-field or emergency landing during emergency descent
- Collision with terrain or object (not controlled flight into terrain) during emergency descent
- Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent
The NTSB's findings
- cause Aircraft › Aircraft power plant › Engine fuel and control › Fuel control/carburetor › Malfunction
- cause Personnel issues › Task performance › Maintenance › Installation › Maintenance personnel
- cause Personnel issues › Action/decision › Action › Incorrect action performance › Maintenance personnel
- cause Aircraft › Aircraft systems › Fuel system › Fuel distribution › Incorrect service/maintenance
- cause Personnel issues › Task performance › Use of equip/info › Use of policy/procedure › Maintenance personnel
- factor Personnel issues › Task performance › Use of equip/info › Use of checklist › Pilot
- Environmental issues › Physical environment › Object/animal/substance › Tree(s) › Contributed to outcome
Pilot
- Certificate: airline transport pilot, flight instructor, commercial pilot
- Ratings: multi-engine land; multi-engine sea; single-engine land; single-engine sea; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
- Flight time: 4,186 hours in all
- Last flight review: August 1, 2012
- Medical certificate: Class 2 (with waivers/limitations)
- Seat: unk
- Injury: fatal
The aircraft
- Airframe total time: 1,350 hours
- Last inspection: annual inspection, March 5, 2011
- Seats: 6
- Landing gear: retractable
- Engine 1: Cont Motor TSIO-360-A (piston); 0 hours total
- Engine 2: Cont Motor TSIO-360-AB (piston); 0 hours total
The flight
- Departed from: EVB New Smyrna Beach FL at 6:12 pm
- Destination: EVB New Smyrna Beach FL
- Flight plan: none
Weather at the time
- Light: daylight
- Wind: from 230° at 15 knots, gusting 20
- Visibility: 7 statute miles
- Sky: broken clouds at 1,500 ft
- Temperature: 82°F (28°C), dew point 64°F (18°C)
- Altimeter: 29.86 inHg
- Observation at 6:47 pm from EVB
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flig | 1 |
About this page
Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The docket at the NTSB holds the report as a PDF and the investigation's photographs and documents. This site never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number ERA13FA131.
