Slashdot Mirror


Robots Dive Deep To Solve Airliner Crash Mystery

coondoggie writes "A small squadron of undersea robots has begun to conduct a 4-month, 3,900 square mile search of Atlantic Ocean bottom looking for the deep-sea wreck site of and black boxes from Air France Flight 447 which crashed off the coast of Brazil nearly two years ago. The Air France plane was flying from Rio de Janeiro to Paris, when for exact reasons that remain a mystery, it crashed into the Atlantic Ocean on June 1, 2009, taking with it 228 souls."

6 of 156 comments (clear)

  1. Reasons unknown?? by Ark42 · · Score: 4, Informative

    Isn't this the flight that flew right into a huge huge storm that was obscured on their radar by a smaller storm which was safe enough to fly through. As soon as the larger storm was in view, it was too late to change course and fly around it. I heard the most likely case is extreme icing of the sensors that monitor airflow, causing autopilot to disengage as the plane no longer knew its own speed. Without any way to know the current speed, the plane lost altitude and crashed, due to a small window of safe speeds that don't result in altitude loss.

    1. Re:Reasons unknown?? by bradgoodman · · Score: 4, Interesting

      I heard of this same sort of thing happening once to a plane. What happened was that the plane was just painted. During the painted process, they put masking tape over the Pitots (holes/ports used to measure air pressure). They forgot to take the tape off, and when they were in flight, the airspeed, altitude, and stall warnings all went crazy from the erronious pressure readings on the clogged/covered pitot tubes. Result was bizarre instrumentation - overspeed and stall warnings at the same time, etc. They wound up crashing from confusion. Perhaps icing in the pitot tubes were causing a similar thing here.

    2. Re:Reasons unknown?? by martyb · · Score: 4, Interesting

      Not necessarily. Even without accurate airspeed readings, the pilots should have still been able to maintain safe airspeed by setting the engines to a specific power output and trimming to a specific angle of attack. Probably pilot error (i.e. being distracted with alarms and not remembering to adjust throttle and angle....) but without that box it's hard to really know.

      Honest Question: Why in this day and age do we still have to chase down a black box? More and more airliners now provide in-flight internet connections. Couldn't they just transmit it as well as record it to the black box? TFA says this search is costing them $12.5 million. That would pay for a lot of upgrades and support for this.

      Continuous Transmission? Send all of the recorded data to both the black box and some remote data center, too. If this is too much to transmit continuously, then maybe a subset of the data? I know planes are becoming increasingly complex and automated, so there's probably loads more data that *could* be considered for transmission. Still, something is better than nothing (what we have now.) Pick some subset of the available data and send it periodically.

      Burst Transmission? Instead of a continuous stream of data, when the pilot (or plane) detects a "dangerous condition", it starts sending a high-speed burst of accumulated data, and continuously until things look "normal" again. Say the plane takes a sudden 200-foot drop in altitude. Or banks unusually sharply. Or... whatever. Just ignore the values that appear 99.9% of the time, and only trigger outside that normal range. (numbers pulled out of thin air; pick whatever works best.)

      At this point, there's nothing much to go on. Imagine if we had the last few minutes' airspeed, altitude, as well as settings for the flaps, rudder, and engine would be an enormous improvement over what we've got now. I suspect the pilots' unions might raise a concern about monitoring and potential for it to be help against them, but I could also imagine some kind of escrow mechanism where the data is sent and stored, but only to be accessed upon certain, predefined circumstances.

      Admittedly, this is quite rough. I'd like to think that there is at least some part of this which could be implemented in parallel to the provision of internet access on planes. I'd appreciate it if anyone who knows more about these things could comment on the viability of this and/or the technical limitations/challenges which I'm missing here.

    3. Re:Reasons unknown?? by jamesrt · · Score: 4, Informative

      I heard of this same sort of thing happening once to a plane. What happened was that the plane was just painted.

      The plane crash being referred to is this one: http://en.wikipedia.org/wiki/XL_Airways_Germany_Flight_888T

    4. Re:Reasons unknown?? by Slutticus · · Score: 4, Informative

      Actually, the plane transmitted quite a lot of information to AirBus HQ as it was going down, but that system (ACARS) is quite outdated i think. The last three minutes of the transmissions gave a wealth of data related to alarms and faults that were occurring (i.e. inconsistent airspeed readings, excessive vertical speed, autopilot information, etc...). It would be interesting to see how much voice data could be reliably transmitted in a situation like that.

  2. Re:Souls? by jamesh · · Score: 4, Interesting

    I'm not religious but I think the concept of the soul at the very basic level is valid. It's the program running in your head that is you. That's about where it ends though - I don't believe in any way that the program keeps running once the hardware fails, outside of the bits of your program that have rubbed off on the other people that you interacted with along the way.