WPR10LA357 · Beech A36
Beech A36 · Accident: loss of engine power (total) en route
From Phoenix Deer Valley Airport (DVT) to Phoenix Deer Valley Airport (DVT)
Event
- NTSB case
- WPR10LA357
- 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
Beech A36
- Aircraft type
- Beechcraft 36
- 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
- N9SH
- Operator
- Reed Hatkoff
- Onboard fatalities
- Unknown
- Route
- From Phoenix Deer Valley Airport (DVT), Phoenix, AZTo Phoenix Deer Valley Airport (DVT), Phoenix, AZ
- Aircraft age
- Not recorded
- 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
- En route · descent
- 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
- Substantial
Cause areas
- Aircraft › Fluids/miscellaneous hardware
- 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 reported flying for about an hour at 10,000 feet during a maintenance test flight to break in newly installed cylinders. The pilot reduced altitude to continue operating for another hour. As he changed altitude, he switched fuel tanks. Shortly after switching tanks, the engine lost power. During the forced landing, the airplane hit an automobile. Following the accident, about 1.5 gallons of fuel were recovered from the right fuel tank, and the left fuel tank was found empty. The right fuel tank was cracked and had leaked some fuel; the left fuel tank was not damaged. During the postaccident engine examination, no mechanical failures or malfunctions were revealed that would have precluded normal operation. The loss of engine power was most likely due to the pilot’s mismanagement of the fuel, resulting in fuel starvation.
Probable cause
A loss of engine power during descent due to fuel starvation that resulted from the pilot's mismanagement of the fuel system.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR10LA357
- Event ID
- 20100718X92742
- Case number
- WPR10LA357
- 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: c4f03b3d7ed3a7ccb63409947c71c15e49964ff191fbbfd259689a503356f9b2; retrieved 2026-09-15T14:43:01.110Z.