MEL definition
Join Date: Apr 2003
Location: Europe
Posts: 3,039
Likes: 0
Received 0 Likes
on
0 Posts
This is what EASA states in its document 'Certification Specificationsand Guidance Material for Master Minimum Equipment List CS-MMEL':
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
‘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.
[...]
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.
You'd be surprised how many pilots don't grasp this simple fact
Join Date: Mar 2012
Location: Having a margarita on the beach
Posts: 2,419
Likes: 0
Received 0 Likes
on
0 Posts
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
Join Date: Jul 2006
Location: Somewhere over the rainbow
Posts: 946
Likes: 0
Received 0 Likes
on
0 Posts
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.).''
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.).''
Join Date: Dec 1998
Location: .
Posts: 2,994
Likes: 0
Received 0 Likes
on
0 Posts
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.
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.
Thread Starter
Join Date: Jun 2004
Location: EU
Posts: 114
Likes: 0
Received 0 Likes
on
0 Posts
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) ?
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) ?
Last edited by jaja; 23rd Jun 2018 at 09:58.
Join Date: Jul 2006
Location: Somewhere over the rainbow
Posts: 946
Likes: 0
Received 0 Likes
on
0 Posts
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.
Thread Starter
Join Date: Jun 2004
Location: EU
Posts: 114
Likes: 0
Received 0 Likes
on
0 Posts
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 !
Join Date: Jul 2006
Location: Somewhere over the rainbow
Posts: 946
Likes: 0
Received 0 Likes
on
0 Posts
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
Just speculating. I'm not sure why. xD
Join Date: Mar 2012
Location: Having a margarita on the beach
Posts: 2,419
Likes: 0
Received 0 Likes
on
0 Posts
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.
Thread Starter
Join Date: Jun 2004
Location: EU
Posts: 114
Likes: 0
Received 0 Likes
on
0 Posts
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.
So I ask again : are there examples on a European company who apply/uses the MEL up until setting takeoff power ?
Join Date: Apr 2003
Location: Europe
Posts: 3,039
Likes: 0
Received 0 Likes
on
0 Posts
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) ?
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 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.
Last edited by PENKO; 23rd Jun 2018 at 11:40.
Thread Starter
Join Date: Jun 2004
Location: EU
Posts: 114
Likes: 0
Received 0 Likes
on
0 Posts
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 ?
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 ?
Join Date: Apr 2003
Location: Europe
Posts: 3,039
Likes: 0
Received 0 Likes
on
0 Posts
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?
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?
Last edited by PENKO; 23rd Jun 2018 at 12:51.
Join Date: Jul 2006
Location: Somewhere over the rainbow
Posts: 946
Likes: 0
Received 0 Likes
on
0 Posts
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.
Join Date: Mar 2012
Location: Having a margarita on the beach
Posts: 2,419
Likes: 0
Received 0 Likes
on
0 Posts
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.
Join Date: Apr 2003
Location: Europe
Posts: 3,039
Likes: 0
Received 0 Likes
on
0 Posts
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.
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.
Only half a speed-brake
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.
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.
Join Date: Jan 2016
Location: Ukraine
Posts: 7
Likes: 0
Received 0 Likes
on
0 Posts
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.