NTSB investigations: Cessna 172
33 cases on aircraft the registry lists as Cessna 172, where the first occurrence was “In flight collision with object”. 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
| 1982 | 2 |
|---|---|
| 1983 | 2 |
| 1984 | 2 |
| 1985 | 3 |
| 1986 | 2 |
| 1987 | 3 |
| 1988 | 1 |
| 1989 | 1 |
| 1992 | 1 |
| 1993 | 1 |
| 1994 | 2 |
| 1995 | 1 |
| 1996 | 1 |
| 1997 | 2 |
| 1998 | 2 |
| 1999 | 2 |
| 2000 | 2 |
| 2002 | 1 |
| 2005 | 1 |
| 2007 | 1 |
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 c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072402')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 220))
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 c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072402')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 220))
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 LAX07CA254Accident · Minor injuriesData collectionFinal reportCessna 172 · Leavenworth, WAthe pilot's failure to maintain an adequate clearance from the trees.NTSB SEA06LA012Accident · No injuriesLimited investigationFinal reportCessna 172 · Gleneden Beach, ORThe pilot's failure to maintain clearance from objects while maneuvering over the airport environment. Dark night conditions, trees, and ground fog were factors.NTSB SEA02LA090Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Carey, IDThe pilot's failure to maintain clearance from trees during takeoff.NTSB SEA00LA093Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Johnson Creek, IDThe pilot's failure to maintain clearance from the rising terrain. Factors include his poor decision to depart without assurance that he could clear the surrounding terrain under the ambient conditions, his failure to adhere to the accepted procedure of…NTSB NYC00LA095Accident · No injuriesLimited investigationFinal reportCessna 172 · New Brighton, PAThe pilot's inadequate compensation for the gusty wind conditions. A factor was the windshear encountered on final approach.NTSB LAX99LA217Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Needles, CAThe pilot's inadequate compensation for the gusty crosswind condition and subsequent failure to maintain alignment with the road used for takeoff, which resulted in a collision with a construction sign during the initial climb.NTSB ATL99FA074Accident · 1 fatalField investigationFinal reportCessna 172 · Savannah, GAThe pilot's selection of the wrong runway for landing and his delayed go-around, which resulted in the collision with trees. A factor was the tailwind on landing.NTSB FTW98FA384Accident · 2 fatalField investigationFinal reportCessna 172 · West Jordan, UTThe pilot's failure to maintain proper airport traffic pattern altitude. Factors were night lighting conditions and the unseen static line.NTSB SEA98LA154Accident · 1 fatalLimited investigationFinal reportCessna 172 · Baker City, ORThe pilot's failure to maintain terrain clearance and inadequate in-flight planning/decision. Contributing to the accident was mountain obscuration.NTSB LAX97LA239Accident · No injuriesLimited investigationFinal reportCessna 172 · Aguiguan Island, MauritiusThe pilot's failure to maintain runway alignment while landing on an undeveloped private dirt strip.NTSB FTW97LA123Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Manchaca, TXThe pilot's continued VFR flight into instrument meteorological conditions and his failure to maintain obstacle clearance. A factor was the weather condition.NTSB IAD96LA149Accident · No injuriesLimited investigationFinal reportCessna 172P · Richwood, WVimproper in-flight planning/decision by the flight crew, and inadequate supervision by the check pilot, which resulted in the flight crew's failure to maintain altitude/clearance from trees on rising terrain. A factor relating to the accident was:…NTSB BFO95LA074Accident · No injuriesLimited investigationFinal reportCessna 172 · Wauseon, OHThe pilot's failure to obtain/maintain adequate altitude/clearance from obstacles during an attempted go-round. Related factors are the pilot's failure to attain the planned approach and the improper go-around procedures.NTSB ATL94LA160Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Pine Mountain, GAThe pilot's inadequate compensation for existing wind conditions, and his failure to maintain both airspeed and clearance from a fence. Factors were the tailwind and the gusts which existed at the time of the accident.NTSB NYC94LA139Accident · No injuriesLimited investigationFinal reportCessna 172A · Block Island, RIThe pilot's improper decision to initiate VFR flight into instrument meteorological conditions. The dark night light conditions and the fog were contributing factors.NTSB ATL93LA112Accident · Serious injuriesLimited investigationFinal reportCessna 172 · St. Elmo, ALThe pilot's failure to maintain adequate clearance from the trees located near the departure end of the runway. Factors were the pilot's failure to use the entire runway for the takeoff, and the trees located near the departure end of the runway.NTSB NYC93LA003Accident · No injuriesLimited investigationFinal reportCessna 172 · Marengo, OHThe pilot's inadequate visual lookout due to sunglare, which resulted in a tree strike on final approach.NTSB DEN89FA200Accident · Serious injuriesField investigationFinal reportCessna 172 · Tremonton, UTThe pilot failed to maintain obstruction clearance while making a low pass over a newly constructed highway. The powerline was considered a contributing factor.NTSB CHI89DEX02Accident · No injuriesFinal reportCessna 172 · Greencastle, INInflight collision with a large bird.NTSB DEN87LA155Accident · No injuriesLimited investigationFinal reportCessna 172 · Paradise, UTThe plt departed bear lake arpt, montpelier, ID, and flew to logan, UT. He departed logan and flew to his father's ranch at avon, UT, near Paradise. A 1400-FT dirt/gravel driveway leading to the ranch house was used as a rwy. The plt said he helped his father…NTSB NYC87LA180Accident · No injuriesLimited investigationFinal reportCessna 172 · Mt.Union Boro, PAThe aircraft collided with transmission wires while flying low during a pleasure flight. An uneventful precautionary landing was made on a highway with reduced power and full flaps.NTSB FTW87LA143Accident · No injuriesLimited investigationFinal reportCessna 172 · Cameron, TXDuring takeoff climb the aircraft struck a powerline then trees and impacted the ground. The aircraft was being flown bya student pilot with no medical certificate or solo endorsement.NTSB ATL86FA133Accident · 1 fatalField investigationFinal reportCessna 172 · Douglasville, GAThe acft was observed flying at low alt & circling several houses. The plt landed on a grass strip, then after a short time, he & his passenger took off again. The acft was again observed circling several houses at low alt in an area near the strip. A witness…NTSB FTW86LA053Accident · No injuriesLimited investigationFinal reportCessna 172 · Sallisaw, OKThe pilot stated that on approach into an unfamiliar airstrip he encountered turbulence and a tail wind. He attempted a go-around at a low altitude with full flaps. Before sufficient airspeed could be reached and flaps retracted, the aircraft collided with…NTSB CHI85FEV03Accident · 1 fatalFinal reportCessna 172 · Sweetwater, ILThe acft was observed flying at low alt parallel to a hiway before colliding with a tree before impacting the ground. The plts wife said that the plt had been under extreme stress for a few months and had not been to bed for 2 days preceding the accident. She…NTSB CHI85FA356Accident · 1 fatalField investigationFinal reportCessna 172 · Rose Township, MIJust prior to the accident, several witnesses observed the acft flying at a very low alt in the vicinity of the crash site. The crash site was located across the road from the home of the plt's brother. According to witnesses, the acfts eng was operating…NTSB DEN85LA219Accident · No injuriesLimited investigationFinal reportCessna C-172 · Killdeer, NDThe plt said he measured the length of the r/w prior to t/o. the t/o was normal on a downsloping r/w with trees at the FAR end. The plt said that as the a/c lifted off the r/w the a/c struck the trees. He said a gust of wind caused the a/c to settle into the…NTSB NYC84FNC09Accident · 1 fatalFinal reportCessna 172 · Pownal, MEPrior to the accident, witnesses observed the acft making several low passes & maneuvering. During the last maneuver, the acft entered a dive & collided with trees before the plt recovered. Trees were broken or damaged over an area of about 200 ft. no…NTSB FTW84LA223Accident · No injuriesLimited investigationFinal reportCessna 172 · Allen, OKThe pilot stated that he could not climb enough to clear the trees at the end of the airport. The left wing hit a tree then the right wing hit a pwr line and utility pole. The acft then crashed into the ground. The plt had about 400 hours in this make and…NTSB ATL83FA378Accident · 3 fatalField investigationFinal reportCessna 172 · Benson, NCAprx 3 mi south of the crash site, a witness saw the acft flying northbound along a railroad track. He reported that the acft was flying below tree top level & the eng was running smoothly. A short time later, another witness aprx 1 1/2 mi further north, also…NTSB MKC83LA077Accident · No injuriesLimited investigationFinal reportCessna 172 · Greenfield, MOThe plt reported that before landing he applied carburetor heat & extended full flaps. Reportedly, he made a steep approach to the 3000 ft, sod rwy. He said he overshot the 1st half of the rwy & touched down at about midfield. At this point, the plt initiated…NTSB LAX83LA029Accident · No injuriesLimited investigationFinal reportCessna 172 · Alamo, NVAfter takeoff from a desert road the acft settled & struck a yucca tree.NTSB SEA82FYK07Accident · 1 fatalFinal reportCessna 172 · Lapine, ORWhen the pilot landed at lakeview,OR,he checked the weather but reported to his passenger that although the weather was bad he did not want to stay in lakeview. The aircraft departed lakeview, following a highway, when the weather conditions continued to…