# NTSB GAA18CA007: Cessna T210, N5EC, Waterford, MI, October 7, 2017 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: October 6, 2017, 23:55 local (Oct 7, 2017, 03:55 UTC) - Place: Waterford, MI - Coordinates: 42.664722, -83.423057 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=42.6647&lon=-83.4231&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach-IFR final approach: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report January 11, 2018 - Report: Approved by Office Director - NTSB office: General Aviation Accidents - Parties: FAA - NTSB case key (mKey): 96164 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA18CA007 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/96164/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=96164 - Page: https://openairdocs.org/ntsb/GAA18CA007 ## Probable cause The pilot's unstabilized approach at night, which resulted in collision with trees. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: descent/approach/glide path](https://openairdocs.org/ntsb-findings/01062040): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna T210M, 2 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=2073451), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cessna T210M, 11 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2073451), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Object/animal/substance: tree(s)](https://openairdocs.org/ntsb-findings/03022020): Environmental issues › Physical environment · Effect on operation (probable cause); cases with it: [Cessna T210M, 3 cases](https://openairdocs.org/ntsb-findings/03022020/cases.md?model=2073451), [All aircraft, 933 cases](https://openairdocs.org/ntsb-findings/03022020/cases.md) - [Light condition: dark](https://openairdocs.org/ntsb-findings/03036020): Environmental issues › Conditions/weather/phenomena · Effect on personnel; cases with it: [Cessna T210M, 3 cases](https://openairdocs.org/ntsb-findings/03036020/cases.md?model=2073451), [All aircraft, 448 cases](https://openairdocs.org/ntsb-findings/03036020/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach-IFR final approach: Course deviation](https://openairdocs.org/ntsb-events/281); cases with it: [Cessna T210M, 2 cases](https://openairdocs.org/ntsb-events/281/sequence.md?model=2073451), [All aircraft, 52 cases](https://openairdocs.org/ntsb-events/281/sequence.md) - [Approach-IFR final approach: Altitude deviation](https://openairdocs.org/ntsb-events/282); cases with it: [Cessna T210M, 2 cases](https://openairdocs.org/ntsb-events/282/sequence.md?model=2073451), [All aircraft, 104 cases](https://openairdocs.org/ntsb-events/282/sequence.md) - [Approach-IFR final approach: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) (defining event); cases with it: [Cessna T210M, 2 cases](https://openairdocs.org/ntsb-events/490/sequence.md?model=2073451), [All aircraft, 1,309 cases](https://openairdocs.org/ntsb-events/490/sequence.md) - [Approach-IFR final approach: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna T210M, 18 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2073451), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis 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. ## Factual 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 glide slope. He added that, during the approach, he increased the descent rate and also 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 ¾ statute mile, light rain, clouds overcast at 200 ft. The pilot landed on runway 9, flying the RNAV (GPS) runway 9 approach. ## Aircraft - Registration: [N5EC](https://openairdocs.org/deregistered/N5EC-2019-10-25), registration cancelled 2019-10-25, S/N 21062373, built 1977 (OpenAirDocs) - Reported make and model: CESSNA T210 (M) - Registry model: [Cessna T210M](https://openairdocs.org/model/cessna-t210m) (registry code 2073451) (OpenAirDocs) - Registry engine: [Continental TSIO-520 series](https://openairdocs.org/engine/continental-tsio-520-series) (registry code 17040, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 62373 - Year built: 1977 - Airframe hours: 4386.7 - Engines: CONT MOTOR TSIO-520-R11B 310 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, November 10, 2016 - Departed: I22, WINCHESTER, IN - Destination: PTK, Waterford, MI - Flight plan: IFR - Airport: PTK, Oakland County Intl, runway 09R, 6,521 × 150 ft, asphalt - Equipment: Stall warning system, Onboard weather, Auto-pilot ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 74; injuries: none; private; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 3, without waivers/limitations; last flight review April 28, 2017; seat: left; restraint: 3-point; flight hours: 3,611 as pilot in command ## Weather - Conditions: Instrument (IMC), Night/dark - Wind: 140° at 5 knots - Lowest ceiling: 200 ft overcast - Temperature: 61 °F, dew point 61 °F - Altimeter: 29.95 inHg - Observed at: KPTK ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20171007024699A](https://openairdocs.org/incident/20171007024699A), Oct 7, 2017: Cessna T210M, Waterford, MI, Substantial damage. Pilot accepted clearance for RNAV (LPV) 9R at kptk. Pilot was asked by approach controller to keep speed up (155KIAS) due to jet aircraft following on… ## Docket (2 files) The files NTSB released with the investigation on December 4, 2017, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=96164. 1.4 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 921 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40458519&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Accident Photo (Courtesy of FAA) (item 2, .PDF, 1 photo, 448 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40458520&FileExtension=.PDF&FileName=Accident%20Photo%20(Courtesy%20of%20FAA)-Master.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.