# AC 120-125: Development and Use of an Operator's MEL, NEF Program, and CDL for Operations Under 14 CFR Parts 91K, 121, 125, and 135

- Type: Advisory circular (guidance, not mandatory unless a rule or AD requires it)
- Status: Current
- Approved: November 1, 2023
- Last reviewed: November 3, 2023
- Family: AC 120-125
- 14 CFR parts: 91, 121, 125, 135
- Pages: 55
- PDF: https://openairdocs.org/files/sha256/b3/e0/b3e02a2720dd36c3091f314447ed4ef820d293a5c4da5359306d5092f2eba4c4
- FAA DRS: https://drs.faa.gov/browse/excelExternalWindow/DRSDOCID153620530720231103142355.0001
- DRS record last changed: November 21, 2025
- Page: https://openairdocs.org/ac/120-125

## Versions

- [AC 120-125](https://openairdocs.org/ac/120-125) (Current), approved Nov 1, 2023, 55 pages

## Text

Each page's text from the PDF; open the PDF at a page with #page=N. Some pages are OCR from the scanned FAA advisory circular. OCR can misread letters and numbers. Those pages are marked (OCR).

### Page 1

U.S . Department of Transportation Federal Aviation Administration Advisory Circular Subject: Development and Use of an Operator’s MEL, NEF Program, and CDL for Operations Under 14 CFR Parts 91K, 121, 125, and 135 Date: 11/1/23 AC No: 120-125 Initiated by: AFS-200 Change:

This advisory circular (AC) provides information for operator development and use of a minimum equipment list (MEL), MEL management program, nonessential equipment and furnishings (NEF) program, and Configuration Deviation List (CDL). This AC applies to all operators subject to Title 14 of the Code of Federal Regulations (14 CFR) parts 91 subpart K (part 91K), 121, 125, and 135. The use of an MEL should only be authorized through the issuance of Operations Specification (OpSpec) or Management Specification (MSpec) D095, Minimum Equipment List (MEL) Authorization, as appropriate. This AC does not address operations conducted under part 91, § 91.213 with inoperative instruments or equipment without an MEL.

This AC describes an acceptable means, but not the only means, for an operator to develop and use t heir MEL, NEF, and CDL in accordance with regulatory requirements and Federal Aviation Administration (FAA) policy. The contents of this document do not have the force and effect of law and are not meant to bind the public in any way, and the document is intended only to provide information to the public regarding existing requirements under the law or agency policies.

Wesl ey L. Mooty Acting Deputy Executive Director, Flight Standards Service

### Page 2

ii

CONTENTS Paragraph Page

Chapter 1. Introduction … 1-1

1.1 P urpose of This Advisory Circular (AC) … 1-1

1.2 Audience … 1-1

1.3 Where You Can Find This AC … 1-1

1.4 B ackground … 1-1

1.5 Nonessential Equipment and Furnishings ( NEF) Program … 1-2

1.6 Configuration Deviation List (CDL) … 1-2

1.7 Terminology … 1-2

1.8 Regulatory Requirements … 1-8

1.9 O pSpec/MSp ec D095 Requirements … 1-9

1.10 Foreign Air Carriers and Foreign Operators of U.S.-Registered Aircraft

Engaged in Common Carriage (14 CFR Part 129) … 1-9

1.11 AC Feedback Form … 1-9

Chapter 2. M inimum Equipment List (MEL)—General … 2-1

2.1 G eneral … 2-1

2.2 Categories of MEL Items … 2-1

2.3 Limitations of MEL Deferrals … 2-1

2.4 Required Sections … 2-2

2.5 Optional Sections … 2-3

Chapter 3. M inimum Equipment List (MEL)—Content … 3-1

3.1 M EL Contents … 3-1

3.2 Air Transport Association of America (ATA) or Joint Aircraft

System/Component (JASC) Coded Sections … 3-1

3.3 Repair Categories … 3-2

3.4

Number of Items Installed … 3-2

3.5 Number Required for Dispatch … 3-3

3.6 Remarks or Exceptions … 3-3

3.7 MEL Remarks and Exceptions Defined … 3-4

3.8 MEL Proviso Stipulations Should Be Specific … 3-4

3.9 (M) and (O) Procedures … 3-4

3.10 Provisos … 3-5

### Page 3

iii

3.11 Notes … 3-5

3.12 Definitions … 3-6

3.13 References … 3-6

3.14 Specific 14 CFR Requirements … 3-7

Chapter 4. M EL Relief for Items Installed After Type Certification … 4-1

4.1 G eneral … 4-1

4.2 Operator NEF Items or Administrative Control Items (ACI) … 4-1

4.3 MMEL Items and MEL Items … 4-1

4.4 STC … 4-1

4.5 Adding Relief for Items Installed After Type Certification … 4-2

4.6 Items Needed for Evaluation of Design Changes … 4-3

Chapter 5. MEL Management Program Requirements … 5-1

5.1 G eneral … 5-1

5.2 MEL Management Program … 5-1

5.3 Continuing Authorization—Single Extension … 5-1

5.4 Additional Extensions … 5-2

Chapter 6. Conducting Operations Utilizing MEL Relief … 6-1

6.1 G eneral. … 6-1

6.2 Operational Requirements … 6-1

6.3 Dispatch or Flight Release Requirements … 6-2

6.4 Multiple Inoperative Items or System Components … 6-3

6.5 Availability of the MEL to Operator Personnel … 6-4

Chapter 7. MEL Creation and Formatting … 7-1

7.1 G eneral … 7-1

7.2 M EL Format Outline … 7-1

7.3 Prohibited Items … 7-3

7.4 MEL Restrictions … 7-3

7.5 Fleet MELs … 7-3

Chapter 8. FAA Review and Initial Approval of an Operator’s MEL … 8-1

8.1 General … 8-1

8.2 Preliminary … 8-1

### Page 4

iv

8.3 Submission … 8-1

8.4 Review and Findings of an Operator’s MEL Submission … 8-2

8.5 MEL Management Program Review … 8-3

8.6 Correction of Deficiencies … 8-4

8.7 Approval and Issuance of OpSpec/MSpec D095 … 8-4

Chapter 9. MEL Revisions … 9-1

9.1 G eneral … 9-1

9.2 FAA-Initiated Revisions … 9-1

Figur e 9- 1. Example Global Change Header Box … 9-3

9.3 O perator- Initiated Revisions … 9-3

Chapter 10. Nonessential Equipment and Furnishings (NEF) Program … 10-1

10.1 B ackground … 10-1

10.2 General … 10-1

10.3 D eferral Authority … 10-2

10.4 NEF Program Development … 10-2

10.5 Required NEF Program Contents … 10-2

F igure 10-1. Required NEF MEL Proviso for an FAA-Approved NEF Program … 10-4

10.6 N EF Program Approval … 10-4

10.7 NEF Program Revisions … 10-5

10.8 Criteria for Selection of NEF Items … 10-5

F igure 10- 2. NEF Item Selection Criteria Elements Flowchart … 10-7

Chapter 11. Configuration Deviation List (CDL) … 11-1

11.1 P urpose of the CDL … 11-1

11.2 D evelopment … 11-1

11.3 Operator Use of the CDL … 11-1

11.4 Operator’s Manual … 11-2

11.5 CDL Item Recording and Notifications … 11-2

### Page 5

**1-1 CHAPTER 1. INTRODUCTION**

1.1 Purpose of This Advisory Circular (AC). This AC provides clarity on minimum equipment list (MEL), nonessential equipment and furnishings (NEF) program, Configuration Deviation List (CDL), and certain Federal Aviation Administration (FAA) requirements regarding the operation of aircraft with inoperative instruments and equipment.

1.1.1 Effects of Guidance. The contents of this document do not have the force and effect of law and are not meant to bind the public in any way, and the document is intended only to provide information to the public regarding existing requirements under the law or agency policies.

1.2 Audience. This AC applies to all operators under Title 14 of the Code of Federal Regulations (14 CFR) parts 91 subpart K (part 91K), 121, 125, and 135.

1.3 Where You Can Find This AC. You can find this AC on the FAA’s website at https://www.faa.gov/regulations_policies/advisory_circulars and the Dynamic Regulatory System (DRS) at https://drs.faa.gov.

1.4 Background. An aircraft’s airworthiness certificate is based on it conforming to its type certificate (TC) and being in a condition for safe operation. While items installed in an aircraft have to be operative for the aircraft to meet TC requirements, an approved MEL allows an operator to operate the aircraft with certain inoperative items for a limited, defined period. An approved MEL, as authorized by the operations specification (OpSpec)/management specification (MSpec), constitutes an approved change to the type design without requiring recertification.

1.4.1 Under part 91, § 91.7, an operator cannot operate an aircraft unless it is in an airworthy condition. To be airworthy under § 91.213, the aircraft must comply with the TC and be in a condition for safe operation. To operate an aircraft with an inoperative instrument or equipment violates § 91.7, unless the inoperative item or equipment is listed on the operator’s approved MEL, in accordance with § 91.213. As such, compliance with all applicable MEL criteria is necessary when taking advantage of the relief that an MEL provides; in the absence of such compliance, the aircraft is not airworthy.

1.4.2 The FAA developed the MEL concept after it recognized that, under certain circumstances, a flight or series of flights might occur safely with certain inoperable instruments and equipment. In certain situations, an Acceptable Level of Safety (ALoS) can be met because not all of an aircraft’s installed instruments and equipment are necessary for every type of operation. For example, a flight that is not being conducted in icing conditions would not require operable airframe deicing or anti-icing equipment.

Similarly, an aircraft that will not operate at night may receive relief from the requirement to have an operable landing light.

1.4.3 All articles, commonly referred to as items, related to aircraft airworthiness that are not included in an approved MEL are required under § 91.213 to be operative in accordance

### Page 6

1-2 with the aircraft’s TC. An MEL does not include obviously required items, such as wings, rudders, flaps, engines, landing gear, etc.

1.4.4 The MEL requirements and related processes are independent from an aircraft’s operating requirements and an MEL cannot authorize a deviation from operating rules.

An aircraft is not airworthy when any item that is not included in the MEL is inoperative.

1.4.5 The MEL is not intended to enable the continued operation of the aircraft with inoperative items for an indefinite period of time. The MEL’s basic purpose is to allow limited operations of aircraft with inoperative equipment within the framework of a well-defined program. This program should be proactively managed by the operator and should ensure that repairs are made as soon as practicable to avoid further operational impact.

1.4.6 An MEL is developed by the operator for their particular operations (e.g., parts 91K, 121, 125, and/or 135). An MEL is typically developed from a Master Minimum Equipment List (MMEL) for the aircraft type. The operator uses the MMEL as the baseline to develop the MEL and the operational and maintenance procedures. The MEL lists the items installed in the operator’s aircraft and is submitted to the responsible FAA Flight Standards office.

1.5 Nonessential Equipment and Furnishings (NEF) Program. An operator’s MEL program may also include an NEF program that allows relief for nonessential items. An NEF program allows an operator to operate an aircraft without the use of nonessential items based on the approved OpSpec/MSpec. See Chapter 10, Nonessential Equipment and Furnishings (NEF) Program, for additional information on NEF programs.

1.6 C onfiguration Deviation List (CDL). A CDL is a list of externally exposed aircraft parts that may be missing for flight. A CDL allows continued operation with missing externally exposed nonstructural parts by defining restrictions, limitations, or performance penalties, while the aircraft remains airworthy. See Chapter 11, Configuration Deviation List (CDL), for additional information on the CDL.

1.7 T erminology.

1.7.1 A ir Transport Association of America (ATA) . The use of the term “ATA coded sections” refers to the ATA codes, which were first published in 1956 as a standardized numbering system for aircraft systems. ATA changed its name to “Airlines for America” (A4A) in 2011, but the acronym “ATA” is still used for coded aircraft systems. The acronyms “ATA” and “A4A” are interchangeable.

1.7.2 Administrative Control Item (ACI). An ACI is an item that is not contained in the MMEL, but that may be included in the operator’s MEL for tracking and informational purposes only. For example, an ACI may be used to track the accomplishment of required auxiliary power unit (APU) cold-soak, or in-flight verification starts for Extended Operations (ETOPS) aircraft. See Chapter 2, Minimum Equipment List (MEL)—General, for additional information regarding ACI.

### Page 7

1-3

1.7.3 Aircraft Evaluation Division (AED). FAA AED inspectors serve as the FAA Flight Standards Service (FS) technical subject matter experts (SME) for operational and engineering activities. They coordinate and assist with aircraft certification and continued airworthiness programs and serve as a liaison with the responsible Aircraft Certification Service office during an aircraft’s initial certification and throughout its service life.

1.7.4 A irplane Flight Manual (AFM)/Rotorcraft Flight Manual (RFM) or Pilot’s Operating Handbook (POH). The FAA-approved AFM/RFM (or POH) is an FAA-approved document that contains information (e.g., operating limitations, operating procedures, performance information, etc.) necessary to operate the aircraft (airplane or rotorcraft, as appropriate) at the level of safety established by the aircraft’s certification basis. It is approved by the responsible Aircraft Certification Service office during type certification.

The approved flight manual for the specific aircraft is listed on the applicable Type Certificate Data Sheet (TCDS). The approved flight manual is the governing document for operational limitations and performance parameters for an aircraft. The term “approved flight manual” can apply to an AFM/RFM (or POH). The FAA requires an approved flight manual for aircraft type certification. Refer to 14 CFR part 21, § 21.5;

part 23, § 23.2620; part 25, § 25.1581; part 27, § 27.1581; and part 29, § 29.1581. The applicable document (AFM, RFM, or POH) should be indicated in the aircraft operator’s MEL when applicable.

1.7.5 C onfiguration Deviation List (CDL). A CDL is a list of exposed (external) aircraft parts that may be missing for flight under specific conditions and limitations. CDLs are developed by aircraft manufacturers for each specific model and approved by the FAA.

1.7.6 C onsidered Inoperative. The phrase “Considered Inoperative,” as used in the “Remarks or Exceptions” column, means an item should be treated for dispatch, taxi with intent for flight, and flight purposes as though it were inoperative. “Inoperative” refers to the malfunction of an item to the extent that it does not accomplish its intended purpose or is not consistently functioning normally within its approved operating limit(s) or tolerance(s), or both. The item will not be used or operated until the original deferred item is repaired. Additional actions include documenting the item on the dispatch release (if applicable); placarding; complying with all remarks or exceptions, including any maintenance and operations procedures; considering applicable notes; and observing the repair category.

1.7.7 D ash ( -). A dash indicates a variable number (quantity) of items may be installed or required for dispatch.

1.7.8 D ay of Discovery. This is the calendar day an item malfunction was recorded in the aircraft maintenance record or logbook and is excluded from the interval established by the assigned repair category.

1.7.9 D eactivated (or Secured) . When the MEL refers to an item as “deactivated” or “secured,” or both, the specified item must be put into an acceptable condition for safe flight (refer to § 91.7). An acceptable method of deactivating or securing may be recommended by the manufacturer or established by the aircraft operator.

### Page 8

1-4

1.7.10 D eferral. A deferral is t he term used to describe the authorization for an operator to delay repair and continue operating with a required item inoperative, under the authority of its FAA-approved MEL. Authority to defer repair of an inoperative item is subject to specific conditions and limitations, as described in the associated proviso.

1.7.11 Deleted. “D eleted” in the “Remarks or Exceptions” column indicates the item was previously listed, but is no longer addressed by the MMEL.

1.7.12 Dynamic Regulatory System (DRS) . DRS is an FAA website that contains regulatory, policy, and guidance information. DRS can be accessed through the FAA home page or at https://drs.faa.gov.

1.7.13 Excess Items. Excess items are items that have been installed in a quantity greater than that required by 14 CFR.

1.7.14 Extended Operations (ETOPS). ETOPS is an a irplane flight operation, in an airplane with two or more engines that complies with the part 25 ETOPS requirements, during which a portion of the flight is conducted with an extended Maximum Diversion Time, as defined by § 121.7.

Note: To obtain ETOPS approval, the specific airplane/engine combination must be certificated to required ETOPS and transport category standards. Refer to §§ 25.3 and 121.162 and part 135 appendix G.

1.7.15 Flight-Day. A flight-day is a 24-hour period (from midnight to midnight) either in Coordinated Universal Time (UTC) or local time, as established by the aircraft operator, during which at least one flight is initiated for the affected aircraft.

1.7.16 Flight Standards Service (FS). FS is the FAA office that promotes safe air transportation by setting the standards for certification and oversight of airmen, air operators, air agencies, and designees. FS promotes safety of flight of civil aircraft and air commerce by, amongst others:

• Acco mp lishing certification, inspection, surveillance, investigation, and enforcement;

• Setting regulations and standards; and

• Managing the system for registration of civil aircraft and certification of airmen.

1.7.17 F light Operations Evaluation Board (FOEB). An FOEB is a group of technically qualified specialists, engineering representatives, and FAA AED aviation safety inspectors (ASI) responsible for developing MMELs from the one proposed by the aircraft manufacturer. An aircraft MMEL is usually developed during initial aircraft certification. The FOEBs are also responsible for developing MMEL revisions.

1.7.18 Global Change (GC). A GC is newly developed or changed relief for an item, usually applicable to numerous MMELs (hence “global”) to allow operators to obtain MEL relief prior to the release of a revised MMEL. Incorporation of a GC into an operator’s MEL is optional, until the GC is incorporated in the aircraft’s MMEL. GCs may be used to

### Page 9

1-5 provide immediate relief for items required by a new regulatory requirement, policy change, or new technology.

1.7.19 Ite m. An item is an instrument, equipment, system, component, message, or function that is installed on or exhibited by the aircraft.

1.7.20 ATA iSpec 2200. A suite of data specifications and modules for the digital representation and exchange of technical data. The iSpec 2200 system incorporates previous ATA 100 and 2100 specs with improved structure and content of aircraft system and component nomenclature. This minimizes the cost and effort expended by operators and manufacturers in managing inventory.

1.7.21 Joint Aircraft System/Component (JASC) Code. The JASC code is a modified version of the ATA code developed by the FAA to address the need for an international standardization of aircraft system codes. It uses a four-digit format along with an abbreviated code title. For additional information, refer to the FAA Joint Aircraft System/Component Code Table and Definitions at https://avinfo.faa.gov/sdrx/documents/JASC_Code.pdf. (Also refer to i Spec 2200.)

1.7.22 Maintenance (M) Procedure. An (M) abbreviation indicates a requirement for a maintenance procedure that must be accomplished prior to operation with the listed item inoperative. Normally, these procedures are accomplished by maintenance personnel;

however, other personnel may be qualified and authorized to perform certain functions.

Procedures requiring specialized knowledge or skill, or requiring the use of tools or test equipment, should be accomplished by maintenance personnel. Appropriate procedures are required to be produced as a part of the aircraft operator’s manual or MEL. See (M) and (O) procedures in Chapter 3, Minimum Equipment List (MEL)—Content, paragraph 3.9.

1.7.23 Master Minimum Equipment List (MMEL).

1.7.23.1 An MMEL is a type-specific master list of aircraft items that may be inoperative under certain conditions while maintaining the aircraft’s airworthiness and an ALoS. All MMELs are developed and revised by the FOEB, receive concurrence from the FAA Safety Standards divisions (the Air Transportation Division, the Aircraft Maintenance Division, and the General Aviation and Commercial Division) and are approved by the AED manager.

An MMEL is the document on which an operator bases its MEL. All MMELs are located in the FAA DRS website.

1.7.23.2 The United States may enter a Bilateral Aviation Safety Agreement (BASA) with a foreign government when there is a need for technical cooperation with the foreign government’s Civil Aviation Authority (CAA), and if the foreign authority’s civil aviation safety oversight is substantially comparable to that of the FAA. BASAs are implemented through associated procedures. Refer to country-specific BASAs for MMEL considerations relating to foreign type-certificated aircraft validated under Implementation Procedures for

### Page 10

1-6 Ai rworthiness (IPA). The BASAs and associated IPAs may be found at http s://www.faa.gov/aircraft/air_cert/international/bilateral_agreements/. This information may be helpful for MMEL/MEL development and FAA TC or Supplemental Type Certificate (STC) application packages.

1.7.24 MMEL Policy Letters (PL ). PLs clarify FAA MMEL policy regarding specific kinds of equipment that may be deferred. While developing its MEL, an operator may need to refer to one or more aircraft or equipment-specific PLs with a GC designation, as these PLs may provide additional relief for items until the MMEL is revised. PLs are available under the “MELs and AED Guidance Documents” tab on DRS.

1.7.25 Make/Mod el/Series (M/M/S). M/M/S is a common abbreviation used when referring to a manufacturer’s particular model or type and series of given aircraft.

1.7.26 Managemen t Specification (MSpec). An MSpec is an authorization issued to part 91K operators by the FAA Administrator via a Letter of Authorization (LOA). An MSpec is equivalent to the OpSpec issued to part 121 or 135 operators.

Note: For the purposes of this AC , the term “OpSpec/MSpec” is used. (See “Operations Specification (OpSpec)” below.)

1.7.27 Minimum Equipment List (MEL). An MEL is an operator-speci fic, FAA-approved document that includes a list of items that may be inoperative during a flight. An MEL constitutes an approved change in the aircraft type design.

1.7.28 Moved. “Moved” in the “Remarks or Exceptions” column indicates the item was moved to a different chapter in the MMEL or an FAA-approved document.

1.7.29 Nonessential Equipment and Furnishings (NEF). NE Fs are those items installed on the aircraft as part of the original TC, STC, Engineering Order (EO), or other form of alteration that have no effect on the safe operation of flight, and would not be required by the applicable certification rules or operational rules. They are those items that, if inoperative, damaged, or missing, have no effect on the aircraft’s ability to be operated safely under all operational conditions. NEF items are not instrument and equipment items already identified in the MEL or CDL of the applicable aircraft. They do not include instrument and equipment items that are functionally required to meet the certification rule or for compliance with any operational rule. See Chapter 10 for additional information on an NEF program.

1.7.30 Note(s). No tes provide additional information for crewmember or maintenance consideration. Notes are used to identify applicable material which is intended to assist with compliance but do not relieve the aircraft operator of the responsibility for compliance with all applicable requirements. Additional notes may be amended, deleted, or added to the MEL by the aircraft operator, as appropriate. Notes are not a part of the provisos.

1.7.31 Number Installed. Th is column indicates the number (quantity) of items normally installed in the aircraft. This number represents the aircraft configuration(s) considered in

### Page 11

1-7 developing an MMEL. If the number is variable or impractical to determine

(e.g., optional equipment, fleet configuration differences, cockpit or cabin lighting items, cargo restraint components, flight data recorder (FDR) parameters), a number is not required and the dash “-” symbol is used instead. A dash or “N/A” (not applicable) may also be used for en route flight advisory service (EFAS) message relief.

1.7.32 Number Required for Dispatch. This column indicates the minimum number (quantity) of items required for operation, providing the conditions specified in the “Remarks or Exceptions” column are met. Where the MMEL shows a variable number “-” required for dispatch, the aircraft operator’s MEL may reflect the actual number required for dispatch or an alternate means of configuration control approved by the Administrator. An aircraft operator’s MEL may contain a “-” where the number required is based on the conditions of flight, such as adequate cockpit lighting or when operations are conducted under more than one set of operating rules.

1.7.33 O perations (O) Procedure. This symbol indicates a requirement for a specific operations procedure that must be accomplished in planning for or operating with the listed item inoperative. Normally, these procedures are accomplished by the flightcrew; however, other personnel may be qualified and authorized to perform certain functions. The satisfactory accomplishment of all procedures, regardless of who performs them, is the responsibility of the aircraft operator. Appropriate procedures are required to be produced as a part of the aircraft operator’s manual or MEL.

1.7.34 O perator. This AC uses the singular term “operator” for simplicity. Unless otherwise noted, the term “operator” when used in this AC applies to a program manager conducting part 91K operations or a certificate holder conducting operations under part 121, 125, or 135, as applicable.

1.7.35 O perations Specification (OpSpec) . An OpSpec is a document issued under 14 CFR part 119 to parts 121, 125, and 135 operators that contains the authorizations, limitations, and certain procedures under which each kind of operation, if applicable, is to be conducted; and certain other procedures under which each class and size of aircraft is to be operated.

1.7.36 P rincipal Inspector (PI). PIs are FAA personnel, within the operator’s responsible Flight Standards office, who are assigned primary responsibility for oversight of an operator’s safety of operations. PIs specialize in the three general areas of aircraft operations according to their qualifications: Avionics (PAI), Maintenance (PMI), and Operations (POI). PIs have FAA administrative authority to evaluate and approve an operator’s manuals, including the MEL.

1.7.37 P roviso. A proviso is used to stipulate conditions or limitations that must be complied with for operation with the listed item inoperative.

1.7.38 R emarks or Exceptions . The “Remarks or Exceptions” column includes the Maintenance (M) and Operations (O) indicators, a statement either prohibiting or permitting operation with a specific number of items inoperative, provisos, and appropriate notes.

### Page 12

1-8

1.7.39 Responsible Aircraft Certification Service Office. The Aircraft Certification Service office performs aircraft certification duties and administers most type certification and continuous airworthiness program activities.

1.7.40 R esponsible Flight Standards Office. The Flight Standards office with oversight responsibility of an operator’s MEL and MEL management program. The term applies to a Certificate Management Office (CMO), Flight Standards District Office (FSDO), or an International Field Office (IFO).

1.7.41 S afety Assurance. Safety assurance is one of the four components of the Safety Management System (SMS), whereby an operator develops and maintains processes to monitor the safety performance of the organization.

1.7.42 S afety Management System (SMS) . SMS is the formal, top-down, organization-wide approach to managing safety risk and assuring the effectiveness of safety risk controls. It includes systematic procedures, practices, and policies for the management of safety risk.

An SMS program is required for part 121 operators in accordance with 14 CFR part 5.

Other operators may choose to implement SMS voluntarily.

1.7.43 S afety Risk Management (SRM) . SRM is a formal process of controlling safety risk by identifying hazards and analyzing and controlling risk. SRM is one of the four components of SMS, the others being safety policy, safety assurance, and safety promotion. SRM requires an accurate description of the application of the system, or subsystem, risk management principles, and processes.

1.7.44 S upplemental Type Certificate (STC) . An STC is issued by the FAA to a person who applies for a major change to a type design when the proposed change does not require an application for a new TC under § 21.19. The STC, which incorporates by reference the related TC, approves not only the modification, but also how that modification affects the original design.

1.7.45 T akeoff. For the purposes of MEL relief, takeoff is considered to be the point at which the pilot physically begins to apply power to initiate the takeoff from the runway or takeoff surface.

1.7.46 T riple Asterisk (***). The triple asterisk in the “Item” column indicates an item that may have been installed on some but not all aircraft covered by an MMEL. This item may be included in the aircraft operator’s MEL after the approving office has determined the item has been or will be imminently installed on one or more of the aircraft operator’s aircraft. This symbol, however, should not be carried forward into the aircraft operator’s MEL. It should be noted that neither this policy nor the use of this symbol provides authority to install or remove an item from an aircraft.

1.7.47 V ertical Bar (Change Bar) . A vertical bar indicates a change, addition, or deletion of content in the adjacent row(s) of text for the current revision of that page only.

1.8 Regulatory Requirements. Regulatory requirements for parts 91K, 121, 125, and 135 operations, in accordance with §§ 91.1115, 121.628, 125.201, and 135.179, as applicable,

### Page 13

1-9 indicate that no person may take off an aircraft with inoperable items unless there is an FAA-approved MEL for the aircraft and the operator fulfills certain other requirements.

For example, operators must:

1. Have authorization in OpSpec/MSpec D095, Minimum Equipment List (MEL) Authorization, to conduct operations using their approved MEL.

2. Provide the flightcrews with direct access, at all times prior to flight, to all of the information contained in the approved MEL through printed or other means approved by the Administrator in the OpSpec or MSpec.

1.9 OpSpec/MSpec D095 Requirements. An operator may request a D095 MEL authorization by submitting to the FAA a comprehensive MEL management program that addresses the management and repair of instruments and equipment listed in their FAA-approved MEL. The documents or manuals in the operator’s document system include a description of the program. For more information on the MEL management program, see Chapter 5, MEL Management Program Requirements. A D095 MEL authorization contains the following:

• A listing of authorized aircraft;

• A description of the maximum times between deferral and repair (repair categories);

• An MEL management program for managing the repair of the items listed in the FAA-approved MEL; and

• Conditions for continuing authorization–single extension.

1.10 Foreign Air Carriers and Foreign Operators of U.S.-Registered Aircraft Engaged in Common Carriage (14 CFR Part 129). Refer to AC 129-4, Maintenance Programs for U.S.-Registered Aircraft Operated Under 14 CFR Part 129, for information regarding their MELs.

1.11 AC Feedback Form. For your convenience, the AC Feedback Form is the last page of this AC. Note any deficiencies found, clarifications needed, or suggested improvements regarding the contents of this AC on the Feedback Form.

### Page 14

**2-1 CHAPTER 2. MINIMUM EQUIPMENT LIST (MEL)—GENERAL**

2.1 General. An MEL allows an operator to continue to operate an aircraft with inoperative items for a period of time, or to reposition it to a place where repairs can be made. It is important that repairs be accomplished at the earliest opportunity. An operator uses the MMEL applicable to an aircraft make/model/series (M/M/S) to develop its own MEL. An FAA-approved MEL may be more restrictive than the MMEL, but never less restrictive.

An operator’s MEL is approved by the Principal Operations Inspector (POI) at the operator’s responsible Flight Standards office. Per § 91.213, all changes to the MEL must be approved by the FAA prior to taking effect.

2.2 Categories of MEL Items. Three categories of items may be contained in an operator’s MEL: items specified in the MMEL, NEF items, and administrative control items (ACI).

2.2.1 MMEL Items. The MEL lists all of the MMEL items for which the operator desires relief, based on the operator’s specific aircraft configuration and type of operation.

2.2.2 N EF Program . The operator’s NEF program may be included in the MEL or a subset of the MEL, and consists of a list of NEF items; the process for evaluating each item in accordance with NEF requirements, reporting procedures, and repair or replacement policy and procedures. The NEF program may be appended to the MEL or it may exist separately within the operator’s manual system.

2.2.3 Ad m inistrative Control Items (ACI). An ACI is listed by the aircraft operator in the MEL for tracking and informational purposes. As an example, ACI may be used to track Extended Operations (ETOPS) accomplishment of required auxiliary power unit (APU) cold-soak, or in-flight verification starts. An ACI may be added to an aircraft operator’s MEL by approval of the POI, provided no relief is granted, or provided conditions and limitations are contained in an approved document (e.g., Structural Repair Manual or Airworthiness Directive (AD)). If relief other than that granted by an approved document is sought for an ACI, a request must be submitted to the Administrator. If the request results in review and approval by the Flight Operations Evaluation Board (FOEB), the item becomes an MMEL item rather than an ACI. Furthermore, with regards to ACIs:

1. The listing of an ACI in its MEL is subject to POI approval.

2. ACIs should either be listed in the MEL systems section under the appropriate Air Transport Association of America (ATA) number section or be listed in a separate chapter reserved for ACIs.

3. An ACI can list all of the conditions and limitations included in the operator’s approved or accepted manual, or could include a reference to all such manuals.

2.3 Limitations of MEL Deferrals. An operator’s MEL may not be less restrictive than the MMEL, the applicable requirements in 14 CFR, the operator’s operations specifications (OpSpecs)/management specifications (MSpecs), applicable AD, or the Airplane Flight Manual (AFM)/Rotorcraft Flight Manual (RFM) limitations and emergency procedures.

### Page 15

2-2

2.4 Required Sections. As technology in aviation evolves, traditional pages may become digital sections or subsections of flowing text. As such, content may be presented and tracked differently in digital format compared to print. The following MMEL-based elements must be in an operator’s MEL, but may be presented according to the operator’s style and system output capabilities. The MMEL format outline contains eight sections, six of which must be in the operator’s MEL:

2.4.1 Table of Contents. The table of contents includes a sequential list of all the content in the MEL, by section, subsection, paragraph, or title, and includes the corresponding location identifier or page identification. The format may vary based on the operator’s manual system preferences.

2.4.2 L og of Revisions. The log of revisions contains the revision identification (usually a number) and the date of the revision. It may also contain a list of the revised pages, a block for the initials of the person posting the change, and additional enhancements for use by the operator. The format may vary based on the operator’s manual system preferences.

2.4.3 D efinitions . A list of definitions of terms used in MMELs and MELs is found in MMEL PL-25. For operator MELs, certain MMEL definitions may be edited or may be omitted if the element is not used in the operator’s MEL. MEL definitions will be tailored, as appropriate, including content and format, dependent upon the aircraft operator’s make/model (M/M) of aircraft, type of installed items, and specific operation.

However, the intent of the definition must be the same and cannot be less restrictive than the MMEL.

2.4.4 P reamble . The standard MMEL preamble should be reproduced verbatim in each MEL, should not be modified, and should comply with the policy requirements included in FAA MMEL PLs. Operators conducting part 91K, 121, 125, or 135 operations should use the preamble included in MMEL PL-34, MMEL and MEL Preamble.

2.4.5 Control Page. The control page is meant for tracking the status of the MEL to ensure currency and applicability to a specific aircraft. It includes a revision record, which lists the date of each page of the operator’s MEL. It may also be used as a means of conveying FAA approval of the MEL. At a minimum, the control page will contain:

• The operator’s name;

• A listing of all pages in the MEL (including the date of each page’s revision);

• The MMEL revision number on which the MEL is based; and

• A signature block containing space for the signature of the POI (required only if this page is used as a means of conveying FAA approval of the MEL).

2.4.6 MMEL ATA or Joint Aircraft System/Component (JASC) Coded Sections. Each MEL contains the MMEL ATA or JASC coded sections, as appropriate to the operator’s and aircraft manufacturer’s nomenclature.

### Page 16

2-3

2.5 Optional Sections.

2.5.1 C over Page. The cover page format and information ma y be the same as the MMEL at the operator’s discretion. If a cover page is used, the operator should include the MMEL revision on which the MEL is based. The operator may also include additional information in the control page at the operator’s discretion.

2.5.2 Highlights of Change Page. This page summarizes the changes made by the operator in each revision.

Note: T he operator may include additional information sections in addition to the ones listed.

### Page 17

**3-1 CHAPTER 3. MINIMUM EQUIPMENT LIST (MEL)—CONTENT**

3.1 MEL Contents. In addition to the required MEL format items, an operator’s MEL includes specific content based on the items installed on the operator’s aircraft. Except for those instances specified by policy, an operator’s MEL should incorporate the phraseology used in the MMEL to ensure clarity and standardization.

3.2 Air Transport Association of America (ATA) or Joint Aircraft System/Component (JASC) Coded Sections. The use of the term “coded sections” refers to either the JASC Code Table or the ATA Specification 100 code. The MEL ATA/JASC coded system sections include a list of individual items in the aircraft, together with requirements for operation when the items are inoperative. Each system sequence may be further broken down into individual item numbers along with repair interval categories.

3.2.1 System and Sequence Item Numbers. Operators should use the ATA or JASC system sequence numbering system. The ATA numbering system provides an industry-wide standard for numbering aircraft systems and is relevant for all aircraft. The alternate format for aircraft system coding is the JASC.

3.2.2 I ndividual Item Numbers.

1. Individual item numbers are not required to match ATA/JASC system and sequence item numbers. An operator may use its own numbering system to identify individual items within a given ATA/JASC code group, as appropriate.

2. A triple asterisk (***) below the system number in column 1 of an MMEL indicates that an item has been installed on some models of a particular aircraft make/model/series (M/M/S). Operators omit the triple asterisk symbol in their MEL and use a system sequence number when the item is installed on one or more of the operator’s aircraft.

3. An MMEL item that is not listed in an operator’s MEL is not subject to MEL relief and must be fully operative at takeoff in accordance with § 91.213.

4. An operator’s MEL limitations, conditions, and restrictions may never be less restrictive than the MMEL. However, an operator may add limitations or increase restrictions for a particular item if they are more restrictive that those required by the MMEL.

5. Operators typically list an MEL item exactly as it is in the MMEL. If an MMEL uses a generic term to describe a particular item, an operator may use different terminology, provided the operator’s terminology is recognizable and easily identified with the corresponding MMEL item.

6. If an MEL item contains multiple components, the operator may choose to list the components separately following the item in the MEL.

7. Operators may not list duplicate items or items that are listed individually elsewhere in the MMEL.

8. Individual components of an MMEL or MEL item may not be listed as NEF.

### Page 18

3-2

3.3 Repair Categories. Each item listed in an MEL (excluding NEF items or administrative control items (ACI)) should include a repair category designator as depicted in the MMEL. Repair categories represent the maximum time interval during which an item may be inoperative. When an item becomes inoperative and the operator defers repair, the aircraft may not be operated beyond the specified period until repairs are made. The requirement to comply with repair categories are included in the operator’s Operations Specification (OpSpec)/Management Specification (MSpec) D095, Minimum Equipment List (MEL) Authorization. Maximum repair time intervals are delineated by repair categories “A,” “B,” “C,” and “D.” Operators may adopt repair intervals that are more restrictive than the MMEL, but may not use a repair category that is less restrictive than the MMEL. Unless exercising an extension as listed in Chapter 5, MEL Management Program Requirements, operators using an MEL should ensure that repairs of deferred inoperative items are accomplished prior to expiration of the repair intervals established by the following letter designators:

3.3.1 R epair Category A. This category item must be repaired within the interval specified in the “Remarks or Exceptions” column of the aircraft operator’s MEL. For repair intervals specified in consecutive calendar days or flight days, the day of discovery is excluded.

For all other time intervals (e.g., flights, flight legs, cycles, hours), the repair interval begins at the point when the item is deferred in accordance with the aircraft operator’s MEL.

3.3.2 R epair Category B. In accordance with § 91.213 and OpSpec/MSpec D095, this category item must be repaired within 3 consecutive calendar days (72 hours), excluding the day of discovery. For example, if it were recorded at 10 a.m. on January 26, the 3-day interval would begin on January 27 and end at 23:59:59 on January 29.

3.3.3 R epair Category C. In accordance with § 91.213 and OpSpec/MSpec D095, this category item must be repaired within 10 consecutive calendar days (240 hours), excluding the day of discovery. For example, if it were recorded at 10 a.m. on January 26, the 10-day interval would begin on January 27 and end at 23:59:59 on February 5.

3.3.4 R epair Category D. In accordance with § 91.213 and OpSpec/MSpec D095, this category item must be repaired within 120 consecutive calendar days (2,880 hours), excluding the day of discovery.

3.4 Number of Items Installed. The “Number Installed” column of an MEL lists the number (quantity) of the specified item installed on the aircraft. This number typically represents the aircraft configuration used to develop the aircraft MMEL.

3.4.1 Variable Number Installed. A dash (-) for number installed indicates a variable number of the installed item. Use of a “-” is common in fleet MELs where aircraft of the same make and model (M/M) have differing numbers of specific items. Additionally, operators may use a “-” if it is impractical to show the actual number of the specific items (e.g., light bulbs, light-emitting diodes (LED)) installed on the aircraft.

### Page 19

3-3

3.4.2 Items Listed on the MMEL But Not Installed on the Aircraft. An operator’s MEL does not have to list items included in the MMEL but not installed on the operator’s aircraft.

For number continuity in an MEL, operators may choose to:

1. Omit the item from the MEL altogether and renumber the individual items within an ATA category as necessary to provide continuity. Individual item numbers in an MMEL are not necessarily ATA/JASC code numbers but could be sequential item numbers within an ATA/JASC category; or

2. List the item in the MEL and show the “Number Installed” as zero (0). In this case, the “Number Required for Dispatch” would also be zero (0), and the remark “Not Installed” would be noted under “Remarks or Exceptions.” In this case, the repair category designators are omitted.

3. Omit the item from the MEL, but not renumber the subsequent items to keep the same numbering as the MMEL. For example, jumping from 21-21-01 to 21-21-03, and omitting 21-21-02.

4. Other alternatives may be proposed by an operator to their FAA Certificate Management Team (CMT).

3.5 Number Required for Dispatch. The “Number Required for Dispatch” column of an MEL reflects the minimum number of items required, provided the conditions specified in the “Remarks or Exceptions” are met. The number of items required for dispatch may differ from what is required in the MMEL under the following conditions:

1. The item is listed in the MMEL as optional, is not installed on the operator’s aircraft, or is installed on the operator’s aircraft but is not required in all operations. In this case, a zero (0) may be shown as the number required for dispatch.

2. The “Number Required for Dispatch” is followed by a “-” in the MMEL.

3. Where the MMEL shows a dash “-” required for dispatch, the MEL should reflect the actual number required for dispatch. Fleet configuration differences and the dispatch requirements will be specified in the “Remarks or Exceptions” column.

4. The number required for dispatch in the MEL cannot be less restrictive than the MMEL.

3.6 Remarks or Exceptions. The “Remarks or Exceptions” column of the MMEL includes the Maintenance (M) and Operations (O) indicators, a statement permitting operation with a specific number of inoperative items and their associated provisos. To accommodate a variety of operators and operating rules, MMELs contain intentionally general “Remarks or Exceptions” for items required by 14 CFR for a particular type of operation, or for items that require specific procedures when inoperative. The MMEL may list a specific number of items that may be inoperative or may state “any in excess” of a number. “Remarks or Exceptions” in an operator’s MEL may not be general. Each operator’s MEL will expand the MMEL “Remarks or Exceptions” to include specific 14 CFR compliance requirements and detailed procedures for operating with the inoperative item(s). Listing the 14 CFR regulation (e.g., § 121.643) in the operator’s

### Page 20

3-4 MEL is optional so long as the compliance requirements are listed. MEL “Remarks or Exceptions” that list references to other manuals containing MEL procedures within the operator’s manual system is an acceptable alternative. The “Remarks or Exceptions” column may be blank or may include a statement permitting operation with a specific number of items inoperative. The statement may include provisos for such operations and appropriate notes. If the MMEL remarks are blank, the aircraft operator’s MEL may, at the operator’s discretion, incorporate the text, “May be inoperative.”

3.7 MEL Remarks and Exceptions Defined. The operator’s MEL will expand on MMEL general “Remarks or Exceptions” and will include specific procedures to enable compliance with applicable operating requirements. The following phrases are examples of MMEL general “Remarks or Exceptions”-specific conditions that should be expanded in the operator’s MEL “Remarks and Exceptions” when the particular item is inoperative.

The FAA may not approve an MEL that includes provisos with general statements such as:

• “May be inoperative provided procedures do not require its use.”

• “May be inoperative or missing if alternate procedures are established and used.”

• “May be inoperative unless required by 14 CFR” or “As required by 14 CFR.”

3.8 MEL Proviso Stipulations Should Be Specific. An operator’s MEL contains specific procedures, requirements, and conditions that apply when a particular item is inoperative.

The operator is responsible for ensuring that the MEL contains enough information to adequately and safely address operations with the item inoperative. The information is assessed by the FAA as part of the approval process.

3.9 (M) and (O) Procedures. The presence of (M) and (O) indicators in the MEL indicates that a specific procedure is required to be accomplished.

3.9.1 (M ) Procedures . This symbol indicates a requirement for a specific maintenance procedure that must be accomplished prior to operation with the listed item inoperative.

Normally, these procedures are accomplished by maintenance personnel. However, other personnel may be qualified and authorized to perform certain functions under 14 CFR part 43. Procedures requiring specialized knowledge or skill, or requiring the use of tools or test equipment, should be accomplished by maintenance personnel.

1. T he operator is responsible for ensuring that all (M) procedures are accomplished in accordance with the operator’s MEL program and applicable maintenance regulations.

2. As part of the review and approval process, the FAA may ask the operator to include additional instructions within the provisos to ensure that deferral procedures will continue to provide an Acceptable Level of Safety (ALoS).

3. The (M) procedures may be fully depicted in the operator’s MEL or in another manual. If a procedure is contained in another manual, the MEL should provide specific reference to the current version of that manual. MEL (M) procedures are

### Page 21

3-5 subject to FAA review and validation to ensure they are adequate for the relief sought.

3.9.2 (O) Procedures. The (O) indicator stipulates an operations procedure intended to be followed for planning purposes or for operating with a deferred item. These procedures may be required for flight planning purposes and are normally accomplished by the flightcrew; however, other personnel may be qualified and authorized to perform certain functions (e.g., an inoperative Global Positioning System (GPS) unit requiring the flight plan to revert to following airways may be submitted by the flightcrew or a qualified dispatcher). Additionally, procedures may have to be developed for MEL items that affect the aircraft weight and balance (W&B), dispatch, or passenger/cargo loading

(e.g., procedures for additional personnel such as those involved with aircraft load control).

1. The (O) procedures may be fully depicted in the operator’s MEL or in another manual. If a procedure is contained in another manual, the MEL should provide specific reference to the current version of that manual. MEL (O) procedures are subject to FAA review and validation to ensure they are adequate for the relief sought.

2. During the MEL review and approval process, the operator may have to include additional instructions in its provisos to ensure that deferral procedures provide an ALoS.

3. The operator is responsible for accomplishing all (O) procedures in accordance with its MEL program.

3.9.3 Operator Developed (M) and (O) Procedures. Operators should develop procedures that appropriately address the type of operation conducted. The procedures can be more restrictive than the MMEL but can never be less restrictive than the MMEL.

3.10 Provisos. Provisos are terms, conditions, or limitations that the operator must comply with to operate an aircraft with an inoperative item. Provisos are listed in the “Remarks or Exceptions” column of an MEL and, if more than one proviso applies to a given item, are listed by a number or a lowercase letter. For example, a proviso may allow an item to be inoperative provided the aircraft is not operated in Extended Operations (ETOPS); or a proviso may require that an aircraft only be operated under visual flight rules (VFR) when a particular item is inoperative. In the operator’s MEL, the phrase “As Required by 14 CFR,” or any similar statements from the MMEL, will be replaced with the specific regulatory references or conditions under which an item may be inoperative.

3.11 Notes. Notes provide additional information for crewmember or maintenance consideration. Notes are used to identify applicable material, which is intended to assist with compliance, but do not relieve the aircraft operator of the responsibility for compliance with all applicable requirements. Additional notes may be amended, deleted, or added to the MEL by the aircraft operator, as appropriate, but must remain within the scope of this definition. Notes are not a part of the provisos.

### Page 22

3-6

3.12 Definitions. MMEL PL-25 provides a list of definitions for use in MMELs and MELs .

For MELs, certain MMEL definitions may be edited or may be omitted if the element is not used in the operator’s MEL. MEL definitions will be tailored, as appropriate, including content and format, dependent upon the aircraft operator’s M/M of aircraft, type of installed items, and specific operation. However, the intent of the definition must be the same and cannot be less restrictive than the MMEL.

3.13 R eferences. The operator should research regulatory requirements in detail to develop the appropriate deferral limitations and conditions. Clarification of specific regulatory requirements will be included in each related proviso. Appendix A of MMEL PL-25 contains a list of regulatory references by ATA section. Operators may use MMEL PL-25 to identify the appropriate terminology to use in their MEL. An operator may include a reference to their FAA-approved or FAA-accepted manual that contains the procedure(s) required to address a particular MEL item. The MEL may only reference FAA-approved or FAA-accepted manuals. The following conditions apply when referencing manuals:

1. Manual reference(s) will be preceded by either a proviso(s) or specific instruction(s) defining the action required. A single proviso or specific instruction may have more than one manual reference associated with it.

2. Manual references will direct the reader to use the current revision of the subject manual. Actual revision level/date of the manual is not required to be listed in the MEL.

3. The operator’s MEL management program and manual system should include procedures for notifying the FAA when references within the MEL have changed. All changes to procedures in the MEL require an MEL revision and FAA approval of the MEL revision.

4. The proviso or specific instruction and manual reference in the MEL is considered the means of compliance for MEL purposes when the MEL is approved by the FAA.

Each procedure referenced is either FAA-approved or FAA-accepted, depending on the status of the manual referenced. For example, for “Remarks or Exceptions” which contain procedures, an operator could include a proviso or specific instruction to secure or isolate an item in accordance with a specific chapter, section, task, or paragraph of the referenced manual. The instructions and the reference to the manual is the means of compliance.

Note: A change to any procedure listed in an MEL (in the event that an operator lists procedures in the MEL instead of providing references to other approved or accepted manuals) will be evaluated and approved as part of the MEL revision.

References in the MEL to maintenance procedures contained in an approved or accepted manual may contain language such as “Deactivate and lock start valve in the closed position according to current version of AMM 80-12-14-201A.” Such language will be approved as part of the original submission of the MEL and will remain approved as long as the reference is valid. An operator may make changes to the referenced AMM procedure without subsequent MEL approval. The FAA does not need to reapprove an MEL as a result of a change in a procedure in a referenced approved or accepted manual.

### Page 23

3-7

3.14 Specific 14 CFR Requirements. “As required by 14 CFR” or any similar statement is prohibited in an operator’s MEL. MEL deferrals based on MMEL items that may be inoperative “unless required” by 14 CFR will contain specific details of the relevant regulatory requirements. For example, an MMEL general “Remarks or Exceptions” for distance measuring equipment (DME) states “As required by 14 CFR.” An acceptable MEL “Remarks or Exceptions” would be “May be inoperative provided flight remains below FL 240.”

### Page 24

**4-1 CHAPTER 4. MEL RELIEF FOR ITEMS INSTALLED AFTER TYPE**

**CERTIFICATION**

4.1 General. The aircraft design approval holder (DAH) determines the configuration of the aircraft, the items installed, and the official parts listed during the initial aircraft type certification process conducted at the time of manufacture. Any subsequent installation or removal of items may be accomplished only through a Supplemental Type Certificate (STC), an Engineering Order (EO), a Field Approval, or other FAA-approved methods (as appropriate).

4.2 Operator NEF Items or Administrative Control Items (ACI). Items listed on an operator’s NEF program and ACIs are excluded from the requirements for evaluation, as listed in this chapter.

4.3 MMEL Items and MEL Items. For an item to be listed in an operator’s MEL, it should first be listed in the MMEL, as the MMEL is the basis for an operator’s MEL. (The only exceptions are MEL relief added through an MMEL PL with a Global Change (GC) designation or an Aircraft Evaluation Division (AED) approval letter, as these are considered addendums to the MMEL.)

4.3.1 Example. If an operator wants to add an item to its MEL, such as a flight management system (FMS) or an autopilot, then that item should first appear in the applicable aircraft’s MMEL as “FMS” or “Autopilot.”

4.3.2 Ite ms Not L isted in an MMEL. An operator may petition the AED to add items to the applicable aircraft’s MMEL through the Flight Operations Evaluation Board (FOEB) process. This may be accomplished through the operator’s responsible Flight Standards office or directly to the responsible AED office. An operator should be prepared to provide the information that the FOEB will need for this evaluation. See the list of needed items found in paragraph 4.6.

4.4 STC. A design change to a TC is often done with an STC. Ideally, MMEL/MEL relief can be evaluated during the STC certification when this is requested by the STC applicant.

4.4.1 Evaluation of MEL Relief During STC Certification. To obtain MMEL/MEL relief, the STC applicant involved in the certification of an STC should submit a request for relief in accordance with the FOEB MMEL Agenda Coordination Process (refer to FAA Order 8900.1, Volume 8, Chapter 2, Section 3, Flight Operations Evaluation Board, and AC 21-40, Guide for Obtaining a Supplemental Type Certificate). This submission should be made early in the certification process to allow MMEL/MEL evaluation concurrent with the certification process. Requests for relief subsequent to the completion of the certification process can delay the availability of MMEL/MEL relief for an item.

4.4.2 MME L PL. MMEL PL-109, Supplemental Type Certificate (STC) MMEL/MEL Relief Process, provides amended guidance regarding MMEL/MEL relief for items installed on an aircraft that affected the aircraft’s type certificate (TC) and to any change to the TC when MMEL/MEL relief is sought. Flight Standards updated this policy to allow

### Page 25

4-2 operators to work with their responsible Flight Standards office to obtain relief for unevaluated STC items as described in this chapter. Operators are no longer required to petition the STC or design holder for relief.

4.5 Adding Relief for Items Installed After Type Certification. STCs issued without concurrent AED evaluation may be granted relief by request from the operator to the FAA. Additional information may be found in Order 8900.1, Volume 4, Chapter 4, Section 3, MEL Re quirements for 14 CFR Parts 91K, 121, 125, 125 LODA, and 135 Operations. STCs already listed by STC number in the applicable aircraft MMEL or in an AED approval letter may be added to the operator’s MEL through the normal revision process without further evaluation. However, a principal inspector (PI) may coordinate with the AED during this process, as needed. Using the normal revision process found in Chapter 9, MEL Revi sions, of this AC, an operator may add relief for items to its MEL through any of the following solutions:

4.5.1 MMEL Specifically Lists the Relief. Where the MMEL lists the specific STC number

(e.g., ST00733SE) or identifies the specific design change nomenclature (other than STCs), an operator may add the relief to its MEL.

4.5.2 Design Change Approval Letters. Upon evaluation and approval of a design change, the AED will submit an approval letter directly to the FAA’s DRS. Operators may access these approval letters at https://drs.faa.gov/ under “MELs and AED Guidance Documents,” “STC Relief Approval Letters.” The approval letter will contain the allowed relief, including conditions and provisos, along with remarks or exceptions. Approval letters will be dated and have revision numbers. Operators may amend their MEL(s) with the relief for the STC(s) in accordance with the AED approval letter. Paper copies of the AED approval letter are also acceptable in lieu of the DRS database.

4.5.3 MEL Relief T hrough MMEL PL With GC Designation. Operators may add relief into their MEL(s) for an STC through an MMEL PL with a current GC designation. However, upon the AED evaluation of the item (if an evaluation is conducted), operators may have to amend or remove previously approved relief in their MEL(s). See Chapter 9 for additional information on GC.

4.5.4 Responsible Flig ht Standards Office’s Relief Evaluation. If the proposed relief is not covered by one of the three solutions immediately above and the MEL item is listed generically in the MMEL, the item may be evaluated by the responsible Flight Standards office. Additional information may be found in Order 8900.1, Volume 4, Chapter 4, Section 3. To add MEL relief using this method, the following points should be considered:

1. T he basic item needs to be found in the applicable aircraft’s MMEL (e.g., FMS, autopilot, passenger seat). If not, the AED must complete the evaluation.

2. The operator’s Safety Management System (SMS) (as applicable) reveals that the proposed relief does not present a hazard to the operator’s use of the relief.

### Page 26

4-3

3. The PIs conducting the evaluation may consult with the STC holder, AED, Original Equipment Manufacturer (OEM), and other stakeholders during their evaluation of the operator’s proposal.

4. If the item was previously evaluated by the AED and relief was not granted, the item is not eligible for evaluation by the responsible Flight Standards office.

5. If the PI believes a hazard exists with the operator’s proposal, the item is not eligible for relief.

4.6 Items Needed for Evaluation of Design Changes. Each proposed operator MEL relief item should have accompanying supporting justification before it will be considered. The information needed by the FAA allows a thorough evaluation of the risk associated with operating the aircraft with the item inoperative. The FAA may reject an item proposal if the justification information is inadequate. At a minimum, the following information should accompany all item proposals:

1. The title and number of the proposed MMEL item;

2. A brief description of the system and its intended functions;

3. A summary of the proposed MMEL relief;

4. A brief description of intent;

5. The effect of dispatching a flight with this inoperative item;

6. The operating rule(s) that requires the item to be operative, as applicable;

7. The transfer of function when the item is inoperative;

8. The next most critical failure;

9. The effect on increased flightcrew workloads (including risk mitigations);

10. The certification requirements for the item;

11. Any conflicts with Airplane Flight Manual (AFM) limitations, procedures, or Airworthiness Directives (AD);

12. If the item affects or is required to accomplish an emergency procedure;

13. The effect on aircraft capability in an emergency;

14. Maintenance (M) and Operations (O) procedures required for the proposed dispatch condition;

15. Any information that adds support to the proposal (e.g., wiring diagrams, schematic drawings, or STC documents); and

16. Any other information requested by the FAA before or during the evaluation.

### Page 27

**5-1 CHAPTER 5. MEL MANAGEMENT PROGRAM REQUIREMENTS**

5.1 General. Each operator will develop and maintain a comprehensive program for managing the repair of items listed in the FAA-approved MEL. An operator’s MEL management program is required by Operations Specification (OpSpec)/Management Specification (MSpec) D095, Minimum Equipment List (MEL) Authorization, issued by the FAA to authorize an operator to use an MEL.

5.2 MEL Management Program. The MEL management program should include at least the following:

1. A method for tracking the date and, when required, the time an item was deferred and subsequently repaired. This should include a supervisory review of:

a. The number of deferred items per aircraft; and

b. Each deferred item to determine:

• The reason for any delay in repair,

• The length of the delay, and

• The estimated date the item will be repaired.

2. A plan for managing the materials, personnel, facilities, and aircraft to ensure timely corrective action.

3. Processes to ensure parts availability.

4. A description of specific duties and responsibilities, by job title, of the personnel who manage the MEL program.

5. Procedures for controlling an extension to specified repair intervals as permitted by the operator’s OpSpec/MSpec to include the limit of the extension and the procedures for authorizing an extension.

5.3 Continuing Authorization—Single Extension. For operations conducted under part 91K, 121, 125, or 135, OpSpec/MSpec D095 authorizes an operator to use a continuing authorization-single extension to approve a single, one-time extension to the repair interval for repair category B and C items only, as specified in the FAA-approved MEL.

5.3.1 OpSpec/MSpec D095 requires each operator’s MEL management program to contain procedures for controlling extensions to item repair intervals. Procedures for the method by which the operator approves a continuing authorization-single extension will be included.

5.3.2 Under OpSpec/MSpec D095, an operator is not authorized to use a continuing authorization-single extension for repair category A or D items.

5.3.3 Under OpSpec/MSpec D095, the operator should notify its responsible Flight Standards office within 24 hours of approving a continuing authorization-single extension.

### Page 28

5-2 Note: The FAA may deny the use of the continuing authorization-single extension privilege if abuse is evident.

5.4 Additional Extensions. After the operator has exercised its one-time extension of a repair category B and C item, approval for additional extensions can only be obtained by submitting a request to the responsible Flight Standards office. An extension to a repair interval may not exceed the time of the original repair interval. For example, a repair category B item with a repair interval of 3 consecutive calendar days may only be extended up to an additional three consecutive calendar days. In rare cases, some additional extensions may be authorized by coordination with Safety Standards divisions.

Operators may request extensions to category A and D items by contacting their responsible Flight Standards office.

### Page 29

**6-1 CHAPTER 6. CONDUCTING OPERATIONS UTILIZING MEL RELIEF**

6.1 General. Parts 91K, 121, 125, and 135 operators’ flightcrew, operational control, and maintenance personnel need to clearly understand the regulatory requirements associated with conducting operations in accordance with their FAA-approved MEL.

6.1.1 A pplicability . MEL item relief may be applied to an MEL item newly identified as inoperative up until takeoff. Takeoff is defined as the act of beginning a flight in which an aircraft is accelerated from a state of rest to that of flight. For the purposes of MEL relief, this means the point at which power is applied to initiate the takeoff from the runway or takeoff surface.

6.1.2 O perator Regulatory Responsibility . Operators must comply with all applicable FAA requirements.

6.1.3 Ite m Failures During Push -Back, Taxi, After Gate or Ramp Departure, Prior to Takeoff.

The MEL does not allow a flight to continue “as dispatched,” as any discrepancy discovered before takeoff must be addressed by repair or deferral. The MEL allows a discrepancy to be addressed by deferral for a specified period. The aircraft should be redispatched with the item of equipment inoperative, and a revised dispatch release, if required, issued showing the deferred item. An operator’s MEL management program and general manual should include the policies and procedures required to ensure an aircraft does not take off with inoperative items until the MEL deferral process has been completed. If the MEL procedures for a specific item require a mechanic’s inspection, takeoff would be prohibited until the required inspection is completed.

6.1.4 Ite m Failures A fter Takeoff. MEL relief does not apply for item failures occurring after takeoff. After takeoff, flightcrews should handle item failures in accordance with the Airplane Flight Manual (AFM)/Rotorcraft Flight Manual (RFM) and the operator’s approved procedures and checklists. However, any item failure that occurs after takeoff must be addressed before the subsequent takeoff in accordance with § 91.213.

6.2 Operational Requirements.

6.2.1 Airworthiness. Section 91.7 prohibits operation of an aircraft that is not airworthy.

Sections 121.605 and 125.355 prohibit any person from dispatching or releasing an aircraft unless it is airworthy, and § 135.143 prohibits operating an aircraft unless the aircraft and required instruments and equipment have been approved and are in an operable condition. In all cases, the operator, pilot in command (PIC), aircraft dispatcher (part 121 domestic and flag), or person authorized to exercise operational control by the operator (part 121 supplemental) are all responsible for ensuring the aircraft is dispatched/released and operated in an airworthy condition.

6.2.2 F ulfillment of Regulatory Responsibility . Each operator should provide a process for persons authorized to exercise operational control (PIC, dispatcher, flight follower, Director of Operations (DO), Operations Control Specialist, or person authorized by the DO, as applicable) to fulfill their regulatory responsibility to ensure an aircraft is not dispatched or released unless it is airworthy.

### Page 30

6-2

6.2.3 Operations With Inoperative Instruments. Under the provisions of §§ 91.1115, 121.628,

125.201, and 135.179, operations with inoperative instruments or equipment may be conducted with an FAA-approved MEL and MEL management program. This may be accomplished through a maintenance control organization that is responsible for verifying airworthiness and providing MEL information to the person authorized to exercise operational control before the aircraft is entered into service.

6.3 Dispatch or Flight Release Requirements. In part 121 operations, both a dispatch and a flight release specify the conditions for origination or continuation of a particular flight.

For this reason, the MEL information should be included on the dispatch or flight release, and the flight planned to account for any limitations, such as system, flight restrictions, or performance limitations imposed by the deferral stipulations of the MEL. Examples of operational limitations include, but are not limited to:

1. Altitude restrictions.

2. Cabin pressure limitations.

3. Temperature limitations.

4. Performance capabilities.

5. Weight restrictions.

6. Fuel penalties and limitations.

7. Navigational limitations.

8. Communication limitations.

9. Weather restrictions (including ice and rain limitations).

10. Cargo loading (including locks and nets) or cargo heating limitations.

11. Flight control limitations.

12. Landing gear restrictions, including braking and steering.

13. Auto flight capabilities.

14. Electrical power limitations.

15. Extended Operations (ETOPS) limitations (when applicable).

16. Lighting restrictions.

17. Oxygen system limitations.

18. Information system limitations.

19. Auxiliary power limitations.

6.3.1 Item Failures that Occur After the Issuance of a Dispatch or Flight Release–Parts 91K, 121, 125, and 135. When a dispatch or flight release is used, operators should have policies and procedures in place for the dispatcher, person authorized to exercise operational control, and the PIC to amend the dispatch or flight release when an MEL item is deferred after the dispatch or flight release has been issued. Those procedures

### Page 31

6-3 should include procedures to update the flight plan to include limitations that are imposed by an MEL.

6.3.2 Ite m Failures T hat Occur After an Aircraft Departs the Gate or Ramp Area, During Push-Back, Taxi, or Prior to Takeoff. In accordance with § 91.213, each operator’s MEL management program must include procedures for the PIC to communicate with the person authorized to exercise operational control and the maintenance organization to determine which of the following actions is required:

6.3.2.1 R eturn for Repairs. If an inoperative item is not included in the MEL or the inoperative item could affect the safety of flight due to circumstances such as weather, performance, weight and balance (W&B), or fuel limitations, the aircraft must return to the gate or ramp area for repairs, in accordance with § 91.213.

6.3.2.2 Return to Accomplish Maintenance (M) and Operations (O) Procedures.

PICs, dispatchers, or persons authorized to exercise operational control may determine that an inoperative item may be deferred and the appropriate (M) or (O) procedures accomplished in accordance with the operator’s approved MEL and MEL management program.

6.3.2.3 Flightcrew Accomplishment of Certain MEL Procedures. An operator may develop, and the FAA may approve, procedures that permit flightcrew members to accomplish MEL deferrals in coordination with the operator’s dispatch and maintenance organization, without returning to the gate or ramp area prior to takeoff. These procedures will be part of the operator’s MEL management program to ensure all applicable procedures are accomplished by appropriately qualified personnel and that all conditions and limitations associated with an MEL item are satisfied.

1. Coordination between flightcrew and the maintenance organization may not involve directed troubleshooting or other forms of system fault diagnosis beyond what is specifically approved in the operator’s MEL management program procedures.

2. Only qualified maintenance personnel may perform troubleshooting or fault diagnosis necessary to determine suitable MEL relief, unless otherwise approved.

3. Any time an MEL item results in operational limitations such as those affecting aircraft performance and altitude capabilities or weight or fuel restrictions, the dispatcher or person authorized to exercise operational control will recalculate a new flight plan and issue a new or amended dispatch or flight release.

6.4 Multiple Inoperative Items or System Components. Because an inoperative component in one system can affect the operation, or limit the inoperability of a component in another system, operator’s personnel should be aware of the impact that

### Page 32

6-4 multiple item failures and deferrals can have on the safety of flight. This includes the consideration of possible additional item failures while an aircraft is en route.

6.5 Availability of the MEL to Operator Personnel. Parts 91K, 121, 125, and 135 require that flightcrews have direct access to the MEL at all times prior to takeoff. Indirect methods of providing access such as telephone, radio, or data link are not acceptable. The method of providing access is part of the operator’s MEL management program.

### Page 33

**7-1 CHAPTER 7. MEL CREATION AND FORMATTING**

7.1 General. When constructing an MEL, each operator should consider their particular aircraft configurations and operational procedures. An MEL is based on the MMEL for the aircraft and should include the characteristics of an MMEL. In addition to the required MEL format items, an operator’s MEL should include specific content based on the items installed on the operator’s aircraft. An operator’s MEL should incorporate the phraseology used in the MMEL, wherever appropriate, to ensure clarity and standardization.

7.2 MEL Format Outline. Operators may copy the MMEL format outline directly into their MEL. An operator may also customize their MEL format provided the format does not make the MEL in any way less restrictive than the MMEL. The MMEL format outline contains eight sections. An MEL should always include six of those sections. The operator may include additional information sections in addition to the ones listed in Chapter 2, Minimum Equipment List (MEL)—General. The following information describes the operator’s recommended MEL format:

7.2.1 V ertical Bar (Change Bar) . All change bars applicable to the previous revision of the MMEL or MEL should be removed prior to release of the next revision in a manner consistent with the operators’ manual system revision process.

7.2.2 Su b system Titles. Identify subsystem titles in column one with 1), 2), etc. For example (bullets are used in this example, but are not required):

