Aviation Accident Summaries

Aviation Accident Summary CHI06LA084

Muncie, IN, USA

Aircraft #1

N75593

Cessna 172

Analysis

The airplane sustained substantial damage during a forced landing to a field after a loss of engine power. The solo student pilot reported that he was practicing three full stop landings at a tower-controlled airport. He taxied to the runway and completed the Before Takeoff checklist. He called tower and was cleared for takeoff for a right traffic pattern. He reported that he climbed to 2,000 feet mean sea level (msl) during a right downwind. At midfield he turned the carburetor heat on and performed the Before Landing checklist. Once he was abeam the touchdown point, he decreased the throttle and put in 10 degrees of flaps. He put in 20 degrees of flaps on base leg. He reported that while on final, he increased the throttle to gain altitude but the engine did not respond. He reported, "I verified the Carb Heat was on, Mixture was full Rich, and Fuel Selector was on." He cycled the throttle to full but the engine did not respond. He executed an engine out forced landing. Tall power lines were directly in front of the airplane so he turned to the left to avoid them. He landed the airplane in a cornfield, but the airplane's left wing struck some trees at the end of the field. The inspection of the airplane revealed no anomalies. A test run of the engine was limited to 2,000 rpm. The throttle was manipulated through the 1,500 to 2,000 rpm range and the engine ran properly. No defects were noted.

Factual Information

On February 20, 2006, at 1745 eastern standard time, a Cessna 172, N75593, operated by Flying Squirrels, Inc., sustained substantial damage during a forced landing after a loss of engine power to a field near the Delaware County Airport (MIE), Muncie, Indiana. The solo student pilot received minor injuries. The 14 Code of Federal Regulations Part 91 solo instructional flight departed MIE at 1740 on a local flight. Visual meteorological conditions prevailed at the time of the accident. No flight plan was filed. The student pilot and the instructor pilot had flown from Kokomo Municipal (OKK) to MIE so that the student pilot could do three solo landings and takeoffs at an airport with an operating control tower. Once they arrived at MIE, the instructor pilot exited the airplane while the engine remained running. The student pilot taxied to runway 20 and completed the Before Takeoff checklist. He called the tower and was cleared for takeoff and a right traffic pattern. The student pilot reported that he climbed to 2,000 feet mean sea level (msl) while on a right downwind. At midfield he turned the carburetor heat on and performed the Before Landing checklist. Once he was abeam the touchdown point, he decreased the throttle and put in 10 degrees of flaps. He put in 20 degrees of flaps on base leg. He reported that while on final, the air traffic control tower informed him that he would have to make a quick stop-and-go. The student acknowledged the transmission. The student pilot reported that while on final approach, he increased the throttle to gain altitude, but the engine did not respond. He reported, "I verified the Carb Heat was on, Mixture was full Rich, and Fuel Selector was on." He cycled the throttle to full, but the engine did not respond. He executed an engine out forced landing. Tall power lines were directly in front of the airplane so he turned to the left to avoid them. He landed the airplane in a cornfield, but the airplane's left wing struck some trees at the end of the field. Once the airplane came to a stop, he secured the engine and exited the airplane. A Federal Aviation Administration airworthiness inspector examined the airplane. The inspection of the airplane revealed no anomalies. A test run of the engine was limited to 2,000 rpm's. The inspector reported he manipulated the throttle through the 1,500 to 2,000 rpm range and the engine ran properly. No defects were noted.

Probable Cause and Findings

The loss of engine power during the final approach to land for an undetermined reason.

 

Source: NTSB Aviation Accident Database

Get all the details on your iPhone or iPad with:

Aviation Accidents App

In-Depth Access to Aviation Accident Reports