Original FAA page, including its printed amendment and change markings. Extracted words support search; text reflow has not been reviewed.

Extracted text for finding words
This extraction supports search. Read the original page for complete notation and layout.
AC 27-1B, Chg 7 2/4/2016
d. System Description.
(1) General. Develop a system description with enough detail to provide for a common
understanding of the design, function, and operation of the system. Thoroughly detail any new or novel
features, interfaces, controls, or other pilot-system interfaces that pilots will use.
(2) Intended function (§ 27.1301).
(i) Describe the intended function of the major pilot-system interfaces. In order to assess the
potential hazards posed by the installation of a system, there must be a clear understanding of the
function provided by the system and the declared intended function. Accomplish this by providing a
detailed description of how the system supports the specified function(s). For example, describing a
function or component, such as a display, as “for pilot situation awareness only” or “for situational
awareness only” is not adequate regardless of whether the function or component is required by the
regulations. A better example for a non-required function might be “to increase terrain awareness.”
Identify the following items, as appropriate, focusing on new or unique features that affect the crew
interface or the allocation of tasks between the pilot and the rotorcraft systems:
(A) The intended function of the system from the pilot’s perspective (coupling between
the pilot and the system).
(B) The role of the pilot relative to the system.
(C) The degree of integration or independence with other flight deck equipment.
(D) The novelty of the system or features of the system.
(E) The criticality of the system and alerting mechanism.
(F) Methods to reduce the occurrence and consequences of crew error when interacting
with the system.
(G) The system features accessible to the pilot other than those normally considered
needed for flight. For example, whether field loadable software, maintenance, and configuration functions
are accessible by the pilot in flight and on the ground, or whether they are accessible only by
maintenance personnel.
(ii) Use the following information to evaluate whether the intended functions and associated
tasks are sufficiently detailed and specific:
(A) Whether each feature includes a statement of the intended function and a description
of the task associated with this feature.
(B) Whether there are assessments, decisions, or actions required by the pilot for these
intended functions.
(C) Whether other information is to be used in conjunction with these intended functions
(for example, other cockpit systems), in combination with the system.
(D) Whether the operational environment in which these intended functions are to be
used is adequately described (e.g., VFR, IFR, phase of flight).
(3) Cockpit layout (§§ 27.771, 27.773, 27.777, 27.1303, 27.1305, 27.1321, 27.1329, and
Appendix B to part 27).
Page MG 20 -6