# Accident 20040723017669A: Cessna 172RG, San Diego, CA, July 23, 2004

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: July 23, 2004, 20:03 local time
- Place: San Diego, CA
- Airport: Montgomery Field Airport
- Damage: Substantial damage
- Phase of flight: Roll-Out (Fixed Wing)
- Operating rules: General operating rules (Part 91)
- Location: 32.8156° N, 117.1394° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=32.8156&lon=-117.1394&mi=10
- Aircraft: N5167R, a cancelled registration (https://openairdocs.org/deregistered/N5167R-2018-05-30) (OpenAirDocs)
- Registry model: Cessna 172RG (registry code 2072438, https://openairdocs.org/model/cessna-172rg) (OpenAirDocs)
- Registry engine: Lycoming O-360 series (registry code 41575, https://openairdocs.org/engine/lycoming-o-360-series) (OpenAirDocs)
- Reported make and model: CESSNA 172RG
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 260 total, 7 in this make and model, 13 in the last 90 days
- NTSB investigation: [NTSB LAX04LA277](https://openairdocs.org/ntsb/LAX04LA277) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20040723017669A

## Narrative

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

(-23) ON JULY 23, 2004, N5167R, A CESSNA CE-172-RG AIRCRAFT WAS INVOLVED IN AN ACCIDENT WHILE CONDUCTING A FULL STOP LANDING AT MONTGOMERY AIRFIELD (KMYF) SAN DIEGO, CA. DURING LANDING ROLL OUT THE RIGHT MAIN LANDING GEAR COLLAPSED. THE AIRCRAFT SUSTAINED SUBSTANTIAL DAMAGE; THE PILOT, THE ONLY OCCUPANT, WAS NOT INJURED. THE FLIGHT DEPARTED (KMYF) AT APPROXIMATELY 1910 PACIFIC TIME UNDER INSTRUMENT FLIGHT RULES (IFR) TO TORRANCE AIRPORT (KTOA). ENROUTE THE LOW VOLTAGE ILLUMINATED FOLLOWED BY A COMPLETE ELECTRICAL FAILURE. THE PILOT TERMINATED THE IFR FLIGHT AND RETURNED TO (KMYF). THIS ACCIDENT IS NOT RELATED TO A NMAC OR PILOT DEVIATION.

## 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 LAX04LA277](https://openairdocs.org/ntsb/LAX04LA277), Jul 24, 2004: Cessna 172RG (N5167R), San Diego, CA, substantial damage. Probable cause: The 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…

## Other reports on N5167R (5)

Matched to the same aircraft by N-number and date.

- [Incident 20141228023879I](https://openairdocs.org/incident/20141228023879I), Dec 28, 2014: Cessna 172RG (N5167R), El Cajon, CA, Minor damage. Detected abnormal landing gear operation, did not lock. Troubleshot using checklist and p.o.h, attempted to lower gear using g-force manuevers and emergency…
- [Incident 20060830022079I](https://openairdocs.org/incident/20060830022079I), Aug 30, 2006: Cessna 172RG (N5167R), El Cajon, CA, Minor damage. (-23) Conduct of this flight was for the purpose of a commercial certificate check ride. The designated pilot examiner (DPE) stated that during the take-off…
- [Incident 20021012030369I](https://openairdocs.org/incident/20021012030369I), Oct 12, 2002: Cessna 172RG (N5167R), Bakersfield, CA, Minor damage. (-23) Flight crew reported that the landing gear indicated as being down and locked, green light, but on landing roll-out, the aircraft nose continued to…
- [Incident 19920521019669I](https://openairdocs.org/incident/19920521019669I), May 21, 1992: Cessna 172RG (N5167R), San Diego, CA, Minor damage. Pilot inadvertently selected the landing gear control to the up position on a touch and go. Nose gear collapsed.
- [Incident 19800913070519I](https://openairdocs.org/incident/19800913070519I), Sep 13, 1980: Cessna 172RG (N5167R), Beaufort, NC, Minor damage. Pilot landed gear up.

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.