NTSB investigations: Cessna 182Q, 2023
6 cases on aircraft the registry lists as Cessna 182Q. 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
| 1977 | 6 |
|---|---|
| 1978 | 15 |
| 1979 | 21 |
| 1980 | 15 |
| 1981 | 17 |
| 1982 | 13 |
| 1983 | 14 |
| 1984 | 9 |
| 1985 | 8 |
| 1986 | 6 |
| 1987 | 9 |
| 1988 | 5 |
| 1989 | 10 |
| 1990 | 4 |
| 1991 | 10 |
| 1992 | 10 |
| 1993 | 8 |
| 1994 | 6 |
| 1995 | 10 |
| 1996 | 7 |
| 1997 | 4 |
| 1998 | 8 |
| 1999 | 9 |
| 2000 | 5 |
| 2001 | 9 |
| 2002 | 15 |
| 2003 | 6 |
| 2004 | 7 |
| 2005 | 4 |
| 2006 | 4 |
| 2007 | 10 |
| 2008 | 2 |
| 2009 | 7 |
| 2010 | 2 |
| 2011 | 3 |
| 2012 | 3 |
| 2013 | 4 |
| 2014 | 5 |
| 2015 | 10 |
| 2016 | 5 |
| 2017 | 2 |
| 2018 | 7 |
| 2019 | 5 |
| 2020 | 1 |
| 2021 | 8 |
| 2022 | 5 |
| 2023 | 6 |
| 2024 | 1 |
| 2025 | 3 |
| 2026 | 5 |
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\") = 2023
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072732'))
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") = 2023
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072732'))
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 ERA23LA383Accident · No injuriesClass 3 · LimitedFinal reportCessna 182 · Towanda, PAA total loss of engine power during initial climb for undetermined reasons.NTSB WPR23LA360Accident · No injuriesClass 4 · LimitedFinal reportCessna 182Q · Aurora, ORThe pilot’s improper landing flare, which resulted in a hard, bounced landing.NTSB ERA23LA299Accident · No injuriesClass 3 · LimitedFinal reportCessna 182 · Richmond, VAThe pilot’s delay in performing a go-around after a likely encounter with low-level wind shear, resulting in a hard landing. Contributing to the accident were the pilot’s failure to recognize the severity of the actual and forecasted weather near the airport…NTSB WPR23LA207Accident · Serious injuriesClass 4 · LimitedFinal reportCessna 182Q · Kingman, AZThe failure of the passenger to adequately maintain a safe distance from the airplane’s propeller and the determination to let the passenger exit the airplane with the engine running.NTSB ERA23FA219Accident · 1 fatalClass 3 · FieldFinal reportCessna 182 · Reliance, TNThe pilot’s decision to continue an instrument flight into an area of forecast weather with severe to extreme turbulence associated with a line of thunderstorms, which resulted in an in-flight breakup. Contributing was the pilot’s operation of the airplane in…NTSB CEN23LA149Accident · No injuriesClass 3 · LimitedFinal reportCessna 182Q · Gardner, KSA total loss of engine power due to failure of the No. 6 connecting rod as a result of detonation.