• 28-xx Fuel Quantity Indicating System o 1) Main Tank o 2) Center Tank

7.2.3 Items That Must be Operative for All Conditions. Generally, an MEL should not include any items that must be operative for all conditions. Operators may include certain items listed as required to be operative to ensure they have not inadvertently been missed, or for fleets with varied configurations, etc.

7.2.4 W hen a n MMEL Relief Item is Deleted or Moved. When an MMEL relief item is deleted or moved, the item name and sequence number will be retained in the MMEL, with an appropriate notation in the “Remarks or Exceptions” column. The MMEL revision number of the deleted or moved relief item is included. For example:

• Relief is deleted entirely: “Deleted, Revision X.”

• Relief is combined with relief at another location: “Relief combined with ATA 31-XX, [Relief Title], Revision X.”

### Page 34

7-2

• Relief is moved to another Air Transport Association of America (ATA) chapter:

“Relief moved to ATA 31-XX, Revision X.”

• Relief is moved to another FAA-approved document: “Relief moved to [Document Name], Revision X.”

Note: Operators may follow the MMEL format using the MEL revision number as appropriate, may simply delete the applicable item, may list the item as required operative, or may use another method that is acceptable to the FAA.

7.2.5 N umber Installed/Number Required for Dispatch . In the “Number Installed” or “Number Required for Dispatch” column, use a number whenever possible; otherwise, use a “-” with proper qualification.

