CHI90LA001 · Cessna 177
Kodiak Flying Club Cessna 177 · Accident: in flight collision with object during landing
From GYG · GREYLING, MI to an unrecorded destination
Event
- NTSB case
- CHI90LA001
- 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
- 0
- 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
- N102AT
- Operator
- Kodiak Flying Club
- Onboard fatalities
- Unknown
- Route
- From GYG · GREYLING, MITo not recorded
- 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
- Landing · aborted
- 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
- In flight collision with object
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall/mush; Wire, transmission
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Airspeed, inadequate
- Pilot in command › Go-around, delayed
- Pilot in command › Raising of flaps, improper
- Pilot in command › Stall/mush, inadvertent
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
AFTER LANDING LONG, THE PLT ELECTED TO GO-AROUND. HE RETRACTED THE FLAPS TO FULL UP & THE ACFT STOPPED CLIMBING & STARTED SETTLING WITH THE STALL WARNING HORN SOUNDING. THE PLT OBSERVED WIRES IN HIS FLT PATH & ROTATED THE PLANE TO AN ATTITUDE WHICH WOULD ALLOW THE WIRE TO STRIKE THE ACFT'S BELLY, RATHER THAN ACROSS THE WINDSHIELD. AFTER THE WIRE STRIKE, THE ACFT DESCENDED OUT OF CONTROL & COLLIDED WITH THE TERRAIN. ACCORDING TO THE GO-AROUND PROCEDURE IN THE FLT MANUAL, THE FLAPS SHOULD HAVE BEEN RETRACTED TO ONLY 20 DEG UNTIL THE ACFT HAD ACCELERATED TO 75 MPH, THEN FURTHER FLAP RETRACTION SHOULD HAVE BEEN PERFORMED SLOWLY.
Probable cause
A DELAYED BY THE PILOT IN GOING AROUND AND HIS FAILURE TO OBTAIN ADEQUATE AIRSPEED BEFORE FULLY RETRACTING THE FLAPS, WHICH ALLOWED THE AIRCRAFT TO MUSH. THE CONTRIBUTING FACTORS WERE: THE PILOT'S FAILURE TO ATTAIN THE PROPER TOUCHDOWN POINT DURING THE LANDING AND THE TRANSMISSION WIRE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI90LA001
- Event ID
- 20001213X29556
- Case number
- CHI90LA001
- 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. 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: 607062675b41a496030be3e8989a4f79fcec09b71eaea9583ac2eec7cc0724a1; retrieved 2026-09-22T00:01:24.003Z.