NTSB investigations: Lycoming 0-320 series, 2002, AZ
13 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 | 6 |
| 1966 | 6 |
| 1967 | 5 |
| 1968 | 7 |
| 1969 | 3 |
| 1970 | 7 |
| 1971 | 11 |
| 1972 | 3 |
| 1973 | 6 |
| 1974 | 4 |
| 1975 | 7 |
| 1976 | 9 |
| 1977 | 5 |
| 1978 | 14 |
| 1979 | 9 |
| 1980 | 9 |
| 1981 | 10 |
| 1982 | 14 |
| 1983 | 2 |
| 1984 | 2 |
| 1985 | 7 |
| 1986 | 7 |
| 1987 | 2 |
| 1988 | 2 |
| 1989 | 9 |
| 1990 | 6 |
| 1991 | 8 |
| 1992 | 4 |
| 1993 | 3 |
| 1994 | 6 |
| 1995 | 5 |
| 1996 | 4 |
| 1997 | 10 |
| 1998 | 8 |
| 1999 | 5 |
| 2000 | 6 |
| 2001 | 7 |
| 2002 | 13 |
| 2003 | 6 |
| 2004 | 6 |
| 2005 | 9 |
| 2006 | 11 |
| 2007 | 10 |
| 2008 | 7 |
| 2009 | 6 |
| 2010 | 4 |
| 2011 | 3 |
| 2012 | 10 |
| 2013 | 5 |
| 2014 | 7 |
| 2015 | 1 |
| 2016 | 1 |
| 2017 | 3 |
| 2018 | 4 |
| 2019 | 4 |
| 2020 | 4 |
| 2021 | 6 |
| 2022 | 5 |
| 2023 | 4 |
| 2024 | 4 |
| 2025 | 1 |
| 2026 | 4 |
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\") = 2002
AND c.\"eventStateOrRegion\" = 'AZ' 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") = 2002
AND c."eventStateOrRegion" = 'AZ' 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 LAX03LA047Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-161 · Scottsdale, AZThe pilot's inadequate preflight inspection and failure to refuel the airplane resulting in a loss of engine power due to fuel starvation.NTSB LAX03LA015Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Queen Creek, AZa loss of engine power for undetermined reasons.NTSB LAX03FA005Accident · 1 fatalField investigationFinal reportGrumman AA-5A · Phoenix, AZfailure of the lubricating system resulting in a total loss of engine power and an off airport forced landing.NTSB LAX02LA274Accident · No injuriesLimited investigationFinal reportCessna 172I · Tucson, AZthe certified flight instructor's failure to maintain an adequate distance from a jet during taxi. A factor was the local/ground controller's failure to issue a safety alert or cautionary advisory to the pilot with regards to the jet blast of the departing…NTSB LAX02FA259Accident · No injuriesField investigationFinal reportCessna 172N · Mesa, AZAn electrical fire of unknown origin centered near the circuit breaker/throttle area of the instrument panel.NTSB LAX02LA241Accident · No injuriesLimited investigationFinal reportCessna 172P · Mesa, AZthe pilot of the other airplane'ss use of an excessive taxi speed and too close of a spacing interval to the Cessna 152, which resulted in an on-ground collision when the Cessna 152 abruptly stopped.NTSB LAX02LA199Accident · No injuriesLimited investigationFinal reportCessna 172M · Saint Johns, AZthe pilot's inadequate compensation for wind conditions resulting in a loss of directional control and collision with terrain. Related factors were the wind gusts, crosswind and soft terrain.NTSB LAX02FA191Accident · 3 fatalField investigationFinal reportPiper PA-23-160 · Rio Rico, AZa loss of engine power in the left engine for undetermined reasons, and the failure of the flying pilot to maintain an adequate single engine minimum control airspeed and aircraft control. Also causal was the decision of all three of the pilots to continue…NTSB LAX02LA153Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Green Valley, AZThe pilot's failure to identify the wind direction, which led to an attempted downwind landing approach that resulted in a hard landing and severe bounce. Also causal was the pilot's failure to promptly retract the flaps during the rejected landing after…NTSB LAX02LA106Accident · No injuriesLimited investigationFinal reportCessna 172M · Tucson, AZthe pilot's misjudged landing flare and improper bounced landing recovery.NTSB LAX02LA104Accident · No injuriesLimited investigationFinal reportCessna 172L · Bullhead City, AZThe pilot's failure to comply with maintenance/inspection requirements that resulted in a propeller failure.NTSB LAX02LA084Accident · No injuriesLimited investigationFinal reportCessna 172S · Glendale, AZThe pilot of the landing airplane failed to maintain directional control resulting in the on-ground collission.NTSB LAX02LA070Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Payson, AZFailure of the pilot to maintain directional control of the airplane. A contributing factor was the premature raising of the flaps.