7.2.6 Single Proviso Formatting. W hen only one proviso condition exists, it should be arranged into the statement of relief.

7.2.7 Control or Switch Position. Where a control or switch position is specified, indicated by label, or special emphasis is required, use all caps instead of underlining (e.g., “ON-OFF” or “OPEN-CLOSED.”) Use of the word “position” in reference to “ON-OFF” or “OPEN-CLOSED” is often redundant and need not be included. Alternative means of emphasis may be used, consistent with the aircraft manuals and operator manual system, if approved by the Principal Operations Inspector (POI).

7.2.8 Reference to Another Item Listed in the MEL. Where a proviso refers to another item listed in the MEL, typically to require that item be operative, the item will always be referred to using the exact same title as listed. The relief item number will generally not be used to reference an item.

7.2.9 Limiting Altitudes. Wh enever possible, all limiting altitudes stated should include the words “or below” (e.g., “10,000 feet MSL or below,” “FL 310 or below”).

7.2.10 Specific Word Usage. The word “operative” should be used instead of “operable.” Delete the word “the” wherever possible.

7.2.11 Provisos. Use letter and parenthesis (e.g., a), b), etc.) to identify proviso conditions.

Delete the word “or” when it is located between proviso conditions. Each set of needed proviso conditions should be repeated as required to eliminate the use of “or.” Use a comma after all proviso conditions and prior to the last one use “, and.” Use a period after last proviso condition. For example:

