Accident Details
Probable Cause and Findings
The pilot's loss of airplane control during a missed approach in instrument meteorological conditions due to spatial disorientation. Contributing to the accident was the pilot's inadequate preflight and inflight weather planning which resulted the pilot's selection of an unsuitable alternate airport, and the Civil Air Patrol's inadequate flight release procedures and inadequate oversight of the flight.
Aircraft Information
Registered Owner (Historical)
Analysis
HISTORY OF FLIGHTOn February 1, 2016, about 1945 central standard time, a Cessna 182T, N784CP, was destroyed when it impacted trees and terrain during a missed approach to Mobile Regional Airport (MOB), Mobile, Alabama. The air line transport pilot and private pilot were fatally injured. The airplane was registered to and operated by the Civil Air Patrol (CAP) under the provisions of Title 14 Code of Federal Regulations (CFR) Part 91. Dark night instrument meteorological conditions prevailed, and an instrument flight rules (IFR) flight plan was filed for the positioning flight, which departed from Louisiana Regional Airport (L38), Gonzales, Louisiana, about 1830, and was destined for Mobile Downtown Airport (BFM), Mobile, Alabama.
The accident flight was the final leg of a 300-nautical mile (nm), three-leg "compassion flight;" the purpose of the flight was to transport a passenger from Florida to her home in Louisiana. The pilots departed BFM about 0930 on the day of the accident and flew to Northwest Florida Beaches International Airport (ECP), Panama City Florida. While at ECP, the pilot contacted the flight release officer (FRO) to inform him that their departure would be delayed about 2 1/2 hours due to a problem with the airplane that was delivering the passenger to ECP. After the passenger arrived, the flight departed ECP for L38 about 1500.
According to the owner of the fixed base operator (FBO) at L38, who was also a CAP member, he saw the pilots in the lobby of his FBO. Noting that they were in CAP uniforms, he introduced himself, asked where they were from and their purpose at L38, and learned they were from Mobile, Alabama. About 1 hour earlier, the FBO owner had returned from a flight along the southeastern coast of Louisiana. He told the accident pilots that he had encountered several patches of sea fog moving inland from the coastal area between the mouth of the Mississippi River and Galliano, Louisiana. He noted it was unusual weather for Louisiana; most of the area was clear with visibility greater than 10 statute miles (sm), and the fog he encountered was very low to the ground with tops about 600 ft above ground level (agl) with no other associated weather. He described the fog patches as "wooly blankets" slowly moving across the ground.
The FBO owner was concerned about the accident pilots flying at night given the potential for fog and offered them a courtesy car and assistance with obtaining accommodations for the night. The crew acknowledged his concern about the weather but wanted to return to BFM in time for their CAP meeting and before the fog set in. At 1833, the flight which was operating under the call sign "CAP 184," departed L38, contacted air traffic control (ATC), and was issued an instrument flight rules clearance to BFM.
About 1924, the pilot indicated to ATC that he wanted to change the flight's destination to MOB. ATC cleared the flight to MOB and issued the flight incremental descents from its cruise altitude.
About 1931, the approach controller verified that the pilot had received the current weather conditions at MOB. About 1935, the controller issued the airplane a right turn to intercept the localizer course and cleared the flight for the ILS RWY 15 approach.
At 1936, the approach controller issued alternate missed approach instructions to climb to 2,000 ft and maintain runway heading. The pilot acknowledged, and the controller subsequently instructed the pilot to contact the MOB tower controller. The pilot checked in with the tower controller, who issued the runway visual range (RVR) for runway 15 and cleared the flight for landing. The pilot acknowledged, and the tower controller issued the wind conditions and updated runway 15 RVR.
At 1937, the approach controller advised the tower controller that the pilot had been assigned to fly runway heading in case of a missed approach, and stated that, "he sounds a little shaken so just be careful with him."
At 1944, the pilot declared a missed approach. Radar data indicated the airplane was at an altitude of about 500 ft msl, (300 ft agl) about that time and had begun a slight right turn away from the localizer course. The tower instructed the pilot to maintain 2,000 ft and verified that the flight had been instructed to fly runway heading in the event of a missed approach. The pilot responded, "affirmative." The tower controller subsequently noticed that the airplane was not climbing and reissued instructions to climb to 2,000 ft; the pilot acknowledged; no further transmissions were received from the accident airplane. The airplane continued the right turn and descended to an altitude about 300 ft msl (about 100 ft agl), then climbed to 400 ft msl. The final radar return, at 1944:45, showed the airplane about 300 ft msl.
At 1945, the tower controller informed the approach controller that radar contact with the airplane was lost.
An airline pilot reported that he was operating a "turn" into and out of MOB on the night of the accident. He stated that MOB was under visual conditions when his flight landed; however, during the 23 minutes his airplane was at MOB before its subsequent departure, conditions deteriorated to about 2,000 ft RVR. His flight was cleared to taxi to the runway without visual contact from the tower, and visibility was between 2,000 and 2,400 ft when the flight departed runway 15. After departure, he reported to the control tower that the top of the fog layer was 500 ft msl, above which were visual conditions.
After contacting the departure controller, he could hear CAP 184 being vectored for the ILS 15 approach at MOB. Reaching 10,000 ft, he elected to monitor the approach/tower frequency to listen to CAP 184. He monitored every radio transmission up to the missed approach by CAP 184, followed by several short static transmissions on the tower frequency. PERSONNEL INFORMATIONComposition of CAP aircrew varied in number and qualifications depending upon the assignment. A typical aircrew was made up of a mission pilot, mission observer, and mission scanner.
According to CAP, both pilots were members of the Alabama Wing's Mobile Composite Squadron. The airline transport pilot was acting as the mission pilot (pilot-in-command), and the private pilot was acting as mission scanner (additional crew member).
Mission Pilot
According to Federal Aviation Administration (FAA) and CAP records, the 67-year-old mission pilot held an airline transport pilot certificate with a rating for airplane multiengine land, with commercial privileges for airplane single-engine land and sea, airplane multiengine sea, rotorcraft helicopter, rotorcraft gyroplane, and glider. He also held a flight instructor certificate with ratings for airplane single- and multiengine, instrument airplane, rotorcraft helicopter, rotorcraft gyroplane, and glider. Additionally, he held a ground instructor certificate with a rating for ground instructor instrument.
He joined CAP in September 1991 and held the rank of major. He was qualified as a CAP examiner, check pilot, instructor, command pilot, and tow pilot, and was qualified to operate several models of airplanes within CAP. His most recent application for an FAA second-class medical certificate was dated October 14, 2015, with a restriction to have available glasses for near vision. Records indicated that he had accrued about 11,000 total hours of flight experience, about 120 hours of which was in the previous 6 months. The pilot's logbooks were not recovered for review.
Mission Scanner
According to FAA and CAP records, the mission scanner held a private pilot certificate with a rating for airplane single-engine land. He joined CAP in November 2015 and held the rank of second lieutenant. He was qualified in general emergency services and as a mission scanner. His most recent application for an FAA third-class medical certificate was dated November 5, 2015. Records indicated that he had accrued about 80 total hours of flight experience. AIRCRAFT INFORMATIONThe accident airplane was a single-engine, high-wing airplane of conventional metal construction. It was powered by a fuel-injected, normally aspirated, air-cooled, six cylinder, 230 horsepower, Lycoming IO-540-AB1A5 engine, driving a three-bladed constant speed McCauley propeller.
Aircraft Information File
According to CAP, the aircraft information file (AIF) was normally carried in the airplane. The AIF contained all applicable inspections, equipment evaluations, and worksheets. The AIF was not recovered from the wreckage and was likely consumed in the postimpact fire. Computerized records provided by CAP indicated that an overhauled engine was installed on October 6, 2015, at 2,000.3 total hours of operation. The most recent annual inspection was completed on November 20, 2015, at 2,021.9 total hours of operation. After the airplane's most recent flight on January 31, 2016, it had accrued 2,082.6 total hours of operation.
Avionics and Flight Instrumentation
The airplane was equipped with a Garmin G1000 avionics suite that comprised of two liquid crystal displays; one acted as the primary flight display (PFD), and the other acted as a multifunction display (MFD). It also included an integrated communications panel mounted between the two displays.
The PFD showed the basic flight instruments, such as the airspeed indicator, altimeter, heading indicator, and course deviation indicator. A small map called the "inset map" could be enabled in the corner. When an instrument approach was loaded and activated, the PFD would display glide slope and localizer information. The PFD could also be used for entering and activating flight plans, and had a "reversionary mode," which was capable of displaying all information shown on the MFD. This capability was provided in case of an MFD failure.
The MFD typically showed a moving map on the right side and engine instrumentation on the left. Most of the other screens in the G1000 system we...
Data Source
Data provided by the National Transportation Safety Board (NTSB). For more information on this event, visit the NTSB Records Search website. NTSB# ERA16FA100