SEA05LA044 · Smuz RAF 2000 GTX SE
Smuz RAF 2000 GTX SE · Accident: hard landing
From S5O · Auburn, WA to 1SO · Puyallup, WA
Event
- NTSB case
- SEA05LA044
- 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
Smuz RAF 2000 GTX SE
- Aircraft type
- Smuz RAF-2000
- 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
- N26AV
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From S5O · Auburn, WATo 1SO · Puyallup, WA
- 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
- Landing · flare/touchdown
- 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
- Hard landing
- 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
- Pilot in command › Flare, misjudged
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot said that he had approximately 1,800 hours of flight experience in helicopters, and was a flight instructor for the army. He was adding the gyroplane rating. He had 13 hours of training, and this was his first solo flight. He said that on his third landing, he was performing a power off 180 degree landing. He said that he flared one to two feet higher than planned, and he added a little power to "smooth out" the touchdown. When the power came in, the engine torque rotated the nose of the gyroplane to the right. The right main gear hit the ground, and the aircraft bounced back and fourth on its main landing gear. Subsequently, the gyroplane rolled onto its right side bending its blades, mast, and horizontal and vertical stabilizer.
Probable cause
The pilot's misjudged flare followed by an oscillation which damaged the aircraft.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA05LA044
- Event ID
- 20050208X00157
- Case number
- SEA05LA044
- 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: 00893899c70c51277225cb9d7af61e0103b5e12f9aac7112b5b92eec01bf9c15; retrieved 2026-09-22T06:18:13.474Z.