NTSB investigations: Lycoming 0-320 series, 1998, WA
11 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 | 11 |
| 1966 | 7 |
| 1967 | 12 |
| 1968 | 4 |
| 1969 | 5 |
| 1970 | 4 |
| 1971 | 6 |
| 1972 | 8 |
| 1973 | 4 |
| 1974 | 1 |
| 1975 | 6 |
| 1976 | 10 |
| 1977 | 2 |
| 1978 | 12 |
| 1979 | 10 |
| 1980 | 9 |
| 1981 | 14 |
| 1982 | 8 |
| 1983 | 7 |
| 1984 | 6 |
| 1985 | 6 |
| 1986 | 3 |
| 1987 | 5 |
| 1988 | 5 |
| 1989 | 8 |
| 1990 | 4 |
| 1991 | 8 |
| 1992 | 8 |
| 1993 | 3 |
| 1994 | 11 |
| 1995 | 8 |
| 1996 | 6 |
| 1997 | 8 |
| 1998 | 11 |
| 1999 | 11 |
| 2000 | 9 |
| 2001 | 9 |
| 2002 | 8 |
| 2003 | 7 |
| 2004 | 16 |
| 2005 | 5 |
| 2006 | 4 |
| 2007 | 1 |
| 2008 | 11 |
| 2009 | 7 |
| 2010 | 6 |
| 2011 | 7 |
| 2012 | 7 |
| 2013 | 6 |
| 2014 | 3 |
| 2015 | 1 |
| 2016 | 5 |
| 2017 | 4 |
| 2018 | 4 |
| 2019 | 2 |
| 2020 | 3 |
| 2021 | 4 |
| 2022 | 4 |
| 2023 | 1 |
| 2024 | 3 |
| 2025 | 2 |
| 2026 | 6 |
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\") = 1998
AND c.\"eventStateOrRegion\" = 'WA' 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") = 1998
AND c."eventStateOrRegion" = 'WA' 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 SEA99LA025Accident · No injuriesLimited investigationFinal reportCessna 177 · Bellingham, WAInadequate preflight planning/preparation, and the pilot's failure to maintain altitude. VFR flight into IMC conditions and cloudy weather conditions were factors.NTSB SEA99LA019Accident · No injuriesLimited investigationFinal reportRobinson R-22B · Carnation, WAThe pilot's failure to maintain clearance with a wire. Related factors were the pilot's performance of a low pass, a transmission wire, and difficulty encountered by the pilot in detecting the wire visually.NTSB SEA98LA191Accident · No injuriesLimited investigationFinal reportCessna 172L · Puyallup, WAThe pilot-in-command's failure to refuel en-route resulting in fuel exhaustion. Contributing factors were a vehicle (in the landing path) and dark night conditions.NTSB SEA98FA170Accident · 1 fatalField investigationFinal reportCessna 172L · Anacortes, WATerrain clearance was not maintained. A low ceiling and the pilot's inadequate in-flight planning/decision were factors.NTSB SEA98LA169Accident · No injuriesLimited investigationFinal reportWiles S1-C · Yelm, WAFuel exhaustion due to overflying an intermediate fuel stop. Factors include high grass in the forced landing area.NTSB SEA98LA144Accident · No injuriesLimited investigationFinal reportCessna 172P · Seattle, WAThe student pilot's failure to maintain directional control of the aircraft. Related factors were the student pilot's lack of total experience, and airport signs in the accident area.NTSB SEA98LA133Accident · No injuriesLimited investigationFinal reportBeech 23 · Oakville, WALoss of power due to the failure of an exhaust valve, and overloading of the landing gear. Factors include the failure of maintenance personnel to verify proper compliance with an Airworthiness Directive related to the exhaust valve, and soft terrain.NTSB SEA98LA111Accident · No injuriesLimited investigationFinal reportKoster Murphy Rebel · Arlington, WAThe pilot/builder's attachment inadequate installation of the aileron control pushrods to the control stick assembly, resulting in the ailerons deflecting in a direction opposite of the input applied by the pilot. Also causal was the pilot's inadequate…NTSB SEA98LA070Accident · No injuriesLimited investigationFinal reportCessna 172N · Enumclaw, WAThe pilot's continued VFR flight into IMC conditions and his failure to maintain clearance from terrain. Clouds and mountainous terrain were a factor.NTSB SEA98LA071Accident · No injuriesLimited investigationFinal reportCessna 172M · Ocean Shores, WAThe pilot's failure to maintain clearance from a light standard (utility pole) just off the edge of the parking ramp. Factors include a light standard placed near the edge of the parking ramp.NTSB SEA98LA068Accident · No injuriesLimited investigationFinal reportPiper PA-28-160 · Monroe, WAFuel starvation due to the flight instructor's improper in-flight decision to simulate an engine failure by pulling the mixture control toward the lean position until the engine shut down, and his failure to return the mixture to the rich position until after…