FAA / Advisory circular

AC 27-1B

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.

Start with the scope.

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.

Download saved FAA PDF ↓

Read the source

The document, within reach.

FAA source document

Printed page B-26

PDF page 82 of 1196

Enlarge original ↗

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

Original FAA AC 27-1B, PDF page 82
AC 27-1B · B-26Open saved PDF here ↗
Extracted text for finding words

This extraction supports search. Read the original page for complete notation and layout.

AC 27-1B, Chg 4                                                     9/17/2009


horizontal acceleration close to the ground has pilot scan outside the cockpit and
adjustment of engine torque or temperature would require an undue increase in
workload). The recommended takeoff procedure must be demonstrated to remain clear
of the HV “avoid” areas without requiring exceptional piloting skill or exceptionally
favorable conditions.

       (2) The hover reference height is established as the minimum skid or wheel height above
the takeoff surface from which a takeoff can consistently be accomplished in zero wind without
contacting the runway surface. The takeoff must be accomplished with power fixed at the power
required to hover at the hover reference height and must not require exceptional piloting skill to
avoid runway surface contact.

AC 27.51A.    § 27.51 (Amendment 27-44) Takeoff.

   a. Explanation. Amendment 27-44 revised the requirement to perform the test at the
most critical center-of-gravity (CG) location as opposed to the most forward CG. While
it is not always the case, the forward CG is particularly critical for most rotorcraft.
Additionally, the change clarifies that the test must be performed at the maximum
weight requested for takeoff for altitudes above sea level. The previous requirement
stated that the test be performed at a weight selected by the applicant for altitudes
above sea level. That weight was traditionally interpreted to mean the maximum
requested takeoff weight for that altitude and it is now stated that way in the rule.

   b. Procedures. The policy material pertaining to the procedures outlined in this
section remain in effect.





Page B - 26

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.

Explore the rotorcraft safety and certification approach →
Source edition and reading coverage

1196 original pages. 0 pages have reviewed text reflows. Original-first pages retain the source layout, with extracted text available for finding words.

Source SHA-256: 2dfac16a3644dc18997069cca78746c10726e4b70d3aba996fc87843ffe68a2b

This is a dated source copy. Automatic source acquisition is not yet scheduled.

Original FAA PDF ↗

Working through a certification question?

Bring the aircraft, the basis and the issue your team needs to resolve.

Discuss your programme →