FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR09CA306 · Jenkins Jack GLASTAR SP

22 Jun 2009 · Coupeville, WA, United States

Jenkins Jack GLASTAR SP · Accident: hard landing

From AJ Eisenberg Airport (KOKH) to Coupville, WA

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
WPR09CA306
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

Jenkins Jack GLASTAR SP

Category
Airplane
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
N5617
Operator
Jenkins Jack
Onboard fatalities
Unknown
Route Narrative disagrees
From AJ Eisenberg Airport (KOKH), Oak Harbor, WATo Coupville, 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
Defining eventThe 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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

While the pilot was practicing off-airport landings in a field next to his home, he inadvertently allowed the airplane's nosewheel strut to hit the ground hard enough that it stuck into the soft grassy terrain and collapsed. The airplane then nosed over, resulting in substantial damage to the vertical stabilizer and rudder. The pilot reported no preaccident mechanical anomalies with the airplane’s flight control systems.

Probable cause

The pilot’s improper landing flare that resulted in a hard landing on soft/grassy terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR09CA306
Event ID
20090622X93729
Case number
WPR09CA306
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 160ab9b5ffabe210c99c733c38562168cb7057d393667018ea102ff844d06a30; retrieved 2026-09-15T11:31:54.157Z.