FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI04CA246 · Utterback Mustang II

4 Sept 2004 · Kendallville, IN, United States

Utterback Mustang II · Accident: dragged wing, rotor, pod, float or tail/skid during takeoff

From 07C · Auburn, IN to Kendallville Municipal Airport (C62)

Report a problem

Event

NTSB case
CHI04CA246
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

Utterback Mustang II

Aircraft type
Utterback MUSTANG
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
N91622
Operator
Unknown
Onboard fatalities
Unknown
Route
From 07C · Auburn, INTo Kendallville Municipal Airport (C62), Kendallville, 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
Takeoff · rejected takeoff
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
  • Pilot in command › Recovery from bounced landing, improper

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

NTSB narrative

The experimental amateur-built airplane impacted terrain during an aborted landing. The pilot stated that during landing the airplane touched down in a three point attitude. He thought the airplane was stalled when he pulled back on the stick, but the airplane flared. He added power to arrest the nose from coming down hard after which he decided to execute a go-around. He applied full power, and the airplane bounced a few times and lifted off the ground. The airplane then nosed up and began to veer towards the left in a right wing high attitude. The left wing contacted the ground, and the airplane came to rest off the left side of the runway.

Probable cause

The pilot's improper recovery from a bounced landing and his failure to maintain aircraft control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI04CA246
Event ID
20040910X01401
Case number
CHI04CA246
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: 8ef689bd7a035302d3cedaa3dc7a065bc9c3431d69fc4daa23cc90aaa68317c2; retrieved 2026-09-21T19:08:57.979Z.