LAX02FA114 · Eurocopter AS-350B
Eurocopter AS-350B · Accident: in flight collision with terrain/water en route
From Reno, NV (no airport) to Susanville Municipal Airport (SVE)
Event
- NTSB case
- LAX02FA114
- 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
- 1 · 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
Eurocopter AS-350B
- Aircraft type
- Eurocopter AS-350
- 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
- N1184H
- Operator
- Dave Reger
- Onboard fatalities
- Unknown
- Route
- From Reno, NV (no airport)To Susanville Municipal Airport (SVE), Susanville, 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
- 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
- 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 › Proper altitude, not maintained
- Pilot in command › Visual illusion
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The helicopter collided with the surface of a glassy smooth lake while in cruise flight at low altitude. The purpose of the flight was to reposition the helicopter to the operator's base, after a patient delivery to a regional medical center. The approximate 10-miles in diameter lake is a shallow non-perennial body of water located about 11 miles east of the operators base. The wreckage was located about 2.5 miles from the east shore line and about 3.5 miles from the west shore. The lake is on a normal routing from the hospital to the operator's base. The flight nurse said he was sitting directly behind the pilot in a forward facing seat. He said that usually they crossed the lake about 500 feet above the surface, but this time they were much lower. He estimated that they had descended to within 20 to 50 feet of the lake surface, and, as they flew further out over the water they seemed to get lower and lower. He looked over the pilot's shoulder, and to the right, and noted how glassy smooth the water was. He stated that it was like a mirror and reflected the clouds and the sky perfectly, and was "kind of mesmerizing and disorienting" to see clouds both above and below with no distinct horizon. Just before they hit the water the pilot said on the intercom, "Boy, it's disorienting when the lake is this smooth." The nurse looked out the right side window at the distant shoreline and thought to himself that the flight seemed very, very low. The helicopter then hit the water. The flight nurse and paramedic medical crew members stated that there were no apparent mechanical malfunctions or failures with the helicopter prior to the collision with the lake surface. Examination of the extensively fragmented helicopter disclosed that all control system torque and push/pull tubes, and their associated rod end fittings, were accounted for. Scoring and other rotational evidence was noted on all drive system components.
Probable cause
Failure of the pilot to maintain sufficient altitude/clearance above the water while performing a low altitude flight. Factors relating to the accident were the glassy water condition, and a lack of visual cues concerning perception of altitude.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX02FA114
- Event ID
- 20020322X00384
- Case number
- LAX02FA114
- 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: 6cd3ee8d3b6ad644a000854b8e3cd18c9e31d05bc54874f7afbb815ba8da3058; retrieved 2026-09-20T20:08:20.431Z.