Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

July 8, 2024 · Cessna 182 A · N2198G

Rutherfordton, NC

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
July 8, 2024
Injury Outcomes
3 injuries (3 fatalities)
Location
Rutherfordton, NC
Aircraft
Cessna 182 A (1958)
Tail Number
N2198G
Operator
Airstar Aviation
Injuries
Fatal
Aircraft Damage
Substantial
NTSB Number
ERA24FA294

On July 7, 2024, about 2107 eastern daylight time, a Cessna 182A, N2198G was substantially damaged when it was involved in an accident near Rutherfordton, North Carolina. The pilot and two passengers were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 positioning flight. The flight departed Johnson County Airport (6A4), Mountain City, Tennessee, destined for Rutherford County Airport/Marchman Field (FQD), Rutherfordton, North Carolina. On the day of the accident, Skydive Mountain City LLC had leased the accident airplane from Airstar Aviation LLC for their skydiving operations that day. All three occupants, the pilot, and two skydiving instructors, worked as independent contractors for both companies. On this day, the pilot was working for Airstar Aviation, and both skydiving instructors were working for Skydive Mountain City. According to the owner of Skydive Mountain City, the airplane was flown into 6A4 that morning from FQD by the pilot, and then had a normal day of skydiving operations, flying a total of 8 “loads”, with each load consisting of a takeoff, release of skydivers, and then a landing. The weather at 6A4 was great for most of the day. In the early afternoon, they were on the ground for about 3 hours due to clouds, but once the clouds cleared, they continued jump operations. There were no issues, as far as they could tell, with the airplane and they finished jump operations around 1945. Before the flight back to FQD, the owner of Skydive Mountain City, the pilot, and the skydiving instructors had conversations about the weather that had been over FQD during the day. They had three plans in place. The first one was for the owner of Sky Dive Mountain City to drive them back to FQD, and the pilot would pick the airplane up on another day. The second was to fly to FQD. The third was to divert to Asheville, North Carolina, in case weather had not cleared over FQD. The pilot then checked the weather one last time and it looked like the weather had just cleared at FQD, so the pilot decided to fly. They still discussed diverting to Asheville, North Carolina, in case the weather was different from what he saw on the radar. The pilot and the two skydiving instructors then departed 6A4 shortly before 2030. The airplane was topped off with fuel prior to the departure. At 2044 the owner of Skydive Mountain City exchanged text messages with one of the skydiving instructors onboard the airplane, during which they indicated that the flight was going as planned and they were heading to FQD. She next sent a text message to the skydiving instructor around 2200, but did not hear back, and she did not think anything more about it since she figured he was driving back to his house. The next day, she was woken around 0400 by the pilot’s wife, who advised her that he had never come home. The Chief Executive Officer/owner of Airstar Aviation LLC, who also owned Skydive Carolina, stated that he leased the airplane to Skydive Mountain City to help the owner out. There was no written contract, and it was “all verbal, but she does pay us.” He also advised that he had done this before for her. The pilot and skydiving instructors were all contract labor, and that the instructors were all “tandem instructors.” Even though the company was based in Chester, South Carolina, the reason for the pilot’s destination was that he lived near FQD. According to a witness, who lived on top of a hill about 3 miles east northeast of Marion, North Carolina, he would always notice airplanes flying in to and out of Shiflet Field (9A9), Marion, North Carolina, but on the day of the accident, he noticed an airplane that was flying north to south. He was outside of his house when he heard the airplane. He described that, “the engine sounded strong,” that the airplane was a half mile west of his position, and that there was a “cloud ceiling.” The airplane was under the clouds, about 1,500 feet above him. The airplane was not banking or turning at the time. He advised that “storms” had come through the area about 1700 to 1900, and the heaviest of the storms was over. He also advised that there was a lot of moisture and fog. According to preliminary Automatic Dependent Surveillance-Broadcast (ADS-B) data, after departing 6A4, the airplane turned south, and the first ADS-B track data was recorded at 2030:59 when the airplane was at 3,425 feet msl, with a ground speed of 82 kts. The airplane then traveled out of ADS-B surveillance coverage, and when track data resumed at 2055:38, the airplane was on a track of 151º at 5,800 feet, with a ground speed of 118 kts. The airplane then entered a descending spiral before proceeding south, entered another descending spiral, and then headed south again until it approached the area where the accident occurred, and after entering another descending spiral. The last track data was recorded at 2106:48 when the airplane was on a track of 100º at 2,250 feet, and 136 kts. Examination of the accident site and wreckage revealed signatures consistent with the airplane impacting the mountainous terrain in a wings level nose low attitude on an approximate heading of 130º, at an altitude of about 2,000 feet. During the impact sequence the airplane first impacted a tall tree severing it approximately 60 feet above ground level, followed by a second shorter thicket of trees, and then dense brush and terrain. The airplane left an impact crater where the propeller was found, and the main wreckage was located 50 feet further along the wreckage path. The airplane was subject to a post-impact fire, and most of the fuselage and cockpit were thermally damaged. The empennage was impact and thermally separated near the baggage compartment bulkhead. The empennage came to rest atop the left wing and displayed leading edge impact damage. Most of the right main wing spar was found near the initial impact crater and fragments of its skin were found along the wreckage path. Both horizontal stabilizers were displaced upwards and displayed leading edge damage. The right elevator was separated from its mounting location. The vertical stabilizer forward dorsal skin displayed wrinkling. The engine was located forward of the burnt fuselage area free from its mounts but partially attached to its control cables and wires. The propeller hub was separated from the crankshaft. Both propeller blades displayed power signatures and were separated from the impact damaged hub. Both fuel tanks were thermally damaged, and the portions of one fuel cap assembly was found in the wreckage. The fuel selector handle and face plate were found free of the wreckage with the connecting stem broken at the fuel selector valve. Air was blown through the selector valve, and it was determined to be in the “Both” position. Fuel consistent in smell with 100LL was present in the lines of the selector. The wreckage was retained for further examination.

