GAA18CA007 · Cessna T210 M
Cessna T210 M · Accident: collision during takeoff/landing on approach
From Randolph County Airport (I22) to Oakland County International Airport (PTK)
Event
- NTSB case
- GAA18CA007
- 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
- Instrument Meteorological Cond
Cessna T210 M
- Aircraft type
- Cessna 210
- 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
- N5EC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Randolph County Airport (I22), Winchester, INTo Oakland County International Airport (PTK), Waterford, MI
- Aircraft age
- About 40 years (built 1977)
- 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 · IFR final approach
- 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
- Collision during takeoff/landing
- 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
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Physical environment
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot of the airplane reported that, while on an instrument flight rules approach to land in instrument meteorological conditions at night, he was "a little late descending" on the glideslope. He added that, during the approach, he increased the descent rate and became "a little right of course." He noticed approach lights but became "fixated" on the instruments while attempting to correct for being off course. Subsequently, the airplane struck the tops of trees, and he immediately pulled up. He landed without further incident.
The airplane sustained substantial damage to the right wing, empennage, and fuselage.
The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.
The automated weather observation system at the accident airport reported, about the time of the accident, that the wind was from 140° at 5 knots, visibility 3/4 statute mile, light rain, and clouds overcast at 200 ft. The pilot landed on runway 9 and flew the RNAV GPS runway 9 approach.
Probable cause
The pilot's unstabilized approach at night, which resulted in collision with trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA18CA007
- Event ID
- 20171010X24839
- Case number
- GAA18CA007
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2017-10-07.
- API snapshot SHA-256: 8dc494f6a7a297c03c7316ba655ea7549e1b67153591383751fd3ab5763e7f99; retrieved 2026-09-16T05:55:32.906Z.