FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX95LA153 · Robinson R22 BETA

2 Apr 1995 · Healdsburg, CA, United States

Robinson R22 BETA · Accident: in flight collision with terrain/water during landing

From Charles M. Schulz Sonoma County Airport (STS) to an unrecorded destination

Report a problem

Event

NTSB case
LAX95LA153
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

Robinson R22 BETA

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
N2323K
Operator
Unknown
Onboard fatalities
Unknown
Route
From Charles M. Schulz Sonoma County Airport (STS), Santa Rosa, 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 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
Landing · flare/touchdown
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
In flight collision with terrain/water
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

  • Pilot in command › Supervision, inadequate

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

THE STUDENT INITIATED A STRAIGHT-IN PRACTICE AUTOROTATION FROM 550 FEET AGL. THE INSTRUCTOR REPORTED THAT DURING THE DESCENT AIRSPEED AND RPM WERE MAINTAINED WITHIN LIMITS. AT 40 FEET AGL, THE STUDENT INITIATED HIS FLARE, BUT APPLIED AFT CYCLIC SO ABRUPTLY AND WITH SUCH FORCE THAT THE INSTRUCTOR WAS UNABLE TO COUNTERACT THE MOVEMENT. THE HELICOPTER CONTINUED TO DESCEND IN A TAIL-LOW ATTITUDE UNTIL THE STINGER AND TAIL ROTOR STRUCK THE GROUND, BUCKLING THE TAILBOOM. THE INSTRUCTOR REPORTED THAT WINDS AT THE ACCIDENT SITE WERE LIGHT AND VARIABLE.

Probable cause

the instructor failed to adequately monitor the student pilot's actions and to react within the control margin necessary to successfully initiate a corrective action.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX95LA153
Event ID
20001207X03311
Case number
LAX95LA153
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: df1ac486d81d77f3376a43fcbfcfd9c6dae7f3848e83f0f20da999e918c1cd7d; retrieved 2026-09-23T00:05:46.094Z.