Fatal NTSB investigations: Lycoming 0-540 series, 1983
8 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 | 5 |
|---|---|
| 1965 | 4 |
| 1966 | 2 |
| 1967 | 7 |
| 1968 | 7 |
| 1969 | 6 |
| 1970 | 10 |
| 1971 | 3 |
| 1972 | 5 |
| 1973 | 2 |
| 1974 | 4 |
| 1975 | 3 |
| 1976 | 4 |
| 1977 | 7 |
| 1978 | 8 |
| 1979 | 8 |
| 1980 | 11 |
| 1981 | 8 |
| 1982 | 12 |
| 1983 | 8 |
| 1984 | 7 |
| 1985 | 12 |
| 1986 | 5 |
| 1987 | 7 |
| 1988 | 6 |
| 1989 | 9 |
| 1990 | 5 |
| 1991 | 7 |
| 1992 | 7 |
| 1993 | 6 |
| 1994 | 8 |
| 1995 | 7 |
| 1996 | 5 |
| 1997 | 4 |
| 1998 | 8 |
| 1999 | 1 |
| 2000 | 6 |
| 2001 | 9 |
| 2002 | 7 |
| 2003 | 10 |
| 2004 | 10 |
| 2005 | 8 |
| 2006 | 11 |
| 2007 | 7 |
| 2008 | 7 |
| 2009 | 10 |
| 2010 | 8 |
| 2011 | 11 |
| 2012 | 5 |
| 2013 | 2 |
| 2014 | 3 |
| 2015 | 4 |
| 2016 | 2 |
| 2017 | 6 |
| 2018 | 5 |
| 2019 | 5 |
| 2020 | 6 |
| 2021 | 10 |
| 2022 | 8 |
| 2023 | 8 |
| 2024 | 1 |
| 2025 | 4 |
| 2026 | 6 |
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\") = 1983
AND c.\"highestInjuryLevel\" = 'Fatal'
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") = 1983
AND c."highestInjuryLevel" = 'Fatal'
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 NYC84FA053Accident · 2 fatalField investigationFinal reportCessna R182 · Greenwich, CTThe acft collided with trees during an ILS approach to westchester arpt in NY. The weather was IMC and an IFR flt plan was filed. The accident occurred during the 2nd attempt with the 1st ending in a missed approach. It was apparent to thecontroller that the…NTSB LAX84FA087Accident · 2 fatalField investigationFinal reportPiper PA-32-260 · Holtville, CAThe plt had departed mazatlan, Mexico at 0632 PST & had landed at los mochis & mexicali, Mexico & at calexico, CA, where he cleared U.S. Customs. Before departing calexico, he telephoned his family & told them the wx had been poor all day. The estimated time…NTSB NYC84FA024Accident · 1 fatalField investigationFinal reportPiper PA-23-250 · West Seneca, NYThe acft was being repositioned by the owner from a maintenance facility at buffalo intl arpt to buffalo airpark. Maintenance personnel at both locations who had dealt with the owner indicated he had attempted to cut costs by performing unauthorized repairs…NTSB DEN84FA019Accident · 1 fatalField investigationFinal reportPiper PA-28-236 · Kim, COThe acft collided with the ground in a wing down nose low attitude. The plt had been advised that VFR flt was not recommended for his route of flt. The non-instrument rated plt went anyway and encountered weather. In maneuvering to get below or out of the…NTSB DEN83FA180Accident · 4 fatalField investigationFinal reportPiper PA-28-235C · Pitkin, COThe acft was on a x-country flt from camarillo, CA to oshkosh, WI. The plt landed at about noon at montrose, CO, where the acft was refueled & the occupants went to a restaurant to eat. After departing montrose, the acft was seen flying low over rising,…NTSB MIA83FA152Accident · 6 fatalField investigationFinal reportPiper PA-32-260 · Sebastian, FLDuring the flt, the plt contacted vero beach tower & requested the wx. He was advised that vero beach & ft pierce, FL were VFR, but there was wx north of vero beach, a convective SIGMET was in effect & there were thunderstorms in the area. The plt…NTSB FTW83FA261Accident · 1 fatalField investigationFinal reportPiper PA-25-235 · Omega, OKThe plt had just completed spraying a field & was in a right turn when the right wing tip hit gently rising terrain. The owner thought that the plt might have diverted his attention while looking at a farmer's map to locate the next field. (Several similar…NTSB NYC83FA107Accident · 1 fatalField investigationFinal reportPiper PA-24-250 · Coram, NYThe acft crashed shortly after declaring an 'emergency.' A witness saw the acft, but heard no eng sound prior to the crash. Examination of eng failed to reveal any discrepancies. However, when the carburetor was examined no fuel was found in the line between…