FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC04FA117 · Eurocopter AS-350BA

4 May 2004 · Brooklyn, NY, United States

Helinet Aviation Eurocopter AS-350BA · Accident: airframe, component or system failure while maneuvering

From Teterboro Airport (TEB) to an unrecorded destination

Report a problem

Event

NTSB case
NYC04FA117
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
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-350BA

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
N4NY
Onboard fatalities
Unknown
Route
From Teterboro Airport (TEB), Teterboro, NJTo 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
Maneuvering · hover
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
Airframe, component or system failure
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Hydraulic system › Failure, total
  • Pilot in command › Aircraft control, not maintained

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 was hovering at 1,000 to 1,200 feet, during an electronic news gathering flight, when it experienced a loss of hydraulic system power. The pilot stated he did not have any specific recollection regarding the beginning of the accident sequence. He said that he felt the helicopter was not responding to his control inputs, "the way it should be." He also did not recall reporting any specific problems over the radio; however, review of communication recordings revealed that the pilot stated he experienced a "tail rotor failure." Another helicopter captured the accident sequence from its onboard video camera. The accident helicopter was observed entering a steep descent and quickly leveling off. A fairly constant, level attitude and heading were briefly maintained before the helicopter came to an unstable hover and began an approximate two revolution left rotation about its vertical axis. During the rotation, the helicopter descended and struck the roof parapet of a 4-story building, before it impacted and came to rest on the roof of an adjacent 2-story building. Examination of the helicopter's hydraulic system revealed that the hydraulic pump drive belt had been installed inside-out and failed due to an overload, leading to a full hydraulic system failure. According to Eurocopter's emergency procedures for the helicopter, the pilot action following a hydraulic system failure would be to "calmly reduce collective pitch and adjust the airspeed to between 40 and 60 knots in level flight" and then cut off the hydraulic pressure, by moving the toggle switch located on the collective pitch lever to off. The procedures further state that when the accumulators are exhausted, the control forces become significantly higher, but "not unmanageable." The helicopter could be controlled without the main and tail rotor servo actuators being hydraulically powered, but this would require the pilot to apply "non-negligible" forces that are substantially different than the forces required with the hydraulic system operating properly. The hydraulic system toggle switch was found in the "on" position. The "flat" hydraulic pump drive belt had accumulated about 440 hours, and had a service life limit of 600 hours. On May 11, 2004, Eurocopter issued a service bulletin which recommended the installation of a"Poly-V" hydraulic pump belt. The improved belt comprised multiple longitudinal "V" shapes on its inner surface that mated with similar surfaces on the hydraulic pump pulley and had a service life limit of 1,500 hours. Eurocopter recommended that all "flat" drive belts be replaced with the "Poly-V" belts.

Probable cause

The pilot's failure to maintain control of the helicopter after a loss of hydraulic system pressure due to a failure of the hydraulic pump belt. Factors in this accident were the pilot's misidentification of a hydraulic failure, the pilot's subsequent failure to perform the appropriate emergency procedure, and the improper installation of the hydraulic pump belt by maintenance personnel.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC04FA117
Event ID
20040512X00594
Case number
NYC04FA117
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: ee0e55e83d761d2419cb5e1e58ec21dd7c88e059a68ad5ff79e533bf8805e65b; retrieved 2026-09-21T09:17:49.145Z.