NTSB investigations: Let L 33 SOLO
14 cases on aircraft the registry lists as Let L 33 SOLO. Aircraft are matched to the registry by N-number and event date, checked against the reported serial number, make and model, so older matches can be wrong.
Cases per year
| 1994 | 1 |
|---|---|
| 1999 | 1 |
| 2000 | 1 |
| 2001 | 2 |
| 2005 | 1 |
| 2007 | 1 |
| 2010 | 1 |
| 2011 | 3 |
| 2014 | 1 |
| 2020 | 1 |
| 2024 | 1 |
Where
Open the mapLatest cases
Query with SQL
duckdb -csv -c "SELECT c.\"ntsbNumber\", c.\"eventDate\", c.\"eventType\", c.\"eventCity\", c.\"eventStateOrRegion\", a.n_number, a.\"aircraftMake\", a.\"aircraftModel\", c.\"highestInjuryLevel\", c.\"totalFatal\", c.\"completionStatus\", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c.\"mKey\" AND a.position = 1
WHERE c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1360309'))
ORDER BY c.\"eventDate\" DESC, c.\"ntsbNumber\" DESC"Prints the whole list as CSV. It reads the release’s Parquet files over HTTPS, so there’s nothing to download first. Install DuckDB to run it.
SELECT c."ntsbNumber", c."eventDate", c."eventType", c."eventCity", c."eventStateOrRegion", a.n_number, a."aircraftMake", a."aircraftModel", c."highestInjuryLevel", c."totalFatal", c."completionStatus", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c."mKey" AND a.position = 1
WHERE c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1360309'))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESCRun it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.
NTSB CEN24LA331Accident · No injuriesClass 4 · LimitedFinal reportLet L 33 Solo · Kingman, KSThe pilot’s loss of control on short final.NTSB WPR20CA151Accident · No injuriesClass 4 · Data collectionFinal reportLet L 33 Solo · Arlington, WAThe loss of lift while on final approach which resulted in a hard off-airport landing.NTSB ERA14LA199Accident · Serious injuriesLimited investigationFinal reportAircraft Industries A.S. L33 Solo · Bunn, NCThe pilot’s failure to maintain airspeed while approaching the airport, which resulted in a stall/mush.NTSB ERA11CA465Accident · No injuriesData collectionFinal reportLet L 33 Solo · Wakefield, VAThe glider’s encounter with atmospheric conditions where the lift was not sufficient to maintain flight, resulting in an off-airport landing.NTSB WPR11CA231Accident · No injuriesData collectionFinal reportLet L 33 Solo · Sparks, NVThe pilot’s failure to maintain an adequate airspeed during landing, which resulted in an aerodynamic stall.NTSB ERA11LA234Accident · 1 fatalLimited investigationFinal reportLet L 33 Solo · New Castle, VAPilot incapacitation shortly after takeoff for unknown reasons.NTSB WPR10CA389Accident · No injuriesData collectionFinal reportLet L 33 Solo · Adelanto, CAThe pilot’s inability to make it to the airport as a result of his inadequate planning for the gusting headwinds.NTSB NYC08CA031Accident · No injuriesData collectionFinal reportLet L-33 Solo · Louisburg, NCThe flight's encounter with an area of no thermal lift. Contributing factors to the accident were the pilot's inadvertent selection of unsuitable terrain with a hidden obstruction.NTSB CHI05CA255Accident · No injuriesData collectionFinal reportLet L 33 Solo · Stanton, MNThe pilot's failure to maintain a proper descent rate during landing due to the wind gusts. The wind gusts were a factor.NTSB NYC02LA027Accident · No injuriesLimited investigationFinal reportLet Blanik L 33 Solo · Windsor, VAThe pilot's inadequate preflight inspection, which resulted in a loose battery charger becoming entangled in the rudder pedals during a spin recovery, and a subsequent overstress of the glider. Factors included the loose battery charger, and the non-standard…NTSB NYC01LA231Accident · No injuriesLimited investigationFinal reportLet 33 · Bardstown, KYThe pilot's improper flare, which resulted in a nose-first, hard touchdown.NTSB NYC00LA147Accident · No injuriesLimited investigationFinal reportLet L 33 Solo · Waynesville, OHThe pilot's failure to maintain aircraft control. Factors were gusty winds, and the pilot's lack of experience in the make and model accident glider.NTSB NYC99LA215Accident · No injuriesLimited investigationFinal reportLet L-33-SOLO · Wellington, OHThe pilot's failure to attain the proper touchdown point. A factor related to the accident was a downdraft.NTSB NYC94LA081Accident · No injuriesLimited investigationFinal reportLet Super Blanik L-33 · New Castle, VAThe pilot's improper use of the flight controls resulting in failure to maintain a proper descent rate during the approach for landing. A factor in this accident was the pilot's lack of total experience in this type of glider.