# NTSB CEN22FA406: Cessna 182, N58807, Cleveland, TN, September 5, 2022 - Type: NTSB accident investigation - Classification: Accident · Fatal · Class 3 · Field · Final report - Date: September 5, 2022, 17:11 local (21:11 UTC) - Place: Cleveland, TN · wooded area - Coordinates: 35.12614, -84.72678 - Nearby events: https://openairdocs.org/map.md?lat=35.1261&lon=-84.7268&mi=10 - Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping) - Defining event: [Enroute: Loss of control in flight](https://openairdocs.org/ntsb-events/240) - Highest injury: Fatal - Injuries: 2 fatal - Status: Completed - Report: Approved by Office Director - Investigation class: Class 3 - NTSB office: Central Region - Parties: Textron Aviation, FAA Flight Standards - NTSB case key (mKey): 105858 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN22FA406 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/105858/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=105858 - Page: https://openairdocs.org/ntsb/CEN22FA406 ## Probable cause The pilot’s loss of airplane control while operating in instrument meteorological conditions. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cessna 182P, 48 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2075816), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Enroute: Loss of control in flight](https://openairdocs.org/ntsb-events/240) (defining event); cases with it: [Cessna 182P, 17 cases](https://openairdocs.org/ntsb-events/240/sequence.md?model=2075816), [All aircraft, 5,002 cases](https://openairdocs.org/ntsb-events/240/sequence.md) - [Uncontrolled descent: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna 182P, 47 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2075816), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) - [Enroute-cruise: Other weather encounter](https://openairdocs.org/ntsb-events/400); cases with it: [Cessna 182P, 9 cases](https://openairdocs.org/ntsb-events/400/sequence.md?model=2075816), [All aircraft, 1,127 cases](https://openairdocs.org/ntsb-events/400/sequence.md) ## Analysis The initial portion of the instrument flight rules cross-country flight was routine. The flight was established in cruise flight about 9,000 feet mean sea level (msl). The air traffic controller advised the pilot of an area of weather about 10 miles ahead and suggested deviating left of course. The pilot initially appeared to establish the course suggested by the controller, but shortly afterward advised the controller that he planned to proceed direct to the intended destination. The controller subsequently informed the pilot that he was entering an area of moderate to heavy precipitation that extended for about 20 miles. The controller approved deviating left or right of course. About three minutes later, the controller advised the pilot of heavy precipitation from the airplane’s current position eastbound and suggested a northbound course before proceeding eastbound to remain clear of the weather. About five minutes before the accident, the airplane entered a left turn as the flight approached the weather. The pilot completed two full 360° turns during which the airplane altitude varied from approximately 8,700 ft msl to 9,300 ft msl. About one minute before the accident, the pilot transmitted, “I’ve got control finally we were in a bit of a whirlwind.” The controller acknowledged, noted heavy precipitation to the north of the airplane’s position, and suggested a west heading. The pilot asked the controller to confirm the suggested heading, and the controller responded, “back to the west about a two seventy.” The pilot’s reply was not discernable, and no further communications were received. About 30 seconds before the accident, the airplane entered a right turn from an approximate altitude of 9,075 ft msl. The airplane’s altitude increased to about 9,375 ft msl briefly before it entered a descent. The final data point was located about one-half mile from the accident site with a corresponding airplane altitude of 7,200 ft msl. The airplane impacted trees and terrain. The airframe was fragmented consistent with a high-speed impact. The propeller blades were fractured and deformed consistent with engine power at impact. A postaccident examination did not identify any anomalies attributable to a preimpact failure or malfunction. Weather data revealed an area of convective activity near the final segment of the flight. The airplane was in instrument meteorological conditions at the time of the loss of control. Toxicology testing detected ethanol in one of the pilot’s muscle tissue samples but was not detected in another muscle tissue sample. Given that there was no ethanol detected in one of two muscle tissue samples, the identified ethanol was likely from sources other than ingestion. The antihistamines diphenhydramine and cetirizine and the muscle relaxant cyclobenzaprine were detected in the pilot’s muscle tissue; no blood specimens were available for toxicology testing. Without blood levels, the investigation was unable to determine whetherthe effects from the pilot’s use of diphenhydramine, cetirizine, and cyclobenzaprine contributed to the accident. ## Factual narrative A representative of the flying club that owned the accident airplane reported that a Stormscope was installed but it was not operational. However, the transponder was able to receive NEXRAD weather radar data and provide that to a Bluetooth-connected device such as a tablet. Weather radar data could not be depicted on the two installed electronic flight displays. The investigation was unable to determine if the pilot was referencing weather data during the accident flight. On September 5, 2022, at 1711 eastern daylight time, a Cessna 182P airplane, N58807, was destroyed when it was involved in an accident near Cleveland, Tennessee. The pilot and passenger were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. Automatic dependent surveillance – broadcast (ADS-B) data revealed that the flight departed Arlington Municipal Airport (GKY), Arlington, Texas, about 1112 and arrived at Fletcher Field Airport (CKM), Clarksdale, Mississippi, about 1400. The accident flight departed CKM about 1448 on an instrument flight rules (IFR) flight plan. The intended destination was Asheville Regional Airport (AVL), Asheville, North Carolina. The pilot proceeded eastbound on course toward AVL and climbed to 9,000 ft msl. At 1655, the air traffic controller advised the pilot of an area of weather about 10 miles ahead and suggested deviating left of course toward either Dayton or Athens, Tennessee, before proceeding on course. The pilot initially appeared to establish a course for Athens. However, the pilot then advised the controller that he planned to proceed to Collegedale and then direct to AVL. At 1706:23, the controller informed the pilot that he was entering an area of moderate to heavy precipitation and that it extended for about 20 miles. The controller approved deviating left or right of course. About three minutes later, the controller advised the pilot of heavy precipitation from the current position eastbound and suggested a northbound course before proceeding toward Athens and then AVL. At 1706:55, the airplane entered a left turn as the flight approached the area of weather. The pilot completed two full 360° turns, momentarily returning to a northeasterly course. During the two turns, the airplane altitude varied from approximately 8,700 ft msl to 9,300 ft msl. At 1710:37, the pilot transmitted, “I’ve got control finally we were in a bit of a whirlwind.” The controller acknowledged, noted heavy precipitation to the north of the airplane’s position, and suggested a west heading. The pilot asked the controller to confirm the suggested heading, and the controller responded, “back to the west about a two seventy.” The pilot’s reply was transmitted at 1711:24 and was not discernable. No further communications were received. At 1711:10, the airplane entered a right turn from an approximate altitude of 9,075 ft msl. The airplane altitude increased to about 9,375 ft msl briefly before the airplaneentered a descent. The final data point was recorded at 1711:32 with a corresponding altitude of 7,200 ft msl. Immediately before the accident, a witness heard the airplane fly over his house, which was adjacent to the accident site. The engine seemed to be at a “normal” cruise power setting. However, 1 to 1-1/2 seconds later, the engine sound increased abruptly to what seemed to be “full throttle.” The engine seemed to increase power smoothly with no hesitation. Moments afterward, he heard a “boom” that shook the house. There were no further sounds from the airplane and he assumed that it had crashed. Toxicology testing performed by the FAA Forensic Sciences Laboratory detected ethanol in the pilot’s muscle tissue at 0.022 grams per hectogram (gm/hg) in one sample but was not detected in another muscle tissue sample. The antihistamines diphenhydramine and cetirizine (10 nanograms per gram [ng/gm]) were detected in the pilot’s muscle tissue. The muscle relaxant cyclobenzaprine and its metabolite norcyclobenzaprine were detected in his muscle tissue at 5 ng/gm and 20 ng/gm, respectively. No blood specimens were available for toxicology testing. These medications can cause sedation and can slow psychomotor responses and reaction times. Ground-based radar imagery depicted an area of convective activity near the final portion of the flight path. Meteorological data depicted saturated conditions between 9,000 and 10,000 feet, cloud tops to over 40,000 feet, regional cloud bases below 3,000 feet, and precipitation surrounding the final portion of the flight path. The witness who reported hearing the airplane at the time of the accident noted that it was raining with low clouds and fog at the time. He was about 200 yards from the accident site and noted that he was unable to see the tops of the trees in his yard. The pilot filed the flight plan through a third-party application about 1428. This was about 20 minutes before the flight departed CKM. A weather briefing was generated at the time the flight plan was filed. The pilot had not viewed any weather imagery provided by the application before the flight. However, the investigation was unable to determine if the pilot had viewed weather data or imagery from other sources. According to the pilot’s logbook, he had logged 33.6 hours of actual instrument flight time and 54.0 hours of simulated instrument flight time. Within the previous 6 months, the pilot logged actual and simulated instrument times of 1.5 hours and 4.5 hours, respectively. The logbook included a notation, “Completed flight review and the IPC,” which was dated July 4, 2022. The entry included a total flight time of 1.6 hours with no actual or simulated instrument time logged. Previous simulated instrument time was logged on June 18, 2022, and June 25, 2022. The initial tree impact was located about 0.56 miles northwest of the final data point. Elevation of the accident site was approximately 830 ft and estimated tree heights were 80 ftabove ground level (agl). The debris path was about 480 ft long and oriented on a north-northeast (020°) bearing. The airframe was fragmented. The engine and propeller assemblies were separated and located within the debris path. Both exhibited damage consistent with impact forces. A postaccident examination identified portions of the entire airframe structure. No evidence of an in-flight structural failure was observed. The flight control system exhibited multiple separations consistent with the fragmentation of the airframe; however, no anomalies attributable to a preimpact failure or malfunction were observed. ## Aircraft - Registration: [N58807](https://openairdocs.org/deregistered/N58807-2023-10-18), registration cancelled 2023-10-18, S/N 18262310, built 1973 (OpenAirDocs) - Reported make and model: CESSNA 182 (P) - Registry model: [Cessna 182P](https://openairdocs.org/model/cessna-182p) (registry code 2075816) (OpenAirDocs) - Registry engine: [Continental O-470 series](https://openairdocs.org/engine/continental-o-470-series) (registry code 17026, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 18262310 - Year built: 1973 - Airframe hours: 4014 - Engines: Continental O-470-R 230 horsepower reciprocating - Damage: Destroyed - Flight: Personal, Part 91 - Operator: Mountain Flyers Inc., doing business as N/A - Registered owner: Mountain Flyers Inc. - Airworthiness certificate: Standard, Normal - Last inspection: Annual, February 2, 2022 - Departed: CKM, Clarksdale, MS - Destination: AVL, Asheville, NC - Flight plan: IFR - Equipment: Stall warning system, ADS-B, Electronic primary flight display ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 68; injuries: fatal; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, with waivers/limitations; last flight review July 4, 2022; seat: left; restraint: 3-point; toxicology performed; flight hours: 421 total, 25 in this make and model, 19 in the last 90 days, 11 in the last 30 days, 3 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 0° at 0 knots - Visibility: 9 statute miles - Lowest ceiling: 2,800 ft broken - Temperature: 77 °F, dew point 73 °F - Altimeter: 30.01 inHg - Observed at: MMI, 16 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 20220905015219A](https://openairdocs.org/incident/20220905015219A), Sep 5, 2022: Cessna 182P, Cleveland, TN, Destroyed, 2 fatal. Pilot was on an IFR flight plan. ATC notified pilot he was heading into a storm. Pilot responded that they were in a whirl wind. ATC tried contacting pilot… ## Docket (20 files) The files NTSB released with the investigation on May 9, 2024, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=105858. 2.5 GB in all. - Flight summary (item 1, PDF, 8 pages, 3.7 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=16997811&FileExtension=pdf&FileName=CEN22FA406%20-%20Flight%20Summary-Rel.pdf - Air traffic control transcript (item 2, PDF, 4 pages, 124 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=16961540&FileExtension=pdf&FileName=03_Air%20Traffic%20Control%20Transcript-Rel.pdf - Witness statement (item 3, PDF, 1 page, 131 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=14867854&FileExtension=pdf&FileName=ROC%20--%20Don%20Loftis%20--%2015Sep2022-Rel.pdf - Wreckage diagram (item 4, PDF, 2 pages, 310 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=16996146&FileExtension=pdf&FileName=Wreckage%20Diagram%20--%20CEN22FA406-Rel.pdf - Accident photos (item 5, PDF, 15 pages, 5.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=16968754&FileExtension=pdf&FileName=Accident%20Photos%20--%20CEN22FA406-Rel.pdf - Flight plan / briefing data (item 6, PDF, 2 pages, 168 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=16974324&FileExtension=pdf&FileName=Foreflight%20Data%20~%20N58807_redacted-Rel.pdf - ADS-B data file (item 7, CSV, 15.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=16961310&FileExtension=csv&FileName=07_ADSB%20Data%20File-Rel.csv - Meteorology specialist's factual report (item 8, PDF, 13 pages, 3.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=14861745&FileExtension=pdf&FileName=WX_CEN22FA406_Specialists_Factual-Rel.pdf - Airplane examination summary (item 9, PDF, 3 pages, 154 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=16961462&FileExtension=pdf&FileName=05_Airplane%20Examination%20Summary-Rel.pdf - Conversation summary -- flying club maintenance manager (item 10, PDF, 1 page, 129 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=16961482&FileExtension=pdf&FileName=09_Conversation%20Summary%20--%20Flying%20Club%20Maintenance%20Manager-Rel.pdf - Maintenance records -- airframe (item 11, PDF, 41 pages, 1.5 GB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=16972511&FileExtension=pdf&FileName=10_Maintenance%20Records%20--%20Airframe_redacted-Rel.pdf - Maintenance records -- engine (item 12, PDF, 12 pages, 407 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=16962512&FileExtension=pdf&FileName=11_Maintenance%20Records%20--%20Engine_redacted-Rel.pdf - Maintenance records -- propeller (item 13, PDF, 3 pages, 73.7 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=16964687&FileExtension=pdf&FileName=12_Maintenance%20Records%20--%20Propeller_redacted-Rel.pdf - Maintenance records -- AD compliance (item 14, PDF, 13 pages, 96.9 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=16975603&FileExtension=pdf&FileName=13_Maintenance%20Records%20--%20AD%20Complicance_redacted-Rel.pdf - Pilot logbook (item 15, PDF, 25 pages, 400 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=16975869&FileExtension=pdf&FileName=16_Pilot%20Logbook_redacted-Rel.pdf - Past flight history (item 16, PDF, 1 page, 106 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=16961637&FileExtension=pdf&FileName=08_Past%20Flight%20History%20--%20N58807-Rel.pdf - Toxicological report (item 17, PDF, 1 page, 197 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=16964156&FileExtension=pdf&FileName=18_Toxicology%20Report%20--%20Pilot_redacted-Rel.pdf - Medical factual (item 18, PDF, 4 pages, 145 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=15417875&FileExtension=pdf&FileName=CEN22FA406_Cleveland_TN_Medical_Factual_FINAL_050123-Rel.pdf - Release of aircraft wreckage, NTSB form 6120.15 (item 19, PDF, 1 page, 165 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=16964728&FileExtension=pdf&FileName=22_Release%20of%20Wreckage%20--%20CEN22FA406_redacted-Rel.pdf - Statement of party representatives to NTSB investigation (item 20, PDF, 1 page, 169 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=16965252&FileExtension=pdf&FileName=23_Statement%20of%20Party%20Representatives%20to%20NTSB%20Investigation_redacted-Rel.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.