FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX05LA140 · Beech 35-C33A

19 Apr 2005 · Paso Robles, CA, United States

Beech 35-C33A · Accident: total loss of engine power (mechanical failure) en route

From Van Nuys Airport (KVNY) to Reid-Hillview Airport of Santa Clara County (KRHV)

Report a problem

Event

NTSB case
LAX05LA140
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 35-C33A

Aircraft type
Beechcraft 35
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
N299X
Operator
Squadron Two
Onboard fatalities
Unknown
Route
From Van Nuys Airport (KVNY), Van Nuys, CATo Reid-Hillview Airport of Santa Clara County (KRHV), San Jose, 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
First occurrenceThe 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
Total loss of engine power (mechanical failure)
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

  • Engine assembly, cylinder › Separation
  • Other maintenance personnel › Maintenance, installation, improper

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The number 4 cylinder and piston separated from the engine during cruise flight and the airplane collided with vine trellises and terrain during an emergency landing in a vineyard. While in flight at 8,500 feet mean sea level, the pilot heard a loud noise and the engine started running rough. He started to divert to a nearby airport when there was another loud bang from the engine compartment; engine rpm dropped dramatically, and the cockpit started to fill with white smoke. He was being vectored to a nearby airport when the cowling popped open and remained open, substantially increasing the airplane's rate of descent. The pilot set up to land in a vineyard by lowering the airplane's landing gear and approaching the field at 45 degrees to the vineyard rows. He started the landing at 75 knots when the left main landing gear snagged a grape vine row pole and wires. The plane veered to the left, and stopped almost immediately. He recalled that his head hit the dashboard during the landing and his passenger in the right seat was unconscious after the landing. Shoulder harnesses or straps were not installed on this airplane, only lap belts. The calculated landing decelerating force was about 19.5 g's, which resulted in both occupants receiving serious head injuries. Post accident examination of the engine revealed that the number 4 cylinder had departed the engine along with the piston. The engine case halves were fractured directly above the number 4 cylinder location. The two upper right cylinder hold down studs were present and appeared undamaged, while the bottom studs were sheared across their diameter above the engine case, and left-hand side studs were sheared across their diameters at the engine case surface. The number 4 cylinder base pad surface of the crankcase exhibited fretting at the 3 and 9 o'clock positions. This condition is consistent with the right-hand and bottom cylinder hold down nuts backing off during engine operation allowing the number 4 cylinder to move in rhythm with the piston until the remaining cylinder studs on the left side failed under the cyclic load. The backing off of the cylinder hold down nuts would not normally occur if the nuts had been properly torqued when installed. The number 2, 4, 5, and 6 cylinders had been removed and replaced or reinstalled 186.2 hours prior to the accident. The under-torqued cylinder hold down nuts were not detected during the 100-hour inspection that was performed 88.1 hours prior to the accident.

Probable cause

the separation of the number 4 engine cylinder due to improperly torqued cylinder hold down nuts. A finding in this accident was the lack of a shoulder restraint system in the airplane, which contributed to the occupants' injuries.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX05LA140
Event ID
20050421X00490
Case number
LAX05LA140
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2005-04-20.
  • API snapshot SHA-256: 81b3eea8938a0ee3af2609ce06db3b9178a90d5c4b7b90de4983d4131fcece6b; retrieved 2026-09-21T09:08:36.123Z.