CHI06FA032 · Aero Commander 500B
Aero Commander 500B · Accident: in flight collision with object on approach
From Gerald R. Ford International Airport (GRR) to Gaylord Regional Airport (GLR)
Event
- NTSB case
- CHI06FA032
- 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
- 1 · 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
- Charter & commuter
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Instrument Meteorological Cond
Aero Commander 500B
- Aircraft type
- Aero Commander 500
- 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
- N1153C
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Gerald R. Ford International Airport (GRR), Grand Rapids, MITo Gaylord Regional Airport (GLR), Gaylord, 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 135: Air Taxi & Commuter
- 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 · IFR final approach
- 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
- Tree(s)
- 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 › Altitude/clearance, 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 was operated as an on-demand cargo flight that impacted trees and terrain about one mile from the destination airport during a non-precision approach. Night instrument meteorological conditions prevailed at the time of the accident. The airplane was equipped with an "icing protection system" and a report by another airplane that flew the approach and landed without incident indicated that light rime icing was encountered during the approach. Radar data shows that the accident airplane flew the localizer course inbound and began a descent past the final approach fix. No mechanical anomalies that would have precluded normal operation were noted with the airplane.
Probable cause
The clearance not maintained with terrain during a nonprecision approach. Contributing factors were the ceiling, visibility, night conditions, and trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI06FA032
- Event ID
- 20051125X01890
- Case number
- CHI06FA032
- 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: 121aeb15d96ab55a754e1ce0ee1e5d115c41c7b0a8cb7b3aa1d95804dc782247; retrieved 2026-09-18T12:57:50.026Z.