LAX04LA203 · Schleicher ASW-20
Schleicher ASW-20 · Accident: airframe, component or system failure during initial climb
From Reno, NV to Reno, NV
Event
- NTSB case
- LAX04LA203
- 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
- 1 · 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
Schleicher ASW-20
- Aircraft type
- Schleicher ASW-20
- 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
- N126PS
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Reno, NVTo Reno, NV
- 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
- First occurrenceThe 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
- Airframe, component or system failure
- 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
- Stall/spin
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Airspeed(vso), not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The glider entered a stall and spin while attempting a return to runway maneuver following an overload failure of the towrope in the takeoff initial climb. During takeoff, the towrope between the tow plane and glider broke while the glider was about 300 feet above ground level. The glider pilot reversed course and attempted to return to the departure runway. The tow plane pilot said that when he looked back the glider was in a left turn with its heading passing through 030 degrees when the right wing suddenly dropped downwards and the glider appeared to descend vertically, nose down. The glider made about 1/2 a clockwise rotation, nose down, before it impacted the desert. The Safety Board Materials Laboratory examination of the towrope and safety link revealed: 1) The towrope was worn by abrasion and sunlight at the glider connection end, which had substantially reduced the strength of the rope at the failure location; 2) the worn end of the rope was about 60 percent weaker than the unworn end; 3) the towrope failed due to overloading at the knot; and 4) the unworn end of the towrope and the safety link met the tensile strength required by 14 CFR 91.309. The rope area around the knot connecting the towrope to the safety link was wrapped in a protective layer of duct tape, and therefore, the rope condition at the failure point could not be easily examined by the pilot during a towrope preflight inspection. Examination of the glider revealed no evidence of preimpact malfunction or failure of the flight control system. The tow plane pilot reported that there were gusty winds and turbulence present at the time. The ASW-20 Flight Manual includes a section titled "Dangerous Flight Attitudes," which contain a number of cautionary statements and warnings pertaining to stalled flight. Full control deflections will result in wing dropping, whereas full-deflected controls in opposite directions with stick pulled completely back will case rapid wing dropping. Initiated from turning flight the wing dropping is more rapid than from level flight. Full deflections of opposite rudder and aileron deflections will lead to a spin. The Federal Aviation Administration produced "Glider Handbook, AC 80-83-14" contained a very brief section about towrope inspection and essentially stated that the rope should be inspected for excessive wear without defining what that means.
Probable cause
the pilot's failure to maintain an adequate airspeed margin while performing a return to runway maneuver, which led to a stall and spin. Factors in the accident were: 1) the deteriorated condition of the glider towrope, which resulted in towrope failure during a critical phase of the tow; 2) the duct tape covering over the abraided portion of the failed rope end that made inspection of the rope difficult; and, 3) the gusty winds and turbulence.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX04LA203
- Event ID
- 20040511X00591
- Case number
- LAX04LA203
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: fd5ef5077d49787ac5fd3f6fbdc86c40992f280ebaa2e5f5cd79a364e72cd1e2; retrieved 2026-09-20T18:29:19.997Z.