Checklist Template

It is worthwhile to note that an FAA approved checklist is provided for many aircraft, certainly including the 182RG – it’s in the POH. That approved checklist has been found to meet all of the certification requirements at the time the plane was manufactured. I agree that there may be merit in adding items which are directly relevant to that plane (like avionics not available/installed on the factory plane, or a landing gear system change). This should be done as an approval activity associated with the installation of the equipment. Otherwise I resist the idea of non approved checklists. Were I to be presented with a non approved checklist, I would set it aside in favour of the approved checklist in the flight manual/POH.

If I were to have an incident/accident while flying an airplane, and that event were to be traced to my using a non approved checklist, I’d have a really difficult time explaining why I had decided to not use the approved checklist (procedures), in favour of a home made one. Perhaps, if I were to demonstrate that the home made one was an exact reproduction of the original Cessna checklist, other than for the addition of an avionic item, I might be able to justify it, but I really would rather not take that chance, and go to that effort, if an approved checklist is available. Missing avionics is rarely a safety item, it’s just embarrassing.

A checklist is not an instruction sheet on how to fly the plane, it is a mechanism a pilot may use to assure that they are flying the plane as the manufacturer intended. It need not, and should not contain expected outcomes of the items – a competent pilot should already know these! A very wordy checklist will either not be properly used, or if properly used, will end up being misused, when it is so long that the pilot cannot complete a section in one session, and has to keep starting again from the beginning, when interrupted by a flying task.

My FAR Part 23 certified amphibious flying boat has an FAA approved (and required) checklist, which, for land and water operation, is a total of 31 items long, and is a total of
87 words, start to finish. This includes landing gear operation, water rudder, and constant speed propeller operation. It’s short such that it is a placard on the instrument panel. The portion of the checklist which is used in flight is less than half of this length.

I consider the Cessna checklists to err to the wordy side too, though not to the point of being a problem. I just wonder if I need a checklist item which reads: “Elevator control — LIFT NOSEWHEEL at 50 KIAS”. Ah, yeah, if I want to fly, I’m going to have to use the elevator to lift the nosewheel. The indicated airspeed for lifting the nosewheel may be 50 KIAS, or a slower speed, in accordance with Cessna procedures, so making it a checklist item is silly – checklist runaway!

A checklist I wrote, and had approved, for a modified 182 (27 STC mods installed) was a total of 169 words for land operation, or 142 words for water operation. This includes amphibious landing gear, glass cockpit, and reversing propeller, among other systems not common to the 182. The authority and I agreed on the checklist contents, and they met all of the regulatory requirements, more words were not only not required, but actually non compliant. Obviously, the standard 182 landplane checklist would not cover a highly modified 182 amphibian, and you know what, my approved 182 amphibian checklist, is less than half the length (and item count) as Cessna’s checklist for the 182 landplane! So I guess that the FAA was looking for more words back in the day when the 182 was approved, than the authority is now! I think that they have learned that long checklists are more a detriment to safe flying, rather than a benefit.

So, a few specific thoughts about the checklist you created: For manual gear extension, autopilot on? Cessna does not say that (the plane may not be equipped with an auto pilot) I have no recollection of any retractable I have ever flown specifying autopilot on for a gear emergency, though perhaps there is one. Can a manual extension be safely accomplished with the autopilot off? I assure you, yes. The last thing I want during a landing gear problem, is to have yet another system to monitor, which could also be malfunctioning. Your checklist says gear and pump circuit breakers in for a manual extension. The Cessna expanded procedure specifies conditions in which the breaker should be pulled. If a pilot follows your checklist, they may be operating the plane counter to what Cessna has stated in their expanded procedures. Engine fire on the ground: your checklist states twice (8 & 10) to “Keep on” the ignition, followed by 13 “Leave aircraft ASAP”. Cessna says: “Ignition switch off” in this circumstance. A pilot following your checklist, and in the rush to get it done with smoke flowing, misses only one item on your checklist: mixture to idle cut off. So, everyone’s out of the plane, it will most likely be ground handled next, and its condition, as left by the pilot (who missed only one item) is: throttle fully open, mixture rich [by oversight], and mags (ignition on). If someone turns the prop by hand, and the engine starts, that plane is going to do a lot of damage before the carb is empty of fuel. Cessna’s procedure is mags off, to very greatly reduce the chance of an errant start by handling the prop. You use the term “magnetos” associated with “continue cranking”. The starter starts, the magnetos are the ignition source. Magnetos don’t crank. Then later, the term “ignition” is exchanged for the term “magnetos”. Using two terms for the same thing, or using the wrong term for something leads to confusion. Your electrical fire in flight section deviates considerably from Cessna’s procedure.

