LAX02LA216 · Grumman-Schweizer G-164B
Grumman-Schweizer G-164B · Accident: airframe, component or system failure during initial climb
From Sacramento, CA to an unrecorded destination
Event
- NTSB case
- LAX02LA216
- 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
Grumman-Schweizer G-164B
- Aircraft type
- Grumman 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
- N3631B
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Sacramento, CATo 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
- Initial climb
- 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
- Airframe, component or system 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
- Propeller system/accessories, blade › Fatigue
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
After taking off and initiating a left turn at an altitude of approximately 15 feet agl, the pilot heard a "loud bang and a sharp jolt as the airplane began shaking violently." The pilot leveled the wings and reduced power; however, the vibration did not subside. He then initiated a shallow right turn in order to land on a road. "As I began to maneuver for landing I saw a burst of flame from the exhaust and heard the engine quit and felt the aircraft settle." The airplane impacted a levee and flipped over, coming to rest inverted. During post-accident investigation of the wreckage, it was noted that the outboard section of one propeller blade was missing. The inboard section of the Hamilton Standard propeller blade was sent to the NTSB Materials Laboratory Division for examination. It was reported that the blade was fractured approximately 26 to 27 inches from the butt end. Optical examination of the fracture face found features consistent with fatigue progression over the majority of the fracture. Closer examinations revealed beach marks and other progression features indicating fatigue initiation at a mechanical dent on the camber surface near midspan. Further examination indicated that fatigue accounted for approximately 70% of the total fracture area.
Probable cause
Propeller blade failure due to fatigue. A contributing factor was the rising embankment.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX02LA216
- Event ID
- 20020709X01072
- Case number
- LAX02LA216
- 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, 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: 0e3facb4dc98f72c8bf117541607f289cc57ff2f956363c6ae6c542d322dd3db; retrieved 2026-09-22T10:45:33.178Z.