ERA22FA149 · Cessna 182Q
Cessna 182Q · Accident: collision with terrain/object (non-CFIT) on approach
From Warren County Memorial Airport (RNC) to ECF · Panama City, FL
Event
- NTSB case
- ERA22FA149
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 2 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Instrument Meteorological Cond
Cessna 182Q
- Aircraft type
- Cessna 182
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N182XT
- Operator
- Slattery Donald J
- Onboard fatalities
- Unknown
- Route
- From Warren County Memorial Airport (RNC), McMinnville, TNTo ECF · Panama City, FL
- Aircraft age
- About 43 years (built 1979)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Approach · IFR final approach
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Collision with terrain/object (non-CFIT)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Action/decision
- Personnel issues › Experience/knowledge
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA22FA149
- Event ID
- 20220309104744
- Case number
- ERA22FA149
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: local date, investigation status, coordinates, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2022-03-09.
- API snapshot SHA-256: f34d9582d61f250579ad011aaa571324804f8f986a90be6e7e25130a1cef2066; retrieved 2026-09-15T07:41:52.895Z.