FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX92FA267 · Robinson R22

29 Jun 1992 · Richmond, CA, United States

Sierra Academy of Aeronautics Robinson R22 · Accident: ditching en route

From Oakland San Francisco Bay Airport (OAK) to Oakland San Francisco Bay Airport (OAK)

Report a problem

Event

NTSB case
LAX92FA267
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
2 · 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

Robinson R22

Aircraft type
Robinson R22
Category
Helicopter
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
N83858
Onboard fatalities
Unknown
Route
From Oakland San Francisco Bay Airport (OAK), Oakland, CATo Oakland San Francisco Bay Airport (OAK)
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
Ditching
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Rotor system › Undetermined

Approximate · Estimated position: the centre of Richmond, CA, the place the record names. Not the accident site.

NTSB narrative

THE STUDENT HAD RECORDED HER PRIMARY FLIGHT LESSON ON A TAPE RECORDER. AFTER REACHING THE PRACTICE AREA, THE CFI INSTRUCTED THE STUDENT TO TURN 180 DEG LEFT. THE STUDENT COMPLIED AND PERFORMED A SHALLOW BANK TURN. SECONDS LATER, WHILE CRUISING AT 2,200 FT, THE CFI BEGAN TALKING. IN MIDSENTENCE AN UNDETERMINED EVENT OCCURRED WHICH INTERRUPTED HIS SPEECH. A WIND-LIKE BACKGROUND NOISE STARTED, AND THE STUDENT EXCLAIMED 'HELP.' RADAR DATA CONFIRMED WITNESS REPORTS THAT THE TAIL BOOM AND M/R HAD SEPARATED IN LEVEL FLT. EXAM OF THE WRECKAGE INDICATED MAST BUMPING HAD OCCURRED, A M/R BLADE CRUSHED THE LEFT SIDE OF THE INBOARD TAIL CONE, AND THE ENTIRE MAST WITH ATTACHED M/R BLADES BROKE OUT OF THE TOP OF THE TRANSMISSION. THE OUTBOARD TAIL BOOM AND ROTOR ASSEMBLY HAVE NOT BEEN FOUND. EVIDENCE OF A MAIN ROTOR BLADE DIVERGENCE WAS FOUND. SPECTRUM ANALYSIS OF THE TAPE REVEALED NO ANOMALIES UNTIL THE CFI'S VOICE WAS TERMINATED. WITHIN 2 SECONDS THE ROTOR SPEED APPEARED TO SIGNIFICANTLY OSCILLATE AND ABRUPTLY END.

Probable cause

A DIVERGENCE OF THE MAIN ROTOR FROM ITS NORMAL PLANE OF ROTATION FOR AN UNDETERMINED REASON(S) WHICH RESULTED IN ROTOR CONTACT TO THE TAILBOOM.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX92FA267
Event ID
20001211X14890
Case number
LAX92FA267
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: 47c4ae4e18df179d719fb787280f4672d37ca5724f3da6810123b143a015cbd8; retrieved 2026-09-21T01:04:35.539Z.