NTSB investigations: Lycoming VO-435 series, 2004
4 cases on aircraft whose registry engine model is Lycoming VO-435 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 | 17 |
|---|---|
| 1965 | 18 |
| 1966 | 15 |
| 1967 | 21 |
| 1968 | 12 |
| 1969 | 16 |
| 1970 | 28 |
| 1971 | 15 |
| 1972 | 20 |
| 1973 | 25 |
| 1974 | 28 |
| 1975 | 24 |
| 1976 | 18 |
| 1977 | 14 |
| 1978 | 27 |
| 1979 | 20 |
| 1980 | 18 |
| 1981 | 16 |
| 1982 | 15 |
| 1983 | 14 |
| 1984 | 14 |
| 1985 | 16 |
| 1986 | 13 |
| 1987 | 10 |
| 1988 | 12 |
| 1989 | 11 |
| 1990 | 6 |
| 1991 | 13 |
| 1992 | 10 |
| 1993 | 8 |
| 1994 | 11 |
| 1995 | 9 |
| 1996 | 7 |
| 1997 | 4 |
| 1998 | 5 |
| 1999 | 5 |
| 2000 | 6 |
| 2001 | 5 |
| 2002 | 8 |
| 2003 | 8 |
| 2004 | 4 |
| 2005 | 4 |
| 2006 | 4 |
| 2007 | 4 |
| 2009 | 3 |
| 2010 | 2 |
| 2011 | 5 |
| 2012 | 3 |
| 2013 | 6 |
| 2014 | 6 |
| 2015 | 4 |
| 2016 | 5 |
| 2017 | 1 |
| 2018 | 3 |
| 2019 | 6 |
| 2021 | 1 |
| 2022 | 2 |
| 2023 | 1 |
| 2025 | 1 |
| 2026 | 2 |
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\") = 2004
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41525'))
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") = 2004
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41525'))
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 CHI04CA229Accident · No injuriesData collectionFinal reportBell 47G2 · Muncie, INThe engine failure for an undetermined reason, and the pilot's inability to properly level-off for landing due to the low rotor speed, which resulted in the hard landing. The low altitude where the engine failure occurred was a factor.NTSB FTW04CA207Accident · No injuriesData collectionFinal reportBell 47G-3B-1 · Troy, TXThe flight instructor's improper flare, resulting in a hard landing. A contributing factor was the high density altitude.NTSB CHI04CA180Accident · No injuriesData collectionFinal reportTexas Helicopter M-74 · Clear Lake, MNThe pilot failed to maintain a proper glidepath to the landing zone. A factor was the truck pad.NTSB LAX04LA158Accident · No injuriesLimited investigationFinal reportQuinn E L Tom Cat MK-5A · Galt, CAa loss of engine power due to water contamination of the fuel system.