Go Back  PPRuNe Forums > Flight Deck Forums > Rumours & News
Reload this Page >

Engine failure during take-off at CPH.

Rumours & News Reporting Points that may affect our jobs or lives as professional pilots. Also, items that may be of interest to professional pilots.

Engine failure during take-off at CPH.

Old 10th Nov 2008, 16:27
  #1 (permalink)  
Thread Starter
 
Join Date: Dec 2004
Location: Belgium
Posts: 4
Engine failure during take-off at CPH.

Did anyone hear about a Bluebird Cargo Boeing 737 having had an engine failure (and stall) during take-off last night in CPH?

Any additional infos?
olivier737 is offline  
Old 11th Nov 2008, 08:16
  #2 (permalink)  
 
Join Date: Oct 2002
Location: In my seat
Posts: 822
Heard the communication on Kastrup.
They declared an urgency and asked for vectors back to land in CPH.
All very professionally handled by the Bluebird crew and ATC.

Rumoured to be a severe damage of the HP compressor.
despegue is offline  
Old 11th Nov 2008, 18:11
  #3 (permalink)  
 
Join Date: Dec 2003
Location: BELGIUM
Posts: 56
Well trained pilots
DIRRIK is offline  
Old 12th Nov 2008, 21:08
  #4 (permalink)  
 
Join Date: Feb 2002
Location: Somewhere between Europe and Africa
Posts: 155
Does anybody knows if they do single engine taxi out?

Check Six Krueger...
Krueger is offline  
Old 13th Nov 2008, 05:33
  #5 (permalink)  
 
Join Date: Sep 2007
Location: Denmark
Posts: 31
They probarly did a single engine taxi in
Walder is offline  
Old 13th Nov 2008, 06:46
  #6 (permalink)  
 
Join Date: Oct 2006
Location: Location
Posts: 259
I don't know of any 737 CFM operators who do single engine taxi out ...

Last edited by AltFlaps; 13th Nov 2008 at 07:16.
AltFlaps is offline  
Old 13th Nov 2008, 20:53
  #7 (permalink)  
 
Join Date: Feb 2002
Location: Somewhere between Europe and Africa
Posts: 155
I don't know of any 737 CFM operators who do single engine taxi out ...
And do you know why?
Krueger is offline  
Old 14th Nov 2008, 09:20
  #8 (permalink)  
 
Join Date: Sep 2007
Location: Denmark
Posts: 31
Angel

On the 737 more than 40% N1 is not recommended with taxi speeds below 10 knots, due to risk of FOD.
On taxi out up to 40% N1 on both engines might be required as “brake away thrust” on a fully loaded 737.
If only one engine is operating, much more than 40% N1 is required and risk for FOD is severely increased.
In case of a severe CTOT, we might taxi out on both engines, then shut them down and do a restart when it is time to take off. Normally the delay should be more than 15 minutes if a shut down is done. Remember not to shut down the APU. Saving is lost, if the APU has to be restarted!

On taxi in single engine is only recommended if taxi time is more than 3 minutes, and no full stops are expected.

Walder
Walder is offline  
Old 16th Nov 2008, 07:10
  #9 (permalink)  
 
Join Date: Feb 2002
Location: Somewhere between Europe and Africa
Posts: 155
Thanks Walder
Krueger is offline  
Old 17th Nov 2008, 09:02
  #10 (permalink)  
 
Join Date: Jul 2001
Location: UK
Age: 52
Posts: 47
Well, if Boeing design an aircraft with its engines (knuckles?!) dragging on the floor it's not surprising they're worried about pebble-dashing. Not an issue on the Airbus.
CleanSpeed is offline  
Old 17th Nov 2008, 09:16
  #11 (permalink)  
The Cooler King
 
Join Date: Feb 2004
Location: In the Desert
Posts: 1,697
"Well, if Boeing design an aircraft with its engines (knuckles?!) dragging on the floor it's not surprising they're worried about pebble-dashing. Not an issue on the Airbus"


Farrell is offline  

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off


Thread Tools
Search this Thread

Contact Us - Archive - Advertising - Cookie Policy - Privacy Statement - Terms of Service - Do Not Sell My Personal Information -

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