PDA

View Full Version : Luckily the dead engine wasn't dead after all.


sheppey
23rd Jun 2017, 14:27
From Subject Received Size Categories
Curt Lewis & Associates, LLC Flight Safety Information [June 23, 2017] [No. 125] Fri 11:27 PM 299 KB

Pilots switch off healthy engine after bird-hit
• A GoAir flight suffered a bird-hit during takeoff at Delhi's IGI airport
• Pilots allegedly turned off the healthy engine which was a wrong decision
• Directorate General of Civil Aviation has grounded both pilots, said a source

NEW DELHI: Over 160 people on a GoAir flight from Delhi to Mumbai on Wednesday had a narrow escape when the aircraft suffered a bird-hit during takeoff at IGI Airport. One of the Airbus A-320's engines ingested the bird during takeoff roll, but instead of switching this engine off as per procedure, the pilots allegedly turned off the healthy one.
"The pilots soon realised their mistake and switched on the healthy engine. The aircraft reached an altitude of about 2,000 feet before it returned to land safely in Delhi. It was a dangerous situation and the Directorate General of Civil Aviation has grounded both pilots. Luckily, the other engine had not failed after the bird-hit and was still powering the plane even after the pilots reportedly switched off the 'healthy' engine, which had not suffered the bird-hit. Otherwise, it would have been bad," said a source.

A GoAir spokesman said: "GoAir flight G8 338 from New Delhi to Mumbai, carrying 155 passengers, suffered a bird-hit on Wednesday. Following standard operating procedure, the aircraft returned to Delhi as a precautionary measure at 11.28am. All passengers were transferred to another aircraft, which was airborne at 1.04pm. The matter is under investigation."

The airline did not comment on the allegedly wrong switching-off of the engine and grounding of the pilots.

Senior commanders said switching off the wrong engine could lead to a disaster. If an engine is damaged for any reason like a bird-hit and the pilots mistakenly switch off the healthy engine too, the aircraft has no working engine.
In February 2015, a Taiwanese airliner (which ceased operations last year) smashed into a highway bridge in Taiwan and then crashed into a river, killing 43 of its 58 passengers, after the pilot turned off the wrong engine.

