LAX94LA201 · Schweizer 300C
Fong Seong Fishing Group Schweizer 300C · Accident: loss of engine power en route
From FISHING VESSEL, PO (no airport) to an unrecorded destination
Event
- NTSB case
- LAX94LA201
- 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
Schweizer 300C
- Aircraft type
- Schweizer 300
- 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
- N60718
- Operator
- Fong Seong Fishing Group
- Onboard fatalities
- Unknown
- Route
- From FISHING VESSEL, PO (no airport)To 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
- 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
- Loss of engine power
- 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
- Altitude › Inadequate
- Pilot in command › Flare, misjudged
Not plotted · Location withheld: coordinates are missing, conflicting, invalid, or have no accepted acquisition method. No substitute location has been invented.
NTSB narrative
The pilot reported that he was 35 minutes into the fish-spotting flight when he 'heard something wrong with the engine.' He then turned his helicopter in the direction of his ship and began a precautionary approach to the water. The pilot stated that engine performance continued to deteriorate during the descent. At an altitude between 350 and 400 feet at an airspeed of 50-to- 60 knots, the engine failed completely. The pilot then initiated an autorotation and turned left into the wind. Approximately 30 seconds after the first indication of an engine problem, the pilot autorotated into the water and landed hard. The pilot stated that he landed hard because of the 'high density altitude conditions, no wind conditions, low altitude where the engine actually failed and quit.' The pilot also stated that the sun's reflection on the water 'created some illusions which made it difficult to visually establish the distance from the water, the speed, and the rate of descent.' The nature of the engine problem was not reported by the operator.
Probable cause
THE LOW ALTITUDE OF THE AIRCRAFT WHEN THE ENGINE LOST POWER AND THE PILOT'S MISJUDGEMENT OF THE FLARE POINT DURING THE AUTOROTATION. FACTORS IN THE ACCIDENT WERE THE LOSS OF ENGINE POWER AND THE SUNGLARE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX94LA201
- Event ID
- 20001206X01141
- Case number
- LAX94LA201
- 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: 06aaaab10136d03eac9f0668ef88fd2c2f11ac3c5275b39e3dc76dea05a70520; retrieved 2026-09-23T01:11:30.376Z.