Air France 447

Message Bookmarked
Bookmark Removed

As the news on this broke when the machine was down I'm not surprised there wasn't a thread yet but as the search continues this is starting to turn into more of a mystery:

The Brazilian air force said Thursday night that debris picked up near where officials believe Air France Flight 447 crashed Monday into the Atlantic Ocean was not from the plane.

The news came after the Brazilian navy began retrieving debris Thursday that it believed was wreckage from the flight, which disappeared over the Atlantic Ocean.

On Wednesday, searchers recovered two debris fields and had identified the wreckage, including an airplane seat and an orange float as coming from Flight 447. Officials now say that none of the debris recovered is from the missing plane.

On a technical end the speculations over what happened are grimly fascinating -- there's something of the same feeling of pre-wireless communication here, where a large commercial vessel goes into the blue and simply is never seen again, leaving only supposition behind. Links to the best sites on all this appreciated.

But on a personal level -- we've had a dying in a plane crash thread before, I didn't post on it then but I admit that as the years have passed I've grown pretty uneasy with long flights in general, and flights over the ocean just leave me feeling glum -- and in combination with turbulence, completely freaked more than once. The logical mind in repose can easily review the statistics, know that planes are designed to deal with all that kind of stuff, that the safety record is pretty damn high all around and so forth, and it still won't leave me feeling any better when a plane first starts to shake, out of nowhere or approaching a storm.

For that reason, whatever seems to have happened here -- something that occurred in the middle of the night, in a raging storm, out over the ocean -- completely unnerves me as a true nightmare situation at its worst. It's nothing compared to the real pain friends and family of the victims are going through but even so.

Ned Raggett, Friday, 5 June 2009 02:43 (fourteen years ago) link

LOST

S Wine Floozie (SeekAltRoute), Friday, 5 June 2009 02:49 (fourteen years ago) link

don't you fly a lot??
xpost

L. Ron Huppert (velko), Friday, 5 June 2009 02:54 (fourteen years ago) link

A few times a year.

Ned Raggett, Friday, 5 June 2009 02:55 (fourteen years ago) link

i fly quite a lot but over the years i've gotten more nervous, not more relaxed. this particular story is completely horrifying and hard to think about.

jesus is the man (jabba hands), Friday, 5 June 2009 03:01 (fourteen years ago) link

One of the things I keep noticing in the news stories about this flight is a particular omission.

The story never seems to mention what the make and model of the airplane was. This may have been reported very prominently somewhere and I missed it, but I keep searching the stories in my local newspaper (Oregonian), which I think are straight AP wire accounts, and I have not seen it mentioned, yet.

I suspect this is out of a misplaced desire to placate the huge corporations which build these planes. If true, that sucks.

Aimless, Friday, 5 June 2009 03:20 (fourteen years ago) link

Really? Every story I've read has made it clear it's an Airbus. Specifically an A330-203 -- Wikipedia entry has plenty more.

Ned Raggett, Friday, 5 June 2009 03:21 (fourteen years ago) link

Yeah all the coverage I've seen on TV talks about it.

╓abies, Friday, 5 June 2009 03:30 (fourteen years ago) link

my question is why the hell would a plane fly right into a storm like this. yes i know they're designed to withstand storms remarkably well, but it seems like you should avoid the fuck out of those big storms over oceans imo.

gangsta hug (omar little), Friday, 5 June 2009 03:39 (fourteen years ago) link

Speculation seems to be that there was nowhere else to go -- the storm system was huge enough that one couldn't really fly around it or fly over it.

Ned Raggett, Friday, 5 June 2009 03:41 (fourteen years ago) link

I think I actually heard the make and model mentioned specifically because this particular plane has never/rarely crashed before and is very common. But I could be wrong.

I get totally zenned out when flying because there is absolutely nothing at all I can do about it, and if you go down, you go down - which is statistically very unlikely. I've never flown over the open ocean though, maybe that would change my opinion.

joygoat, Friday, 5 June 2009 03:56 (fourteen years ago) link

This is a mystery indeed. This kind of crash, cruising altitude well into the flight, is so unusual. Also lightening strikes and severe turbulence are common occurrences and have almost never caused an accident. Part of me wonders if the weather thing isn't a red herring. Maybe the severe weather was just a coinciding event and not the actual cause of the crash. Looks like we may never know.

Super Cub, Friday, 5 June 2009 04:30 (fourteen years ago) link

wanna post a ray liotta in turbulence jpeg but too soon

L. Ron Huppert (velko), Friday, 5 June 2009 04:49 (fourteen years ago) link

to the point: the plane "would have been flying through significant turbulence and thunderstorm activity for about 75 miles (125 km), lasting about 12 minutes of flight time."

terrifying. gimme a car crash. at least i can duck right before impact.

dovlandau, Friday, 5 June 2009 06:04 (fourteen years ago) link

how come sully could land a plane in the hudson river but everyones assuming these people are all dead?

Whiney G. Weingarten, Friday, 5 June 2009 06:42 (fourteen years ago) link

that's not a serious question is it

let free dom ring (J0rdan S.), Friday, 5 June 2009 06:47 (fourteen years ago) link

Ned's link affirms my general impression that weather alone is unlikely to have brought down the plane. The weather may have triggered "a cascading series of failures" or whatever they call it. The expert types usually talk about a series of problems leading to a crash. Because there are redundancies designed into airplane systems, one problem can usually be overcome assuming the pilots handle the situation well. Two or three problems together, or a problem mishandled by the pilots, and the plane may be lost.

Take the Buffalo crash a couple of months ago. My understanding is that the plane stalled due to icing, and the autopilot kicked in and began a maneuver to regain airspeed (nose down). The pilots, who seemed shockingly unprofessional and poorly trained, didn't understand what was happening and overreacted in the wrong way, pulled up. Plane loses more airspeed and crashes. The original problem, the stall caused by icing, didn't doom the plane. The pilots mishandling of the problem did.

So seems like the main issue surrounding the 447 crash is what did the turbulence or lightening trigger? Those factors alone are unlikely to have caused the crash, so what came after? The black boxes might answer this question, but they may never be found.

Super Cub, Friday, 5 June 2009 07:18 (fourteen years ago) link

Apparently this is a theory accident investigators are pursuing:

Speed sensors on aircraft fail (could be caused by icing) and the pilots get incorrect speed readings.

Plane is flying way too fast as it encounters the weather and the excessive speed, combined with severe turbulence, puts too much stress on the airplane's frame. The plane breaks up in mid air and falls to the ocean.

Pretty freaky, but there are a lot worse ways to go.

Super Cub, Friday, 5 June 2009 07:34 (fourteen years ago) link

plane crash has got to be one of the worst ways to go imo - if it broke up in mid air... they would've died immediately upon the plane breaking or what?

let free dom ring (J0rdan S.), Friday, 5 June 2009 07:36 (fourteen years ago) link

i fly quite a lot but over the years i've gotten more nervous, not more relaxed.

And I haven't even told you that my company is managing travel for your company.

And I'm backup for your company's account.

"too worldly to compete on /b/" (King Boy Pato), Friday, 5 June 2009 08:09 (fourteen years ago) link

I've been following this story very carefully over at the airliners.net forums and there's a lot of pretty good information there before the threads devolved into commentaries about Air France. There's still precious little information to go on here except for what scant information is available from the ACARS messages and even those readings could be skewed if the weather was severe enough to freeze the pitot tubes up or otherwise damage things from hail.

Carroll Shelby Downard (Elvis Telecom), Friday, 5 June 2009 09:34 (fourteen years ago) link

This airliners.net post is crazy thorough

AirlineCritic From Finland, joined Mar 2009, 49 posts, RR: 0
Reply 1, posted Thu Jun 4 2009 23:47:51 your local time (2 hours 35 minutes 31 secs ago) and read 4636 times:

This is the third version of my list of speculated causes of the accident. Please contribute by adding theories, evidence, or suggesting revisions to the conclusions for existing ones. And I would like to thank everyone who has posted speculations, evidence, and arguments in these threads. The information below is entirely based on your input.

For currently known facts about the accident, please see the Wikipedia at http://en.wikipedia.org/wiki/Air_France_Flight_447

A. Terrorism or other malicious use of explosives

A bomb explodes in the cargo hold, crippling the aircraft's control systems or starting a structural break-up that eventually leads to loss of control.

