N5798T

Destroyed
Fatal

CESSNA 172S/N: 17251698

Accident Details

Date
Sunday, December 26, 2021
NTSB Number
CEN22FA082
Location
Hardy, AR
Event ID
20211227104443
Coordinates
36.346112, -91.542252
Aircraft Damage
Destroyed
Highest Injury
Fatal
Fatalities
2
Serious Injuries
0
Minor Injuries
0
Uninjured
0
Total Aboard
2

Probable Cause and Findings

The non-instrument rated pilot’s decision to continue visual flight into an area of instrument meteorological conditions, which resulted in a loss of control due to spatial disorientation. Contributing to the accident was a loss of engine power due to fuel exhaustion.

Aircraft Information

Registration
N5798T
Make
CESSNA
Serial Number
17251698
Engine Type
Reciprocating
Year Built
1964
Model / ICAO
172C172
Aircraft Type
Fixed Wing Single Engine
No. of Engines
1

Registered Owner (Historical)

Name
DUNHAM BRADLEY L
Address
PO BOX 514
Status
Deregistered
City
BONO
State / Zip Code
AR 72416-0514
Country
United States

Analysis

HISTORY OF FLIGHTOn December 26, 2021, about 1729 central standard time, a Cessna 172E airplane, N5798T, was destroyed when it was involved in an accident near Hardy, Arkansas. The private pilot and passenger sustained fatal injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

A review of flight track data indicated that the airplane was airborne before it was visible on radar. The airplane first appeared about 13 nm north of the Walnut Ridge Regional Airport (ARG), Walnut Ridge, Arkansas, at 1627, at an altitude of about 2,500 ft. The airplane flew generally south toward ARG until track data was lost at about 1643, 3.5 nm north of ARG.

The airplane’s track data reappeared at 1653, about 3 nm north of ARG, climbing from 2,800 ft. The airplane flew left and right several times in a back and forth “s-type" movement and then straightened out, flew west-north-west, and climbed to an altitude of about 4,500 ft, then descended lower in the latter part of the flight.

While en route, the pilot contacted air traffic control and requested the weather at his destination airport along with the weather at additional airports. When queried, he stated he was over his destination airport. The pilot reported that he wanted to land because he had less than a quarter tank of fuel left, and he was going to continue flying west. The pilot then informed air traffic control that he was setting up to land at an alternate airport when radar contact was lost.

At 1722, the airplane crossed over the Sharp County Regional Airport (CVK), Ash Flat, Arkansas, from east to west at an altitude of about 4,000 ft. When the airplane was almost 2.5 nm west-north-west of CVK, it turned right, descended slowly, and flew a track consistent with an attempt to make an approach to CVK. The airplane then entered a tight left turn and traveled to the north. During this time there were abrupt changes in ground speed, altitude, and the direction of flight. The airplane entered at least one sharp counterclockwise 360° turn and flew north-north-east until track data was lost about 1728.

The Fulton County (Arkansas) Sheriff’s Office was provided copies of text messages the passenger sent to a family member while in flight. One text message stated, “ran into weather can’t see anything” and another text message later stated, “out of gas in air.”

The airplane, which was located on heavily wooded private property in the Ozark mountains, was destroyed by the impact sequence. PERSONNEL INFORMATIONAccording to Federal Aviation Administration (FAA) records, the pilot did not hold an instrument rating.

The pilot’s logbook had an entry for a flight review; however, the date block was found empty. The entry was signed by the flight instructor on November 14, 2019. AIRCRAFT INFORMATIONThe airplane was not equipped for instrument flight.

The airplane was modified via an FAA-approved supplemental type certificate to utilize automotive gasoline. Investigators were not able to determine how much fuel was on board at the time of departure.

The airplane’s maintenance records were not available for review. METEOROLOGICAL INFORMATIONA search of archived ForeFlight information indicated that the pilot did have a ForeFlight account and could have looked at “live” weather data, but that data is not logged. The pilot did not request a weather briefing or review static weather imagery before the accident flight.

A review of meteorological data showed that a warm frontal boundary was located over the area of the accident site, with small temperature-dew point spreads, allowing for abundant moisture for cloud, fog, and drizzle formation. An inversion with the inversion top near 5,000 ft mean sea level (msl) was over ARG and over the area of the accident site. In addition to the low instrument flight rules (LIFR) conditions, there were relatively strong wind conditions from the surface to 8,000 ft msl that would have led to low-level wind shear.

