FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI04LA076 · Cessna 177

14 Feb 2004 · Sturgis, MI, United States

Cessna 177 · Accident: dragged wing, rotor, pod, float or tail/skid on approach

From Kirsch Municipal Airport (IRS) to Kirsch Municipal Airport (IRS)

Report a problem

Event

NTSB case
CHI04LA076
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 177

Aircraft type
Cessna 177
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
N3468T
Operator
Unknown
Onboard fatalities
Unknown
Route
From Kirsch Municipal Airport (IRS), Sturgis, MITo Kirsch Municipal Airport (IRS), Sturgis, MI
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
First occurrenceThe 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
Dragged wing, rotor, pod, float or tail/skid
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

  • Pilot in command › Aircraft control, not maintained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane sustained substantial damage on impact with a runway during an attempted go-around. The pilot reported that on his third practice landing, at approximately 5-10 feet above ground level, he was aligned just left of the center of the runway with the right wing tip slightly down, when he unexpectedly experienced a small gust of wind. The pilot stated that he attempted a go-around by applying full power and retrimming the airplane. The airplane momentarily began to gain altitude but the pilot mistakenly retracted all the flaps. The airplane settled back to the ground and the right wing tip impacted the runway. The pilot stated that he over corrected causing the left wing tip to impact the runway. The airplane exited the runway coming to a full-stop in snow to the east side of the runway.

Probable cause

The pilot's inadvertent raising of flaps resulting in a loss of lift and his failure to maintain aircraft control resulting in a dragging of the wing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI04LA076
Event ID
20040225X00240
Case number
CHI04LA076
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, coordinates. 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: 345e68e82e969c762e0d2ff8f625d265e8762c833e751d7826acab235c1c7543; retrieved 2026-09-22T07:57:40.434Z.