In the last article, we spoke about checklists, how they can be used objectively and subjectively in a risk management perspective, how checklists touch on the critical items that if skipped or forgotten could spell disaster. We illustrated how the use of checklists is not about ticking boxes, but can be used to push security culture, teamwork, and discipline. We started to discuss how some checklists need to be practiced.
In my previous article, we discussed how some of the aviation and cyber security regulations have come about, and what are some of the driving factors. Typically it is a loss of some sort; most of the aviation regulations are borne of the loss of life. The pre-flight checklist is no exception.
I have been an IT and security professional for almost my entire adult life. I started off my career as a network engineer and fell into being a security engineer fairly quickly. It started by adding a firewall certification, then I added intrusion detection and prevention. The areas of security continued to grow; adding forensics investigations, eDiscovery, project consulting, and so much more. In the project consulting, we focused on ensuring the risk level of a project was within acceptable levels for the organization. I have been the top of the cyber security organization in my last three roles; but I've wanted to be a pilot for as long as I can remember.
In 2018, I became a certificated pilot and in 2019 an advanced and instrument ground school instructor. I recently finished teaching a formal ground school class to about 15 students of differing skill levels, ages, and goals for their piloting careers.