This article is the first in a regular series where we will examine accident reports. But we hope to do something different here at Air Facts. Instead of just proclaiming Pilot Error and assuming “it couldn’t happen to me,” we hope to use the NTSB reports to become safer pilots. The question we’ll pose each time is: “what will I change about my flying after reading this report?”
The phrase is so overused that it’s become a cliche: aviate, navigate, communicate. The clear suggestion is that flying the airplane is much more important than messing with the GPS or telling Air Traffic Control about your problems. But while all pilots hear this advice from day one of flight training, the accident record shows that it’s hard to do when something goes wrong.
It sounds so simple: full power, pitch up and climb. What could possibly go wrong on takeoff, assuming the engine keeps running? The truth is, an awful lot, as a Cirrus accident from 2013 makes clear. We are at our most vulnerable just after takeoff, with little altitude or airspeed but lots to do in the cockpit. Throw in bad weather or dark skies and things can get overwhelming in a hurry.
The checkride is a time of transition, when new pilots go from the clearly defined instructor-student relationship to the much fuzzier examiner-applicant relationship. Who’s in charge? The simple answer is the applicant, but an accident from late 2013 shows how tricky this question can be in real life.
According to Hemingway, a man goes bankrupt gradually, then suddenly. The same could be said of the way pilots crash airplanes: a series of small mistakes slowly build up until a final mistake suddenly ends the flight. A 2009 Pilatus PC-12 accident in Montana is a tragic example.
Many pilots get complacent when they’re in ATC’s warm embrace, assuming that terrain, weather and traffic concerns are being handled by the person in a dark room. But a chilling accident report from 2010 offers an important reminder that controllers can make mistakes.