# NTSB CHI01LA303: Cessna 172N, N5593E, Sheldon, IA, September 1, 2001

- Type: NTSB accident investigation
- Classification: Accident · Minor injuries · Limited investigation · Final report
- Date: September 1, 2001, 18:25 local (23:25 UTC)
- Place: Sheldon, IA
- Coordinates: 43.170478, -95.840438 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=43.1705&lon=-95.8404&mi=10
- Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping)
- Highest injury: Minor injuries
- Injuries: 1 minor, 1 uninjured
- Status: Completed, report January 23, 2002
- Report: Approved by Office Director
- Parties: Federal Aviation Administration
- NTSB case key (mKey): 53406
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CHI01LA303
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/53406/pdf
- Page: https://openairdocs.org/ntsb/CHI01LA303

## Probable cause

the in-flight planning/decision and proper touchdown point not attained by the pilot.  Contributing factors were the ingested exhaust valve and lack of experience of the pilot.

## Sequence of events

In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf).

- Loss of engine power(partial) - mech failure/malf, approach
- Loss of engine power(total) - mech failure/malf, go-around (vfr)
- In flight collision with terrain/water, emergency landing
  - in-flight planning/decision - inadequate, pilot in command (cause)
  - lack of experience, pilot in command (contributing factor)
  - engine assembly,valve,exhaust - ingested (contributing factor)
  - proper touchdown point - not attained, pilot in command (cause)
- Nose over, emergency landing

## Analysis

The airplane experienced a rough running engine 1/4 mile from the approach end of runway 33 (4,199 feet by 75 feet, concrete) at an altitude of 1,581 feet above the airport.   The pilot reported being too high and fast while landing on runway 33 with 20 degrees of flaps, so he executed a go around which was then followed by a total loss of engine power. The airplane landed in a dry corn field and came to rest inverted.  The private pilot had a total flight time of 119 hours.  The Flight Training Handbook cites techniques for performing an emergency landing and also states that the eagerness to get down is one of the most common faults of inexperienced pilots during simulated forced landings resulting in excessive speed to permit a safe landing.  Examination of the engine revealed an ingested exhaust valve from the number two cylinder.

## Factual narrative

On September 1, 2001, at 1825 central daylight time, a Cessna 172N, N5593E, operated by Midwest Flying Service Incorporated, was substantially damaged during a forced landing on a cornfield one mile northwest of the Sheldon Municipal Airport (SHL), Sheldon, Iowa.   The pilot reported a rough running engine while on approach to runway 33 (4,199 feet by 75 feet, concrete).  Visual meteorological conditions prevailed at the time of the accident.  The 14 CFR Part 91 personal flight was operating on a visual flight rules flight plan.  The private pilot received no injuries and passenger received minor injuries.  The flight departed from the Des Moines International Airport, Des Moines, Iowa, at 1705, en route to SHL.

The pilot reported the following in a written statement, "...I was coming back from a cross-country trip originated from Des Moines, IA.  Where we refueled full tanks.  I believe I opened my VFR flight plan about 5:05 CST. ... I tried to get AWOS for altimeter setting, wind direction and velocity information when about 10 miles of the airport but I didn't work for some reason.  So I decided to cross the field at higher altitude than pattern altitude as recommended to find out the wind direction from the windsock.  (Refer to figure attached, #1).  The wind was from about 180 degrees.  I needed then to land on runway 15.  So I went on heading 150 degrees close to the runway (#4), at point #5 the engine started to shake real bad, I decided to proceed with an emergency landing downwind.  But I was too close to the runway, high and too fast to make it on runway 33.  But still I tried (#6).  At point #7, I decided to go-around realizing for sure that I wouldn't have enough runway to land safely.  At point #8, at less than 400' AGL, the engine quit while I started a climb for a go-around.  At that point all I could do was to put the plane in gliding attitude with appropriate angle of attack, correct airspeed and find a suitable field to land.  The cornfield was my best choice (#9).  We landed safely on the main landing gear, the plane rolled for a while; then the cornstalk resistance made the plane flips upside down..."

