[FedCom] Re: Calif CAP over the weekend

A10382 a10382 at snet.net
Tue Apr 22 14:48:57 EDT 2008


Hi Andy,

What is the time period of each sat pass on the new 406 MHZ system ?

On the older 121.5 MHZ SARSAT system, the Air Force typically needed at 
least 2 and sometimes 3 or more passes to
narrow a fix down to a 100 sq mile area !).   Those 3 passes on the old 
system could, I believe,
take up to 4+ hours - a verrrry long time if you are the one pinned in the 
aircraft wreckage.

The new system, with registered owners, could at least get the filed route 
and start a search much quicker -- but even at that, 3 passes sounds like a 
long time.

====
Frank

._._.


----- Original Message ----- 
Sent: Tuesday, April 22, 2008 2:30 PM
Subject: [FedCom] Re: Calif CAP over the weekend


> >From what I hear, the VAST majority of these are false alerts where the
> beacon was set off accidentally, then later corrected by the owner with no
> follow-up action taken by them.  Yes, on 406 there aren't supposed to be
> false alerts anymore because (a) no alert happens unless it includes 
> digital
> data (no more plasma TVs causing a wild goose chase), and (b) the beacon 
> is
> SUPPOSED to be registered so a quick phone call may confirm whether or not
> it is real.
>
> The fact that it was a 406 beacon and the AFRCC called it off "after 3
> cycles" implies it was unregistered and had no GPS.  Two strikes down.
> AFRCC typically waits for 3 or more LEO satellite passes before even
> initiating an alert, and by then the owner might realize it and turn it 
> off.
> Then, if no signal is received for 3 satellite passes, and no registered
> owner, the AFRCC assumes it was a false alarm and calls it off.  All 
> without
> any news from the owner.  So CAP starts the search after it was shut off 
> and
> finds nothing.
> 


More information about the FedCom mailing list