GAA18CA382 · PZL-Swidnik PW 5
PZL-Swidnik PW 5 · Accident: collision during takeoff/landing
From Soaring Club of Houston Gliderport (89TA) to Soaring Club of Houston Gliderport (89TA)
Event
- NTSB case
- GAA18CA382
- 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
- N123PW
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Soaring Club of Houston Gliderport (89TA), Waller, TXTo Soaring Club of Houston Gliderport (89TA), Waller, TX
- Aircraft age
- About 22 years (built 1996)
- 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
- 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
- Collision during takeoff/landing
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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
- Environmental issues › Physical environment
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the glider pilot, about 15 minutes into the flight, the glider had reached 2,000 ft above ground level (agl), but he was unable to find more lift. The glider was about 1.5 miles west of the airfield, and he decided to continue west in search of lift under a cloud formation. He did not find lift and returned to his previous position 1.5 miles west of the airfield at 1,200 ft agl. The pilot decided to land off the airfield.
The pilot entered the pattern using the glider's spoilers and turned from the downwind leg to the base leg at 700 ft agl. He reported that he allowed the glider's flightpath to take him .5 mile too far downwind. During the base leg of the pattern, he reported that he had to "crab the airplane into the wind" to avoid being pushed further downwind. On final, the glider descended rapidly and collided with trees.
The glider sustained substantial damage to the left wing spar.
The pilot reported that the wind at the time of the accident was from 190° at 15 knots. He attempted to land on a heading of 170°.
The pilot reported that there were no mechanical malfunctions or failures with the glider that would have precluded normal operation.
Probable cause
The glider pilot’s failure to maintain clearance from trees during landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA18CA382
- Event ID
- 20180624X33458
- Case number
- GAA18CA382
- 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: cf394c1416768d1bbb264b9fd234c13f24423f9f599cc2906044fd8202fb01fc; retrieved 2026-09-16T07:38:18.056Z.