You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Velocity Vector lights on both EFIS are not lighting up when TRK FPA is selected.
Expected behavior
A video of crew conducting circuits in an A350 Simulator. I know this is an A350 instead of the A380! but they share common features and system behaviours. Just for reference at video times 2:43 and 9:06 shows when pilot monitoring selects TRK/FPA, the (VV) Velocity Vector on EFIS panels is automatically selected on both sides. When HDG V/S is selected, (VV) Velocity Vector is automatically selected off, both sides. At video time 7:52 when the thrust levers are moved to TOGA detent, the FD's turn on and the AFS reverts back from TRK/FPA to HDG V/S and the (VV) Velocity Vector is automatically turned off.
BravoMike99
changed the title
The Velocity Vector lights on both EFIS when selecting TRK FPA.
VV P/B does not light on both EFIS when selecting TRK FPA.
Nov 14, 2024
Aircraft Version
Stable
Build info
.
Describe the bug
The Velocity Vector lights on both EFIS are not lighting up when TRK FPA is selected.
Expected behavior
A video of crew conducting circuits in an A350 Simulator. I know this is an A350 instead of the A380! but they share common features and system behaviours. Just for reference at video times 2:43 and 9:06 shows when pilot monitoring selects TRK/FPA, the (VV) Velocity Vector on EFIS panels is automatically selected on both sides. When HDG V/S is selected, (VV) Velocity Vector is automatically selected off, both sides. At video time 7:52 when the thrust levers are moved to TOGA detent, the FD's turn on and the AFS reverts back from TRK/FPA to HDG V/S and the (VV) Velocity Vector is automatically turned off.
https://www.youtube.com/watch?v=bwzhsBNwrIU
Steps to reproduce
References (optional)
No response
Additional info (optional)
No response
Discord Username (optional)
No response
The text was updated successfully, but these errors were encountered: