Per Neil Krey's request of Delta Air Lines, Inc. formal Automation
Policy, the following is taken from the Delta Air Lines, Inc. FOM
(Flight Operations Manual), Chapter 4: General Policy, page 8:
Automation Policy
General
Automation is provided to enhance safety, reduce pilot workload and
improve operational capabilities. Automation should be used at the most
appropriate level.
Pilots will maintain proficiency in the use of all levels of automation
and the skills required to shift between levels of automation. The level
used should permit both pilots to maintain a comfortable workload
distribution and maintain situational awareness. The following
guidelines apply to the use of automation:
* If any autoflight system is not operating as expected, disengage it.
* All pilots should be aware of all settings and changes to automation
systems.
* Automation tasks should not interfere with outside vigilance.
* Briefings should include special automation duties and
responsibilities.
* The PF must compare the performance of the autoflight systems with
the flight path of the aircraft.
When a pilot conducts a briefing, the level of automation will be
addressed. As an MD-11 flight instructor, it would be acceptable to hear
the following:
This will be a coupled approach for the ILS Runway 24R at KLAX. I am
planning to autoland; in the event we do not get an ALIGN annunciation
at 150' AGL, if I have the runway in sight, I will disconnect and land,
otherwise I will call missed approach - OR - this will be a coupled
approach for the NDB Runway 24R at KLAX. I am going to NAV it in with
TRACK Preselected to the final course of 249 degrees. Prior to ROMEN,
the FAF inbound, I want you to display APPROACH (raw data), and call out
any deviation noted. I will correct back on course Selecting TRACK.
Hope this helps Neil!
Lonny M. Regan
Delta Air Lines, Inc.