April 20, 2011
Aeronautical Decision Making Skills Put to the Test
As part of the FAA Wings program I recently took and completed the "Art of Aeronautical Decision Making" online course. The FAA defines Aeronautical Decision-Making as a "Systematic approach to the mental process of evaluating a given set of circumstance and determining the best course of action." More practically they use a framework for ADM and risk management: Perceive - Process - Perform.
- PERCEIVE the "given set of circumstances" for your flight
- PROCESS by evaluating their impact on flight safety
- PERFORM by implementing the best course of action
AOPA's Air Safety Foundation uses "Anticipate, Recognize, Act". Both promote identifying an issue, determining a plan to mitigate or eliminate risk then putting that plan into action. ASF says "...the thing that seems to cause pilots the most difficulty -- is recognizing potential hazards and taking timely action to avoid them."
With every flight, pilots get a chance to use their ADM skills. However, I did not anticipate the level to which these skills would be used when a fellow flight club member invited me to join him for a flight in his Columbia 400 (now called the Cessna 400). The mission was to fly from Chicago to Miami University in Oxford, OH (my alma mater) to pick up his daughter and bring her back to Chicago. He was planning to file an IFR flightplan and use supplemental oxygen allowing us to fly at 18,000 feet, more than double what I typically cruise at. I figured this flight would be a great learning experience for me, having never flown in a Columbia 400 or having much experience with instrument flight plans. Little did I know what a great learning experience this flight would become.
About forty-five minutes from our destination airport cruising along at FL180 and enjoying a 100 knot tailwind that was helping us achieve a 290 knot ground speed, Ray and I felt a hiccup in the engine and what felt like a short-lived decrease in power. We looked at each other than quickly switched the G1000 Multi-Function Display (MFD) engine page to check for any anomalies. There were no red flags As we were doing that the issue replicated itself. At that point we agreed an issue might be imminent and that he would continue to fly the plane and I would take over the radios if an emergency developed. We knew altitude was on our side and we agreed on an airport we could safely glide to while we troubleshooted the issue. Unfortunately, we had not identified a likely cause when the issue happened twice more in short succession. Each time we were seeing manifold pressure decrease with the hiccup and we noticed the oil temperature was lower than normally expected but still no clear cause or resolution presented itself.
Despite that we had a specific mission for this flight, "to pick up his daughter", we agreed there was a significant risk at hand and that we would be best to troubleshoot this issue on the ground and have a mechanic checkout the engine. It would have been easy for Ray to have stayed in "Mission" mode or to be swayed by Get-There-Itis and keep pushing through. But, we are both all too familiar that too many pilots have lost their lives or their aircraft with such decisions.
Without thinking about it we had just completed Perceive and Process in the FAA's Solution and Recognize in the Air Safety Foundation's thought process. Now it was time to Act or Perform. We agreed now was a good time for some Crew Resource Management (CRM) so Ray continued to focus on flying the plane while I took over responsibilities for radio communications. We informed Air Traffic Control that we wished to divert to Delaware County Airport in Muncie, IN. As we switched over to the Delaware County Tower the controller was aware we had been experiencing some engine irregularities and radioed "Columbia N262RK are you declaring an emergency?", a phrase no pilot wants to hear. I was relieved to be able to respond "Negative, we are not declaring an emergency and we have the runway in sight." A few minutes later we were safely on the ground.
A few years ago I made a precautionary diversion due to deteriorating weather conditions, this was the first diversion related to a mechanical malfunction but proved to be my best example in my flying experiences of appropriate use of Aeronautical Decision Making skills. A few days later I learned the mechanics determined the issue was caused by pin size holes in an exhaust host to the engine manifold, which I guess is common in turbo planes. The plane was not in imminent danger but I believe we made the right decision mitigating the risk.
A wise person once said "the difference between an ordeal and an adventure is your attitude" and on that day we had the right attitude and enjoyed our afternoon at the quiet Muncie airport enjoying a meal at Kacy J's Airport terminal restaurant while we waited for the cavalry. Marc, the Leading Edge Flying Club President, offered to fly down in the club Cirrus SR20 to help us complete the mission. As a result I got another new experience out of the day. It was my first time flying in the Cirrus SR20 which Marc let me fly for much of the short flight from Muncie, IN to Oxford, OH. I enjoyed a brief visit to Oxford before we turned for home. With four passengers and some baggage we had to manage fuel and make a fuel stop in Lafayette, IN before successfully completing the trip back to Chicago.
Although the flight did not go as planned, I had a great day of flying and aviation camaraderie none the less. Below are some photos from the day.