LAX94LA133 · Schweizer G-164B
Schweizer G-164B · Accident: total loss of engine power (mechanical failure) en route
Event
- NTSB case
- LAX94LA133
- 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
Schweizer G-164B
- Aircraft type
- Schweizer G-164
- 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
- N36265
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- 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 137: Agricultural
- 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
- Company maintenance personnel › Maintenance, adjustment, improper
- Company maintenance personnel › Mixture, improper
- Engine assembly, cylinder › Failure, total
- Engine assembly, cylinder › Fatigue
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE AIRPLANE SUSTAINED A TOTAL LOSS OF ENGINE POWER SHORTLY AFTER DEPARTING A PRIVATELY OWNED AIRSTRIP. THE PILOT EXECUTED AN EMERGENCY LANDING ON A PLOWED FIELD. THE AIRPLANE NOSED OVER DURING THE LANDING ROLL. THE ENGINE EXAMINATION REVEALED THAT THE NO. 1 CYLINDER FAILED IN FATIGUE ORIGINATING AT ITS SPARK PLUG HOLES. THE CYLINDER HEAD COMBUSTION SIGNATURES SHOWED THAT THE ENGINE HAS BEEN EXPOSED TO THIS OPERATING CONDITION FOR SOME TIME. THE DETONATION RESULTED FROM TOO LEAN OF A MIXTURE.
Probable cause
THE TOTAL FAILURE OF THE NO. 1 CYLINDER DUE TO FATIGUE RESULTING FROM AN IMPROPERLY ADJUSTED MIXTURE CAUSING DETONATION. THE SOFT, WET PLOWED FIELD WAS A FACTOR IN THIS ACCIDENT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX94LA133
- Event ID
- 20001206X00777
- Case number
- LAX94LA133
- 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: ef0d1fdd19be5d3dfe5ade6a86ec1cd1b3e350f77d17c3712323248499baf6d4; retrieved 2026-09-23T01:19:12.344Z.