SEA02LA176 · Eells Air Command 503
Eells Air Command 503 · Accident: hard landing
From Prineville Airport (S39) to S39
Event
- NTSB case
- SEA02LA176
- 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
Eells Air Command 503
- Aircraft type
- Eells AIR COMMAND 503
- 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
- N25069
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Prineville Airport (S39), Prineville, ORTo S39
- 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
- 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 › Airspeed, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The student pilot reported that he flew the gyroplane down to about 11 feet above the runway surface for landing. He then pulled the control stick back to level the aircraft. The student pilot stated that the aircraft ballooned a little so he pushed the stick forward. At this point, the aircraft was about 12 feet above the runway and it began to rapidly descend. The student pilot applied power to arrest the sink rate, however, the rotor speed had decayed and the aircraft landed hard with no forward airspeed. After touchdown, the aircraft bounced and tilted to the left. The rotors contacted the runway surface and the aircraft came to rest on its left side. The student pilot reported no mechanical failures or malfunctions with the aircraft at the time.
Probable cause
The student pilot's failure to maintain airspeed resulting in a hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA02LA176
- Event ID
- 20020917X02631
- Case number
- SEA02LA176
- 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: cf8e88fdeb6f59244e1ae9fe2507e0a48f3e69e197823cb64ea9766b7db12267; retrieved 2026-09-22T10:16:15.956Z.