NYC00LA174 · Enstrom 280 FX
Enstrom 280 FX · Accident: total loss of engine power (non-mechanical) en route
From Galenstein Park Heliport (22OH) to an unrecorded destination
Event
- NTSB case
- NYC00LA174
- 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 280 FX
- Aircraft type
- Enstrom 280
- 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
- N383MA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Galenstein Park Heliport (22OH), Blue Ash, OHTo 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
- Total loss of engine power (non-mechanical)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Fuel exhaustion
- 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
- Fluid, fuel › Exhaustion
- Pilot in command › Aircraft preflight, inadequate
- Pilot in command › Fuel supply, inattentive
- Terrain condition › None suitable
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was performing an aerial observation flight of vehicle traffic, operating about 500 feet AGL, when the engine missed and lost power. The pilot performed a run-on landing on the edge of the road, next to a median. One skid was on asphalt and the other skin was in the grass/dirt. The skid in grass/dirt dug in and the helicopter rotated 90 degrees and rolled over. Examination of the helicopter revealed no fuel in the tank, the fuel cap in place, and no evidence of leakage. When fuel was added, the fuel gauge consistently read less than the actual amount of fuel onboard. The pilot told the Safety Board he had checked the fuel prior to departure; however, in follow-up interviews with the FAA, the pilot reported he had not checked the fuel tanks prior to departure and had not paid attention to the fuel gauge while flying.
Probable cause
The pilot's inadequate preflight of the helicopter, and his subsequent failure to monitor his fuel supply, which resulted in a power loss due to fuel exhaustion, over unsuitable terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC00LA174
- Event ID
- 20001212X21319
- Case number
- NYC00LA174
- 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: 6f4a919bd1a862f6e601ffc12bd5636cb07185449d5bb705e3c967a9d8fb9bc7; retrieved 2026-09-22T12:47:09.855Z.