Supportive evidence: According to Wikipedia, a bomb threat had been made on an earlier flight. Lack of communications from the flight crew indicates either a sudden event or something which lead to significant problems that the crew had to focus on. This would be consistent with the effects of a bomb. The automatic messages about computer system failures sent by the aircraft could be interpreted either as indications that the aircraft's movements have exceeded the limits that the systems can handle, or as indications about direct damage to the systems. A flash of light has been seen by other aircraft in the area.

Evidence against: While terrorist organizations exist both in France and Brazil, there has been no recent activity. No organization has claimed responsibility for the act. There is no specific evidence about a bomb. Nothing is known about any individuals or organizations who would have non-terrorism related reasons for malicious acts. It seems too big of a coincidence that a bomb would go off at the same time as the aircraft flies through very rough weather. Finally, what we know about the sequence of ACARS messages indicates that loss of cabin pressure was the last message in the sequence. This appears to rule out an explosion, unless it was contained in the hull and only damaged internal structures and components. This seems unlikely. The flash of light was apparently seen from too far to be caused by AF 447 related problems.

Open questions: Where are the cargo holds that are used to carry the passengers' luggage? Are they physically close to the computer and navigation systems that ACARS messages reported as failing? And obviously, physical evidence would be useful.

Verdict: Can most likely be ruled out

References: http://en.wikipedia.org/wiki/Air_France_Flight_447#cite_note-58 A flash of white light has been reported by other aircraft in the area: http://ca.news.yahoo.com/s/reuters/0...orld/international_us_france_plane Distance calculation for the flash of light and AF 447 was in Pihero's post in thread 9: http://www.airliners.net/aviation-fo...general_aviation/read.main/4435136

B. Explosion or other rapid, harmful reaction from the cargo

The sequence of events is as in the terrorism theory.

Supportive evidence: The sequence of events fits this theory, as it does the terrorism theory. The cargo might have shifted at the time of turbulence, initiating the reaction.

Evidence against: See the evidence regarding the malicious use of explosives. In addition, there is no information that the cargo could have contained something harmful.

Open questions: More information is needed about what was in the cargo, and who cargo was taken from.

Verdict: Can most likely be ruled out

C. Fire

Fire starts in cargo hold, in systems, or somewhere else in the aircraft. Eventually the fire either disables a sufficient number of aircraft systems leading to a loss of control, or incapacitates the crew.

Supportive evidence: Systems turning themselves off one by one could be caused by fire. Cabin pressure warning might have been generated through the crew's actions to let the air out of the cabin in an effort to put out the fire. The location of the debris indicates that the crew might have turned back in an effort to get to the nearest airport (but it has now become uncertain if any debris has actually been found). The long duration of the ACARS messaging (4 minutes) seems to indicate a slowly progressing event like fire, as opposed to sudden event like a bomb or structural failure. The fire might have been initiated when the aircraft hit heave turbulence 10 minutes before the problems began.

Evidence against: It seems unlikely that the fire could have spread fast enough that the crew would not have notified air traffic control. Why would fire happen exactly at the same time as the aircraft flies through extreme weather? Wouldn't a cargo hold fire lead to an ACARS message?

Open questions: More information is needed about the ACARS messages and whether they could have been caused by fire.

Verdict: Possible, but there are several open questions

D. Weather

D1. Turbulence

Turbulence breaks up the plane, or causes it to enter an uncontrollable dive.

Supportive evidence: Very high winds and turbulence were detected in the area. Tim Vasquez's analysis indicates that there were strong updrafts in the exact area that the flight was expected to fly through. The crew manually sent a report of turbulence 10 minutes before the accident.

Evidence against: other flights in the same time frame and route did not encounter significant turbulence.

Verdict: Possible, but there are several unexplained questions. In particular, why was only AF 447 affected? Or did several issues contribute to the outcome, along with turbulence?

References: Tim Vasquez's analysis: http://www.weathergraphics.com/tim/af447/ AP reports that the pilots sent a report about turbulence and timing of the various events: http://hosted.ap.org/dynamic/stories...CJAC&SECTION=HOME&TEMPLATE=DEFAULT

D2. Lightning

Lightning hits the aircraft and causes either structural or systems damage.

Evidence against: Tim Vasquez's analysis speaks against this.

Verdict: Unlikely, by itself

D3. Hail

Hail hits the aircraft and causes either structural damage, shuts the engines down, or breaks cockpit windows and incapacitates the crew.

Supportive evidence: There has been rumors about ACARS icing messages.

Evidence against: Tim Vasquez's analysis speaks against the occurrence of significant hail. Unless the crew was incapacitated, mere engine shutdown would have lead to the crew contacting the air traffic control. What we know about the sequence of ACARS messages indicates that the cabin pressure loss happened last, which speaks against the accident beginning with the breakage of the cockpit windows.

Open questions: The sequence of ACARS messages needs to be known in more detail.

Verdict: Unlikely

D4. Ice

Icing causes the aircraft to lose its flying capabilities.

Supportive evidence: See the evidence for the hail theory.

Evidence against: Tim Vasquez's analysis speaks against the existence of supercooled water at the flight level and conditions that the aircraft was flying through.

Verdict: Unlikely

D5. Sensor icing

Speed or other sensors are iced over or malfunction in some other way, leading to the computers or pilots taking incorrect action, causing the aircraft to stall and/or break up.

Supportive evidence: There are rumors of icing-related ACARS messages.

Evidence against: Normally the sensors (such as the pitot tubes) are heated. Icing should not affect them, unless the crew failed to turn the heating on, particularly severe icing conditions existed in the strom cell that they flew through, or hail hit the sensors. Also, Tim Vasquez's analysis speaks against the existence of suitable icing or hail conditions.

Open questions: More data is needed about the actual ACARS message sent by the aircraft.

Verdict: Unlikely

References: BBC article: http://news.bbc.co.uk/2/hi/americas/8083474.stm

E. Systems malfunction

A repeat of the Qantas incident: ADIRU failures cause the aircraft control systems to believe that a steep dive and/or nose-up is needed, leading to a loss of control and/or aircraft break-up.

Supportive evidence: See GlobeEx's posts.

Evidence against: It seems unlikely that the crew would have been unable to control the situation at FL35, when crews in the previous incidents were able to regain control with the loss of few hundred feet of altitude. There are some reports that AF uses ADIRUs from a different manufacturer. The long duration (4 minutes) of the automatic messaging speaks against a very sudden event.

Open questions: At this point, we do not yet know if AF used the same manufacturer's ADIRU (Litton) as was involved in the Qantas incident. Rumors indicate that the equipment comes from a different manufacturer, namely Honeywell. No previous incident is known on a Honeywell ADIRU.

Verdict: Unlikely, though more information is needed. Perhaps combined with a pilot error and the effects of the bad weather this theory is more likely, e.g., maybe the recovery was not executed in time.

References: GlobeEx's post, reply 71 in part 8 of the a.net thread: http://www.airliners.net/aviation-fo...general_aviation/read.main/4433331 and reply 129 in part 9 http://www.airliners.net/aviation-fo...general_aviation/read.main/4435136 The Qantas incident is described in http://www.atsb.gov.au/publications/...008/AAIR/pdf/AO2008070_interim.pdf Qantas downplays the link http://www.theaustralian.news.com.au...tory/0,25197,25579625-2702,00.html

F. Collision

Collision with another flying object such as aircraft or meteor.

Supportive evidence: This could cause similar effects as a bomb, so in some sense it fits the sequence of events. A flash of light was seen, which might also be from a meteor

Evidence against: There is no known collision with another aircraft. Meteor collision is extremely improbable. The flash of light was apparently seen from too far to be caused by AF 447 related problems.

Verdict: Very, very unlikely

References: White flash of light: http://ca.news.yahoo.com/s/reuters/0...orld/international_us_france_plane

G. Fuel tank explosion

A TWA800 -like event.

Supportive evidence: Fuel tank explosion, like other explosions, would fit the sequence of events observed through ACARS and lack of a mayday message from the crew.

Evidence against: By this time, the center fuel tank would have been very cold. TWA800 accident required a warm fuel tank for the vapors to develop in suitable quantity.

Verdict: Can be ruled out.

H. Explosive decompression

A cargo door or other part departs the aircraft, leading to an explosive decompression.

Supportive evidence: ACARS message about cabin pressure.

Evidence against: The sequence of messages is wrong, as cabin pressure drop was not the first one.

