CFM Leap ecam
Thread Starter
CFM Leap ecam
I have been flying the Dyson powered A321 recently and it often produces an ecam caution Engine x Minor Fault. The fcom is not exactly forthcoming as to what the fault is, any ideas?
Join Date: Feb 2013
Location: 60 north
Age: 59
Posts: 17
Likes: 0
Received 0 Likes
on
0 Posts
On a serious note...
I have forgotten my A320 stuff, but still remember the new Do328 Jet with PWC engines churning out Fadec Minor ( Blue) Info only
Fadec Major ( Amber) action dependent on other indications and ECAM
And Fadec Fault= Shut it Down ( anything can happen ie overspeed , idle or fail.)
Mind you this was in 2000 and I would hope Airbus is a bit more advanced then my respected Dornier friends.
Was it blue with no ECAM action needed and nothing in the QRH, If so a maintenance distraction.
A heads up that there might be something more coming ,,
Sorry, Now I am just making things up.
I have forgotten my A320 stuff, but still remember the new Do328 Jet with PWC engines churning out Fadec Minor ( Blue) Info only
Fadec Major ( Amber) action dependent on other indications and ECAM
And Fadec Fault= Shut it Down ( anything can happen ie overspeed , idle or fail.)
Mind you this was in 2000 and I would hope Airbus is a bit more advanced then my respected Dornier friends.
Was it blue with no ECAM action needed and nothing in the QRH, If so a maintenance distraction.
A heads up that there might be something more coming ,,
Sorry, Now I am just making things up.
Thread Starter
It usually appears on taxi -in. This is with the CFM Leap engine on an aircraft only a few months old.
This alert triggers when a minor engine failure is detected.
This alert triggers when a minor engine failure is detected.
Most modern FADEC systems make use of something called "Time Limited Dispatch" or TLD. Basically, TLD allows dispatch with loss of redundancy faults that don't directly affect engine operation for some specified time before corrective action needs to be taken (anywhere from a few days to 2,000 flight hours depending on the engine and the nature of the fault).
To determine the fault that is causing the message you'd need to check the maintenance message on whatever Airbus calls their maintenance computer.
However, given you're talking a very new installation (the Leap) it could well be a nuisance message - maintenance would have some notification that if they do some check and it's OK, they can ignore message xyz until it gets fixed in the next FADEC s/w update.
To determine the fault that is causing the message you'd need to check the maintenance message on whatever Airbus calls their maintenance computer.
However, given you're talking a very new installation (the Leap) it could well be a nuisance message - maintenance would have some notification that if they do some check and it's OK, they can ignore message xyz until it gets fixed in the next FADEC s/w update.
Join Date: Feb 2013
Location: 60 north
Age: 59
Posts: 17
Likes: 0
Received 0 Likes
on
0 Posts
tdracer
So how is this presented on the new 737 Max as it has no fancy ECAM but good old 6 packs and a fat QRH.
Will it be hidden from us or come up on lover DU .
We are getting them next year so I am super exited!!!
So how is this presented on the new 737 Max as it has no fancy ECAM but good old 6 packs and a fat QRH.
Will it be hidden from us or come up on lover DU .
We are getting them next year so I am super exited!!!
Overall, GE/CFM uses two classes of TLD faults - Short term and Long term (plus of course 'No Dispatch'). Short term will have some sort of flight deck indication and are handled via the MMEL (typically 10 day dispatch allowed via the MMEL). On EICAS aircraft, it'll generate a Status message - again not sure how that's handled on the 737.
Long term dispatch (which is what I assume the OP is describing) don't require a flight deck indication - you need to go look for them in the maintenance computer at some interval (between 500 and 2000 hours, depending on the engine). On the newer EICAS installations the presence of a long term fault will be indicated on one of the Engine Performance maintenance pages.
Join Date: Aug 2000
Location: U.K.
Posts: 42
Likes: 0
Received 0 Likes
on
0 Posts
Faults not affecting despatch are not shown to the crew, those that do switch on the maint light (replaces pseu):
"You use the LATCHED MESSAGE ERASE page to do these
processes:
- Erase latched status messages
- View and erase scheduled maintenance task (SMT) messages.
Fault Categories
There are three fault categories:
- No dispatch
- Category 1 (C1)
- Category 2 (C2).
No dispatch and C1 engine faults have related status messages or
flight deck indications (MAINT light). C2 faults are scheduled
maintenance task (SMT) messages. C2 faults do not cause status
messages.
Latched Status Messages
The top part of the display shows status messages that latch in the
DPC. After you repair the system, use the ERASE key to remove the
message from memory. After you erase the latched message, it does
not show on this page or the status page. Select ERASE ALL to erase
all latched status messages. You cannot erase a latched message for
an active fault.
Scheduled Maintenance Task Messages
The bottom part of the display shows SMT messages. After you repair
the system, use the ERASE key to remove the message from memory.
SMTs show on the lower part of the latched message page. SMTs do
not cause the MAINT light to come on. You can operate the airplane
with SMT messages for specified intervals. You must check SMT
messages at intervals set by your airline.
737-7/8/9 Training Manual
MDS -- MAS - MAINT CTRL PGS - ERASEABLE STATUS/SCHEDULED MAINTENANCE TASK MESSAGES
17-Oct-2016 31-65-00
- 230"
Last edited by WenWe; 28th Oct 2018 at 10:21. Reason: Sp
Join Date: May 2009
Location: sfo
Age: 70
Posts: 309
Likes: 0
Received 0 Likes
on
0 Posts
tubby
From the maintenance side, we have seen this fault occasionally, usually it goes away after a couple minutes. The thinking is that simultaneous engine shutdown at the gate may trigger it, but we are getting no info from CFM or AB as to a fix. If the message is still there when I get up to the flight deck, a FADEC ground test for both channels will clear it.
Only once have I seen it for both engines. A320-NEO type.
Only once have I seen it for both engines. A320-NEO type.
Thread Starter
Thanks for the reply Sb sfo. I have seen it once and it was just after landing with both running. It remained after shutdown but disappeared when the fadecs were no longer powered.
The other one we see a lot are mech adv reports about low oip, but this is usually triggered when the engine is running down.
The other one we see a lot are mech adv reports about low oip, but this is usually triggered when the engine is running down.
