NTSB investigations: Cessna 172RG, CA
37 cases on aircraft the registry lists as Cessna 172RG. 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
| 1965 | 1 |
|---|---|
| 1979 | 1 |
| 1981 | 1 |
| 1982 | 1 |
| 1983 | 1 |
| 1984 | 2 |
| 1985 | 2 |
| 1987 | 2 |
| 1988 | 1 |
| 1990 | 2 |
| 1991 | 3 |
| 1993 | 1 |
| 1994 | 1 |
| 1997 | 3 |
| 1999 | 1 |
| 2000 | 1 |
| 2001 | 1 |
| 2002 | 1 |
| 2003 | 2 |
| 2004 | 1 |
| 2005 | 1 |
| 2006 | 2 |
| 2008 | 2 |
| 2013 | 1 |
| 2014 | 1 |
| 2017 | 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\" = 'CA' 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 ('2072438'))
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" = 'CA' 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 ('2072438'))
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 GAA17CA372Accident · No injuriesData collectionFinal reportCessna 172RG · El Cajon, CAThe pilot's failure to extend the landing gear with sufficient time to allow the landing gear to fully extend and the flight instructor's failure to visually check to see if the right main landing gear were extended.NTSB WPR14LA250Accident · No injuriesLimited investigationFinal reportCessna 172RG · Alturas, CAThe airplane’s failure to attain rotation speed during the takeoff roll for reasons that could not be determined because postaccident examination did not reveal any anomalies that would have precluded normal operation. Contributing to the accident was the…NTSB WPR13FA211Accident · 2 fatalClass 3 · FieldFinal reportCessna 172RG · Calabasas, CAThe failure of the pilots in both aircraft to maintain an adequate visual lookout, which resulted in a midair collision.NTSB WPR09CA055Accident · No injuriesData collectionFinal reportCessna 172RG · Truckee, CAThe pilot misjudged the landing flare resulting in a hard landing.NTSB LAX08LA221Accident · Minor injuriesLimited investigationFinal reportCessna 172RG · Moorpark, CAA partial loss of engine power due to the disconnection of the throttle control cable from the throttle arm due to the operator's improper maintenance. Contributing to the accident was unsuitable terrain for a forced landing.NTSB LAX07LA039Accident · No injuriesLimited investigationFinal reportCessna 172RG · San Diego, CAAn undetermined total electrical failure. The pilot's failure to extend the landing gear to the down and locked position was a factor.NTSB LAX06FA106Accident · 3 fatalField investigationFinal reportCessna 172RG · El Cajon, CAThe pilots of both airplanes failure to maintain an adequate visual lookout due to their relative flight paths, which limited the available visual cues. Factors were the failure of the air traffic controller(s) to issue a conflict alert to the Cessna 172RG…NTSB LAX05FA290Accident · 2 fatalField investigationFinal reportCessna 172RG · Avalon, CAan in-flight loss of control for undetermined reasons.NTSB LAX04LA277Accident · No injuriesLimited investigationFinal reportCessna 172RG · San Diego, CAThe pilot's failure to ensure that the landing gear was fully extended, by use of the emergency gear extension system, which resulted in its partial collapse during landing rollout. Also causal was the pilot's failure to follow POH procedures relating to…NTSB LAX04LA011Accident · No injuriesLimited investigationFinal reportCessna 172RG · Camarillo, CAThe fracture and failure of the left landing gear actuator. Contributing to the accident was the operator's failure to comply with the manufacturer's service bulletin.NTSB LAX03LA290Accident · No injuriesLimited investigationFinal reportCessna 172RG · Santa Ana, CAthe failure of the right main landing gear pivot assembly.NTSB LAX02LA292Accident · No injuriesLimited investigationFinal reportCessna 172RG · Del Mar, CAThe loss of engine power due to failure of the number three connecting rod cap. Also causal was the failure of the pilot of a previous flight to report an engine overspeed event precluding the performance of the appropriate maintenance inspection.NTSB LAX01LA123Accident · No injuriesLimited investigationFinal reportCessna 172RG · Stanford, CAFailure of company maintenance personnel to properly install and safety wire the oil filter, which subsequently lead to a loss of engine power.NTSB LAX00LA315Accident · No injuriesLimited investigationFinal reportPitts S1S · Westminister, CAThe pilot of the Pitts misjudged the clearance while maneuvering under the Cessna.NTSB LAX99LA134Accident · No injuriesLimited investigationFinal reportCessna 172RG · Moorpark, CAThe failure and separation of the number two cylinder for undetermined reasons. A factor was the soft terrain at the forced landing site.NTSB LAX98LA036Accident · No injuriesLimited investigationFinal reportCessna 172RG · San Diego, CAOverload of the main gear actuator piston and the subsequent collapse of the landing gear.NTSB LAX97LA297Accident · No injuriesLimited investigationFinal reportCessna 172RG · Lancaster, CAImproper flare.NTSB LAX97LA095Accident · No injuriesLimited investigationFinal reportCessna 172RG · Corona, CAFailure of the pilot in command to follow the airplane's before landing checklist and verify the landing gear was fully extended before landing. Factors in the accident were anxiety and diversion of the pilot's attention due to fuel gauge readings.NTSB LAX94FA353Accident · 4 fatalField investigationFinal reportCessna 172RG · Truckee, CAFailure of the pilot to obtain/maintain adequate airspeed to climb after takeoff, which resulted in a stall and subsequent collision with the ground. Factors related to the accident were: high density altitude, improper trim setting for takeoff, the…NTSB LAX94LA050Accident · No injuriesLimited investigationFinal reportCessna 172RG · Santa Ana, CAwere the CFI's inadequate supervision of the flight and his delay in taking remedial action. The dual student's excessive taxi speed and the worn right brake lining were factors in this accident.NTSB LAX91LA285Accident · Minor injuriesLimited investigationFinal reportCessna 172RG/A · Vacaville, CAThe private pilot PIC failed to maintain directional control during landing rollout. The CFI pilot failed to take remedial action.NTSB LAX91LA233Accident · Minor injuriesLimited investigationFinal reportCessna 172RG · Point Magu, CAA short circuit in the airplane's strobe light electrical system which ignited the plastic tubing of the pitot static system causing an inflight fire and subsequent forced landing.NTSB LAX91FA074Accident · 1 fatalField investigationFinal reportCessna 172RG · Hayward, CAThe pilot's failure to maintain altitude. Contributing factors related to the pilot's improper VFR procedures and his misjudged evaluation of the weather in daylight conditions. Additional factors related to the presence of low clouds and to the restricted…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 LAX90LA236Accident · No injuriesLimited investigationFinal reportCessna 172RG · Concord, CAThe student pilot's initiating an excessive descent and the cfi's inadequate remedial action.NTSB LAX88LA141Accident · No injuriesLimited investigationFinal reportCessna 172RG · Malibu, CAThe pilot stated that the purpose of the flight was to allow the passenger to photograph some yachts sailing off the Malibu coast. The pilot said that he initiated a turn at 300 feet AGL around one of the yachts and the aircraft 'suddenly stalled' and he was…NTSB LAX88FA001Accident · 1 fatalField investigationFinal reportCessna 172RG · Calistoga, CAUpon arriving over the destination arpt the plt used an incorrect CTAF frequency to contact the arpt and he used a right hand traffic pattern approaching the 2600 foot-long rwy. Because a residential area lay west of the arpt & open fields lay to the east,…NTSB LAX87LA118Accident · Serious injuriesLimited investigationFinal reportCessna 172RG · San Diego, CADuring a local pleasure flight, the pilot returned to the airport to practice touch-and-go landings. On take-off, ascending through 200 feet, the engine began to surge then quit. The pilot made a forced landing on an occupied road where the aircraft collided…NTSB LAX85LA271Accident · No injuriesLimited investigationFinal reportCessna 172RG · Upland, CAThe plt stated that on the flt prior to the accident he felt a slight pull to the right as he applied brakes. On the next flt he touched down normally, lowered the nose and lightly applied brakes. The pull to the right was more severe this time. He applied…NTSB LAX85LA096Accident · No injuriesLimited investigationFinal reportCessna 172RG · Camarillo, CAThe plt reported that upon landing a strong gust of wind caused the acft to deviate to the left. Application of the appropriate flight controls did not arrest the deviation. Brakes were applied but not in time to prevent the acft from exiting the rwy. The…NTSB LAX85LA021Accident · No injuriesLimited investigationFinal reportCessna 172RG · El Monte, CAThe plt landed the acft fast & lost control. Subsequently, the acft went off the right side of the rwy & struck a perimeter fence.NTSB LAX84LA364Accident · Serious injuriesLimited investigationFinal reportCessna 172RG · Lee Vining, CAThe plt reported that after entering tioga pass, he made a left turn to follow the center of the pass & the acft began to sink. He applied full power & went to the best angle of climb speed, but was unable to stop the sink. The acft then hit an electrical…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 LAX83IA036Incident · Minor injuriesIncident investigationFinal reportCessna 172RG · Santa Ana, CAWhile cruising at 6500 MSL during a night cross country, the cabin filled with smoke. The pilot declared an emergency and landed after securing all of the electrical equipment. The pilot required hospitalization due to smoke inhalation and an irregular…NTSB LAX81DUG21Accident · No injuriesClosedCessna 172RG · 29 Palms, CANTSB LAX80FA019Accident · 4 fatalClosedCessna 172RG · Lassen Peak, CANTSB LAX66F0178Accident · No injuriesClosedN American P-51D · Santa Monica, CA