PPRuNe Forums

PPRuNe Forums (https://www.pprune.org/)
-   Tech Log (https://www.pprune.org/tech-log-15/)
-   -   MEL definition (https://www.pprune.org/tech-log/552003-mel-definition.html)

jaja 27th Nov 2014 20:23

MEL definition
 
A quick question for the knowledgeable :

I am looking for the definition of "commencement of flight" with regard to MEL.

I want to find the present valid EASA documents on this.

Thank you !

Skyjob 27th Nov 2014 20:52


‘Commencement of flight’ is the point when an aircraft begins to move under its own power for the purpose of preparing for take-off.
CS-MMEL (Certification Specifications and Guidance Material for Master Minimum Equipment List), Book 2 – Guidance Material, Subpart B, Master Minimum Equipment List, GM5 MMEL.120 Format and content of MMEL, Definitions And Explanatory Notes

For an older reference to JAR:
Commencement of flight is defined in JAR-MMEL/MEL.001(d) and .005(d) as “the point when an aircraft begins to move under its own power for the purpose of preparing for take-off.” In the case of a helicopter, it refers to the moment the helicopter commences air or ground taxi.

torghabe 28th Nov 2014 08:43

So, MEL working on the ground until "the point when an aircraft begins to move under its own power for the purpose of preparing for take-off", after that point- QRH only.

8che 28th Nov 2014 09:10

Not QRH only ! Life's not that simple. You would be foolish not to consult the MEL after taxi particularly for take off where the failure affects performance (or indeed something that will stop you returning from destination). That's Captaincy



For example Antiskid fail. The QRH says nothing but the MEL details the various takeoff performance penalties which you must still apply whether you have dispatched or not.

Ollie Onion 28th Nov 2014 09:35

And just be careful because it CAN be airline specific. For example our aircraft aren't defined as dispatched until take off power is set. So any fault prior to takeoff is subject to MEL.

john_tullamarine 28th Nov 2014 10:33

And just be careful because it CAN be airline specific

Generally, such will be the case.

The MMEL must be tailored to suit the operator and then processed through whatever regulatory approval process applies in the particular jurisdiction.

Sometimes the regulator will help out - developing an MEL is a painful exercise - as, for instance, in Australia where, for a period, CASA developed a generalised MEL (GMEL) for given Types which the operator could purchase for a fee much more attractive than the cost of a do-it-yourself animal. The GMEL system fell into disuse for reasons I have never discovered ..

Having had some involvement in MEL (and GMEL) development and defect investigation, I can only shake my head at the philosophy that holds a flight starts prior to takeoff ..

om15 28th Nov 2014 12:43

EASA Air Operations Requirements ORO.MLR.105 MEL


"The Operator should include guidance in the MEL on how to deal with any failures that occur between the commencement of the flight and the start of the take off run".


As I understand it this guidance should include how to comply with the O&M procedures in that period between taxy and take off.

torghabe 1st Dec 2014 07:39

8che, you"re on! ..."the point when an aircraft begins to move under its own power for the purpose of preparing for take-off, after that point- QRH only." It means- if you are on the RW and start moving for T/O. Sure, if you taxi to the RW and EICAS messages appears, NNCL first, MEL second, decision third. But if you start moving on the RW for T/O purpose, QRH- first and later you CAN use MEL, but for reference only.

framer 1st Dec 2014 07:49

If you fly for an outfit that doesn't clarify exactly what is expected between pushback and comencement of the takeoff roll then you probably fly for a crap outfit.....if that is the case, the safety of the paying public relies on the Captains sound judgement and knowledge only. No systemic back up. It'll work well most of the time, it won't work well when the Captain is a fruit-loop.

jaja 1st Dec 2014 09:15

Thank you Skyjob for the EASA reference.

When you read the definition on commencement of flight, it says
"the point when an aircraft begins to move under its own power for the purpose of preparing for take-off".
You could read this in two ways, either as beginning of the taxi phase, or the Take Off roll. But in the "old" JAR documents it says further :

"The operator's MEL should include procedures to deal with any failures which
occur between the start of taxi or push back and take-off brake release (see
ACJ to JAR-MMEL/MEL.001(d)). Any failure which occurs after take-off
commences should be dealt with as an in-flight failure, by reference to the
appropriate section of the Aircraft Flight Manual, if necessary."

(do you have the above as an EASA document ?)

As I understand it, "the point when an aircraft begins to move under its own power for the purpose of preparing for take-off" means the taxi phase, agree ?


If that is correct, then according the above, we should have tailored "on-ground Abnormal Procedures" (we fly Airbus`s) to cover the part of the flight from were it commences (beginning of taxi) until T/O ?

Skyjob 1st Dec 2014 12:48

The EASA reference given is and can be explained either way. So it is up to an individual operator to establish the policy for its fleet and remove ambiguity.

As 8che mentioned, some operators rely on Captaincy to return to stand should a failure occur prior to departing during taxi, some require a return to stand no matter what.

Some failures (eg turnoff light failing) are benign but others (eg an antiskid failure) not so. Captaincy requires the Captain of the vessel to make an informed judgement call (decision) whether to continue the flight, having established the failure prior to departure, or to return to stand and have it looked at by Engineers, or speak to Engineers before continuing the flight without a return to stand, or to refer to MEL/CDL and assess if possible to apply restrictions for the flight to be undertaken instead delaying the aircraft further even though the restriction is not (yet) raised as a defect in the technical log of the aircraft.

There is no EASA defence to Captaincy and the area between the lines is in the hands of the Operator to define.

SkyWagon737 2nd Dec 2014 01:33

The definitions will not save your a$$ , but your decisions. Your company will ask you at the end. It is always good to check MEL for futher actions and it gives you vaulable information.

LeadSled 2nd Dec 2014 11:58


For example our aircraft aren't defined as dispatched until take off power is set
Folks,
That is close enough to the FAR definition for government work, the MEL applies up to the point of commencement of takeoff. It definitely does not mean commencement of taxiing.
Sorry I can't give a reference, too late at night.

PS: Have a look through a B744 or B767 etc. MEL, at the king of things that can happen between commencement of taxi, and ask yourself if you would want to get airborne.

Sue Ridgepipe 5th Dec 2014 00:50

Our airbus MEL says this...

The provisions of the MEL are applicable until the start of the takeoff roll.
If a failure occurs between Pushback (OFF BLOCKS) and the takeoff roll, flight crew must complete all actions as required by the failure, including ECAM Actions and then refer to the MEL .

mgTF 28th Dec 2014 11:29

MEL are NOT legally binding ONLY after the takeoff roll has begun.
From the moment the plane moves under its own power to takeoff roll, MEL are still legally binding.

The spirit of the sentence is that if you have an APU fire after pushback, first you deal with the fire drills as per QRH, then eventually consider a dispatch with an inop APU, though I guess first you want to investigate the fire damages :E

Dufo 28th Dec 2014 11:49

After engine start, MEL and/or QRH apply in our joint. Plus common sense and captain discretion. All well written and explained.

vilas 28th Dec 2014 12:15

Start of flight is although company specific there are far too many issues to consider before you take off and it is not possible or practical to apply MEL during taxi and if you ignore it because by definition the flight has begun it could have serious implications and land you in trouble. The least of which is getting grounded at destination where maintenance is not available. Prudent option is to return to dispersal switch off and do the needful.

Skyjob 28th Dec 2014 16:14


Prudent option is to return to dispersal
And herein lies the discretion of application.
If a failure would occur at home base with engineering support it may be more prudent to return to stand, whereas if the same failure had occurred down-route at an outstation it would probably more prudent to "return to dispersal".
Same failure, different choice made by, but both governed by the same definition in MEL, both correct.

jaja 23rd Jun 2018 06:53

So please give examples of which major airlines in Europe, apply the MEL up until takeoff power is set, and not just until start of taxi.

PENKO 23rd Jun 2018 07:21

Just to be clear, it's misleading in this discussion to say 'the MEL applies'.
The MEL does not 'apply' anything. What applies is that you go back to the gate, open the doors, enter the defect in the tech log, call an engineer, wait an hour for the engineer to arrive, and THEN, if the fault cannot be cleared in a reasonable time frame, possibly apply the MEL in order to dispatch.

PENKO 23rd Jun 2018 07:40

This is what EASA states in its document 'Certification Specificationsand Guidance Material for Master Minimum Equipment List CS-MMEL':

‘Commencement of flight’ is the point when an aircraft begins to move under its own power for the purpose of preparing for take-off.
[...]

Operators should include guidance in the MEL to deal with any failures which occur between the commencement of the flight and the start of the take-off.
So it is very, very, very clear till what stage a defect needs to be entered in the Tech Log, rectified by an engineer or possibly deferred under the MEL: the release of the parking brake for taxi.

You'd be surprised how many pilots don't grasp this simple fact

sonicbum 23rd Jun 2018 08:31


Originally Posted by PENKO (Post 10179730)
the release of the parking brake for taxi.

100% agree, my previous operator had exactly the same wording in our OM(A) and that cleared any possibile doubts amongst the pilot population. My current one uses the wording "commencement of the flight" which should still be pretty clear but does indeed create confusion sometimes over a widespread fleet. As we all know most of the times wording is kept in such a way that it can be twisted and interpreted as needed depending on whom is supposed to be right or wrong :E

pineteam 23rd Jun 2018 09:08

Same as PENKO.

From our FOM:

''The crew must refer to the MEL if a failure occurs or a component is degraded or a function is inoperative before taxi-out. If a failure occurs between the start of taxi ( when the aircraft begins to move under his own power) until the start of the takeoff roll it is subject to good pilot judgement and airmanship. The PIC may refer to the MEL to make an assessment before any decision to continue the flight is taken. This is particularly true for those failures that might affect the takeoff performance (i.e loss of spoilers, brake failure, etc.).''

spannersatcx 23rd Jun 2018 09:09


Originally Posted by PENKO (Post 10179721)
Just to be clear, it's misleading in this discussion to say 'the MEL applies'.
The MEL does not 'apply' anything. What applies is that you go back to the gate, open the doors, enter the defect in the tech log, call an engineer, wait an hour for the engineer to arrive, and THEN, if the fault cannot be cleared in a reasonable time frame, possibly apply the MEL in order to dispatch.

Maybe where you are, WE are on the headset for departure at our airline! :p

jaja 23rd Jun 2018 09:37

No it is not clear when to apply the MEL or the Abnormal checklist, but it used to be clear (up to approx 15 years ago).

The MEL should be applied up until setting takeoff power if you have failures on startup/taxi, and when airborne you look into the Abnormal checklist. That is the way we used to do it.

Let me give an example why : on taxi out you have an ECAM warning, and this failure is a “NO DISPATCH” according to the MEL. Common sense would be not to continue the flight, but as it is company procedure in many places, it is up to captain to decide if it is OK to continue (after using “good airmanship etc”.

In todays complex aircraft it should not be up to the captain to decide that. The MEL should be used/applied up to setting takeoff power.

Please give examples on in which European companies is the MEL used/applied that way (up to setting takeoff power) ?



pineteam 23rd Jun 2018 10:08

Many MEL '' No dispatch'' are conservative and therefore not busine$$ friendly so it would not necessary make sense to return to the gate especially if you are in a remote area where they would not be able to fix the aircraft. Most of the time, it will have zero effect on the flight as there is redundancy. As long as you are aware of the potential consequences and comfortable with it. Then why not continue. I personally like the way it is. :)

jaja 23rd Jun 2018 10:12

Yes Pineteam, that is also the answer I get from many, BUT if we have such good system redundancy why should we in the first place appy the MEL restrictions if we have failures before pushback ? It does not make sense !

pineteam 23rd Jun 2018 10:16

Maybe since we are still att the gate, probably with no pax on board with engines shut down, and maintenance available it's worth it to try and fix it? During taxi we are left alone. xD
Just speculating. I'm not sure why. xD

sonicbum 23rd Jun 2018 10:23


Originally Posted by jaja (Post 10179855)
Yes Pineteam, that is also the answer I get from many, BUT if we have such good system redundancy why should we in the first place appy the MEL restrictions if we have failures before pushback ? It does not make sense !

The MEL provisions also consider the worst case scenario of a subsequent inflight failure of another critical system and therefore protects You accordingly. Once the applicability of the MEL ceases it is up to You to cater for all the different scenarios that could happen and decide. Regardless of what the MEL says the final word is anyway always with the flight crew (ie the Captain) if a more restrictive interpretation of the MEL is required given the conditions of the day.

jaja 23rd Jun 2018 10:30


Originally Posted by sonicbum (Post 10179864)
The MEL provisions also consider the worst case scenario of a subsequent inflight failure of another critical system and therefore protects You accordingly. Once the applicability of the MEL ceases it is up to You to cater for all the different scenarios that could happen and decide. Regardless of what the MEL says the final word is anyway always with the flight crew (ie the Captain) if a more restrictive interpretation of the MEL is required given the conditions of the day.

yes SONICBUM that is exactly why you should apply the MEL up until setting takeoff power = no normal captain or technician can fully understand the consequences of flying with a “NO DISPATCH” failure on todays complex aircraft.

So I ask again : are there examples on a European company who apply/uses the MEL up until setting takeoff power ?

PENKO 23rd Jun 2018 11:25


Originally Posted by jaja (Post 10179834)
No it is not clear when to apply the MEL or the Abnormal checklist, but it used to be clear (up to approx 15 years ago).

The MEL should be applied up until setting takeoff power if you have failures on startup/taxi, and when airborne you look into the Abnormal checklist. That is the way we used to do it.

Let me give an example why : on taxi out you have an ECAM warning, and this failure is a “NO DISPATCH” according to the MEL. Common sense would be not to continue the flight, but as it is company procedure in many places, it is up to captain to decide if it is OK to continue (after using “good airmanship etc”.

In todays complex aircraft it should not be up to the captain to decide that. The MEL should be used/applied up to setting takeoff power.

Please give examples on in which European companies is the MEL used/applied that way (up to setting takeoff power) ?





If you ask me what is whise, then yes, of course, the MEL is one of the things you consider in your scenario of ECAM during taxi. The MEL is also a wonderful companion with ECAM in flight if time permits, or reading FCOM in bed at home.

If you ask what are the rules, then the rules are very clear, see my quote in an earlier post.
If you disagree with this, then please explain why. I pointed out that EASA also has the provision regarding failures during taxi. This should answer your initial question.

As for your point that we need tailored on ground procedures for dealing with failures, well, that's exactly what you have in your MEL: once dispatched but before TO, complete the QRH/ECAM and consider the implications of the MEL, maintenance facilities etc and then decide to go or not. But you are not bound by the MEL at that stage.

jaja 23rd Jun 2018 12:18

yes PENKO, but the average flightcrew/technician can not “consider the implications of the MEL”

so if you as a flightcrew decide to continue the flight, after having a failure during taxi that is a “NO DISPATCH” according to the MEL, then indeed you are on “un known ground”.

Why not be professional, and consider the aircraft “not airworthy” if you have a “NO DISPATCH” fault during taxi ?

PENKO 23rd Jun 2018 12:33

That's a different discussion jaja. An interesting discussion for those quiet cruise portions on a long flight indeed, but still a different discussion.
Now we can produce a long list of failures and ask 'would you take off'. Or we can ask one simple question: why have the regulators chosen the moment of taxi as the start of a flight with respect to defect handling? Apparently they trust our professionalism.

Fair enough, no?

pineteam 23rd Jun 2018 12:46


Originally Posted by jaja (Post 10179933)
Why not be professional, and consider the aircraft “not airworthy” if you have a “NO DISPATCH” fault during taxi ?

Because a return to the gate can be extremely expensive if for instance the flight is cancelled. Being safe is good but you can’t be overly safe and competitive at the same time. Airlines main target is to make profit. It’s a business. We should not forget that.
How many times have you heard of a serious incident/accident after a crew decided to continue a flight after a « no dispatch failure » during taxi? Must be extremely rare otherwise I would expect that we apply the MEL the way you describe.



sonicbum 23rd Jun 2018 16:52


Originally Posted by Small cog (Post 10179979)
How can you apply requirements and restrictions of the MEL when (M) is required, without returning to the gate?

Well You can't that's why You need to balance risks, assess the situation and come up with a decision using all the available tools. If possible a phone/satcom/HF call to your maintenance team while at the holding point could give you valuable inputs to come up with your decision and if you're still stuck a call to your duty pilot (if there is one where your work) can help you out as he is going to speak on behalf of the company even though he's not going to decide for you but most likely give you "food for thoughts". Main thing when in a grey area is to get as many inputs as possible before jumping to a decision and being told "oh yeah but you could have talked to etc..". In the end no one decides for You but if the feeling You get from all around is that it smells "dodgy" then the parking bay is where you are heading to.

hans brinker 23rd Jun 2018 17:57

https://cimg3.ibsrv.net/gimg/www.gmf...3f83d4121d.jpg

Clear I would hope...

PENKO 23rd Jun 2018 18:27

This is not EASA-based.
So to be clear, you would go back to the gate for say..a burnt turn off light?

PENKO 23rd Jun 2018 19:43


Originally Posted by Small cog (Post 10180217)


Nice idea, but I would suggest it would be a brave manager or engineer who would authorise departing without a tech log entry. If you having enough doubt to call them ...

Ever been told “it’s OK” and then asked of it in writing? I did once, and I got it (I didn’t agree with CP and engineering that I should do an engine run after a problem). Carried out the requested engine run ... very expensive bang followed. Play safe.

Just my 2 cents worth.

Why so paranoid? It's perfectly legal, no tech log entry necessary after you've dispatched. Any professional engineer will have no hesitation to advise you to go or not go, in writing, or on a recorded phone conversation.

I'm glad I work with sensible professionals who are not afraid to offer sensible advise or take sensible decisions. Also in writing when requested.

FlightDetent 23rd Jun 2018 20:44

The regulation is worded the way it is for a reason. By people who - unlike common line folks such as us here (both FD an MX) - actually do know the backgroud, understand the implications, and are expertly trained in writing legal documents.

jaja, have you considered if perhaps the strong discord between your convictions and the law could be due to lack of education on the side of the liveware unit? There are valid answers to your queries, yet until you pass through that door they could remain out of sight.


767 pilot 13th Jul 2018 17:45

Boeing 767 DDG quotation "Upon completion of any applicable procedures and prior to takeoff, the operator’s MEL should be consulted to determine if relief is available for continued operation with system faults displayed at the alert level (Warning, Caution, Advisory).", so Boeing's policy is: if after or during engine start and before TO there is an alert message: 1) do the respective non-normal checklist (NNC), 2) check the DDG or MEL to make decision. For me, it is still unclear what to do if on this stage and before ETOPS entry point there some issues related to ETOPS MEL ITEMS and which usually not considered for NON-ETOPS flights.


All times are GMT. The time now is 05:22.


Copyright © 2024 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.