# NTSB ERA23FA219: Cessna 182, N725AS, Reliance, TN, May 7, 2023 - Type: NTSB accident investigation - Classification: Accident · Fatal · Class 3 · Field · Final report - Date: May 7, 2023, 18:49 local (22:49 UTC) - Place: Reliance, TN - Coordinates: 35.225799, -84.421951 - Nearby events: https://openairdocs.org/map.md?lat=35.2258&lon=-84.4220&mi=10 - Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping) - Defining event: [Enroute-cruise: Windshear or thunderstorm](https://openairdocs.org/ntsb-events/390) - Highest injury: Fatal - Injuries: 1 fatal - Status: Completed - Report: Approved by Office Director - Investigation class: Class 3 - NTSB office: Eastern Region Aviation - Parties: BRS Aerospace, FAA FSDO, Textron Aviation - NTSB case key (mKey): 114699 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA23FA219 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/114699/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=114699 - Page: https://openairdocs.org/ntsb/ERA23FA219 ## Probable cause The pilot’s decision to continue an instrument flight into an area of forecast weather with severe to extreme turbulence associated with a line of thunderstorms, which resulted in an in-flight breakup. Contributing was the pilot’s operation of the airplane in excess of its published maneuvering speed. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: airspeed](https://openairdocs.org/ntsb-findings/01062010): Aircraft › Aircraft oper/perf/capability · Capability exceeded (probable cause); cases with it: [Cessna 182Q, 3 cases](https://openairdocs.org/ntsb-findings/01062010/cases.md?model=2072732), [All aircraft, 1,681 cases](https://openairdocs.org/ntsb-findings/01062010/cases.md) - [Use of equip/info: use of equip/system](https://openairdocs.org/ntsb-findings/02063015): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cessna 182Q, 6 cases](https://openairdocs.org/ntsb-findings/02063015/cases.md?model=2072732), [All aircraft, 1,391 cases](https://openairdocs.org/ntsb-findings/02063015/cases.md) - [Info processing/decision: decision making/judgment](https://openairdocs.org/ntsb-findings/02041520): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Cessna 182Q, 15 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md?model=2072732), [All aircraft, 3,098 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md) - [Convective weather: thunderstorm](https://openairdocs.org/ntsb-findings/03033010): Environmental issues › Conditions/weather/phenomena · Decision related to condition (probable cause); cases with it: [Cessna 182Q, 2 cases](https://openairdocs.org/ntsb-findings/03033010/cases.md?model=2072732), [All aircraft, 100 cases](https://openairdocs.org/ntsb-findings/03033010/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Enroute-cruise: Windshear or thunderstorm](https://openairdocs.org/ntsb-events/390) (defining event); cases with it: [Cessna 182Q, 3 cases](https://openairdocs.org/ntsb-events/390/sequence.md?model=2072732), [All aircraft, 224 cases](https://openairdocs.org/ntsb-events/390/sequence.md) - [Enroute-cruise: Course deviation](https://openairdocs.org/ntsb-events/281); cases with it: [Cessna 182Q, 1 case](https://openairdocs.org/ntsb-events/281/sequence.md?model=2072732), [All aircraft, 52 cases](https://openairdocs.org/ntsb-events/281/sequence.md) - [Enroute-cruise: Altitude deviation](https://openairdocs.org/ntsb-events/282); cases with it: [Cessna 182Q, 2 cases](https://openairdocs.org/ntsb-events/282/sequence.md?model=2072732), [All aircraft, 104 cases](https://openairdocs.org/ntsb-events/282/sequence.md) - [Other: Aircraft structural failure](https://openairdocs.org/ntsb-events/337); cases with it: [Cessna 182Q, 1 case](https://openairdocs.org/ntsb-events/337/sequence.md?model=2072732), [All aircraft, 290 cases](https://openairdocs.org/ntsb-events/337/sequence.md) - [Enroute-descent: Part(s) separation from AC](https://openairdocs.org/ntsb-events/338); cases with it: [Cessna 182Q, 2 cases](https://openairdocs.org/ntsb-events/338/sequence.md?model=2072732), [All aircraft, 563 cases](https://openairdocs.org/ntsb-events/338/sequence.md) - [Uncontrolled descent: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna 182Q, 28 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2072732), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The instrument-rated private pilot departed on an instrument flight rules (IFR) flight and climbed to 9,000 ft mean sea level (msl) on a southeast heading. Radar data indicated that for about the first 2 hours and 30 minutes, the airplane maintained a relatively straight course. Twice the pilot requested air traffic control (ATC) provide radar vectors around weather, confirming with one controller that the airplane was equipped with on-board weather observation capability. During cruise flight, while flying at an airspeed above the airplane’s published maneuvering speed in an area with a valid Convective SIGMET, the airplane encountered the leading edge of precipitation and building cumuliform clouds in convective updrafts. This weather system was associated with a line of forecast thunderstorms and other pilots had reported the presence of severe to extreme turbulence while flying in the vicinity of it. The accident airplane’s heading and altitude changed several times during the final portion of the flight, and these deviations were not instructed by the controller or announced by the pilot. Following a second right turn the controller commented to the pilot, “it looks like you are in a little bit of a descent in a turn is everything alright?” The pilot did not reply to that communication and radar contact with the airplane was lost. A radar performance study indicated that when the airplane was last observed by radar, while flying at an altitude of about 8,850 ft msl, it was operating at a calibrated airspeed of 134 knots, which was 35 knots greater than the published maneuvering speed. Although the radar data did not capture the final descent, the airplane likely began descending after encountering severe to extreme turbulence. During that descent, the airplane’s airspeed which was already well above the published maneuvering speed likely increased and an in-flight break-up occurred, separating both wings and a majority of the right horizontal stabilizer and right elevator from the fuselage. The postaccident examination of the airframe revealed that all fracture surfaces displayed features consistent with overload failure with no evidence of preexisting cracking. The examination of the engine revealed no evidence of any preimpact failures or malfunctions. The airplane was equipped with a Ballistic Recovery Systems (BRS), and that system’s parachute and riser (lanyard) were not recovered following the accident. Examination of the BRS airframe system components revealed that the fire pin actuator was inside the rocket cone with the activation cable still attached, which was consistent with normal activation. Evidence indicated that the forward straps that connected to each front main spar, and the rear straps that were connected to the left and right attach plates on the rear bulkhead, remained connected to their respective bolts at the 3-point shackle. The 3-point shackle, which had separate attach points (bolts) for the forward and aftstraps, and for the riser (lanyard) of the parachute, was located within the main wreckage. However, the riser for the airframe parachute was not attached to the 3-point shackle. The 3-point shackle bolt for the parachute riser was not visibly deformed. The other two bolts of the 3-point shackle that secured the forward and aft straps also did not exhibit any visible damage. Examination of a portion of the rear harness revealed that the shock absorption stitching pattern was not peeled/torn, indicating that there was no force applied to the rear harness at the 3-point shackle level. Based on this information, it is likely that the pilot activated the airframe parachute at some point during the accident sequence, the parachute bag properly deployed from its canister, and the forward harness straps opened from their stowed position; however, with the parachute riser not attached to the 3-point shackle, the BRS parachute would have been useless. Because the parachute and riser were not located, it could not be determined why the parachute riser, which last had maintenance performed nearly 6 years earlier, was not attached to the 3-point shackle. The pilot’s logbook was not located; therefore, the date of his last flight review and his instrument currency could not be determined. About 7 months before the accident, he last reported having accumulated 341 total hours of flight experience, of which 265 hours were in the accident airplane make and model. Toxicological testing results were positive for amphetamine, quetiapine, hydroxychloroquine, tadalafil, acetaminophen and ethanol. The FAA considers amphetamine and quetiapine as “Do Not Issue/Do Not Fly” medications. Whether the effects of the pilot’s use of amphetamine, quetiapine, hydroxychloroquine, or any associated underlying conditions contributed to the accident or affected his decision making could not be determined. Some or all of the small amount of detected ethanol could have been the result of postmortem production, and it is unlikely that ethanol effects contributed to the accident. In summary, the relatively low-time instrument pilot, who was flying while using multiple unapproved medications, flew into an area of a forecast convective weather that included precipitation and building cumuliform clouds in convective updrafts. These conditions were associated with a line of thunderstorms and severe to extreme turbulence, the latter of which by definition can render an airplane practically impossible to control. While flying well above the published maneuvering speed for the airplane’s weight, the airplane likely began descending with a corresponding airspeed increase, followed by an abrupt or full-control input that resulted in the in-flight breakup. ## Factual narrative According to the FAA Instrument Flying Handbook, a turn to a specific heading should be made at standard rate, defined as 3° per second, which results in a complete 360° turn in 2 minutes. For purposes of instrument flight training in conventional airplanes, any turn greater than a standard rate may be considered steep. A rule of thumb to determine the approximate angle of bank is to use 15% of the true airspeed. The airplane Type Certificate design was modified in December 2006 in accordance with (IAW) Supplemental Type Certificate (STC) SA01999CH by installation of a BRS-182 parachute recovery system. Review of the maintenance records indicated that on August 13, 2007, BRS, Inc., Service Bulletin 07-02 was accomplished by installation of kit part number 014125-01, pickup collar upgrade. On February 12, 2016, the BRS parachute was removed for a 10-year repacking., On August 24, 2017, the repacked BRS parachute was reinstalled, and the rocket and igniter were replaced. That same entry specified that the line cutter was due for replacement in August 2022. There was no record that the line cutter was replaced. By design, the BRS airframe parachute assembly was secured to the airframe by straps connected to both main spars at each wing root and also by straps connected to the left and right attach plates on the rear bulkhead. The front and rear harness straps were connected to separate bolts/bushings of a 3-point shackle assembly (3-point shackle). The riser (strap) of the parachute was connected to the third bolt/bushing of the 3-point shackle. The flight manual supplement associated with the BRS specified that deployment was approved by the FAA up to an airspeed of 135 knots, which matched a placard on the instrument panel. As part of the parachute repacking, the technician attached the parachute riser strap and the rear harness strap to separate attach points of the 3-point shackle; the work was confirmed and signed off by a quality assurance inspector. During installation of the parachute into the airplane after repacking, the front harness was the only harness required to be attached to the remaining separate bolt of the 3-point shackle. During the airplane’s last annual inspection, which was completed on September 1, 2022, the mechanic who signed off the inspection reported that he performed an inspection of the airframe parachute system using instructions provided by the airplane owner. He reported that the inspection was mostly visual, and he did not report any discrepancies with the system. The BRS system instructions for continued airworthiness (ICA) inspections specified external and internal inspections; however, the 3-point shackle was not specifically mentioned, and it could not be viewed during the external or internal inspection as part of the ICA. The airplane was equipped with an Avidyne EX500 multifunction display that was able to display weather radar images, datalink weather that included METARs, AIRMETs, and SIGMETs, andtraffic and terrain information. The airplane was also equipped with a Sandel SN3500 electronic horizontal situation indicator (EHSI) that could display lightning and datalink weather. Both retained components were submitted to the NTSB’s Vehicle Recorder Laboratory for read-out. Data recovered from the Avidyne indicated that the weather receiver of the device was functional during the accident flight, but the recovered data did not contain any other pertinent information to the investigation. Each non-volatile memory chip of the EHSI was removed from the circuit board and read out and imaged successfully but further attempts to recover data from the chips were not performed. Weight calculations were performed using the airplane’s latest empty weight (1,894 pounds), the weight of useable fuel with full fuel tanks (528 pounds), the weight listed at the pilot’s last medical (185 pounds), the estimated weight of a duffle bag found in the wreckage (30 pounds), and subtracting the estimated fuel consumed (255 pounds) during the 2-hour-and-50-minute flight based on the flight plan fuel consumption of 15 gallons per hour. Thus, the estimated airplane weight at the time of the accident was about 2,382 pounds. According to the airplane Pilot’s Operating Handbook and FAA Approved Airplane Flight Manual, the published maneuvering speeds (no abrupt or full control movements) at 2,450 pounds were 100 knots indicated airspeed, or 99 knots calibrated airspeed. On May 7, 2023, about 1849 eastern daylight time, a Cessna 182Q, N725AS, was substantially damaged when it was involved in an accident near Reliance, Tennessee. The private pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. According to FAA air traffic control (ATC) records, the flight departed the South Bend International Airport (SBN), South Bend, Indiana, about 1559, on an IFR flight plan enroute to the Jackson County Airport (JCA), Jefferson, Georgia. Radar data indicated that for about the first 2 hours and 30 minutes of the flight, the airplane maintained a relatively straight course on a southeast track, at an altitude of about 9,100 ft msl. Two times during the flight while in contact with separate ATC facilities the pilot requested a radar vector around weather, confirming with one controller that the airplane was equipped with on-board weather observation capability. About 1834, while flying on a southerly heading assigned by the controller, the airplane was located north of moderate to heavy precipitation as indicated by ground-based weather radar returns. The precipitation was associated with thunderstorms that were moving north to south. The associated cumuliform clouds building ahead of the precipitation line would have had strong updrafts as well. At 1839:29, the pilot was provided with a radar vector for weather and advised to proceed direct to the destination airport. The airplane remained briefly on the vectoredheading and then turned left flying on a southeasterly heading. At 1844:00, the pilot established contact with the Atlanta Air Route Traffic Control Center and advised the controller that the airplane was at 8,900 ft msl, which the controller acknowledged. At 1845:04, the controller asked the pilot if he was assigned 8,900 ft msl, to which he replied that he was assigned 9,000 ft msl but was getting “bounced around a little bit.” The controller advised the pilot that the airplane appeared to be out of the southern edge of the weather and appeared to be “…clear of anything I am showing uh although we do show moderate or greater.” About 1847, a Convective SIGMET was valid for the area and the airplane was at the leading edge of precipitation and building cumuliform clouds, and in an area with multiple pilot reports of moderate to severe turbulence. The airplane continued on the southeasterly heading when, after 1847:22, heading and altitude deviations occurred. A performance study of the airplane’s flight track, based on ATC radar information, showed that the airplane was flying at a calibrated airspeed that was about 11 knots above the published maneuvering speed for its weight. The calibrated airspeed remained above the published maneuvering speed for the remainder of the flight. Beginning about 1848, while flying at 110 knots calibrated airspeed, the airplane began a second right turn increasing to at least a 20° bank angle; the turn was not announced by the pilot or instructed by the controller. About that time, while flying about 26 knots above the published maneuvering speed, the controller broadcast the call sign of the airplane, which the pilot acknowledged. At 1848:24, the controller informed the pilot, “it looks like you are in a little bit of a descent in a turn is everything alright.” The pilot did not reply to that communication and radar contact with the airplane was lost. At the last radar return the airplane was at an altitude of about 8,900 ft msl, at a calibrated airspeed of about 134 knots, and was flying toward the west-northwest. An alert notice was issued for the missing airplane and ground and air searches were performed. The airplane’s fuselage was located the next day about .3 nautical mile south-southeast from the last radar target. A postmortem examination of the pilot was performed by an Assistant Medical Examiner, Knox County, Knoxville, Tennessee. The cause of death was multiple blunt force trauma, and his manner of death was accident. Forensic toxicology was performed on the putrefied specimens of the pilot by the FAA Forensic Sciences Laboratory, Oklahoma City, Oklahoma. Ethanol (14 mg/dL) was detected in the liver but was not detected in the brain. The results were also positive in the liver and muscle for amphetamine, acetaminophen, tadalafil, and hydroxychloroquine. Quetiapine (unquantified amount) was also positive in the liver specimen. Ethanol is a type of alcohol. It is the intoxicating alcohol in beer, wine,and liquor, and if consumed, can impair judgment, psychomotor performance, cognition, and vigilance. FAA regulation imposes strict limits on flying after consuming ethanol, including prohibiting pilots from flying with a blood ethanol level of 0.04 g/dL or greater. Alcohol consumption is not the only possible source of ethanol in postmortem specimens. Ethanol can sometimes be produced by microbes in a person’s body after death. Postmortem ethanol production is made more likely by extensive traumatic injury. Quetiapine, sometimes marketed as Seroquel, is a prescription antipsychotic medication. In the United States, quetiapine is approved by the Food and Drug Administration (FDA) for treating schizophrenia, and conditions associated with bipolar disorder. Quetiapine is regularly prescribed for off-label (non-FDA-approved) uses, including treatment of insomnia without underlying psychiatric illness, as well as treatment of post-traumatic stress disorder and anxiety. Quetiapine may also be misused or abused, often in combination with other recreational substances. Quetiapine commonly causes drowsiness, especially in the initial days after starting a treatment regimen; users may develop tolerance to this effect over time. Quetiapine typically carries a warning that use has the potential to impair judgment, thinking, and motor skills, and that users should be cautioned about performing activities requiring mental alertness, such as operating a motor vehicle or hazardous machinery, until they are reasonably certain that the drug does not affect them adversely. The FAA considers quetiapine to be a “Do Not Issue/Do Not Fly” medication. Amphetamine is a prescription medication and a Schedule II controlled substance. Amphetamine may be prescribed for attention-deficit/hyperactivity disorder, attention-deficit disorder, narcolepsy, and obesity. Amphetamine usually carries a warning that the drug may impair the ability to operate a vehicle or machinery, and that care should be taken until the effects of the drug are assessed after initiation of use. At lower doses, amphetamine has few effects on cognitive functioning and use may result in an enhancement of some psychomotor tasks, including improved reaction time, less fatigue and increased alertness, but may increase willingness to make high-risk choices. Amphetamine use at higher doses may cause poor impulse control and altered cognition, including inability to focus on divided attention tasks, worsened reaction time, and depressed reflexes. Amphetamine can also be used recreationally by users seeking euphoric effects, increased alertness, and relief of fatigue. According to the FAA, amphetamine is a “do not issue/do not fly” medication. Hydroxychloroquine, sometimes marketed as Plaquenil, is a prescription medication; in addition to FDA- approved uses, hydroxychloroquine was proposed for use in treatment or prevention of COVID-19, however, studies have not demonstrated effectiveness for such use.Hydroxychloroquine typically carries a warning that use may cause, cardiac arrhythmias, retinal toxicity, anemia, and neuropsychiatric disorders. In addition, studies noted that persons using hydroxychloroquine for COVID-19 symptoms or prevention, had an increased risk of having abnormal electrocardiograms, increasing their risk for cardiac arrhythmias. The FAA’s Guide for Aviation Medical Examiners issuing medical certificates to pilot’s using hydroxychloroquine for conditions such as arthritis includes a status report form for the purpose of collecting information from an ophthalmologist or optometrist on an individual on hydroxychloroquine who is being considered for medical certification. Tadalafil is a prescription medication commonly used to treat erectile dysfunction, symptoms of an enlarged prostate, and to treat pulmonary hypertension. Occasional use of tadalafil for erectile dysfunction is acceptable for pilots if there are no side effects and a 24-hour waiting period is observed from the last dose prior to flying. Daily use of tadalafil for an enlarged prostate is also acceptable for pilots if there are no side effects with use, and a 1-week waiting period has passed after initiation of therapy. Acetaminophen is an over-the-counter medication commonly used to treat minor aches and pains and reduce fever. Acetaminophen is not generally considered impairing. The accident pilot requested and received a standard preflight weather briefing package from ForeFlight at 1544 on May 6th. The weather briefing package contained all the standard weather forecast information valid at that time. Because the weather briefing was more than 18 hours before the intended departure, the weather data provided to the pilot did not include graphical forecast data. The pilot did not request a standard, updated or abbreviated briefing package from ForeFlight before departure on May 7th. Had he done so, forecast data and graphics would have been provided. The pilot also viewed airport information at 1301, 1313, 1429, and while in-flight at 1624 for his destination airport. Convective SIGMET 26E, which implied severe or greater turbulence, severe icing, and low-level windshear, was issued at 1755, or about 54 minutes before the accident, and it was valid until 1955. The Convective SIGMET was valid for VA, NC, TN, and KY and it reported an area of severe thunderstorms moving from 320° at 35 knots, with tops to Flight Level (FL) 410, hail to 1 inch, and wind gusts to 50 knots possible. High-Resolution Rapid Refresh (HRRR) modeling for the approximate accident site coordinates for 1900 hours local indicated that the wind at about 8,500 ft was from 270° at 16 knots. One witness near the accident site reported that about the time of the accident a varying wind gust from 168° to 340° occurred, with the gust from the south-southeast being described as “really hard.” Pilot reports indicated that severe turbulence was encountered in the area of the accident. One pilot,flying a Beech 350 airplane about 131 nautical miles west-northwest of the accident site in the same moving line of thunderstorms reported about 31 minutes after the accident encountering severe turbulence at 5,000 ft msl with ± 500 ft altitude change. Another pilot flying a Piper PA-46 airplane about 156 nautical miles west-northwest of the accident site in the same moving line of thunderstorms also submitted an urgent pilot report about an hour before the accident encountering extreme turbulence between 10,000 and 11,000 ft msl. There was no injury or damage reported by either pilot. FAA Aviation Weather Services Advisory Circular 00-45E defined moderate turbulence as causing changes in altitude and/or attitude but the aircraft remained in positive control at all times and usually caused variations in indicated airspeed. Severe turbulence was defined as large, abrupt changes in altitude and/or attitude causing large variations in indicated airspeed, with momentary times where the aircraft is out of control. Extreme turbulence was defined as the aircraft being violently tossed about and being practically impossible to control with possible structural damage. According to the pilot’s FAA airman records, on November 21, 2020, he received notification of disapproval of application for adding an instrument rating to his private pilot certificate. The notice indicated he would be re-examined on preflight procedures, air traffic control clearances and procedures, flight by reference to instruments, navigation systems, and instrument approach procedures. On December 15, 2020, he passed a check ride in the accident airplane, adding an instrument rating to his private pilot certificate. He reported having accumulated 270 total hours of flight experience and 49.5 hours of instrument flight experience on the application for the instrument rating. The pilot’s logbook was not located; therefore, the date of his last flight review and his instrument currency could not be determined. He reported to an insurance company having 341 total hours of flight experience and 265 hours of flight experience in the accident airplane make and model as of October 10, 2022. The main wreckage, consisting of the fuselage and cabin, came to rest in a wooded area behind a house. Damage to a tree immediately adjacent to the main wreckage was noted about 30 ft above ground level; the impact mark was oriented on a magnetic heading of 167°. No fire was noted on any observed components. Both wings, the aft empennage, both wing lift struts, both cockpit/cabin entry doors, majority of the right horizontal stabilizer, right elevator, and right elevator trim tab were not attached. The propeller remained attached to the engine, which remained attached to the fuselage by one engine mount. The empennage was separated at approximately fuselage station (FS) 156.0. Exiting the aft portion of the fuselage were black (front) and yellow straps (rear) associated with the front harnessesconnecting through the 3-point shackle to the rear harness of the airframe ballistic parachute. The front harness strap was wrapped tightly several times to the left. Entrapped with the twisted webbing harness were the elevator and rudder primary control cables, trim cables, and red rope, which was the same kind of rope found in the cabin section of the wreckage. Examination of the front harness revealed it exhibited entanglement and tightening. The left and right wings were located about 0.6 nautical mile (nm) and 165° and 0.7 nm and 185°, from the main wreckage respectively. The aft empennage was located about 434 ft and 203° from the main wreckage. The right wing and a piece of left-side fuselage skin between FS 156.0 and 172.0 was found embedded into the fractured right aileron at approximately wing station 154.0. The airframe parachute and rocket were never located. Inspection of the aft empennage revealed a 1/4-inch diameter rope was wrapped around the elevator trim cable and multiple loops of the rope were noted. The vertical stabilizer and rudder remained attached, but the rudder counterweight was separated and not located. The left horizontal stabilizer and elevator remained attached, but the left elevator counterweight was subsequently recovered away from the main wreckage. Examination of the remaining section of the right horizontal stabilizer revealed the forward and aft spars were fractured outboard from the root about 9.5 inches and 23 inches, respectively. The forward spar top spar cap was displaced down, while the lower spar cap was displaced up. The spar web was displaced aft. The aft spar was displaced down about 90° beginning 4 inches outboard of the attach. The fracture surfaces exhibited evidence consistent with overload with no evidence of preexisting cracking. Examination of the left wing forward spar structure revealed the main attach fitting (spar block) was structurally separated but still had the BRS attachment bracket and associated harness installed; it was located near the main wreckage. A small section of left-wing front spar root reinforcement plate remained entrapped by the spar attach bolt. The reinforcement plate was bent forward. The forward-wing attach bolt was in place and the bolt was bent. Examination of the airframe and left-wing aft structure revealed the aft spar (wing side) was fractured about 1.5 inches outboard of the wing attach bolt. Two sections of wing spar reinforcement plate and spar remained attached. The rear spar carry thru was twisted down 90° and aft 90°. The wing spar reinforcements were rotated up about 30° and bent aft. The wing lift strut lower fitting was fractured consistent with overload. Examination of the airframe and right wing forward structure revealed a section of door post remained attached. The spar block remained attached. The bolt was in place, and a small section of front root reinforcement plate and spar “L” shaped remained attached. The BRS bracket remained attachedwith corresponding 54 inches of fractured webbing. The front spar root reinforcement plate was bent forward and the spar “L” shaped was bent slightly aft. The right wing lift strut exhibited a semi-circular impact damage and was fractured consistent with overload about 31 inches from the upper attach point; thus, 61 inches of lift strut were not accounted for. Examination of the right wing aft spar revealed it was displaced forward and slightly down. Further examination of the aft spar fitting revealed a portion of fractured rear fuselage spar remained attached by the securing hardware. The fracture surfaces exhibited evidence consistent with an overload fracture with no evidence of preexisting cracking. All fracture surfaces of both wings’ main and aft spars and left-wing lower lift strut fitting exhibited evidence consistent with overload failure with no evidence of preexisting cracking. Examination of the flight controls for roll, pitch, yaw, including the canards that were installed IAW an STC, revealed no evidence consistent with preimpact failure or malfunction. The flap actuator depicted the flaps were fully retracted, which corresponded to the flap selector position in the cockpit. Examination of the cockpit revealed extensive impact damage, and the instrument panel was structurally separated with numerous avionics separated from the instrument panel and radio stack. Evidence of circumferential scoring was noted on either the rotor, housing, or both of several gyroscopic flight instruments including from a loose rotor, from the rotor of the S-Tec gyroscope instrument, and the attitude indicator. The throttle, propeller, and mixture controls were full in, and the BRS Activation Handle was outside the handle housing and the activation cable had a slight kink near the handle. Examination of the airframe BRS parachute system components revealed the parachute canister and rocket support, and the rocket fairing exhibited extensive impact damage. The fire pin actuator was found inside the rocket cone with the activation cable still attached consistent with normal activation. Kevlar straps that connected to each front main spar and also behind the rear seats on both sides of the airplane remained connected at all attach points on the airplane and at the 3-point shackle; however, the right forward strap was fractured 54 inches from the spar attach point. The 3-point Shackle, which had separate attach points for the forward and aft straps and also for the riser of the airframe parachute, was located within the main wreckage; however, the riser for the airframe parachute was not attached to the 3-point shackle. The bolt/bushing at the 3-point shackle that would have secured the parachute riser did not have any strap in place and the bolt/bushing were not visibly deformed. The other two bolts/bushings of the 3-point shackle that secured the forward and aft straps also did not exhibit any visible damage. Further examination of a portion of the rearharness revealed that the shock absorption stitching pattern was not peeled or torn, consistent with no force having been applied to the rear harness at the 3-point shackle level. Examination of the engine following recovery revealed thumb suction and compression on all cylinders, valvetrain continuity, and continuity was confirmed to the accessory section when the propeller was rotated through 720° by hand. The propeller governor remained attached to the engine and the governor oil screen was clear of debris. The propeller control cable remained attached to the governor and continuity was confirmed to the propeller control knob. Examination of the ignition, lubrication, and engine fuel system components revealed no evidence consistent with preimpact failure or malfunction. Examination of the vacuum system components revealed the vacuum pump was impact damaged but remained attached to the engine by one bolt. The top two bolts remained in place, but the housing impact separated and one of the lower attachment bolts sheared. One tooth of the engine-side vacuum pump drive coupling was missing, and one was damaged. The teeth of the vacuum-pump drive coupling and the vacuum pump shear coupling remained intact; the pump could not be rotated by hand. Following removal of the back cover the rotor exhibited several cracks and one vane was cracked. The propeller hub remained attached to the crankshaft flange and was undamaged. The propeller spinner was impact crushed aft and torn. Both blades remained secured inside the hub but could be rotated using hand force. One blade was bent aft about 90° about 8 inches from the hub attachment point, exhibited both chordwise and longitudinal scratching, and the outer 2 inches were slightly curled, while the remaining blade exhibited distortion, and the tip was curled aft. ## Aircraft - Registration: [N725AS](https://openairdocs.org/aircraft/N725AS), registered now, S/N 18266640, built 1978 (OpenAirDocs) - Reported make and model: CESSNA 182 (Q) - Registry model: [Cessna 182Q](https://openairdocs.org/model/cessna-182q) (registry code 2072732) (OpenAirDocs) - Registry engine: [Continental O-470 series](https://openairdocs.org/engine/continental-o-470-series) (registry code 17026, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 18266640 - Year built: 1978 - Airframe hours: 3265.29 - Engines: Teledyne Continental IO-470-F (33) 260 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, September 1, 2022 - Departed: SBN, South Bend, IN - Destination: JCA, Jefferson, GA - Flight plan: IFR - Equipment: Electronic multifunction display, Stall warning system, ADS-B, Airframe parachute, Auto-pilot, Data recorder ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 54; injuries: fatal; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 2, without waivers/limitations; seat: left; restraint: 4-point; toxicology performed; flight hours: 363.4 total, 287.4 in this make and model ## Weather - Conditions: Instrument (IMC), Day - Wind: 360° at 10 knots, gusting 29 - Visibility: 10 statute miles - Lowest ceiling: 4,900 ft broken - Temperature: 70 °F, dew point 59 °F - Altimeter: 30.11 inHg - Turbulence: Extreme - Observed at: KMMI, 12 nm away - METAR: KMMI 072235Z AUTO 36010G29KT 10SM SCT042 BKN049 OVC070 21/15 A3011 RMK A01 ## 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 20230507008449A](https://openairdocs.org/incident/20230507008449A), May 7, 2023: Cessna 182Q, Reliance, TN, Destroyed, 1 fatal. According to ATC data, the aircraft was enroute from ksbn to kjca at 9000 feet when at 2248Z the aircraft enter a slow descent and turn. Radio and radar… ## Other investigations on N725AS (1) 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. - [NTSB ERA14CA023](https://openairdocs.org/ntsb/ERA14CA023), Oct 27, 2013: Cessna 182Q (N725AS), Wauchula, FL, substantial damage. Probable cause: The pilot's improper landing flare which resulted in a hard landing. ## Docket (26 files) The files NTSB released with the investigation on June 24, 2025, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=114699. 93.5 MB in all. - Witness statements (item 1, PDF, 2 pages, 239 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=15544304&FileExtension=pdf&FileName=Witness%20Statements_Redacted-Rel.pdf - Record of NTSB conversations (item 2, PDF, 11 pages, 1 photo, 2.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18405925&FileExtension=pdf&FileName=Record%20of%20NTSB%20Conversations_11%20Pgs_Redacted-Rel.pdf - NTSB memorandum for record - federal aviation administration airman file review (item 3, PDF, 1 page, 67 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18413737&FileExtension=pdf&FileName=FINAl%20Memo%20For%20Record%20-%20Pilot%20Airman%20File%20Review%20v01-Rel.pdf - NTSB memorandum for record - pilot flight time from insurance paperwork (item 4, PDF, 1 page, 64 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18414596&FileExtension=pdf&FileName=FINAL%20Memo%20For%20Record%20-%20Pilot%20Flight%20Time%20Fm%20Insurance%20Paperwork%20v01-Rel.pdf - Excerpts from pilot's operating handbook and FAA approved airplane flight manual (item 5, PDF, 2 pages, 597 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18414606&FileExtension=pdf&FileName=Excerpts%20Fm%20POH_AFM-Rel.pdf - Maintenance record excerpts (item 6, PDF, 4 pages, 2.6 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18480120&FileExtension=pdf&FileName=Maintenance%20Log%20Excerpts_Redacted-Rel.pdf - Weather factual report (item 7, PDF, 36 pages, 4.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=16564656&FileExtension=pdf&FileName=ERA23FA219_weatherfactualSuffernfinal-Rel.pdf - Weather attachment 1 (item 8, GIF, 12.6 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=16235540&FileExtension=gif&FileName=attachment1_animation_2201to2331utc_CODNEXLAB-GOES-East-local-Tennessee-02-23_31Z-20230507_map-id-glm_flash_noBar-19-1n-10-100-Rel.gif - Weather attachment 2 (item 9, GIF, 20.8 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=16236073&FileExtension=gif&FileName=attachment2_animationwxradar_lightning_2214to2301utc_0_5degree-Rel.gif - Weather attachment 3 (item 10, ZIP, 21.9 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=16235975&FileExtension=zip&FileName=attachment3_PDWB-Rel.zip - Weather attachment 4 (item 11, PDF, 7 pages, 3.6 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=16236260&FileExtension=pdf&FileName=attachment4_GFA-Rel.pdf - Weather attachment 5 (item 12, PDF, 3 pages, 191 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=16235985&FileExtension=pdf&FileName=attachment5_foreflightERA23FA219_Redacted-Rel.pdf - Weather attachment 6 (item 13, ZIP, 1.9 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=16235231&FileExtension=zip&FileName=attachment6_Briefing%20KSBN%20to%20KJCA-Rel.zip - NTSB prepared partial transcription of communications (item 14, PDF, 4 pages, 66 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=16192368&FileExtension=pdf&FileName=NTSB%20Prepared%20Partial%20Transcription%20of%20Communications_4%20Pgs-Rel.pdf - FAA chronological summary of flight communications (item 15, PDF, 10 pages, 7.9 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=16187375&FileExtension=pdf&FileName=FAA%20Chronological%20Summary%20of%20Flight%20Communications-Rel.pdf - Flight plan information (item 16, PDF, 2 pages, 39 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18335690&FileExtension=pdf&FileName=Flight%20Plan%20Information_Redacted-Rel.pdf - Aircraft performance study (item 17, PDF, 9 pages, 2.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18643294&FileExtension=pdf&FileName=ERA23FA219_PerformanceStudy-Rel.pdf - N725AS radar data (item 18, CSV, 106 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18645781&FileExtension=csv&FileName=N725AS-Rel.csv - Wing examination summary (item 19, PDF, 14 pages, 11 photos, 3.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18705933&FileExtension=pdf&FileName=FINAL%20Wing%20Exam%20Summary%20v04_ERA23FA219_ALL%20Exctd_Redacted-Rel.pdf - Airplane information and brs system description and examination summary (item 20, PDF, 22 pages, 22 photos, 4.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18540271&FileExtension=pdf&FileName=FINAL%20BRS%20System%20Description%20%26%20EXAMINATION%20SUMMARY%20v07_ALL%20Exctd_Redacted-Rel.pdf - Toxicological report (item 21, PDF, 1 page, 358 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18312527&FileExtension=pdf&FileName=FAA%20Tox%20Report_Redacted-Rel.pdf - Medical factual report (item 22, PDF, 8 pages, 200 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18685742&FileExtension=pdf&FileName=ERA23FA219_Reliance,%20TN%20Medical%20Factual%20Report%20longform%20-%20final-Rel.pdf - Multiple electronic devices - specialist's factual report (item 23, PDF, 9 pages, 908 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18505452&FileExtension=pdf&FileName=Multiple%20Electronic%20Devices%20-%20Specialist%27s%20Factual%20Report_ERA23FA219-Rel.pdf - Attachment 1 to multiple electronic devices - specialist's factual report (item 24, CSV, 45 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18246794&FileExtension=csv&FileName=Attachment%201%20to%20Multiple%20Electronic%20Devices%20-%20Specialist%27s%20Factual%20Report_ERA23FA219-Rel.csv - Statement of party representatives to NTSB investigation (item 25, PDF, 10 pages, 1.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18312104&FileExtension=pdf&FileName=Party%20Forms_Redacted-Rel.pdf - Release of aircraft wreckage, NTSB form 6120.15, and NTSB evidence control forms (item 26, PDF, 10 pages, 2.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18272955&FileExtension=pdf&FileName=Wreckage%20Release%20%26%20ECFs_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.