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

B777-300ER Landing OPT Max manual vs Max Auto

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

B777-300ER Landing OPT Max manual vs Max Auto

Thread Tools
 
Search this Thread
 
Old 15th Nov 2017, 07:17
  #1 (permalink)  
Thread Starter
 
Join Date: Jun 2014
Location: Aussie and US
Posts: 44
Likes: 0
Received 0 Likes on 0 Posts
B777-300ER Landing OPT Max manual vs Max Auto

I was asked by a colleague about some OPT landing calculations and it's got me stumped!

We are using Boeing OPT on iPad for B777-300ER and using the landing-enroute calculator.

For a manual landing the max manual brake landing distance is shorter than the max auto brake landing distance (which I expect).

For an autoland the max manual brake landing distance is longer than the max auto brake landing distance (which has me stumped!)

I tried several runways and conditions (the difference is greater with dry runway) with similar results.
LH777 is offline  
Old 15th Nov 2017, 08:13
  #2 (permalink)  
 
Join Date: Jul 2000
Location: My views - Not my employer!
Posts: 1,031
Likes: 0
Received 0 Likes on 0 Posts
Guessing mode....

Rollout mode will be active guiding the aircraft down the runway. As it makes it's inputs, perhaps Boeing discovered that the pilot can't just ram down the brake pedals whilst the autopilot controls the aircraft on the centreline. When you are doing it all yourself its easier. Maybe there is an adjustment for that?
Cough is offline  
Old 15th Nov 2017, 08:23
  #3 (permalink)  
Thread Starter
 
Join Date: Jun 2014
Location: Aussie and US
Posts: 44
Likes: 0
Received 0 Likes on 0 Posts
I had researched along those lines but if that was the case then these techniques would be documented in the FCTM but I cannot find anything along those lines.

From the depths of my memory JAA needed autoland distances multiplied by 115% of certified landing distance (not sure if FAA requires this). Is this correct? Maybe the OPT figures cannot be less than the 115% so they are artificially increased?

Just looked up an old Airbus document "Getting to grips with AC performance". It seems JAA (JAR AWO - now CS AWO?) used to require autoland distances to be increased by 3 x std dev of some of the airborne portion (end of g/s to touchdown) and also by 3 x std dev of ground roll. So the above 115% may not be correct.

Last edited by LH777; 15th Nov 2017 at 08:38.
LH777 is offline  
Old 15th Nov 2017, 10:45
  #4 (permalink)  
 
Join Date: Jan 2000
Location: FL410
Posts: 860
Likes: 0
Received 0 Likes on 0 Posts
There is indeed a margin built in as the pilot has no external reference to keep aircraft straight during rollout.This in turn results in less brake pressure being applied as concentration is diverted to keeping plane tracking centreline.
Skyjob is offline  
Old 16th Nov 2017, 14:22
  #5 (permalink)  
 
Join Date: Dec 2002
Location: UK
Posts: 2,451
Likes: 0
Received 9 Likes on 5 Posts
Skyjob, it’s difficult to understand the logic of a visual constraint affecting brake use.
In the very low visibility conditions suggested, then the automatic landing system should have a high integrity rollout control or guidance element, thus the pilot should not be in visual loop as you suggest.
Does the T7 have rudder fine steering? If so, then steering would be independent of brake pressure.
Manually braked landing distances do not normally consider crosswind effects - ops on contaminated runways might.

Are there any system differences involving brake application between manual and auto landing?
Any differences in the deployment of spoilers, WoW, or reverse thrust, auto/manual land?
Presumably the landing data is based on the Boeing ‘actual distance’, but is the basis of calculation the old style ‘actual’ actual or the more recent Operational Landing Distances (with/without Factors).

With fast fading memory and from a very longtime ago, didn’t autoland distances always have to assume a wet runway, and that Cat3B ops had to use autobrake.?
safetypee is offline  
Old 20th Nov 2017, 17:53
  #6 (permalink)  
 
Join Date: Apr 2008
Location: nowhere
Posts: 1
Likes: 0
Received 0 Likes on 0 Posts
For a 235 ton landing weight I found this info. For what I will call a normal landing the required runway was 5615' using max autobrake while max manual braking had a significantly shorter requirement of 4462'.

If autoland was used, the max autobrake setting increased by around 300 feet to 5918' but, the max manual braking distance increased by almost 3000 feet to 7301'.

Why so much?
JammedStab is offline  
Old 22nd Nov 2017, 09:30
  #7 (permalink)  
Thread Starter
 
Join Date: Jun 2014
Location: Aussie and US
Posts: 44
Likes: 0
Received 0 Likes on 0 Posts
Change the runway condition to wet and the difference gets a lot smaller!

I find this inconsistent.
LH777 is offline  
Old 22nd Nov 2017, 12:03
  #8 (permalink)  
 
Join Date: Jan 2008
Location: farmm intersection, our ranch
Age: 57
Posts: 206
Likes: 0
Received 0 Likes on 0 Posts
We consider anything under 4000 RVR to be a wet runway.
flyingchanges is offline  
Old 22nd Nov 2017, 19:47
  #9 (permalink)  
 
Join Date: Feb 2001
Location: The Winchester
Posts: 6,553
Received 5 Likes on 5 Posts
Are there any system differences involving brake application between manual and auto landing?
FWIW not that I know of and in our old fashioned tables (in EASA land) I can find no extra increments that need applying to braking distances In the event of planning for an auto land for any of our T7s...no mention of this in our FCTM either....

Interested to hear more..
wiggy 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.