NTSB investigations: Lycoming 0-320 series, IN
8 cases on aircraft whose registry engine model is Lycoming 0-320 series, where the first occurrence was “In flight collision with object”. 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
| 1984 | 1 |
|---|---|
| 1986 | 1 |
| 1987 | 1 |
| 1991 | 1 |
| 1997 | 1 |
| 1998 | 1 |
| 2001 | 1 |
| 2003 | 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\" = 'IN' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41508')
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\" = 220))
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" = 'IN' AND c."eventCountry" = 'USA'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41508')
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" = 220))
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 CHI03LA220Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Evansville, INThe pilot's failure to attain the proper touchdown point. The barrels were a factor.NTSB CHI01LA069Accident · No injuriesLimited investigationFinal reportCessna 172L · Culver, INthe proper glide path not attained by both pilots during a short field landing. The snow bank was a contributing factor.NTSB CHI98LA289Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Laporte, INwas the student pilot s inadequate compensation for the wind conditions he encountered during the landing phase. A factor in this accident was the pilot s lack of total experience.NTSB CHI97LA144Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-140 · Arcadia, INimproper planning/decision by the pilot. Factors related to the accident were: the pilot's selection of the wrong runway for takeoff, and the resultant tailwind.NTSB CHI92FA013Accident · 2 fatalField investigationFinal reportPiper PA28-140 · Lafayette, INFailure of the pilot to compensate for wind conditions during initial climb. Factors associated with the accident are crosswind conditions and a dark night light condition.NTSB CHI87LA215Accident · No injuriesLimited investigationFinal reportPiper PA-22-150 · Belleville, INThe aircraft was returning to an unlighted private airstrip after a local pleasure flight. The sun had set but, according to the pilot, the sky was still illuminated. The pilot stated he was able to set up an approach, but when established on final he 'lost…NTSB CHI86LA106Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Veedersburg, INThe pilot was attempting a short field takeoff from a 1080 foot wheat field that he had mistaken for a private airstrip 1 1/2 miles to the northeast. The pilot said the engine had a slight RPM loss and then developed full power but he was unable to clear the…NTSB CHI85LA024Accident · Minor injuriesLimited investigationFinal reportPiper PA28-151 · Lake Village, INThe plt reported that he was on final apch to land on a wet, sod rwy when he noticed a flock of geese over the apch end. He added power to fly over the geese then proceeded to touchdown further down the rwy than what he had planned. Due to his speed & the wet…