CB1 Posted December 21, 2019 Report Share Posted December 21, 2019 I've noted this in the 170/190 personally and witnessed it in a stream of the 195. The PFD speed scale warning/caution colouring seems to be working off the prediction line as opposed to the current IAS. See below, the speed window has gone reverse video red despite not entering the low-speed awareness nor overspeed tape, however the prediction line has entered the overspeed tape. I'm afraid I don't have an AFM to reference but this video (https://www.youtube.com/watch?v=PQEezXiJg10&t=34s) looks to be an Embraer training video and demonstrates the correct behaviour: You can see the speed window colour only changes based on the actual IAS not the prediction line. As a second issue the the reverse video for overspeed/red stick shaker region should be white text on a red background, currently the text remain black. Cheers Link to comment Share on other sites More sharing options...
alex.koshterek Posted December 22, 2019 Report Share Posted December 22, 2019 Selected to fix in SP 1 Link to comment Share on other sites More sharing options...
Triholer Posted January 27, 2020 Report Share Posted January 27, 2020 Hey there, I just came to this report here on the Known Issue List and made my way through the E190 AOM, where I found this: Quote E190 AOM 14-09-05: [...] 6 - AIRSPEED TREND VECTOR – Shows the airspeed which the airplane will be within 10 s, if the present acceleration/deceleration rate is maintained. [...] 16 - AIRSPEED ROLLING DIGITS – Displays the indicated airspeed (IAS), above 30 kt. GREEN: normal range. AMBER: airspeed trend vector (when displayed) is reaching the VMO/MMO or it is at amber low speed awareness tape or the actual airspeed is at amber low speed awareness tape. RED INVERSE VIDEO: airspeed trend vector (when displayed) or actual airspeed is at red low speed awareness tape or at VMO/MMO barber pole. – The airspeed trend vector when displayed has the priority over actual airspeed to define the airspeed rolling digits color. So from my point of view the actual solution until now is handbook-wise correct and should therefore not be changed in the Service Pack. To the question on why this behavior is not visible in the posted video above, I can just say that I have to give it a pass - luckily until now I was not able to reflect that myself. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now