Murphy’s (real) law seems to be that we often succeed despite poor procedures and sloppy execution (luck). It is only the painful failure that stimulates reflection and results in learning; ouch! In most cases, “lucky success” actually reinforces and “normalizes” questionable procedures and activities so they persist (no real learning). Popular online stupidity provides an additional catalog of “leveraged luck.” Just because some wild act worked once (or for one person in a well-rehearsed YouTube environment) does not mean it is a good idea or solid procedure for us (please watch those “fail” videos too).
Humans are “learning machines” and we input everything despite our best intentions to “unsee” some content. But this “continuous input” should really have analysis and filtering or bad habits can easily get embedded in our operating system – coded as “useful/acceptable.” Uncorrected bad habits lie dormant, like viruses, to surprise us at the worst times e.g. “what was I thinking?” Reflective analysis is the proper antidote; a skill every pilot must learn and practice for safety. The military version of this same process is an after-action report.
Challenge and adventure are what makes flying so addictive. Pilots are very practical, straight ahead, hard chargers, and enjoy overcoming obstacles. Aviation requires positive, time-critical decisions in a real-world, high-stakes environment. However, learning and growing the pilot and educator toolkit of resources safely requires reflection. This process involves insisting always on a quiet, thoughtful time for a review and analysis. Reflection has to happen soon after every active flight. “Reflective analysis” is the heart of improvement and positive change. Reflection requires asking questions of ourselves: “How and why did this action work?” “Was my success (or failings) a result of skill or luck?” “Am I normalizing some non-standard procedure that just happened to work (luck)? It is a huge (but very human) mistake to validate procedures based on results alone (normalizing). Just because something worked (for us or for others) is not a reason to accept and use a procedure.
Because the flight environment is time-critical and always in motion, pilots often function on the level of embedded, automatic “scripts.” These stored routines come from prior hours of hard training and review. When facing unique and rapid challenges, a pilot often has to punt, choosing the “less bad,” reflexive actions guided by previous experience but with no clear script. (A previous blog covered “satisficing,” which is the heart of aeronautical decision-making) Careful after-action analysis of these actions that occurred “in the moment” builds the master pilot and educator.
This contrast of “regular day, plain vanilla” missions vs “off the wall challenges” is profiled in Gary Kline’s excellent book “Streetlights and Shadows.” Dr. Klein argues for a precise script – think checklist/SOP – when the situation is predictable (Streetlight) and inspired and flexibility when “all bets are off” and no rulebook applies (Shadows). The latter would be the Sioux City DC-10 or the Miracle on the Hudson response; they never wrote a checklist for these situations. The key to safety is defining these different worlds and applying the correct formula. “Going cowboy” is inappropriate to meet the demands of an ordinary day where checklists and procedures are the proper guidance.
Reflection is the antidote to “normalizing” or “regulatory drift.” Celebrating mere success might just memorialize LUCK and create permission to lower performance standards when adopting new procedures. This process was the cause of both of NASA’s shuttle accidents where a deviation from protocol was accepted as “normal procedure” due to the lack of any immediate negative consequences (they got “lucky”). In these cases, when the luck runs out we experience the shock and surprise of our inadvertent violation of proper safety standards (“What were we thinking?”)
After every flight spend a moment and review your actions. Did they meet standard SOPs and regulatory standards? Were the successes of the flight a result of skill – or just luck? The debrief every CFI does with pilots-in-This process should become a habit for every pilot when they achieve certification. To make master pilots, every CFI must encourage and embed this habit into every new pilot. After every flight ask yourself; “Was our success a result of skill and knowledge correctly applied or was I lucky?” and adjust accordingly. Fly safely out there (and often). You’ll ive longer and fly more.
Join SAFE and get great benefits like 1/3 off ForeFlight and your membership supports our mission of increasing aviation safety by promoting excellence in education. Our FREE SAFE Toolkit App puts required pilot endorsements and experience requirements right on your smartphone and facilitates CFI+DPE teamwork. Our CFI insurance was developed by SAFE specifically for CFIs (and is the best value in the business)
The “other” way of describing this is the tried and true “normalization of deviation”. One gets away with the deviation from standardized actions, e.g. skipping checklist items, and nothing happens. And nothing happens and nothing happens until you die. I do check rides for a volunteer organization and I absolutely demand that the check list be followed or the examinee fails the ride. Usually before we even get in the airplane. Rigid? Yup. I don’t want to have to stand before a board to explain why the pilot I just signed off is dead.
Engaging piece on the importance of reflective analysis in aviation! The challenges of flying indeed require constant learning and adaptation. In this context, the Gibbs Reflective Model seems to be an invaluable tool for pilots. The model encourages individuals to delve into their experiences, question their actions and outcomes, and differentiate between skill-based successes and those driven by luck. It’s an excellent way to avoid normalizing non-standard procedures that may have worked once but could be hazardous in the long run. By applying the Gibbs Model (https://productive.fish/blog/gibbs-reflective-cycle/), pilots can enhance their skills, improve safety measures, and ensure continuous professional growth. Keep up the great writing!
Thank you for the great lead on reflective analysis. My blog article was largely derived from personal experience ofver years of flying (and learning). We learn best from after-action analysis in a quiet space, and only in this manner avoid normalizing. I now have a robust paradigm to link that too; thanks so much!