home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!uwm.edu!rutgers!sgigate!sgi!wdl1!wdl39!mab
- From: mab@wdl39.wdl.loral.com (Mark A Biggar)
- Newsgroups: comp.org.eff.talk
- Subject: Re: Software as PE
- Message-ID: <1993Jan5.233126.17915@wdl.loral.com>
- Date: 5 Jan 93 23:31:26 GMT
- References: <1992Dec30.125324.27900@mksol.dseg.ti.com> <522322457DN5.61R@tanda.isis.org> <1993Jan5.154910.19144@nastar.uucp>
- Sender: news@wdl.loral.com
- Distribution: na
- Organization: Loral Western Development Labs
- Lines: 22
-
- In article <1993Jan5.154910.19144@nastar.uucp> phardie@nastar.uucp (Pete Hardie) writes:
- >In article <522322457DN5.61R@tanda.isis.org> marc@tanda.isis.org writes:
- >> It was a software engineer who decided that the brakes on the
- >> Fokker 100 shouldn't operate if a sensor indicated the wheels
- >> were up. They were designated part of the "on the ground"
- >> module. An aircraft systems engineer would have understood the
- >> difference between the sensor and the fact, recognised that
- >> applying brakes in midair could do no harm, and saved a few
- >> pilots a change of underwear.
- >First of all, is this a confirmed thing?
- >Secondly, just to clarify: is the problem here that a sensor failed, thus
- >preventing the brakes from operating when the wheels were in fact down?
-
- It is my understanding that the decision of the software engineer was the
- CORRECT one. On a large jet aricraft the wheel brakes MUST NOT be applied
- until after the wheels are on the ground and rolling because there is too
- much chance of blow-out on touchdown otherwise. The real problem was that
- there was no emeregecy override in case the weight-on-wheels sensor failed.
-
- --
- Mark Biggar
- mab@wdl1.wdl.loral.com
-