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

Airbus 320 Honeywell H3 FMGC Standard

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

Airbus 320 Honeywell H3 FMGC Standard

Thread Tools
 
Search this Thread
 
Old 8th Jun 2022, 07:27
  #1 (permalink)  
Thread Starter
 
Join Date: Jul 2019
Location: In the Dog Box
Posts: 6
Likes: 0
Received 0 Likes on 0 Posts
Red face Airbus 320 Honeywell H3 FMGC Standard

Can anyone offer any insight into the new Honeywell H3 FMGC standard now available on the 320? In particular, what is behind Airbus’s decision to prioritise the vertical path over selected speed when in a “latched on profile descent”?

15 years of pulling speed to comply with ATC speed requests and then possibly adding a bit of speed brake to maintain or regain the profile if slowing in DES mode, but now the aircraft is maintaining a “latched on profile descent” at the expense of the selected speed unless I muck about in the MCDU or select OP DES or VS, the latter two then requiring an adjustment to selected Altitude to comply with coded STAR constraints.

Someone should have said “If it ain’t broke, don’t fix it”.

Any real world experience managing this “not really selected speed” whilst “latched on profile”. How is it working for you?
Yeah nah is offline  
Old 8th Jun 2022, 11:28
  #2 (permalink)  
 
Join Date: Jun 2014
Location: Mordor
Posts: 335
Likes: 0
Received 0 Likes on 0 Posts
I’m not familiar with the new FMS standard, but it seems similar to Boeing VNAV, which keeps the profile even if it means flying significantly faster than the tgt speed.

it actually works quite well on Boeings. The only difference will be that instead of using speed brakes to maintain the path, you will use the speed brakes to maintain the speed…
Sidestick_n_Rudder is offline  
Old 8th Jun 2022, 13:19
  #3 (permalink)  
 
Join Date: Mar 2006
Location: England
Posts: 995
Likes: 0
Received 4 Likes on 2 Posts
Is this change a reflection that ATC procedures prioritise computerised flight paths over speed; but speed - time - distance management still required ?

By constraining flight path (FMS Auto), it is more natural to use thrust - airbrake to manage speed opposed to using a secondary effect of these to manage flight path ?
PEI_3721 is online now  

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.