NYC86FHD01 · Piasecki Acft. Corp. HELISTAT 97-34J HELISTAT 9
Piasecki Acft. Corp. HELISTAT 97-34J HELISTAT 9 · Accident: partial loss of engine power (mechanical failure) while taxiing
Event
- NTSB case
- NYC86FHD01
- 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
Piasecki Acft. Corp. HELISTAT 97-34J HELISTAT 9
- Aircraft type
- Piasecki HELISTAT 97
- 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
- N1897Z
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo 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
- Taxi · from runway
- 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
- Partial loss of engine power (mechanical 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
- Manufacturer › Acft/equip, inadequate design
- Manufacturer › Acft/equip, inadequate handling/perf capabilities
- Rotorcraft flight control › Inadequate
- Throttle/power lever, linkage › Disconnected
Approximate · Estimated position: the centre of Lakehurst, NJ, the place the record names. Not the accident site.
NTSB narrative
THE HELISTAT, A HYBRID A/C WITH 4 H-34 MAIN FUSELAGES ATTACHED TO A FRAME ALONG WITH A ZPG-2 HELIUM FILLED ENVELOPE HAD JUST COMPLETED IT FIRST HOVER TEST FLT SUCCESSFULLY AND LANDED. A PWR LOSS WAS NOTED ON THE NO. 3 HELICOPTER AND THE TEST WAS TERMINATED AND THE MOORING MAST CALLED FOR. PRIOR TO RE-MOORING A WIND SHIFT CAUSED AN UNCOMMANDED LEFT TURN WHICH THE PILOT COULD NOT CONTROL WITH THE FLT CONTROLS. WITH A TAILWIND, NO WHEEL BRAKES OR GND STEERING A TAKEOFF WAS ATTEMPTED. THE 4 MAIN LANDING GEAR WHICH HAD NO SHIMMY DAMPNERS STARTED TO SHIMMY. THE FOUR HELICOPTERS STARTED TO REACT TO THE SHIMMY WITH GROUND RESONANCE. AS THE HELISTAT FINALLY LIFTED OFF, THE FOUR INDIVIDUAL HELICOPTERS BROKE OFF AND FELL TO THE GROUND. ONE PILOT RECEIVED FATAL INJURIES, 3 RECEIVED SERIOUS INJURIES AND ONE MINOR INJURIES. THE HELISTAT WAS DESTROYED. THE PRW LOSS ON THE NO. 3 HELICOPTER WAS TRACED TO A MISSING THROTTLE LINKAGE CORRELATION PIN. WHY THE PIN WAS MISSING WAS NOT DETERMINED.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record NYC86FHD01
- Event ID
- 20001213X34293
- Case number
- NYC86FHD01
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1986-07-02.
- API snapshot SHA-256: 72bca298f85d0b5acfa332add82524aaf3bf482d2a362fef9b0fd10a1e439ce7; retrieved 2026-09-21T04:30:22.041Z.