IAD98FA092 · Austin REVOLUTION MINI 500 REVOLUTION
Austin REVOLUTION MINI 500 REVOLUTION · Accident: rotor failure/malfunction while maneuvering
From Bangor, PA (no airport) to an unrecorded destination
Event
- NTSB case
- IAD98FA092
- 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
Austin REVOLUTION MINI 500 REVOLUTION
- Aircraft type
- Austin REVOLUTION MINI 500
- 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
- N2XK
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Bangor, 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 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
- 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
- Rotor failure/malfunction
- 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
- Owner/builder › Maintenance, adjustment, improper
- Rotorcraft flight control, pitch change rod/link › Loose part/bolt/nut/clamp/etc
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot departed his home in the home-built helicopter on a maintenance test flight. The purpose of the flight was to track the main rotor system after repair and re-assembly of the helicopter. The main transmission, transmission mast, main rotor system, and tailboom and associated components had been replaced following a rollover accident. The pilot changed the blade track by adjustment of the pitch change links during ground runs prior to takeoff. Witnesses to the accident reported unusual sounds from the helicopter before two sharp reports and an uncontrolled descent. One main rotor blade was found 400 feet from the main wreckage. Examination of the wreckage revealed rotor to tailboom contact. Fracture separation of one rotor blade and fracture of the pitch horn on the same side were due to overload. The pitch change link barrel was loose on the fractured horn with no torque applied to the barrel nuts.
Probable cause
the improper maintenance adjustment and the failure to properly torque the pitch-change link barrel by the owner/builder which resulted in main rotor to tailboom contact and main rotor separation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD98FA092
- Event ID
- 20001211X10871
- Case number
- IAD98FA092
- 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: 5cd8cdeb2e1344e87137311bcc02b07beda6a24cbe8c44a68d53dd99eadc4aa1; retrieved 2026-09-20T22:28:06.684Z.