NTSB investigations: Let BLANIK L-13, MI
7 cases on aircraft the registry lists as Let BLANIK L-13. 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
| 1981 | 1 |
|---|---|
| 1984 | 1 |
| 1985 | 1 |
| 1986 | 1 |
| 1990 | 1 |
| 1991 | 1 |
| 2001 | 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.\"eventStateOrRegion\" = 'MI' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1360306'))
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."eventStateOrRegion" = 'MI' AND c."eventCountry" = 'USA'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1360306'))
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 CHI01LA277Accident · Serious injuriesLimited investigationFinal reportBlanik L-13 · Marlette, MIGround crew personnel improperly connected the tow winch cable prior to takeoff which resulted in one side of the winch cable coming disconnected. Factors associated with the accident were the ditch and the tree branch which the airplane contacted.NTSB CHI91LA231Accident · No injuriesLimited investigationFinal reportLet L-13 · Gregory, MIA collision with wires after the glider overshot the landing area due to inadvertent lowering of the flaps and no use of spoilers.NTSB CHI90LA140Accident · No injuriesLimited investigationFinal reportLet L-13 · Oxford, MIThe glider pilot's failure to maintain adequate aircraft control during the touchdown and landing roll. The poorly executed approach to landing, and rough/uneven terrain were contributing factors in this accident.NTSB CHI86LA133Accident · No injuriesLimited investigationFinal reportLet L-13 · Gregory, MIThe pilot stated that during landing the right wing of the glider touched the ground causing a right turn. The left wing then caught on a truck tire causing a 70 degree turn to the left. The glider was stopped when the right wing struck a barn. He was later…NTSB CHI85LA247Accident · No injuriesLimited investigationFinal reportLet L-13 · Gregory, MIThe glider landed in trees after the spoiler 'popped' open in flt during a towed takeoff. The tow plane released the glider at 300 ft AGL after the spoilers opened. The plt landed without retracting the spoilers. Two FAA inspectors stated that they checked…NTSB CHI84LA409Accident · No injuriesLimited investigationFinal reportLet L-13 · Gregory, MIAccording to the CFI the glider was at about 500 ft AGL on base leg when a downdraft caused the acft to descend and touch down 50 ft short of the rwy.NTSB CHI81DEC41Accident · Minor injuriesClosedBlanik L-13 · Oxford, MI