NTSB investigations: Cessna 172N
92 cases on aircraft the registry lists as Cessna 172N, 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 | 8 |
|---|---|
| 1983 | 4 |
| 1984 | 3 |
| 1985 | 6 |
| 1986 | 5 |
| 1987 | 4 |
| 1988 | 2 |
| 1989 | 2 |
| 1990 | 3 |
| 1991 | 6 |
| 1992 | 2 |
| 1993 | 1 |
| 1994 | 5 |
| 1995 | 4 |
| 1996 | 4 |
| 1997 | 3 |
| 1998 | 4 |
| 1999 | 5 |
| 2000 | 3 |
| 2001 | 2 |
| 2002 | 4 |
| 2003 | 1 |
| 2004 | 4 |
| 2005 | 2 |
| 2006 | 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 c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072434')
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 ('2072434')
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 DEN07CA043Accident · No injuriesData collectionFinal reportCessna 172N · Cottonwood Fall, KSthe pilot's failure to maintain clearance from the fence. Contributing to the accident was the pilot's inability to properly identify the runway environment, and the improper in-flight decision to initiate a go-around.NTSB MIA06CA134Accident · Minor injuriesData collectionFinal reportCessna 172N · Pensacola, FLThe student pilot's failure to raise the wing flaps for a go-around resulting in the airplane not climbing and an in-flight collision with trees.NTSB DFW06FA187Accident · 2 fatalField investigationFinal reportCessna 172N · Petal, MSThe pilot's improper use of flaps, which resulted in an impact with trees during takeoff-initial climb.NTSB NYC06FA154Accident · 4 fatalField investigationFinal reportCessna 172N · Newry, METhe flight instructor's failure to maintain altitude/clearance while maneuvering, which resulted in an impact with trees.NTSB LAX06CA125Accident · Minor injuriesData collectionFinal reportCessna 172N · Compton, CAcontrol interference by the student pilot during a go-around that resulted in an in-flight collision with power lines.NTSB MIA06CA009Accident · No injuriesData collectionFinal reportCessna 172N · Punta Gorda, FLThe in-flight collision with a bird resulting in substantial damage to the airplane.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 ATL04FA099Accident · 3 fatalField investigationFinal reportCessna 172N · Moselle, MSThe pilot's failure to maintain clearance and his inadequate visual look-out while maneuvering resulting in an in-flight collision with a radio tower.NTSB ATL04CA089Accident · No injuriesData collectionFinal reportCessna 172N · Statesboro, GAThe pilot's failure to establish a positive climb and his failure to maintain clearance during a go-around, which resulted in an in-flight collision with trees. A factor was the gusting winds.NTSB SEA04LA048Accident · No injuriesLimited investigationFinal reportCessna 172N · Gig Harbor, WAThe pilot's failure to follow the published IFR procedure resulting in failure to maintain clearance from objects during an instrument approach. Trees and an inoperative glide slope receiver were factors.NTSB NYC04CA076Accident · No injuriesData collectionFinal reportCessna 172N · Youngstown, OHAn inadvertent collision with a deer while landing.NTSB NYC04CA032Accident · Minor injuriesData collectionFinal reportCessna 172N · Philippi, WVThe pilot's improper decision to depart from a runway of insufficient length. Factors in the accident were the turf runway and tailwind condition.NTSB IAD03FA005Accident · 2 fatalField investigationFinal reportCessna 172N · Mount Sterling, KYThe failure of the pilot to follow the published instrument approach procedure, which resulted in an early descent into an antenna tower. A factor was the low ceiling.NTSB IAD02FA088Accident · 1 fatalField investigationFinal reportCessna 172N · Stanardsville, VAThe pilot's failure to maintain sufficient altitude/clearance while descending over mountainous terrain. A factor was the night lighting conditions.NTSB SEA02FA125Accident · 2 fatalField investigationFinal reportCessna 172N · Otis, ORThe pilot's failure to maintain adequate clearance with power lines while conducting low altitude flight resulting in a loss of control and subsequent collision with terrain. Contributing factors were the pilot's low altitude flight and the power lines.NTSB FTW02LA063Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Durango, COthe pilot's failure to maintain clearance with the trees and mountainous terrain while maneuvering. A contributing factor was the pilot's delay in taking remedial action.NTSB MIA01LA207Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Covington, GAThe flight instructor's improper monitoring of the dual student during a simulated engine out approach and her delayed decision to initiate a go-around resulting in the airplane colliding with trees at the departure end of the runway during the go-around.NTSB CHI01FA130Accident · 2 fatalField investigationFinal reportCessna 172N · Wichita, KSthe student pilot not maintaining clearance from the tower support wire during the practice emergency landing maneuver and the instructor pilot's inadequate supervision of the student pilot. Factors relating to the accident were the static wire and the low…NTSB DEN00FA149Accident · 1 fatalField investigationFinal reportCessna 172N · Kamas, UTThe pilot's improper inflight decision to enter a valley at low altitude and attempt a climb towards rising terrain. A factor was exceeding the airplane's climb performance.NTSB LAX00LA152Accident · No injuriesLimited investigationFinal reportCessna 172N · Lakeport, CAThe pilot's decision to continue with a high, steep, and fast approach, which resulted in a touchdown beyond the halfway point of the runway and the inability to stop on the remaining pavement, and, his delayed decision to initiate a landing abort. Also…NTSB MIA00LA074Accident · No injuriesLimited investigationFinal reportCessna 172N · Lincolnton, GAThe pilot's failure to remove ice from the wings prior to takeoff resulting in the aircraft not climbing after takeoff and colliding with a tree.NTSB CHI00LA021Accident · No injuriesLimited investigationFinal reportCessna 172N · Crandon, WIthe deer that ran out onto the runway and collided with the airplane. A factor associated with the accident was the night lighting conditions.NTSB NYC99FA213Accident · 3 fatalField investigationFinal reportCessna 172N · Sussex, NJThe pilot's improper decision to takeoff with a tailwind. Factor's in this accident were the tailwind condition and pressure to depart caused by other airplanes performing successful downwind departures.NTSB SEA99LA077Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Covington, WAThe student pilot's inadequate recovery from a bounced landing, and his subsequent improper execution of the go-around procedure, resulting in collision with trees off the departure end of the runway. Factors included the student pilot's lack of total…NTSB MIA99LA148Accident · No injuriesLimited investigationFinal reportCessna 172N · Eagleville, TNThe dual's student failure to maintain adequate altitude/clearance from the wire during takeoff/initial climb. Also causal was the certified flight instructor's inadequate supervision.NTSB FTW99LA114Accident · No injuriesLimited investigationFinal reportCessna 172N · Cleburne, TXThe pilot's failure to maintain adequate altitude/ clearance from the wires.NTSB ATL99FA020Accident · Serious injuriesField investigationFinal reportCessna 172N · Concord, NCThe pilot's improper in-flight decision and his failure to maintain clearance during approach that resulted in collision with utility lines. Related factors were dark night, trees and low ceilings.NTSB NYC99FA015Accident · 1 fatalField investigationFinal reportCessna 172N · Linden, NJThe pilot's failure to maintain clearance from the power lines. A factor was sunglare.NTSB FTW98FA358Accident · 1 fatalField investigationFinal reportCessna 172N · Cord, ARThe pilot's performance of low altitude flight and his failure to maintain obstacle clearance.NTSB IAD98LA087Accident · No injuriesLimited investigationFinal reportCessna 172N · Lebanon, OHThe pilot's delay in aborting the landing, which resulted in inadequate obstacle (car) clearance during initial takeoff climb. A contributing factor is the pilot's decision to perform a tailwind landing.NTSB MIA97FA176Accident · 3 fatalField investigationFinal reportCessna 172N · Comerio, PRthe pilot's improper in-flight planning/decision, which resulted in his failure to maintain sufficient altitude/clearance from obstructions on rising terrain.NTSB SEA97LA059Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Madras, ORThe pilot's inadvertent visual flight rules (VFR) flight into instrument meteorological conditions (IMC). Factors include the pilot's improper decision to fly under a low ceiling while in mountainous/hilly terrain, and his encounter with fog and low clouds…NTSB FTW97LA085Accident · No injuriesLimited investigationFinal reportCessna 172N · Steamboat Spgs, COFailure of the flight instructor and the dual student to maintain an adequate visual lookout. Factors were the flight instructor's inadequate supervision of the flight, inadequate altitude in which to clear obstacles, and the dual student's lack of…NTSB MIA97LA007Accident · No injuriesLimited investigationFinal reportCessna 172N · Fruitland Park, FLThe pilot's inadequate compensation for wind conditions and failure to maintain proper runway alignment during takeoff. The unfavorable wind condition was a related factor.NTSB LAX96LA304Accident · No injuriesLimited investigationFinal reportCessna 172N · Fullerton, CAthe pilot's misjudged glide path and delayed remedial action by not promptly initiating a go-around. A contributing factor was the pilot's lack of experience flying the airplane.NTSB ATL96FA094Accident · 1 fatalField investigationFinal reportCessna 172N · Arlington, TNThe pilot's failure to maintain clearance above the trees. A factor was the dark night.NTSB CHI96LA156Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Crystal Lake, ILthe pilot not flying a proper glidepath for the displaced runway threshold.NTSB SEA96LA035Accident · No injuriesLimited investigationFinal reportCessna 172N · Pacific City, ORThe pilot's delay in aborting the landing, which resulted in his failure to clear the perimeter fence. Factors relating to the accident were: the tailwind, and the pilot's failure to land at the proper touchdown point.NTSB LAX95FA198Accident · 4 fatalField investigationFinal reportCessna 172N · Lovelock, NVthe pilot's intentional flight at low altitude and subsequent collision with transmission wires during dusk light conditions.NTSB MIA95FA070Accident · 2 fatalField investigationFinal reportCessna 172N · Mintonville, KYThe flightcrew's intentional VFR flight into known instrument meteorological conditions. A factor was the inadequate altitude to prevent an inadvertent collision with an obstruction.NTSB SEA95FA037Accident · 3 fatalField investigationFinal reportCessna 172N · Blyn, WAThe pilot's VFR flight into instrument meteorological conditions. Factors in the accident were the weather conditions and the dark night.NTSB BFO95FA001Accident · 1 fatalField investigationFinal reportCessna 172N · Fancy Gap, VAThe pilot's inadequate inflight planning and his failure to maintain adequate terrain clearance. Other related factors are: fog, rain, VFR flight into IMC, inexperience and mountainous terrain.NTSB NYC94LA132Accident · No injuriesLimited investigationFinal reportCessna 172N · Chatham, MAThe pilot's failure to see and avoid the birds. The presence of the birds at the airport was a contributing factor.NTSB SEA94LA113Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Monarch, MTPoor in flight planning/decision. A factor to the accident was downdrafts.NTSB LAX94LA176Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Gasquet, CAThe failure of the pilot to adequately compensate for the cross- wind conditions, and to maintain proper alignment with the runway.NTSB SEA94LA070Accident · No injuriesLimited investigationFinal reportCessna 172 · Casper, WYThe pilot's failure to maintain proper alignment with the runway. The crosswind was of factor.NTSB MIA93LA132Accident · No injuriesLimited investigationFinal reportCessna 172N · Immokalee, FLThe decision of the pilot to buzz and his failure to maintain adequate visual lookout.NTSB CHI92FA254Accident · 1 fatalField investigationFinal reportCessna 172N · Marquette, MIThe pilot's failure to maintain proper altitude during the approach.NTSB MIA92LA148Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Sanford, FLInadequate visual lookout by both pilots, which resulted in their failure to see-and-avoid of the power line. The proximity of the power line was a related factor.NTSB SEA92FA013Accident · 3 fatalField investigationFinal reportCessna 172N · Columbus, MTThe pilot in command's operation at too low an altitude over the river and his failure to maintain adequate clearance from the power lines. Factors contributing to the accident were the wires crossing the river and the pilot in command's poor judgement in…