Pilots switch off healthy engine after bird-hit | Delhi News - Times of India (http://timesofindia.indiatimes.com/city/delhi/pilots-switch-off-healthy-engine-after-bird-hit/articleshow/59276868.cms)

EDLB
23rd Jun 2017, 16:15
Not the first and not the last time. Hopefully they switched on the APU. Sully found out, that this is not a bad idea in any case. On a small prop plane the training to verify the bad engine after TO is rushed, because it creates a lot of drag. On a jet that should be much more relaxed since the bad engine does not create as much drag. As long as there is positive rate of climb there should be no rush and a thorough check from both pilots. So some of the CRM and checklist procedure broke down. Sitting in an armchair it is so easy...

er340790
23rd Jun 2017, 16:53
For the next generation of pilots, not a bad time to re-read the British Midland M1 'Kegworth' crash.

https://www.icao.int/safety/airnavigation/OPS/CabinSafety/Cabin%20Safety%20Library/Accidents%20in%20Doc%2010062/British%20Midland%20Airways%2092.pdf

dixi188
23rd Jun 2017, 17:00
If an engine is not on fire and not shaking itself to pieces then why shut it down at all?
If it's giving elec. and hyd. power and can be kept below vibration rpm, keep it running.

gonebutnotforgotten
23rd Jun 2017, 21:20
One reason (THE reason?) for making the first action of a shutdown procedure 'Thrust Lever - Identify - Close' is that it is the one that is quickly reversible. It's a very good time to consider whether the reaction and outcome is what you would expect. I always thought it worth emphasising in the pre T/O brief.

rottenray
24th Jun 2017, 00:11
I was thinking this same thing, sort of, from a PAX point of view.

Kegworth was almost understandable -- 737-300 vs. -400, with the change in ducting and the poor gauges on the -300. Trust the smoke rather than the dials.

Glad everything worked out, it's a testament to the flexibility of twins.

lomapaseo
24th Jun 2017, 00:49
I wouldn't spend too much time judging what the pilots did based on a news story likely transcribed into English.

For instance I really don't know exactly where they were in the flight regime when they ingested a bird and got symptoms of some sort. Seeing as there was a report that it later was producing power they may have had no more symptoms than a bang followed by a buzz sound.

At the point that they alleged grabbed the wrong throttle they may have been free of symptoms except for the buzz sound. If all they did was pull back the throttle on the unaffected engine to idle or greater, the buzz sound on the damaged engine would continue and so would its thrust. At that point they may have simply advanced the undamaged engines thrust and made an airturnback having sorted out the correct response.

WingNut60
24th Jun 2017, 02:50
......the pilots allegedly turned off the healthy one.
"The pilots soon realised their mistake and switched on the healthy engine.

You should probably cut the crew some slack until you know what the terms above really mean.

No Fly Zone
24th Jun 2017, 06:11
It has happened before - and it will happen again. Other then extreme caution and verification by both pilots, what else can be done? Verify = and verify again/ This should NOT Happen, but it will. Close call!!

dised101
25th Jun 2017, 00:59
Really.

It takes some effort to shut down the wrong engine on an A320 when the ECAM literally tells you what to do!

Given it hadn't actually failed I can only imagine they didn't get an ECAM caution/warning and instead were working off the vibration indicator or something on the EWD and in the heat of the moment failed to agree and confirm the right engine.

I agree. But there are some circumstances where the Airbus ECAM logic will lead you down the wrong path. It is still advisable to take your time and analyze the entire scenario before you start listening to FIFI.

ekw
15th Jul 2017, 02:32
Probably a case of ASS (arrogant skipper syndrome) with an absence of CRM.

Old Fella
15th Jul 2017, 09:58
I was thinking this same thing, sort of, from a PAX point of view.

Kegworth was almost understandable -- 737-300 vs. -400, with the change in ducting and the poor gauges on the -300. Trust the smoke rather than the dials.

Glad everything worked out, it's a testament to the flexibility of twins.

This is a classic example of where a little knowledge is very dangerous. If "rottenray" really believes that the Kegworth was almost understandable, based on the flawed understanding of the pneumatic system by the pilots, then I think he is sadly mistaken. Kegworth need not have happened. Time taken to properly identify the defective engine, based on the indications presented, would/should have prevented the Kegworth accident.

DaveReidUK
15th Jul 2017, 10:42
Kegworth was almost understandable

Kegworth need not have happened

Those two statements are not mutually exclusive.

FlightDetent
15th Jul 2017, 12:32
Picked an OEI technique some time ago in the SIM from a colleague. One was quite ashamed of not being trained to do so earlier, nor devising it on my own.

2577

a) As the trust-lever is moved to idle, as a part of the shut-down drill, focus the eyes on the TL position indicator (white doughnut on the picture above). Observe its movement on the correct engine.
b) move the TL slowly, watching with your other eye the good engine's N1 - that they do NOT move, with sharp ears and sensitive pants towards any undesired change.

It is easily done with a two-phased movement: retard to 2/3rds, check the gauges and gut, if all ok then close the TL all the way.

c) do not let go of the retarded TL straight away, pause for one deep breath with the eyes on the instruments.

Rush is the ultimate killer. Tenerife, Spanair, Taipei, sadly many others.

threep
5th Feb 2019, 12:44
From Flight Global website 5th February 2019

"Once airborne the first officer “misinterpreted” the N1 speed reading of the right-hand engine as a vibration of the left-hand engine, the inquiry states.
The first officer called out a beyond-limit vibration of the unaffected left-hand engine and, as a result of the incorrect assessment, the left-hand engine was incorrectly shut down around 30s after rotation.
Thrust of the problematic right-hand engine was increased and the aircraft was left to climb on this engine alone for over 3min.
The first officer, says the inquiry, “repeatedly” advised the captain, incorrectly, that the left-hand engine was experiencing out-of-limit vibration."

