# Accident 19980425013299A: Cessna 172N, Parker, CO, April 25, 1998

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: April 25, 1998, 13:30 local time
- Place: Parker, CO
- Damage: Substantial damage
- Phase of flight: Forced Landing
- Operating rules: General operating rules (Part 91)
- Location: 39.5004° N, 104.7596° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=39.5004&lon=-104.7596&mi=10
- Aircraft: N6356D, a cancelled registration (https://openairdocs.org/deregistered/N6356D-2012-08-03) (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: LYC O320H2AD
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 7,300 total, 5,000 in this make and model, 79 in the last 90 days
- NTSB investigation: [NTSB FTW98LA198](https://openairdocs.org/ntsb/FTW98LA198) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19980425013299A

## Narrative

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

ENGINE LOST POWER ON DUAL FLIGHT. LANDED IN MUDDY FIELD. NOSED OVER. (.4)THE INSTRUCTOR PILOT (CFI) SAID THAT AFTER COMPLETING A LOCAL INSTRUCTIONAL FLIGHT, HE AND HIS STUDENT ENTERED AN EXTENDED RIGHT BASE FOR RUNWAY 35R, ABOUT 5 MILES SOUTHEAST OF THE AIRPORT. HE 'SUDDENLY HEARD THE ENGINE LOSE A MAJOR PORTION OF POWER.'  WHILE PERFORMING AN EMERGENCY CHECK OF THE INSTRUMENTS, THE INSTRUCTOR NOTED THAT THE ENGINE POWER HAD DROPPED TO 1,800 RPM. REALIZING THEY WOULD BE UNABLE TO GLIDE TO THE AIRPORT DUE TO THE LOSS OF ENGINE POWER, THE CFI EXECUTED AN EMERGENCY LANDING ON A FIELD NEAR A GOLF COURSE. THE GROUND WAS MUDDY DUE TO AN ACCUMULATION OF RAIN AND SNOW FROM THE PREVIOUS NIGHT. AFTER THE AIRPLANE TRAVELED A SHORT DISTANCE, THE NOSE WHEEL STRUCK A RUT, AND THE AIRPLANE NOSED OVER. EXAMINATION OF THE AIRCRAFT ENGINE REVEALED THAT THE #1 (RIGHT FRONT) CYLINDER INTAKE PUSHROD WAS BENT.  AFTER REMOVING THE VALVE COVER, A STUD THAT ANCHORED THE #1 EXHAUST VALVE ROCKER ARM WAS FOUND TO BE FRACTURED, AND THE #1 EXHAUST VALVE WAS IN THE CLOSED POSITION. THERE WAS NO DAMAGE TO THE VALVE LIFTERS OR CAMSHAFT.                                                                               (-23)DURING INSTRUCTIONAL FLIGHT ENGINE BEGAN TO LOOSE POWER. WHEN INSTRUCTOR REALIZED THAT HE COULD NOT MAKE IT BACK TO AIRPORT HE LANDED IN FIELD.  THE FIELD WAS EXTREMELY MUDDY AND THE NOSE WHEEL DUG INTO MUD AND AIRCRAFT FLIPPED OVER.

## 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 FTW98LA198](https://openairdocs.org/ntsb/FTW98LA198), Apr 25, 1998: Cessna 172N (N6356D), Parker, CO, substantial damage. Probable cause: a fractured #1 exhaust valve rocker arm stud, which subsequently resulted in loss of engine power and a forced landing. The lack of suitable terrain in the forced landing area was a related factor.

## Other reports on N6356D (2)

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

- [Accident 19900427013029A](https://openairdocs.org/incident/19900427013029A), Apr 27, 1990: Cessna 172N (N6356D), Denver, CO, Substantial damage. Wind gusty on final due approaching front then reversed and blew over aircraft on landing roll after slowing down.
- [Accident 19881206053069A](https://openairdocs.org/incident/19881206053069A), Dec 6, 1988: Cessna 172N (N6356D), Denver, CO, Substantial damage. Student bounced, added power and nosed up. Took off power, hit runway, and veered into parked aircraft.

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.