PPRuNe Forums

PPRuNe Forums (https://www.pprune.org/)
-   Tech Log (https://www.pprune.org/tech-log-15/)
-   -   Engine Seperation (https://www.pprune.org/tech-log/579795-engine-seperation.html)

Pin Head 1st Jun 2016 18:55

Engine Seperation
 
Hi

Bar no hydraulic fluid left, what other indications will you have of engine Seperation?

Learning experience today had lots of 0's and put it down as engine severe damage as all indications were there.

Thank you.

lomapaseo 1st Jun 2016 19:41

If this is a question about simulator training

then its a book answer

if its a real life question then the answer will vary with other factors

grounded27 1st Jun 2016 20:06

Screaming PAX?

Pin Head 1st Jun 2016 20:30

Book answer then please.

PDR1 1st Jun 2016 20:34

Letters from the engine's lawyer demanding vacant possession of the aircraft's hangar and 50% of its future revenue, plus another 10% for each of the three APUs...

PDR

RAT 5 1st Jun 2016 23:01

Type A/C please.

Pin Head 2nd Jun 2016 02:57

B737ng
Thank you

Intruder 2nd Jun 2016 03:50

Look out the window?

felixthecat 2nd Jun 2016 04:10

Isn't the memory item 'Engine Severe Damage and Separation' ? So its the same checklist anyway....
(Been a long time since I was on the 737 so could well be wrong)

msbbarratt 2nd Jun 2016 05:45

From SLF
 
As a matter of interest, is it the case that cabin crew observations do not play a formal role in the procedures pilots use to diagnose problems like this?

I mean, if one of them got on the phone and mentioned that an engine was missing, or that there was burning fuel on the ground underneath an obviously broken engine, presumably the pilots would take them seriously, no matter what the official procedure said...

In the absence of a view from the cockpit and video displays of the wing, a pair of trained eyes down the back of the aircraft could be a useful thing.

So have I touched on the answer to my question - training (and the cost of it)? But for basic things like fire or absence you don't really need much training.

I wouldn't be surprised if retro fitting a video system was also much more expensive than one might casually think. However for new designs it would surely be a piece of cake. Or are they so keen to carry over pilot type ratings that they are adding nothing new like this at all? That would be a pity...

RAT 5 2nd Jun 2016 07:49

I can only comment on what the sim shows; I am curious why your SFI/TRI's can't answer this.
Firstly: you could be flying freight or a ferry, so CA eyes down the back might be unavailable.
2ndly: Yes the same checklist, but I'd be very cautious about deploying LED's with a separated engine. If the runway did not require it I might configure for a non LED landing if there is no option to make a visual inspection of the LED's. It could be night time, or the windows (freight version) could be blanked. Vision from the flight deck is only the 2 outboard LED's.
3rdly: The '0's' in the engine gauges are not the primary indications. The N1% shows 0, but the ancillary gauges show 'blank'. That means the sensor connection is missing. It is also why I suggest to students that during their analysis of the engine instruments, said out loud, is to differentiate between "no oil pressure" & "blank oil pressure". They mean different things and to non-english speaking (primary language) pilots under stress the wrong understanding is possible.
In the FFS sim I used to demonstrate all the different engine failures in sequence to confirm understanding of the possibilities. I was amazed how many students had not seen a surge or separation during FBS phase.

Pin Head 2nd Jun 2016 17:39

Thanks.
Can you explain more about note 2 please?
I had all indications there just lots of 0's. I always thought that these would not be there at all in a Seperation. Hence why I called it severe damage.
Thank you

tdracer 2nd Jun 2016 18:52

FADEC supplied parameters would 'blank', while analog inputs would read "0" (note that your rotor speeds use the FADEC as the primary source, but have analog backup).
But a dead FADEC would also result in blank parameters.

RAT 5 2nd Jun 2016 20:03

Note 2. Ref: DC-10 Chicago: B747 Amsterdam. Both had engine separation problems and both, unbeknown, had LED damage. DC-10 had engine failure on takeoff and reduced speed to V2 and stalled the damaged wing. B747 deployed LED's for landing and stalled the damaged wing. No doubt there has been others, but little thinking outside the box can help.

lomapaseo 2nd Jun 2016 20:29


Note 2. Ref: DC-10 Chicago: B747 Amsterdam. Both had engine separation problems and both, unbeknown, had LED damage. DC-10 had engine failure on takeoff and reduced speed to V2 and stalled the damaged wing. B747 deployed LED's for landing and stalled the damaged wing. No doubt there has been others, but little thinking outside the box can help.
several early B737s with JT8D and B727s, and B707s. No wing damage (different aero forces on released engine) +Kalita B747

Engines that don't fail but just separate do different things to the aircraft whilst departing.

Side load departures in turbulence or spin may also vary.

Yet keeping the briefing simple and recallable in training serves a value so I wouldn't want to mess with that at this time.

Pin Head 2nd Jun 2016 21:16

So at 'Identify failure' how many of you check systems page as well as primary and secondary engine data?

Pin Head 2nd Jun 2016 22:28

So just to confirm physically no information missing?
I.e just black?
I think the 756 would do this on a seperation.

B737900er 3rd Jun 2016 18:41

If the indications all read zero I would expect at separation. if the N1 and N2 read zero and possible high EGT I would diagnose that as an Turbin Seizure so, Engine fire, severe damage, separation NNC.

Pin Head 3rd Jun 2016 22:47

Thanks.
But do any indications just dissapear? So black background only,

tdracer 4th Jun 2016 04:22


Originally Posted by Pin Head (Post 9398206)
Thanks.
But do any indications just dissapear? So black background only,


I don't have first hand knowledge of the 737, but standard Boeing design practice is to blank displays if the digital data is lost or invalid. With analog signals, you can't tell the difference between lost and valid but zero, so they will still display zero.
Next time you do an engine start, before you do anything look at the engine displays - digital inputs only from the FADEC will be blank until the FADEC is powered, anything that is analog (or has an analog backup - rotor speeds) will read zero. That's pretty much what you'll see if the engine decides to go it's own way :E


All times are GMT. The time now is 23:18.


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