Advisory Circular: U.S. Department of Transportation
Advisory Circular: U.S. Department of Transportation
Department Advisory
of Transportation
Federal Aviation
Administration
Circular
Subject: Maintenance Review Board Report Date: 10/29/10 AC No: 121-22B
Maintenance Type Board, and Initiated by: AFS-300 Change:
OEM/TCH Inspection Program
Procedures
FOREWORD
This advisory circular (AC) provides guidelines that industry may use to develop and revise the
minimum scheduled interval/tasking requirements for derivative or newly type-certificated
aircraft and powerplants for Federal Aviation Administration (FAA) approval. This AC refers to
these minimum scheduled interval/tasking requirements as the Maintenance Review Board
Report (MRBR), Maintenance Type Board. After FAA approval, the requirements become a
basis upon which operators develop their own individual maintenance programs. The report will
become a living report for each type-certificate holder.
for
John M. Allen
Director, Flight Standards Service
10/29/10 AC 121-22B
CONTENTS
Paragraph Page
i
AC 121-22B 10/29/10
CONTENTS (Continued)
Paragraph Page
ii
10/29/10 AC 121-22B
CONTENTS (Continued)
Paragraph Page
LIST OF FIGURES
1-1. PURPOSE. This advisory circular (AC) provides guidelines that industry may use to
develop and revise the minimum scheduled interval/tasking requirements for derivative, or newly
type-certificated aircraft and powerplants for Federal Aviation Administration (FAA) approval.
This AC refers to these minimum scheduled interval/tasking requirements as the Maintenance
Review Board Report (MRBR) Maintenance Type Board (MTB). After FAA approval, the
requirements become a basis upon which operators develop their own individual maintenance
programs. The report will become a living report for each type-certificate holder (TCH).
1-4. AUDIENCE. Guidance in this AC pertains to FAA personnel, air operators, air carriers,
and original equipment manufacturer (OEM)/TCH and their vendors involved in the
development of the MRBR process.
1-5. USE OF THIS AC. This AC is not mandatory and is not the only means to comply with
the regulations. The FAA issues this AC for guidance and to outline a method of compliance. A
person may elect to follow an alternative method, provided the FAA finds it to be an acceptable
means of complying with the applicable requirements of 14 CFR. If you use the methods
described in this AC you must follow them in all respects. The FAA derived these guidelines
from regulatory authorities and aviation industry experience. This AC is primarily designed to
provide advice and recommendations for the standardized development, implementation, and
update of FAA-approved minimum scheduled maintenance/inspection requirements
NOTE: This AC uses the term “must” only in the sense of ensuring the
applicability of these particular methods of compliance when operators use
the acceptable means of compliance described herein. This AC does not
change regulatory requirements and does not authorize changes in, or
deviations from, regulatory requirements.
• Order 8430.21, Flight Standards Division, Aircraft Certification Division and Aircraft
Evaluation Group Responsibilities.
b. Role of the Maintenance Steering Group. In 2006, the Air Transportation Association
of America (ATA) MSG was named the Maintenance Programs Industry Group (MPIG), while
the latest version of MSG still retained the same original title. ATA coordinates, and industry
chairs the MPIG; it assumed the same duties as the original MSG task force. MPIG meets
annually, or as required, to review issues submitted by industry and the regulatory authorities
affecting the latest version of MSG and institute improvements or any necessary evolutionary
changes due to revised regulatory requirements or advances in industry technology.
Certification Maintenance Requirements. This revision also added text and revised flowcharts to
clarify the FD logic. It was a major rewrite of the L/HIRF protection systems.
b. Use of the MSG Analysis Process. You must use the latest version of the Air
Transportation Association of America Maintenance Steering Group (MSG) analysis process and
procedures for the development of an MRBR for all new, derivative, and optimization of aircraft
and engines. Reapplication for a TC requires using the most recent latest version of the MSG
logic process. The FAA no longer supports MSG-2 at the committee or working group level.
Each OEM/TCH is responsible for supporting the regulatory requirements for their MSG-2
aircraft.
tasks, can be adequately performed and that the procedure meets the intent of the MRB task.
Additional tasks may be validated at FAA’s discretion.
NOTE: Figure 2-1 outlines the relationships between the various documents
involved in the creation of the minimum scheduled interval/tasking
requirements, including the MRBR.
a. Approve the PPH and forward it to the MRB chairperson for review and acceptance.
The FAA MRB chairperson will direct to the OEM/TCH further comments during the MRB PPH
review process. The ISC must approve the initial PPH and all subsequent revisions; the FAA
must accept them before any WG meetings can begin.
b. Determine the number and type of each WG that will be necessary and then organize
and manage those groups. The ISC will ensure that a minimum of three separate operators attend
each WG meeting.
c. Provide the MRB chairperson with a list of the number and various type of each WG,
the name and affiliation of each member, and any subsequent personnel changes.
d. Arrange for required aircraft technical/MSG training for all ISC and WG members, and
FAA/regulatory authorities.
e. Invite the MRB chairperson and selected MRB members to ISC meetings.
f. Invite other regulatory authorities to ISC and WG meetings, with concurrence and
coordination of the MRB chairperson.
h. Review all WG analyses and presentations. Return to the WG for further review
analysis with which the ISC does not concur. The ISC must establish a tracking system to
resolve these actions and issues.
j. Provide complete and accurate meeting minutes for all ISC and WG meetings. Establish
a method of distributing and tracking all meeting minutes.
k. Establish a tracking system to ensure resolution of all maintenance issues and open
action items or concerns. Document and resolve all maintenance issues and open action items
before presenting an MRBR proposal to the MRB chairperson.
l. Provide to the appropriate MRB members all supporting technical data/analysis for the
proposed MRBR.
3-4. OEM/TCH FUNCTIONS. The OEM/TCH will perform the following functions:
b. Provide required aircraft technical/MSG training for all ISC and WG members, and
FAA/regulatory authorities before holding the first WG meeting.
c. Provide the ISC with a comprehensive list of Maintenance Significant Items (MSI) and
Structural Significant Items (SSI), and the items precluded from the MSI/SSI list before
beginning any ISC/WG meeting.
d. Arrange for the required attendance of the appropriate OEM/TCH design personnel at
each ISC/WG meeting.
e. Provide WG members with current technical data to support the analysis of each MSI,
SSI, and zones of the aircraft for analysis by each WG. The data are required 30 days before the
ISC/WG meeting.
f. Arrange for technical support and access to the aircraft or appropriate OEM/TCH and or
vendor facility for the review and validation of all analysis and tasks.
g. Provide the ISC/MRB and appropriate WG members, during each ISC/MRB meeting,
with an updated report of all Airworthiness Limitation (ALI) item, Certification Maintenance
Requirements (CMR), and all design changes.
h. Ensure that the OEM/TCH manuals contain information and procedures for
accomplishing all on-aircraft systems/structures/zonal tasks covered in the MRBR.
i. Participate in all ISC and WG activities in support of the development of the MRBR.
j. Provide the MRB chairperson a copy of all supporting technical data/analysis for the
proposed MRBR at the conclusion of the project.
k. Submit the MRBR proposal to the MRB chairperson at least 90 working days before
scheduled approval.
b. Notification of MRB Composition. The MRB chairperson will provide formal written
notification to AFS-302 of the MRB board composition. Refer to Figure 4-1. The MRB
chairperson will also invite AFS-302 or his or her representative, along with an invitation to the
Maintenance Program Industry Group (MPIG) chairperson, to participate in the MRB process.
d. Assignment of MRB Members. The MRB chairperson will assign an FAA MRB
member to each WG. The MRB chairperson may assign additional FAA advisors to each WG if
necessary. FAA WG advisors will include staff from FAA engineering/design certification
branches as well as appropriate aviation safety inspectors from Flight Standards Service (AFS)
having oversight of aircraft maintenance operations, and AEG personnel.
(1) This FAA MRB chairperson is the counterpart to the international MRB chairperson
in all matters concerning MRB activities and MSG processes. The MRB chairperson is the sole
authority regarding United States FAA requirements. The chairperson also provides the
collective input from all the FAA advisors regarding WG activities. The primary duty is to
ensure compliance with the applicable Title 14 of the Code of Federal Regulations (14 CFR)
minimum interval/tasking requirements/FAA regulatory requirements. Also, to the extent
possible, the chairperson ensures standardization and harmonization of the domestic and
international MRB activities within the international MRB process.
(2) Regarding all issues of concern, the FAA MRB chairperson is also responsible for
coordination with FAA certification within the appropriate Aircraft Directorate project manager
and engineering staff. This may require developing issue papers and responding to certification
issue papers, or seeking consultation on new technological issues that may arise during the
design and development process of the aircraft.
(3) The FAA WG advisors provide assistance and guidance to WG members regarding
the Policy and Procedures Handbook (PPH), latest version of MSG process, FAA policy, and
regulatory requirements. The FAA advisors report directly to the FAA MRB chairperson on all
matters regarding assigned WG activities, actions, results, and controversial issues.
a. MRB Personnel. The MRB supports the development of an industry MRBR proposal
containing the minimum scheduled interval/tasking requirements for a newly FAA
type-certificated or derivative aircraft and its aircraft engines. The MRB may include qualified
FAA AFS inspector personnel, AEG personnel, and engineering representatives from the
controlling FAA certification/directorate office.
b. MRB Chairperson Functions. The MRB chairperson will initiate the development of
an MRB obtaining a complete schedule of all MSG process activities from the OEM/TCH. The
MRB chairperson assigns MRB members or other qualified FAA personnel to work as advisors
to each applicable industry WG. It is also the responsibility of the MRB chairperson to perform
the functions identified in the PPH, described in Chapter 3. These include the following:
(1) Determine the number and type of qualified FAA personnel that are necessary, and
assign them to their respective WG by specialty (systems, engines, avionics, structures, zonal,
lighting/High Intensity Radiated Field, etc.).
(2) Provide the ISC chairperson with a list of FAA personnel names, their affiliations,
assignments, and changes in personnel as they occur.
(3) Invite other regulatory authorities, in coordination with the AEG manager and the
OEM/TCH, to participate in the MRB, and coordinate the activities with regulatory authorities
through their representatives.
(4) Obtain letters of confirmation between the FAA and each participating regulatory
authority. Refer to the template example Figure 5 Letter of Confirmation in Appendix 4.
(6) Establish and maintain a file of all MRB proceedings in the MRB historical file.
(7) Establish the extent of other regulatory authority participation and assignment as
WG Advisors.
(8) Keep other regulatory authorities informed regarding any changes to MRB policy
and procedures before and during the MRB process.
(9) Accept the ISC-approved PPH, following a review by all participating regulatory
authorities, within 30 working days of receipt.
(10) Coordinate all MRB activities and associated matters with the ISC chairperson.
(12) Schedule the MRB meeting before attendance of ISC meetings, as required.
(13) Attend all ISC meetings and be prepared to address any previous open issues that
developed during WG or ISC meetings.
(14) Ensure that the appropriate FAA and other regulatory authorities attend WG
meetings.
(15) Offer information, guidance, and assistance to the ISC and each WG regarding
regulatory requirements, PPH, compliance and process management, MSG noncompliance, and
other related issues.
(16) Review reports from previous ISC meetings (if applicable) and from the WG
members with regard to open issues or concerns.
(18) Discuss and correct potential problem areas of controversy with other regulatory
authority participants and decide if FAA Maintenance Review Board Policy Board (MRBPB)
guidance is needed. If required, draft an appropriate issue paper for submittal to MRBPB for
resolution.
(19) Coordinate all items of new technology developments and issues not previously
addressed by the MSG standard with the FAA MRBPB and international MRBPB.
(20) Approve the MRBR, and revisions, in accordance with established MRBR
revision procedures.
b. Direct FAA WG advisors in assigned WG regarding compliance with the PPH and
current regulatory and policy requirements.
c. Attend MRB meeting to review and discuss all significant quality problems and open
issues as required.
d. Attend ISC meetings, as invited by the ISC chairperson to support regulatory and policy
requirements.
e. Attend WG meetings to review and discuss all significant quality problems and open
issues as required. Ensure that the WG follows the MSG process and PPH guidelines. Report any
deviations from the MSG process/approved PPH procedures to MRB chairperson.
f. Review technical data and MSG analysis and PPH revisions provided by the OEM/TCH
before each WG meeting, as required. The OEM/TCH must provide and deliver the data
30 working days before each meeting.
g. Record all WG activity and discussion in the meeting minutes, and record unresolved
open actions/open issues in a formal ongoing action list or report.
i. Review WG meeting minutes and provide progress reports to the MRB chairperson
within 2 weeks after each WG meeting, but no later than the next scheduled ISC meeting. This
review will contain an assessment of WG activities, including a notification of any controversy
for potential problem areas or issues affecting the MSG process.
a. Attend WG meetings and provide technical information, assistance, and guidance to the
WG members.
c. Act as an MRB member for the WG when requested by the MRB chairperson. Perform
all the functions of the MRB member while acting as an MRB member.
b. Attend ISC meetings by invitation from the ISC chairperson and the concurrence of the
MRB chairperson.
c. Notify the ISC chairperson, via the MRB chairperson, of any national regulatory
differences requirements before compiling the MRB report proposal.
d. Acknowledge approval of the MRB report in the manner outlined in the letter of
confirmation and in the PPH.
NOTE: When the lack of personnel or other reasons limit the role of the host
authority, the MRB chairperson may seek more involvement of other
regulatory authorities as MRB members/WG advisors.
a. MRBR Proposal. The industry steering committee (ISC) chairperson forwards the
Maintenance Review Board (MRB) MRBR proposal to the original equipment manufacturer
(OEM)/type certificate holder (TCH) representative(s) and may invite the OEM/TCH to discuss
the comments or findings. The OEM/TCH must present the ISC-proposed MRBR, as
recommended, to the Federal Aviation Administration (FAA) for review as part of the
instructions for continued airworthiness. Following ISC final review, the OEM/TCH submits a
formal letter and the MRBR proposal to the MRB chairperson for review and approval.
b. FAA Approval Process. Concurrent with MRBR approval, the MRB chairperson will
forward a copy of the MRBR with an approval recommendation to AFS-302 for their
concurrence. The AFS-302 representative concurs or rejects and returns the MRBR to the
assigned Aircraft Evaluation Group (AEG). If AFS-302 concurs, the MRB chairperson sends a
letter of approval along with the signed approval page of the MRBR to the OEM/TCH (ISC
co-chair). Refer to Figures 5-1 and 5-2, below. Should AFS-302 reject the MRBR, the assigned
AEG MRB chairperson will return the report to the OEM/TCH for corrections and resubmit. The
chairperson returns the corrected report to AFS-302 for their concurrence. Normally, the FAA
approval process occurs within a timeframe of 90 working-days, unless corrections are required.
Approval by foreign regulatory authorities will normally occur concurrently with FAA approval.
The OEM/TCH is responsible for publishing and distributing the initial and revised MRBR, and
any supporting documents in a format acceptable to the Administrator.
operator’s approved maintenance program. The FAA recommends the operator’s program
incorporate MRBR revisions associated with type design changes. The local regulatory authority
must approve and/or accept all maintenance program revisions.
6-1. MRB REPORT ANNUAL REVIEW. Because the Maintenance Review Board (MRB)
report is intended to be an up-to-date, “living” document, the original equipment manufacturer
(OEM)/type certificate holder (TCH), industry steering committee (ISC), and the MRB
chairperson should annually conduct a joint MRB Report (MRBR) review to determine any need
for a revision. The MRB chairperson should document results of these reviews for inclusion in
the MRB historical file.
a. Proposed Changes. If needed, the OEM/TCH, ISC and the MRB will convene to
evaluate any proposed changes. Submit all proposed changes with supporting data to the MRB
chairperson. Approval or disapproval of the proposed changes will be processed in the same
manner as outlined for the MRBR approval/disapproval process.
c. Multiple Approvals. If more than one regulatory authority approves an MRBR, each
approving authority will evaluate proposed changes (as per letter of confirmation) before
approval by the FAA. The corresponding regulatory authority will review published revisions to
the MRBR for possible changes to an operator’s maintenance program.
6-2. TEMPORARY REVISIONS. If temporary revisions (TR) are needed, the OEM/TCH,
ISC and the MRB will convene to evaluate any proposed changes. Submit all proposed changes
with supporting data to the MRB chairperson. Approval or disapproval of the proposed changes
will be processed in the same manner as outlined for the MRBR approval/nonapproval process.
Specifically identify and incorporate all TRs during the next MRBR review process.
a. Title Page. Containing the title of the MRBR and the report number, if any.
b. Table of Contents.
(2) “The requirements in the report have been developed using Maintenance Steering
Group (MSG) decision logic from the current MSG revision (or alternative procedure as agreed
upon by FAA, ISC, or WG).”
(3) “The Federal Aviation Administration (FAA) hereby approves that this report be
used by U.S. certificated operators of the (aircraft make, model, and series).” (Insert page for
each foreign regulatory authority approval, as applicable) Chapter 5 contains sample approval
letters.
d. Record of Revisions.
e. Summary of Changes.
f. List of Effective Pages (including the revision status and corresponding dates).
h. The MRBR Preamble. (The following information should be included in the preamble
of each MRB report.) “This report outlines the minimum scheduled interval/tasking requirements
to be used in the development of an approved maintenance/inspection program for the airframe,
engines (on aircraft), systems, components, and appliances, of (aircraft make, model, and series).
These MRB report requirements are a basis from which each operator develops its own
maintenance/inspection program.”
i. Acronyms. Define all acronyms in the MRBR. Appendix 1 contains a list of acronyms
in the MRBR.
j. Definitions. Include definitions of technical terms in the MRBR. (Refer to Appendix 2.)
Whenever possible, use industry accepted definitions such as those found in the Air
Transportation Association ATA latest version of MSG documents and World Airlines Technical
Operations Glossary.
k. Applicability. The MRBR must identify the specific aircraft make, model, and series,
and the standard options/modifications. New options/modifications as amended by MSG analysis
will be added to the MRBR.
l. Analysis of MSIs and SSIs. Analyze all maintenance significant items (MSI) and
structural significant items (SSI) on a task-by-task basis without regard for letter checks. If a task
is determined to be a safety task or applicable cost effective task, select the appropriate tasking
interval.
(1) The MRBR will provide guidance regarding the means to optimize the minimum
scheduled interval/tasking requirements to a level higher than that provided as initial
requirements in the MRBR. This guidance will be unique to the aircraft model.
(2) Optimization guidance should consider the content of like checks or other related
inspections and their repetitive intervals. A determined series or sequence of specified checks or
other related inspections must be completed and the resultant data found satisfactory before
optimization of that type of check/inspection. Include in this section of the MRBR the
description, type of checks/inspections, and their intervals.
(1) The optimization procedures as described in the Policy and Procedure Handbook,
the following rules applies: Refer to Chapter 12 for optimization details.
(3) Task interval parameters expressed in the MRBR may be converted to an individual
operator’s desired units, provided this conversion does not result in the operator exceeding the
initial requirements of the MRBR.
(4) The use of nondestructive inspection (NDI) methods, such as X-ray, ultrasonic,
eddy current, and radioisotope, or alternative processes that the manufacturer approves, can
provide an alternative to the methods this report prescribes. Each operator should notify its
regulatory authority of the use of an acceptable alternative method.
NOTE: Within this report, the terms “check” and “inspection” are not
intended to imply a level of skill required to accomplish a task.
(5) Life-limited items must be retired in accordance with the limits established in the
engine or aircraft Type Certificate Data Sheets (TCDS) or the Airworthiness Limitations section
of the engine or aircraft OEM/TCH Instructions for Continued Airworthiness.
(6) After the accumulation of industry service experience, the ISC or MRB chairpersons
may request changes to the requirements of this MRBR that the operator may use after approval
of the appropriate regulatory authority.
(7) Failure Effect Category (5 or 8) safety tasks cannot be deleted or escalated without
the approval of the MRB Chairman and/or the Aircraft Certification Office (ACO).
(1) MSG (Specify the revision) logic was used to develop an on-aircraft minimum
scheduled interval/tasking requirement. With the exception of life-limited items, this process
does not normally include detailed shop maintenance procedures. Individual operators control
off-aircraft detailed procedures; they are in accordance with the OEM/TCH published minimum
interval/tasking requirements, which the regulations require.
(2) MSI: The OEM/TCH provides the MSI list in a separate specified document.
(3) Each MSI the OEM/TCH identified has been subjected to MSG analysis. This
process has resulted in the identification of maintenance tasks that are contained in this report.
Each MSI for which a task was not generated during the analysis is identified as follows:
(Provide MSI listing, or other means as specified, for which no tasks were identified.)
(4) SSI. SSIs must not be confused with Principal Structural Elements, (PSE) (Title 14
of the Code of Federal Regulations part 25, § 25.571); however, the SSIs must address all PSEs.
(1) All aircraft in an operator’s, or group of operator’s fleet are subject to the provisions
of this report. These requirements include external and internal inspections, structural sampling
and age-exploration programs, corrosion prevention and control programs, and additional
supplemental structural inspections that may be required for fatigue-related items. Calendar time,
flight cycles, or flight hours express the initial check intervals for the SIP. Do not optimize a
repeat inspection interval until at least one aircraft in an operator’s or group of operator’s fleet
has been inspected within the initially defined interval listed in the MRBR.
(2) All changes to structural inspection items listed in the Airworthiness Limitations
section require FAA engineering approval. Document number in the appropriate appendix will
reference structural inspection limitations listed in the aircraft manufacturer’s Airworthiness
Limitations inspection section in the MRBR.
p. Zonal Program Rules. The Zonal Inspection Program (ZIP) provides for the
consolidation of a number of general visual inspection (GVI) tasks for each zone. A zonal
inspection may include GVI tasks derived from MSI and SSI. An MSI/SSI task that is in the ZIP
must be cross-referenced with supporting documentation and located in the appendix of the
MRB as a zonal item. Likewise, the zonal item must be cross-referenced as an MSI/SSI task to
ensure content and accountability. Include the following contents of the Zonal Procedure Rules
section of the MRBR:
NOTE: Failure Effect Category (5 or 8) safety tasks are not candidates for
zonal requirements.
(1) The ZIP contains a series of GVI tasks. Detailed inspection (DET) and special
detailed inspection (SDI) are not to be contained in the ZIP. Zonal inspection requirements apply
only to zones.
(2) The ZIP contains GVI tasks derived from enhanced zonal analysis procedures
(EZAP).
(a) Identify zones that both contain electrical wiring and have potential for
combustible material being present. For those zones, perform an enhanced zonal analysis that
permits the identification of stand-alone inspection tasks that allow appropriate attention to be
given to deterioration of installed wiring and electrical wiring interconnection system (EWIS),
(b) EWIS tasks derived during the EZAP process will be identified as GVI, DET, or
Restoration (RST) tasks. The ZIP will not contain stand-alone EWIS tasks. These special
dedicated tasks reside in ATA 20 of the Systems/Powerplant section of the MRBR, and do not
have a failure effect category.
(c) Uniquely identify all EWIS/EZAP-derived stand-alone tasks GVI, DET, or RST
in the EZAP analysis for traceability during future changes. This prevents inadvertent deletion or
escalation of an EZAP-derived stand-alone task without proper consideration of the risk basis for
the task and its interval. All escalations must go through the appropriate FAA oversight office.
(d) The latest version of the MSG analysis develops all Lightning and High
Intensity Radiated Field (L/HIRF) GVI tasks. The ZIP will not contain stand-alone L/HIRF
tasks. These special dedicated tasks should reside in a separate section of the MRB. Uniquely
identify all L/HIRF tasks.
(3) Access to zones should be easy to accomplish and should not require the use of
special tools. Normally, the inspection aids include a flashlight and/or inspection mirror. Inspect
the entire visible contents of the zone for obvious damage, security of installation, and general
condition including corrosion and leaks. Refer to latest version of MSG document for an
accurate definition of GVI.
(4) The following zones do not contain system installations, but receive adequate
surveillance from other maintenance or structural inspections tasks. Accordingly, the inspection
requirements in the ZIP do not specify these zones. (Insert listing of the zones not specified in
the ZIP or in other document as specified.) (Insert aircraft zone diagram sheets or in other
document as specified.)
r. Appendices.
8-1. GENERAL. The Maintenance Type Boards (MTB) process permits type certificate (TC)
applicants to develop minimum scheduled interval/tasking requirements when air operators are
not available to participate in the process. The MTB and Maintenance Review Board (MRB)
processes are similar, except with the MTB process there is limited or no operator participation.
MTB maintenance instructions are developed using current Air Transportation Association of
America (ATA) Maintenance Steering Group (MSG) analytic logic. The minimum scheduled
interval/tasking requirements are published as manufacturer recommendations.
a. Where United States is the State of Design. Where the Federal Aviation
Administration (FAA) is the primary type certification authority, the applicant who is seeking a
TC for a new or a derivative aircraft for which this chapter is applicable may develop their
scheduled maintenance instructions in accordance with an MTB or request the Aircraft
Evaluation Group (AEG) to convene an MRB.
b. Where United States is Not the State of Design. A foreign applicant who is seeking,
or intending to seek, an FAA type certificate for a new or a derivative aircraft for which this
chapter is applicable, will invite the FAA AEG to discuss the process under which the scheduled
maintenance instructions have been or will be developed, and how the FAA might accept that
process.
c. Analytic Logic to Use for Scheduled Maintenance Task Development. Use the most
current version of the MSG logic when initiating a new MTB. Electrical wiring interconnection
system (EWIS)/enhanced zonal analysis procedure (EZAP) analysis may be necessary if
applicable by certification rule.
minimum, can be adequately performed and that the procedure meets the intent of the MTBR
task. Additional tasks may be validated at FAA’s discretion.
b. MTBR Review and Approval. The OEM/TCH applicant is responsible for developing
a proposed MTBR and presenting it to the AEG for approval. The MTBR format and content
criteria should be aligned with the criteria used for the Maintenance Review Board report, as
found in Chapter 6. Once approved, the OEM/TCH holder publishes the MTBR as part of the
aircraft’s instructions for continued airworthiness (ICA). It is a means of complying in part with
the maintenance instruction requirements of Appendix H of Title 14 of the Code of Federal
Regulations (14 CFR) part 25, and Appendix A of 14 CFR part 29 as required by part 25,
§ 25.1529 and part 29, § 29.1529. The AEG must approve the MTBR, as well as subsequent
changes, before it becomes available for use by U.S. operators.
NOTE: MTBR tasks will be identified as such in the ICA and can only be
changed through the MTB process.
d. Publication of the MTBR. When an MTBR has been produced, the OEM/TCH will
publish it as part of the ICA for the aircraft.
(2) The OEM/TCH and the MTB will convene and evaluate proposed changes to the
MTBR. Proposed changes and their supporting data are submitted to the MTB chairperson.
Approval or disapproval of the proposed changes must be processed in the same manner as
outlined for the initial MTBR approval/disapproval. Any changes to the MTBR must follow the
optimization process in Chapter 12.
a. General. The OEM/TCH must develop an internal policy and procedures document or
handbook for the purpose of managing the MTB process. The FAA recommends that the format
and content of the Policy and Procedure Handbook (PPH) outline be adopted for the MTB
process (refer to Appendix 3). Present a copy of the PPH to the MTB chairperson for AEG
review and acceptance before beginning any task development work. All participants in the MTB
process are to use the PPH as the standard to conduct the MTB process. Regulatory authority and
industry experience have indicated that the following information is expected in each PPH for
the successful latest version of MSG process and development of a MRBR:
b. Training. Representatives must have undergone training in the analytic logic process to
be used.
(1) Determine the number and type of FAA personnel that are necessary, and then
organize them into an MTB.
(2) Provide the OEM/TCH with the names of FAA/AEG MTB personnel, their
affiliations, assignments, and changes as they occur.
(3) Establish and maintain a file of all MTB proceedings for the MTB historical file.
(5) Ensure that the OEM/TCH provides the necessary technical and analytical logic
training to MTB members/WG advisors.
(9) Review reports from previous SC meetings (if applicable) and from the WG
members.
b. MTB Members. MTB members are expected to meet or have the equivalent experience
and training this chapter requires. In addition, the MTB members are expected to perform the
following functions:
(2) Review WG meeting minutes and provide progress reports to the MTB chairperson
before the next scheduled SC meeting. This review will contain an assessment of WG activities,
including a notification of any controversy or potential problem areas.
(3) Attend SC meetings, as invited by the MTB chairperson, in coordination with the
OEM/TCH.
c. Experience and Training Requisites. MTB members must meet the following levels:
(1) Experience:
(2) Training:
a. United States is the State of Design. The FAA is the primary type certification
authority, the OEM/TCH who is applying for a TC for a new or a derivative aircraft for which
this chapter is applicable may develop its scheduled maintenance instructions in accordance with
a recommended maintenance process.
b. United States is Not the State of Design. A foreign applicant who is applying for an
FAA TC for a new or a derivative aircraft for which this chapter is applicable, will invite the
FAA Aircraft Evaluation Group (AEG) to discuss the process under which the scheduled
maintenance instructions will be developed, and how the FAA may accept that process.
a. Audit of the Completed Analytical Process. All OEM/TCH must maintain records of
the analysis to develop their scheduled maintenance instructions. OEMs/TCHs must keep the
records in such a manner that the FAA may readily audit the analytic process and any subsequent
analytic processes that may lead to an amendment of the minimum scheduled interval/tasking
requirements.
(1) A system for acquiring from operators reports related to adequacy of task, failures,
failure frequencies, and the consequence of the failure.
(3) A system for controlling the addition of new scheduled tasks, to ensure that they are
applicable and effective.
(4) A system for the periodic evaluation of all tasks in the program to eliminate those
that are no longer applicable and effective.
(5) A system for evaluating unanticipated problems and determining the appropriate
action.
10-2. APPLICABILITY. These requirements apply to aircraft that have a Maintenance Review
Board Report (MRBR) and Maintenance Type Board Report (MTBR) or have been analyzed
under the Maintenance Steering Group (MSG) to define the minimum scheduled interval/tasking
requirements.
a. When the aircraft has been analyzed using MSG logic, it is not necessary to revisit the
analysis before applying the proper low-utilization parameter for a task.
11-1. GENERAL. This section addresses flightcrew performing maintenance tasks. Title 14 of
the Code of Federal Regulations (14 CFR) defines people authorized to accomplish maintenance.
Flight crews cannot take credit for any Maintenance Review Board Report/Maintenance Type
Board Report tasks.
12-1. INTRODUCTION. The guidance in this document is intended for use by original
equipment manufacturer(OEM)/type certificate holder (TCH) and Maintenance Review Board
(MRB)/Industry Steering Committee (ISC) members who are involved with the
evolution/optimization or deletion/addition of tasks in an initial/current MRB Report (MRBR).
Apply this guidance for evolution/optimization or deletion/addition activities where no official
correspondence has been forwarded to the airworthiness authorities, or for activities to be
finalized (MRBR proposal submittal) after April 2009. The following is guidance for developing
and assessing proposals to the MRBR.
a. The initial MRBR for any new aircraft is developed in the absence of actual in-service
experience. As a result, the tendency is to be conservative in the decisionmaking process. As
service experience is accumulated, task intervals (thresholds/repeats) should be adjusted to
reflect the results of actual in-service data.
b. The OEM/TCH evolution/optimization process does not assume any operational control
over an operator’s maintenance program.
12-2. PURPOSE. While this guidance is not exhaustive, use it as the basis for a Policy and
Procedures Handbook (PPH) procedure when the OEM/TCH, MRB, and Industry Steering
Committee (ISC) wish to proceed with evolution/optimization regarding the MRBR process.
Evolution/optimization or deletion/addition of a task through the management of data is a means
to assure the continued applicability and effectiveness of the task, while simultaneously
improving the integrity of the MRB process. This policy allows the OEM/TCH to develop and
use a process that serves as a continuous analysis and evolution/optimization or deletion/addition
for the MRBR. It is based on performance data and experience for model-specific fleets flown by
multiple operators under a variety of operating conditions and environments.
12-3. POLICY DESCRIPTION. The OEM/TCH must meet the policy requirements defined by
the regulatory authorities of the country of origin; and will define further details and procedure
clarifications in the PPH. As the PPH is a living document, a response must be given within
60 days after ISC acceptance/OEM submission. The following should occur:
a. The MRB/ISC must coordinate and approve PPH revisions, where applicable.
b. Evaluate in-service data, both scheduled and unscheduled maintenance findings related
to the intent of the Maintenance Steering Group (MSG) task.
d. Standardize data format and content (ATA SPEC 2000 Chapter 11 or equivalent).
k. Use safety management principles at the OEM level. Safety management is the
application of engineering and management principles, criteria and techniques to optimize safety.
It is an integrated and comprehensive engineering effort.
m. The OEM/TCH will collect sufficient data that would support the expected confidence
level. However, engineering judgment will remain a part of the evaluation. Statistical analysis
should be supported and validated by engineering judgment.
n. Measure task effectiveness should be measured and demonstrated, that is, the ability to:
p. Ensure the effectiveness and integrity of the process by: 1) collecting in-service data in
an ATA SPEC 2000 Chapter 11 format or equivalent, 2) analyzing it, and 3) comparing the
results with existing MRBR task requirements.
r. Adjust the MRBR based on performance data and analysis processes. However,
operator reliability programs should continue to ensure continuous evolution/optimization of
their maintenance programs.
s. The OEM/TCH evolution/optimization process does not assume any operational control
over an operator’s maintenance program.
12-4. RESPONSIBILITIES. The OEM/TCH applicant must notify the approving authorities in
writing of their intent to begin an evolution/optimization or deletion/addition process. This will
be in the form of an official correspondence as defined by the approving authorities.
NOTE: Approving authorities are those authorities that approve the MRBR.
The approving authorities will respond, in writing, to the OEM/TCH of their
intent to participate in the evolution/optimization or deletion/addition
exercise for a given fleet or model.
b. OEM/TCH Data Collection. The OEM/TCH system must include a data quality, data
integrity, data quantity, audit system, and historical data tool as defined in the next steps.
c. Data Format. The OEM/TCH will use in-service data in a standardized format (ATA
SPEC 2000 Chapter 11 format, or equivalent), as deemed acceptable by the regulatory authority,
to ensure data quality and integrity. ATA SPEC 2000 Chapter 11 is an industry-sanctioned
maintenance reliability data communication format. In order to use this format, operators would
have to transition to this type of format, or the OEM/TCH would have to convert the operator
data into this standardized format.
12-5. DATA QUALITY. The OEM/TCH should have a system in place that allows for the
collection of data found during operator’s task accomplishment to be delivered to the OEM/TCH
and then entered in a standardized format into their data collection system. The data collected
and used by the OEM/TCH regarding evolution/optimization will include the following
information:
a. Aircraft Age. Aircraft age (since delivery) is measured in calendar days, flight hours,
or flight cycles, as applicable. MRB task evolution will be based on in-service data collected
from a representative sample of older and newer aircraft incorporating more current production
standards and modifications. Fleet age representation will be summarized in the analysis report.
c. Number of Tasks Accomplished. The number of times the task has been accomplished
including “nil/no findings” will be captured and used in the evaluation. Participating operators
should provide task findings and nonroutine write-ups for the related tasks of the sample fleet for
the evolution/optimization or deletion/addition exercise reporting period.
d. Interval of Tasks findings Applied. Actual task interval of each participating operator
will be captured and evaluated.
NOTE: The actual intervals may vary between operators and may be
different from MRBR requirement. The impact of these variations will be
assessed and accounted.
f. Correct Mapping to the MRBR Task. Nonroutine write-ups and in-service findings
should be linked to appropriate MRBR tasks, as applicable. Only findings related to the MSG-3
task intent are relevant.
(1) Routine Maintenance Tasks That Generate No Findings. Tasks that generate no
findings are as important as tasks that generate findings in determining failure-mode and
life-cycle analysis.
(2) Routine Maintenance Tasks That Generate Nonroutine Cards. These findings,
which require corrective action, involve structures, area/zonal, and aircraft systems categorized
by ATA chapter.
m. Four-Digit ATA Code, If Available. To the extent possible, operators should provide
four-digit ATA code for scheduled/unscheduled maintenance write-ups to facilitate transfer of
findings to appropriate MRBR tasks.
n. Serial Number of Aircraft. The operator should provide an aircraft manufacturer serial
number that uniquely identifies each aircraft in the sample fleet.
12-6. DATA INTEGRITY. Data integrity is the quality of correctness, completeness, and
compliance with the intention of the creators of the data. It is the condition in which data are
identically maintained during any operation, such as transfer, storage, and retrieval. Data
integrity is achieved by preventing accidental or deliberate, but unauthorized insertion,
modification, or destruction of data in a database.
a. Data Validation. OEM/TCH must have a data validation process that does the
following:
(1) Verifies that operator data are converted to ATA SPEC 2000 Chapter 11 or
equivalent standard format.
(2) Ensures that all required data elements and attributes are satisfied for submitted
data.
b. Audit System. The audit system must ensure that all data be traceable to the original
task.
b. Statistical Analysis. The OEM/TCH will develop and implement a statistical analysis
system to provide justification that a 95 percent confidence level has been achieved for the
evolution/optimization or deletion/addition exercise on a task-by-task basis. Exceptions can be
presented and may be approved at the discretion of the approving airworthiness authorities.
c. Engineering Analysis. Engineering analysis will verify that findings are relevant to the
scheduled task under evaluation. Nonroutine write-ups will be evaluated to determine the
significance or severity of findings. Pilot reports and component reliability reports will also be
examined to account for line maintenance activities that may be relevant to the task under
evaluation. The severity of the findings must be considered and evaluated.
e. Internal Review. The OEM/TCH will develop and implement internal quality
procedures to review and validate MRBR revision process as defined in the PPH. OEM/TCH
will develop and implement internal processes to validate MRBR revised tasks and/or intervals
resulting from evolution, or demonstrate that an equivalent written internal process already exists
to reach the same intent (not required before April 2010).
12-8. DATA CORRELATION. Correlate mean time between unscheduled removal, mean time
between failures, pilot reports, nonroutines, technical followup on open technical issue, and all
other pertinent data, as applicable.
(1) MRB task intervals can be escalated based on the results of in-service experience. In
addition, tasks should be de-escalated when in-service data support interval reductions. A task
may also be deleted when it is determined that it is ineffective, or the failure mode for which the
task was selected never developed due to effective design provisions.
Page 52 Par12-7
10/29/10 AC 121-22B
(3) The intervals of potential failure finding tasks (i.e., those looking for degradation)
should be less than the shortest likely interval between the point at which a potential failure
becomes detectable and the point at which it degrades into a functional failure. If the specific
failure data are available, this interval may be referred to as the “P to F” interval. Assess
consecutive task accomplishments to show that failures are not occurring before the new initial
interval.
b. ISC Review Acceptance of MRBRP. The ISC will ensure all PPH guidance has been
followed and applied. The MRB will ensure all PPH guidance has been followed and applied.
The MRBR is released.
a. A delivery system of data from the operator to the OEM in an ATA SPEC 2200 format
(or equivalent).
The following is a recommended listing of acronyms and abbreviations that may be contained in
each MRB Report.
AC Advisory Circular
ACO Aircraft Certification Office
AD Accidental Damage/Airworthiness Directive
ADR Accidental Damage Rating
AEG Aircraft Evaluation Groups
AEG-BOS Boston-AEG, Engines, Propellers
AEG-DFW Dallas Ft. Worth-AEG, Rotorcraft
AEG-LGB Long Beach-AEG, Transport Aircraft
AEG-MKC Kansas City-AEG, Small Airplane
AEG-SEA Seattle-AEG, Transport Aircraft
AFS Flight Standards Services
AEP Age Exploration Program
AFRP Aramid Fiber Reinforced Plastic
ALI Airworthiness Limitations
AMM Aircraft Maintenance Manual
AMOC Alternate Means of Compliance
ATA Air Transport Association of America, Inc.
CAM Canadian Airworthiness Manual
CAA Civil Airworthiness Authority
CFR Code of Federal Regulations
CFRP Carbon Fiber Reinforced Plastic
CMCC Certification Maintenance Coordination Committee
CMM Component Maintenance Manual
CMO Certificate Management Office
CMR Certification Maintenance Requirement
CP Corrosion Program
CPCP Corrosion Prevention and Control Program
DAH Design Authority Holder
DET Detailed Inspection
DIS Discard
DSO Design Service Objective
DTA Design Tolerance Assessment
DTR Damage Tolerance Rating
DVI Detailed Visual Inspection
DY Daily
EASA European Aviation Safety Agency
EAPAS Enhanced Airworthiness Program for Airplane
Systems
ECO Engine Certification Office
ED Environmental Deterioration
Page 1
AC 121-22B 10/29/10
Appendix 1
EDR Environmental Deterioration Rating
EICAS Engine Indicating and Crew Alerting System
EROPS Extended Range Operations
ETOPS Extended Two Engine Operations
EWIS Electrical Wiring Interconnection System
EZAP Enhanced Zonal Analysis Procedure
FAA Federal Aviation Administration
FAR Federal Aviation Regulations
FC Functional Check
FCK Functional Check
FD Fatigue Damage
FEC Failure Effect Category
FH Flight Hours
FLT Flight
FMEA Failure Mode and Effects Analysis
FOEB Flight Operations Evaluation Board
FSDO Flight Standards District Office
FTS Fuel Tank Safety
GFRP Glass Fiber Reinforced Plastic
GV General Visual
GVI General Visual Inspection
HIRF High Intensity Radiated Fields
ICA Instructions for Continuing Airworthiness
ICAO International Civil Aviation Organization
IP Issue Paper
ISC Industry Steering Committee
IMRBPB International Maintenance Review Board Policy
Board
JAA Joint Aviation Authorities
JAR Joint Airworthiness Requirement
JOEB Joint Operations Evaluation Board
L/HIRF Lightning/High Intensity Radiated Field
LU Lubrication Task
MEA Maintenance Engineering Analysis
MMEL Master Minimum Equipment List
MFG Manufacturer
MEL Minimum Equipment List
MTB Maintenance Type Board Process
MTBR Maintenance Type Board Process Report
MPD Maintenance Planning Data Document
MPIG Maintenance Program Industry Group
MPP Maintenance Program Proposal
MRB Maintenance Review Board
MRBPB Maintenance Review Board Policy Board
MRB Report Maintenance Review Board Report
Page 2
10/29/10 AC 121-22B
Appendix 1
MSC Maintenance Steering Committee
MSG-1 Maintenance Steering Group - 1st Task Force
MSG-2 Maintenance Steering Group - 2nd Task Force
MSG-3 Maintenance Steering Group - 3rd Task Force
MSI Maintenance Significant Item
MTBF Mean Time Between Failure
MTBUR Mean Time Between Unscheduled Removal
MWG Maintenance Working Group
NDI Non-destructive Inspection
NDT Non-destructive Test
OEM Original Equipment Manufacturer
OPC Operational Check
PI Principal Inspector
PMMEL Proposed Master Minimum Equipment List
PPH Policy and Procedures Handbook
PSE Principal Structural Element
R/I Remove and Install
RF Radiated Frequency
RMP Recommended Maintenance Process (RMP)
RS Restoration Task
RST Restoration
SATO Statistical Analysis Tasking Optimization
SDI Special Detailed Inspection
SID Supplemental Inspection Document
SFAR Special Federal Aviation Regulation
SIP Structural Inspection Procedure
SSA System Safety Assessment
SSI Structural Significant Item
SSID Supplemental Structural Inspection Document
SVC Service Task
STWG Structures Working Group
SWG Structures Working Group
TCH Type Certificate Holder
TBD To Be Determined
TCDS Type Certificate Data Sheet
UV Ultra-Violet
VC Visual Check Task
VCK Visual Check
WG Work Group
ZA Zonal Analysis
ZIP Zonal Inspection Program
ZLWG Zonal Working Group
ZWG Zonal Working Group
Page 3
10/29/10 AC 121-22B
Appendix 2
APPENDIX 2. IP 44 DEFINITIONS
a. Confidence Level. The likelihood that the overall fleet performance lies within the
range specified by the sample fleet performance. The confidence level is usually expressed as a
percentage.
k. Structural Significant Items (SSI). Any detail, element, or assembly that contributes
significantly to carrying flight, ground, pressure or control loads, and whose failure could affect
the structural integrity necessary for the safety of the aircraft.
Page 1
10/29/10 AC 121-22B
Appendix 3
APPENDIX 3. POLICIES AND PROCEDURES HANDBOOK FORMAT
This appendix intends to provide standardized and harmonized policy in the development of a
proper policy and procedures handbook (PPH). It is encouraged that all industry applicant’s PPH
documents be developed containing the same basic data and information, as applicable, to
provide for a complete, consistent, and quality process.
Regulatory authority and industry experience has indicated that the following information is
expected in each PPH, as applicable, for the successful latest version of the Maintenance
Steering Group process and development of a Maintenance Review Board Report:
Contents of PPH
II Record of Revisions
IV History of Changes
Table of Contents
List of Figures
List of Tables
1. Introduction
1.1 Purpose
1.2 Background
Page 1
AC 121-22B 10/29/10
Appendix 3
1.9 Main Principles and Design Standards
1.11.4.1 General
2.1.1 General
Page 2
10/29/10 AC 121-22B
Appendix 3
2.1.3 Communications, Internal and External
2.1.6 OEM/TCH
2.2.1 General
2.3 Documentation
Page 3
AC 121-22B 10/29/10
Appendix 3
3. Systems and Powerplant Analysis Procedures
3.1 General
3.1.2 Handling and Tracking of Task Transfers amongst Systems and Powerplant
WGs
3.2.4 Component Supplier & Maintainability and Reliability Data (MDR) Form
3.4 Responsibilities
3.4.1 OEM/TCH
3.6.1 Introduction
3.6.3 Proposal
Page 4
10/29/10 AC 121-22B
Appendix 3
3.6.4 Revised Process Overview
4.1 General
Page 5
AC 121-22B 10/29/10
Appendix 3
4.5.2 Susceptibility and Residual Strength Matrix
4.10 Responsibilities
4.12 Glossary
Page 6
10/29/10 AC 121-22B
Appendix 3
5. Zonal Analysis Procedures
5.1 General
5.4 Responsibilities
6.1 General
7. Training
Page 7
AC 121-22B 10/29/10
Appendix 3
7.2 MSG Analysis Training
8.1 Purpose
8.2.2 Contents
8.3.1 Contents
8.4.1 MRB Item Numbering Scheme for Systems, Structures & Zonal Tasks
Page 8
10/29/10 AC 121-22B
Appendix 3
Appendix I Advisory Circulars & Regulatory Documents
References
Revision Record
Page 9
10/29/10 AC 121-22B
Appendix 4
APPENDIX 4. RELEVANT FLOWCHARTS AND LETTERS
Page 1
AC 121-22B 10/29/10
Appendix 4
FIGURE 2. OEM/TCH REQUEST FOR AN MRB
Page 2
10/29/10 AC 121-22B
Appendix 4
FIGURE 3. INVITE LETTER TO WG MEMBERS/ADVISORS
Page 3
AC 121-22B 10/29/10
Appendix 4
FIGURE 4. REGULATORY LETTER OF PARTICIPATION
Page 4
10/29/10 AC 121-22B
Appendix 4
FIGURE 5. LETTER OF CONFIRMATION TEMPLATE
IP 83/IMRBPB AI N°05/07
Per (Host NAA guidance), I would like to offer this letter of confirmation regarding the
(TCH aircraft type) aircraft, MRBR revision xx.
As the host country for the (TCH aircraft Type) aircraft we (Host NAA) would like to define our
requirements in accordance with our guidelines, and per the process agreed in the IMRBPB
IP 83, for guest signatories’ regulatory authorities. This letter will serve as the confirmation letter
outlining our working relationship with your NAA. The guest signatory’s regulatory authorities
will perform the following functions regarding the (TCH aircraft Type) Aircraft MRB activities:
1. Participate in the development and acceptance of the PPH. Any NAA regulatory differences
will be defined in an appendix to the PPH.
2. (Guest NAA] will coordinate all requested PPH changes through the (Host NAA) MRB
chairperson.
3. Participate in the MRB WG activities; inform the (Host NAA) work group advisor of any
national regulatory or technical differences. The (Host NAA) advisor will ask for regulatory
concurrence. Any non-concurrence will be documented in the meeting minutes. In addition, any
regulatory differences between the host country and signatory authorities at the completion of the
MSG-3 process would be documented in a separate MRBR appendix.
4. The (Host NAA) advisor will ensure the conversation or debate over an issue ends in a timely
fashion to ensure the completion of WG activities in the allotted time.
5. Attend ISC meetings by invitation from the ISC chairperson released through TCH in
coordination with of the (Host NAA) MRB chairperson.
6. Notify the ISC chairperson, via the (host) MRB chairperson of any national regulatory
differences before compiling the MRBR proposal.
The final responsibility of the (Guest NAA) will be to coordinate with the (Host NAA), the
(Guest NAA) MRBR approval and appendixes, if applicable.
Sincerely,
Host NAA
Page 5