NTSB investigations: Lycoming 0-320 series, OK
6 cases on aircraft whose registry engine model is Lycoming 0-320 series, where the first occurrence was “Loss of engine power”. 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
| 1993 | 1 |
|---|---|
| 1996 | 1 |
| 2001 | 1 |
| 2002 | 1 |
| 2003 | 2 |
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\" = 'OK' 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\" = 350))
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" = 'OK' 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" = 350))
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 FTW04LA015Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Henryetta, OKA loss of engine power due to fuel starvation. A contributing factor was the inadequate inflight planning procedures for a cross country flight.NTSB FTW03LA230Accident · Minor injuriesLimited investigationFinal reportPiper PA-12 · Wayne, OKA loss of engine power due to fuel exhaustion as a result of the pilot's failure to refuel. Factors were the lack of suitable terrain for the forced landing.NTSB FTW02LA133Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-140 · Owasso, OKThe loss of engine power as a result of the pilot's failure to remove the engine cowling plugs during the preflight inspection. A contributing factor was lack of suitable terrain for the forced landing.NTSB FTW01LA175Accident · No injuriesLimited investigationFinal reportPiper PA-28 · Tulsa, OKthe partial loss of engine power for an undetermined reason. A factor was the lack of suitable terrain for the forced landing.NTSB FTW97LA062Accident · No injuriesLimited investigationFinal reportLuscombe 8E · Ardmore, OKThe loss of engine power for undetermined reasons. A factor was the lack of suitable terrain for the pilot to execute the forced landing.NTSB FTW93LA248Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Tulsa, OKThe loss of engine power and engine fire for undetermined reasons.