a) F irst c ondition,

b) Second condition, and

c) Last condition.

7.2.12 N ote(s) . Each note applies only to the relief proviso it immediately follows and is located in the “Remarks or Exceptions” column, using all caps for the word “NOTE.” Note(s)

### Page 35

7-3 should be repeated, as necessary, following each applicable proviso. If there is only one note, do not number it. If there is more than one note, number each (e.g., “NOTE 1:”, “NOTE 2:”).

7.3 Prohibited Items. An MEL will not include items of the aircraft required by operating regulations (e.g., wings, flaps, rudder, etc.), nor will it include instruments and equipment required for specific operations under 14 CFR (refer to § 91.1115).

7.4 MEL Restrictions. An operator’s MEL may not be less restrictive in any way (more restrictive is acceptable) than the following:

• The MMEL from which it was developed;

• Title 14 CFR;

• The operator’s Operations Specification (OpSpec)/Management Specification (MSpec) D095, Minimum Equipment List (MEL) Authorization;

• The Airplane Flight Manual (AFM)/Rotorcraft Flight Manual (RFM) limitations and emergency procedures;

• The Supplemental Type Certificate (STC)/instructions for continued airworthiness (ICA) (as applicable); or

• Applicable Airworthiness Directives (AD).

Note: Occasionally, an AD may apply to an item that may be authorized to be inoperative under the MEL. In those cases, the operator must fully comply with the terms of the AD or an FAA-approved alternative method of compliance (AMOC) with the AD. Refer to 14 CFR part 39, §§ 39.3 and 39.19. When provisions of an AD allow operation of the aircraft on the condition that certain installed items be used or be operable, those affected items must be operable, even if the MEL provides for deferral of repair.

