NTSB investigations: Cessna 172L, 1988
11 cases on aircraft the registry lists as Cessna 172L. 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
| 1970 | 2 |
|---|---|
| 1971 | 17 |
| 1972 | 34 |
| 1973 | 40 |
| 1974 | 28 |
| 1975 | 23 |
| 1976 | 17 |
| 1977 | 19 |
| 1978 | 17 |
| 1979 | 5 |
| 1980 | 8 |
| 1981 | 7 |
| 1982 | 5 |
| 1983 | 2 |
| 1984 | 5 |
| 1985 | 6 |
| 1986 | 4 |
| 1987 | 3 |
| 1988 | 11 |
| 1989 | 4 |
| 1990 | 8 |
| 1991 | 1 |
| 1992 | 6 |
| 1993 | 3 |
| 1994 | 7 |
| 1995 | 6 |
| 1996 | 7 |
| 1997 | 2 |
| 1998 | 6 |
| 1999 | 7 |
| 2000 | 6 |
| 2001 | 9 |
| 2002 | 4 |
| 2003 | 5 |
| 2004 | 5 |
| 2005 | 9 |
| 2006 | 7 |
| 2007 | 5 |
| 2008 | 4 |
| 2009 | 2 |
| 2010 | 1 |
| 2011 | 1 |
| 2012 | 1 |
| 2013 | 4 |
| 2014 | 1 |
| 2015 | 3 |
| 2016 | 1 |
| 2017 | 3 |
| 2018 | 6 |
| 2019 | 4 |
| 2020 | 1 |
| 2021 | 1 |
| 2022 | 4 |
| 2023 | 3 |
| 2024 | 5 |
| 2025 | 5 |
| 2026 | 4 |
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\") = 1988
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072432'))
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") = 1988
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072432'))
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 ATL89LA039Accident · No injuriesLimited investigationFinal reportCessna 172 · Pikeville, KYThe pilot had flown about 3.7 hours and was about 2 miles from his destination airport when the engine stopped and he was forced to land in a swamp. The pilot had topped off the acft so that it contained 42 gallons of fuel (38 gallons of usable fuel). The…NTSB FTW89LA008Accident · Serious injuriesLimited investigationFinal reportCessna 172 · San Antonio, TXThe airplane had been flown for 2.2 hours since refueling when this pilot started his flight. This pilot flew the airplane for 2.5 hours and the engine quit. During the forced landing, the airplane impacted a power pole and power lines, and then the terrain.…NTSB MKC88LA178Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Cameron, MOThe student pilot said he was practicing short field takeoffs from his pasture, when he stalled shortly after takeoff. The aircraft fell uncontrolled to the terrain causing substantial damage to the wings, fuselage and nose gear.NTSB LAX88LA326Accident · No injuriesLimited investigationFinal reportCessna 172L · Banning, CADuring a crosscountry flt, while enroute from lake havasu city, AZ, to Banning, CA, the engine experienced a loss of power. The airplane collided with the terrain after a forced landing. Inspection of the fuel system revealed there was no fuel on board.NTSB SEA88LA171Accident · Serious injuriesLimited investigationFinal reportCessna 172L · Leavenworth, WAOn initial climb over trees bordering 2500-FT mountain strip, plt experienced sudden and severe wind gusts beyond his capability to counter. Acft collided with trees and terrain.NTSB NYC88LA199Accident · Minor injuriesLimited investigationFinal reportCessna 172L · No. Kingstown, RIThe failure of the boston center controller to adequately understand the pilot-in-command's request and to assess the gravity of the situation.NTSB ATL88LA216Accident · Serious injuriesLimited investigationFinal reportCessna 172L · Michie, TNWitness reported that the airplane engine was running rough during takeoff; the airplane subsequently disappeared from sight in a nose-down attitude. The plt later reported that he could not remember the events that led up to the power loss. Post-crash exam…NTSB SEA88FA095Accident · 1 fatalField investigationFinal reportCessna 172L · Ocean Shores, WAThe student pilot departed on his fifth solo flight from the airport where he had been accustomed to originating his instructional flights. After several touch and go landings he proceeded to a nearby airport and conducted at least one more touch and go.…NTSB CHI88DEP04Accident · No injuriesFinal reportCessna 172L · West Bend, WIAfter 30 minutes of local flight, on a dark night, the pilot increased the throttle setting after selecting approach flaps. There was no response from the engine. A forced landing was initiated and the aircraft collided with trees and terrain. A subsequent…NTSB SEA88LA035Accident · No injuriesLimited investigationFinal reportCessna 172 · Everett, WAThe student pilot had landed with full flaps prior to the application of full power for takeoff. The aircraft veered to the left side of the runway into mud and nosed over inverted. The aircraft's flap indicator had been placarded inoperative by the operator.NTSB CHI88LA049Accident · No injuriesLimited investigationFinal reportCessna 172L · Buffalo, MN