NTSB investigations: Lycoming 0-320 series, 1982, VA
4 cases on aircraft whose registry engine model is Lycoming 0-320 series. 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
| 1964 | 5 |
|---|---|
| 1965 | 7 |
| 1966 | 7 |
| 1967 | 6 |
| 1968 | 10 |
| 1969 | 9 |
| 1970 | 5 |
| 1971 | 5 |
| 1972 | 6 |
| 1973 | 10 |
| 1974 | 4 |
| 1975 | 3 |
| 1976 | 8 |
| 1977 | 8 |
| 1978 | 4 |
| 1979 | 4 |
| 1980 | 6 |
| 1981 | 2 |
| 1982 | 4 |
| 1983 | 4 |
| 1984 | 6 |
| 1985 | 2 |
| 1986 | 5 |
| 1987 | 3 |
| 1988 | 2 |
| 1989 | 4 |
| 1990 | 1 |
| 1991 | 3 |
| 1992 | 2 |
| 1993 | 3 |
| 1994 | 3 |
| 1995 | 4 |
| 1996 | 2 |
| 1997 | 2 |
| 1998 | 1 |
| 1999 | 1 |
| 2000 | 4 |
| 2001 | 5 |
| 2002 | 8 |
| 2003 | 4 |
| 2004 | 1 |
| 2005 | 3 |
| 2007 | 8 |
| 2008 | 1 |
| 2009 | 6 |
| 2010 | 3 |
| 2011 | 1 |
| 2012 | 3 |
| 2013 | 3 |
| 2014 | 2 |
| 2015 | 4 |
| 2016 | 2 |
| 2017 | 5 |
| 2018 | 3 |
| 2019 | 4 |
| 2020 | 1 |
| 2021 | 3 |
| 2022 | 5 |
| 2023 | 3 |
| 2024 | 2 |
| 2025 | 3 |
| 2026 | 1 |
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\") = 1982
AND c.\"eventStateOrRegion\" = 'VA' 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'))
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") = 1982
AND c."eventStateOrRegion" = 'VA' 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'))
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 ATL83LA074Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Nelly'S Ford, VADuring takeoff roll the aircraft swerved to the left. The pilot applied full right rudder but was not able to straighten the aircraft. The pilot reduced the power and applied brakes. The aircraft collided with a fence at the end of the runway. Fifteen knot…NTSB ATL82FID13Accident · No injuriesFinal reportBeech B-19 · Franklin, VAN7698R crashed while on final approach, approximately one half mile east of Franklin airport. The father of the pilot stated that the aircraft had been taken without permission. The pilot holds an expired student pilot certificate. In addition, the pilot was…NTSB ATL83FA186Accident · 1 fatalField investigationFinal reportPiper PA-18 · Ft. Pickett, VAThe acft collided with the ground at ft Pickett shortly after a similiar acft was seen trying to approach blackstone army airfield. This acft made a go-around and disappeared to the south. The wrecked acft was found 3.5 miles south of the arpt 8 months later.…NTSB ATL82DA166Accident · Minor injuriesFinal reportPiper 22-160 · Lynchburg, VAThe pilot took off from newport news, VA on a VFR flight to south boston, VA. Later at dusk, he contacted the roanoke fss and asked for an "accurate fix" of his position. At that time, the pilot indicated that he was low on fuel. Fss personnel reported that…