WPR12LA285 · Schweizer SGS233 A
Soar Truckee Schweizer SGS233 A · Accident: collision during takeoff/landing
From Truckee Tahoe Airport (TRK) to Truckee Tahoe Airport (TRK)
Event
- NTSB case
- WPR12LA285
- 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
Schweizer SGS233 A
- Aircraft type
- Schweizer SGS233
- 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
- N2061T
- Operator
- Soar Truckee
- Onboard fatalities
- Unknown
- Route
- From Truckee Tahoe Airport (TRK), Truckee, CATo Truckee Tahoe Airport (TRK), Truckee, CA
- 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
- Takeoff
- 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
- 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
- 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
During the takeoff roll, the glider encountered a strong gust of wind from behind the aircraft, which caused it to veer to the left. The pilot was able to release from the tow plane, but was unable to lift the left wing to an adequate height before it collided with a runway distance remaining sign. Although the pilot contended that the sign had been an obstruction from the time the airport crew had moved it from behind the takeoff area to in front of the takeoff area, the distance of the sign from the runway was consistent with parameters outlined in a Federal Aviation Administration Advisory Circular (AC) on the placement of runway distance remaining signs. At the time of the accident the wind was variable at 10 knots with gusts to 15 knots.
Probable cause
The pilot's failure to maintain control of the glider while taking off with a gusting wind, which resulted in the glider impacting a runway sign.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR12LA285
- Event ID
- 20120702X04032
- Case number
- WPR12LA285
- 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: eae01bd6049948ab30c70ea8a2c3003b3074d7bd35bfd4a6a902704f05e82ecb; retrieved 2026-09-15T18:41:18.703Z.