# Incident 20170928021409I: Cessna 172N, Riverside, CA, September 28, 2017

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: September 28, 2017, 14:00 local time
- Place: Riverside, CA
- Airport: Riverside Airport
- Damage: No damage
- Phase of flight: Takeoff: Climb Out
- Operating rules: General operating rules (Part 91)
- Location: 33.9519° N, 117.4451° W: Placed by OpenAirDocs at RIVERSIDE (RAL), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=33.9519&lon=-117.4451&mi=10
- Aircraft: N5184J, registered now (https://openairdocs.org/aircraft/N5184J) (OpenAirDocs)
- Registry model: Cessna 172N (registry code 2072434, https://openairdocs.org/model/cessna-172n) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172N
- Reported engine: LYCOMING 0-320 SERIES
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot
- Pilot flight hours: 1,360 total, 634 in this make and model, 231 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20170928021409I

## Narrative

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

DURING TAKEOFF FROM (RAL) RIVERSIDE AIRPORT THE PILOT REPORTED THAT THE ENGINE STARTED TO SURGE AND WAS ACCOMPANIED BY A STIFF JOLT OF THE ENGINE COWLING. THE SURGING OCCURRED ABOUT ONCE EVERY TWO SECONDS. THE PILOT ALSO NOTICED THAT THE OIL TEMP WAS UNUSUALLY HIGH. AFTER THE FIRST TWO SURGES THE INSTRUCTOR PILOT TOOK CONTROL OF THE AIRCRAFT AND TURNED BACK TOWARDS THE AIRPORT.  THE PILOT INFORMED THE TOWER THAT THEY NEEDED TO RETURN TO THE AIRPORT AND LANDED THE AIRCRAFT ON RUNWAY 27 WITHOUT INCIDENT AND TAXIED BACK TO RIVERSIDE FLIGHT ACADEMY BEFORE SHUTTING DOWN THE ENGINE.

## Other reports on N5184J (5)

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

- [Incident 20201105018109I](https://openairdocs.org/incident/20201105018109I), Nov 5, 2020: Cessna 172N (N5184J), Riverside, CA, Minor damage. On 11/05/2020 about 10:00AM a student pilot took off on his first solo flight. Previous to his first solo take off he did three takeoffs and landings with his…
- [Incident 19990815012329I](https://openairdocs.org/incident/19990815012329I), Aug 15, 1999: Cessna 172N (N5184J), Denver, CO, Minor damage. Pilot reported hard landing at apa arpt after performing several touch and go's. (-23) student pilot was flying in local traffic pattern on unsupervised solo.…
- [Incident 19920718031739I](https://openairdocs.org/incident/19920718031739I), Jul 18, 1992: Cessna 172N (N5184J), Greeley, CO. Electrical failure en route. Pilot diverted to Greeley.
- [Incident 19890627041479I](https://openairdocs.org/incident/19890627041479I), Jun 27, 1989: Cessna 172N (N5184J), Denver, CO. Aircraft reported to be flying low over rock concert at 500 ft. pilot states he was at 1000 feet.
- [Incident 19831115071079I](https://openairdocs.org/incident/19831115071079I), Nov 15, 1983: Cessna 172N (N5184J), Englewood, CO. Student lost control while landing with a light tailwind. Tower was in process of changing runways.

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.