Free Republic
Browse · Search
News/Activism
Topics · Post Article

To: JLAGRAYFOX

Ummm... no, the codes do not indicate a blowout of the window. Not at all - a window blowout would have been accompanied by a long list of pressurization loss error codes and it wasn’t. I posted this in one of the other threads:

***

Doesn’t work with the ACARS reporting timeline - fire was first detected inside the bulkhead under/around the right front windows. Check the timeline (I’ve annotated it):

00:26Z 3044 ANTI ICE R WINDOW - right forward cockpit window anti-ice sensor has detected elevated temperatures when the computer wasn’t expecting to see them.
00:26Z 561200 R SLIDING WINDOW SENSOR - right side cockpit window sensor has detected elevated temperatures when the computer was not expecting to see them.
00:26Z 2600 SMOKE LAVATORY SMOKE - Smoke detected in the lavatory. The front lav on an A320 is one the *left* side of the aircraft. It shares the back wall of the cockpit on the left side.
00:27Z 2600 AVIONICS SMOKE - Smoke detected in the avionics bay which IIRC is under the floor of the cockpit.
00:28Z 561100 R FIXED WINDOW SENSOR - right side cockpit window sensor has detected elevated temperatures when the computer was not expecting to see them.
00:29Z 2200 AUTO FLT FCU 2 FAULT - Autopilot module 2 has failed, probably due to fire given prior messages.
00:29Z 2700 F/CTL SEC 3 FAULT - Part of main flight controls has failed, probably due to fire given prior messages.

This reads like an underfloor fire.

***

Note the time between the codes - three *minutes* between first heat alarm and loss of one of the flight control systems. There are no in-cockpit codes, so this fire was not actually in the cockpit. The smoke was wafting its way up from the bottom of the fuselage and getting out by any way it could - first through the lavatory plumbing and electrical passthroughs then getting into the avionics bay after the (presumed) fire had breached its containment.

This does *not* rule out terrorism, but it does rule out in-flight participation by anyone on board. The areas where an incendiary could cause these areas and no others are *not* accessible in flight. Nor is the forward baggage compartment far enough forward for a device in the luggage to be the likely cause. If it was terrorism, it was an incendiary placed in the nose or in the fuselage under the cockpit area by someone on the ground. It is, however, more likely that this is another SwissAir Flight 111 incident where faulty electronics or wiring caused a fire. Remember, this is a FRENCH built plane.


13 posted on 05/23/2016 4:59:38 AM PDT by Spktyr (Overwhelmingly superior firepower and the willingness to use it is the only proven peace solution.)
[ Post Reply | Private Reply | To 4 | View Replies ]


To: Spktyr
Last ATC communication was the handoff to the next controller in line just like with the Malaysian plane that disappeared. Since the time when one is between controllers (at least judging from my experience in the US) is less than a percent of the time a plane is actually in the air, I'd guess these were planned events.

ML/NJ

20 posted on 05/23/2016 5:28:06 AM PDT by ml/nj
[ Post Reply | Private Reply | To 13 | View Replies ]

To: Spktyr

You make some good points........however I am not an Airbus expert....but I am a B707 & 747 maintenance expert. I have also worked in aviation maintenance for too many years to mention, wth a number of airlines and OEMs, mainly Boeing!!!

But, knowing that the A320 aircraft is a “fly-by-wire” aircraft and, although it is a fully safe operating system under normal operational modes, a major destruction of computor components and inputs can quickly cause severe loss of active or prevent manual flight control!!! I get nervous when I note that all smoke/fire activity as sent from the “ACARS” inputs is located in the same area...the cockpit, cockpit windows, the left foward lavatory and the E&E lctrical/avionics, control compartment where the flight contol computors are located.

Now......my input is just me thinking out loud....but I am 100% sure that Airbus Engineering knows exactly what happened, based on the input from “ACARS”. If this model of Airbus aircraft has had a long list of these type failures, I could see keeping an open mind. But, no such history trail exists. All are silent on both the Captain & First Officer & no “Mayday” call from either of the flight crew. Airbus can quickly calculate the ACARS failure messages in a time lapse and know whether sufficient time was available for a crew “Mayday” radio call or not!!! Like I say Airbus has a darn good idea exactly what happened on the doomed airplane and, I believe, they believe their aircraft was not al fault & terrorism is at fault.....set off by either one or both of the flight crew or, an invader into the cockpit or lavatory, setting off the bomb device of in a strategic location. I stiil smell the Muslim Brotherhood/ISIS cartel are the villians of this massive planned and successfully carried out massacre...and, they for obvious reasons of the Obama/Clinton adoration of MB/ISIS want to remain silent. We shall see, although, Airbus and the involved governments, including the USA, will spin this incident out over a prolonged period of time. The truth and timely relaease of such is not at the top of the list for the media, the governments, the aircraft manufacturer. The public, and, sadly, the relatives and loved ones of those murdered on this ill fated airplane take it in the shorts once again!!!!


26 posted on 05/23/2016 6:28:41 AM PDT by JLAGRAYFOX (Defeat both the Republican (e) & Democrat (e) political parties....Forever!!!)
[ Post Reply | Private Reply | To 13 | View Replies ]

To: Spktyr
It is, however, more likely that this is another SwissAir Flight 111 incident where faulty electronics or wiring caused a fire.

Possibly. But it seems the crew would have had time to get off a distress signal. There are also witnesses that saw the plane blow up.

27 posted on 05/23/2016 7:47:59 AM PDT by plain talk
[ Post Reply | Private Reply | To 13 | View Replies ]

Free Republic
Browse · Search
News/Activism
Topics · Post Article


FreeRepublic, LLC, PO BOX 9771, FRESNO, CA 93794
FreeRepublic.com is powered by software copyright 2000-2008 John Robinson