During a postaccident telephone interview, the pilot stated that approximately 25 nm from SHL the engine began to run rough but thinking that it was carburetor ice he selected carburetor heat which stopped the engine roughness.  He added that the engine began to run rough approximately 1/4 mile from the approach end of runway 33 and at an altitude of approximately 3,000 feet msl.  He selected a flap setting of 20 degrees for a landing flap setting on runway 33.  During the go around, the engine quit and the pilot landed on a reportedly dry corn field with approximately 6 foot tall corn stalks.  The airplane nosed over and came to rest.

SHL elevation is 1,419 feet msl.

Advisory Circular 61-21A, Flight Training Handbook, "Emergency Approaches (Simulated)", states, "...Slipping the airplane, using flaps, varying the position of the base leg, and varying the turn onto final approach should be stressed as ways of correcting for misjudgment of altitude and glide angle.  Eagerness to get down is one of the most common faults of inexperienced pilots during simulated forced landings.  In giving way to this, they forget about speed and arrive at the edge of the field with too much speed to permit a safe landing.  Too much speed may be just as dangerous as too little; it results in excessive floating and overshooting the desired landing spot..."

The pilot reported a total flight time of 119 hours all of which were in the make and model of the accident airplane.

Examination of the engine by the Federal Aviation Administration (FAA) revealed a missing exhaust valve from the number two cylinder.  The valve was not found in the exhaust system or elsewhere in the engine.  The piston dome was damaged but not punctured.

The Lycoming O-320-H2AD, serial number RL-1767-76T, engine accumulated a total time of 1,595.6 hours since overhaul.

## Aircraft

- Registration: [N5593E](https://openairdocs.org/deregistered/N5593E-2013-08-20), registration cancelled 2013-08-20, S/N 17271895, built 1978 (OpenAirDocs)
- Reported make and model: Cessna 172N
- Registry model: [Cessna 172N](https://openairdocs.org/model/cessna-172n) (registry code 2072434) (OpenAirDocs)
- Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 17271895
- Airframe hours: 6879.9
- Engines: Lycoming O-320-H2AD 160 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Registered owner: Midwest Flying Service Inc.
- Airworthiness certificate: Standard, Normal
- Last inspection: 100 hour, July 24, 2001, 55.9 hours before
- Departed: DSM, Des Moines, IA
- Destination: SHL, Sheldon, IA
- Flight plan: VFR
- Airport: SHL, Sheldon Municipal, runway 33, 4,199 × 75 ft, concrete

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 45; injuries: minor; private; airplane ratings: single-engine land; medical: class 3, valid medical--no waivers/lim.; seat: left; flight hours: 119 total, 119 in this make and model, 42 as pilot in command, 27 in the last 90 days, 7 in the last 30 days

## Weather

- Conditions: Visual (VMC), Day
- Wind: 160° at 8 knots
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 75 °F, dew point 66 °F
- Altimeter: 29.92 inHg
- Observed at: SHL, 1 nm away

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20010901033069A](https://openairdocs.org/incident/20010901033069A), Sep 1, 2001: Cessna 172M, Sheldon, IA, No damage. (-23) Pilot stated he was returning from des moines, Iowa on a pleasure flight with his wife when the engine started running rough over cherokee, Iowa. When he…

## Other investigations on N5593E (2)

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 IAD98LA030](https://openairdocs.org/ntsb/IAD98LA030), Feb 26, 1998: Cessna 172 (N5593E), Rutland, VT, substantial damage. Probable cause: the pilot's improper in-flight planning/decision, which resulted in fuel exhaustion, loss of engine power, and a forced landing. Related factors were: unfavorable (headwind) conditions, and…
- [NTSB NYC80DHA03](https://openairdocs.org/ntsb/NYC80DHA03), Jan 6, 1980: Cessna 172N (N5593E), Reading, PA, substantial damage

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.

---
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.
