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.
2/4/2016 AC 27-1B, Chg 7
(i) Drawings of the cockpit layout showing positions of system components, even if
preliminary, are beneficial for providing an understanding of the intended overall cockpit arrangement
(controls, displays, sample display screens, seating, stowage, and so forth). Including measurements
and dimensions of displays, their locations and locations of controls relative to the pilot’s central line of
vision or the design eye position is also beneficial to both the applicant’s and certification authority teams.
As the system design changes, keep the certification team updated so they are current on proposed
changes. Give special attention to the following, especially if they are novel or unique:
(A) Arrangements of the controls, displays, or other cockpit or flight deck features or
equipment.
(B) Controls, such as cursor control devices, touchscreen displays, or new applications of
existing control technology.
(C) Content, format, and function of the pilot interface on the display as generated by the
systems software.
(D) Display hardware technology.
(E) Screen usage, alerting mechanisms, and mode annunciation.
(ii) Sketches of the crew interfaces for the specific systems or the items listed above can be
helpful in providing an early understanding of the features that may face certification issues.
(4) Underlying principles for automation logic (§ 27.1309, § 27.1329, and Appendix B to part 27).
Define the system’s automated functions design early in the process. The automation features should
follow a design philosophy that supports the intended functions regarding the system behavior, modes of
operation, and pilot interface with controls, displays, and alerts. For designs that involve significant
automation, the way automation operates and communicates that operation to the pilot can have
significant effects on the crew interface. The system description should include, but not be limited to:
(i) Pilot actions to engage or disengage, or activate or deactivate, modes and features.
(ii) Principles underlying mode transition.
(iii) Mode annunciation scheme.
(iv) Automation engagement or disengagement principles.
(v) Level of automation.
(vi) Logic diagrams and complexity of the logic, if available.
(vii) Failure modes, how they appear to the pilot, and how the pilot’s interaction with the
system and rotorcraft changes.
(5) Operational considerations (§ 27.1523, Minimum flight crew; § 27.1525, Kinds of operations).
Consider consulting the AEG inspector that is responsible for the make and model of rotorcraft on the
system installation.
(i) Pilot characteristics (§ 27.1523). The FAA has not accepted certain designs, in past
projects, that specifically relied on crew resource management or certain pilot characteristics to mitigate a
system design flaw. Consider assessing the level of certification, skill, and knowledge a “nominal pilot”
possesses in order to evaluate the pilot workload when interacting with the system and rotorcraft.
Page MG 20 - 7