NTSB investigations: Lycoming 0-320 series, 1994
9 cases on aircraft whose registry engine model is Lycoming 0-320 series, where the first occurrence was “Overrun”. 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 | 15 |
|---|---|
| 1983 | 22 |
| 1984 | 19 |
| 1985 | 12 |
| 1986 | 5 |
| 1987 | 6 |
| 1988 | 10 |
| 1989 | 11 |
| 1990 | 14 |
| 1991 | 10 |
| 1992 | 15 |
| 1993 | 12 |
| 1994 | 9 |
| 1995 | 7 |
| 1996 | 3 |
| 1997 | 8 |
| 1998 | 4 |
| 1999 | 8 |
| 2000 | 8 |
| 2001 | 4 |
| 2002 | 9 |
| 2003 | 9 |
| 2004 | 7 |
| 2005 | 6 |
| 2006 | 5 |
| 2007 | 2 |
Where
Latest 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 year(c.\"eventDate\") = 1994
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\" = 340))
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 year(c."eventDate") = 1994
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" = 340))
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 CHI94LA326Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Brookfield, WIthe commercial pilot's poor planning/decision making. A related factor is the wet, grass runway selected for landing.NTSB CHI94LA305Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Jackson, MNthe pilot's selection of unsuitable terrain for takeoff and his delay in aborting the takeoff. Factors in the accident were the soft terrain and the ditch.NTSB NYC94LA157Accident · No injuriesLimited investigationFinal reportPiper PA-28 · Pennington, NJThe pilot's misjudged distance and speed during an aborted takeoff which resulted in an overrun. A contributing factor was the wet grass.NTSB FTW94LA228Accident · No injuriesLimited investigationFinal reportPiper PA-22-150 · Ravenna, TXThe pilot overshooting the landing and his failure to execute a G0-around. The wet grass was a factor.NTSB NYC94LA102Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · New Philadelphi, OHThe pilot's inadequate decision and his delay in aborting the takeoff, which resulted in an overrun of the runway and collision with obstaclesNTSB LAX94LA228Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Sonoma, CAThe pilot's failure to attain the proper touchdown point and his failure to initiate a go-around.NTSB CHI94LA171Accident · No injuriesLimited investigationFinal reportCessna 172N · Mackinac Island, MIExcessive airspeed and a failure to attain the proper touchdown point on the runway. Factors related to the accident were the wet runway and the fence which was contacted.NTSB SEA94LA102Accident · No injuriesLimited investigationFinal reportCessna 172L · Colville, WAThe pilot's failure to attain a proper touchdown point, and his excessive airspeed at the point of touchdown. Factors include the student pilot's lack of recent experience, and a ravine off the end of the runway.NTSB NYC94LA060Accident · No injuriesLimited investigationFinal reportCessna 172K · Dayton, OHthe pilot's failure to maintain directional control which resulted in a runway overrun. Factors are the pilot's improper recovery from a bounced landing, and his lack of experience.