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-30

PDF page 88 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 88
AC 27-1B · B-30Open saved PDF here ↗
Extracted text for finding words

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

AC 27-1B                                                                  9/30/99


     b. Procedures.

         (1) Tests are conducted at speeds which bracket the anticipated speeds for
minimum rate of descent and best glide angle. On a power required plot, the speed for
minimum power required approximates the speed for minimum rate of descent. The
speed for maximum range glide may be estimated by drawing a tangent from the origin
to the power required curve.

         (2) Autorotative performance tests may be conducted in conjunction with the
climb performance tests. The required data are similar for both tests and it is
sometimes convenient and efficient to run alternating climbs and descents through a
desired altitude band. Descents should be conducted on reciprocal headings and
results averaged in the same manner as climb performance tests.

         (3) A reduction in rotor RPM from the normal power-on value may enhance
autorotative performance.  If the applicant wishes to develop autorotative performance
at RPM values significantly below the governing or power-on range, the practicality of
reducing and controlling RPM at the lower value and of then increasing RPM as a
landing is approached, must be considered. At low weights and low density altitudes,
full down collective may automatically produce lower RPM values and this condition is,
of course, acceptable provided the approved power-off RPM range is not exceeded.

         (4) During autorotation tests, care must be taken to make certain that no engine
power is delivered to the rotor drive system since a very small amount of power can
have a large effect on descent performance.





Page B - 30

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 →