Accident Details
Probable Cause and Findings
The student pilot’s continued visual flight rules flight into night instrument meteorological conditions, which resulted in spatial disorientation and a rapid uncontrolled descent into terrain. Contributing to the accident were the self-induced and external pressures that likely influenced the pilot’s decision to both initiate and continue the flight.
Aircraft Information
Registered Owner (Historical)
Analysis
HISTORY OF FLIGHTOn April 20, 2021, at 2052 central daylight time, a Piper PA-28RT-201T airplane, N4303G, was destroyed when it was involved in an accident near Brownsville, Tennessee. The student pilot and passenger were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.
According to the student pilot’s flight instructor, he and the student met mid-morning to discuss a solo cross-country flight from Pearland Regional Airport (LVJ), Houston, Texas, to Kyle-Oakley Field Airport (CEY), Murray, Kentucky. The student told the instructor that he needed to visit his father, who had recently been admitted to the hospital. The flight instructor stated that “it was supposed to be a daytime flight,” expecting the student to depart no later than 1300 or 1400 due to the weather coming in later in the evening.
Review of Federal Aviation Administration (FAA) automatic dependent surveillance – broadcast (ADS-B) data found that the student pilot departed LVJ at 1720, proceeded southbound for a few minutes, then northeast on an en route course that was generally consistent with a direct route of flight to CEY for about 3 hours and 30 minutes at altitudes between about 7,000 ft mean sea level (msl) to 9,000 ft msl. The course showed little deviation until the final 2 minutes of flight.
Review of air traffic control communications provided by the FAA revealed that in the final few minutes of the flight, the pilot was communicating with Memphis Air Route Traffic Control Center (Memphis Center) while receiving visual flight rules (VFR) flight-following services. About 2 minutes and 30 seconds prior to radar contact being lost, the pilot stated to the controller that he was flying at 7,500 ft msl, his destination was CEY, and added that he was planning to “start my descent now” and he was going to make it a “gradual descent.”
The controller responded by providing the CEY altimeter setting and advised the pilot of moderate precipitation “starting now lasting all the way to the [destination] airport.” The controller further stated, in part, that “everything between now and [CEY] is on the verge of being i f r [instrument flight rule] conditions. It looks likes ceilings are down around about 1,500 ft most everywhere.”
The pilot responded, “ok affirmative I’m gonna still descend down” to “2,000 3,000 feet to have plenty of clearance for anything that’s not updated on my screen if that’s ok and until I get within 10 miles I’ll drop to my final descent.” The controller responded by advising the pilot to maintain VFR and provided an additional weather observation report for an airport along the route of flight that was reporting IFR conditions. The controller advised that a course to the east may help him remain clear of the weather and advised that McKellar-Sipes Regional Airport (MKL) was still reporting clear skies.
The pilot acknowledged the controller and said he would fly east to stay out of the weather. The controller responded by providing one additional airport reporting VFR conditions that was about 20 miles south of his destination, which the pilot acknowledged. About 35 seconds later, a “mayday” call was announced over the radio. There was no call sign associated with the distress call, nor any further information given with the call. The controller attempted to reach the pilot several times after the mayday call; however, no further communications were received. Figure 1 provides an overview of the final minutes of the ADS-B flight track overlaid with paraphrased controller-pilot communications.
Figure 1. End of flight ADS-B data with controller-pilot communication paraphrased. N4303G is the accident airplane and ‘ZME’ is Memphis Center.
A National Transportation Safety Board (NTSB) performance study reviewed the final few minutes of ADS-B data and found that a descent was initiated at 2051:50. In the subsequent 20 seconds, the airplane slowed from 160 knots calibrated airspeed (KCAS) to 120 KCAS and entered a right turn. The descent then rapidly accelerated, airspeed rapidly increased, and the right turn tightened into a descending spiral.
At 2052:29, the airplane exceeded its never-exceed speed (VNE) of 185 KCAS in the descent, and about 10-15 seconds later, the airplane reached a maximum recorded speed of about 270 KCAS. The final data point was at 2052:46; the airplane was at an altitude of 1,450 ft msl, flying south-southwest about 165 KCAS. The wreckage was located about 1,000 ft from the final reported position at an elevation of about 300 ft msl. Figure 2 provides an overview of this calculated performance information based upon ADS-B data.
Figure 2. End of flight altitude (msl) and calculated groundspeed and calibrated airspeed.
The FAA issued a missing aircraft alert shortly after radar contact was lost. Local authorities discovered the wreckage about 0730 the next morning.
PERSONNEL INFORMATIONAccording to FAA airman records, the pilot was issued a student pilot certificate on August 4, 2019. He was issued a third-class medical certificate on January 14, 2019, which had expired on January 31, 2021. The flight instructor reported that the student told him that he had renewed his medical certificate in February 2021; however, the FAA had no record of such medical examination nor any record the pilot attempted to complete the FAA BasicMed Certification.
Review of the pilot’s logbook found that his first flight was logged on December 5, 2018, and entries continued through October 4, 2020. The logbook showed that, in November 2019, the student completed two cross-country flights between LVJ and CEY. The first flight was a dual instructional flight and the second flight, later in the month, was a solo cross-country flight. A remark in the logbook for the solo flight stated, “cross-country to KCEY but set down KDYR/ Weather.”
The flight instructor provided photocopies of a current 90-day solo endorsement and a cross-country route of flight endorsement for the accident flight that he had given the pilot. He added that he had no knowledge that the pilot planned to depart with a passenger. The instructor reported that the student had not attempted the private pilot aeronautical knowledge test prior to the accident.
AIRCRAFT INFORMATIONAccording to FAA registration records, the pilot purchased the accident airplane in July 2019. A mechanic reported that he performed a routine annual inspection on the airplane in April 2021; however, the airplane’s maintenance records were not recovered during the investigation.
According to the Airplane Flight Manual, Section 2 Limitations, VNE was 193 knots indicated airspeed, or 186 KCAS.
METEOROLOGICAL INFORMATIONA cold front had moved across the area hours prior to the accident, and a low- and mid-level trough was located above the accident site at the accident time, helping to bring clouds and precipitation to the region.
Cloud ceilings at the accident site were indicated by a high-resolution rapid refresh sounding from 1,200 ft above ground level (agl) with reduced visibility due to mist, with cloud tops indicated near 13,500 ft msl based on satellite information. Review of METARs for airports near the accident site supported this satellite and sounding information. The freezing level was near 7,500 ft mean sea level. In addition, strong northerly wind gusting to 24 knots at the surface through 14,000 ft msl was observed.
Review of data from the nearest weather surveillance radar station revealed that airplane’s flight track in the final few minutes of flight approached an area of light precipitation. Figure 3 shows the airplane’s flight track, precipitation, and the accident site.
Figure 3. Overview of the flight track and weather surveillance radar data near the time of the accident
AIRMET advisories Tango and Zulu were valid for the area at the accident time. The AIRMETs warned of moderate turbulence between 8,000 and 16,000 ft msl and moderate icing between the freezing level and 18,000 ft msl.
The nearest TAF to the accident site was McKellar-Sipes Regional Airport (MKL), located 23 miles east of the accident site. About the time of the accident, the TAF called for wind from 340° at 17 knots with gusts to 28 knots, greater than 6 miles visibility, moderate rain showers in the vicinity, broken ceiling at 2,500 ft agl, and overcast skies at 8,000 ft agl.
Review of CEY METARs revealed that, at 2115, the airport was reporting marginal visual flight rule conditions (MVFR) with visibility of 3 statute miles (sm), scattered clouds at 900 ft agl, a broken ceiling at 1,300 ft agl, and overcast clouds at 5,500 ft agl. At 2135, the airport reported IFR conditions of 4 sm visibility, broken clouds at 700 ft agl and 1,300 ft agl, and overcast clouds at 3,500 ft agl. For the next several hours, the airport continued to report IFR conditions.
At 2053, MKL reported 10 statute miles visibility, scattered clouds at 4,700 ft agl, broken clouds at 8,000 ft agl, and overcast clouds at 9,500 ft agl.
According to Leidos Flight Service and Foreflight, there was no record that the pilot filed a flight plan or requested a weather briefing via telephone or online. Review of METARs and TAFs nearby and at the destination airport found that day VFR conditions prevailed throughout the afternoon and early evening.
AIRPORT INFORMATIONAccording to FAA registration records, the pilot purchased the accident airplane in July 2019. A mechanic reported that he performed a routine annual inspection on the airplane in April 2021; however, the airplane’s maintenance records were not recovered during the investigation.
According to the Airplane Flight Manual, Section 2 Limitations, VNE was 193 knots indicated airspeed, or 186 KCAS.
WRECKAGE AND IMPACT INFORMATIONThe wreckage was located partially submerged in a creek and along a muddy ravine in a forest. All major components of the airplane were located within about a 100-ft-long debris path, and...
Data Source
Data provided by the National Transportation Safety Board (NTSB). For more information on this event, visit the NTSB Records Search website. NTSB# ERA21FA189