-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[A380X] FCU ALT ABOVE/BELOW A/C on FMA (Batch 7) #9410
Comments
Hello, are there any references for this ? My FCOM doesn't mention these messages (maybe because it's from 2011 lol) and I would like to take a look at this request and maybe try implementing it. |
I have an A350 reference from the video over at https://pbnportal.eu/epbn/main/Using-PBN/PBN-on-the-Flight-Deck/RNP-Authorisation-Required--AR--Approach.html: |
As far as logic goes I know it's only shown in V/S and FPA and the altitude being above/below respectively. It's to protected you from climbing/descending unrestricted. Apparently the "FCU ALT ABOVE A/C" is also only shown for 10s, whereas the other one is shown continuously. |
Right, I might have a look at it. (This doesn't mean anyone reading this cannot start working at it - if you've implemented this - go ahead and open a PR) Thank you for the video and extra info! |
The logic behind being that you can get in an underspeed condition with inadvertant +VS and with inadvertant -VS you can only CFIT? I'd consider both equally dangerous, would be interesting to know what Airbus thought if it is like this |
High AOA protection prevents underspeed being an issue. |
I know the FBW protects against it in normal law, but doesn't that raise the question even more? |
Description
In batch 7 two new messages have been introduced:
These show when you're VS/FPA and not protected by ALT. For example, climbing with V/S and FCU ALT below current altitude would result in "FCU ALT BELOW A/C", and vice-versa.
References (optional)
No response
Additional info (optional)
No response
Discord Username (optional)
No response
The text was updated successfully, but these errors were encountered: