NTSB investigations: Let BLANIK L-13
19 cases on aircraft the registry lists as Let BLANIK L-13, where the first occurrence was “Undershoot”. 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
| 1982 | 1 |
|---|---|
| 1983 | 1 |
| 1984 | 3 |
| 1985 | 2 |
| 1986 | 3 |
| 1991 | 2 |
| 1996 | 1 |
| 1997 | 2 |
| 1999 | 2 |
| 2000 | 1 |
| 2005 | 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 ('1360306')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 390))
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 ('1360306')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 390))
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 MIA05LA077Accident · Serious injuriesLimited investigationFinal reportLet Blanik L-13 · DeLand, FLThe failure of the pilot to maintain sufficient airspeed during landing, resulting in an inadvertent stall, undershoot and collision with the ground.NTSB MIA00LA165Accident · No injuriesLimited investigationFinal reportLet L-13 · Pensacola, FLThe student's failure to maintain the proper landing pattern altitude resulting in an undershoot during landing and collision with a fence. A factor in the accident was the pilot's failure to realize the spoilers were still deployed during the undershoot.NTSB FTW99LA243Accident · Serious injuriesLimited investigationFinal reportLet Blanik L-13 · Jonesboro, ARThe pilot's misjudgment of distance/altitude during the final approach to landing, resulting in an undershoot, and collision with a power line pole.NTSB MIA99LA193Accident · No injuriesLimited investigationFinal reportLet Blanik L-13 · Monroe, GAthe pilot-in command's improper handling and inflight decisions resulting in an undershoot of the intended landing runway. The pilot-in-command then failed to maintain airspeed, which resulted in a stall and the right wingtip impacting the ground.NTSB MIA98LA023Accident · No injuriesLimited investigationFinal reportLet L-13 · Elkin, NCThe instructor's pilot's misjudgment of altitude and distance, and his inadequate compensation for the wind conditions. Unfavorable winds and a fence were contributing factors.NTSB LAX97LA165Accident · Serious injuriesLimited investigationFinal reportLet Blanik L-13 · Hemet, CAthe pilot's failure to adjust his traffic pattern to compensate for local atmospheric conditions.NTSB LAX96LA158Accident · No injuriesLimited investigationFinal reportLet Blanik L-13 · Jean, NVthe pilot's poorly planned approach. The flight's encounter with a downdraft is a factor in this accident.NTSB LAX91LA349Accident · No injuriesLimited investigationFinal reportLet L-13 · Byron, CAThe on ground collision with a hidden ditch not visible to the pilot during the landing roll out phase of a forced landing.NTSB SEA91LA147Accident · No injuriesLimited investigationFinal reportLet L-13 · Driggs, IDThe pilot misjudged his distance and altitude to the runway during the approach and failed to attain the proper touchdown point for landing. His lack of experience in the make and model of glider was a related factor.NTSB CHI87LA002Accident · No injuriesLimited investigationFinal reportLet L-13 · White Bear Lake, MNThe plt reported that he entered the traffic pattern for rwy 30 at aprx 900 ft and completed a right turn to base. The plt stated that while on base, he realized the aircraft was too high and deployed the spoilers halfway. As he turned to final, he stated…NTSB SEA86LA209Accident · No injuriesLimited investigationFinal reportLet L-13 · Issaquah, WAPlt undershot approach after encountering downdraft, collided with perimeter fence.NTSB MIA86LA166Accident · Minor injuriesLimited investigationFinal reportLet L-13 · Pensacola, FLThe pvt glider plt with a total of 47 hours of flt time departed his local field with one passenger. At about 2000 ft AGL he disengaged the aero tow and proceeded to glide for about one hour. The plt stated that when he started back to his local airport and…NTSB ATL85LKG11Accident · Minor injuriesFinal reportLet L-13 · Huntsville, ALThe commercial plt was in training for a glider rating & was on a supervised solo flt to practice a landing. During the traffic pattern, he rolled out hi on final & extended the spoilers to adjust to the desired glide path, then retracted the spoilers to the…NTSB ATL85FMG06Accident · No injuriesFinal reportLet L-13 · Chester, SCThe glider landed about 150 ft short of the rwy on the plts 1st solo in this acft. He said he noticed a rapid drop in alt at 55 mph on final approach and began to change spoiler position to compensate. He complained that the stiffness of the operation of the…NTSB MIA85LA030Accident · No injuriesLimited investigationFinal reportLet L-13 · Homestead, FLAccording to the plt, a downdraft was encountered on base leg causing the acft to descend and decelerate. Unable to reach the rwy the glider landed in an orchard.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 LAX84LA386Accident · Minor injuriesLimited investigationFinal reportLet L-13 · Llano, CAAccording to the plt, the glider did not sink as fast as expected on the downwind leg, so he extended flaps to 30 to 40 deg, used spoilers & extended the downwind. On base leg he entered an area of high sink; therefore, he closed the spoilers & angled toward…NTSB ATL83LA226Accident · No injuriesLimited investigationFinal reportLet L-13 · Warrenton, VAThe pilot stated that this was his third flt of the day and his first in this particular acft. He misjudged his glide path and landed about 100 feet short of the runway. The glider rolled into the creek and the nose impacted about 2 feet below the top of the…NTSB LAX82DA254Accident · No injuriesFinal reportBlanik L-13 · Murrieta, CAPilot landed short of runway in a glider and impacted the ground at high speed with high sink rate. He had released early from an aerotow and descended at high airspeed with dive brakes open which accelerated his rate of sink. He was not injured in the…