ERA15FA378 · Piper PA 30
Sowards Aircraft Leasing Piper PA 30 · Accident: loss of control in flight during initial climb
From St. Petersburg Clearwater International Airport (PIE) to St. Petersburg Clearwater International Airport (PIE)
Narrative check · The NTSB narrative appears to contradict this record's date. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- ERA15FA378
- 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
Piper PA 30
- Aircraft type
- Piper PA-30
- 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
- N21ND
- Operator
- Sowards Aircraft Leasing
- Onboard fatalities
- Unknown
- Route
- From St. Petersburg Clearwater International Airport (PIE), St. Petersburg, FLTo St. Petersburg Clearwater International Airport (PIE), St. Petersburg, FL
- Aircraft age
- About 52 years (built 1963)
- 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 control in flight
- 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 power plant
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The commercial pilot, who had no documented previous experience in the make and model multiengine airplane, was performing touch-and-go landings on a 9,730-ft-long runway to familiarize himself with the airplane. Witnesses reported that, during the second takeoff, the airplane appeared to "struggle." Another witness reported the airplane was climbing at an unusually shallow angle. The airplane then drifted to the right of the runway centerline, rolled sharply to the right, and descended to ground impact in a steep, nose-low attitude. The airplane came to rest about 180 ft right of the runway centerline and about 1,450 ft before the end of the runway's paved surface.
Examination of the wreckage revealed that the right engine throttle was retarded, and the propeller lever was in the feather position. The right propeller blades displayed little damage and appeared to be in the feathered position. The left engine throttle and propeller levers were full forward, and damage to the left propeller was indicative of full left engine power at impact. Examination of the right engine revealed three anomalies; the diaphragm of the right fuel servo exhibited an unusual soot pattern; particulate contamination was in the fuel filter screen; and the spark plugs were in a degraded condition. However, none of these anomalies would likely have resulted in a total loss of engine power.
Based on the witness descriptions and the lack of damage to the right propeller blades, it is likely that during the climb, the right engine experienced, at least, a partial loss of power. Based on the postaccident positions of the right engine throttle and propeller levers and signatures observed on the right engine's propeller, the pilot likely responded to the loss of right engine power by retarding the right throttle and feathering the right propeller; however, he did not maintain the appropriate airspeed and subsequently lost control of the airplane. Given the airplane's impact location about 1,450 ft before the end of the runway, it is likely that, if the pilot had immediately retarded both throttles, maintained the appropriate airspeed, and landed straight ahead, he likely would have maintained control of the airplane. Additionally, the airspeed indicator did not have a marking for single-engine minimum controllable airspeed, nor was there a placard on the instrument panel as required by a Federal Aviation Administration airworthiness directive and the airplane flight manual. While the lack of these markings was not causal to the accident, their presence might have reminded the pilot of this critical information, and might have changed the outcome of the event.
Probable cause
The pilot's failure to maintain single-engine minimum controllable airspeed following a loss of right engine power during initial climb. Also causal was the loss of right engine power for reasons that could not be determined because examination of the wreckage revealed no significant mechanical deficiencies. Contributing to the outcome was the failure of maintenance personnel to ensure that required airspeed markings and placards were installed in accordance with an airworthiness directive and the airplane flight manual.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA15FA378
- Event ID
- 20150925X54323
- Case number
- ERA15FA378
- 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: a651571a195cb46258ae79fb5e6ad5c44aec6bc1b89d8289b974dea22e9b3ea0; retrieved 2026-09-14T21:31:26.450Z.