From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail From: "Alejandro R. Mosteo" Newsgroups: comp.lang.ada Subject: Curious bug in 737 glass instruments Date: Fri, 10 Jan 2020 17:07:04 +0100 Organization: A noiseless patient Spider Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Fri, 10 Jan 2020 16:07:05 -0000 (UTC) Injection-Info: reader02.eternal-september.org; posting-host="d5ef301548005263b244e421ab5e59a8"; logging-data="1039"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18gwfCrzTf+DEZJR6rr04uD" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.1 Cancel-Lock: sha1:kDPyWkx5IBzxJPWALC1hZPbZpMs= Content-Language: en-US X-Mozilla-News-Host: news://news.eternal-september.org:119 Xref: reader01.eternal-september.org comp.lang.ada:57814 Date: 2020-01-10T17:07:04+01:00 List-Id: Came across this one in pprune the other day: https://www.pprune.org/rumours-news/628664-blackout-bug-boeing-737-cockpit-screens-go-blank-if-pilots-land-specific-runways.html https://www.theregister.co.uk/2020/01/08/boeing_737_ng_cockpit_screen_blank_bug/ > "All six display units (DUs) blanked with a selected instrument approach to a runway with a 270-degree true heading, and all six DUs stayed blank until a different runway was selected," noted the FAA's airworthiness directive, summarising three incidents that occurred on scheduled 737 flights to Barrow, Alaska, in 2019." > Although full technical details were not given in the airworthiness directive, the FAA said that the seven runways had "latitude and longitude values" that "triggered the blanking behaviour", suggesting some kind of memory interaction between onboard computers causing the screens to stop displaying any information until a different runway was selected in the flight plan. > The bug affects 737-600, -700, -700C, -800, -900 and -900ER model aircraft, which are running Common Display System Block Point 15 (CDS BP 15) software for their display electronic units (DEUs) together with flight management computer (FMC) software version U12 or later. Just wondering if some Ada is be involved...