NTSB investigations: Cessna 172N, 2005
26 cases on aircraft the registry lists as Cessna 172N. 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
| 1965 | 1 |
|---|---|
| 1966 | 2 |
| 1967 | 2 |
| 1975 | 1 |
| 1976 | 2 |
| 1977 | 26 |
| 1978 | 62 |
| 1979 | 81 |
| 1980 | 107 |
| 1981 | 86 |
| 1982 | 91 |
| 1983 | 53 |
| 1984 | 55 |
| 1985 | 40 |
| 1986 | 44 |
| 1987 | 42 |
| 1988 | 47 |
| 1989 | 45 |
| 1990 | 46 |
| 1991 | 57 |
| 1992 | 40 |
| 1993 | 51 |
| 1994 | 43 |
| 1995 | 48 |
| 1996 | 37 |
| 1997 | 40 |
| 1998 | 37 |
| 1999 | 46 |
| 2000 | 35 |
| 2001 | 32 |
| 2002 | 43 |
| 2003 | 32 |
| 2004 | 38 |
| 2005 | 26 |
| 2006 | 23 |
| 2007 | 21 |
| 2008 | 21 |
| 2009 | 20 |
| 2010 | 23 |
| 2011 | 22 |
| 2012 | 14 |
| 2013 | 20 |
| 2014 | 15 |
| 2015 | 10 |
| 2016 | 24 |
| 2017 | 19 |
| 2018 | 14 |
| 2019 | 16 |
| 2020 | 25 |
| 2021 | 15 |
| 2022 | 16 |
| 2023 | 20 |
| 2024 | 13 |
| 2025 | 15 |
| 2026 | 11 |
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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072434'))
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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072434'))
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 LAX06LA065Accident · No injuriesLimited investigationFinal reportBeech F33A · La Verne, CAthe failure of the pilot of the other aircraft to comply with his air traffic control clearance and line up for the proper runway, and his failure to maintain an adequate visual lookout, which resulted in his in-flight collision with the Cessna airplane.NTSB DFW06CA030Accident · No injuriesData collectionFinal reportCessna 172N · Arlington, TXThe students improper recovery from a bounced landing. A contributing factor was the pilots excessive airspeed on final approach.NTSB ATL06CA118Accident · No injuriesData collectionFinal reportCessna 172N · Perry, GAThe student pilot's failure to maintain airspeed during a touch-and-go landing on initial takeoff climb, resulting in a hard landing on the departure runway.NTSB DFW06CA026Accident · No injuriesData collectionFinal reportCessna 172N · Sherman, TXThe pilot's failure to maintain directional control during takeoff.NTSB MIA06CA009Accident · No injuriesData collectionFinal reportCessna 172N · Punta Gorda, FLThe in-flight collision with a bird resulting in substantial damage to the airplane.NTSB ANC05CA132Accident · No injuriesData collectionFinal reportCessna 172 · Tyonek, AKThe pilot's inadequate compensation for wind conditions during takeoff-initial climb, which resulted in a loss of control, and subsequent in-flight collision with a creek. A factor associated with the accident is a sudden windshift.NTSB LAX05CA276Accident · No injuriesData collectionFinal reportCessna 172N · Ramona, CAthe pilot's failure to maintain directional control during landing.NTSB DEN05LA127Accident · No injuriesLimited investigationFinal reportCessna 172N · Cedar City, UTthe loss of engine power for reasons undetermined. Contributing factors include the lack of suitable terrain for a forced landing, and the soft dirt.NTSB LAX05CA240Accident · No injuriesData collectionFinal reportCessna 172N · North Las Vegas, NVthe student pilot's failure to maintain directional control.NTSB SEA05LA145Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Bonners Ferry, IDThe pilot's failure to maintain terrain clearance while maneuvering. Mountainous terrain was a factor.NTSB ATL05FA128Accident · 1 fatalField investigationFinal reportCessna 172N · Penrose, NCA loss of engine power for undetermined reasons. Contributing to the accident was the pilot's failure to use the full length of the runway for takeoff, and the inadvertent stall.NTSB ANC05CA099Accident · No injuriesData collectionFinal reportCessna 172 · Akiachak, AKThe pilot's delay in aborting the landing, which resulted in the airplane running off the end of the runway and nosing over. A factor associated with the accident was the rough/uneven terrain off the end of the runway.NTSB NYC05LA106Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Edgartown, MAThe pilot's failure to maintain airspeed during a go-around, which resulted in an inadvertent stall and subsequent impact with terrain. [This report was modified on June 10, 2008]NTSB DEN05LA093Accident · No injuriesLimited investigationFinal reportCessna 172N · Hudson, COThe flight instructor's improper use raising of the flaps. Contributing factors were the student pilot's misunderstanding of the instructor's intentions, the instructor's inadequate supervision of the student pilot, the density altitude, and the soft terrain.NTSB LAX05CA191Accident · No injuriesData collectionFinal reportCessna 172N · Stockton, CAthe pilot's improper use of the brakes, and his failure to maintain directional control during the landing rollout.NTSB LAX05CA148Accident · No injuriesData collectionFinal reportCessna 172N · Palo Alto, CAThe student's failure to maintain directional control and the CFI's failure to adequately supervise the flight.NTSB NYC05CA073Accident · No injuriesData collectionFinal reportCessna 172N · Wellington, OHThe pilot's failure to obtain the proper touchdown point, and his failure to initiate a go-around, which resulted in an overrun during landing. A factor in the accident was the tail wind.NTSB DFW05LA103Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Olney, TXThe loss of engine power due to carburetor ice. Contributing factors were the weather conditions conducive for carburetor icing and the lack of suitable terrain for a forced landing.NTSB LAX05CA128Accident · No injuriesData collectionFinal reportCessna 172N · San Jose, CAthe student pilot's misjudged landing flare, which resulted in a hard landing.NTSB DFW05CA091Accident · No injuriesData collectionFinal reportCessna 172N · Rio Grande City, TXThe pilot's failure to maintain clearance from objects, and his improper compensation for wind conditions while landing. A contributing factor was the gusty wind condition.NTSB LAX05CA111Accident · No injuriesData collectionFinal reportCessna 172A · Emigrant Gap, CAthe pilot's inadequate preflight planning and his selection of an unsuitable landing area, resulting in an encounter with a snow-covered runway.NTSB IAD05LA043Accident · No injuriesLimited investigationFinal reportCessna 172N · Frederick, MDThe inadequate visual lookout of the pilots in each airplane, which resulted in a ground collision.NTSB ANC05FA037Accident · 1 fatalField investigationFinal reportCessna 172 · Cedar Key, FLThe pilot's continued flight into instrument meteorological conditions (IMC), and his failure to maintain adequate airspeed during an abrupt maneuver to avoid a power line, which resulted in an inadvertent stall, a loss of control, and subsequent collision…NTSB CHI05LA070Accident · No injuriesLimited investigationFinal reportCessna 172N · Grafton, NDThe pilot's inadequate compensation for the wind conditions which resulted in a loss of directional control during the landing. Factors associated with the accident were the crosswind condition and the snow bank.NTSB SEA05CA043Accident · No injuriesData collectionFinal reportCessna 172N · Idaho Falls, IDThe student pilot's failure to maintain directional control and the instructor's inadequate supervision of the flight. A contributing factor was the deep snow beside the runway.NTSB DEN05LA055Accident · No injuriesLimited investigationFinal reportCessna 172N · Loveland, COThe dual student's improper flare and the flight instructor's inadequate supervision.. A contributing factor was the inadequate communication between the flight instructor and the dual student,