N182XT

HISTORY OF FLIGHTOn March 8, 2022, about 1846 central standard time, a Cessna 182Q airplane, N182XT, was destroyed when it was involved in an accident near Northwest Florida Beaches International Airport (ECP), Panama City, Florida. The private pilot and passenger were fatally injured. The airplane was operated under the provisions of Title 14 Code of Federal Regulations Part 91 as a personal flight.

According to a family member, the pilot and passenger (his wife) planned a cross-country flight departing from their home airport, Jack Barstow Airport (IKW), Midland, Michigan, with a final destination of Panama City, Florida. Review of Federal Aviation Administration (FAA) Automatic Dependent Surveillance–Broadcast (ADS-B) data revealed that the pilot completed a 10-minute local flight at IKW that concluded about 1118 (1018 eastern standard time). The pilot then initiated an instrument flight rules (IFR) cross-country flight from IKW about 1212 (1112 eastern standard time) and arrived at Warren County Memorial Airport (RNC), McMinnville, Tennessee, about 1503 central standard time, resulting in a total flight time of 3 hours 51 minutes. A fuel receipt showed that, about 1520, the pilot purchased 74 gallons of 100 low-lead fuel. The airplane departed RNC about 1554 and arrived in the ECP area after about 2 hours 45 minutes of flight time.

Review of air traffic control (ATC) communications provided by the US Air Force and the FAA revealed that the flight was in contact with Tyndall Air Force Base. The approach controller informed the pilot that automatic traffic information service information Quebec was current, cleared him to the initial approach fix, and instructed the pilot to cross the initial approach fix at or above 3,000 ft mean sea level (msl). Subsequently, the controller issued an approach clearance for the straight-in instrument landing system (ILS) runway 16 approach. A few minutes later, the pilot confirmed that the airplane was established on the approach, and the controller then instructed the pilot to contact the ECP ATC tower.

The pilot informed the ECP tower that the airplane was inbound on the ILS runway 16 approach. The controller acknowledged the transmission and provided the current weather observation at the airport, which indicated that the wind was from 150° at 6 knots, visibility was 2 statute miles, an overcast ceiling was present at 200 ft above ground level (agl) and the barometric pressure was 29.92 inches of mercury. The pilot stated, “200 overcast we’ll give it [a] try and see if we can get her down.” The controller then issued a landing clearance and offered to turn up the approach lights to the highest setting available. The pilot stated, “affirmative that would be good.” The controller subsequently told the pilot that, if the airplane were able to descend beneath the overcast clouds, the approach lights might be “pretty bright,” and the pilot acknowledged this information.

About 40 seconds later, the controller stated, “I’m receiving a low altitude alert. Check your altitude,” to which the pilot stated “affirmative.” The controller then informed the pilot that the Tyndall approach controller noticed that the airplane’s flight track was deviating to the right of the final approach course and advised the pilot to use caution. The controller again provided the wind and ceiling information, which had not changed from the previous report; the pilot stated “affirmative.” The controller then stated, “there are other airports nearby with better weather conditions.” The pilot replied, “alright we’ll try this down to minimums and go around if need be.”

About 12 seconds later, the controller stated that the airplane appeared to be “drifting a little to the right” and then “well to the right.” No further communications were received from the pilot despite several attempts by the controller to reach him. The controller subsequently alerted airport operations of a possible downed airplane.

Review of the ADS-B flight track in the final approach phase found that the airplane’s course continuously deviated left and right from the initial approach fix to the accident site, which was 1.55 nautical miles from the runway threshold. The airplane’s altitude showed momentary descents and climbs while on final approach. At both instrument approach fixes, OTTOE (initial) and LIVVY (final), the airplane crossed the waypoints below the minimum altitudes prescribed in the instrument approach chart by about 500 and 700 ft, respectively. The final ADS-B data point recorded the airplane at 75 ft msl at a groundspeed of 144 knots and a ground track heading of 130°. Figures 1 and 2 provide an overview of the ADS-B data recorded during the final approach segment.

Figure 1 - Overview of the flight track, final approach course, and accident site.

Figure 2 - Final 6 minutes of ADS-B altitude and groundspeed data overlaid with waypoint information for the ECP ILS runway 16 approach.

