NTSB investigations: Cessna 172N, MD
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
| 1977 | 1 |
|---|---|
| 1978 | 1 |
| 1979 | 1 |
| 1980 | 3 |
| 1981 | 2 |
| 1982 | 1 |
| 1983 | 1 |
| 1984 | 1 |
| 1985 | 1 |
| 1990 | 1 |
| 1991 | 1 |
| 1992 | 2 |
| 1997 | 1 |
| 1998 | 2 |
| 2004 | 1 |
| 2005 | 1 |
| 2007 | 1 |
| 2008 | 1 |
| 2010 | 1 |
| 2014 | 1 |
| 2021 | 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.\"eventStateOrRegion\" = 'MD' AND c.\"eventCountry\" = 'USA'
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 c."eventStateOrRegion" = 'MD' AND c."eventCountry" = 'USA'
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 ERA22LA044Accident · Minor injuriesClass 4 · LimitedFinal reportCessna 172 · Stevensville, MDAn in-flight collision with a bird during initial climb.NTSB ERA14CA334Accident · No injuriesData collectionFinal reportCessna 172N · Edgewater, MDThe pilot's inadvertent encounter with an unanticipated convective gust front or low-level wind shear while landing, which resulted in a loss of control and subsequent hard landing.NTSB ERA11CA061Accident · No injuriesData collectionFinal reportCessna 172N · Gaithersburg, MDThe student pilot's inadequate use of the rudder, and subsequent loss of directional control.NTSB NYC08CA248Accident · No injuriesData collectionFinal reportCessna 172N · Edgewater, MDThe pilot's misjudged distance/speed during landing.NTSB NYC08LA049Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Gaithersburg, MDThe student pilot's failure to maintain aircraft control during an attempted touch-and-go. Contributing to the accident was the instructor's delay in taking remedial action, and the presence of trees in proximity to the side of the 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 NYC04CA073Accident · No injuriesData collectionFinal reportCessna 172N · Easton, MDThe student pilot's improper flare, which resulted in a hard landing.NTSB IAD98FA070Accident · 1 fatalField investigationFinal reportCessna 172N · Ocean City, MDThe pilot's failure to maintain control of the aircraft due to spatial disorientation. Contributing factors wer fog, dark night conditions, lack of recent experience, inadequate preflight planning, and flight into known adverse weather.NTSB IAD98LA045Accident · No injuriesLimited investigationFinal reportCessna 172N · Stevensville, MDthe pilot's improper flare, improper recover from a bounced landing, and failure to maintain directional control.NTSB IAD97LA063Accident · No injuriesLimited investigationFinal reportCessna 172N · Annapolis, MDThe pilot's failure to raise the flaps during the go-around. Factors involved were the high wind conditions and the pilot's failure to remove the carburetor heat.NTSB BFO92LA142Accident · No injuriesLimited investigationFinal reportCessna 172N · Havre De Grace, MDThe pilot's improper use of carburetor heat control resulting in a total loss of engine power. Factors contributing to the accident include the existence of weather conditions conducive to carburetor icing and the rough terrain on which the aircraft was…NTSB NYC92FA093Accident · 3 fatalField investigationFinal reportCessna 172N · Brookeville, MDImproper inflight planning/decision by the flight instructor (pic/cfi) in the Cessna 172, his misjudgement of distance between the two airplanes, and inadequate visual lookout by both pilots in the Cessna 172.NTSB BFO91LA033Accident · No injuriesLimited investigationFinal reportCessna 172 · Hagerstown, MDWorn camshaft lobes which resulted in the loss of engine power.NTSB BFO90LA022Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Gaithersburg, MDInadequate supervision by the instructor pilot (CFI), which resulted in failure to maintain airspeed and a subsequent stall. Factors related to the accident were: gusty/crosswind conditions, the student pilot's inadequate compensation for wind conditions and…NTSB BFO86LA001Accident · No injuriesLimited investigationFinal reportCessna 172N · Annapolis, MDThe plt crossed mid-field, and entered a left down wind for rwy 30. He then checked wind direction, completed a base leg, and entered final apch. After reducing his airspeed, the acft 'floated' prior to touching down aprx 600 ft short of mid-fld. The plt…NTSB NYC84LA309Accident · No injuriesLimited investigationFinal reportCessna 172N · Gaithersburg, MDDue to a left drifting tendency the solo student plt aborted the first landing. On touchdown for the second apch, the acft again veered left and continued off of the rwy colliding with a ditch. There were no mechanical malfunctons reported or discovered.NTSB ATL83LA216Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Mitchellville, MDThe plt reported that when he was on final apch to land, his speed was a little fast. After touching down, the acft bounced & began drifting to the right. Once the right wheel went off the rwy, the right turn increased & the acft struck a rwy edge light. Full…NTSB ATL83FIG01Accident · No injuriesFinal reportCessna 172N · Mitchellville, MDThe aircraft was landed with 20 degrees flaps at 67 mph. It continued off the end of the 2,150 foot runway, went through a fence and came to rest at the edge of highway route 50. The handbook recommended 40 degrees of flaps and a 61 mph approach speed.NTSB ATL82FIG04Accident · No injuriesClosedCessna 172N · Stevensville, MDNTSB ATL81FIG08Accident · No injuriesClosedCessna 172 · Churchville, MDNTSB ATL81FIG01Accident · Minor injuriesClosedCessna 172N · College Park, MDNTSB ATL80FIG18Accident · No injuriesClosedCessna 172 · Mitchellville, MDNTSB IAD80FIG09Accident · No injuriesClosedCessna 172 · Mitchellville, MDNTSB IAD79FIG12Accident · No injuriesClosedCessna 172 · Gaithersburg, MDNTSB IAD78FIG12Accident · Minor injuriesClosedCessna 172 · Largo, MDNTSB IAD77FIG13Accident · Serious injuriesClosedCessna 172 · Cumberland, MD