NYC83FA102 · Hiller FH-1100
Hiller FH-1100 · Accident: abrupt maneuver en route
From Gettysburg, PA to York, PA
Event
- NTSB case
- NYC83FA102
- 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
- 2 · 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
Hiller FH-1100
- Aircraft type
- Hiller FH-1100
- 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
- N4034K
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Gettysburg, PATo York, PA
- 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
- Abrupt maneuver
- 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
- Reason for occurrence undetermined
- Rotor drive system, main rotor mast(drive shaft) › Overload
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PLT TOOK OFF ON A FLT TO YORK, PA TO REFUEL THE HELICOPTER & TO DEMONSTRATE IT TO A PROSPECTIVE BUYER WHILE EN ROUTE. WITNESSES OBSERVED THE HELICOPTER SHORTLY AFTER DEPARTURE. TWO OF 4 WITNESSES HEARD A CHANGE IN THE SOUND OF THE HELICOPTER, 2 WITNESSES SAW THE HELICOPTER SWINGING FROM SIDE TO SIDE PRIOR TO CRASHING, AND 2 OR THE WITNESSES SAW THE MAIN ROTOR ASSEMBLY SEPARATE FROM THE MAIN ROTOR DRIVE SHAFT. ONE WITNESS, WHO SAW THE HELICOPTER FLYING TOWARD HIS POSITION, REPORTED THAT IT STARTED TO 'SWOOP' DOWN, THEN TURNED UPWARD, AND THEN THE MAIN ROTOR ASSEMBLY & 2 OTHER PIECES SEPARATED. THE HELICOPTER THEN TURNED OVER & CRASHED. THE 1ST PERSON TO ARRIVE AT THE CRASH SITE SAID THE PLT DID NOT HAVE A SEAT BELT ON. AN EXAM OF THE WRECKAGE REVEALED THAT THE MAIN ROTOR MAST HAD SEPARATED ADJACENT TO THE MAIN ROTOR SYS STATIC STOPS. ALL FUSELAGE & FLT CONTROL SEPARATIONS WERE EXAMINED & FOUND TYPICAL OF OVERLOAD FAILURES. THE TAIL CONE HAD BEEN SEVERED BY THE MAIN ROTOR.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record NYC83FA102
- Event ID
- 20001214X42796
- Case number
- NYC83FA102
- 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: 0eae1f42043828ec1cb66fc0ad8c5be17de72aadc35a54efe1665051afa250cb; retrieved 2026-09-21T06:53:24.938Z.