7.5 F leet MELs. An operator may develop a fleet MEL for multiple aircraft of the same make and model (M/M). When a fleet MEL is used, aircraft of the same M/M may have differing numbers of specific items installed. PIs may approve an operator’s use of a fleet MEL to reflect all of the items that are applicable to a specific aircraft fleet type. This is allowable provided the MMEL applies to all of the make, model, and series (M/M/S) aircraft contained in the fleet. For example, the MMEL applies to all model B747-100/200/300 aircraft.

7.5.1 I dentify Each Model and Configuration Difference. A fleet MEL should identify each aircraft model and configuration difference, when appropriate. The operator does not need to list aircraft identification numbers.

7.5.2 Modifications Within a Fleet. The aircraft manufacturer determines the configuration of the aircraft, the items installed, and the official parts listed during the initial aircraft type certification process conducted at the time of manufacture. Any subsequent installation or removal of items must be accomplished through the use of an STC or other

### Page 36

7-4 FAA-acceptable methods, techniques, and practices, including the use of FAA-approved technical data if the installation or item removal is a major alteration. Operators with an approved fleet MEL may continue to operate under the provisions of the current fleet MEL with new items installed in one or more fleet aircraft. However, operators may not defer repair of the new items until an appropriate revision to the fleet MEL has been approved.

