# NTSB CHI06FA141: Cessna 210N, N5212U, Ft. Thomas, KY, May 30, 2006 - Type: NTSB accident investigation - Classification: Accident · Fatal · Field investigation · Final report - Date: May 30, 2006, 18:09 local (22:09 UTC) - Place: Ft. Thomas, KY - Coordinates: 39.079746, -84.449935 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=39.0797&lon=-84.4499&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Highest injury: Fatal - Injuries: 1 fatal - Status: Completed, report October 31, 2007 - Report: Approved by Office Director - Parties: Sigma Tek, Federal Aviation Administration, Cessna Aircraft Company, Teledyne Continental Motors - NTSB case key (mKey): 63810 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CHI06FA141 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/63810/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=63810 - Page: https://openairdocs.org/ntsb/CHI06FA141 ## Probable cause The pilot failed to maintain altitude/clearance with trees while attempting to return to the airport. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - In flight collision with object, approach - physiological condition, pilot in command - altitude/clearance - not maintained, pilot in command (cause) - object - tree(s) - lack of certification, pilot in command - In flight collision with object, descent - uncontrolled - object - tree(s) (cause) - In flight collision with terrain/water, descent - uncontrolled - terrain condition - ground ## Analysis The airplane impacted trees and terrain during a return to the departure airport approximately two minutes after takeoff. The pilot reported to air traffic control that he wanted to return for unspecified reasons and did not declare an emergency or respond appropriately to ATC directions or inquiries. The airplane was not in a landing configuration and the debris path was consistent with an impact substantially higher than a landing speed. Examination of the wreckage did not reveal any mechanical anomalies that would have precluded operation. The pilot had a number of significant medical conditions. At the time of the accident, the pilot had not received a letter from the Federal Aviation Administration recertifying his airman medical certificate. ## Factual narrative "THIS CASE WAS MODIFIED ON APRIL 4, 2008" On May 30, 2006, at 1809 eastern daylight time, a Cessna 210N, N5212U, piloted by a private pilot, received substantial damage on impact with trees and terrain near Ft. Thomas, Kentucky, while returning to the departure airport. Visual meteorological conditions prevailed at the time of the accident. The Title 14 CFR Part 91 flight was not operating on a flight plan. The pilot was fatally injured. The flight originated from Cincinnati Municipal Airport-Lunken Field (LUK), Cincinnati, Ohio, and was en route to Greene County-Lewis A. Jackson Regional Airport (I19), Dayton, Ohio. At 1603:15, a caller representing N5212U called Dayton Automated Flight Service Station requesting a briefing for a visual flight rules flight from LUK to I19, "transporting a plane about 1730." The following is a transcription of transmissions from N5212U, Lunken Local Tower/Ground Control (LC/GC), and Cincinnati Approach Control (CVG APCH): 1754:45, LC/GC, are ya going to be remaining clear of the class b airspace of cincinnati or do you want flight following 1754:49, N5212U, negative i i'll be alright i'm familiar with the route 1755:53, N5212U, one two uniform i guess i missed golf here 1755:57, LC/GC, ok alright i tell you what uh five two one uniform just hold your position there do you see the sign that says hold here for two one left 1756:04, N5212U, affirmative 1756:05, LC/GC, hold there for two one left i'll get ya a two one left departure and call me on eighteen seven when you're ready 1756:12, N5212U, one two one uniform roger 1758:14, N5212U, lunken tower uh one two uniform ready for takeoff 1758:16, LC/GC, one two uniform uh lunken tower cross runway two five runway two one cleared for takeoff 1758:24, N5212U, cross runway two five two one cleared for takeoff left two one two one left 1759:40, LC/GC, five two one uniform right turn north northwest bound approved 1759:47, N5212U, ah right turn approved one two uniform roger 1800:13, LC/GC, five two one uniform squawk one two zero zero 1800:41, LC/GC, five two one uniform squawk one two zero zero please 1801:00, LC/GC, november five two one uniform north northwest bound approved remain clear of the arrival path for the two one left tra traffic inbound 1801:09, N5212U, ah one two uniform roger 1802:23, LC/GC, five two one uniform traffic eleven o'clock three miles south bound altitude indicates three thousand two hundred 1802:35, N5212U, one two uniform looking 1803:03, N5212U, one two uniform lunkin i want to circle and come back in 1803:14, LC/GC, cessna five two one uniform you want to make a right turn back towards the airport you say 1803:57, LC/GC, cessna five two one uniform lunken tower 1803:36, LC/GC, cessna five two one uniform lunken tower 1803:47, N5212U, lunken approach i want to return 1703:50, LC/GC, november five two one uniform roger turn right and head southbound toward the airport uh are you alright There were no further transmissions from N5212U and at 1704, there was no response when LC/GC asked the N5212U to squawk ident if he heard the transmission. LNK ATCT then cleared N5212U to land on either runway, 21R or 21L. but there was no response. At 1707, LC/GC observed one radar hit of a primary target approximately 1 mile southwest of the airport but did not see N5212U visually. A witness reported that he was driving an automobile when he saw the airplane. He stated that the landing gear was retracted and the propeller was turning, but he could not hear any engine sounds. The airplane was at a "very low" altitude. He observed the airplane banking left to go over the Ohio River. It did not appear to him that the airplane had enough altitude or speed to make it to LUK. The airplane was "sinking" in altitude when it was over the Ohio River. A second witness stated that she was watering flowers when she heard an airplane engine "revving" and it "sounded very close." She looked up and heard branches breaking and saw a small airplane hit the ground and break apart. A third witness stated that he saw the airplane flying at "tree top level" and the engine was "skipping and sputtering." He said that the airplane was in a "hard left bank turn" and that he could only see the underside of the airplane to illustrate the degree of turn that the airplane was in. Approximately 3 seconds after he lost sight of the airplane, he heard the airplane impact trees or the ground. AIRCRAFT INFORMATION The 1984 Cessna 210N, serial number 21064854, was powered by a Teledyne Continental Motors (TCM) IO-520-L19, serial number 577286, engine. The airplane and engine were last inspected during an annual inspection dated February 14, 2006, at a tachometer time of 2196.8. PERSONNEL INFORMATION The pilot held a private pilot certificate with airplane single-engine land, multiengine land limited to center thrust and VFR only, and instrument airplane ratings. He reported a total flight time of 3,900 hours at the time of issuance of his last medical certificate. The pilot received an Authorization for Special Issuance of Medical Certificate dated September 14, 2005. MEDICAL AND PATHOLOGICAL INFORMATION An autopsy of the pilot was conducted by Northern Kentucky Regional Medical Examiners Office, Fort Thomas, Kentucky, on May 31, 2006. The FAA Final Forensic Toxicological Fatal Accident Report states: No carbon monoxide detected in blood No cyanide detected in blood No ethanol detected in vitreous 0.033 (ug/ml, mg/g) diphendyrnamine detected in blood Diphenhydramine detected in liver A review of the FAA Aerospace Medical Certification Division blue ribbon medical records and the autopsy revealed that the pilot had a number of significant medical conditions, including congestive heart failure, chronic atrial fibrillation, morbid obesity, high blood pressure, diabetes, high cholesterol, diverticulitis, hypothyroidism, and severe obstructive sleep apnea. He had an installed pacemaker that kept his heart rate at a minimum of 50 beats per minute, and was on a blood thinner to reduce his risk of stroke. He had stopped using the blood thinner without notifying his physician approximately nine months prior to the accident, and had apparently restarted his medication only after having his Special Issuance medical certificate withdrawn by the FAA approximately two months prior to the accident. He had provided evidence of use of the blood thinner to the FAA, and an internal FAA memo dated five days prior to the accident indicates that he was to be recertified. The letter conveying that decision was dated one week following the accident. WRECKAGE AND IMPACT INFORMATION The main wreckage of the airplane, which consisted of the fuselage, wings and empennage was resting upright in a grass area located approximately 1 1/2 nautical miles from the approach end of runway 25. The wreckage path was approximately 95 feet in length and oriented on a southerly heading along a grass area behind a house. The northern area of the wreckage path contained a tree about 30 feet in height with broken tree limbs that were about 1-foot diameter. Approximately 75 feet south from the broken tree was the main wreckage and approximately 20 feet south of the main wreckage was the engine. The right trailing edge flap and the landing gear were in the retracted positions. The engine was attached to a three-bladed propeller assembly. One blade of the propeller assembly was separated at its hub and displayed twisting about the longitudinal axis. The engine was shipped to Teledyne Continental Motors for further examination. A blue colored liquid consistent with 100 low lead aviation fuel was drained from the gascolator bowl. The bowl was removed and the screen was inspected and did not contain debris. The flight control cables were inspected from their flight cont ## Aircraft - Registration: [N5212U](https://openairdocs.org/deregistered/N5212U-2013-04-02), registration cancelled 2013-04-02, S/N 21064854, built 1984 (OpenAirDocs) - Reported make and model: Cessna 210N - Registry model: [Cessna 210N](https://openairdocs.org/model/cessna-210n) (registry code 2073453) (OpenAirDocs) - Registry engine: [Continental IO-520 series](https://openairdocs.org/engine/continental-io-520-series) (registry code 17032, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 21064854 - Engines: Teledyne Continental IO-520-L19 285 horsepower reciprocating - Damage: Substantial damage - Flight: Part 91 - Operator: Pilot - Registered owner: Wheels Auto Leasing - Airworthiness certificate: Standard, Normal - Last inspection: Annual, May 1, 2006 - Departed: LUK, Cincinnati, OH - Destination: I19, Dayton, OH - Airport: LUK, Cincinnati Muni Airport Lunken ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 79; injuries: fatal; private; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 3; seat: left; toxicology performed; flight hours: 3,900 total ## Weather - Conditions: Visual (VMC), Day - Wind: 170° at 3 knots - Visibility: 8 statute miles - Lowest ceiling: none - Temperature: 84 °F, dew point 70 °F - Altimeter: 30.04 inHg - Observed at: LUK, 2 nm away ## 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 20060530013589A](https://openairdocs.org/incident/20060530013589A), May 30, 2006: Cessna 210N, Cincinnati, OH, Destroyed, 1 fatal. (-23) On may 30, 2006, at approximately 1810 eastern time, a Cessna 210, N5212U, operated by a private pilot, was destroyed when it impacted the terrain 3… ## Docket (18 files) The files NTSB released with the investigation on September 28, 2007, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=63810. 55.4 MB in all. - Witness Statements & Record of Interviews (item 1, .PDF, 119 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40282547&FileExtension=.PDF&FileName=Witness%20Statements%20%26%20Record%20of%20Interviews-Master.PDF - Weather Information (item 2, .PDF, 48 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40282548&FileExtension=.PDF&FileName=Weather%20Information-Master.PDF - Partial ATC Package (item 3, .PDF, 195 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40282549&FileExtension=.PDF&FileName=Partial%20ATC%20Package-Master.PDF - AFSS Transcript (item 4, .PDF, 96 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40377240&FileExtension=.PDF&FileName=AFSS%20Transcript-Redacted.PDF - Medical Records Information (item 5, .PDF, 18 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40278973&FileExtension=.PDF&FileName=Medical%20Records%20Information-Master.PDF - Aircraft Logs (item 6, .PDF, 1.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40282551&FileExtension=.PDF&FileName=Aircraft%20Logs-Master.PDF - Toxicological Report (item 7, .PDF, 53 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40377241&FileExtension=.PDF&FileName=Toxicological%20Report-Redacted.PDF - Statement of Party Representatives to NTSB Investigation (item 8, .PDF, 295 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40282553&FileExtension=.PDF&FileName=Statement%20of%20Party%20Representatives%20to%20NTSB%20Investigation-Master.PDF - Release of Aircraft Wreckage, NTSB Form 6120.15 (item 9, .PDF, 73 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40282554&FileExtension=.PDF&FileName=Release%20of%20Aircraft%20Wreckage,%20NTSB%20Form%206120.15-Master.PDF - Photo 1. Broken Tree Limbs at Northern Wreckage Path (item 10, .PDF, 5.8 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40282557&FileExtension=.PDF&FileName=Photo%201.%20%20Broken%20Tree%20Limbs%20at%20Northern%20Wreckage%20Path-Master.PDF - Photo 2. Main Wreckage (item 11, .PDF, 6.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40282560&FileExtension=.PDF&FileName=Photo%202.%20%20Main%20Wreckage-Master.PDF - Photo 3. Main Wreckage (item 12, .PDF, 5.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40282561&FileExtension=.PDF&FileName=Photo%203.%20%20Main%20Wreckage-Master.PDF - Photo 4. Main Wreckage (item 13, .PDF, 5.7 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40282562&FileExtension=.PDF&FileName=Photo%204.%20%20Main%20Wreckage-Master.PDF - Photo 5. Main Wreckage (item 14, .PDF, 5.6 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40282563&FileExtension=.PDF&FileName=Photo%205.%20%20Main%20Wreckage-Master.PDF - Photo 6. Cockpit (item 15, .PDF, 6.9 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40282564&FileExtension=.PDF&FileName=Photo%206.%20%20Cockpit-Master.PDF - Photo 7. Engine (item 16, .PDF, 5.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40282565&FileExtension=.PDF&FileName=Photo%207.%20%20Engine-Master.PDF - Photo 8. Engine (item 17, .PDF, 6.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40282566&FileExtension=.PDF&FileName=Photo%208.%20%20Engine-Master.PDF - Photo 9. Main Wreckage (item 18, .PDF, 5.8 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40282567&FileExtension=.PDF&FileName=Photo%209.%20%20Main%20Wreckage-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.