WPR10CA215 · PZL-Swidnik PW-5
Tucson Soaring Club PZL-Swidnik PW-5 · Accident: electrical system malfunction/failure en route
From El Tiro Gliderport (AZ67) to El Tiro Gliderport (AZ67)
Event
- NTSB case
- WPR10CA215
- 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
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
- N500JN
- Operator
- Tucson Soaring Club
- Onboard fatalities
- Unknown
- Route
- From El Tiro Gliderport (AZ67), El Tiro, AZTo El Tiro Gliderport (AZ67), El Tiro, AZ
- 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
- En route · cruise
- 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
- Electrical system malfunction/failure
- 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
- Environmental issues › Conditions/weather/phenomena
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The glider pilot had been checked out in the glider the day of the accident and it was the first time she had flown this make and model. Approximately two hours into the flight, she smelled a burning rubber smell before all of the electronics ceased operating. She turned back to her departure airport, but due to her lack of experience she was unable to find a thermal and the glider continued to descend. During the forced off-field landing, the glider impacted trees and desert brush. Postaccident examination of the glider revealed that the cable supplying power to the removable data logger was routed improperly and had rubbed against a metal computer port, causing an electrical short and disabling the glide computer, global positioning system, and the vertical speed indicator.
Probable cause
The pilot's inability to find thermal lift. Contributing to the accident was the failure of a computer that provided glide information and vertical speed instrumentation as a result of an improperly routed electrical cable that caused a short in the electrical system and the pilot's lack of experience in the glider.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR10CA215
- Event ID
- 20100426X90849
- Case number
- WPR10CA215
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2010-04-26.
- API snapshot SHA-256: 54f79f6aeee09260c9b943f6f88cc9a92bf1a8b935824ee86a5c69dede61fc45; retrieved 2026-09-15T13:55:15.435Z.