7.5.3 OpSpecs/MSpecs and Manuals. The operator’s OpSpec/MSpec D095 and appropriate company manuals, such as the maintenance manual, should list aircraft M/M/S for each fleet MEL approval.

### Page 37

8-1 CHAPTER 8. FAA REVIEW AND INITIAL APPROVAL OF AN OPERATOR’S MEL

8.1 General. When an operator submits an MEL to the responsible Flight Standards office for approval, the Principal Operations Inspector (POI) will coordinate with the Principal Avionics Inspector (PAI), Principal Maintenance Inspector (PMI), and inspectors in other specialties as necessary during the approval process. The process of developing and obtaining FAA approval of an MEL can be viewed as a five-phase process: preliminary, submission, MEL review, MEL management program review, and approval and issuance of Operations Specification (OpSpec)/Management Specification (MSpec) D095, Minimum Equipment List (MEL) Authorization.

8.2 Preliminary. In the preliminary phase, the operator will consult with the principal inspectors (PI) regarding the requirements for initially developing an MEL. The PIs will discuss the operator’s type and scope of operations and advise the operator on how to find the current MMEL for their fleet(s).

8.3 Submission. Upon developing a draft of their proposed MEL, the operator will submit the MEL and associated documents to the FAA for review. The submitted material should be in a format that allows review and comment that is acceptable to the responsible Flight Standards office. Additionally, an MEL should be in a format that provides the FS office with the ability for thorough review and comment. The submission should include, at a minimum:

1. The proposed MEL.

2. The current equipment list for each aircraft make/model/series (M/M/S) that will be included in the MEL.

3. The MEL management program and its procedures, as required by OpSpec/MSpec D095.

4. MEL-related portions of the operator’s training program for flight and ground personnel and any associated guidance material.

5. Any manual(s) or document(s) that are referenced in the MEL and MEL management program, including:

a. Instructions for managing the repair of items listed in the MEL.

b. Policies and procedures for flightcrews to report mechanical irregularities.

c. Procedures for:

• Approving the aircraft for return to service (part 43, §§ 43.9 and 43.11); or

• Preparing the aircraft airworthiness release or the appropriate entry (§§ 91.1443, 121.709, 125.411, or 135.443).

d. Procedures for maintenance, preventive maintenance, and alterations.

e. Procedures for verification of aircraft airworthiness.

f. Inspection program requirements and procedures for required inspection personnel.

### Page 38

8-2

8.4 Review and Findings of an Operator’s MEL Submission.

8.4.1 Initial Review. The PIs will conduct an initial review of the operator’s submittal to verify its completeness and will verify that submittal is detailed enough to permit a thorough evaluation. They will contact the operator if the proposed MEL package is incomplete or otherwise unacceptable.

8.4.2 C omprehensive Review. If the initial review is acceptable, the PIs will then conduct a comprehensive review. This review will normally be completed within 90 days from the initial review.

8.4.2.1 During the comprehensive review process, the MMEL is used as the primary reference document; however, the review will include verification that the MEL does not conflict with the applicable regulations of 14 CFR, the Airplane Flight Manual (AFM)/Rotorcraft Flight Manual (RFM), and the operator’s OpSpecs/MSpecs. Items that are not eligible for deferral, and therefore cannot be listed in the MEL, include:

• Type Certificate Data Sheet (TCDS) items.

• Any items required by the rules under which the aircraft is type certificated and which are essential for safe operations under all operating conditions.

• Instruments and equipment required for specific operations under the applicable operating rule(s)

• Any items required by Airworthiness Directives (AD).

8.4.2.2 The reviewers will verify, amongst other things, that:

1. The MEL format should contain sections and content, as listed in Chapters 2, Minimum Equipment List (MEL)—General, and 3, Minimum Equipment List (MEL)—Content.

2. The table of contents and pages are numbered according to the applicable Air Transport Association of America (ATA) or Joint Aircraft System/Component (JASC) numbering system.

3. The prescribed MEL preamble is used without modification (refer to MMEL PL-34).

4. The MEL contains all installed items listed in the MMEL for which relief is requested.

5. The MEL repair categories are not less restrictive than the MMEL.

6. The “Number Required” section agrees with the number installed, according to the current equipment list and is not less restrictive than the MMEL.

### Page 39

8-3

7. The operator’s program includes a revision process to ensure that the MEL is revised when there are changes in the MMEL, including process instructions and a method for maintaining a current List of Effective Pages (LEP) of the MEL.

8. All abbreviations and symbols used in the MEL are defined.

9. The MEL “Remarks or Exceptions” column includes specific procedures in accordance with the requirements of the operating rules (e.g., parts 91K, 121, 135, etc.) under which the operator conducts its operation. The procedures should address what is required when a particular item is inoperative, any fleet configuration differences, and that the dispatch requirements are specified in sufficient detail. “Remarks or Exceptions” may not be general.

10. T he operator’s (M) and (O) procedures are fully developed.

8.5 MEL Management Program Review. The review of the operator’s submission will also verify that the operator’s MEL management program meets the requirements of OpSpec/MSpec D095 and the requirements of FAA Order 8900.1, Volume 4, Chapter 4, Configuration Deviation List (CDL) and Minimum Equipment List (MEL). The MEL management program should at least include:

1. A l i st of personnel responsible for MEL management.

2. A list of personnel authorized to defer maintenance in accordance with the MEL.

3. A description of specific duties and responsibilities, by job title, of the personnel who manage the MEL management program.

4. A description of training requirements for conducting MEL procedures.

5. Procedures for granting deferral authority.

6. Procedures for controlling an extension to specified repair intervals, as permitted by OpSpec/MSpec D095, to include the limit of the extension and the procedures to be used for authorizing an extension.

7. Instructions for the placarding of inoperative and removed items, including sample placards, as they would appear in service.

8. A plan for bringing together parts, maintenance personnel, and aircraft at a specific time and place for repair.

9. A review of items deferred because of the unavailability of parts to ensure that a valid back order exists with a firm delivery date.

10. A method that provides for tracking the date and, when appropriate, the time an item was deferred and subsequently repaired. The method should include a supervisory review of:

• The number of deferred items per aircraft; and

• Each deferred item to determine the reason for any delay in repair, length of delay, and the estimated date the item will be repaired.

### Page 40

8-4

11. Procedures for control of MEL deferred maintenance items, including:

• Item procurement and distribution for the corrective action(s) associated with deferred items.

• Scheduling of corrective action(s), describing when and where maintenance is performed.

• Coordination between the operator’s maintenance, flight operations, and dispatch/operational control organizations regarding MEL conditions and limitations and any operational restrictions.

• Reporting and recording of the deferred MEL item and the subsequent repair or replacement of the item.

8.6 Correction of Deficiencies. The operator will correct any deficiencies before the MEL and the MEL management program approval.

8.7 Approval and Issuance of OpSpec/MSpec D095. When the review verifies that the MEL complies with all applicable requirements, the POI will sign the MEL LEPs or the control page(s) as applicable, indicating MEL approval. Authorization to use the approved MEL is granted through the issuance of OpSpec/MSpec D095. If the operator has not been previously authorized to operate with an MEL, the PMI will issue OpSpec/MSpec D095. The responsible Flight Standards office will maintain a copy of each current MEL, provided to the FAA by the operator.

### Page 41

**9-1 CHAPTER 9. MEL REVISIONS**

9.1 General. Either the FAA or the operator may initiate revisions to an MEL. All MEL revisions require approval from the Principal Operations Inspector (POI) per § 91.213.

9.2 FAA-Initiated Revisions. An operator’s MEL can be revised due to FAA actions, revision to the MMEL, a Global Change (GC) in an MMEL PL, or a request from the operator’s responsible Flight Standards office. There are two types of MMEL revisions:

nonmandatory/interim and mandatory/standard.

9.2.1 No n -Mandatory/Interim MMEL Revision.