The total time en route from RNC to the time that the accident occurred was 3 hours 51 minutes. The total flight time on the day of the accident was 6 hours 53 minutes. PERSONNEL INFORMATIONReview of the pilot’s logbook revealed that he had accumulated 691 hours of total flight time, of which 569 hours were in the accident airplane. He had logged a total of 35 hours of night flight experience and a total of 2.5 hours of night actual instrument flight experience. During the 12 months that preceded the accident, he had logged 13 hours of actual instrument experience; 1.5 hours of night flight experience, 0.5 hours of which was in actual instrument experience; and four night landings. During the 6 months before the accident, the pilot logged 11 instrument approaches. During the 90 days preceding the accident, he logged 51.3 hours of actual instrument flight experience and no night flights. His most recent flight review was competed on June 14, 2021. There was no record indicating that the pilot had landed at ECP within the 3 years before the accident.

The pilot received his instrument airplane rating on June 27, 2019, on the third practical examination attempt. The pilot received a notice of disapproval during two separate practical examination flights (in May and early June 2019). The comments on the first notice of disapproval indicated that the pilot became distracted, lost situational awareness, and improperly managed tasks during partial panel operations. The comments on the second notice of disapproval indicated that the pilot had flown an ILS approach to a full-scale deflection on the glideslope.

According to an individual who had flown with the pilot as a safety pilot during instrument training, the pilot would typically disengage the autopilot and hand fly approaches. AIRCRAFT INFORMATIONAccording to maintenance records and interviews with individuals who had spoken with the pilot before the accident flight, the airplane had a persistent autopilot problem. The autopilot, when engaged and selected to altitude hold mode (ALT HOLD), would begin an altitude oscillation that would eventually reach 1,500 ft per minute in climbs and descents. Disengaging the autopilot had not been an issue. Maintenance records showed autopilot discrepancies and corrective actions from October 2020 to January 21, 2022. The maintenance shop that worked on the autopilot thought that the issue had been corrected, and, on January 31, 2022, the pilot departed with his airplane. The oscillations still persisted, so the pilot brought his airplane back to the maintenance shop on February 14, 2022.

The airport manager at IKW spoke with the pilot 3 days before the accident. She stated that, according to the pilot, he was “chasing an autopilot issue” that was still not fixed. She also stated that the pilot had indicated that he would be completing his planned trip to ECP without the autopilot operating.

In addition to the original autopilot altitude porpoise issue, the pilot reported that he had performed autopilot/trim system troubleshooting, but he did not describe the specific actions he took to the maintenance shop manager. The pilot indicated that the programmer/computer for the autopilot displayed a fault but that the manual elevator trim wheel operation was normal. The pilot did not have an appointment for service, and the shop could not evaluate the airplane at that time; thus, the pilot decided to return to the shop at a later time. No record indicated any maintenance performed after January 2022.

According to a friend of the pilot who spoke with him 3 days before the accident, the pilot stated that he was going to fly to Florida as soon as his airplane was fixed. The friend asked the pilot, “are you comfortable flying without autopilot and single pilot that far?” The pilot responded, “yeah I’ll be fine.” METEOROLOGICAL INFORMATIONAccording to a customer service employee at RNC, the pilot discussed that he was on his way to Florida and was trying to beat bad weather arriving at the ECP area. The pilot explained that he was trying to arrive between two lines of thunderstorms. The pilot appeared to be checking the weather and filing a flight plan on his personal iPad.

According to ForeFlight archived records, the pilot filed an IFR flight plan from RNC to ECP with an alternate of Dothan Regional Airport (DHN), Dothan, Alabama. The flight plan was filed at 1028 eastern standard time (before the first flight leg of the day). The pilot received a standard preflight weather briefing as part of filing the flight plan. No records showed that the pilot received additional weather briefings later that day.

A National Transportation Safety Board weather study reviewed National Weather Service forecast and observation data for ECP and surrounding airports. The weather at ECP at 1453 (while the pilot was on the ground at RNC) indicated the following: wind from 140° at 11 knots gusting to 19 knots, 7-statute mile visibility, and a broken ceiling at 1,800 ft agl. ...