FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN09CA148 · Cessna 172 S

1 Feb 2009 · Union Mills, IN, United States

J.S. Aviation DBA Cessna 172 S · Accident: collision with terrain/object (non-CFIT) on approach

From Porter County Municipal Airport (VPZ) to Porter County Municipal Airport (VPZ)

Report a problem

Event

NTSB case
CEN09CA148
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Cessna 172 S

Aircraft type
Cessna 172
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N53576
Onboard fatalities
Unknown
Route
From Porter County Municipal Airport (VPZ), Valparaso, INTo Porter County Municipal Airport (VPZ), Valparaso, IN
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Approach · VFR go-around
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Collision with terrain/object (non-CFIT)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

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.

Probable cause

The certificated flight instructor's failure to follow correct engine clearing procedures. A factor was the unsuitable landing area.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN09CA148
Event ID
20090202X02717
Case number
CEN09CA148
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 000f623b31db304b9ac2c67eb12adfe616f0a892e396f19d6d960465e14f7ca8; retrieved 2026-09-15T10:43:30.525Z.