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

combined failures & factored distance

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

combined failures & factored distance

Thread Tools
 
Search this Thread
 
Old 25th Jun 2008, 10:32
  #1 (permalink)  
Thread Starter
 
Join Date: Mar 2005
Location: I would like to know
Age: 62
Posts: 110
Likes: 0
Received 0 Likes on 0 Posts
combined failures & factored distance

EXAMPLE :

We have a combined failure with "antiskid inop" (AFM correction of 40 % on landing distance) and "flap failure" (correction of 30 %).

Should I increase landing distance by 70 % (40+30) or calculate the first correction anche THEN multiply by 30 ?

Results are-of course-different and AFM do not give me any information on that.


Thanksssssss

Last edited by gigi116; 25th Jun 2008 at 10:58.
gigi116 is offline  
Old 25th Jun 2008, 10:43
  #2 (permalink)  
Warning Toxic!
Disgusted of Tunbridge
 
Join Date: Jan 2005
Location: Hampshire, UK
Posts: 4,011
Likes: 0
Received 0 Likes on 0 Posts
The increased allowance for anti-skid is because of degraded braking. By factoring it onto the flap failure, you are increasing the penalty for anti-skid above what was in the makers mind. Therefore in my opinion, you add them separately and not factor one on top of the other. That is what I would do. There are tables for defects in the QRH, and if the maker wanted increased penalties to apply, then there would be a combined failure mode given.

I would say I think it unfair to be hammered with that in the simulator!
Rainboe is offline  
Old 25th Jun 2008, 11:49
  #3 (permalink)  
 
Join Date: Oct 2003
Location: If this is Tuesday, it must be?
Posts: 651
Likes: 0
Received 0 Likes on 0 Posts
Our QRH specifically states that speed increments are additive but distance factors are cumulative, i.e. you multiply by 1.3 for the extra speed/less drag of failed flaps then by 1.4 for the lack of anti-skid
However, since the starting figure is the actual landing distance, not the field length required for normal landing (ALD x 1.67) it's not as bad as it first looks. Your example gives a total factor of 1.82, so not dramatically longer than your normal runway.
BizJetJock is offline  
Old 25th Jun 2008, 21:08
  #4 (permalink)  
 
Join Date: Feb 2008
Location: Standby...call you back..
Posts: 210
Likes: 0
Received 0 Likes on 0 Posts
Verry interesting question...

and considering the fact that when everything's ok, you have to factorize the landing distance, for commercial ops...

When in trouble ...this should be ignored ???..this is a question ..not a statement..This safety margin could be considered as well !!!

So with the same exemple.. (ald x 1.82) x 1.67

thanks for your feelings..
roljoe is offline  
Old 26th Jun 2008, 07:02
  #5 (permalink)  
 
Join Date: Oct 2003
Location: If this is Tuesday, it must be?
Posts: 651
Likes: 0
Received 0 Likes on 0 Posts
The lawyer's answer is that no further factoring is required. The normal ops landing distance factor is purely a planning consideration, once you are airborne you use actual distances for calculations.
However, it's a bit of a no-brainer that if you have a choice of places to land flapless/no anti-skid or whatever, one has 1 metre more than the figure you've calculated and the other has a lot more - which do you choose?
BizJetJock is offline  
Old 26th Jun 2008, 10:23
  #6 (permalink)  
 
Join Date: Feb 2008
Location: Standby...call you back..
Posts: 210
Likes: 0
Received 0 Likes on 0 Posts
Thanks, bizjetrock....the answer is obvious..
roljoe 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.