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.
9/17/2009 AC 27-1B, Chg 4
(ii) Comprehensive controllability tests are typically conducted at low,
intermediate (~7000 feet Hd) and high tests sites, with prepared landing surfaces, in
conjunction with takeoff, landing, and performance testing.
(iii) Alternatively, a predicted controllability model developed for high altitude
may be used if verified by limited flight-testing with steady ambient winds. The
extrapolation guidelines in AC 27.45 b (2) are still applicable. These high altitude
controllability tests could typically be conducted in conjunction with takeoff, landing, and
performance tests.
(iv) Controllability can usually be extrapolated up to a maximum of 2,000
feet above the highest test site altitude.
Note: Engine operating characteristics must be considered during the limited high
altitude tests.
(4) Prior to engine failure testing, the pilot should be fully aware of his engine,
drive system, and rotor limits. These limits were established during previous ground
and flight tests and should be specified in the type inspection authorization (TIA).
Particular attention should be given to minimum stabilized and minimum transient rotor
RPM limits. These values should be included in the TIA and should be approached
gradually with a build-up in time delay unless the company testing has completely
validated all pertinent aspects of engine failure testing. On Category A installations, the
maximum power output of each engine should be limited so that when an engine fails
and the remaining engine(s) assume the additional load, the remaining engine(s) are
not damaged by excessive power extraction and exceeding a temperature limitation.
This is needed for compliance with § 29.903(b). The propulsion engineer should have
assured that this feature was properly addressed in the engine and drive system
substantiation; however, it must be assumed that for some period of time the pilot may
extract maximum available power from the remaining engine(s) when an engine fails
during critical flight maneuvers. Substantiation of this feature should be accomplished
primarily by engine and drive system ground tests.
(5) Longitudinal cyclic authority at VNE with any power setting must permit
suitable nose down pitching of the rotorcraft. If the remaining control travel is considered
marginal, tests should include applications up to full control deflection to assess the
remaining authority. Some knowledge of the aircraft's response to turbulence is useful
in assessing the remaining margin. As a minimum, the rotorcraft must have adequate
margin available to overcome a moderate turbulent gust and must not have any
divergent characteristic that requires full deflection of the primary recovery control to
arrest aircraft motion. If other controls must be utilized to overcome adverse aircraft
motion, the results are unacceptable (e.g., if a pitch up tendency resulting from an
actual or simulated moderate turbulent gust cannot be satisfactorily overcome by
remaining forward cyclic, the use of throttle or collective controls to assist the recovery
is not an acceptable procedure; however, the use of lateral cyclic to correct roll in
conjunction with forward cyclic to correct pitch-up, is satisfactory). Obviously, during the
Page B – 52.7
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.