Go Back  PPRuNe Forums > Flight Deck Forums > Tech Log
Reload this Page >

Airbus Smoke/Fire checklist and emergency config summary.

Wikiposts
Search
Tech Log The very best in practical technical discussion on the web

Airbus Smoke/Fire checklist and emergency config summary.

Thread Tools
 
Search this Thread
 
Old 24th Jan 2012, 05:29
  #1 (permalink)  
Thread Starter
 
Join Date: Jun 2007
Location: Doha
Posts: 64
Likes: 0
Received 0 Likes on 0 Posts
Airbus Smoke/Fire checklist and emergency config summary.

Hi folks,

Does anyone have a thought on whether or not the use of the Emerg electric config summary is appropriate after having had smoke and elected to set ember elec config?

The FCOM has been amended (2011).

Thanks
9 points is offline  
Old 24th Jan 2012, 08:59
  #2 (permalink)  
 
Join Date: Oct 2009
Location: UK
Posts: 1,270
Likes: 0
Received 0 Likes on 0 Posts
Hi 9 points,

It depends on the length of runway I have chosen to divert to. If it was so long that I could land in Emer Config - then I'd probably leave it in Emer Elec and consult the summary.
If I needed anti skid brake system in order to stop - then I'd restore the electrics and wouldn't need to consult the summary.
rudderrudderrat is offline  
Old 24th Jan 2012, 12:12
  #3 (permalink)  
 
Join Date: May 2000
Location: Glorious West Sussex
Age: 76
Posts: 1,020
Likes: 0
Received 0 Likes on 0 Posts
It is appropriate, in order to calculate the LDR...

Other considerations...
If selcting EMER ELEC config has definitely cured the smoke I would consider remaining in that config ..

If EMER ELEC has no effect on the smoke I would prefer to reinstate GEN2 and EMER ELEC GEN1 LINE ... as required by the QRH procedure and ECAM .. I quite like Anti-Skid and Fuel Pumps working...
See FCOM 3 for more gen.
TyroPicard is offline  
Old 25th Jan 2012, 13:08
  #4 (permalink)  
Thread Starter
 
Join Date: Jun 2007
Location: Doha
Posts: 64
Likes: 0
Received 0 Likes on 0 Posts
Thanks Tyro
I presume your a320 so there are some systems differences, I'm 330 but flew the 320 years ago.
Yep I figure it is a quick way get LDR etc. not mandatory but as a technique it works. We just have to cover ourselves by completing the approved checklist if time permits...
thanks
9 points is offline  
Old 25th Jan 2012, 21:22
  #5 (permalink)  
 
Join Date: May 2000
Location: Glorious West Sussex
Age: 76
Posts: 1,020
Likes: 0
Received 0 Likes on 0 Posts
9P
Doh! If you had specified A330 I would not have bothered - but I spent a useful 15 minutes refreshing so no harm done!
TyroPicard is offline  
Old 28th Jan 2012, 02:39
  #6 (permalink)  
 
Join Date: Oct 2004
Location: Floating around the planet
Posts: 386
Likes: 0
Received 0 Likes on 0 Posts
For the A330 Guys:

I think there is one step missing at QRH:

When the QRH says to reconect the GENs (2000ft or 3 min )they forget to tell you to also connect LAND RECOVERY. I sent an email to Airbus , but no replies so far.

Am I correct or I´m missing something?

A320
A-3TWENTY is offline  
Old 28th Jan 2012, 07:49
  #7 (permalink)  
Thread Starter
 
Join Date: Jun 2007
Location: Doha
Posts: 64
Likes: 0
Received 0 Likes on 0 Posts
Bit fatigued at the moment but I think land recovery is not necessary once the gens are back online. Will give it some thought though.
Too tired now....
Cheers
9 points is offline  
Old 2nd Feb 2012, 04:07
  #8 (permalink)  
 
Join Date: Oct 2004
Location: Floating around the planet
Posts: 386
Likes: 0
Received 0 Likes on 0 Posts
Since we are restoring from an ELEC EMERG CONFIG , LAND RECOVERY shoud be always used .

Check it at FCTM AO 24

A320
A-3TWENTY 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



Contact Us - Archive - Advertising - Cookie Policy - Privacy Statement - Terms of Service

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