FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI08CA225 · Aero Commander 200D

31 Jul 2008 · Tecumseh, MI, United States

Aero Commander 200D · Accident: loss of control in flight during landing

From Newman's Airport (4N0) to Al Meyers Airport (3TE)

Report a problem

Event

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

Aero Commander 200D

Aircraft type
Aero Commander 200
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
N260M
Operator
Unknown
Onboard fatalities
Unknown
Route
From Newman's Airport (4N0), Kalamazoo, MITo Al Meyers Airport (3TE), Tecumseh, 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
Landing · flare/touchdown
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
Loss of control in flight
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision

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

NTSB narrative

The pilot reported that the landing approach was uneventful up to the flare and touchdown. He increased engine power just prior to landing because he thought the airplane was slow. He flared higher than normal, and then the airplane "hit hard" on all three landing gear. The airplane began to porpoise, contacting the runway alternately with the nose and main landing gear, but eventually settled onto all three landing gear. The airplane then made an uncommanded left swerve that the pilot was unable to counteract. The nose landing gear separated from the airplane when the airplane nose impacted a non-breakaway steel runway light. The airplane then nosed over in the grass easement off the left side of the runway. The cabin roof, engine firewall, rudder, and vertical stabilizer were substantially damaged.

Probable cause

The pilot flaring too high, and his inadvertent pilot-induced oscillation during the landing flare/touchdown. Contributing to the accident was the collapse of the nose landing gear.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI08CA225
Event ID
20080902X01357
Case number
CHI08CA225
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, 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: f5c3344ca4672606751c294d16e5cabbfff33b0a90a195a913ec8e7dce12f9d4; retrieved 2026-09-15T10:08:06.171Z.