CEN15LA357 · Piper PA 30
Piper PA 30 · Accident: loss of engine power (total) on approach
From Clifton Municipal Isenhower Field (7F7) to San Antonio International Airport (SAT)
Event
- NTSB case
- CEN15LA357
- 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
- 0 · 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
- N7768Y
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Clifton Municipal Isenhower Field (7F7), Clifton, TXTo San Antonio International Airport (SAT), San Antonio, TX
- Aircraft age
- About 50 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
- Approach · VFR pattern downwind
- 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 (total)
- 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
- Not determined › Not determined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that the accident flight was the first flight following an annual inspection. During initial climb after takeoff, he noticed that the fuel flow to the right engine was higher than normal, and that the exhaust gas temperature was lower than normal. He noted that moving the propeller control had no effect on propeller rpm, and he elected to return to the airport. On the downwind leg of the traffic pattern for landing, the right engine experienced a total loss of power, and the pilot was unable to restart the engine or feather the propeller. The pilot also stated that the propeller was not windmilling following the loss of power. During the subsequent final landing approach, when the airplane was about 20 feet above the ground, the right wing "suddenly and violently rolled to the right," and the airplane impacted the ground.
Postaccident examination of the airplane's engines, ignition systems, fuel system, and fuel controls did not reveal any anomalies, and a reason for the loss of engine power could not be determined. Although a first responder to the accident observed the right engine fuel selector in the auxiliary tank position, no information was available regarding fuel quantities present in the fuel tanks at the time of the accident. Examination of the right propeller revealed that the propeller dome had no air charge, which is likely the reason for the lack of response to the pilot's propeller control inputs; however, this should not have prevented the propeller from entering the feather position after the engine lost power. It is likely that the propeller did not feather because the start locks engaged following the loss of power and the pilot's subsequent attempts to restart the engine.
Probable cause
The pilot's failure to maintain control during a precautionary landing following a total loss of power to one engine. The reason for the loss of engine power could not be determined based on available information.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN15LA357
- Event ID
- 20150813X00148
- Case number
- CEN15LA357
- 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, coordinates. 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: b9b904b4773868e7068721a268d7a0beda95bf56dcc61f0cceb2b82f7a8cf001; retrieved 2026-09-16T02:39:59.516Z.