NTSB investigations: Lycoming VO-540 series, 1998
6 cases on aircraft whose registry engine model is Lycoming VO-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 | 4 |
|---|---|
| 1965 | 15 |
| 1966 | 16 |
| 1967 | 5 |
| 1968 | 15 |
| 1969 | 10 |
| 1970 | 8 |
| 1971 | 7 |
| 1972 | 6 |
| 1973 | 9 |
| 1974 | 11 |
| 1975 | 14 |
| 1976 | 13 |
| 1977 | 13 |
| 1978 | 22 |
| 1979 | 17 |
| 1980 | 8 |
| 1981 | 14 |
| 1982 | 9 |
| 1983 | 10 |
| 1984 | 9 |
| 1985 | 3 |
| 1986 | 9 |
| 1987 | 8 |
| 1988 | 6 |
| 1989 | 5 |
| 1990 | 6 |
| 1991 | 8 |
| 1992 | 6 |
| 1993 | 7 |
| 1994 | 4 |
| 1995 | 7 |
| 1996 | 7 |
| 1997 | 5 |
| 1998 | 6 |
| 1999 | 2 |
| 2000 | 3 |
| 2001 | 4 |
| 2002 | 6 |
| 2003 | 4 |
| 2004 | 3 |
| 2005 | 4 |
| 2008 | 6 |
| 2009 | 2 |
| 2010 | 6 |
| 2011 | 3 |
| 2012 | 1 |
| 2013 | 1 |
| 2014 | 1 |
| 2015 | 3 |
| 2017 | 1 |
| 2022 | 2 |
| 2025 | 1 |
| 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\") = 1998
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41534', '41582'))
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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41534', '41582'))
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 SEA99LA022Accident · No injuriesLimited investigationFinal reportHiller UH-12E · Wenatchee, WAFuel exhaustion due to the pilot's failure to accomplish refueling.NTSB SEA99FA013Accident · 1 fatalField investigationFinal reportHiller UH-12E · Marshall, WAThe loss of the bolt that connects the lateral cyclic linkage push rod to the lower end of the upper firewall-mounted lateral cyclic linkage bellcrank, resulting in an uncontrolled descent into the terrain.NTSB MIA98FA229Accident · No injuriesField investigationFinal reportBell 47G-4A · Carrollton, ALThe pilots failure to follow written instructions in the flight manual for an engine failure, and the improper use of flight controls (cyclic/collective) during an autorotation resulting in a hard landing, and collision of the main rotor blades with the…NTSB CHI98LA312Accident · Serious injuriesLimited investigationFinal reportHiller UH-12E · Shelton, NEThe pilot mismanaged the fuel which led to fuel starvation and subsequent loss of engine power.NTSB LAX98LA197Accident · No injuriesLimited investigationFinal reportBell 47G-4A · Shafter, CAThe aircraft's encounter with settling with power, which resulted from the pilot's decision to perform a steep downwind approach.NTSB LAX98LA089Accident · No injuriesLimited investigationFinal reportHiller UH-12E · Chico, CAFuel exhaustion due to the pilot's failure to ensure that an adequate fuel supply was onboard. A contributing factor was related to the fuel quantity gage's erroneous indication of fuel.