NTSB investigations: Lycoming GO-480 series, 1996
4 cases on aircraft whose registry engine model is Lycoming GO-480 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 | 6 |
|---|---|
| 1965 | 6 |
| 1966 | 7 |
| 1967 | 10 |
| 1968 | 7 |
| 1969 | 6 |
| 1970 | 8 |
| 1971 | 2 |
| 1972 | 4 |
| 1973 | 4 |
| 1974 | 9 |
| 1975 | 5 |
| 1976 | 6 |
| 1977 | 5 |
| 1978 | 8 |
| 1979 | 9 |
| 1980 | 7 |
| 1981 | 4 |
| 1982 | 3 |
| 1983 | 5 |
| 1984 | 1 |
| 1985 | 3 |
| 1986 | 2 |
| 1987 | 1 |
| 1988 | 4 |
| 1990 | 2 |
| 1991 | 5 |
| 1992 | 3 |
| 1994 | 2 |
| 1995 | 6 |
| 1996 | 4 |
| 1997 | 2 |
| 1998 | 1 |
| 1999 | 2 |
| 2000 | 1 |
| 2001 | 2 |
| 2002 | 2 |
| 2004 | 2 |
| 2005 | 2 |
| 2006 | 2 |
| 2007 | 1 |
| 2008 | 1 |
| 2009 | 4 |
| 2011 | 1 |
| 2012 | 1 |
| 2013 | 2 |
| 2014 | 2 |
| 2015 | 3 |
| 2016 | 4 |
| 2018 | 3 |
| 2019 | 2 |
| 2020 | 1 |
| 2023 | 1 |
| 2025 | 2 |
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\") = 1996
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41527'))
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") = 1996
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41527'))
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 SEA96FA201Accident · 1 fatalField investigationFinal reportBeech D50 · Seattle, WAfailure of the pilot to follow proper emergency procedures (properly configure the airplane and feather the appropriate propeller) after loosing power in one engine, which resulted in his inability to maintain altitude until reaching an airport. Factors…NTSB LAX96LA174Accident · No injuriesLimited investigationFinal reportHelio H-295 · Grand Canyon, AZthe partial failure of the landing gear brake system resulting from loss of the clips retaining the right-hand brake disk. The resulting loss of braking authority impaired the pilot's ability to maintain directional control in a left quartering tailwind and…NTSB ANC96IA039Incident · No injuriesIncident investigationFinal reportHelio H295 · Angoon, AKthe pilot's inadequate compensation for the gusty wind conditions. A factor associated with the accident was the gusty wind conditions.NTSB MIA96LA090Accident · No injuriesLimited investigationFinal reportHelio H-295 · Key West, FLThe pilot's inadequate compensation for wind conditions during lift-off, which resulted in the right wingtip contacting the runway. The gusty crosswind was a related factor.