I have not read all of the checklist you have produced, so there could be other comments. But, as an experienced 182RG pilot, I would stow your checklist, and use the approved one in the POH. In doing so, I would assure that I have met the expectation to operate the aircraft in accordance with approved procedures. Sorry to seem rough on your checklist effort, but you asked. And, it is my job to evaluate and approve, or submit for approval, aircraft modifications, including flight manual supplements and checklists. I take this stuff pretty seriously, and follow guidance and and experience provided to me by the regulator.

I encourage checklists to be approved, thus most easy is to use the one provided with the airplane flight manual/POH. If you think it is missing a safety item (perhaps because of a modification incorporated), that’s certainly worth discussion with the installer or the authority. If your checklist needs to include one or two items unique to the airport environment (like: obtain clearance prior to contacting ground), sure, include that, but otherwise copy the Cessna, or other approved checklist word for word.

I very much agree with the “read out loud” element. Yes! I teach this unrelentingly for amphibian flying, as wheels up landings are required, and there is no warning system for landing gear position in many amphibians.

I think your checklist looks great! Nice to implement some human factors research!

I did something similar for a Cirrus. Basically I removed all the repeat „soft“ items (like seatbelts fastend 5 times) and kept those that can kill you.

It’s a shame manufacturers are not required to provide a realistic checklist for actual use instead of a long garble of text written by lawyers.

Pilot_DAR wrote:

If I were to have an incident/accident while flying an airplane, and that event were to be traced to my using a non approved checklist, I’d have a really difficult time explaining why I had decided to not use the approved checklist (procedures), in favour of a home made one.

That the POH checklist was not fit for purpose? The Cessna checklists/procedures for the 172 features such wonderful items as “TOUCH DOWN – MAIN WHEELS FIRST”.

The main reason for me to make my own checklists was that I fly different aircraft models and want (as long as it is compatible with safe aircraft operation) the checklist items to come in the same order. Obviously I don’t change the contents of the procedures in the POH as in your example about gear retraction.

The checklists/procedures in the POH may be “approved”, but my understanding is that the only part of the POH which regulations say you must follow is the limitations section. AMC1 to NCO.GEN.105(c) does say that you should use the manufacturer’s checklists, on the other hand part-NCO also allows the operator to make its own AltMOCs.

Also, there might not be a useable “manufacturer’s checklist” if the aircraft has been modified. I say “useable” because even if STCs etc come with their own checklists in the POH supplement there will be several checklists that need to be stitched together — and suddenly you have your own checklists anyway.

Pilot_DAR wrote:

So I guess that the FAA was looking for more words back in the day when the 182 was approved, than the authority is now!

So if you have an older aircraft should you still use a checklist that everyone now agrees should have been written in a different manner?

Compare with leaning instructions in old and more recent POHs. They are quite different, still there have been no changes to engines or fuel systems to motivate such differences.

I made my own check list for the TB10, largely based on the POH.

For the PA17 I don’t use one. It doesn’t have most of the items that typically feature on a check list so I just do a sweep left to right across the cockpit. There is certainly no official check list.

I have noted that most GA flyers tend to use check lists as a ‘task list’ (i.e. they actually do the items as they work through it) as opposed to the airline method which seems to be checking off (hence the word checklist) items that are PROB99 already set as required. Perhaps the reason for this is the piston engine power checks – if you include these actions then it almost by definition becomes a task list rather than a check list, and once doing one part of it this way you might as well do it all this way?

I too made my own checklist when I got the TB20 in 2002. It contains stuff on the actual avionics installed, for example. And checklists on things like setting up the autopilot to fly an ILS, with the GPS in OBS mode and showing where the LOC lies.

Thank you Thomas for a great post on a relevant topic.

I don’t understand how an experienced pilot such as Pilot_DAR fails to understand the human factors behind checklist design and doesn’t recognize that the aircraft manufacturers are not necessarily the most well-versed people regarding this topic. Especially if we talk about older aircraft. A manufacturer in the 1970s did not have access to the knowledge posted by Thomas in his OP. So even if the content of the approved original checklist in the POH stays the same (which is not always the case), the design will most definitely and without exception be outdated!
Thus the effort in the OP is commendable!

thomas_witt wrote:

The InDesign Source File is located here: cdn.thomas-witt.com/checklist-template.indd (It’s released under a Creative Commons License CC BY-NC-SA 4.0)

Is it possible to export it to a file useable for Apple Pages?

When I learned to fly many pilots around me flew without checklists.
I was never comfortable with that and always used one.
After a year or so on the same aircraft I too became familiar enough to not require a checklist but recognised quite quickly that I definitely was capable of a cock-up.
So I decided my safest option was a cut down ‘essential items’ checklist incorporating everything in a way that I wouldn’t start to second guess the list and use it reliably.
Human factors taken into consideration included specifically having 1 item per line and a careful use of block capitals.
I belive this inreased my overall safety significantly.
I use an aftermarket Cessna list now but again am picking through it where stuff isn’t relevant.
How many sections cover the same ground. This is where you could begin to skim and miss something.
I shall be creating my own version again soon.