Certification of Normal Category Rotorcraft — Changes 1–9
Normal category rotorcraft guidance with Changes 1–9 incorporated. Search the complete AC or start with the system safety, flight controls and instrument-flight guidance.
This source includes guidance for different amendments of Part 27. Match the guidance to the aircraft’s agreed certification basis: the 27.1309 entries for Amendments 27-21, 27-46 and 27-51 are separate. The base AC was issued on 30 September 1999; Change 9 is dated 23 June 2023. The FAA catalogue’s 30 September 2008 date is not the date of the latest change.
The source, within reach.
Search within this AC, jump to a source page, or download the complete saved publication.
This extraction supports search. Read the original page for complete notation and layout.
4/25/06 AC 27-1B, Chg 2
warnings include, but are not limited to, an obvious aircraft attitude change following the
failure or an audio warning tone. A visual indication itself may not be adequate since
detection of a visual warning would normally require special pilot attention. The use of
devices such as stick pushers or shakers is not acceptable as a warning means since
the automatic flight control systems (AFCS) may provide a hands-off capability or
normal helicopter vibrations could mask a control shaker. However, this rule is not
intended to eliminate the use of such devices for other purposes. Examples of
automatic control systems other than a stability augmentation system would be a pitch
axis actuator used for the purpose of demonstrating compliance with longitudinal static
stability requirements or a fly-by-wire elevator. For control systems where a series
actuator malfunction could degrade control authority, a means should be provided to the
pilot to determine actuator alignment (see § 27.1329(b)).
(2) The corrective flight control input following a system failure should be in the
logical direction. For example, a malfunction resulting in a nosedown pitch of the
aircraft should require a corrective cyclic control input in the aft direction. The system
deactivating means does not have to be located on the primary flight control grips;
however, it should be easily accessible to the pilot. Consideration should be given to
the consequences of inadvertent de-selection of the automatic stabilization system,
especially if the deactivation control is mounted on a primary control grip. Malfunctions
and subsequent recoveries must be shown throughout the operating envelope of the
aircraft. In a case where control authority is decreased following a malfunction, a
practical flight envelope must be defined wherein compliance with controllability and
maneuverability requirements can be demonstrated. This practical flight envelope must
be presented in the flight manual. Compliance with trim and stability characteristics is
not required following a malfunction; however, a pilot workload assessment should be
made to show that these characteristics are not impaired below that needed for
continued needed for continued safe flight and landing.
AC 27.673. § 27.673 (Amendment 27-21) PRIMARY FLIGHT CONTROL.
a. Explanation. This regulation basically defines primary flight controls as “those
used by the pilot for immediate control of pitch, roll, yaw, and vertical motion of the
rotorcraft.” This regulation was generated to clarify the application of § 27.1555 which
requires markings for controls other than “primary flight controls or control(s) whose
function is obvious.”
b. Procedures. The primary flight controls; i.e., cyclic stick, collective, and tail
rotor pitch control pedals are excluded from the marking requirements of § 27.1555.
AC 27.674. § 27.674 (Amendment 27-26) INTERCONNECTED CONTROLS.
a. Explanation. A new § 27.674 is added by Amendment 27-26 which requires
that the rotorcraft be capable of safe flight and landing after a malfunction, failure, or
jam of any auxiliary interconnected control.
Page D - 37
Saved from the FAA on November 17, 2026. All original pages are retained. Engineering explanations are presented separately below.
Aerospace Consulting / Engineering perspective
Start with the certification basis and the function.
Identify the applicable amendment before selecting the safety guidance. Connect intended functions and operating conditions to failure conditions, architecture decisions, common-cause considerations, verification and limitations. For flight controls and IFR work, carry the relevant 27.672, 27.1329 and Appendix B assumptions into the system safety and compliance evidence.
1196 original pages. 0 pages have reviewed text reflows. Original-first pages retain the source layout, with extracted text available for finding words.
A focused review, an agreed assessment package or ongoing support alongside your team. We can agree the relevant inputs and scope in the initial conversation.
This opens your email application.
Start a conversation
Tell us about your programme, the system you are developing and the support you need.
We can agree a focused use-case review, a defined evidence package or ongoing programme support.
This opens your email application.
Specialist aerospace expertise
Aerospace Consulting is led by Hussein Khimji, an FAA Designated Engineering Representative in systems and equipment, with a focus on system safety, flight controls and avionics.
We work with aircraft developers and systems suppliers to connect technical decisions, safety assessments and certification evidence.
This is the proposed introduction. The full About page will add your approved biography and associate expertise.
Systems engineering & development assurance
Tell us about the aircraft or system, its intended function, stage of development and the support you need.