ERA21LA081 · Piper PA28 140
Piper PA28 140 · Accident: loss of engine power (total) on approach
From Zephyrhills Municipal Airport (KZPH) to an unrecorded destination
Event
- NTSB case
- ERA21LA081
- 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
- Event fatalities
- Unknown
- 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 PA28 140
- Aircraft type
- Piper PA28
- 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
- N6978W
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Zephyrhills Municipal Airport (KZPH), Zephyrhills, FLTo not recorded
- Aircraft age
- About 55 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 final
- 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
- Aircraft › Aircraft systems
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During an instructional flight, the flight instructor noted that the flight was getting low during final approach and instructed the student pilot to add power, which he did; however, the engine did not respond. The flight instructor assumed control of the airplane and attempted to restore power but was unable to do so. The airplane subsequently impacted a utility pole and power lines during a forced landing. A postimpact fire ensued, and the airplane fell to the ground.
Postaccident examination of the engine revealed no evidence of any mechanical anomalies that would have precluded normal operation. Examination of the airframe revealed that the fuel selector was in the OFF position. During the approach and forced landing, the student pilot was not instructed to move, and was not observed moving, the fuel selector to OFF, and he did not recall doing so. The student pilot had repositioned his seat during the final approach. The passenger (in the rear seat) noticed that the loss of engine power occurred shortly after the student pilot had repositioned his seat and that the fuel pressure indicated zero just before the impact with the power lines. Given all available information, it is likely that the student pilot moved the fuel selector inadvertently to the OFF position when he repositioned his seat before the approach. The incorrect fuel selector position led to fuel starvation and a total loss of engine power.
The fuel selector was located on the airplane’s left sidewall near where the left seat pilot’s knee would be positioned. The fuel selector cover and bezel allowed the pilot to freely rotate the handle through its four positions (right tank, left tank, and two OFF positions) with no safety provision to prevent the handle from being inadvertently moved to one of the off positions. The fuel selector was the original model design. The airframe manufacturer had twice upgraded the fuel selector design; the most recent design required the pilot to depress a spring-loaded stop while positioning the fuel selector to OFF to prevent the inadvertent selection of that position. The manufacturer issued a service bulletin to upgrade fuel selectors from the original to the most recent design, but the Federal Aviation Administration did not issue an airworthiness directive, which would have required operator compliance with that service bulletin. Examination of the accident airplane’s logbook revealed that the fuel selector was replaced during the last annual inspection (about 3 months before the accident); however, the replacement fuel selector, including its cover and bezel, had the original design. Had the fuel selector in the accident airplane been replaced with the newer model, rather than the original model, it is possible that the inadvertent movement of the fuel selector to the OFF position might not have occurred.
Probable cause
A total loss of engine power due to the student pilot inadvertently moving the fuel selector to the OFF position.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA21LA081
- Event ID
- 20201218102432
- Case number
- ERA21LA081
- 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, cause areas. 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: b51416e99ddf8fc02ecbc9ca89a5d098e2e3366ffc1f8ad9b10ea7ac35e8cee2; retrieved 2026-09-16T13:30:22.338Z.