NTSB investigations: Cessna 172RG
17 cases on aircraft the registry lists as Cessna 172RG, where the first occurrence was “In flight collision with terrain/water”. 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 | 1 |
|---|---|
| 1983 | 2 |
| 1984 | 2 |
| 1986 | 2 |
| 1987 | 2 |
| 1990 | 2 |
| 1992 | 1 |
| 1994 | 1 |
| 1995 | 1 |
| 1996 | 1 |
| 2000 | 1 |
| 2001 | 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 ('2072438')
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\" = 230))
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 ('2072438')
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" = 230))
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 DEN01LA130Accident · Serious injuriesLimited investigationFinal reportCessna 172RG · Gunnison, COthe pilot's failure to attain the proper climb rate, and his improper inflight planning/decision to attempt to cross mountainous terrain at an inadequate altitude. Contributing factors were the downdraft and the pilot's total lack of experience in mountain…NTSB LAX00FA207Accident · 2 fatalField investigationFinal reportCessna 172RG · Prescott, AZThe flight instructor's delayed remedial action, and his failure to correct an inappropriate descent during maneuvering flight, while engaged in commercial flight training maneuvers.NTSB LAX97FA003Accident · 4 fatalField investigationFinal reportCessna 172RG · Grand Canyon, AZthe pilot's inadequate preflight planning and preparation, which resulted in an inability to outclimb rising/wooded terrain after takeoff. Factors relating to the accident were: failure of the pilot to ensure that the aircraft's gross weight was not exceed…NTSB FTW95LA168Accident · No injuriesLimited investigationFinal reportCessna 172 RG · Tulsa, OKThe pilot's improper emergency procedure preventing emergency gear extension. A factor was the loss of electrical alternator power for undetermined reasons.NTSB FTW94FA101Accident · 4 fatalField investigationFinal reportCessna 172RG · Dulce, NMFailure by the pilot in command to properly plan the flight and calculate performance data.NTSB LAX92LA228Accident · 1 fatalLimited investigationFinal reportCessna 172RG · Strawberry, AZThe pilot committed suicide due to the pilot's emotional state from interpersonal relations.NTSB LAX91LA032Accident · 1 fatalLimited investigationFinal reportCessna 172RG · San Clemente, CAThe pilots selection of improper cruise altitude while operating under a low overcast on a dark night. A factor in the accident was fatigue and lack of sleep.NTSB SEA90LA172Accident · Serious injuriesLimited investigationFinal reportCessna 172RG · Brothers, ORThe pilot's improper flight planning and decisions that led to him flying into rising terraain while engaged in low level flight activities.NTSB SEA87FA166Accident · 1 fatalField investigationFinal reportCessna 172RG · Kettle Falls, WAWhile on a local personal flight, plt entered a canyon into rising terrain, colliding first with a tree and then ground near crest. Investigation revealed that acft probably had performance to clear crest had tree not been struck. Circumstances indicate plt…NTSB DEN87LA197Accident · No injuriesLimited investigationFinal reportCessna 172RG · Aspen, COThe plt said that because of thunderstorm activity in the local area he was distracted from concentrating on his flying. During his landing approach, he failed to extend the landing gear and landed the aircraft wheels up.NTSB CHI87LA051Accident · Serious injuriesLimited investigationFinal reportCessna 172RG · Bloominton, INAccording to the pilot he was cleared for the ILS approach and followed his glideslope and localizer indications in a normal manner. He eventually saw the ground prior to reaching his decision height of approx 200 feet AGL. This sighting of the ground was the…NTSB MIA86LA169Accident · No injuriesLimited investigationFinal reportCessna 172RG · Jackson, MSThe plt stated that she intentionally landed gear up because the nose wheel well doors were jammed closed and would not allow the gear to completely lock down. Examination of the nose landing gear revealed that the nose gear up stop bumper plate assembly fell…NTSB DEN84FA196Accident · 3 fatalField investigationFinal reportCessna 172RG · Red Feather Lak, COAcft departed downwind into rising terrain with density altitude calculated to be 10,935 ft. acft was observed to mush into rising terrain 300 ft higher than and 3 mi west of the rwy.NTSB ANC84LA029Accident · No injuriesLimited investigationFinal reportCessna 172RG · Big Lake, AKThe dual student and instructor were practicing emergency procedures. During the turn onto final approach the left main landing gear and left wing struck a snowbank. Flying club procedures state that no emergency practice procedure will be conducted below 500…NTSB MIA84FA038Accident · 1 fatalField investigationFinal reportCessna 172RG · Cross City, FLWhile in the vicinity of Cross City the plt requested VFR flt following from jacksonville ARTCC. While he was in radio &radar contact, the controller suddenly lost radar contact with the flt. Radar indicated that the acft made a rapid descent from the cruise…NTSB LAX83FUM06Accident · Serious injuriesFinal reportCessna 172RG · San Clemente, CAThe acft crashed on San Clemente island during a fish spotting flt on a dark night. These flts are usually flown at an alt of 1000-2000 ft AGL. A navy witness on the accident island said the ceiling was zero and the visibility about 200 yards at the accident…NTSB NYC82DA042Accident · No injuriesFinal reportCessna 172RG · Palmer, MAThe pilot initiated a takeoff on runway 04. He reported the wind was from 300 to 330 degrees at 10 gusting 25 KTS. During the takeoff roll, a bump in the runway was encountered and the aircraft became airborne. The pilot reported that a gust of wind from the…