NTSB investigations: Lycoming 0-320 series, 2000
8 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
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 year(c.\"eventDate\") = 2000
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") = 2000
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 SEA01LA012Accident · No injuriesLimited investigationFinal reportCessna 172P · Waldron Island, WAThe pilot's improper distance/speed during the approach, which lead to an overrun during the landing roll and subsequent collision with trees. A factor was the trees beyond the upwind end of the runway.NTSB LAX01LA021Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Half Moon Bay, CAA local windshear condition that exceeded the airplane's climb performance capability during landing approach and resulted in the runway overrun during an attempted go-around.NTSB ATL01LA006Accident · No injuriesLimited investigationFinal reportCessna 172K · Indiantown, FLThe pilot had excessive airspeed, misjudged the landing distance, and did not perform a go-around, which resulted in a nose over. The ditch was a contributing factor.NTSB CHI00LA259Accident · No injuriesLimited investigationFinal reportCessna 172M · Harbor Springs, MIthe pilot's long touchdown, and inadequate braking to stop on the runway. Factors relating to this accident were the pilot's improper in-flight planning and decision resulting in the long touchdown, and the fence.NTSB SEA00LA125Accident · No injuriesLimited investigationFinal reportCessna 172I · Sandy, ORThe pilot's failure to attain the proper touchdown point for landing, and his failure to go around from the improperly executed approach. Factors included the pilot's failure to attain the proper glidepath on the approach, a short landing runway, and…NTSB CHI00LA192Accident · No injuriesLimited investigationFinal reportCreed Lancair 235 · Hot Springs, SDthe failure of the pilot to select the correct runway for takeoff. Factors to the accident were the inadequate preflight planning/preparation, the aborted takeoff not performed, and the tailwind.NTSB CHI00LA128Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Fulton, MOthe pilot's poor inflight planning which resulted in exceeded the proper touchdown point on the runway. A factor associated with the accident was the ditch that the airplane contacted.NTSB NYC00LA109Accident · No injuriesLimited investigationFinal reportCessna 172 · North Adams, MAThe pilot's failure to obtain the proper touchdown point. A factor was a tailwind.