# NTSB CEN09CA148: Cessna 172, N53576, Union Mills, IN, February 1, 2009 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: February 1, 2009, 12:30 local (17:30 UTC) - Place: Union Mills, IN - Coordinates: 41.453887, -86.792221 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=41.4539&lon=-86.7922&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach-VFR go-around: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report April 28, 2011 - Report: Approved by Office Director - NTSB office: Central Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 73304 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN09CA148 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/73304/pdf - Page: https://openairdocs.org/ntsb/CEN09CA148 ## Probable cause The certificated flight instructor's failure to follow correct engine clearing procedures. A factor was the unsuitable landing area. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Planning/preparation](https://openairdocs.org/ntsb-findings/02061000): Personnel issues › Task performance · Instructor/check pilot (probable cause); cases with it: [Cessna 172S, 1 case](https://openairdocs.org/ntsb-findings/02061000/cases.md?model=2072439), [All aircraft, 113 cases](https://openairdocs.org/ntsb-findings/02061000/cases.md) - [Action: delayed action](https://openairdocs.org/ntsb-findings/02041025): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Cessna 172S, 30 cases](https://openairdocs.org/ntsb-findings/02041025/cases.md?model=2072439), [All aircraft, 894 cases](https://openairdocs.org/ntsb-findings/02041025/cases.md) - [Performance/control parameters: powerplant parameters](https://openairdocs.org/ntsb-findings/01062050): Aircraft › Aircraft oper/perf/capability · Not specified (probable cause); cases with it: [Cessna 172S, 1 case](https://openairdocs.org/ntsb-findings/01062050/cases.md?model=2072439), [All aircraft, 81 cases](https://openairdocs.org/ntsb-findings/01062050/cases.md) - [Runway/land/takeoff/taxi surface: snow/slush/ice covered surface](https://openairdocs.org/ntsb-findings/03023015): Environmental issues › Physical environment · Effect on equipment (probable cause); cases with it: [Cessna 172S, 6 cases](https://openairdocs.org/ntsb-findings/03023015/cases.md?model=2072439), [All aircraft, 219 cases](https://openairdocs.org/ntsb-findings/03023015/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach-IFR final approach: Simulated/training event](https://openairdocs.org/ntsb-events/600); cases with it: [Cessna 172S, 8 cases](https://openairdocs.org/ntsb-events/600/sequence.md?model=2072439), [All aircraft, 173 cases](https://openairdocs.org/ntsb-events/600/sequence.md) - [Approach-VFR go-around: Attempted remediation/recovery](https://openairdocs.org/ntsb-events/060); cases with it: [Cessna 172S, 22 cases](https://openairdocs.org/ntsb-events/060/sequence.md?model=2072439), [All aircraft, 1,422 cases](https://openairdocs.org/ntsb-events/060/sequence.md) - [Approach-VFR go-around: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470) (defining event); cases with it: [Cessna 172S, 118 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2072439), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The certificated flight instructor (CFI) and student pilot departed on an introductory instructional flight towards a training area where they performed basic flight maneuvers. They then flew to an airport where the CFI demonstrated a simulated forced landing which was to be followed by a go-around to a runway that was reportedly covered with about 12-14 inches of snow. During the demonstration, the CFI reduced engine power to idle from an altitude of 2,000 feet mean sea level and executed a descent to an altitude of about 5 - 6 feet above ground level at 60 knots indicated airspeed. The CFI did not increase engine throttle during this descent to clear the engine. The CFI applied full throttle during the go-around, but the engine hesitated and the airplane continued to descend. The main landing gear wheels followed by the airplane's nose contacted the snow. The left wing contacted the ground followed by the right wing.. Both wings buckled, resulting in substantial damage to the airplane. The Federal Aviation Administration Flight Training Handbook states in the section under 'Descents (Maximum Distance Glides)' that during power-off descents, the engine should be cleared periodically to prevent excessive cooling and fouling. ## Factual narrative A flight instructor and student pilot departed on an introductory instructional flight towards a training area where they performed basic flight maneuvers. They then flew to Flying U Ranch Airport, Union Mills, Indiana, where the flight instructor demonstrated a simulated forced landing which was to be followed by a go-around to runway 18 (2,745 feet by 100 feet, grass). The runway was reportedly covered with about 12-14 inches of snow. During the demonstration, the flight instructor reduced engine power to idle from an altitude of 2,000 feet mean sea level and executed a descent to an altitude of about 5 - 6 feet above ground level at 60 knots indicated airspeed. The flight instructor did not increase engine throttle during this descent to "clear the engine." The flight instructor applied full throttle during the go-around, but the engine hesitated and the airplane continued to descend. The main landing gear wheels followed by the airplane nose contacted the snow. The left wing followed by the right wing then contacted the ground. Both wings buckled from the ground contact resulting in substantial damage to the airplane. The flight instructor accumulated a total flight time of 2,163 hours as an instructor. ## Aircraft - Registration: [N53576](https://openairdocs.org/aircraft/N53576), registered now, S/N 172S9398 (OpenAirDocs) - Reported make and model: CESSNA 172 (S) - Registry model: [Cessna 172S](https://openairdocs.org/model/cessna-172s) (registry code 2072439) (OpenAirDocs) - Category: Airplane - Serial number: 172S9398 - Airframe hours: 3136 - Engines: LYCOMING IO360 180 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Operator: J.S. Aviation Inc., doing business as Eagle Aircraft - Registered owner: Aerogramm LLC - Airworthiness certificate: Standard, Normal; Standard, Utility - Last inspection: 100 hour, October 24, 2008 - Departed: VPZ, Valparaso, IN - Destination: VPZ, Valparaso, IN - Flight plan: Unknown - Airport: 4C1, Flying U Ranch, runway 18, 2,745 × 100 ft, snow ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 67; injuries: none; flight instructor, commercial; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, without waivers/limitations; last flight review October 10, 2008; seat: right; flight hours: 3,204 total, 1,568 in this make and model, 2,991 as pilot in command, 59 in the last 90 days, 10 in the last 30 days - Student pilot; age 52; injuries: none; medical: unknown; seat: left ## Weather - Conditions: Visual (VMC), Day - Wind: 220° at 9 knots - Visibility: 10 statute miles - Lowest ceiling: 10,000 ft broken - Temperature: 36 °F, dew point 25 °F - Altimeter: 29.92 inHg - Observed at: VPZ ## 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 20090201001429A](https://openairdocs.org/incident/20090201001429A), Feb 1, 2009: Cessna 172S, Union Mills, IN, Substantial damage. (-23) Instructional flight originated at vpz with instructor andprimary student. Instructor was simulating an emergency landing at the 4C1 airport. Instructor… 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.