ED Decision 2014/004/R
These Certification Specifications establish the specifications for the applicant for a type certificate, change approval or supplemental type certificate to develop and provide the Master Minimum Equipment List (MMEL) as part of the Operational Suitability Data (OSD) defined in Part 21 .
ED Decision 2020/012/R
These Certification Specifications for establishing the MMEL are applicable to complex motor‑powered aircraft and to non-complex helicopters that are certified for:
— operation under instrument flight rules (IFR),
— flight into icing conditions, or
— Category A operations.
Issue No: MMEL/2
ED Decision 2014/004/R
For the purpose of this CS, the following terms mean:
(a) ‘Applicant’: an applicant for, or a holder of, a type certificate (TC), change approval or supplemental type certificate (STC), applying for the approval by the European Aviation Safety Agency (hereinafter referred to as ‘the Agency’) of the Operational Suitability Data (OSD) related to MMEL.
(b) ‘Calendar Day’: a 24-hour period from midnight to midnight based on either UTC or local time, as selected by the operator.
(c) ‘Catastrophic Failure Condition’: as defined in the applicable Type Certification Basis.
(d) ‘Day of discovery’: the calendar day when a malfunction was recorded in the aircraft maintenance record/log book.
(e) ‘End user’: an operator or training organisation having a Minimum Equipment List (MEL) based on the MMEL approved by the Agency.
(f) ‘External Event’: an occurrence which has its origin distinct from the aircraft or the system being examined, such as atmospheric conditions (e.g. wind gusts/shear, temperature variations, icing, lightning strikes), operating environment (e.g. runway conditions, conditions of communication, navigation and surveillance services), cabin and baggage fires, and bird strike.
(g) ‘Flight Day’: a 24-hour period from midnight to midnight based on either UTC or local time, as selected by the operator, during which at least one flight is initiated for the affected aircraft.
(h) ‘Hazardous Failure Condition’: as defined in the applicable Type Certification Basis.
(i) ‘Inoperative’: an item which does not accomplish its intended purpose or is not consistently functioning within its approved operating limits or tolerances.
(j) ‘Item’: a component, instrument, equipment, system or function.
(k) ‘Rectification Interval (RI)’: a limitation on the duration of operations with inoperative items.
ED Decision 2014/004/R
CALENDAR DAYS
All calendar days are considered to run consecutively.
ED Decision 2014/004/R
INOPERATIVE
Some items have been designed to be fault tolerant and are monitored by computers which transmit fault messages for the purpose of maintenance. The presence of this category of message does not necessarily mean that the item is inoperative.
ED Decision 2014/004/R
ITEM
(a) In the context of these Certification Specifications, a component is considered to be a piece of equipment or instrument.
(b) In the context of these Certification Specifications, a system is considered to be a collection of equipments and/or instruments that perform a function. (See AMC 25.1309)
CS MMEL.107 Status of provided data
ED Decision 2014/004/R
(a) CS-MMEL Subpart B specifies data provision which is required from the applicant and data provided at request of the applicant. Data provided by the applicant is presented as mandatory or non-mandatory (recommendations) for the end user.
(1) Data required from the applicant and mandatory for the end user:
(2) Data required from the applicant and non-mandatory (recommendations) for the end user:
(3) Data at request of the applicant and mandatory for the end user:
CS MMEL.110 (Non-safety-related items only).
(4) Data at request of the applicant and non-mandatory (recommendations) for the end user:
(b) CS-MMEL Subpart C provides specifications on the development of the MMEL and associated justifications to be developed by the applicant.
GM1 CS MMEL.107(a) status of provided data: OSD box concept
ED Decision 2014/004/R
OSD BOX CONCEPT DIAGRAM
Box 1: Required from the applicant; mandatory for end users.
Box 2: Required from the applicant; non-mandatory (recommendations) for end users.
Box 3: At request of the applicant; mandatory for end users.
Box 4: At request of the applicant; non-mandatory (recommendations) for end users.
GM2 MMEL.107(a) Status of provided data: OSD box concept
ED Decision 2020/012/R
(a) Because of the alleviative nature of the MEL, the fact that the MMEL is mandatory data for the end-user means that the MEL is not less restrictive than the MMEL, but it may be more restrictive.
(b) The content of the operational and maintenance procedures provided by the applicant is recommended to the end user as defined in ORO.MLR.105(g).