Verdict: Can be ruled out

I. Crew error

I1. Flying into severe weather

The crew flies directly into the most severe part of the storm

Supportive evidence: Tim Vasquez's analysis of the weather system indicates that it would have been very hard for AF447 to avoid the weather system alltogether, but there is no evidence to suggest that they flew directly into the worst part.

Open questions: Exact flight path is needed.

Verdict: They did fly into the weather, but it is unknown if this was avoidable or if they flew to the worst part. Note that in combination with another problem, such as radar failure the likelihood of this theory would be much higher.

References: Assumed flight path from the BBC article http://news.bbc.co.uk/1/hi/world/americas/8082241.stm Tim Vasquez's analysis http://www.weathergraphics.com/tim/af447/

I2. Flying too high

Trying to fly over the weather system and exceeding limits of the aircraft, leading to a "coffin corner" situation and an unrecoverable stall.

Supportive evidence: None, except perhaps the diffult and hard-to-avoid weather system. Tim Vasquez's analysis points to very high updrafts, which might have contributed to an involuntary gain in elevation.

Open questions: Additional information about the aircraft's altitude is needed.

Verdict: Unlikely, it is very hard to believe that an experienced crew would on purpose violate the aircraft's limits

I3. Excessive corrective action

The crew over-corrects the effects of turbulence or high wind in a manner similar to AA587.

Supportive evidence: This might have lead to separation of control surfaces, which in turn might have lead to autopilot and other control systems giving up. The sequence of ACARS messages might match this situation.

Evidence against: A330 is a fly-by-wire aircraft which may not allow excessive control input. On the other hand, the first ACARS message received indicated disengaging the autopilot and the control systems entering the alternate law mode. This mode has less protection against exceeding the safe flight envelope.

Open questions: More information is needed about the exact ACARS messages and in what conditions they will be sent. More information is needed about the effects of excessive control inputs in the A330 fly-by-wire system.

Verdict: Very unlikely, unless something else happened, disabling the autopilot and then the crew accidentally exceeded the structural limits of the aircraft.

J. Prior damage from a ground collision

The aircraft in question collided in 2006 with an Airbus A321 aircraft. An undetected problem in the wing of the A330 might have stayed dormant until the airframe was stressed in severe turbulence.

Supportive evidence:

Evidence against: The maintenance procedures for inspecting and correcting collision damage are quite extensive, and it is hard to image something was missed.

Verdict: Unlikely

References: http://www.jacdec.de/news/years/ALL2006.txt

K. Combination of factors

K1. Systems failure and crew error

A systems failure initiates an event and the crew fails to respond properly or in time. For instance, a radar failure might lead to the crew flying blind into the worst part of the weather. Or disengaging the autopilot or Airbus flight envelope protection leads the crew to overstressing the airframe.

Supportive evidence: There is no strong evidence of any single event that is know to bring down the airplane. There is evidence of some of the control systems (autopilot, ADIRU) shutting down. While these events should be recoverable, it is easy to imagine a crew error that exacerbates the situation, particularly in bad weather.

Evidence against: There is no information about any errors by the crew. Many of the systems, such as the radar electronics, have backups, and are not expected to completely fail.

Open questions: CVR and FDR are needed to find out more.

Verdict: Possible

K2. External event and crew error

Icing, turbulence, lightning or lightning causes an upset, and the crew reacts in an inappropriate manner or fails to recover in time. Or, alternatively the crew makes an error in setting the proper speed for the type of weather (turbulence, updrafts) which later leads to a stall or a spin.

Supportive evidence: There is no strong evidence of any single event that is know to bring down the airplane. There is evidence of conditions that are potentially harmful (like turbulence), but that are known to be experienced by a large number of aircraft, so its not clear why these events alone would have caused the accident. But it is easy to imagine a combination of two problems, or one problem and a crew error to lead to a disaster.

Evidence against: There is no information about any errors by the crew.

Verdict: Possible

Open questions: Again, CVR and FDR are needed.

References: Incorrect speed has been mentioned in the press as a possible cause of the accident: http://ca.news.yahoo.com/s/reuters/0...orld/international_us_france_plane

K3. External event leading to fire

Turbulence rocks the plane, leading to a short circuit and fire. Lightning hits the plane and causes a fire. The fire eventually spreads to the whole aircraft.

Supportive evidence: The crew reported turbulence, and at least turbulence and maybe even lightning is known to exist in the area. For the other evidence, see the fire theory.

Evidence against: See the evidence regarding fire; it is odd that no ACARS or crew message would have been received from a slowly progressing event such as fire in the cargo hold.

Open questions: Again, CVR and FDR are needed.

Verdict: Possible, but there are open questions

References: CB97's reply 105 on thread 9: http://www.airliners.net/aviation-fo.../general_aviation/read.main/443513 Tim Vasquez's weather analysis: http://www.weathergraphics.com/tim/af447/

Carroll Shelby Downard (Elvis Telecom), Friday, 5 June 2009 09:36 (fourteen years ago) link

The black boxes might answer this question, but they may never be found.

There's a good chance they will be though. Hell, one of the boxes from SAA 295 (possibly the spookiest airliner crash ever) was recovered from 5000 meters deep.

Carroll Shelby Downard (Elvis Telecom), Friday, 5 June 2009 09:44 (fourteen years ago) link

Speed sensors on aircraft fail (could be caused by icing) and the pilots get incorrect speed readings.

Case in point: http://en.wikipedia.org/wiki/Aeroperú_Flight_603

(although in this case, a piece of tape was left over one of the sensors)

Carroll Shelby Downard (Elvis Telecom), Friday, 5 June 2009 09:47 (fourteen years ago) link

On Wednesday, searchers recovered two debris fields and had identified the wreckage, including an airplane seat and an orange float as coming from Flight 447. Officials now say that none of the debris recovered is from the missing plane.

Ok is anyone else a little upset by the fact that there's this much shit floating in the ocean that looks like pieces of this airplane, but isn't?

Brundlefly (kenan), Friday, 5 June 2009 09:52 (fourteen years ago) link

Aside, I had no idea this place existed: http://en.wikipedia.org/wiki/Saint_Peter_and_Paul_Rocks

Carroll Shelby Downard (Elvis Telecom), Friday, 5 June 2009 09:57 (fourteen years ago) link

"a rocky place where my seed can find no purchase"

Brundlefly (kenan), Friday, 5 June 2009 10:06 (fourteen years ago) link

Was I alone in thinking that it was pretty difficult to lose an airliner these days?

ambience chaser (S-), Friday, 5 June 2009 11:36 (fourteen years ago) link

