LAX98LA242 · Enstrom F28A
Enstrom F28A · Accident: on ground/water collision with terrain/water during landing
From Reid-Hillview Airport of Santa Clara County (RHV) to Livermore Municipal Airport (LVK)
Event
- NTSB case
- LAX98LA242
- 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
Enstrom F28A
- Aircraft type
- Enstrom F28
- 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
- N288Q
- Operator
- William Mohler
- Onboard fatalities
- Unknown
- Route
- From Reid-Hillview Airport of Santa Clara County (RHV), San Jose, CATo Livermore Municipal Airport (LVK), Livermore, CA
- 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
- On ground/water 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
- Dual student › Rotor RPM, not maintained
- Pilot in command(cfi) › Remedial action, delayed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The dual student performed an off-airport pinnacle landing. The CFI stated that the helicopter began to vibrate and moved sideways so he rolled on power. By the time the helicopter reached the edge of the landing area, the rpm had decreased and he could not reposition the aircraft. The CFI reported that he pedal-turned so that the tail was pointing downhill, lowered the collective, and rolled off the throttle. The helicopter slid approximately 300 feet off the top of the hill and down a 30-degree slope. The main rotor blades contacted the ground but the aircraft remained upright. The CFI reported that there were no mechanical malfunctions with the aircraft prior to the accident.
Probable cause
The flight instructor's delayed remedial action and the student pilot's failure to maintain rotor RPM. A factor was the downhill terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX98LA242
- Event ID
- 20001211X10640
- Case number
- LAX98LA242
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1998-07-24.
- API snapshot SHA-256: 757cda19f66649d816a45e299af516358b4bf975450e2ef0f0182dd6d6b206e2; retrieved 2026-09-22T17:21:07.332Z.