[42153] in North American Network Operators' Group

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

RE: Analysis from a JHU CS Prof

daemon@ATHENA.MIT.EDU (John Fraizer)
Thu Sep 13 18:54:57 2001

Date: Thu, 13 Sep 2001 18:41:51 -0400 (EDT)
From: John Fraizer <nanog@Overkill.EnterZone.Net>
To: Matt Levine <matt@deliver3.com>
Cc: "'Joel Baker'" <lucifer@lightbearer.com>, nanog@merit.edu
In-Reply-To: <001501c13ca1$c5c1d3e0$6601a8c0@m00se>
Message-ID: <Pine.LNX.4.21.0109131834330.29075-100000@Overkill.EnterZone.Net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu



On Thu, 13 Sep 2001, Matt Levine wrote:

> 
>  
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> It's a moot point anyway, it's pretty clear the hijackers had flight
> training of some sort AND were well organized, and would be familiar
> with the steps that the pilots would take.
> 
> 
> Regards,
> Matt
> 

Since most commercial aircraft have multiple transponders, it should be
assumed that if an aircraft stops squacking, something is BAD
WRONG.  Beyond this, the ability of the flight crew (any of them) to push
a "panic" button that would cause the transponder to squack a
predetermined distress code may me a good measure to implement.  This
"Panic" button should NOT provide any visible confirmation in the
flight-deck instrumentation but instead, the ATC should in some cryptic
form acknowledge the fact that the aircraft is in distress via radio
communications. (perhaps a minor heading correction that is not needed,
etc.)

---
John Fraizer
EnterZone, Inc





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