SEA08CA122 · Schempp-Hirth Nimbus-4M
Schempp-Hirth Nimbus-4M · Accident: loss of control in flight during initial climb
From Ephrata Municipal Airport (KEPH) to an unrecorded destination
Event
- NTSB case
- SEA08CA122
- 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
Schempp-Hirth Nimbus-4M
- Aircraft type
- Schempp Hirth NIMBUS-4
- Category
- Glider
- 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
- N747JN
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Ephrata Municipal Airport (KEPH), Ephrata, WATo 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
- 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
- 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
- Substantial
Cause areas
- Aircraft › Aircraft systems
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
This was the first flight after removal of the glider from storage and its reassembly. The pilot reported that during takeoff initial climb, the glider started to roll to the left despite his control inputs. He decided to abort the takeoff and land straight ahead while attempting to maintain control of the powered glider. Subsequently, the left wing struck the ground, and the glider began to cartwheel. Examination of the airframe revealed that the left and right wings were structurally damaged and the empennage was partially separated. Examination of the flight control system revealed that the left aileron connecting rod was disconnected at the fuselage/wing quick connection point and was undamaged. The pilot stated that during assembly of the glider prior to the flight, the left aileron control tube was inadvertently not attached, and that he did not verify that all flight controls moved free and correct prior to takeoff.
Probable cause
The pilot's inadequate preflight inspection and his failure to connect the left aileron control rod during assembly.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA08CA122
- Event ID
- 20080602X00759
- Case number
- SEA08CA122
- 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, 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: e5c3d9f6e4c02de0a6cbf8cc530181cdf3540840b0082255956ba8b1d53fa92d; retrieved 2026-09-15T09:42:18.966Z.