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=0.6 required=5.0 tests=BAYES_00,FROM_WORDY autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,af986aa93b89733e X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-04-12 06:10:37 PST Path: supernews.google.com!sn-xit-02!supernews.com!news.gv.tsc.tdk.com!falcon.america.net!sunqbc.risq.qc.ca!howland.erols.net!newscon04-ext.news.prodigy.com.MISMATCH!newscon04.news.prodigy.com!prodigy.com!newsmst01!postmaster.news.prodigy.com!newssvr10-int.news.prodigy.com.POSTED!not-for-mail From: "Ken Garlington" Newsgroups: comp.lang.ada References: <1Q_z6.474$VI4.153258056@newssvr10-int.news.prodigy.com> <3htA6.809$j53.240510015@newssvr10-int.news.prodigy.com> Subject: Re: V-22 Osprey and exception handling Organization: ex-FlashNet, now Prodigy X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Message-ID: <6LhB6.1318$FY6.412769297@newssvr10-int.news.prodigy.com> NNTP-Posting-Host: 65.65.210.97 X-Complaints-To: abuse@prodigy.net X-Trace: newssvr10-int.news.prodigy.com 987080770 6207069 65.65.210.97 (Thu, 12 Apr 2001 09:06:10 EDT) NNTP-Posting-Date: Thu, 12 Apr 2001 09:06:10 EDT Date: Thu, 12 Apr 2001 13:06:10 GMT Xref: supernews.google.com comp.lang.ada:6815 Date: 2001-04-12T13:06:10+00:00 List-Id: "Ted Dennison" wrote in message news:L7GA6.2062$FY5.147618@www.newsranger.com... : In article <3htA6.809$j53.240510015@newssvr10-int.news.prodigy.com>, Ken : Garlington says... : > : > : >Ted Dennison" wrote in message : >news:knjA6.787$FY5.40878@www.newsranger.com... : >: In article <1Q_z6.474$VI4.153258056@newssvr10-int.news.prodigy.com>, Ken : >: Garlington says... : >: failures when it should have been. Until the other report that is to go : >: >into the aircraft itself comes out... : > : >Which report is this? : : From the press conference that you posted: [Aircraft Mishap Board] AFAIK, military mishap board results are not released to the public. Furthermore, as the General noted, the mishap board's primary focus is on developing recommendations for avoiding future mishaps. The JAGMAN report is intended to focus on the cause of a mishap. I would not expect the mishap board to generate much more information with respect to the cause of the accident. With respect to the NAVAIR review, this will also be focused on making sure there are no similar failure paths in the software, not further identifying the root cause of the accident. I recently had a chance to get more information from the company that developed the software, and the root cause of this particular incident apparently is well understood at this point.