WPR12FA012 · Beech E33
Beech E33 · Accident: loss of engine power (total) en route
From North Las Vegas Airport (KVGT) to Corona Municipal Airport (KAJO)
Event
- NTSB case
- WPR12FA012
- 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
- 3 · 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 E33
- 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
- N7011N
- Operator
- Fly Corona!
- Onboard fatalities
- Unknown
- Route
- From North Las Vegas Airport (KVGT), Las Vegas, NVTo Corona Municipal Airport (KAJO), Corona, CA
- 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 · cruise
- 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 › Aircraft power plant
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
While in cruise flight, the pilot transmitted that he was in trouble and thought the airplane had experienced a propeller failure. The air traffic controller provided the pilot with instructions to the nearest airport, which was about 21 miles away. The pilot radioed that he thought that he could make it and began a descent toward the airport. A witness near the accident site observed the airplane flying in a southwesterly direction about 500 feet above ground level. As the airplane approached a set of suspended power lines, it pitched up 15 degrees, increased altitude by 100 to 200 feet, yawed to the right, made two 360-degree rotations descending vertically, and impacted terrain, consistent with an aerodynamic stall/spin.
Postaccident examination of the engine revealed a 2-inch hole in the top of the crankcase between the Nos. 3 and 4 cylinders. The No. 1 piston connecting rod had separated from the crankshaft, bending the end cap flat with no thermal discoloration evident. Laboratory examination of the bearing insert half identified circumferential wear marks on the back side of the bearing insert. The wear marks on the backside of the intact insert, the lack of heat damage to the connecting rod journal, and the lack of heat damage to the connecting rod and end cap suggest that the bearing began to spin, which led to extrusion/ejection of half of the connecting rod bearing. Once the bearing was free, fragments of bearing material worked their way up between the piston and the cylinder wall causing damage to and embedding in the piston skirt. The increased clearances between the connecting rod end cap and connecting rod journal caused large stress amplitudes that resulted in a fatigue fracture of the connecting rod bolts.
In 1998, after 1,002 hours of operation, the engine was top overhauled. A top overhaul does not inspect or replace items inside the crankcase, such as the main bearings or connecting rod bearings. At the time of the accident, the engine had accumulated 2,601 hours. The engine manufacturer recommends that the time between overhaul be 1,500 hours or every 12 years.
Probable cause
A loss of engine power due to the separation of a connecting rod, and the pilot's failure to maintain airplane control during a sudden maneuver to avoid power lines during the descent, which resulted in an unrecoverable aerodynamic stall and subsequent spin. Contributing to the accident was noncompliance with the manufacturer-recommended engine overhaul schedule.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR12FA012
- Event ID
- 20111016X83732
- Case number
- WPR12FA012
- 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. 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: 9b09682446a7e0a679a235d02b8942daf4008509c3f7c546bb27685d7196474a; retrieved 2026-09-13T21:55:25.571Z.