NTSB investigations: Lycoming I0360 series, 2005, FL
4 cases on aircraft whose registry engine model is Lycoming I0360 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 | 2 |
|---|---|
| 1965 | 1 |
| 1966 | 2 |
| 1967 | 1 |
| 1969 | 3 |
| 1970 | 2 |
| 1971 | 5 |
| 1972 | 3 |
| 1973 | 5 |
| 1974 | 3 |
| 1975 | 7 |
| 1976 | 6 |
| 1977 | 8 |
| 1978 | 7 |
| 1979 | 9 |
| 1980 | 7 |
| 1981 | 3 |
| 1982 | 3 |
| 1983 | 3 |
| 1984 | 4 |
| 1985 | 2 |
| 1986 | 7 |
| 1987 | 4 |
| 1988 | 1 |
| 1989 | 5 |
| 1990 | 1 |
| 1991 | 2 |
| 1992 | 3 |
| 1993 | 2 |
| 1994 | 1 |
| 1995 | 2 |
| 1996 | 2 |
| 1997 | 2 |
| 1998 | 4 |
| 1999 | 4 |
| 2000 | 3 |
| 2001 | 8 |
| 2002 | 3 |
| 2003 | 5 |
| 2004 | 2 |
| 2005 | 4 |
| 2006 | 2 |
| 2007 | 7 |
| 2008 | 2 |
| 2009 | 4 |
| 2010 | 1 |
| 2011 | 6 |
| 2012 | 4 |
| 2013 | 2 |
| 2014 | 4 |
| 2015 | 5 |
| 2016 | 2 |
| 2017 | 7 |
| 2018 | 4 |
| 2019 | 3 |
| 2020 | 2 |
| 2021 | 1 |
| 2022 | 3 |
| 2023 | 5 |
| 2024 | 1 |
| 2025 | 4 |
| 2026 | 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\") = 2005
AND c.\"eventStateOrRegion\" = 'FL' 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 ('41515'))
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") = 2005
AND c."eventStateOrRegion" = 'FL' 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 ('41515'))
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 MIA06LA019Accident · Minor injuriesLimited investigationFinal reportPiper PA-28R-180 · Heathrow, FLA partial loss of engine power due to undetermined reasons resulting in a forced landing in a residential area.NTSB MIA06LA015Accident · No injuriesLimited investigationFinal reportPiper PA-28R-180 · Opa-Locka, FLThe failure of the pilot-in-command/CFI to maintain control of the airplane and his inattentiveness to the altitude while troubleshooting the landing gear system resulting in the in-flight collision with terrain.NTSB ATL05CA114Accident · No injuriesData collectionFinal reportPiper PA-28R-200 · Daytona Beach, FLThe private pilots improper landing flare. Factors were flight instructors inadequate supervision, and landing crosswind.NTSB MIA05CA048Accident · No injuriesData collectionFinal reportCessna 172SP · Clewiston, FLThe pilot's failure to maintain directional control during landing rollout which resulted in the airplane veering off the runway and colliding into an airport sign.