As noted by pilot reports and the 1700 High-Resolution Rapid Refresh sounding, the cloud tops of the first layer of clouds were likely between 2,700 and 3,500 ft msl, with additional high clouds above that noted on the GOES-16 infrared imagery.

An AIRman’s METeorological Information (AIRMET) Sierra for instrument flight rules (IFR) conditions was valid for the accident site at the accident time along with Center Weather Advisory 106, which forecast LIFR conditions. The freezing level was above 12,000 ft, which was above the accident flight’s flight level. The AIRMET for IFR conditions were noted on the Graphical Forecasts for Aviation, and were valid before the accident flight departed.

A witness, located about 1 mile north of the accident site, reported that he observed “heavy fog” in the area at the time of the accident and he estimated the visibility to be about 500 ft.

Astronomical conditions indicated the accident occurred right after the conclusion of civil twilight, which occurred at 1726. Sunset occurred at 1657. AIRPORT INFORMATIONThe airplane was not equipped for instrument flight.

The airplane was modified via an FAA-approved supplemental type certificate to utilize automotive gasoline. Investigators were not able to determine how much fuel was on board at the time of departure.

The airplane’s maintenance records were not available for review. WRECKAGE AND IMPACT INFORMATIONThe airplane came to rest in a heavily wooded area on private property. The area was composed of various deciduous trees about 50 ft tall and a collapsed and abandoned house (the house was collapsed before the accident).

The airplane came to rest, nose down, and created a 6 ft deep by 6 ft wide impact crater. The engine and the propeller were buried in the dirt. There was no postimpact fire or evidence of an explosion. No smell of fuel was present, and no signs of fuel were observed in the wreckage. All major structural components of the airplane were accounted for, and the wreckage was confined to the immediate area around the impact crater. The airplane was destroyed.

Several of the 50 ft trees had broken limbs; however, no trees appeared to have fallen due to an impact with the airplane. The damage to the various trees was consistent with a near-vertical descent through the trees that terminated in the ground.

The accident site was at an elevation of 730 ft above msl.

Flight control continuity was established from the control surfaces to inboard toward the cabin. Flight control continuity within the cabin could not be established due to the damage sustained.

The left and right fuel tanks were both breached from the accident sequence. The right and left fuel tank caps were found open from the filler opening but remained connected with the chain lanyard. No signs of fuel were found in the fuel tanks. The insides of both tanks were examined, and no issues were noted. No major debris was found within the fuel system that would have inhibited fuel delivery from either tank.

Airframe to engine control continuity could not be determined due to the impact damage. The cockpit area was destroyed along with the various instrumentation.

The engine and engine accessories sustained impact damage. The propeller sustained impact damage that separated the hub and both propeller blades were found separated. The hub sustained several impact fractures. Chordwise scratching was observed on both blades.

Examination of the airframe and the engine did not reveal any preimpact mechanical malfunctions or failures that would have precluded normal operation. ADDITIONAL INFORMATIONSpatial Disorientation

The FAA Civil Aeromedical Institute's publication, "Introduction to Aviation Physiology," defines spatial disorientation as a "loss of proper bearings; state of mental confusion as to position, location, or movement relative to the position of the earth." This document lists flight factors contributing to spatial disorientation: changes in angular acceleration, flight in IFR conditions, low-level flight over water, frequent transfer from VFR to IFR conditions, and unperceived changes in aircraft attitude. This document concludes with, "anytime there is low or no visual cue coming from outside of the aircraft, you are a candidate for spatial disorientation."

The FAA's Airplane Flying Handbook, FAA-H-8083-3C, describes some hazards associated with flying when the ground or horizon are obscured. The handbook states, in part:

The vestibular sense (motion sensing by the inner ear) in particular tends to confuse the pilot. Because of inertia, the sensory areas of the inner ear cannot detect slight changes in airplane attitude, nor can they accurately sense attitude changes that occur at a uniform rate over a period of time. On the other hand, false sensations are often generated, leading the pilot to believe the attitude of the airplane has changed when, in fact, it has not. These false sensations result in the pilot experiencing spatial disorientation. MEDICAL AND PATHOLOGICAL INFORMATIONAn autopsy of the pilot was performed by the Arkansas State Crime Laboratory in Little Rock, Arkansas. The autopsy report was reviewed by the NTSB Investigator-In-Charge. The cause of death was multiple blunt force injuries

Data Source

Data provided by the National Transportation Safety Board (NTSB). For more information on this event, visit the NTSB Records Search website. NTSB# CEN22FA082