PPRuNe Forums - View Single Post - Engine overheat
Thread: Engine overheat
View Single Post
Old 27th May 2017, 19:50
  #1 (permalink)  
k738
 
Join Date: Jan 2011
Location: N/A
Posts: 18
Likes: 0
Received 0 Likes on 0 Posts
Engine overheat

So, had a very interesting day, flying the B737.

During our takeoff roll, we aborted at around 60kts when we got master caution ELEC --> DRIVE, eng nr 2.

After troubleshooting and talking with our company, we were assigned a slot for departure, so we decided to shut down the engines, about 10 minutes after the aborted takeoff.

Slot improved shorty after, so we completed our checklists and were getting ready for a new startup. We started engine number 2 and it was a good start. Planning for single engine taxi, we were about to do the "one engine taxi checklist" when we noticed OVHT/DET on the master caution panel.
Looking down on the fire panel, the ENG 2 OVERHEAT was illuminated. We did the memory items. QRH refers you to go to the "engine fire" NNC since the overheat indication still was illuminated, but since we were on stand and already at idle thrust, we put the engine start lever to cutoff instead.

Talking with our company again, this day was just getting better and better.

The OVHT DET switch at ENG nr 2 was set at NORMAL. The FCOM says that "normally both loops have to sense an overheat condition while engines running" to cause the indication. After shutdown, we changed OVHT DET switch to loop A, and the indication disappeared. Switched it to B, the overheat indication illuminated(this was done a couple of minutes after shutdown). We did the fault and fire test, and there was no indication of any malfunction on any of the loops. The OVERHEAT indication disappeared about 10 minutes after engine shutdown(OVHT DET panel set at Normal).

We did another engine restart and shutdown without pax - also this time, we got the engine overheat indication, but only when selection loop B, unlike the first time, when the detection switch was set to Normal.
We concluded that loop B was fault, as engine indication was normal

Anyway, my point is that we got an engine overheat indication on loop B, despite the loop passing the fault and fire tests. Others had similar experiences?

Taking into account the aborted departure with the drive malfunction, this was a very special experience.

Best regards

Note: The APU were powering both AC busses at startup when we got the engine overheat indication.

Last edited by k738; 27th May 2017 at 20:18. Reason: additional info
k738 is offline