SEA05CA195 · Eiland RAF-200 Gyro
Eiland RAF-200 Gyro · Accident: airframe, component or system failure during initial climb
From S07 · Bend, OR to an unrecorded destination
Event
- NTSB case
- SEA05CA195
- 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
Eiland RAF-200 Gyro
- Aircraft type
- Eiland RAF-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
- N4416N
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From S07 · Bend, ORTo 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
- Initial climb
- 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
- Substantial
Cause areas
- Flight control system › Malfunction
- Pilot in command › Aircraft control, not possible
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to the pilot, during the initial takeoff climb from runway 34, he noticed that the "controls felt sluggish compared to normal precise feeling of the gyroplane." He decided to execute a 180 degree turn back to the taxiway parallel to the runway. As soon as he began a shallow turn to the right, the gyroplane entered "a very steep diving spiral turn," and the controls "seemed totally ineffective." The gyroplane continued to descend and turn until it impacted a road running perpendicular to the runway about 50 feet north of the departure end. The pilot reported that the "cause of control malfunction is uncertain."
Probable cause
The malfunction of the flight controls for an undetermined reason, which resulted in a loss of control and in-flight collision with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA05CA195
- Event ID
- 20051007X01597
- Case number
- SEA05CA195
- 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: c76da1100b58ef7d1ccb5d088fd949dd151ed37a1224b9ee14627b44c245eda5; retrieved 2026-09-21T18:53:47.329Z.