ASN Wikibase Occurrence # 276312
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Tuesday 8 March 2022 |
| Time: | 18:46 |
| Type: |  Cessna 182Q Skylane |
| Owner/operator: | Private |
| Registration: | N182XT |
| MSN: | 18266723 |
| Year of manufacture: | 1979 |
| Total airframe hrs: | 3413 hours |
| Engine model: | P. Ponk O-470-50 |
| Fatalities: | Fatalities: 2 / Occupants: 2 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | Panama City, FL -
 United States of America
|
| Phase: | Approach |
| Nature: | Private |
| Departure airport: | McMinnville-Warren County Airport, TN (RNC/KRNC) |
| Panama City-Northwest Florida Beaches International Airport, FL (ECP/KECP) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
On 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.
The pilot and passenger departed during the middle of the day for a nearly 7-hour instrument flight rules cross-country flight with one fuel stop. During the fuel stop, the pilot reported to an airport employee that he was trying to time his flight to arrive at the destination between two thunderstorms. The flight departed and entered the destination airport area at night without incident. Air traffic control cleared the pilot for a straight-in instrument landing system approach and advised him that the cloud ceiling was 200 ft above ground level, which was the decision height for the straight-in instrument landing system approach the pilot was about to perform.
The pilot told the controller that the airplane was established on the final approach course. However, between the initial approach fix and final approach segment the airplane’s altitude and flightpath showed deviations, and the pilot was cautioned of those deviations by controller. Additionally, the airplane crossed the initial approach fix about 500 ft below the specified crossing altitude and about 700 ft below the expected altitude at the final approach fix. As the airplane continued in the final approach segment, continuous deviations to the left and right of course occurred. The airplane subsequently descended below the decision height for the approach and impacted heavily wooded terrain about 1.55 nautical miles from the runway threshold in a 18°-to-20° descent.
The wreckage was highly fragmented, but all major components of the airplane were located in the debris path. No evidence indicated any preimpact mechanical malfunction or failure of the airplane. The evidence also indicated that the engine was producing power at the time of impact.
Prior to the accident, the airplane had ongoing autopilot altitude-hold control issues despite several recent maintenance corrective actions. The pilot was aware that the autopilot issue persisted, and he told a friend a few days before the accident flight that he felt comfortable hand flying the airplane during the long cross-country flight. The investigation was unable to determine whether the autopilot was activated during the approach, and testing of the autopilot system could not be performed due to the significant impact damage to the airplane and autopilot components. Furthermore, a safety pilot who had flown with the accident pilot reported that it was typical of the pilot to turn off the autopilot for instrument approaches and hand fly the airplane. Thus, it is likely that the pilot flew the accident approach without the autopilot engaged.
The weather observed at the destination airport had deteriorated significantly after the pilot departed for the last leg of the flight, and the weather was worse than the expected forecast conditions. During the approach, the controller advised the pilot of the low ceiling and visibility and advised that other nearby airports were reporting better weather conditions. The pilot responded that he would continue the approach. Review of the weather at the alternate airport for the flight, which was about 25 to 30 minutes away from the planned destination, found that visual flight rules conditions were occurring during the time surrounding the accident. It is likely that had the pilot discontinued the instrument approach and diverted to the alternate airport after the approach had become unstable, and after having been warned of his flightpath deviations, the accident would have been avoided.
Review of the pilot’s logbook found that he had logged less than 2 hours of night experience during the 12 months preceding the accident and had logged no night flights in the 90 days before the accident. The pilot had logged 11 instrument approaches in the 6 months that preceded the accident. The pilot’s total actual instrument experience was 32 hours, but only 2.5 hours of this time was logged as night actual instrument experience. In addition, the pilot was disapproved twice when testing for his instrument airplane rating because he had become distracted and lost situational awareness and had a full-scale deflection on the glideslope during an instrument approach. Although the pilot was approved for an instrument rating on his third attempt, he likely did not possess the experience or ability to successfully complete the night instrument approach in low instrument meteorological conditions.
Probable Cause: The pilot’s deviation from the final approach course during a night instrument approach with low instrument meterological conditions, which resulted in an impact with heavily wooded terrain. Contributing to the accident was the pilot’s decision to continue the approach after being warned of his flightpath deviations and his lack of experience in instrument conditions at night.
Accident investigation:
 |
|
Sources:
https://www.wjhg.com/2022/03/09/airplane-goes-missing-two-miles-ecp-airport/
https://data.ntsb.gov/Docket?ProjectID=104744
https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=182XT
https://flightaware.com/live/flight/N182XT/history/20220308/2230Z/KRNC/KECP
https://globe.adsbexchange.com/?icao=a14a39&lat=30.412&lon=-85.837&zoom=13.0&showTrace=2022-03-09
https://flightaware.com/photos/view/183613-b019cf0ca963c9edef463237ebfc48f4269fb010/aircrafttype/C182 (photo)
Location
Images:
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 09-Mar-2022 04:28 | Captain Adam | Added |
| 09-Mar-2022 06:43 | RobertMB | Updated [Time, Aircraft type, Registration, Cn, Operator, Other fatalities, Source, Narrative] |
| 09-Mar-2022 07:56 | RobertMB | Updated [Source] |
| 09-Mar-2022 13:30 | johnwg | Updated [Time, Registration, Total fatalities, Total occupants, Phase, Departure airport, Source, Damage, Narrative, Category] |
| 09-Mar-2022 20:52 | RobertMB | Updated [Time, Location, Phase, Source, Narrative] |
| 09-Mar-2022 21:02 | aaronwk | Updated [Phase, Narrative] |
| 10-Mar-2022 02:02 | johnwg | Updated [Phase, Source, Narrative] |
| 10-Mar-2022 07:06 | aaronwk | Updated [Phase, Narrative] |
| 11-Mar-2022 02:25 | johnwg | Updated [Time, Phase, Narrative] |
| 14-Mar-2022 08:43 | The2ndBaron | Updated [Phase] |
| 22-Mar-2022 22:18 | Captain Adam | Updated [Time, Source, Narrative, Category] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation