NTSB investigations: Lycoming 0-320 series, 1982, OR
9 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 | 7 |
|---|---|
| 1965 | 10 |
| 1966 | 5 |
| 1967 | 6 |
| 1968 | 9 |
| 1969 | 6 |
| 1970 | 1 |
| 1971 | 6 |
| 1972 | 13 |
| 1973 | 9 |
| 1974 | 3 |
| 1975 | 6 |
| 1976 | 6 |
| 1977 | 5 |
| 1978 | 5 |
| 1979 | 9 |
| 1980 | 6 |
| 1981 | 5 |
| 1982 | 9 |
| 1983 | 2 |
| 1984 | 4 |
| 1985 | 2 |
| 1986 | 5 |
| 1987 | 3 |
| 1988 | 3 |
| 1989 | 4 |
| 1990 | 3 |
| 1991 | 4 |
| 1992 | 4 |
| 1993 | 4 |
| 1994 | 4 |
| 1995 | 7 |
| 1996 | 6 |
| 1997 | 5 |
| 1998 | 3 |
| 1999 | 7 |
| 2000 | 5 |
| 2001 | 4 |
| 2002 | 4 |
| 2003 | 5 |
| 2004 | 8 |
| 2005 | 8 |
| 2006 | 5 |
| 2007 | 9 |
| 2008 | 8 |
| 2009 | 4 |
| 2010 | 6 |
| 2011 | 2 |
| 2012 | 3 |
| 2014 | 1 |
| 2015 | 4 |
| 2017 | 4 |
| 2018 | 4 |
| 2019 | 3 |
| 2020 | 2 |
| 2021 | 3 |
| 2022 | 5 |
| 2023 | 1 |
| 2024 | 2 |
| 2025 | 1 |
| 2026 | 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 year(c.\"eventDate\") = 1982
AND c.\"eventStateOrRegion\" = 'OR' 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" = 'OR' 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 SEA83FYM01Accident · 1 fatalFinal reportBellanca 7GCBC · 1/4nm S. Of Peo, ORThe pilot and passenger were on a pleasure flight over the willamette river. The passenger stated that after following the river the aircraft began to climb and turn east. There was a sudden jolt and the plane began to spin and impacted the water.NTSB SEA83LA003Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-140 · Newberg, ORDuring a local flight, the pilot made 3 landings on a 2860 ft runway at sportsman airpark. He then landed on a 2300 ft turf runway at chehalem airport in light and variable wind conditions. While landing at chehalem, the aircraft rolled beyond the departure…NTSB SEA82FYM24Accident · 2 fatalFinal reportCessna 172P · 3nm Se Scappoos, ORThe acft struck & severed power lines strung between two 90-foot towers located about 1500 feet apart. The power lines were about 50 to 60 feet above the water at the lowest point of the line sag.NTSB SEA82DA145Accident · No injuriesFinal reportGulfstream American AA-5A · Medford, ORThe pilot reported that while landing, he flared too soon, touched down hard, and bounced. He reported that he made a power adjustment after bouncing, but landed hard again on the second touchdown. The aircraft was substantially damaged after the second…NTSB SEA82FYM22Accident · 3 fatalFinal reportPiper 24-140 · Enterprise, ORWitnesses observed an aircraft fly over the city of Enterprise, Oregon on a bright night with clear sky conditions. Reportedly, the aircraft was flying very erratic; and just as it disappeared from the witnesses' sight, an explosion andfireball were observed…NTSB SEA82FA117Accident · 1 fatalField investigationFinal reportPiper PA-28-161 · Portland, ORThe pilot, enrolled in a course for a commercial pilot certificate, was scheduled for a solo flight from seattle to bremerton, Washington and return. He departed at about 1300 PDT. At about 1635 PDT, residents near the crash site reported that they saw and…NTSB SEA82FYM19Accident · Minor injuriesFinal reportChampion 7GCAA · Independence, ORThe pilot reported that during a full stall landing, the aircraft veered to the left at the moment of touchdown. Full power was applied for a go-around, but reportedly, the pilot was unable to turn the aircraft back to the right toward the runway. After…NTSB SEA82DA079Accident · No injuriesFinal reportCessna 177 · Waldport, ORThe pilot elected to make a normal takeoff from a field of tall, wet grass. Acceleration was noted to be less than desired and the takeoff was aborted. The aircraft continued into a ditch in the overrun area.NTSB SEA82FA015Accident · 4 fatalField investigationFinal reportPiper PA-28-161 · Pleasant Hill, ORThe plane tookoff at 1505 PST on a local VFR pleasure flight with 4 occupants and about 48 gallons of fuel on board. The plane was estimated to be about 140 lbs over the maximum gross weight limit. At about 1622 PST, it was observed to break up in flight.…