# Accident 19970128001149A: Cessna 172RG, Corona, CA, January 28, 1997

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: January 28, 1997, 15:00 local time
- Place: Corona, CA
- Airport: Corona Municipal Airport
- Damage: Substantial damage
- Phase of flight: Fcd/Prec Ldg From Cruise
- Operating rules: General operating rules (Part 91)
- Location: 33.8977° N, 117.6024° W: Placed by OpenAirDocs at CORONA MUNI (AJO), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=33.8977&lon=-117.6024&mi=10
- Aircraft: N80138, registered now (https://openairdocs.org/aircraft/N80138) (OpenAirDocs)
- Registry model: Cessna 172RG (registry code 2072438, https://openairdocs.org/model/cessna-172rg) (OpenAirDocs)
- Registry engine: Lycoming O&VO-360 series (registry code 41514, https://openairdocs.org/engine/lycoming-o-vo-360-series) (OpenAirDocs)
- Reported make and model: CESSNA 172RG
- Reported engine: LYC O360F1A6
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 288 total, 32 in this make and model, 10 in the last 90 days
- NTSB investigation: [NTSB LAX97LA095](https://openairdocs.org/ntsb/LAX97LA095) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19970128001149A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

AIRCRAFT LANDING GEAR COLLAPSED ON LANDING.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     (.4)THE PILOT NOTICED THAT THE FUEL GAUGES WERE INDICATING THAT THE FUEL QUANTITY WAS LOW ABOUT 20 MINUTES INTO THE FLIGHT. HE ELECTED TO MAKE A PRECAUTIONARY LANDING AT THE NEAREST AIRPORT.  THE PILOT SAID HIS APPROACH WAS HIGH AND FAST AND HE LANDED LONG ON THE RUNWAY.  THE AIRPLANE WAS OBSERVED CROSSING THE RUNWAY THRESHOLD WITH THE LANDING GEAR IN TRANSIT.  THE AIRPLANE TOUCHED DOWN WITH THE LANDING GEAR NOT FULLY EXTENDED, THE MAIN GEAR COLLAPSED, AND THE AIRPLANE SLID OFF THE RUNWAY.  AFTER THE ACCIDENT, 42 GALLONS OF FUEL WERE DRAINED FROM THE AIRPLANE.  NO EVIDENCE WAS FOUND OF A LANDING GEAR SYSTEM MALFUNCTION DURING A POSTACCIDENT EXAMINATION.  THE AIRPLANE'S NORMAL PROCEDURE CHECKLIST INSTRUCTS THE PILOT TO CHECK AND OBSERVE THE MAIN GEAR IS DOWN AND THE GREEN GEAR DOWN INDICATOR LIGHT IS ILLUMINATED.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB LAX97LA095](https://openairdocs.org/ntsb/LAX97LA095), Jan 28, 1997: Cessna 172RG (N80138), Corona, CA, substantial damage. Probable cause: Failure 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…

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.