i was ok on planes, but i've now got contagious freaked deathcrash meltdown due to my girlfriend's manic hand-clutching on take-off. (we're flying to sydney tomorrow morn)

wilter, Friday, 5 June 2009 12:38 (fourteen years ago) link

Was I alone in thinking that it was pretty difficult to lose an airliner these days?

this is an important aspect of the story. it's potentially easier to find an automobile than a jumbo-jet. we can pinpoint the location of most anything, most anywhere in the world assuming it has the right equipment. GPS is hardly an exotic technology at this point. Yet, investigators have to rely on the last radar hit and projected flight path to find this plane.

Super Cub, Friday, 5 June 2009 17:55 (fourteen years ago) link

How would you use GPS to find a car? The GPS device in your car is only a receiver. The satellite that broadcasts the signal doesn't know where the receivers are.
Cell phone type signals could help (your cell phone identifies itself to the network, you also transmit signals), except that there's no reception on the high seas.

StanM, Friday, 5 June 2009 18:22 (fourteen years ago) link

How would you use GPS to find a car? The GPS device in your car is only a receiver. The satellite that broadcasts the signal doesn't know where the receivers are.
Cell phone type signals could help (your cell phone identifies itself to the network, you also transmit signals), except that there's no reception on the high seas.

http://en.wikipedia.org/wiki/GPS_tracking

Super Cub, Friday, 5 June 2009 23:11 (fourteen years ago) link

Ok, it's not impossible. Isn't it kind of like the (?) ACARS messages planes already have, though?

StanM, Friday, 5 June 2009 23:32 (fourteen years ago) link

ACARS could be used to push GPS data to receivers on the ground, I would assume. I have no idea why such a system does not exist. Seems easy to do.

Super Cub, Friday, 5 June 2009 23:47 (fourteen years ago) link

Cost? (Would probably be considerable. An always-on connection with every plane in the air all over the world, when there's already more than 5,000 commercial flights in the air above north america alone at any given time - I wish I remembered where I read that, but I did) also, Different standards everywhere and an already full transmission spectrum?

If it would be cheap and easy I think we'd already have it. Now, it's not worth bothering with just because of this one freak occurrence where one crashed plane can't be located right away. (Statistically, this just doesn't happen.)

StanM, Saturday, 6 June 2009 00:11 (fourteen years ago) link

I have no idea why such a system does not exist. Seems easy to do.

It's entirely possible that this could be the incident that spurs this on.

Carroll Shelby Downard (Elvis Telecom), Saturday, 6 June 2009 00:15 (fourteen years ago) link

Now, it's not worth bothering with just because of this one freak occurrence where one crashed plane can't be located right away. (Statistically, this just doesn't happen.)

At least twice before:
http://en.wikipedia.org/wiki/Adam_Air_Flight_574
http://en.wikipedia.org/wiki/South_African_Airways_Flight_295 (though in this case, the pilot did manage to get off some radio transmissions)

Carroll Shelby Downard (Elvis Telecom), Saturday, 6 June 2009 00:23 (fourteen years ago) link

CNN has anticipated our discussion here: http://edition.cnn.com/2009/TECH/06/03/db.plane.nav.tracking/index.html

StanM, Saturday, 6 June 2009 00:44 (fourteen years ago) link

They still think they found the right wreckage in that article though, btw.

StanM, Saturday, 6 June 2009 00:51 (fourteen years ago) link

http://www.salon.com/tech/col/smith/2009/06/02/askthepilot322/index.html

cozwn, Saturday, 6 June 2009 05:22 (fourteen years ago) link

Bermuda Triangle.

For reals.

(*゚ー゚)θ L(。・_・)   °~ヾ(・ε・ *) (Steve Shasta), Saturday, 6 June 2009 05:43 (fourteen years ago) link

SuperCub:

it's potentially easier to find an automobile than a jumbo-jet. we can pinpoint the location of most anything, most anywhere in the world assuming it has the right equipment.

there is a rather massive difference between triangulation within dense urban centers versus remote intercontinental flight paths.

(*゚ー゚)θ L(。・_・)   °~ヾ(・ε・ *) (Steve Shasta), Saturday, 6 June 2009 05:48 (fourteen years ago) link

just sayin...

(*゚ー゚)θ L(。・_・)   °~ヾ(・ε・ *) (Steve Shasta), Saturday, 6 June 2009 05:48 (fourteen years ago) link

* 11 p.m. The pilot sends a manual signal saying the jet was flying through CBs -- towering cumulo-nimulus thunderheads.

* 11:10 p.m. A cascade of automatic messages indicate trouble: The autopilot had disengaged, stabilizing controls were damaged, flight systems deteriorated.

* 11:13 p.m. Messages report more problems: The system that monitors speed, altitude and direction failed. The main flight computer and wing spoilers failed.

* 11:14 p.m. The final message indicates a loss of cabin pressure and complete system failure -- catastrophic events in a plane that was likely already plunging toward the ocean.

: /

cozwn, Saturday, 6 June 2009 05:57 (fourteen years ago) link

off-topic but related. terrifying and sad

http://www.telegraph.co.uk/news/worldnews/northamerica/canada/5167883/Man-jumps-to-his-death-from-Canadian-charter-plane.html

cozwn, Saturday, 6 June 2009 06:13 (fourteen years ago) link

Weirder and weirder:

Airlines confirmed that at least a dozen aircraft departed roughly at the same time and traversed approximately the same route, but did not report problematic weather conditions. This has led some aviation experts to suggest that technical problems on the airplane might be the main cause of the crash, though they may have combined with weather conditions to create serious problems.

...In addition to Flight 447, Air France had four other Paris-bound flights that left in the same broad time frame from that part of the world, according to an airline spokesman. One flight left Rio de Janeiro, Brazil, at 4:20 p.m. At that same moment, another Air France flight left nearby Sao Paulo. A third Air France flight left Buenos Aires, Argentina, at 5:50 p.m., also heading for Paris. A final Air France flight left Sao Paulo at 7:10 p.m., almost exactly when the doomed flight took off from Rio.

All of these flights took a similar route toward Paris, heading first toward Recife on the east coast of Brazil and then continuing northeast over the Atlantic. None of the other flights experienced anything unusual, the spokesman said. All arrived in Paris the next day, with no significant delays of any kind.

That same evening two Air Iberia flights bound for Madrid, Spain, left Brazil at about the same time as Flight 447; one departed from Rio de Janeiro and another from Sao Paulo, according to officials at Iberia. Those flights also reported no problems.

It was the same story for one British Airways flight and three Air TAM Brazil flights, all of which flew routes similar to the missing plane.

Although none of the other flights are known to have reported weather problems en route, aviation experts said weather can change suddenly and vary over short distances, so one plane might experience conditions far worse than another.

Ned Raggett, Saturday, 6 June 2009 14:08 (fourteen years ago) link

approximately the same route

meaning what? there's no question that it flew through a large area of cells in the intertropical convergence zone. the question is which cells it flew between/into/over - did the other planes go through the same ones at the same time?

Reggiano Jackson (gabbneb), Saturday, 6 June 2009 14:11 (fourteen years ago) link

apparently there's a lot of academic support for the notion that the Atlantic ITCZ responds to ENSO signs (among a lot of other things) in late Spring (the Southern Fall), largely in May. i don't see support in a very cursory search, but wikipedia says it can be correlated with ENSO cool to neutral conditions (as exist now) and disappears with El Nino (to which we are probably transitioning).

Reggiano Jackson (gabbneb), Saturday, 6 June 2009 14:39 (fourteen years ago) link

OK this is the kind of stuff that could turn me into a conspiracy theorist.

Kevin John Bozelka, Thursday, 11 June 2009 10:41 (fourteen years ago) link

woah

Ant Attack.. (Ste), Thursday, 11 June 2009 10:42 (fourteen years ago) link

urgh

baaderonixx, Thursday, 11 June 2009 12:31 (fourteen years ago) link

Cars with Italian plates veering off the road near Kufstein are about as mysterious and uncommon as dog poop on a city sidewalk.

Three Word Username, Thursday, 11 June 2009 12:46 (fourteen years ago) link

it was the Bermuda Triangle

Reggiano Jackson (gabbneb), Thursday, 11 June 2009 13:14 (fourteen years ago) link

The Bermuda Triangle is nowhere near there. Unless it got lost, of course. Which would be, like, wow, man.

StanM, Thursday, 11 June 2009 15:01 (fourteen years ago) link

no it is very well known that the Bermuda Triangle is centered over Austria

Reggiano Jackson (gabbneb), Thursday, 11 June 2009 15:07 (fourteen years ago) link

two weeks pass...

This day has too much news in it already!

Ned Raggett, Thursday, 25 June 2009 22:56 (fourteen years ago) link

Yeesh:

A French investigator says Air France Flight 447 did not break up in flight but plunged vertically into the Atlantic Ocean.

Alain Bouillard, leading the investigation into the June 1 crash for the French accident investigation agency BEA, also says life vests found among the wreckage of the plane were not inflated.

Ned Raggett, Thursday, 2 July 2009 16:50 (fourteen years ago) link

Fallows has a post with thoughts from two readers on what might have occurred, including one from a pilot who encountered what might have been a similar situation. The sequence as suggested:

1. The plane got into a thunderstorm, where the updrafts and downdrafts are extremely powerful and where unusual conditions apply -- including the possibility of the plane being covered with ice;

2. Storm-related ice may have blocked the pitot tubes -- small probe devices that measure the force of the oncoming air. When compared with other data, pitot data lets the pilot derive the plane's airspeed. If the small openings at the front of the pitot tubes are blocked by ice or anything else, the pilots don't know the plane's speed, which is the most important single piece of info for keeping an airplane under control;

3. When the sophisticated, computerized, highly-redundant autopilot system detected bad readings from the pitot tubes -- or readings from some of the tubes that differed from the others -- it disconnected the autopilot and returned control to the captain. This is a safety measure to prevent an automated system from following bad data all the way to the ground;

4. When the human pilot took over, the absence of the autopilot gave him full control over the airplane's rudder. The autopilot and computerized guidance system included a "yaw damper," which limited sudden or severe movements of the rudder (which place strain on an airplane's tail);

5. While in the storm under manual control, the violent forces on the plane and perhaps movements of the rudder may have broken off the tail and sent the airplane down.

As the reader sums up the sequence:

"My personal opinion about what happened is as follows - one or both pitot tubes iced over, which means that the air data computers are getting airspeed indications more than 5 knots apart. In that case, the autopilots disconnect, and the aircraft reverts to basic flight mode - which may be thought of as a limp mode - and among other things the yaw damper is turned off. Now the pilot has full rate authority on the rudder and the stab. The airbus has a known weak tail [he cites this Wikipedia entry about the crash of American Airlines flight 587] -- they got into some turbulence and it broke off. the airplane tumbled and came apart... which explains no mayday call and the diagnostic message about loss of cabin pressure.

"I note with interest that the rudder on both 447 and AA 587 were both found intact."

Ned Raggett, Thursday, 9 July 2009 20:37 (fourteen years ago) link

http://www.counterpunch.com/garcia07012009.html"">I can one up you on stomach churning detailed speculation, from a aviation physicist 3 weeks ago

1. Gradual icing reduces the inlet areas of all 3 Pitot probes, uniformly. The angle-of-attack (AOA) sensor is a weathervane attached to a horizontal shaft at the side of the aircraft near its nose. The AOA measures the angle between the airflow and the longitudinal axis of the airplane. Assume the AOA vane also ices, swiveling gradually to higher angle. Both effects cause a gradual speed-up on auto-thrust (the airplane version of cruise control).

2. Pitot icing blockage becomes severe and non-uniform; a 50 kph discrepancy between probes is recorded.

3. The Pitot system fails at 2:10 UTC, auto-pilot and auto-thrust go to the "alternate" mode, which is comparable to the combination of automatic and manual control used on the Boeing 777. The rudder is no longer limited to only 5 degrees of deflection because the flight control programming presumes the pilots would need the freedom of greater motion to perform recovery maneuvers. The shift to alternate mode is not a failure of the automated system, but the response programmed for the situation.

4. The speed window ("coffin corner") at 35,000 feet is 757-913 kph (Mach 0.72-0.86). The pilots had set auto-thrust to maintain a speed near 881 kph (Mach 0.83). They are fooled into thinking their present speed is about 834-850 kph because of the last presumably good speed readings they observed prior to the warnings of 2:10 UTC. They assume the current power settings are for this speed, when actually the speed has crept up to 913-929 kph without notice.

5. Arriving at excessive speed causes 1.3 g shaking, which is self-induced but they interpret as atmospheric turbulence. If they were really cruising at 881 kph (Mach 0.83) and had encountered turbulence, then they should have reduced their speed to 819 kph (Mach 0.77). Assuming this is their situation, they try reducing speed by using the 'no airspeed data' flying procedure. They throttle back a bit, guessing at a 16-32 kph reduction based on the combination of the AOA sensor (which is iced and showing too high an angle) and the power setting. They assume the power setting accounts for a higher headwind than is the case (because it seems high), and they want to be assured of avoiding a stall, so they actually only reduce power to slow down by 16 kph to 897-913 kph (a good thing, too!), imagining they are now flying at 819-834 kph.

6. The AOA system fails at 2:11 UTC. Either the vane stalk is frozen into position, or the 1.3+ g shaking from excessive speed has caused too many erratic and wide swings of the vane, and it has faced broadside into the flow and become heavily balled up in ice. So, speed guessing is now nearing impossible. They are at about 897-913 kph when they should be 819 kph, assuming turbulence; and there may actually be some real turbulence as well. The majority of the "turbulence" they are experiencing is really the buffeting effect of excessive speed caused by the erratic shock and pressure jumps along the fuselage, wings, tailplanes, vertical stabilizer and rudder during transonic cruise. At 2:12 UTC, air data discrepancies are flagged; perhaps icing and transonic flow (shock wave effects) prevent other measurements such as of total air temperature.

7. Swept-wing transports have a tendency to swing back and forth in a lateral rolling motion called a Dutch Roll. A combined yaw and roll make the nose point left and the right wing dip (or go into the opposite combination), which is countered by the ailerons to level the wings, and the rudder to steer back on track. But, the lag in response swings the plane past straight and level into a nose pointing right and the left wing down attitude. The Dutch Roll is an oscillation between control inputs and lateral swings. Part of the automatic flight control system is a yaw damper, a slight shifting of the rudder back and forth as needed to keep the airplane straight and level.

At 2:13 UTC, AF447 was flying at excessive speed, the surrounding atmosphere may have exacerbated flight instability by being turbulent, and the flight control system no longer limited rudder deflection to 5 degrees. Yaw damping became ineffective. Because of the 1.3+ g shaking and the shock-induced flow disruptions of transonic cruise, the responses to the deflections of the ailerons and rudder became erratic, and an amplifying Dutch Roll oscillation sets in.

8. A big tail swing right is countered by a rightward rudder deflection of greater then 5 degrees, and the combined moment (torque) to the right and the air resistance against the vertical fin (to the left) puts a greater then 2.5 g load on the vertical stabilizer, and snaps the entire fin-plus-rudder assembly off to the left.

9. The loss of the vertical stabilizer releases resistance to the rightward moment, and an instant angular acceleration of 3.5 to 5 g, or more, swings the tail rightward.

10. The rear pressure bulkhead in the fuselage has a pressure force directed rearward, from the pressurized cabin and cargo hold toward the unpressurized tailcone. During a rightward tail swing, this force points to the back and rightward. At the same time, the rightward moment acting on the tailcone puts a lateral force on it, which is to the left and increasingly back during the rightward swing. With the tail wagged right, the rear bulkhead is tilted forward on right side, backward on left side, and the resultant force on it is more or less straight back. This causes a rotation of the bulkhead so as to open its seam on the right side of the fuselage, breaching the pressure seal and allowing the cabin to de-pressurizes rapidly.

11. An automatic signal sent at 2:14 UTC announces cabin de-pressurization.

12. The unimpeded rightward tail swing sweeps the right wing square into the airstream while the airplane is near its maximum speed, about 881-913 kph (Mach 0.83-0.86). This swings the right wing leading edge forward at a higher relative speed than Mach 1, so it moves forward of the leading shock.

13. The shock extends along the middle chord of right wing, now angled more squarely into the flow, and causes flow separation behind it, with a complete loss of lift; shock stall.

14. The plane's nose is yawed left in a rightward tail swing, the right side losses lift force while left keeps it, and the result is a sudden strong moment causing a rotation (perhaps 5 g) about the plane's longitudinal axis: left side/wing up, right side/wing down.

15. The excessive right twist of the fuselage causes engine pylons to fail. Engine number 1 (left side) breaks off -- cutting electrical power -- rotating in an upward swing right, smashing into the bottom of the left wing near the wing root and trailing edge, and then smashing into and through the left side of the fuselage just past the left wing root.

16. Engine number 2 (right side) swings up and right to twist bottom-up through the right wing leading edge, outboard of the engine location, and the outer wing then snaps off by rotating about the rip, with a tip upward motion. Air blast through its underside blows off upper surface spoilers like the one recovered by the Brazilian Navy.

17. The tailplanes probably snap off at the same time as the engines.

18. The reduction in mass on the right side, relative to the left, gives a boost (less inertia and drag) to the rightward roll underway.

19. The rear section of fuselage twists off from its remaining right side connection with a leftward swing, and the tailcone section separates from it, tearing off from the right to left side of its pressure bulkhead seam.

20. The interior of the fuselage originally behind the wings experiences an air blast through its forward open section toward the tail end; many panels and weakly attached objects are blown out.

21. The still intact assembly of forward fuselage plus right wing stub plus left wing continues to roll completely over while also yawing back and forth, for several cycles. The wing experiences lift forces that make the entire body spin, like a maple seed pod, whose single airfoil causes it to gyrate during a swinging descent.

22. The angular force at the left wingtip and at the cockpit end of the fuselage are greatest, so the fuselage snaps apart aft of the cockpit and also ahead of the left wing root, while an outboard length of left wing also snaps off.

23. The sections of the airplane that fall are: the vertical stabilizer with its rudder (recovered by the Brazilian Navy), the tailcone (with or without tailplanes), the rear cabin section (probably further ruptured during descent by air blast), the engines, the right wing outboard of the number 2 engine location; then after a bit of 'maple seed' auto-rotating helicopter flight as a unit: the cockpit section of the forward fuselage, another length of the forward fuselage, an outer length of left wing and the wing root section of the fuselage with the remaining wing stubs.

24. The four sections of the cabin (the tailcone is a fifth fuselage section) guessed here might experience further air blast rupture and content ejection as they descend; and the large structural remnants hitting the water would then suffer collision fragmentation.

Derelict, Thursday, 9 July 2009 21:01 (fourteen years ago) link

three weeks pass...

Hope sinks as 2 ships stop Air France Flight 447 black box hunt

Elvis Telecom, Tuesday, 4 August 2009 00:46 (fourteen years ago) link

The comments on that thing!

Ned Raggett, Tuesday, 4 August 2009 01:04 (fourteen years ago) link

surely it's not that hard to design a black box that floats.

ken "save-a-finn" c (ken c), Tuesday, 4 August 2009 01:12 (fourteen years ago) link

one month passes...

Bosses blame the pilots for Air France 447 disaster

It is over three months since Air France Flight 447 crashed into the Atlantic off Brazil. They have not found the flight recorders but the elements are falling into place. It became clear this week that Air France, the Airbus corporation and the BEA, the French state accident investigators, would like to blame the crew for the crash of the A330 Airbus, which had 228 souls aboard.

Pilots are angry over what they say is an attempt to make them scapegoats for a failing in the Airbus design. Families of the victims are also accusing the authorities of obfuscation. A lot is at stake. I have been talking to Air France pilots. Gérard Arnoux, an Airbus A320 captain with the company, told me: "They are trying to blame the pilots. They do not want the truth." Arnoux is active in the Union of Air France Pilots (SPAF), a militant offshoot from the company's branch of the mainstream National Union of Airline Pilots (SNPL)

Thanks to data transmitted in the final minutes, we know the outline of what happened to AF447 as it cruised through a storm en route from Rio to Paris. The sequence began with the pitot tubes, the sensors on the outside of the plane which measure the pressure of the oncoming air, thus the plane's airspeed. The pitots failed on AF447, probably because of ice. The flawed speed data upset the electronic flight system, leaving the pilots to hand fly the plane with partially automated controls. They were unable to keep control and the plane dropped at high speed from cruising altitude, hitting the ocean in upright attitude and in one piece, according to evidence from the wreckage.

The argument centres on the question of whether the pilots should have been able to control the handicapped plane. A series of similar -- but apparently less severe -- pitot failures have hit Airbuses over the past decade, it has emerged (Since the crash, the European and US aviation authorities have ordered new pitot tubes on all long-haul Airbuses). In the previous incidents, which did not last long, the crew recovered their planes. A system failure of this type in a storm at cruising altitude would leave the crew with tiny margin to manoeuvre. In this so-called 'coffin corner', a few dozen knots too slow and the plane stalls. A few dozen knots too fast and it will overspeed and dive.

The accident investigators and Airbus say the crew should have been able to recover the plane. Paul-Louis Arslanian, chief investigator, said the pitot failure was a "factor but not the cause" of the crash. Last Monday, he suggested that Air France had not sufficiently trained its pilots in how to handle high-altitude malfunctions of this sort.

On Friday, Thomas Enders, the CEO of Airbus, told le Parisien newspaper: "The pitot probes may have been a factor in explaining the crash. They were not the principal reason." Air France is trying to finger its its pilots, according to Christophe Guillot-Noel, who heads an association of AF447 victims' families. Pierre-Henri Gourgeon, the airline boss, has told them that faulty decision-making is suspected, said Guillot-Noel, whose brother was killed in the crash.

Interestingly, Air France has just started giving special simulator training to all its Airbus crew to teach them how to handle high altitude failures in speed data. Pilots told me that they had never previously been given hands-on instruction in this field. "No appropriate safety manoeuvre exists to cope with this very dangerous situation in the coffin corner and no training was given to Air France pilots in the simulator," Captain Arnoux has just told me by e-mail. All the evidence points to the big Airbus entering a flat spin -- a pilot's absolute nightmare. The crew would have been unable to recover because the computer, having switched to so-called "alternate law", would have prevented them from deflecting the rudder enough to halt the turns, said Arnoux.

"Airbus, as well as the BEA, have obvious interests in minimizing the pitot faults as they have not demonstrated a proactive attitude since the very serious incidents which occurred on the Airbus fleet since the late 1990s," he said.

There are other points of view. James Healy-Pratt of Stewarts Law, the London firm which is representing victims' families, tells me that they have just carried out trials on a simulator and found that the pilots recovered the Airbus each time they tried. The only failure was when the pilot at the simulator controls did not realise that there was a flaw in the speed readings. Simulators cannot recreate the full violence of heavy turbulence of the kind suffered by AF447, he noted. Healy-Pratt, who is a pilot as well as lawyer, also says that questions have to be asked about the crew's failure to divert around the storm and their skills at interpreting their weather radar. Air France will face a bill of some 450 million dollars for the disaster, his firm estimates.

Without the black box recorders, no firm conclusion may ever be reached. They are about to to start a third search of the mountainous ocean floor off northeast Brazil. Airbus is contributing several million euros to the effort. Arslanian likens the task to hunting for a shoe-box at night in Switzerland using a single flash light.

One result of the disaster has been a push to replace onboard flight recorders, invented over 40 years ago, with real-time data links. Enders said Airbus is working on a system to transmit key parameters, as well as video from the cockpit, via satellite, rather than storing the data in metal boxes that can be lost at the bottom of the ocean. My Air France friend said the pilots have no objection to this "provided this data cannot be used against crew handling of the aircraft in any way and be used for disciplinary reasons."

Elvis Telecom, Sunday, 6 September 2009 04:06 (fourteen years ago) link

three months pass...

Another Air France jet hits trouble near AF447 crash site

December 11, 2009 -- Updated 1342 GMT (2142 HKT)
Paris, France (CNN) -- French investigators said they are looking into problems encountered by an Air France jet last month in nearly the same spot over the Atlantic where another Air France jet mysteriously crashed in June.

Air France flight 445 was flying from Rio de Janeiro, Brazil, to Paris, France, the night of Nov. 29 when it encountered the problems, the French accident investigation agency, BEA, said in a news release this week.

It is the same route taken by Air France flight 447 when it went down in the Atlantic Ocean in stormy weather June 1, killing all 228 people aboard. The investigation agency has not established the cause of the crash, and large parts of the plane -- including both flight recorders -- have never been found.

"The analysis of what happened could lead to complementary explanations about the accident of flight AF 447," the investigation agency said.
Flight 445 encountered "severe turbulence" about four hours after takeoff on Nov. 29, forcing the pilots to descend, Air France said in a statement after the flight.

The crew sent out an emergency radio message to indicate it had left its flight level, Air France said.

The flight, with 215 people aboard, "continued normally" after half an hour of moderate to severe turbulence, the airline said.

Elvis Telecom, Saturday, 12 December 2009 09:02 (fourteen years ago) link

-----
The French BEA has issued an interim report on the loss of the Air France A330 over the South Atlantic that includes a summary of the conclusions to far:

- Parts were recovered from all over the aircraft, ranging from the nose radome cover to parts of the spoilers, ailerons, cabin, and elevators.
- Aircraft probably impacted water intact.
- Flaps were retracted.
- An analysis of damage to the cabin crew seats that were recovered (3/11 seats) indicated they were not occupied at impact.
- Life vests were still in their containers.
- O2 masks were not deployed, indicating no decompression above 14,000 ft.
- Injuries to passengers (spine compression and fractured pelvises) plus damage to aircraft parts indicates a high rate of descent at impact.
- Attitude of aircraft at impact slightly nose up, with a small bank angle and minimal side slip.

They intend making further attempts to recover the aircraft and FDRs starting in the new year.

An English version of the interim report is available here (PDF):

http://www.bea.aero/docspa/2009/f-cp090601e2.en/pdf/f-cp090601e2.en.pdf

The report includes a detailed description of the maintenance messages that were automatically sent by the aircraft, plus discussion of the pitot tube problems seen on other aircraft.
-----

Elvis Telecom, Friday, 18 December 2009 21:02 (fourteen years ago) link

can you put that in english for me ET?

it landed nose slightly up + small bank angle + no slip + no masks or vests deployed + crew was not braced for emergency landing = surprise turbulence rendering the aircraft inoperable and fell out of sky like a brick?

quiet and secretively we will always be together (Steve Shasta), Friday, 18 December 2009 21:20 (fourteen years ago) link

good advice for future oversea flights: don't fly into monstrous storms in the middle of oceans.

you are wrong I'm bone thugs in harmon (omar little), Friday, 18 December 2009 21:24 (fourteen years ago) link

can you put that in english for me ET?

it landed nose slightly up + small bank angle + no slip + no masks or vests deployed + crew was not braced for emergency landing = surprise turbulence rendering the aircraft inoperable and fell out of sky like a brick?

Cribbing from the interim report PDF, it looks like the plane impacted the water as if you held a model airplane stationary in the air and then just dropped it. Compression fractures in the area of the tail topped off at 36g so it was definitely brick-like in it's descent. We just don't know how it got there.

Elvis Telecom, Saturday, 19 December 2009 01:15 (fourteen years ago) link

don't fly into monstrous storms in the middle of oceans.

Corollary to that... you may have flown through big storms before but in the end Mother Nature always holds the trump card.

Elvis Telecom, Saturday, 19 December 2009 01:16 (fourteen years ago) link

one year passes...

New wreckage found.

Ned Raggett, Monday, 4 April 2011 15:25 (thirteen years ago) link

In fact it's more than that -- seems like they've found the fuselage and a number of bodies, though they're not sure about the black boxes yet.

Ned Raggett, Monday, 4 April 2011 15:27 (thirteen years ago) link

for some reason it's really freaky to me, the idea of these bodies & this plane just having been floating around in the atlantic all this time

J0rdan S., Monday, 4 April 2011 17:41 (thirteen years ago) link

well, maybe not floating, but you get what i'm saying

J0rdan S., Monday, 4 April 2011 17:41 (thirteen years ago) link

three weeks pass...

Part of the black box found

Search teams have found a part of the crucial "data recorders" of the Air France flight which crashed into the Atlantic Ocean in 2009, says France's Bureau of Investigation and Analysis (BEA).

The orange-colored recorder 'chassis' was found on Wednesday during the second day of an operation which also hopes to retrieve bodies from the wreckage site.

All 228 people aboard the Airbus A330 Flight 447 from Rio de Janeiro to Paris were killed.

The find - which comes more than three weeks after search teams found the tail section of the aircraft -- does not include the "memory unit" which holds the recorded data that could eventually help investigators determine the cause of the crash.

Martine Del Bono, a spokeswoman for the Paris-based BEA says there is a good chance the memory unit, which records any instructions sent to the aircraft's electronic systems, will still hold retrievable data.

Stockhausen's Ekranoplan Quartet (Elvis Telecom), Friday, 29 April 2011 00:23 (twelve years ago) link

Here's hoping. Grim comfort at best even so.

Ned Raggett, Friday, 29 April 2011 00:32 (twelve years ago) link

Big new NYT Magazine piece up:

http://www.nytimes.com/2011/05/08/magazine/mag-08Plane-t.html

Ned Raggett, Wednesday, 4 May 2011 19:45 (twelve years ago) link

Also, both the data and cockpit voice recording parts have been recovered.

Ned Raggett, Wednesday, 4 May 2011 19:51 (twelve years ago) link

Air France 447: How scientists found a needle in a haystack

This year's search was the fourth attempt to find the wreckage of Flight 447, and it probably would have been the last, even if the plane hadn't been found. Previous searches had been done by boat, mini-sub, and—back when there was still a chance of catching the audio signal from the plane's black boxes—underwater acoustic sensors. In 2010, scientists from the Woods Hole Oceanographic Institute were brought in to search for the crash site using autonomous robot subs. Still nothing had been found.

On March 22, 2011, the Woods Hole team set out from Brazil to try again. They'd barely been at the search location for a week when they found what they were looking for. On April 3, researchers spotted the plane's debris field, 13,000 feet down, smack in the middle of a massive underwater mountain range.

The success was astounding, but I wanted to know ... what made this search different from the others? What could the team from Woods Hole do that other groups could not, and how did their system work? To find out, I spoke with Mike Purcell, senior engineer with Woods Hole, and the chief of sea search operations for the mission.

Stockhausen's Ekranoplan Quartet (Elvis Telecom), Saturday, 7 May 2011 19:40 (twelve years ago) link

All flight data and cockpit conversations recovered. We should all know the basics of what happened in a couple of months.

Ned Raggett, Monday, 16 May 2011 14:28 (twelve years ago) link

Preliminary Findings Suggest Pilot Error in Air France Crash

The pilots of an Air France jet that crashed into the Atlantic Ocean two years ago apparently became distracted with faulty airspeed indicators and failed to properly deal with other vital systems, including adjusting engine thrust, according to people familiar with preliminary findings from the plane's recorders.

The final moments inside the cockpit of the twin-engine Airbus A330, these people said, indicates the pilots seemingly were confused by alarms they received from various automated flight-control systems as the plane bucked through some turbulence expected on the route from Rio de Janeiro to Paris but also faced unexpectedly heavy icing at 35,000 feet. Such icing is renowned for making airspeed-indicators and other external sensors unreliable.

Ultimately, the crew failed to follow standard procedures to maintain or increase thrust and keep the aircraft's nose level, while trouble-shooting and waiting for the airspeed sensors and related functions to return to normal, according to these people.

Slated to be disclosed by investigators on Friday, the sequence of events captured on the recorders is expected to highlight that the twin-engine jet slowed dangerously shortly after the autopilot disconnected. The pilots almost immediately faced the beginning of what became a series of automation failures or disconnects related to problems with the plane's airspeed sensors, these people said. The crew apparently had difficulty sorting out the warning messages, chimes and other cues, while monitoring essential displays showing engine power and aircraft trajectory.

The pilots were never trained to handle precisely such an emergency at high altitude, according to safety experts and a previous report by France's Bureau d'Enquetes et d'Analyses, which is heading up the investigation. All 228 people aboard died in the accident.

The senior captain, Marc Dubois, appears to have been out of the cockpit for a routine rest break when the fatal chain of events started, according to safety experts familiar with the details. But according to one person close to the probe, the cockpit-voice recorder suggests that once problems cropped up, he may have rushed back to the cockpit to join the other two pilots of Air France Flight 447.

Though Friday's announcement won't provide final conclusions or specific causes, investigators believe Air France never trained its pilots to cope with such automation problems in conjunction with a high-altitude aerodynamic stall, an emergency when the wings lose lift and the plane quickly becomes uncontrollable.

Stockhausen's Ekranoplan Quartet (Elvis Telecom), Monday, 23 May 2011 21:14 (twelve years ago) link

must be horrendous listening to the last few seconds of that cockpit recorder but then i guess i am morbidly fascinated enough to be thinking about it at all wargh

school of seven bellhops (blueski), Monday, 23 May 2011 21:47 (twelve years ago) link

Its always frightening to think that what keeps jet planes in the air is really just their forward momentum. And if that stops...

The man who mistook his life for a FAP (Trayce), Monday, 23 May 2011 21:58 (twelve years ago) link

It's their job. If people like this or people who work at morgues etc wouldn't be able to disconnect they would be working somewhere else. xpost

StanM, Monday, 23 May 2011 22:01 (twelve years ago) link

Yeesh...

3.5 minutes of terror: Air France crash dropped at 10,000 feet a minute

Passengers on an Air France flight plunged for three and a half minutes before crashing into the Atlantic, killing all 228 on board, after it lost speed and stalled while the main pilot was resting, the first evidence from black boxes has found.

AF447's junior pilot battled to save the Rio de Janeiro to Paris flight, as the second pilot tried to rouse the captain shortly after the plane had begun its fateful descent in a tropical storm.
According to flight recorder data, the younger of the two men, Pierre-Cédric Bonin, 32, angled the jet's nose higher, a position the aircraft maintained until its final impact, after inconsistent speed readings confused the plane.

Aviation experts asked why the pilot kept giving nose-up inputs when the plane was in a stall, given that one normally puts the nose down to recover speed and regain control.

All 228 people on board – including crew – died after the Airbus hurtled into the Atlantic at a speed of 180 feet a second in the worst disaster in Air France's history.
David Robert, 37, the second pilot, had begun anxiously calling for their more experienced captain after autopilot suddenly cut out four hours after take-off. Captain Marc Dubois, returned a minute and a half later, but never retook control of the plane – instead leaving the flying to his assistants.

...

Releasing preliminary findings yesterday, France's accident investigation office, the Bureau d'Enquêtes et d'Analyses (BEA), said they showed the co-pilots decided to turn slightly to the left to avoid a zone of turbulence, warning cabin crew to expect the plane to "move around" in forthcoming turbulence.

Two minutes later the autopilot disengaged, the instruments began showing that the speed had slowed dramatically and the engine stall warning began to sound.

The BEA said the pilots received inconsistent speed readings for around a minute, with one pilot saying: "We have no valid indications." This suggests there was a problem with the plane's speed sensors, so-called Pitot tubes that an earlier preliminary investigation had indicated might have contributed to the crash.

The pilots responded by pulling up the nose of the aircraft, triggering a stall warning in the cockpit.

According to the BEA, the co-pilots continued to increase the angle of climb, rising rapidly from 35,000 feet to 37,500 feet. When a third stall warning sounded, they continued to pull back on the controls with the engines set to full thrust and rose to about 38,000 feet, where the plane entered a stall.

With the plane's nose still pointed up about 15 degrees, the jet began falling at about 10,000 feet a minute, rolling left and right. Almost one minute into the stall, the pilots had reduced engine thrust and tried pushing down on the controls to lower the nose.

Airspeed indications returned and the alarm sounded again as the stalled aircraft picked up some speed, but the plane never recovered.

I'm not easily scared, but a 10,000 feet a minute drop squicks the hell out of me.

Stockhausen's Ekranoplan Quartet (Elvis Telecom), Friday, 27 May 2011 22:11 (twelve years ago) link

well, i guess it's no fun, but if it's any consolation they may not even have realized

http://www.guardian.co.uk/world/2011/may/27/air-france-crash-inquiry

Despite what the pilots must have been going through in the cockpit, the pitch attitude remained fairly constant throughout so the passengers would not have sensed something was seriously wrong. They would have felt mild buffeting of the stalled airflow over the wings and the initial sinking feeling. That's all.

caek, Friday, 27 May 2011 22:16 (twelve years ago) link

3.5 minutes is a long time, in that situation, i bet i felt a lot longer.

I know it's a minor thing, but your ears can hurt on descent, i wonder if it was in issue for those aboard 447?
I can picture furious boiled sweet sucking to prevent ear popping.

Sorry :/

not_goodwin, Friday, 27 May 2011 22:21 (twelve years ago) link

three weeks pass...

Long Aviation Week article on the results so far.. The takeaway is that pilot training hasn't really kept up with the systems management duty required by modern airplanes.

“We will learn a lot from this accident,” says William R. Voss, president and CEO of the Flight Safety Foundation, who believes that AF447 should have fundamental consequences for the content of pilot training globally. “We are still training for the engine fire at V1, but the complexity of automated systems has grown. We have to develop crews that can deal with incidents such as QF32,” the Qantas Airbus A380 that suffered an uncontained engine failure after takeoff in Singapore on Nov. 4, 2010, and returned to the airport severely damaged.

Voss argues that AF447 would not have crashed if the aircraft had been of an older generation. “Highly automated aircraft have saved many lives, but they fail differently than aircraft of 20 years ago,” he says. He sees it as a “failure of the industry” that pilot training has not kept in step with the latest aircraft technologies. He also argues for improved upset recovery training, as “we are not explicitly training that” and the AF447 A330 “seems to have had pitch-and-roll authority all the way down to the water.”

Stockhausen's Ekranoplan Quartet (Elvis Telecom), Saturday, 18 June 2011 03:44 (twelve years ago) link

one month passes...

Was scanning that earlier. Sounds like a compounding of a lot of problems in the end, but if the core was that the pilots weren't trained properly...

Ned Raggett, Friday, 29 July 2011 14:37 (twelve years ago) link

in some ways much more disturbing than simple mechanical failure - how many pilots out there are qualified to deal with that kind of situation? air travel is a growing industry in many developing countries, most notably China where many pilots have been caught with fake licenses.

flop's son (dayo), Friday, 29 July 2011 14:45 (twelve years ago) link

pilots should probably know how to fly the plane manually at high altitude, yeah

J0rdan S., Friday, 29 July 2011 16:52 (twelve years ago) link

The part that scared me was that there is no indicator in the cockpit that shows the "angle of attack" - a key piece of information in that situation.

o. nate, Friday, 29 July 2011 18:25 (twelve years ago) link

"Safety experts say those procedures are now essentially the same for both aircraft makes, regardless of altitude, and instruct pilots in the first instance to lower the nose of the aircraft and, if necessary, to reduce thrust to avoid excessive acceleration.

Previously, the standard procedure for an approaching stall at low altitude was to raise the nose by around 5 degrees and to maintain full thrust. "

Why was the previous method for overcoming stalls pointing the nose up? Unless by "low altitude" they mean in the very early stages of a flight, where I guess you can't nose down for long enough to build up speed.

nickn, Friday, 29 July 2011 18:55 (twelve years ago) link

eleven months pass...

Final report from the French crash investigators is out

LE BOURGET, France — French investigators’ final report on the 2009 crash of an Air France jet that killed 228 people portrays a cockpit rapidly consumed by confusion and unable to decode a welter of alarms to determine which flight readings could be trusted, with the pilots’ apparent reliance on a faulty display cementing the plane into its fatal stall.

The report, released Thursday by the Bureau of Investigation and Analysis, concluded that the errors were the outcome of a confluence of factors beyond the competence of any individual pilot. The investigators stood by earlier findings that the pilots had not been adequately trained to fly the aircraft manually in the event of equipment failure or a stall at high altitude.

There was a “profound loss of understanding” among all three pilots of Air France Flight 447, an Airbus A330 en route to Paris from Rio de Janeiro, about what was happening after ice crystals threw off the plane’s airspeed sensors and the autopilot disconnected, the report said. The pilots then struggled to control the plane manually amid a barrage of alarms, a situation further confused by the faulty instructions displayed by an automated navigational aid called the flight director.

“The crew never understood they were in a stall situation,” the report said, “and therefore never undertook any recovery maneuvers.” It said further that “the combination of the ergonomics of the warning design, the conditions in which airline pilots are trained and exposed to stalls during their professional training and the process of recurrent training does not generate the expected behavior in any acceptable reliable way.”

The report offered an answer to a central puzzle: the consistent and aggressive “nose up” inputs by the pilot at the controls, which added to the loss of lift. Pilots are normally trained to point the nose of the aircraft down in a stall to regain speed.

The report said that the readings being gathered by the automated flight director — which uses cross hairs superimposed over an artificial horizon to indicate the required positioning of the plane — would have resulted in repeated calls for the plane’s nose to be lifted.

One aviation expert was troubled that the pilots did not appear to have the skills to start from the basic observation that airspeed indicators were giving conflicting readings and anticipate which of their flight readings — like that of the flight director — would therefore be untrustworthy.

William R. Voss, president of the Flight Safety Foundation in Alexandria, Va., said: “We are seeing a situation where we have pilots that can’t understand what the airplane is doing unless a computer interprets it for them. This isn’t a problem that is unique to Airbus or unique to Air France. It’s a new training challenge that the whole industry has to face.”

Elvis Telecom, Thursday, 5 July 2012 23:21 (eleven years ago) link

one year passes...

Air Crash Investigations gets to the AF447 crash. In the last eight minutes I'm shouting at the co-pilot "GET YOUR SHIT STOWED AND PUSH FORWARD ON THE FUCKING STICK!"

"we're searching an area the size of Switzerland - including the Alps"

https://www.youtube.com/watch?v=NTuagG3aW_g

Elvis Telecom, Monday, 20 January 2014 01:13 (ten years ago) link

seven months pass...

New deep story on the crash and questions of air safety in general

http://www.vanityfair.com/business/2014/10/air-france-flight-447-crash

Ned Raggett, Thursday, 18 September 2014 15:23 (nine years ago) link

No crisis existed. The episode should have been a non-event, and one that would not last long. The airplane was in the control of the pilots, and if they had done nothing, they would have done all they needed to do.

William Langewiesche is the best.

Plasmon, Monday, 22 September 2014 07:19 (nine years ago) link


You must be logged in to post. Please either login here, or if you are not registered, you may register here.