9.2.1.1 Applicability. A nonmandatory/interim MMEL revision is optional and an operator has discretion on revising or not revising its MEL in light of the non-mandatory/interim MMEL revision.

9.2.1.2 Numbering. A nonmandatory/interim MMEL revision is identified by the current standard revision number plus a lowercase letter. For example, a non-mandatory/interim revision following Revision 5 will be identified as Revision 5a. There may be subsequent interim revisions to the same standard revision. These carry the next lowercase letter (e.g., 5b, 5c, 5d).

Note: The operator’s MEL revision number does not have to match the MMEL revision number. Operators may use their own revision numbering system.

9.2.2 M andatory/Standard MMEL Revision. A mandatory/standard MMEL revision is compulsory under § 119.51 and includes changes that are applicable to all operators using an approved MEL for a specific aircraft make and model (M/M). All operators should amend their MELs by following these standards:

9.2.2.1 A pplicability. If a mandatory/standard MMEL revision is not applicable to an operator, the operator will document the inapplicability in a form that is acceptable to the POI. The operator will then reissue the MEL control page and will indicate that the MEL is in compliance with the required MMEL revision.

9.2.2.2 Numbering. A mandatory/standard MMEL revision is numbered with the next successive change to the basic MMEL revision number. For example, the next mandatory/standard revision following non-mandatory/interim Revisions 6a or 6b is Revision 7.

9.2.2.3 Submission and Review Time Table. Operators should incorporate MMEL changes into their MEL and submit them for review and approval within 90 days of the MMEL revision date. In the case where relief for an item is removed from an MMEL, there may be a more restrictive time requirement for an operator to revise its MEL to remove the relief. If at any time an operator does not take active steps to revise its MEL, the POI may initiate the

### Page 42

9-2 process to remove the MEL operations specification (OpSpec)/management specification (MSpec) authorization in accordance with applicable regulations.

Principal inspectors (PI) will complete the MEL review and approval process within 90 days of receiving the MEL revision from the operator.

9.2.2.4 Restrictive Categories or Provisos. If an MMEL revision results in a more restrictive repair category or proviso, the operator does not have to close and reinitiate an existing open MEL item affected by the revision. Existing MEL items may remain open in accordance with the original repair category and proviso under which the item was initially deferred until such time as the item is repaired and the MEL item is closed. If an MMEL revision results in a change to the system or sequence item number, the operator does not have to close an open MEL item and reinitiate it under its new number. Instead, the item may continue to be tracked under its original item number until the repair category interval is reached.

9.2.3 M MEL PL GC . A GC is newly developed or changed MMEL relief for an item which may or may not be time sensitive. The sole purpose of a GC designation is to allow operators to obtain timely MEL relief for installed items referenced in an MMEL PL prior to the release of a revised MMEL. Operator incorporation of a GC is optional.

9.2.3.1 A pplicability. GCs are applicable to all or a large number of MMELs and will describe its applicability (inclusion or exclusion) when it does not apply to all aircraft types. GCs may be used to provide immediate relief for items required by a new regulatory requirement, FAA policy change, or new technology.

9.2.3.2 Numbering. GCs are identified by the letters “GC” after the MMEL PL revision number on the title page. For example: “MMEL Policy Letter (PL)-54, Revision 10 GC”.

9.2.3.3 Frequency of Publication and Life Span. GCs will not typically occur in great number or regularity and their application and use is normally limited.

Most GCs have an expiration date and the relief granted by the GC may only be exercised in an operator’s MEL before the GC expires. It is expected that the applicable aircraft’s MMEL will be amended with the relief contained in the MMEL PL GC before the expiration of the GC designation. GCs may be extended by the FAA’s initiative or upon request by the Flight Operations Evaluation Board (FOEB) Chair. The Office of Safety Standards division responsible for the PL is the approving authority for all GC extension requests. Although a GC designation may expire, the PL itself is still applicable until amended or archived.

9.2.3.4 Review and Approval. The POI has the authority to approve the operator’s MEL revision on the basis that the GC is an approved addendum to the existing MMEL.

### Page 43

9-3

9.2.3.5 Header Box. A GC will contain a header box that will explain its applicability. The header box will also contain requirement(s) on how to apply the sample proviso(s) of the GC to an operator’s MEL. See Figure 9-1 below for an example of a GC header box.

Figure 9-1. Example Global Change Header Box

MMEL GLOBAL CHANGE (GC) This is an approved addendum to all existing MMEL documents. Operators may seek use of the specific relief contained in this PL by revising their minimum equipment list (MEL). In doing so, each applicable sample proviso stating the relief in this PL must be copied verbatim in the operator’s MEL. Approval of a revised MEL is gained utilizing established procedures, through the operator’s assigned Principal Operations Inspector (POI).

9.2.4 Revisions Initiated by a Flight Standards Service (FS) Office. The operator’s responsible Flight Standards office may require the operator to initiate an MEL revision for reasons such as the issuance of an Airworthiness Directive (AD), discovery of deficiencies in the operator’s MEL (including Maintenance (M) and Operations (O) procedures) or when the operator modifies their fleet. The operator’s responsible Flight Standards office will inform the operator in writing of the need to revise their MEL, including the reason(s) for the required revisions. The operator is allowed 90 days to complete the revision process.

The responsible Fight Standards office may specify a lesser period if the PIs determine that safety of flight could be affected.

9.3 Operator-Initiated Revisions. An operator-initiated MEL revision may not be less restrictive than the MMEL. An operator may revise their MEL for a number of reasons such as aircraft modifications, installation of additional equipment, changes in types of operation, or changes in maintenance or operational procedures. Operators may also revise their MEL due to suggestions or findings from their safety programs, such as Safety Management System (SMS) or Aviation Safety Action Program (ASAP).

9.3.1 Major Aircraft Modifications. An operator may need to initiate an MEL revision due to major aircraft modifications, such as a Supplemental Type Certificate (STC), a major alteration (FAA Form 337, Major Repair and Alteration (Airframe, Powerplant, Propeller, or Appliance)), or a modification to the type certificate (TC). (See Chapter 4, MEL Relief for Items Installed After Type Certification, for design changes to a TC.)

9.3.2 In stallation of Additiona l Items. An operator may initiate a change based on the installation of additional items. An operator may only add an item to their MEL if it is included in the MMEL. If an operator desires relief for an item that is not included in the MMEL, the operator may request an MMEL revision from the FOEB Chair, through their PI or directly through the Aircraft Evaluation Division (AED) (refer to FAA Order 8900.1 for information regarding the FOEB and the MMEL revision process).

### Page 44

9-4

9.3.3 Changes in Operational Complexity. An operator may need to revise their MEL due to changes in operational complexity, such as adding a type of operations (e.g., passenger carrying operations) or additional OpSpec/MSpec authority (e.g., Extended Operations (ETOPS) or Category (CAT) II/II landing minimums).

9.3.4 C hanges in (M) and (O) Procedures. (M) and (O) procedures may need to be revised due to changes in operational complexity, a change by the Original Equipment Manufacturer (OEM) in recommended procedures, or as the result of analysis of data acquired through the operator’s SMS program (the Safety Assurance Process) or from voluntary programs such as ASAP data.

### Page 45

**10-1 CHAPTER 10. NONESSENTIAL EQUIPMENT AND FURNISHINGS (NEF)**

**PROGRAM**

10.1 Background. The NEF program originated from an earlier form called Passenger Convenience Items (PCI) program. Passenger convenience items were items related to passenger convenience, comfort, or entertainment located in the passenger compartment, galley, and lavatory areas. The PCI program did not allow for nonessential items that were missing or inoperative located elsewhere in the aircraft. Due to the limited nature of PCI, the FAA replaced the PCI title in Air Transport Association of America (ATA) code 25 in all MMELs with the acronym NEF. An NEF program allows operators to use the deferral authority granted by virtue of their operations specification (OpSpec)/management specification (MSpec) to provide deferral relief for nonessential items located throughout the aircraft.

10.2 General. An operator may develop an NEF program to meet its individual needs and may submit it to the FAA for approval. The NEF program resides within an operator’s MEL management program. The NEF program encompasses a list of NEF items located in the operator’s MEL, a process for evaluating an item in accordance with NEF requirements, reporting procedures, and policies and procedures for repair or replacement. Operators may choose to use the recommended method of evaluation shown in Figure 10-2, NEF Item Selection C riteria Elements Flowchart, or they may use an alternative, yet equivalent, method that is acceptable to the FAA. If the supporting policies and procedures are insufficient or systemically problematic, the FAA may remove the NEF authority from the approved MEL and reapprove the MEL without it.

10.2.1 NEF Items. N EF items are:

• Items installed on the aircraft that have no effect on the safe operation of the aircraft.

• Items installed as part of the original type certificate (TC), Supplemental Type Certificate (STC), Engineering Order (EO), or other form of alteration, not required by certification or operational rules.

• Items that if inoperative, damaged, or missing, have no effect on the safe operation of the aircraft under all operational conditions.

• Nonessential items located throughout the aircraft, including the flight deck area, service areas, cargo areas, and crew rest areas, in addition to the passenger compartment, lavatories, and galley areas.

• Cosmetic items not associated with an MEL or CDL item.

Note: Cosmetic items may have associated fire retardant or blocking requirements to be considered before approval as an NEF item.

10.2.2 No n -NEF Items. NEF items are not:

• Instruments and equipment already identified in the MEL or CDL of the applicable aircraft.

### Page 46

10-2

• Instruments and equipment functionally required for meeting any certification rule.

• Instruments and equipment required for compliance with any operational rule.

• Items deferred contrary to an operator’s Continuous Airworthiness Maintenance Program (CAMP).

• Paint (mismatched, bad, or worn condition).

Note: Paint is addressed in other maintenance documents utilized for determining airworthiness; the NEF program is not applicable.

• Rodent or pest (bug) infestations of any type.

• Items which are only dirty or soiled (e.g., carpet, seats, interior sidewalls, dirty garbage can, etc.).

Note: An NEF item is not to be used as an administrative control item (ACI). An ACI is listed in the MEL for tracking and informational purposes. (Refer to MMEL PL-25 for more information regarding ACIs.)

10.3 Deferral Authority. The deferral authority granted by the operator’s OpSpec or MSpec is the basis for developing an operator-specific NEF program.

10.3.1 Although the NEF program is included in ATA chapter 25, it may address items that fall under other ATA chapters.

10.3.2 The operator’s NEF process may not provide for deferral of items within serviceable limits identified in the manufacturer’s maintenance manual, Structural Repair Manual, Airworthiness Directives (AD), or operator’s maintenance program (e.g., CAMP, General Maintenance Manual (GMM), etc.).

10.3.3 NEF items are deferred under the operator’s approved NEF program, not under the authority of an Airframe and Powerplant (A&P) certificate.

10.3.4 The NEF program for a part 91K, 121, 125, or 135 operator is part of, and resides within, the operator’s MEL management program.

10.4 N EF Program Development. Each operator implements, maintains, and revises its NEF program. The NEF program provides for the ability to defer NEF items whose failure would otherwise result in a non-airworthy status until repair (or replacement) of an item not affecting safety of flight. The responsible FAA principal inspector (PI) monitors the operator’s NEF program and handling of NEF items. Failure to comply with the FAA-approved NEF program may result in the removal of the NEF program authorization.

10.5 Required NEF Program Contents. The operator will design its NEF program to fit its scope and depth of operation, including at a minimum the following ten processes and procedures:

### Page 47

10-3

10.5.1 M ethod of Tracking NEF Items. A list or other equivalent method of tracking NEF items may be used. Although an operator does not need to develop and maintain a list, nor include the specific NEF items inside the MEL, a list reduces both the FAA and operator’s time spent analyzing recurring deferrals of the same item. Operators who choose not to develop an NEF list will treat each NEF deferral as a newly discovered NEF item, as outlined in their individual NEF program.

10.5.1.1 If a List Is Not Used. FAA safety inspectors will work with those operators who choose not to develop a NEF list to determine a mutually acceptable timeframe in which each newly identified and deferred NEF item will be reported for review.

10.5.1.2 If a List Is Used. If the operator develops a list, the Principal Operations Inspector (POI) (or aviation safety inspector (ASI) with MEL oversight responsibility) will review all subsequent additions/revisions.

1. The NEF list should be comprehensive but may be listed in general terms with the concurrence of the POI or ASI with oversight responsibility. For example, cosmetic trim-strips may be listed rather than identifying each strip individually on the NEF list.

2. Either in paper or electronic format, the applicable portions of the list (if applicable) and NEF process should be available to the flight and cabin crews, maintenance, and flight operations personnel, as appropriate, when items are being deferred in accordance with the operator NEF program.

3. Parts 91K, 121, 125, and 135 operators should work with POIs to determine a mutually acceptable timeframe in which the newly identified and deferred NEF items will be reported for review.

10.5.2 I dent ifying Deferrals. Procedures and processes for identifying NEF items that may be deferred.

10.5.3 Tracking Deferrals. Procedures for tracking program deferrals.

10.5.4 Reporting Deferrals. Procedures for the reporting of deferrals, as required, to the POI (parts 91K, 121, 125, and 135).

Note: N EF lists and processes may reside together or separately in the location and manner selected by the operator and acceptable to the POI/ASI.

10.5.5 D ocumentation Procedures. Documentation procedures for inoperative, damaged, or missing NEF items.

10.5.6 (M) and (O) Procedures. Appropriate (M) and (O) procedures.

10.5.7 Follow-Up Maintenance. Procedures for follow-up maintenance, repair, and replacement.

### Page 48

10-4

