FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR13LA384 · Piper PA 28 180

23 Aug 2013 · Sacramento, CA, United States

Capitol Flying Piper PA 28 180 · Accident: loss of engine power (partial) during initial climb

From Sacramento Executive Airport (SAC) to Sacramento Executive Airport (SAC)

Report a problem

Event

NTSB case
WPR13LA384
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 28 180

Aircraft type
Piper PA-28
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
N8223W
Onboard fatalities
Unknown
Route
From Sacramento Executive Airport (SAC), Sacramento, CATo Sacramento Executive Airport (SAC), Sacramento, CA
Aircraft age
About 48 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
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

  • Not determined › Not determined

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

NTSB narrative

The pilot was receiving a checkout in the airplane from a flight instructor. This was their second flight together in the airplane, and the pilot's second flight in that airplane make and model. According to the pilot and the instructor, the preflight inspection detected no anomalies, and the airplane had sufficient fuel for the flight. Engine start, taxi, and engine run-up were all normal. According to the pilot, during the climbout, when the airplane was about 500 feet above the ground, the engine "sputtered," recovered briefly, and then "lost thrust." The flight instructor reported that the engine was running "roughly." The pilots briefly attempted to restore power. Their efforts, which included changing the position of the fuel selector handle, were unsuccessful; they then attempted to land in a clearing on a golf course adjacent to the airport. The airplane struck trees and came to rest inverted on the golf course. Postaccident examination of the airframe and engine confirmed that the engine was developing little or no power at impact but did not reveal any preimpact conditions or failures that would have precluded continued engine operation.

Before the takeoff, the engine was idled on the ground for at least 8 minutes. Although the carburetor heat was off (the recovered checklist did not reference carburetor heat) and the ambient conditions were conducive to "serious icing" at glide power, both pilots reported that the taxi, engine run-up, and takeoff roll were normal. Thus, it is unlikely that carburetor ice was present at the time the engine began to lose power.

The airplane's original fuel selector handle and placard design were ambiguous with regard to the selection indication, particularly to a person unfamiliar with the airplane; the selector could inadvertently and unknowingly be set to the "OFF" position for flight. The manufacturer issued two service letters (in 1971 and 1972), which recommended modification of the fuel selector, and subsequently issued a mandatory service bulletin (in 1986) that called for the replacement of the handle and placard to reduce the possibility of pilots inadvertently selecting the "OFF" position for flight. Although the service bulletin was applicable to the accident airplane, the handle and placard had not been replaced.

Because the pilot manipulated the fuel selector following the power loss and a first responder manipulated it after the accident, neither the takeoff nor the preimpact setting of the fuel selector valve could be determined. The investigation was unable to determine if the fuel selector valve was inadvertently set to the "OFF" position at some point before the takeoff, allowing some limited high-power engine operation using residual fuel. The investigation also considered the possibility that the fuel selector valve was improperly set so that the selector valve ports were partially, instead of fully, aligned, allowing sufficient fuel for low-power operation and limited-time high-power operation. However, because power was not restored after the pilot repositioned the fuel selector after the first indication of an engine problem, it is unlikely that a mis-set fuel selector valve caused the power loss.

Probable cause

A partial loss of engine power during initial climb for reasons that could not be determined because postaccident examination revealed no evidence of preimpact mechanical malfunction or failure that would have precluded normal operation.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR13LA384
Event ID
20130823X31739
Case number
WPR13LA384
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2013-08-24.
  • API snapshot SHA-256: 03fa2fc5e5d87ed2d7ad260f2fb856330314bcf807a4e036308d2afd117bc275; retrieved 2026-09-15T22:36:00.201Z.