# Incident 19940502013319I: Cessna 152, Spring Hill, KS, May 2, 1994

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: May 2, 1994, 11:45 local time
- Place: Spring Hill, KS
- Phase of flight: Simulated Forced Landing/Tkof
- Operating rules: General operating rules (Part 91)
- Location: 38.7567° N, 94.8210° W: Placed by OpenAirDocs: center of Spring Hill, KS, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=38.7567&lon=-94.8210&mi=10
- Aircraft: N6142Q, a cancelled registration (https://openairdocs.org/deregistered/N6142Q-2013-08-19) (OpenAirDocs)
- Registry model: Cessna 152 (registry code 2071835, https://openairdocs.org/model/cessna-152) (OpenAirDocs)
- Registry engine: Lycoming 0-235 series (registry code 41505, https://openairdocs.org/engine/lycoming-0-235-series) (OpenAirDocs)
- Reported make and model: CESSNA 152
- Reported engine: LYC O235L2C
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 2,000 total, 800 in this make and model, 160 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19940502013319I

## Narrative

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

ON A SIMULATED ENFGINE FAILURE, ENGINE FAILED TO RESPOD. FORCED LANDING IN FIELD.

## Other reports on N6142Q (2)

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

- [Incident 19950218006149I](https://openairdocs.org/incident/19950218006149I), Feb 18, 1995: Cessna 152 (N6142Q), Warrensburg, MO, Minor damage. Narrative: while taxiing at night, the pilot inadvertently taxied into a "pot-hole" resulting in minor damage to the propeller tip. The pilot was counseled on…
- [Incident 19851220072769I](https://openairdocs.org/incident/19851220072769I), Dec 20, 1985: Cessna 152 (N6142Q), Franktown, CO. Severe vibration with loss of RPM at cruise. No damage during field landing. Valve clearance adjustment screw loose

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.