[42348] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

An Idea

daemon@ATHENA.MIT.EDU (Grace, Terry)
Fri Sep 14 23:07:44 2001

Message-ID: <B3AA75A19260D3118F3B00902798992B023C9019@mail2.thestar.ca>
From: "Grace, Terry" <tgrace@thestar.ca>
To: "'nanog@merit.edu'" <nanog@merit.edu>
Date: Fri, 14 Sep 2001 23:06:59 -0400
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="==_03101754239356==_"
Errors-To: owner-nanog-outgoing@merit.edu


This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.


--==_03101754239356==_
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C13D93.6488323E"

------_=_NextPart_001_01C13D93.6488323E
Content-Type: text/plain;
	charset="iso-8859-1"

With all of the difficulties piecing together what occurred on the aircraft,
a friend and I were throwing around some wild ideas. One that I thought had
some merit was to have all instrumentation output, voice and even possibly
video (flight deck and cabin) continuosly downlinked to ground stations or
uplinked to satellites enroute. Yes, this would be a lot of data  even with
some type of encoding to reduce the volume and would be very costly to
implement sonsidering the computing power alone required to correlate it in
realtime, but considering that the information could saves lives, provide
early warning to all sorts of troubles, etc, IMHO, worth it. Far fethced
idea? Yes. Possible? I don't know.

------_=_NextPart_001_01C13D93.6488323E
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2650.12">
<TITLE>An Idea</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>With all of the difficulties piecing together what =
occurred on the aircraft, a friend and I were throwing around some wild =
ideas. One that I thought had some merit was to have all =
instrumentation output, voice and even possibly video (flight deck and =
cabin) continuosly downlinked to ground stations or uplinked to =
satellites enroute. Yes, this would be a lot of data&nbsp; even with =
some type of encoding to reduce the volume and would be very costly to =
implement sonsidering the computing power alone required to correlate =
it in realtime, but considering that the information could saves lives, =
provide early warning to all sorts of troubles, etc, IMHO, worth it. =
Far fethced idea? Yes. Possible? I don't know.</FONT></P>

</BODY>
</HTML>
------_=_NextPart_001_01C13D93.6488323E--


--==_03101754239356==_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Get to know us
http://www.thestar.com - Canada's largest daily newspaper online
http://www.toronto.com - All you need to know about T.O.
http://www.workopolis.com - Canada's biggest job site
http://www.torontostartv.com - Webcasting & Production
http://www.newinhomes.com - Ontario's Largest New Home & Condo Website
http://www.waymoresports.com - Canada's most comprehensive sports site

--==_03101754239356==_--

home help back first fref pref prev next nref lref last post