NYC83FA210 · Aerospatiale SA-360C
Aerospatiale SA-360C · Accident: loss of engine power on approach
From LaGuardia Airport (LGA) to an unrecorded destination
Event
- NTSB case
- NYC83FA210
- 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
- Charter & commuter
- 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
Aerospatiale SA-360C
- Aircraft type
- Aerospatiale SA-360
- 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
- N8479U
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From LaGuardia Airport (LGA), FLUSHING, NYTo 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 135: Air Taxi & Commuter
- 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
- Approach · VFR pattern final
- 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
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
WHILE ON FINAL APCH TO A HELIPORT, THE HELICOPTER WAS AT APRX 70 KTS & 100 FT AGL WHEN THE PLT APPLIED POWER TO BEGIN DECELERATING. AS COLLECTIVE PITCH WAS APPLIED, HE HEARD A SERIES OF BANGING NOISES WHICH HE DESCRIBED AS SIMILAR TO COMPRESS STALLS. SIMULTANEOUSLY, HE NOTED A DECAY OF THE ENG POWER. THE PLT CHANGED HIS COURSE TO MINIMIZE THE DISTANCE TO THE LANDING AREA & RAISED THE NOSE TO FURTHER DECELERATE FOR A VERTICAL DESCENT. HOWEVER, DURING TOUCHDOWN, THE TAILWHEEL STRUT FAIRING HIT A BARRIER AT THE EDGE OF THE HELIPORT, SEPARATING THE VERTICAL STABILIZER & FENESTRON. THE SEPARATED COMPONENT TRAVELED UPWARD & STRUCK THE MAIN ROTOR BLADES. REPORTEDLY, THE LOW RPM WARNING HORN SOUNDED JUST BEFORE THE COMPRESSOR STALL. CORRECTIVE ACTION FOR A LOW RPM WARNING HORN IN THIS SITUATION SHOULD HAVE BEEN TO REDUCE THE POWER DEMAND BY LOWERING THE COLLECTIVE AND/OR REDUCING RIGHT PEDAL APPLICATION. AN ENG CHECK REVEALED IT WAS CAPABLE OF EXCEEDING THE MAX REQUIRED TORQUE, BUT IT HAD SLIGHT FOULING OF THE FUEL INJECTOR WHEEL & COMPRESSOR AIR FLOW
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record NYC83FA210
- Event ID
- 20001214X44305
- Case number
- NYC83FA210
- 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: 3f457f89587273d9f9912b14244a9b9e6bfc73e9a15dcf28c5e3686928f8116c; retrieved 2026-09-18T20:55:38.178Z.