NTSB investigations: Lycoming 0-540 series, 2002, CA
4 cases on aircraft whose registry engine model is Lycoming 0-540 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 | 18 |
|---|---|
| 1965 | 13 |
| 1966 | 25 |
| 1967 | 12 |
| 1968 | 14 |
| 1969 | 7 |
| 1970 | 5 |
| 1971 | 14 |
| 1972 | 7 |
| 1973 | 9 |
| 1974 | 8 |
| 1975 | 10 |
| 1976 | 10 |
| 1977 | 9 |
| 1978 | 10 |
| 1979 | 10 |
| 1980 | 7 |
| 1981 | 5 |
| 1982 | 4 |
| 1983 | 4 |
| 1984 | 5 |
| 1985 | 7 |
| 1986 | 2 |
| 1987 | 4 |
| 1988 | 7 |
| 1989 | 7 |
| 1990 | 5 |
| 1991 | 3 |
| 1992 | 5 |
| 1993 | 4 |
| 1994 | 5 |
| 1995 | 1 |
| 1996 | 10 |
| 1997 | 3 |
| 1998 | 5 |
| 1999 | 2 |
| 2000 | 2 |
| 2001 | 6 |
| 2002 | 4 |
| 2003 | 1 |
| 2004 | 2 |
| 2005 | 8 |
| 2006 | 3 |
| 2007 | 3 |
| 2008 | 3 |
| 2009 | 10 |
| 2010 | 5 |
| 2011 | 3 |
| 2012 | 2 |
| 2013 | 1 |
| 2014 | 5 |
| 2015 | 1 |
| 2016 | 1 |
| 2017 | 1 |
| 2018 | 2 |
| 2019 | 2 |
| 2021 | 2 |
| 2022 | 2 |
| 2023 | 1 |
| 2024 | 2 |
| 2025 | 4 |
| 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\") = 2002
AND c.\"eventStateOrRegion\" = 'CA' 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 ('41532'))
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" = 'CA' 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 ('41532'))
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 LAX03FA051Accident · 2 fatalField investigationFinal reportPiper PA-24-250 · Anaheim Hills, CAthe pilot's encounter with forecast severe turbulence during an inadvertent penetration of an intense weather cell, which resulted in the pilot exceeding the design structural limits of the airplane. A factor in the accident was the pilot's inadequate…NTSB LAX03LA012Accident · No injuriesLimited investigationFinal reportPiper PA-28-235 · Van Nuys, CAfuel starvation due to the pilot's mismanagement of the fuel system and failure to select a tank containing fuel.NTSB LAX02LA095Accident · No injuriesLimited investigationFinal reportPiper PA-24-250 · San Jose, CAThe pilot's inadequate planning and improper fuel consumption calculation, which resulted in fuel exhaustion.NTSB LAX02LA065Accident · No injuriesLimited investigationFinal reportPiper PA-24-250 · Oceano, CAA loss of engine power due to the separation of the mixture control cable from the mixture control arm of the carburetor. The mixture cable separation was due to maintenance personnel's failure to secure the mixture control cable away from the nose landing…