Scary! I squirmed in my seat as I read the article. You see I did the electrical design part of a similar system. Our system had a critical design flaw. It was a mechanical error so I was not responsible for the error but it could have crashed the airplane. Luckily we did not use a contractor for certification. We submitted straight to the FAA. The FAA spotted the problem and it was soon fixed. It makes me wonder what would have happened if we used a contractor to certify.
In another vein, did anyone else pick up the error in the article? It related to the disk drive. It probably was the reporter's error. I see errors of this kind so frequently when you have a journalist or English major writing about scientific issues. They are not equipped to do the job. Fred Townsend Ken Javor wrote: > I drove from Huntsville, AL to Ft. Wayne, IN, today mostly because flying > is such a pain these days. Now I'm glad I drove from a safety viewpoint as > well. > > Seriously, there is something wrong if gov't oversight is necessary to make > sure an aircraft is put together right. I think there is a very simple, > very old fix for this problem. Accountability. They had it back in > Babylon. The Code of Hammurabi. If an architect builds a house, and that > house collapses and kills the owner, then the architect's life is also > forfeit... > > on 2/18/03 7:50 PM, Gary McInturff at [email protected] > wrote: > > > > > http://www.usatoday.com/travel/news/2003/2003-02-17-swissair.htm > > > > > > > > > > ------------------------------------------- > > This message is from the IEEE EMC Society Product Safety > > Technical Committee emc-pstc discussion list. > > > > Visit our web site at: http://www.ewh.ieee.org/soc/emcs/pstc/ > > > > To cancel your subscription, send mail to: > > [email protected] > > with the single line: > > unsubscribe emc-pstc > > > > For help, send mail to the list administrators: > > Ron Pickard: [email protected] > > Dave Heald: [email protected] > > > > For policy questions, send mail to: > > Richard Nute: [email protected] > > Jim Bacher: [email protected] > > > > Archive is being moved, we will announce when it is back on-line. > > All emc-pstc postings are archived and searchable on the web at: > > http://www.ieeecommunities.org/emc-pstc > > > > -- > > Ken Javor > EMC Compliance > Huntsville, Alabama > 256/650-5261 > > ------------------------------------------- > This message is from the IEEE EMC Society Product Safety > Technical Committee emc-pstc discussion list. > > Visit our web site at: http://www.ewh.ieee.org/soc/emcs/pstc/ > > To cancel your subscription, send mail to: > [email protected] > with the single line: > unsubscribe emc-pstc > > For help, send mail to the list administrators: > Ron Pickard: [email protected] > Dave Heald: [email protected] > > For policy questions, send mail to: > Richard Nute: [email protected] > Jim Bacher: [email protected] > > Archive is being moved, we will announce when it is back on-line. > All emc-pstc postings are archived and searchable on the web at: > http://www.ieeecommunities.org/emc-pstc This message is from the IEEE EMC Society Product Safety Technical Committee emc-pstc discussion list. Visit our web site at: http://www.ewh.ieee.org/soc/emcs/pstc/ To cancel your subscription, send mail to: [email protected] with the single line: unsubscribe emc-pstc For help, send mail to the list administrators: Ron Pickard: [email protected] Dave Heald: [email protected] For policy questions, send mail to: Richard Nute: [email protected] Jim Bacher: [email protected] Archive is being moved, we will announce when it is back on-line. All emc-pstc postings are archived and searchable on the web at: http://www.ieeecommunities.org/emc-pstc
