FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX00LA074 · Beech F-33A

11 Jan 2000 · MOBILE, AZ, United States

Beech F-33A · Accident: total loss of engine power (mechanical failure) en route

From Bishop Airfield (1AZ0) to Phoenix Goodyear Airport (GYR)

Report a problem

Event

NTSB case
LAX00LA074
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
0
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 F-33A

Aircraft type
Beechcraft F-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
Operator
Unknown
Onboard fatalities
Unknown
Route
From Bishop Airfield (1AZ0), AZTo Phoenix Goodyear Airport (GYR), Goodyear, 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 · climb to 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

  • Eng assembly, crankshaft counterweights/vib damper › Fractured
  • Manufacturer › Maintenance, installation, improper

Not plotted · Location withheld: coordinates are missing, conflicting, invalid, or have no accepted acquisition method. No substitute location has been invented.

NTSB narrative

During climb out the engine began shaking, rattling, and losing power. The flight instructor took the controls and performed an emergency off-airport landing. While on rollout the aircraft sustained substantial damage to the leading edges and lower surfaces of both wings. The engine had been previously inspected IAW TCM 99-3, which required the removal of the No. 1 and 3 cylinders. Upon reassembly of the cylinders, it was necessary to reinstall three snap rings on the crankshaft counterweights at the No. 2 and 5 cheeks. An inspection of he No. 5 cheek revealed that these three snap rings were not fully seated. The signatures on the crankshaft and counterweight were consistent with a counterweight striking the crankshaft. This can only happen if the counterweight pin is not in place. A revision to TCM mandatory service bulletin 99-3C, published on July 27, 1999, now requires that the gap between the snap ring ears be measured to insure that they are properly seated during reassembly.

Probable cause

the manufacturer representative's improper reinstallation of the crankshaft counterweight snap rings which subsequently separated, allowing the crankshaft counterweight to contact the crankshaft resulting in a total power loss of engine power.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX00LA074
Event ID
20001212X20389
Case number
LAX00LA074
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: 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: 7526a0cbf4fc919d2003afa195f37eda0c0c0cd76ec97771d0d919f213304afd; retrieved 2026-09-22T13:24:08.830Z.