I would post the full link but I'm more of a lurker and haven't posted enough times yet to be allowed to post a link.

I know its a pressure situation, but identifying the wrong engine for shutdown when the instrumentation clearly identified the correct engine is a bad error.
How can high vibration indications be made clearer to avoid mis-reading which engine has suffered damage? I'm not familiar with the cockpit display in the 737, presumable its graphical rather than spell out "HIGH VIBS LEFT" ?

pattern_is_full
5th Feb 2019, 16:06
I'm not familiar with the cockpit display in the 737, presumable its graphical rather than spell out "HIGH VIBS LEFT" ?

The VIB display (according to picture at Aviation Herald: Incident: GoAir A320 at Delhi on Jun 21st 2017, bird strike, wrong engine shut down and restarted (http://avherald.com/h?article=4aaadd7a&opt=0)) looks like

0.0 — VIB N1 — 0.0
0.0 — ......N2 — 0.0

... and it did occur to me that in a rush, or lacking experience with a VIB indication (or one's morning coffee), the brain could read

0.0 — VIB N1 — 3.6

as "(Engine) N(umber) 1, Vibration 3.6"

Not an excuse, possibly a reason.

zahnpastaesser
5th Feb 2019, 16:22
The VIB display (according to picture at Aviation Herald:) looks like

0.0 — VIB N1 — 0.0
0.0 — ......N2 — 0.0

... and it did occur to me that in a rush, or lacking experience with a VIB indication (or one's morning coffee), the brain could read

0.0 — VIB N1 — 3.6

as "(Engine) N(umber) 1, Vibration 3.6"

Not an excuse, possibly a reason.


My thought exactly! And the most propable scenario in my opinion.

They could redesign it to read NL (low) and NH (high) instead. But then again you´ll have folks reading N-"left" when under stress...

Kiltrash
5th Feb 2019, 17:50
From what I read the Captain PF and 20000 hrs and the First Officer PM less than 1000 made a mistake and got all safely on the ground.... well done
The worry for me is that the flight crew then took the replacement aircraft and landed no more than 4 hrs behind schedule
WTF no one grounded them immediately while investigating what happened

FE Hoppy
5th Feb 2019, 18:05
Why the rush to shut down engines. If it's vibrating it's vibrating. Wait until everything else is sorted then both of you take your time to identify the problem. Wait long enough and it will resolve itself!

Consol
5th Feb 2019, 18:47
The incident report goes on to tell that the crew managed to alpha floor the aircraft during the restart phase. Not a great day's work by any measure.

lomapaseo
5th Feb 2019, 18:49
Well you can usually go partway just by retarding throttles and observing the effects on each engine at a time. The only rush point would be if EGT was overlimits and did not respond to a throttle reduction.

But like every new report on this site, I wasn't there so I have no need to critizize

LeadSled
5th Feb 2019, 23:33
This is a classic example of where a little knowledge is very dangerous. If "rottenray" really believes that the Kegworth was almost understandable, based on the flawed understanding of the pneumatic system by the pilots, then I think he is sadly mistaken. Kegworth need not have happened. Time taken to properly identify the defective engine, based on the indications presented, would/should have prevented the Kegworth accident.

Spot on!! A case of a little knowledge is dangerous.
Have I missed the post (with all these wonderful ways of determining a failed engine) of "Dead foot, dead engine" ??
Tootle pip!!
PS: I have read the Kegworth report, (and I used to work for BMA) and I do know that other actions disguised/didn't help the proper identification of the failed engine.

12A
6th Feb 2019, 06:03
This is a classic example of where a little knowledge is very dangerous. If "rottenray" really believes that the Kegworth was almost understandable, based on the flawed understanding of the pneumatic system by the pilots, then I think he is sadly mistaken. Kegworth need not have happened. Time taken to properly identify the defective engine, based on the indications presented, would/should have prevented the Kegworth accident.

Kegworth was down to many factors supporting the pilot's bias, not least, inadequate training by their employer.

Volume
6th Feb 2019, 08:36
For the next generation of pilots
For the next generation of rules and aircraft it may be wort rethinking the auto-rudder-trim vs. dead foot - dead engine philosophy...
Nothing is as clear to understand as tactile indications.
Maybe some remaining mis-trim (low enough to prevent loss of control, high enough to be clearly felt by the pilot) or artificial feel might be the way to go ?

Or having a "throtlle shaker" which makes the power lever vibrate with the vibration indication? (Healthy engine lever feels fine, failed engine lever vibrates)

There is a lot aircraft designers could do to support pilots, which due to their human nature do make mistakes, even more if you automate many items and take the pilot out of the loop.

Check Airman
6th Feb 2019, 12:49
For the next generation of rules and aircraft it may be wort rethinking the auto-rudder-trim vs. dead foot - dead engine philosophy...
Nothing is as clear to understand as tactile indications.
Maybe some remaining mis-trim (low enough to prevent loss of control, high enough to be clearly felt by the pilot) or artificial feel might be the way to go ?

Or having a "throtlle shaker" which makes the power lever vibrate with the vibration indication? (Healthy engine lever feels fine, failed engine lever vibrates)

There is a lot aircraft designers could do to support pilots, which due to their human nature do make mistakes, even more if you automate many items and take the pilot out of the loop.

I like your idea, but this manufacturer isn't big on tactile feedback.

I'm just puzzled why they set the operating engine to idle in the attempt to restart the good engine.

threep
6th Feb 2019, 14:34
Or having a "throtlle shaker" which makes the power lever vibrate with the vibration indication? (Healthy engine lever feels fine, failed engine lever vibrates)
.

I like the sound of a throttle shaker to indicate which engine has high vibs. Mobile phones have a vibrate mode, so there are small and robust mechanisms out there. It doesn't sound like the biggest job in the world to incorporate something similar into a throttle lever.

Sailvi767
6th Feb 2019, 14:56
When things go south, wind the clock! Not to mention at every airline I know moving a critical switch requires both pilots confirm the action.

lomapaseo
6th Feb 2019, 16:17
When things go south, wind the clock! Not to mention at every airline I know moving a critical switch requires both pilots confirm the action.


That didn't even come into the picture in the Sim where one engine caught fire on takeoff and after firing both bottles the PNF ran the checklist and at the end the checklist called to switch off the affected engine so the PNF reached for the switch and as he did so the PF let out a yell but it was too late and a glider we became at 2k feet. It seems that the challenge action at the front of a drill works OK by rote but when the action.is called for a minute or two later it didn't have a challenge

Council Van
6th Feb 2019, 17:04
From aviation herald

"was in the takeoff roll at about 115 KIAS out of Delhi's runway 09 when a bird struck the right hand engine (CFM56) causing vibrations and abnormal sounds. The crew continued takeoff"

115 KIAS and they continued, is that not way below V1 with 158 pax on board?

Right Way Up
6th Feb 2019, 17:13
I like the sound of a throttle shaker to indicate which engine has high vibs

Not what I want when I have a double birdstrike and I am trying to fly a crippled aircraft round the circuit!

I think we would be better to ensure we put people into the flight deck with better non-technical skills and who can read a basic instrument display. Compared to some of the old steam driven engine instrument displays the Airbus is a doddle.

DaveReidUK
6th Feb 2019, 19:04
115 KIAS and they continued, is that not way below V1 with 158 pax on board?

From DGAC: Final Investigation Report on Air Turn Back Incident due to Bird Strike to Go Airlines (India) Ltd Airbus A320-214 Aircraft VT-GOS On 21/06/2017 at Delhi (http://www.dgca.nic.in/accident/reports/incident/VT-GOS.pdf):

During take-off roll on Runway 09 at around 115 knots IAS, aircraft encountered bird strike on Engine # 2. Both crew noticed abnormal sound and vibrations but PIC decided to continue for take-off probably wanting to investigate the problem after getting airborne.

Nil by mouth
6th Feb 2019, 19:37
I like the sound of a throttle shaker to indicate which engine has high vibs. Mobile phones have a vibrate mode, so there are small and robust mechanisms out there. It doesn't sound like the biggest job in the world to incorporate something similar into a throttle lever.

Difficult maybe with just two throttle levers when there is an engine vibration and a lot else going on.
Four throttle levers.... Eeny, meeny, miny, moe that one's vibrating let it go. Not viable!

EcamSurprise
6th Feb 2019, 19:48
This hasn't been mentioned. No excuse but also shows this wasn't a beautiful smooth day like we often practice in the sim..
As per the occurrence report, the weather, after take-off, was very turbulent and the autopilot was not holding. Autopilot was disengaged at 05:41:50 hrs and several times from 05:45:43 hrs to 05:46:44 hrs.

physicus
6th Feb 2019, 23:17
A terrible display of poor airmanship. Especially the alpha floor part. Lucky they were in a bus forcing alpha floor protection on them, kept them from becoming another statistic. It is astounding who all is issued with a license to be up front these days. Training standards?

noske
7th Feb 2019, 08:43
Or having a "throtlle shaker" which makes the power lever vibrate with the vibration indication? (Healthy engine lever feels fine, failed engine lever vibrates)
Good idea. But not a shaker, just put red/amber rings on the edge of each throttle handle that can light up as a master warning/caution for the corresponding engine.

Airbus tried hard to do the right thing, putting all the indications for the left engine in the left column and those for the right engine in the right column. Nevertheless the FO got confused, and page 37 in the report (http://dgca.gov.in/accident/reports/incident/VT-GOS.pdf) is a good illustration of what he thought he saw and why.

I'm surprised that among the recommendations in the report there is none for Airbus to improve that part of the engine display. One could easily give the text column a better symmetry by putting the "VIB" above the N1/N2 rather than next to it. And, like zahnpastaesser said, maybe the terms N1/N2 should better be avoided in this context. LP/HP or FAN/CORE would be obvious alternatives.

Shackeng
8th Feb 2019, 18:31
I am still surprised that, under normal conditions, but particularly after suffering an engine failure, there is no operating engine(s) proving check, at a safe height above the ground, just as you would check your response to flight controls had any control malfunction occurred. While this would not have helped in this case, it certainly would in others, perhaps Kegworth, or the BA777 at LHR. It may be too late if you leave it until approach checks. Or perhaps there is such a check nowadays?

DaveReidUK
8th Feb 2019, 19:26
While this would not have helped in this case, it certainly would in others, perhaps Kegworth, or the BA777 at LHR.

I don't think (in)ability to identify a failed engine was a factor in the BA38 accident.

smala01
8th Feb 2019, 20:19
Airbus tried hard to do the right thing, putting all the indications for the left engine in the left column and those for the right engine in the right column. Nevertheless the FO got confused, and page 37 in the report (http://dgca.gov.in/accident/reports/incident/VT-GOS.pdf) is a good illustration of what he thought he saw and why.

I'm surprised that among the recommendations in the report there is none for Airbus to improve that part of the engine display. One could easily give the text column a better symmetry by putting the "VIB" above the N1/N2 rather than next to it. And, like zahnpastaesser said, maybe the terms N1/N2 should better be avoided in this context. LP/HP or FAN/CORE would be obvious alternatives.

Of course when seeing the display it makes "sense" why the FO confused this in times of high stress. Its a terrible design. Speaking generally - I have noticed the smartphone generation coming through in many industries have a default expectation of visual intuition... software displays today are designed in a specific and logical way, placing a legacy or non-standard display to younger generation reaps confusion in unpredictable ways

The bus gauge is awfully designed. However, when you fly the thing day in and day out there is an expectation you understand it!

Right Way Up
8th Feb 2019, 22:20
Nope it is not an awful design, but someone found a way to misunderstand it. Many, many, many pilots don’t have a problem with the Airbus instrument design but if you keep putting the lowest common denominators into the flight deck you will find someone who does.

Shackeng
9th Feb 2019, 08:54
I don't think (in)ability to identify a failed engine was a factor in the BA38 accident.

True, but my point was that in all conditions, failure or not, proving engines with height beneath before approach makes sense to me.

A Squared
9th Feb 2019, 16:43
I don't think (in)ability to identify a failed engine was a factor in the BA38 accident.

LOL
"Hey, I think both engines have flamed out"

"IDENTIFY"

" Both engines"

*VERIFY"

(pulls both throttles back to flight idle) "Yep, it's both of them"

tdracer
9th Feb 2019, 23:14
Sorry to be anal about this, but the BA38 engines didn't "fail" - they were both running above idle and producing thrust up to the point when they hit the ground. However the ice restriction in the fuel/oil heat exchanger meant that when they throttled up, the engines couldn't respond because the ice restriction wouldn't permit increased fuel flow.

Shackeng
10th Feb 2019, 09:12
Sorry to be anal about this, but the BA38 engines didn't "fail" - they were both running above idle and producing thrust up to the point when they hit the ground. However the ice restriction in the fuel/oil heat exchanger meant that when they throttled up, the engines couldn't respond because the ice restriction wouldn't permit increased fuel flow.

Precisely why I suggest 'proving' engines while still at a safe height before the approach, under all conditions, after failure or not, is a sound idea. Of course this normally happens at busy airports anyway, but not always, and it may be very satisfying for a pilot to arrange their approach and landing such that the first application of power required after TOD is at the flare.

RVF750
10th Feb 2019, 09:33
Precisely why I suggest 'proving' engines while still at a safe height before the approach, under all conditions, after failure or not, is a sound idea. Of course this normally happens at busy airports anyway, but not always, and it may be very satisfying for a pilot to arrange their approach and landing such that the first application of power required after TOD is at the flare.
Nice. If the first application is at the flare, that's a bit irrelevant, as that's where you normally close the levers. I get what you're after though. The modern trend for CDAs is driven by noise around airports and other fuel driven causes. It's slick, but in reality, power is at about 42-60% for most of the final approach, certainly on CFM types.

It really is a bad day out if it happens, and cool headed judgement, calm demeanour and logic are key to successful outcomes in many cases. Like nearly everyone else here, I just hope I don't get tested on this for real. A friend recently did and passed with honours.

Shackeng
10th Feb 2019, 09:38
Your not familiar with normal ops into an airport or stabilised approach requirements then?


Not for some time, but while flying commercially for 20 odd years, there were occasions when what I described occurred into remote airfields. Call me an old granny if you like.https://www.pprune.org/images/infopop/icons/icon7.gif

climb350
31st Aug 2019, 03:51
That was an Exapt, traveling as passenger that saved the day and not the crew of that flight.
Stand by for more detail as truth is surfacing.

climb350
31st Aug 2019, 04:09
Dave,

There are a lot missing from this report.
It was an Expat traveling as a passenger that see aircraft has lost its aerodynamic and falling from sky!
He has written 4 to 5 pages of report from the time that he has gone to the cockpit and "saved the day".
stand by for more detail of his reports and other issues that this company management taking this company down the tube.

ironbutt57
31st Aug 2019, 04:15
That was an Exapt, traveling as passenger that saved the day and not the crew of that flight.
Stand by for more detail as truth is surfacing.


how did a dyslexic EXPAT save the day...please tell

climb350
31st Aug 2019, 04:16
Sorry to be anal about this, but the BA38 engines didn't "fail" - they were both running above idle and producing thrust up to the point when they hit the ground. However the ice restriction in the fuel/oil heat exchanger meant that when they throttled up, the engines couldn't respond because the ice restriction wouldn't permit increased fuel flow.
tdracer,
On GoAir Flight 338 DEL to BOM with VT-GOS.
There is a lot missing from the truth.
That was an Expat that was traveling as a passenger in that flight that saved the day.
The truth is hidden but it is surfacing shortly. LOL
There are so much info missing that you would say WOW.

climb350
31st Aug 2019, 04:57
I like your idea, but this manufacturer isn't big on tactile feedback.

I'm just puzzled why they set the operating engine to idle in the attempt to restart the good engine.
Check Airman,
Keep digging for truth and eventually you will get it in this case.
There are more truth to this incident that would of be defiant was accident with lost of one aircraft and 164 sole which turned around by an Expat who was a passenger in that flight and "saved the day".
Note, Crew did two attempt to restart the Healthy Eng Number 1 Eng) but unsuccessful.
It was the expat that restart the Eng number one(Healthy Eng) then the captain of the flight G8-338 requested and ask Expat " Okay I want to shut down number Two Eng now"?
Expat by grading the center thrust lever and after pushing Captains hand away, advice him that "The only time he is going to allow him to shut down any Eng is on the Ground after parking brake set".

AviatorDave
31st Aug 2019, 11:12
If an engine is not on fire and not shaking itself to pieces then why shut it down at all?
If it's giving elec. and hyd. power and can be kept below vibration rpm, keep it running.

And if the so treated engine decides to go really bust after a while (after all, there was some damage to the engine in the first place), you may end up in a much worse situation than if you had shut it down right away.

lomapaseo
31st Aug 2019, 14:02
And if the so treated engine decides to go really bust after a while (after all, there was some damage to the engine in the first place), you may end up in a much worse situation than if you had shut it down right away.



There is quite a bit of historical experience to argue against this. Nobody is telling you what to do other than your operating manuals. But given that there is no nacelle fire warning bells I would advise you to take your time about turning off the the fuel to an engine. Sure pull it back to idle and then monitor the gages if you want. There are lots of in-service test points that say the worst you can do is melt the turbine blades and scrap out a compressor with no significant threat to continued safe flight.on the remaining engines

Fursty Ferret
31st Aug 2019, 14:31
Picked an OEI technique some time ago in the SIM from a colleague. One was quite ashamed of not being trained to do so earlier, nor devising it on my own.

Rush is the ultimate killer. Tenerife, Spanair, Taipei, sadly many others.

Completely agree and I do the same thing.

Drives me nuts in the sim when my partner slams the thrust lever for the "failed" engine closed. Even worse on Boeing types where PNF moves thrust levers and the manufacturer insists on dealing with serious engine malfunctions from memory.

Herod
31st Aug 2019, 17:44
Just to clear my own mind. The incident happened at 115 kts, and the FO asked whether the Capt wanted to reject when the IAS was 129 kts. V1 was 146 kts, ASDA is 2813m. The Capt didn't reject because he wasn't certain he could stop in the remaining runway?

dontgive2FACs
1st Sep 2019, 11:07
Sorry for slight drift here but I’m astounded by the number of incidents of non-normal situations ending up in Aloha Floor on the Bus.

Airbus family FBW logic is great technology but it demonstrates the less than optimal use of automation/task fixation in these events.

There-but by the grace of god do I....

vilas
1st Sep 2019, 11:48
This incident is very poor example of flying. The Capt had 12000 hrs on type. Thirty knots before V1 they had bird hit on the right engine. The rookie copilot suggested reject which the Capt decided to investigate in the air. The engine was vibrating badly. The No2 engine vibration monitor was showing excessive reading of N1,which the copilot read as NO1 engine. And the Capt of total 20000hrs didn't bother to check and shut down No.1. During restart at 2000ft thanks to Airbus they got alpha floor in Boeing they would be dead. Managed to restart asked for immediate Landing without much preparation. When vectored made a meal of it had to goround and landed safely if you can call that second time around. Some guardian angel who's duty time was not over must have taken mercy.

hans brinker
1st Sep 2019, 17:22
Just to clear my own mind. The incident happened at 115 kts, and the FO asked whether the Capt wanted to reject when the IAS was 129 kts. V1 was 146 kts, ASDA is 2813m. The Capt didn't reject because he wasn't certain he could stop in the remaining runway?

Yes to all of the above. It should clear your mind, but not put it at ease.

ManaAdaSystem
1st Sep 2019, 19:47
Even worse on Boeing types where PNF moves thrust levers and the manufacturer insists on dealing with serious engine malfunctions from memory.

Boeing SOP has the PF move the thrust lever after confirmation from PNF.

climb350
2nd Sep 2019, 01:07
The incident report goes on to tell that the crew managed to alpha floor the aircraft during the restart phase. Not a great day's work by any measure.
Consol,

It was the Expat, who saved the day and not the crew of that flight.
Expat was as a passenger.
The crew of that flight fail to restart the Eng number one after two attempt.
It was the Expat who came in, from that point full power the Eng number 2 and restart the Eng number one,...…….
it will more news will surface as you dig more to the incident.
The report is hidden a lot.
Dig and you will get to truth,
Keep looking into it and you will be surprise !!!

climb350
2nd Sep 2019, 01:11
Boeing SOP has the PF move the thrust lever after confirmation from PNF.
ManaAdaSystem,

The Crew of this flight was so behind, so behind and lost in the cockpit to what is going on.
It was the Expat that has gone in and saved the day.
Keep digging and try to question of this incident.
They are not telling the truth.

climb350
2nd Sep 2019, 01:34
This incident is very poor example of flying. The Capt had 12000 hrs on type. Thirty knots before V1 they had bird hit on the right engine. The rookie copilot suggested reject which the Capt decided to investigate in the air. The engine was vibrating badly. The No2 engine vibration monitor was showing excessive reading of N1,which the copilot read as NO1 engine. And the Capt of total 20000hrs didn't bother to check and shut down No.1. During restart at 2000ft thanks to Airbus they got alpha floor in Boeing they would be dead. Managed to restart asked for immediate Landing without much preparation. When vectored made a meal of it had to goround and landed safely if you can call that second time around. Some guardian angel who's duty time was not over must have taken mercy.
Vilas,
Dig into this matter.
There are a lot that they have not covered and has been hidden.
This is not all the truth.
Company management are good at hide the truth but keep asking and you will be surprise.You said: Some guardian angel who's duty time was not over must have taken mercy.
Yes it was, In the flight it was called EXPAT. Yes An Expat was traveling on this flight as a passenger and he is the one that Saved the day.
Flight G8-338, VT-GOS with 164 passenger and Multi Million dollars Aircraft(Airbus 320) with bunch of ancient people between building on the ground should of crashed , if it was not because of what this expat did.
Go back and dig and ask question from the other pilots and personal that they have been working at the time and they are still there and they will tell you that this is truth.https://www.pprune.org/images/statusicon/user_offline.gif https://www.pprune.org/images/buttons/report.gif (https://www.pprune.org/report.php?p=10559214)

fdr
2nd Sep 2019, 02:06
how did a dyslexic EXPAT save the day...please tell

ROFL Thanks for the highlight of an otherwise forgettable day.

Thanks 'but57.


As long as there have been more than one noise maker, drivers have been shutting down the wrong one. Personally have had guy grab the wrong lever in a 2 engine, and on a 4 engine, the latter, grabbing the #4 shutdown handle and saying confirm "confirm #1...". Stuff happens. This crew got the righteous engine up and running again in short order, recovering from their faux pas. Shades of a B767 over the water west of LAX.

Want to reduce such failures, improve the HMI interface, get rid of extraneous warm fuzzy stuff that has no benefit to the decision process in the cockpit. Improve the training for failures, we are effectively trained to be trigger happy just to complete the matrix in 4 hour sessions, rather than to review the decision making before flicking switches.

A comment was made earlier about confirmation in a shutdown; there is a widespread problem in the inflight restart as well where the confirmation is frequently missed after the selection of fuel to run, where the actioning pilot removes his hand from the fuel control during the process, and in the event of an aborted start fuel chops the engine without confirmation. A perennial problem from a bad checklist and bad training, not limited to any particular airline or aircraft. Usually not a problem with corporate or military jets, where the fuel cutoff is a gated position on the thrust level except with a start in a descent where both throttles may be close to idle.

hans brinker
2nd Sep 2019, 05:33
ManaAdaSystem,

The Crew of this flight was so behind, so behind and lost in the cockpit to what is going on.
It was the Expat that has gone in and saved the day.
Keep digging and try to question of this incident.
They are not telling the truth.

So you say, with 12 post (5 of which are:"look for the expat"). How about you just tell us what happened?