| Let's start estimating the technical challenge here (we're supposed to be techies, after all). Bandwidth: quick googling shows that a flight data recorder records between 64 and 256 12-bit words a second, i.e. 1-3 kbps. Browsing http://en.wikipedia.org/wiki/Bit_rate shows that another 2-8 kbps is needed for voice recording (from one microphone). Let's call it 10 kpbs all together. Number of simultaneous connections: there are around 20,000 (ballpark) airliners in the air at the peak time each day. Compare this to the rather old Iridium satellite network: 2400 (uplink) baud rate, 1100 calls simultaneously per satellite (of which there are 68). Not quite enough, since airplanes are not evenly distributed over the Earth or under the satellites, but not outrageously far from our requirements. Cost: several billion dollars (under 10, I think) have been invested into building the Iridium network, and their operating expenses are around 100 million per year (they are a public company). Clearly, it would not be unrealistically expensive, in the world of 500 million dollar airliners, to build and maintain a network of satellites to record all black-box voice and data in real time. |
http://en.wikipedia.org/wiki/TWA_Flight_800
http://en.wikipedia.org/wiki/China_Airlines_Flight_611
http://en.wikipedia.org/wiki/Air_France_Flight_447
Of the three, TWA flight 800 is the only one whose cause is controversial, and in-flight data transmission likely would not have helped identify the cause of that crash.
Of all the above accidents, the causes are understood and have not been repeated. In fact, the cause of Air France 447's instrumentation failure was understood before the crash - there was an an active airworthiness directive to fix the pitot icing.
Extraordinary expense with no(?) payback.