10.5.8 Repair Intervals. Repair intervals are prescribed for NEF items. Operators may use the current MEL deferral categories at their discretion or an alternate method acceptable to the Administrator.

10.5.9 Section 43.13 Compliance. Any portions of an NEF program that reference maintenance or a maintenance procedure must comply with acceptable practices as set forth in § 43.13.

10.5.10 N EF Proviso . The following proviso to an NEF program (see Figure 10-1 below) is included in MEL ATA chapter 25 for approved NEF programs under parts 91K, 121, 125, and 135. The reference proviso should be copied verbatim. The aircraft operator’s manual containing the NEF program will contain specific processes and procedures as indicated in the proviso.

Figure 10-1. Required NEF MEL Proviso for an FAA-Approved NEF Program System & Sequence Numbers 25 Equipment / Furnishings Repair Interval Number Installed Number Required For Dispatch Remarks or Exceptions Nonessential Equipment and Furnishings (NEF)

- - 0 May be inoperative, damaged, or missing provided that the item(s) is deferred in accordance with the NEF deferral program. The NEF program, procedures, and processes are outlined in the operator’s [insert name] Manual. (M) and (O) procedures, if required, must be available to the flightcrew and included in the aircraft operator’s appropriate document.

NOTE: Exterior lavatory door ash trays are not considered NEF items.

10.6 NEF Program Approval. Parts 91K, 121, 125, and 135 operators submit their NEF program to the responsible Flight Standards office with oversight responsibility for approval. Once approved, a reference proviso to the program is to be incorporated into the MEL ATA chapter 25 (see Figure 10-1).

10.6.1 An operator may develop and submit a list of items desired to be included on the NEF list. As the NEF program is part of the MEL, FAA concurrence is required for approval of the operator’s program in accordance with § 91.213.

10.6.2 The NEF list does not have to be part of the standard MEL and may be kept in a form and manner agreed upon by the operator and the FAA.

### Page 49

10-5

10.7 NEF Program Revisions. All additions and revisions to an FAA-approved NEF program are reviewed by POIs.

10.8 Criteria for Selection of NEF Items. NEF items are not safety of flight items and are not evaluated by the FAA through the normal Aircraft Evaluation Division (AED) review process. NEF items may require the concurrence of FAA maintenance and operations inspectors. An operator will follow its FAA-approved NEF program procedures in order to list an item as being deferrable under the NEF program. When reviewing items for inclusion in an operator’s NEF program, FAA inspectors will ask the following questions:

1. Is the item required for the operational rules in which the aircraft is operated?

2. Is the item required to be functional by the applicable certification requirements?

3. Does the item create the potential for fire/smoke or other hazardous condition?

4. Could the item have an adverse effect on other required systems or components?

5. Does the item’s condition potentially affect the safety of passengers, crew, or service personnel?

6. Could the item have a negative impact on emergency or abnormal procedures?

7. Does the item create an additional workload for the crew at critical times of flight or flight preparation?

8. Do crewmembers need to evaluate the deferred NEF item on a flight-by-flight basis?

Note: See Figure 10-2 for a flowchart that includes the following elements in sequence. The flowchart is provided as a guide for developing an NEF deferral process. The process may be modified to facilitate inclusion in an operator’s overall MEL deferral program with the intent of the elements outlined in the flowchart below being addressed.

10.8.1 Documentation. For an inoperative, damaged, or missing item to be considered for inclusion in an NEF program, the discrepancy will be documented in the aircraft logbook (or other approved location) per the operator’s discrepancy reporting system. This action is completed by the flightcrew, company maintenance personnel, or personnel authorized and approved to perform such functions as outlined in the operator’s maintenance program.

10.8.2 Current NEF Items. If the inoperative, damaged, or missing item is already on the NEF deferral list (if used), the established procedures for NEF deferral of the item will be followed.

10.8.3 MMEL, CDL, or MEL Items. An MMEL, CDL, or MEL item may not be deferred in accordance with the operator’s NEF program. The operator must follow the deferral procedures for inoperative, damaged, or missing items listed in the MMEL, MEL, or CDL, as per § 91.213(a)(5).

### Page 50

10-6

10.8.4 Subcomponents of MMEL, CDL, or MEL Items. If the inoperative, damaged, or missing item is a subcomponent of a system identified in the MMEL/MEL/CDL, where no previous relief was authorized, the subcomponent may not be deferred in accordance with the operator’s NEF program.

10.8.5 R equired by Certification or Operational Rules . If the item is required by any applicable certification or operational rules, the item may not be deferred in accordance with the operator’s NEF program.

10.8.6 S afety of Fli ght Issues. If it is evident from a maintenance or operational perspective that an item could have an adverse effect on safety of flight; or if there is a safety of flight issue with an inoperative, damaged, or missing item, that item may not be deferred.

10.8.7 S ource (Underlying Cause). If the presence of a safety of flight issue is unknown, not present, or not applicable, ascertain whether the source or root cause for the item can be identified. If the source or root cause cannot be identified or isolated, that item may not be deferred in accordance with the operator’s NEF program. If the item has no impact on the safety of flight, that item may be deferred in accordance with the operator’s NEF program. If the item can be isolated and reevaluated using applicable maintenance procedures and a determination made that there is no safety of flight concern, it may be deferred in accordance with the operator’s NEF program.

10.8.8 D efer in Accordance w ith the Operator’s NEF Program.

10.8.9 Update the NEF List, as Required.

10.8.10 Provide the NEF Items to the Responsible Flight Standards Office.

### Page 51 (OCR)

Figure 10-2. NEF Item Selection Criteria Elements Flowchart

1. Documentation:

Discrepancy Noted in Logbook Defer in Accordance YES 2. Current With the Operator's NEF Item?

NEF Program NO Follow MMEL/CDL/ YES 3. MMEL/CDL/ MEL Procedures MEL Item?

NO May NOT be Deferred • YES 4. MMEL, CDL.

in Accordance With MEL Item NEF Program Subcomponent?

NO May NOT be Deferred YES 5. Required for in Accordance With NEF Program Cert or Op Rules?

NO Repair the Item YES 6. Safety of Prior to Flight Flight Issue?

_ NO, Unknown, or N/A Repair the Item Prior to Flight NO 7. ID Source (Underlying Cause)?

YES or N/A Repair the Item YES Equivalent Level of 8. Effects an NO → Accerdance With Defer in Prior to Flight Safety? the Operator's NEF Program Uncertain

(1) YES, Repair the Item NO . Isolated With Reevaluate Prior to Flight Applicable Maint Procedures?

(2) YES, Passed Reevaluation

10. Defer in Accordance With 11. Update NEF the Operator's List as Required NEF Program

12. Provide NEF Items to Responsible Flight Standards Office 10-7

### Page 52

**11-1 CHAPTER 11. CONFIGURATION DEVIATION LIST (CDL)**

11.1 Purpose of the CDL. The CDL is a list of externally exposed nonstructural aircraft parts that may be missing, and is tailored for each model aircraft. The CDL evolved over several years from what was commonly known as a “missing parts list,” which was a list of nonstructural external parts of an aircraft that were found missing after flight. A CDL allows continued operation with missing externally exposed nonstructural parts by defining restrictions, limitations, or performance penalties, while the aircraft remains airworthy.

11.2 Development. The aircraft manufacturer develops a CDL during the initial certification process. This is not a requirement for aircraft certification. The manufacturer makes the decision to develop or not to develop a CDL. The responsible Aircraft Certification Service office has final approval of all FAA-approved CDLs and all requests for revisions to an FAA-approved CDL.

11.2.1 Which Aircraft Has a CDL. A CDL is developed for most U.S.-built transport category part 25 aircraft and many part 23 aircraft by aircraft manufacturers during the initial certification process. If deemed necessary, the aircraft manufacturer develops a proposed CDL and coordinates submission with the responsible Aircraft Certification Service office and the Aircraft Evaluation Division (AED). The responsible Aircraft Certification Service office and the AED review, evaluate, and may conduct or oversee any required testing and data collection necessary to approve proposed CDL items. Approval of a CDL is by the responsible Aircraft Certification Service office or through an Original Equipment Manufacturer’s (OEM) Organization Designation Authorization (ODA) program.

11.2.2 U. S. -Manufactured Aircraft. For U.S.-manufactured aircraft, an FAA-approved CDL is either:

• Incorporated into the limitations section of the Airplane Flight Manual (AFM);

• Published as an appendix to the AFM; or

• Published as a supplement to the AFM.

11.2.3 Aircraft Manufactured Outside the United States. The CDL may be a standalone document that is part of the Structural Repair Manual or other manufacturer’s document.

11.3 Operator Use of the CDL.

11.3.1 FAA-Approved CDL. An operator may use a CDL and incorporate it into its manual system. However, the manufacturer’s CDL is already approved by the responsible Aircraft Certification Service office and therefore, will not be approved or accepted by the responsible Flight Standards office. It should not appear on the List of Effective Pages (LEP) of an operator’s MEL or any other documents showing approval or acceptance by the responsible Flight Standards office. The manufacturer’s CDL may be

### Page 53

11-2 attached to the operator’s MEL, but should be treated as a separate and “standalone” document.

11.3.1.1 The manuals used by flightcrew members, maintenance personnel, and dispatch personnel should include instructions governing CDL use. An operator may increase fuel and performance penalties or add additional limitations and restrictions beyond what is already required in the FAA-approved CDL. These additional penalties, limitations, and restrictions may be listed in the operator’s manual system and should be submitted to the responsible Flight Standards office for approval or acceptance. Such additions should be delineated as “operator-specific” requirements and under no circumstances be less restrictive than the FAA-approved CDL.

11.3.1.2 If an operator desires an amendment to the manufacturer’s CDL, such requests may be coordinated with the responsible Aircraft Certification Service office through the responsible Flight Standards office, directly with the responsible Aircraft Certification Service office, or directly with the aircraft manufacturer.

11.3.2 O perator- Specific CDL. An operator may also choose to create an operator-specific CDL for use in its operation, using the FAA-approved CDL’s data. Operators creating their own operator-specific CDL should not confuse this CDL with the official FAA-approved CDL or make it less restrictive than the FAA-approved CDL. Operator-specific CDLs will be accepted by the responsible Flight Standards office and be incorporated into an operator’s manual system.

11.4 O perato r’s Manual. Operators should consider having policies and procedures in their manual system regarding use of the CDL, such as:

• A description of how the CDL is applied and utilized in their operation.

• Instructions on where to access current FAA-approved CDLs for specific model aircraft and future revisions.

• Methods for the proper application of fuel and performance penalties, procedures, or restrictions and limitations while conducting flight operations utilizing the CDL.

• A page control system to show that the operator-specific CDL is current and complete (if one has been developed by the operator).

• A page control system associated with the manufacturer’s CDL that is approved by the responsible Aircraft Certification Service office.

• The policies and procedures may be combined within the operator’s approved MEL management program procedures.

11.5 CDL Item Recording and Notifications. Operators should establish a standard procedure for advising flightcrews, aircraft dispatchers, and maintenance personnel of an aircraft’s status with current CDL and MEL issues along with the conditions and limitations that apply.

### Page 54

11-3

11.5.1 R eporting of Found CDL Items. If a CDL item(s) is discovered missing by:

11.5.1.1 Maintenance Person Positioned at the Aircraft. If a CDL item is discovered missing by maintenance personnel, that person notifies the flightcrew and the maintenance organization (e.g., Maintenance Control).

11.5.1.2 Flightcrew. If a CDL item is discovered missing by the flightcrew, the flightcrew notifies the maintenance organization and appropriate flight operations personnel.

Note: The maintenance organization or flightcrew notifies flight operations personnel (e.g., dispatch, flight following, or other persons authorized to exercise operational control) in accordance with the aircraft operator’s approved MEL or CDL procedures.

11.5.2 L ogging and Notification Requirements. Each missing CDL item is entered into the aircraft maintenance logbook and listed on a placard, which is then affixed in the cockpit in clear view of the flightcrew, per the AFM. Principal Operations Inspectors (POI) may allow operators to use their MEL procedures for addressing an aircraft’s CDL status and limitations. Such procedures will conform to the AFM CDL placarding requirements.

11.5.3 Fuel and Performance. Fuel and performance penal ties, limitations, and restrictions associated with each CDL item are calculated and entered in the appropriate flight documentation (e.g., dispatch, flight release, or flight plan). If flight documentation has been issued prior to the application of the CDL item, the operator will ensure that fuel and performance planning are recalculated in accordance with the CDL item, if applicable. Operators conducting part 121 operations should issue a new or amended dispatch or flight release to include these penalties.

### Page 55

Advisory Circular Feedback Form If you find an error in this AC, have recommendations for improving it, or have suggestions for new items/subjects to be added, you may let us know by contacting the Air Transportation Division at 9-AFS-200-Correspondence@faa.gov or the Flight Standards Directives Management Officer at 9-AWA-AFB-120-Directives@faa.gov.

Subject: AC 120-125, Development and Use of an Operator’s MEL, NEF Program, and CDL for Operations Under 14 CFR Parts 91K, 121, 125, and 135 Date: _____________________ Please check all appropriate line items:

An error (procedural or typographical) has been noted in paragraph ____________ on page _______.

R ecommend paragraph _____________ on page __________ be changed as follows:

______________________________________________________________________ ______________________________________________________________________ In a future change to this AC, please cover the following subject:

(Briefly describe what you want added.)

______________________________________________________________________ ______________________________________________________________________ Other comments:

______________________________________________________________________ ______________________________________________________________________ I would like to discuss the above. Please contact me.

Submitted by: Date: ______________________

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.
