checklist - ERAU ETA - Embry-Riddle Aeronautical University

2 PA-28R-201 SOP
ERAU CHECKLIST POLICY
A critical element in the development as a professional pilot is in the
training in checklist usage and discipline. Pilot deviations from standard
operating procedures are the number one crew related cause of hull loss
accidents. Many of these accidents and incidents are the direct result of
the improper use of or lack of training in checklist usage. Therefore,
checklist usage and discipline must be emphasized in our “crew”
environment to help ensure safe and efficient flight operations at Embry-
Riddle Aeronautical University and in preparing students for careers as
professional pilots.
All checklists are accomplished by either a “Do/Verify” or
“Challenge/Response” methodology. The “Read/Do” methodology has
been eliminated as an acceptable means of conducting the checklist. The
principle advantage of the “Do/Verify” philosophy provides for setup
redundancy.
Setup redundancy occurs when the aircraft is configured from memory
(“Flow”) and the checklist is used only to verify that all items have been
accomplished properly. Therefore, if an item is missed in a flow check, a
second opportunity exists to catch the missed item during the checklist
procedure. While the “Do/Verify” method may require additional “dry” time
to learn the “flows”, when practiced and perfected, the level of a truly
professional pilot will be attained.
Consistent with the “Do/Verify” philosophy, the checklist must be used to
back up the flow (except for the Before Takeoff “Final Items”) even though
a memorized flow check shall be employed. A memory-guided checklist
(no verification of the flow with the checklist) is unacceptable and not
consistent with safe flight operations. In addition, only a visual verification
that a switch or control is in the correct position when accomplishing the
checklist is mandatory (not to be verbalized).
The only exception to the “Do/Verify” philosophy occurs when conducting
Abnormal Checklist items. These items are not performed as part of a flow
but as “Read/Do”. The initiation and completion of all checklists shall be
announced by the executing crewmember or the challenging crewmember
in the case of a “Challenge/Response” checklist (e.g., “Before Start
Checklist”.......“Before Start Checklist Complete”).
Revised 07-01-2012 © Embry-Riddle Aeronautical University Rev 06