SEA99LA151 · Rotordyne 200
Rotordyne 200 · Accident: loss of control in flight while maneuvering
From S36 to an unrecorded destination
Event
- NTSB case
- SEA99LA151
- 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
Rotordyne 200
- Aircraft type
- Rotordyne 200
- Category
- Gyroplane
- 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
- N85Z
- Operator
- Mellema, Roger, D. · private individual
- Onboard fatalities
- Unknown
- Route
- From S36To 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
- Loss of control in flight
- 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, not performed
- Rotor system, main rotor blade retaining pin/bolt › Undertorqued
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The co-owner/builder had been engaged in resetting the angle of attack (pitch angle) of the main rotor blades previous to the accident. Witnesses reported observing the gyrocopter depart to the south, proceed west, and then execute several oscillatory, rocking or pitching like maneuvers after which the aircraft entered a steep descent to the ground. Post-crash examination revealed that all eight of the main rotor blade pitch adjustment bolts were loose. Examination of the upper outboard shim plate of each blade attach bar revealed markings which clearly established a pitch bolt torque of 190 inch-pounds. Release of the main rotor blade pitch adjustment bolts would allow a rotor blade pitch change and subsequent loss of control.
Probable cause
The owner/builder's failure to properly torque the rotor blade retaining bolts.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA99LA151
- Event ID
- 20001212X19656
- Case number
- SEA99LA151
- 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 1999-08-31.
- API snapshot SHA-256: 4bdbbee0b47d8a02f64d5ceaa9a3cd8d5897b63cede33276048dff7db9cdc286; retrieved 2026-09-20T21:50:25.573Z.