FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR24LA205 · Replica PA-12 REPLICA

22 Jun 2024 · Douglas, WY, United States Narrative disagrees

Replica PA-12 REPLICA · Accident: fuel exhaustion on approach

From Converse County Airport (DGW) to an unrecorded destination

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
WPR24LA205
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

Replica PA-12 REPLICA

Aircraft type
Replica PA-12
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
N406Z
Operator
Unknown
Onboard fatalities
Unknown
Route
From Converse County Airport (DGW), Douglas, WYTo not recorded
Aircraft age
About 15 years (built 2009)
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
Fuel exhaustion
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 › Fluids/miscellaneous hardware
  • Personnel issues › Action/decision
  • 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 pilot was performing a Phase 1 flight test in the airplane following the installation of a new engine. The pilot reported that before departure the engine ran rough, with a loss of about 250 rpm while operating on only one of the two electronic magnetos. He dismissed the anomaly as the engine functioned normally with both electronic control unit (ECUs) on or on the other ECU. The pilot then flew for 2 hours on 40 gallons of fuel. The pilot switched tanks halfway through the flight. About 20 minutes before the accident, the pilot saw one of the multi-function displays flicker and then 20 minutes later a total loss of engine power occurred. Both ECUs indicated they were off and the pilot’s three attempts to restore power to the engine by recycling the ECUs were unsuccessful. The pilot initiated a slip maneuver to descend quickly from the base leg and rolled out into a three-point attitude over the runway. The airplane landed hard, both main landing gear axles failed, and the airplane nosed over and came to rest inverted. The vertical stabilizer and rudder were substantially damaged. The pilot noted that the axles were likely insufficient to carry the loads of the airplane during normal operations and sheared during the hard landing. Postaccident examination of the airplane and engine did not reveal any preimpact mechanical anomalies that would have precluded normal operation. The pilot reported that his multi-function display flickered and that he received indications that ECU 1 was off and ECU 2 was disconnected after the loss of power; however, all the ECU connections were secure and both ECUs functioned normally during a postaccident engine run. Performance computations showed that the airplane would have consumed about 39 gallons of the 40 gallons of fuel onboard at the beginning of the flight. Thus, it is likely that the loss of engine power was due to fuel exhaustion. The displayed fuel consumption (in gallons per hour) by the ECU was likely incorrect and may have been off by several gallons as the pilot had not calibrated the fuel flow, which was required by the ECU manufacturer after installation. The ECU operation would not have been influenced by or affected the system’s fuel management during the accident flight, as the systems were not connected.

Probable cause

A loss of power due to fuel exhaustion as a result of the pilot’s failure to calibrate the fuel flow indicator.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR24LA205
Event ID
20240624194537
Case number
WPR24LA205
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: bdf222f2afcc747e656a733e6e89ae84cba4d857924b7404482dc5154c183a5f; retrieved 2026-09-16T18:57:34.103Z.