NYC00FA136 · Bell UH-1H
Bell UH-1H · Accident: loss of engine power while maneuvering
From PA (no airport) to an unrecorded destination
Event
- NTSB case
- NYC00FA136
- 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
- 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
Bell UH-1H
- Aircraft type
- Bell UH-1
- 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
- N52AG
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From PA (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 137: Agricultural
- 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
- Maneuvering · aerial application
- 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
- 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
- Tree(s)
- 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
- Compressor assembly › Foreign object damage
- Turbine assembly › Foreign object damage
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The helicopter was on its fourth spray mission of the day, and the pilot's 51st spray mission for the season, when the accident occurred. The helicopter returned from the third mission, was refueled, reloaded, and departed. The helicopter then crashed a couple of minutes after takeoff in a wooded area. The weather was clear at the time of the accident. Main-rotor blade, and tail-rotor blade damage was consistent with low rotor rpm at impact. Examination of the transmission revealed no preimpact failures or malfunctions. Examination of the engine revealed that the compressor and turbine sections of the engine had been exposed to a large amount of aluminum from an unknown source prior to impacting the trees.
Probable cause
Foreign object damage to the compressor and turbine sections of the engine, which resulted in a loss of power.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC00FA136
- Event ID
- 20001212X21095
- Case number
- NYC00FA136
- 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: 6af503152b195e257ffbac18b5c0e97b7ab8af027e84a06389c1bae8d2be5f48; retrieved 2026-09-20T21:13:33.181Z.