Accident Details
Probable Cause and Findings
The pilot's loss of control while operating in night instrument meteorological conditions as a result of spatial disorientation. Contributing to the accident was the pilot's decision to operate an airplane after consuming alcohol and his resulting intoxication, which degraded the pilot's judgment and decision-making.
Aircraft Information
Registered Owner (Historical)
Analysis
HISTORY OF FLIGHTOn April 15, 2018, at 2054 eastern daylight time, a Cessna 525, N525P, was destroyed after it impacted terrain near Crozet, Virginia. The private pilot was fatally injured. The airplane was owned by a private individual and was being operated under the provisions of Title 14 Code of Federal Regulations (CFR) Part 91 as a personal flight. Night instrument meteorological conditions prevailed at the time of the accident, and no flight plan was filed for the flight, which departed Richmond Executive–Chesterfield County Airport (FCI), Richmond, Virginia, about 2035 and was destined for Shenandoah Valley Regional Airport (SHD), Weyers Cave, Virginia.
According to a friend of the pilot, the pilot had "a couple of drinks" while they were preparing dinner. The pilot left her home about 1930. The pilot's friend thought that the pilot would be going to a hotel because it was getting dark, but FCI security video showed that the pilot arrived at the airport at 2002 and walked to the airplane at 2004. The pilot then walked around the airplane for about 3 minutes, boarded the airplane, closed the main cabin door, and initiated the engine start sequence at 2017. About 2 minutes later, the airplane began to taxi to the departure end of runway 15 and then taxied back to the departure end of runway 33. The takeoff roll began on runway 33 at 2033. The airport security video showed the windsock, which indicated that the wind favored a departure from runway 15. According to an airport line service employee, the airplane departed with a tailwind. The employee also stated that the pilot did not communicate on the Unicom frequency.
According to air traffic control data provided by the Federal Aviation Administration (FAA), a radar target identified as the accident airplane departed FCI and reached a maximum altitude of about 11,500 ft mean sea level (msl) at 2040. The airplane then began to descend and, at 2044, leveled off at an altitude of about 4,300 ft (which was below the minimum safe altitude of 5,700 ft msl for SHD). The airplane remained at 4,300 ft until 2053, when it began a descending left turn. The last two radar returns were 5 seconds apart and showed the airplane at 3,300 ft and 2,800 msl, which indicated that the airplane was descending about 6,000 ft per minute. Radar contact was lost at 2054. Throughout the flight, the pilot did not have any contact with air traffic control.
According to a witness near the accident location, he heard the "screaming of the engines" and then felt the terrain shake when the airplane impacted the ground. He stated that, at the time of the accident, the cloud ceiling was "really low," the winds were moderate, and heavy rain was occurring. PERSONNEL INFORMATIONAccording to FAA airman records, the pilot held a private pilot certificate with ratings for airplane single-engine land, multiengine land, and instrument airplane. In addition, the pilot had a Cessna CE-525S type rating. The pilot was issued a third-class medical certificate on November 30, 2016. At that time, he reported 1,900 hours of total flight experience, of which 25 hours were within the previous 6 months.
According to the pilot's logbook, he had a total of 737.9 hours of flight time, of which 13.5 hours were in the 30 days before the accident. In addition, he reported 1.4 hours of instrument time in the previous 90 days, which included 9 instrument approaches. Since 2014, the pilot had flown 165.4 hours in the accident airplane. According to family members, the pilot flew to Richmond, Virginia, the day before the accident to perform a flight review on the afternoon of the accident date. AIRCRAFT INFORMATIONAccording to FAA airworthiness records, the airplane was manufactured in 1996 and was equipped with two Williams International FJ44-1A engines, each of which produced 1,900 lbs of thrust. According to the maintenance logbooks, the most recent continuous airworthiness inspection was recorded on March 1, 2017; at that time, the airframe had accumulated 3,311.6 total hours of operation.
According to FAA airworthiness records, the airplane was equipped with a multifunction display and a Garmin MX20, which displayed satellite weather information. According to the Garmin MX20 description, the display had a built-in terrain elevation database that color-coded relevant ground features in relation to an aircraft's altitude and could alert the pilot to rising terrain. The MX20 was also integrated with various onboard weather radar, lightning, traffic awareness, and datalink systems that enabled uploading of graphical weather information and Next Generation Weather Radar depictions. METEOROLOGICAL INFORMATIONThe recorded weather conditions at FCI about the time of departure indicated wind from 140° at 12 knots, 10 miles visibility, and broken cloud ceilings at 3,200 and 4,000 ft above ground level (agl).
The 2057 recorded weather observation at Charlottesville-Albemarle Airport (CHO), Charlottesville, Virginia, which was about 13 miles northeast of the accident location, included wind from 020° at 4 knots, visibility 2 ½ miles, rain and mist, broken clouds at 700 ft agl, overcast clouds at 1,500 ft agl, temperature 11°C, dew point 11°C, and an altimeter setting of 29.79 inches of mercury. The remarks section indicated that lightning was detected northeast and south of the airport.
The 2035 recorded weather observation at SHD, which was about 15 miles northwest of the accident site, indicated wind from 350° at 12 knots, 7 miles visibility, moderate rain, scattered clouds at 900 ft agl, broken ceiling at 4,700 ft agl, overcast clouds at 5,000 ft agl, temperature 11°C, dew point 11°C, and an altimeter setting of 29.77 inches of mercury. The remarks section stated that the station had a precipitation discriminator and provided the following information: lightning distant (beyond 10 miles but less than 30 miles from the center of the airport) southeast, 0.29 inch of precipitation since 1955, temperature 11.1°C, and dew point 10.5°C.
The 2035 recorded automated weather observation at Eagles Nest Airport (W13), Waynesboro, Virginia, which was about 12 miles southwest of the accident location, indicated wind from 040° at 3 knots, 7 miles visibility, scattered clouds at 600 ft agl, broken ceiling at 1,600 ft agl, overcast clouds at 4,400 ft agl, temperature 14°C, dew point 14°C, and an altimeter setting of 29.74 inches of mercury. The remarks indicated that the station did not have a precipitation discriminator and provided the following information: 0.14 inch of precipitation since 1955, temperature 13.7°C, and dew point 13.6°C.
According to Lockheed Martin Flight Services, for the accident flight, the pilot did not obtain a weather briefing or use the direct user access terminal service.
According to reviewed radar data, reflectivity values between 25 and 35 dBZ were located above the accident site at 2053 (see figure 1), which corresponded with the surface observation precipitation reports from W13, SHD, and CHO. The reflectivity bands were moving from south-southwest to north-northeast between 2004 and 2103. The reflectivity targets indicated of moderate-to-heavy rain moving northward across the accident site at the accident time.
The accident airplane flew through a thunderstorm line between 2042 and 2047. There were no lightning strikes within 10 miles of the accident site about the accident time.
Figure 1. Radar reflectivity at 2053 with the accident site marked with a black circle, the accident flight track in pink, the airplane's position at 2053 marked with a red circle and the lightning flashes represented by the black dots.
Further, two convective SIGMET advisories were valid for the accident site at the accident time. SIGMET 31E, issued at 1855 and valid through 2055, warned of a line of severe thunderstorms moving from 210° at 40 knots with cloud tops to FL420 (about 42,000 ft) with tornadoes, hail with a size up to 1 inch, and wind gusts to 60 knots possible. SIGMET 36E, issued at 1955 and valid through 2155, contained the same severe thunderstorm information as SIGMET 31E except that the cloud tops were to FL410 (about 41,000 ft).
AIRMETs Sierra, Tango, and Zulu were valid for the accident site at the accident time. The AIRMETs warned of instrument flight rules conditions due to precipitation and mist; mountain obscuration conditions due to clouds, precipitation, and mist; moderate turbulence below FL180 (about 18,000 ft), low-level wind shear conditions, and moderate icing below FL240 (about 24,000 ft).
In addition, there were three urgent pilot reports for the area near CHO within the 2 hours that preceded the time of the accident. All three reports were from Bombardier CRJ-200 airplanes. The reports stated that there was moderate turbulence in the vicinity, and one of the reports stated that the cloud bases were overcast at 1,500 ft msl.
According to the Astronomical Applications Department at the US Naval Observatory, for the area of the accident, sunset was at 1951, and the end of civil twilight was at 2018. Moonrise was at 0644, and the phase of the moon was a new moon at 2157. AIRPORT INFORMATIONAccording to FAA airworthiness records, the airplane was manufactured in 1996 and was equipped with two Williams International FJ44-1A engines, each of which produced 1,900 lbs of thrust. According to the maintenance logbooks, the most recent continuous airworthiness inspection was recorded on March 1, 2017; at that time, the airframe had accumulated 3,311.6 total hours of operation.
According to FAA airworthiness records, the airplane was equipped with a multifunction display and a Garmin MX20, which displayed satellite weather information. According to the Garmin MX20 description, the display had a built-in terrain elevation database that color-coded relevant ground features in relation to an aircraft's altitude and could alert the pilot to rising terrain. The MX20 was also integrated wi...
Data Source
Data provided by the National Transportation Safety Board (NTSB). For more information on this event, visit the NTSB Records Search website. NTSB# ERA18FA127