NTSB Probable Cause

The pilot’s failure to maintain clearance from clouds, resulting in controlled flight into terrain due to mountain obscuration.

Full Narrative

HISTORY OF FLIGHTOn July 7, 2024, about 2107 eastern daylight time, a Cessna 182A airplane, N2198G, was destroyed when it was involved in an accident near Rutherfordton, North Carolina. The pilot and two passengers were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 positioning flight. The pilot flew the airplane to Johnson County Airport (6A4), Mountain City, Tennessee, from Rutherford County/Marchman Field (FQD), Rutherfordton, North Carolina, on the morning of the accident for the purpose of skydiving operations. According to the owner of the skydiving operation, the pilot completed jump operations about 1945 and was returning to FQD when the accident occurred. Before the flight back to FQD, the owner of the skydiving operation, the pilot, and the two skydiving instructors who were passengers on the accident flight discussed the weather that was over FQD during the day. They had three plans in place. The first one was for the owner to drive them back to FQD, and the pilot would pick the airplane up on another day. The second was to fly to FQD. The third was to divert to Asheville, North Carolina, in case the weather had not cleared over FQD. The owner of the skydiving operation reported that the pilot then checked the weather one last time and decided it had just cleared at FQD, so he decided to fly there. They still discussed diverting to Asheville, North Carolina, in case the weather they encountered was different from what he saw on the radar. The pilot and the two skydiving instructors then departed 6A4 shortly before 2030. The airplane was topped off with fuel prior to the departure. At 2044 the owner of the skydiving operation exchanged text messages with one of the skydiving instructors onboard the airplane, who responded that the flight was going as planned and they were heading to FQD. The owner sent another text message to the skydiving instructor about 2200, but did not receive a response. She reported that she did not think anything more about it since she thought he was likely driving back to his house. The next day, she was awoken about 0400 by a call from the pilot’s wife, who advised her that he had not come home. According to a witness who lived on top of a hill about 3 miles east-northeast of Marion, North Carolina, he frequently noticed airplanes flying into and out of Shiflet Field (9A9), Marion, North Carolina. On the day of the accident, he noticed an airplane flying north to south. He was outside of his house when he heard the airplane. He reported that “the engine sounded strong,” that the airplane was about a half a mile west of his position, and that there was a “cloud ceiling.” The airplane was under the clouds, about 1,500 ft above him. The airplane did not bank or turn at that time. He reported that “storms” had come through the area about 1700 to 1900, and the heaviest of the storms was over. He also reported that there was a lot of moisture and fog. According to radar data, after departing 6A4, the airplane turned south, and the first ADS-B track data was recorded at 2030:59 when the airplane was at 3,425 ft msl, with a ground speed of 82 kts. The airplane then traveled out of radar coverage, and when track data resumed at 2055:38, the airplane was on a track of 151° at 5,800 ft msl, with a ground speed of 118 kts. The airplane then entered a descending right spiral before proceeding south. The airplane entered another descending spiral, during which a passenger sent two photos via text message to a family member. The view of the photos was out the left side of the airplane, showing the airplane surrounded by cloud cover and included the statement, “Flying over mountains and can’t see sheet.” The airplane then headed south again. Figure 1. Radar track showing the flight path from the beginning of the right 360° turns to the end of the flight track. The airplane made a turn to the left and began a climbing right turn until it reached an altitude of 2,250 ft msl. The airplane continued its right turn and began a descent until it impacted terrain at an altitude of about 2,000 ft msl. Figure 2. End of the flight track showing low-altitude flight with a left turn followed by an ascending right 360° turn over rising terrain, with the track ending with a descent into terrain. The pilot did not file a flight plan and was not in communication with air traffic control. PERSONNEL INFORMATIONAlong with his flight certificates the pilot was also a certified airframe and powerplant mechanic. The pilot’s most recent flight log entries indicated a total flight time of 1,098.3 hours, including 32.5 hours of actual instrument time and 75.6 hours of simulated instrument time. His last FAA second-class medical certificate was issued with a limitation for corrective lenses to meet vision standards at all required distances. Review of the pilot’s flight logbook dating back to November 19, 2023, did not show evidence of instrument currency in the 6 months prior to the accident flight. AIRCRAFT INFORMATIONThe airplane was configured as a skydiving airplane by removing the passenger seats and modifying the right cabin door into a swing-up jump door. METEOROLOGICAL INFORMATIONWeather radar data from a station located about 6 miles south of the accident site indicated that the accident airplane's flight path ended in an area of light precipitation. Weather model data identified an atmosphere that was conducive to clouds down to 1,800 ft msl. At 2105, weather at FQD reported a calm wind, visibility of 7 statute miles, with light rain, ceiling overcast at 700 ft agl, ambient temperature and dew point temperature of 22°C, and altimeter setting of 30.09 inches of mercury. The automated station had a precipitation discriminator and detected lightning beyond 10 statute miles to the southeast, with a precipitation rate of 0.01 inches per hour. Meteorological data supported the presence of ceilings as low as 1,800 ft msl. Figure 3. Greer, South Carolina, Weather Surveillance Radar 88 Doppler 0.218° Level-II base reflectivity product from a sweep initiated at 2106:05. The accident airplane’s flight track is marked by the white line. Figure 4. Geostationary Operational Environmental Satellite-16 infrared imagery from 2106. The accident location is indicated by the red dot. Image is not corrected for parallax error. AIRPORT INFORMATIONThe airplane was configured as a skydiving airplane by removing the passenger seats and modifying the right cabin door into a swing-up jump door. WRECKAGE AND IMPACT INFORMATIONExamination of the accident site and wreckage revealed signatures consistent with the airplane impacting the mountainous terrain in a wings-level, nose-low attitude on an approximate heading of 130°, at an altitude of about 2,000 ft msl. Terrain signatures were consistent with the airplane first impacting a tall tree, followed by a second shorter thicket of trees, and then dense brush and terrain. The airplane left an impact crater where the propeller was found, and the main wreckage was located 50 ft further along the wreckage path. The airplane was subject to a post-impact fire, and most of the fuselage and cockpit were thermally damaged. The empennage was impact and thermally separated near the baggage compartment bulkhead. The empennage came to rest atop the left wing, and the wing displayed leading edge impact damage. Most of the right main wing spar was found near the initial impact crater and fragments of its skin were found along the wreckage path. Both horizontal stabilizers were displaced upward and displayed leading edge damage. The right elevator was separated from its mounting location. The vertical stabilizer forward dorsal skin displayed wrinkling. The engine was located forward of the burnt fuselage area free from its mounts but partially attached to its control cables and wires. The propeller hub was separated from the crankshaft. Both propeller blades displayed power signatures and were separated from the impact-damaged hub. Both fuel tanks were thermally damaged, and portions of one fuel cap assembly were found in the wreckage. The fuel selector handle and face plate were found free of the wreckage with the connecting stem broken at the fuel selector valve. Air was blown through the selector valve, and it was determined to be in the Both position. Fuel consistent in smell with 100LL aviation fuel was present in the lines of the selector. Postaccident examination of the wreckage did not reveal any preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation. MEDICAL AND PATHOLOGICAL INFORMATIONAn autopsy of the pilot was performed by Autopsy Service at Atrium Health Wake Forest Baptist, which is designated as the Regional Autopsy Center for Rutherford County by the North Carolina Office of the Chief Medical Examiner. According to the autopsy report, the cause of death was multiple blunt force injuries, and the manner of death was an accident. Due to the extent of the 59-year-old male pilot’s injuries, his autopsy, including examination of his heart, brain, and lungs, was markedly limited for evaluation of natural disease. Within this limitation, no significant natural disease was identified. Postmortem toxicological testing by the FAA Forensic Sciences Laboratory detected ethanol at 0.042 g/hg in brain tissue (in tissue, concentrations in g/hg are approximately equivalent to concentrations in g/dL). N-propanol was also detected in brain tissue. Neither ethanol nor n-propanol was detected in liver tissue. The laboratory determined that available blood was unsuitable for analysis. No urine or vitreous fluid was available for testing. Ethanol – Ethanol 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 a prohibition on piloting a civil aircraft while having 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 sometimes may be produced by microbes in a person’s body tissues and fluids after death. Postmortem ethanol production is made more likely by extensive traumatic injury, which can spread microbes. N-propanol – N-propanol is another alcohol that can be produced by microbes in a person’s body tissues and fluids after death. Detection of n-propanol in a postmortem specimen potentially is indicative of postmortem microbial activity in the specimen, with or without associated ethanol production.

Flight

Event TypeAccident
Event Time21:07 EDT
Nearest Airport0nm
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireGrd
Aircraft ExplosionNo

Aircraft

AircraftCessna 182 A
Tail NumberN2198G
Aircraft CategoryAir
DamageSubstantial
OperatorAirstar Aviation
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsCont Motor · O-470-R25 · Reciprocating · 230
Seats1

People & Injuries

Injury Summary3 injuries (3 fatalities)
Fatal3
Serious0
Minor0
Uninjured0
Total3
Crew 1Age 59 · Second Class · Fatal
Crew 2Age 54 · Fatal
Crew 3Age 37 · Fatal

Conditions

ConditionsIMC
LightDusk
Wind300° @ 3 kt
Visibility5 sm
CeilingBroken clouds 2800 ft
Altimeter30.06 inHg
Observation Time20:05
Weather SourceWFAC

Appendix: Source Data