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.
AC 27-1B, Chg 1 2/12/03
(4) Satisfactory comparison of processed directed action to actual
maintenance performed as a result of inspection. This approach would require data
collection on the system prior to actual credit application. The amount and duration of
data collection should be agreed between the applicant and the certifying authority at
the beginning of the project on a case-by-case basis.
(5) Any other independent means of verifying the accuracy/integrity of the
equipment including software by a satisfactory comparison to the directed action of the
HUMS processed data.
(B) Integrity Level Considerations. The methodology is the same for
different integrity level requirements as they relate to COTS hardware/software, but the
compliance requirement will vary. The processes described in the previous and
subsequent paragraphs of f(3) should be applied to meet the initial integrity
requirements for the criticality categories of Hazardous/Severe Major and Major. Minor
criticality category level will also require qualification by this process, except that
independent verification can be performed after certification, provided that an approved
plan is submitted for this activity. Other applications that do not employ COTS will use
standard engineering practices to satisfy the integrity level considerations.
Modification of Approved Systems. Changes to the equipment including software
should be qualified on a case-by-case basis that is dependent on the effect on the
integrity and functionality of the system. If mitigation had been successfully
demonstrated for the original configuration, the mitigation must be shown to provide the
same level of integrity for the changed configuration.
(C) Ground Based Equipment Hardware. This hardware may consist of
data processing, display, and possibly printing equipment or other accessories. The
hardware must be compatible with the intended application and software. The
independent means of verification activity is required due to the use of COTS hardware.
(D) Software. Most systems will employ two types of software. One type
is the operational software and the other is the HUMS specific software. The
operational software may be COTS. (See following figure for typical ground based
application process for HUMS specific software using COTS as an operational
software.)
Page MG 15 - 10
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.