---------------------------------------------------------- Aviation-List Digest Archive --- Total Messages Posted Tue 09/07/10: 3 ---------------------------------------------------------- Today's Message Index: ---------------------- 1. 11:53 AM - =?us-ascii?Q?Re=3A =5BAviatia=2Ero=5D L13 si L13 Blanik? (releu3@seznam.cz) 2. 11:54 AM - [Aviatia.ro] =?us-ascii?Q?Concluzia prealabila=2E=2E? (releu3@seznam.cz) 3. 11:54 AM - [Aviatia.ro] =?us-ascii?Q?Poate este doar o poveste=2E=2E=2E=2Epoate nu?= [1 Attachment] (releu3@seznam.cz) ________________________________ Message 1 _____________________________________ Time: 11:53:19 AM PST US From: releu3@seznam.cz Subject: Aviation-List: =?us-ascii?Q?Re=3A =5BAviatia=2Ero=5D L13 si L13 Blanik? Vineri a fost un accident in Austria.Si ironia sortii, duminica inainte de intrarea in vigoare a fost un alt accident in Cehia soldat cu decesul elevului de 17 ani. Se pare ca e ceva la aripa. Stirea o am din ziar, nu am cautat pe portalul AESA-/EASA. > ------------ Pvodn zprva ------------ > Od: Gica > Pedmt: Re: [Aviatia.ro] L13 si L13 Blanik > Datum: 07.9.2010 07:56:07 > ---------------------------------------- > Pe ce motiv? > > Gica Pascariu > Flight Design Romania > www. flightdesign. com > > > > > > Op Sep 6, 2010 om 23:50 heeft releu3@seznam.cz het volgende geschreven:\ > > Incepand de duminica 5.9.2010 AESA/EASA a oprit de la zbor numitul planor > ceh(oslovac). > > > > > > > ------------------------------------ Aviatia.ro - Un vis real! -|- http://www.aviatia.ro/ \_____(===)_____/ TOTI PENTRU UNUL SI UNUL PENTRU TOTI ! 0 ! ! 0 -------------------------------------------------------------------------- Cea mai competenta sursa independenta de informare in aviatie din Romania! -------------------------------------------------------------------------- Publicare mesaj : aviatia@yahoogroups.com Inscriere pe lista : aviatia-subscribe@yahoogroups.com Stergere de pe lista: aviatia-unsubscribe@yahoogroups.comYahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/aviatia/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/aviatia/join (Yahoo! ID required) <*> To change settings via email: aviatia-digest@yahoogroups.com aviatia-fullfeatured@yahoogroups.com <*> To unsubscribe from this group, send an email to: aviatia-unsubscribe@yahoogroups.com <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/ ________________________________ Message 2 _____________________________________ Time: 11:54:25 AM PST US From: releu3@seznam.cz Subject: Aviation-List: [Aviatia.ro] =?us-ascii?Q?Concluzia prealabila=2E=2E? Computer Virus Linked (Loosely) To Airline Crash Two years ago, a Spanair MD-82 crashed on takeoff at Madrid, killing 154 people and marking Spain's worst air tragedy in 25 years; now, malicious code infecting a maintenance department computer has been implicated in the crash. To be clear, the code was not flown on the aircraft's own systems and did not cause the crash. This specific crash could have been avoided regardless of the malware's existence. But the discovery of malicious code introduced into an on-ground system operated by the airline's maintenance department does suggests certain negative possibilities. One possible scenario is that the code slowed a program which, if properly maintained, would have flagged the aircraft for service and disallowed the takeoff because of a series of smaller problems already noted with the plane. That's a lot of qualifiers. But the fact that the system was infected and didn't flag the aircraft in this case closed one door on an opportunity to save the flight. It also suggests the u rgency of proper computer maintenance throughout the entire airline system to assure safety of flight. The Spanair jet reportedly had hosted two maintenance problems on the day prior to the crash and then aborted a takeoff just prior to the fatal takeoff run due to a faulty sensor. A maintenance tracking system used by the airline could have issued an alert based on those three anomalies and prevented the next takeoff attempt. But Spanish media reports say it took a full 24 hours for the last anomaly to enter the system. It is possible that delay was caused in part by the influence of bad code. No judgment should be passed until investigative bodies publish their final report. What we do know is that after the aborted takeoff, the crew taxied the aircraft for another attempt and attempted a second takeoff while the aircraft's slats were improperly set. The crew didn't notice the error and it seems no cockpit warnings sounded to make them aware. ________________________________ Message 3 _____________________________________ Time: 11:54:38 AM PST US From: releu3@seznam.cz Subject: Aviation-List: [Aviatia.ro] =?us-ascii?Q?Poate este doar o poveste=2E=2E=2E=2Epoate nu?= [1 Attachment] ------------------------------------------------------------------------------------- Other Matronics Email List Services ------------------------------------------------------------------------------------- Post A New Message aviation-list@matronics.com UN/SUBSCRIBE http://www.matronics.com/subscription List FAQ http://www.matronics.com/FAQ/Aviation-List.htm Web Forum Interface To Lists http://forums.matronics.com Matronics List Wiki http://wiki.matronics.com Full Archive Search Engine http://www.matronics.com/search 7-Day List Browse http://www.matronics.com/browse/aviation-list Browse Digests http://www.matronics.com/digest/aviation-list Browse Other Lists http://www.matronics.com/browse Live Online Chat! http://www.matronics.com/chat Archive Downloading http://www.matronics.com/archives Photo Share http://www.matronics.com/photoshare Other Email Lists http://www.matronics.com/emaillists Contributions http://www.matronics.com/contribution ------------------------------------------------------------------------------------- These Email List Services are sponsored solely by Matronics and through the generous Contributions of its members.