Aircraft checklists: Difference between revisions

Jump to navigation Jump to search
m
Line 209: Line 209:
Automated checklist execution is not restricted to autostart and shutdown. If you have an "After Landing" checklist that switches landing lights off, raises flaps and turns taxi lights on, for example, you could assign that to a keyboard shortcut. Rollout and taxi is a busy time on some aircraft and it's often not easy to find the switches and controls necessary to complete this kind of checklist.
Automated checklist execution is not restricted to autostart and shutdown. If you have an "After Landing" checklist that switches landing lights off, raises flaps and turns taxi lights on, for example, you could assign that to a keyboard shortcut. Rollout and taxi is a busy time on some aircraft and it's often not easy to find the switches and controls necessary to complete this kind of checklist.


To use the <tt>autochecklist.nas</tt> script, pilots need <tt>FGDATA</tt> v3.5 or greater, otherwise the <tt>autochecklist.nas</tt> script will not be available. The availability of the autochecklist script can be tested by checking whether the <tt>sim/checklists/auto</tt> node is nil and a suitable indication given to the pilot.
To use the <tt>autochecklist.nas</tt> script, pilots need <tt>FGDATA</tt> v3.5 or greater, otherwise the script will not be available. The availability of automated checklists can be tested by checking whether the <tt>sim/checklists/auto</tt> node is nil and a suitable indication given to the pilot if it is nil.


For an example of using automated checklists, refer to the [[Lockheed Constellation]], for which the script was originally written.
For an example of using automated checklists, refer to the [[Lockheed Constellation]], for which the script was originally written.
149

edits

Navigation menu