Message-
> From: amsat-bb-boun...@amsat.org [mailto:amsat-bb-boun...@amsat.org] On
> Behalf Of Paul Williamson
> Sent: Saturday, May 12, 2012 3:17 AM
> To: Thomas Doyle
> Cc: AMSAT-BB@amsat.org
> Subject: [amsat-bb] Re: TACSAT 3 Question
>
> On May 11, 2012, at 12:59
To: Thomas Doyle
Cc: AMSAT-BB@amsat.org
Subject: [amsat-bb] Re: TACSAT 3 Question
On May 11, 2012, at 12:59 PM, Thomas Doyle wrote:
> There must be a better way to detect re-entry than simply than throwing an
> unhandled exception.
>
> You guys seem to be the experts - any suggestions
On May 11, 2012, at 12:59 PM, Thomas Doyle wrote:
> There must be a better way to detect re-entry than simply than throwing an
> unhandled exception.
>
> You guys seem to be the experts - any suggestions on how to do it ?
> It seems to be related to the BSTAR drag value. Some say when the BSTAR
>
Bob and Alan,
There must be a better way to detect re-entry than simply than throwing an
unhandled exception.
You guys seem to be the experts - any suggestions on how to do it ?
It seems to be related to the BSTAR drag value. Some say when the BSTAR
drag value gets "too high" the sat has re-enter
Tom,
According to Space Track, TACSAT 3 reentered April 30th. The final Keps
will normally have huge values for drag, etc which may break the standard
predictive calculations.
73s,
Alan
WA4SCA
TIP Reports for Object 35001, TACSAT 3, (Decayed 2012-04-30), US
Report Date/Time2012-05-01
