WPR26LA203 · PZL-Swidnik PW-5
Puget Sound Soaring Association PZL-Swidnik PW-5 · Accident: system/component malfunction/failure (non-power) en route
From Ephrata Municipal Airport (KEPH) to an unrecorded destination
Event
- NTSB case
- WPR26LA203
- 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
- Event fatalities
- Unknown
- 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
PZL-Swidnik PW-5
- Aircraft type
- PZL Swidnik PW-5
- 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
- N157AJ
- Operator
- Puget Sound Soaring Association
- Onboard fatalities
- Unknown
- Route
- From Ephrata Municipal Airport (KEPH), Ephrata, WATo not recorded
- Aircraft age
- About 28 years (built 1998)
- 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
- En route
- 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
- System/component malfunction/failure (non-power)
- 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 structures
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that he and three club members assembled the glider before the accidewnt flight, following the manufacturer's assembly procedures. After a preflight inspection and positive control check, the glider was towed and released. Approximately 10 minutes later, the pilot heard a sharp cracking sound and elected to return to the airport and land. A postflight examination revealed substantial damage to the wing spar root, wing, and fuselage. During disassembly of the glider following the accident, the assembly crew noted that the right main wing pin was in its halfway position and had not been secured. The left main wing pin was fully inserted and secured. They noted that the in-flight structural damage was likely due to the right main wing pin not being fully seated and secured during assembly.
Probable cause
The pilot’s failure to ensure the proper preflight assembly of the glider's wing attachment system, which resulted in substantial damage to the wing structure during flight.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR26LA203
- Event ID
- 20260601203101
- Case number
- WPR26LA203
- 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, cause areas. 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: 7612a774e9724f990196228a5494fefa5f7de1e372e00469d9ca0cc0f5a3c0aa; retrieved 2026-09-16T21:37:06.665Z.