WPR24LA146 · Robert Sterling 4P
Robert Sterling 4P · Accident: fuel starvation during initial climb
Event
- NTSB case
- WPR24LA146
- 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
Robert Sterling 4P
- Aircraft type
- Robert Sterling 4
- 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
- N78GP
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 27 years (built 1997)
- 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
- Fuel starvation
- 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 power plant
- Aircraft › Aircraft systems
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The float-equipped, experimental amateur-built airplane had just come out of its condition inspection and the accident flight was the first time it had flown in about 6 years. The pilot stated that the engine performed normally during multiple post maintenance run-ups, and with no anomalies observed he departed with the intention of remaining within the traffic pattern. However, shortly after takeoff the engine lost power and the pilot performed a forced landing into a flat open area, where the airplane landed hard on its floats and tumbled over.
The airplane was originally an FAA type-certificated Piper PA-22 Tri-Pacer but had been reclassified to the experimental amateur-built category after undergoing extensive modifications, including a larger fuel-injected engine and an extension of the fuselage and wings.
Postaccident examination did not reveal any failures in the airframe or engine that would have precluded normal operation, and fuel was present in the fuel tanks and lines leading into the fuel injection system. Review of data recorded by the airplane’s engine monitor revealed that shortly after takeoff, a reduction in fuel flow was followed immediately by an increase in engine exhaust gas temperatures. Such an increase is consistent with a lean fuel-to-air mixture, often experienced during the initial phases of a fuel exhaustion event. The manifold pressure remained unchanged, indicating the pilot kept the throttle fully open. A short time later, with no change in manifold pressure, the engine began to lose power. The loss of power was partially interrupted as fuel flow resumed, but then all power was again lost as fuel flow dropped.
The manufacturer of the engine’s fuel injection servo gave specific instructions for the design of fuel supply system that were intended to prevent vapor lock. The instructions recommended that if a fuel strainer must be used, it should not be installed on the engine side of the firewall, and if it must be installed there, it should be configured to receive blast air. Additionally, a purge valve should be installed as close to the fuel flow divider as possible, preferably directly next to it.
However, the examination of the airframe revealed that the fuel strainer was mounted on the firewall right next to a hot exhaust pipe, and although a purge valve was installed, it was installed within the cabin, where its lines were routed through the engine compartment.
Due to the multiple engine starts performed before takeoff, the engine would have been hot and retaining residual heat, and as such the fuel system likely exhibited vapor lock. The installation of a purge valve indicated the airplane likely had a history of vapor lock. Such a vapor lock would have presented itself as a fuel starvation event as observed in the engine monitor data.
Probable cause
A loss of engine power during initial climb due to fuel vapor lock. Contributing to the accident was the incorrect installation of the ancillary fuel supply system components.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR24LA146
- Event ID
- 20240509194233
- Case number
- WPR24LA146
- 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, 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: d6f94fc188cdf8d3b566f98828e60b7125d971b8af1bbb222a5256f85c285e04; retrieved 2026-09-16T18:45:07.996Z.