WPR10LA280 · Beech F33 A
Airline Transport Training Center Arizona Beech F33 A · Accident: loss of engine power (total) on approach
From Phoenix Goodyear Airport (GYR) to Marana Regional Airport (AVQ)
Event
- NTSB case
- WPR10LA280
- 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 F33 A
- Aircraft type
- Beechcraft 33
- 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
- N1565A
- Onboard fatalities
- Unknown
- Route
- From Phoenix Goodyear Airport (GYR), Goodyear, AZTo Marana Regional Airport (AVQ), Marana, 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
- 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
- Substantial
Cause areas
- Not determined › Not determined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
While maneuvering to enter the traffic pattern prior to landing, the airplane's engine experienced a partial power loss. The flight instructor took control of the airplane from the student pilot and turned on the fuel pump, which resulted in power being temporarily restored to the engine, followed about 10 seconds later by a total loss of engine power. During the off-airport forced landing, the left wing's leading edge struck a tree, resulting in substantial damage. A postaccident inspection of the engine's fuel control unit and engine driven fuel pump revealed no anomalies that would have precluded normal operation. Additionally, a technician who examined the engine reported that the engine did not exhibit any abnormalities that would have prevented normal operation and production of rated horsepower. The reason for the total power loss could not be determined.
Probable cause
The loss of engine power while maneuvering to land for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR10LA280
- Event ID
- 20100605X21658
- Case number
- WPR10LA280
- 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: abe15e0ff6c5bd051950767ce0d53b37e55931a5d9ebd5c2c0a169828b70708a; retrieved 2026-09-15T14:21:28.713Z.