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.
3/31/2014 AC 27-1B, Chg 4
(ii) Low Hover. From the low hover position there is no flare capability and little
time for collective reaction. No time delay is applied other than normal pilot reaction.
For typical designs the collective may not be lowered after power failure. Lowering of
the collective is not permitted because it is not a pilot action which could be expected if
an engine failed without notice during a hovering condition in service. Initial lowering of
collective immediately after power failure can result in a very high, unconservative low
hover height that is unrealistic for operational conditions. If, however, a design is such
that a 1-second pilot delay after power failure could be achieved without any
appreciable descent, a slight lowering of collective could be allowed.
(iii) Takeoff Corridor. Normal pilot reaction is applied when the engine is made
inoperative. At low speeds, collective may be lowered quickly to retain RPM and
minimize the time between power failure and ground contact. If airspeed is sufficient for
an effective flare, the aircraft is flared to reduce airspeed, retain rotor RPM, and control
vertical speed prior to touchdown. Considerable surface area may be needed for a
sliding or rolling stop.
(iv) Additional Considerations. The “in-between” points utilize similar
techniques. The cruise or “fly-in” points are similar to the high hover point although the
steep initial pitch attitudes are not needed as altitude is decreased and airspeed is
increased along the curve. The low speed points along the takeoff corridor are similar
to the low hover point except that the collective may be quickly lowered and some flare
capability may be used as the “knee” is approached. The pilot should be proficient in all
normal autorotation landings before conducting HV tests in a single-engine rotorcraft.
(7) Ground Support. Motion picture or theodolite coverage and ground safety
equipment are necessary. Communication capability among these elements should be
provided. Use of a phototheodolite to compare height and speed with cockpit
observations is very desirable.
(8) Verifying the HV Diagram.
(i) A sufficient number of test points must be flown to verify the diagram. The
key areas are the knee, high altitude hover, low altitude hover, and low altitude high
speed flight. Test points with excessive gear loads, exceptional skill requirements,
winds above permissible levels, rotor droop below approved minimum transient RPM,
damage to the rotorcraft, excessive power, incorrect time delay, etc., cannot be
accepted.
(ii) After the HV diagram is defined, it should be ascertained that the corridor
permits takeoffs within ±5 knots of the recommended takeoff profile.
(9) Flight Manual. The flight manual should list any procedures which may apply
to specific points (e.g., high speed points) and test conditions, such as runway surface,
wave height for amphibious tests, marginal areas of controllability or landing gear
Page B - 41
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.