[Date Prev][Date Next][Thread Prev][Thread Next] - [Date Index][Thread Index][Author Index]
Re: Tracking STS is hard
- Subject: [sarex] Re: Tracking STS is hard
- From: David Bate <davebate@xxxxxxxx>
- Date: Mon, 22 May 2000 21:28:27 -0400
Up-to-date keps for STS-101 are being provided as STSNEW.TXT from Dave
Ransom's site via the DoD C-Band Radar team...
Here is the last update:
STS-101 DOCK
1 26368U 00027A 00143.79514699 .00007202 21896-9 38510-4 0 147
2 26368 51.5843 268.1427 0005289 230.5775 348.0034 15.79593359 543
Launch time for STS-101: 19 MAY 00 @ 10:11:10.0752 UTC
Earth-Fixed Greenwich State Vector:
Vector format = 117
Satellite Name: STS-101 DOCK
Catalog Number: 26368 00027A
Epoch Date/Time: 00143.79514699100
05/22/2000 19:05:00.700 UTC
EFG E: 11717510.0000000 ft
F: -15209475.000000 ft
G: -10769846.000000 ft
Edot: 7867.22999999999 ft/s
Fdot: 17014.3199999999 ft/s
Gdot: -15483.069999999 ft/s
ndot/2 (drag): 0.00007202446 rev/day^2
nddt/6: 2.18965E-10 rev/day^3
Bstar: 3.85096E-05 1/Earth Radii
Elset #: 14
Rev @ Epoch: 54.60722988932
Keplerian Elements (Amsat format):
Satellite: STS-101 DOCK
Catalog number: 26368
Epoch time: 00143.79514699
Element set: 14
Inclination: 51.5843 deg
RA of node: 268.1427 deg
Eccentricity: 0.0005289
Arg of perigee: 230.5775 deg
Mean anomaly: 348.0034 deg
Mean motion: 15.79593359 rev/day
Decay rate: 7.20245e-05 rev/day^2
Epoch rev: 54
Checksum: 315
SPACE SHUTTLE ORBITAL DATA:
These 2-line elements have been generated using Ken Ernandes' program
VEC2TLE using real time state vector data supplied by DOD C-Band Radar
Network courtesy Dave Simonson. Note that the epoch of the 2-line
elements is the same as the state vector time.
Drag and B-Star parameters are internally calculated by VEC2TLE using
a drag factor of 0.5. Rev numbers use NASA orbit numbering convention.
Dave Ransom
http://www.dransom.com
http://tie.jpl.nasa.gov/dransom/
Miles Mann wrote:
>
> Hi All:
>
> It is very difficult to track a NASA shuttle.
> The reason is because they are constantly firing
> their engines and other maneuvers.
> The kep data you have assumes there are NO engine
> maneuvers at all.
>
> If you have week old keps for ISS, then you may only
> have a tracking error of less than 1 minute.
>
> If you have 1 day old keps for the Shuttle, then
> you may be off by hours.
>
> Docking Missions:
> When the shuttle is docking with an object such as ISS
> or Hubbell, then you should track the docking object and
> not the shuttle. The ISS is in a stable orbit 229 Statute Miles up.
> The shuttle, 2 hours after launch is only 100 miles up. On just about
> every orbit the shuttle fires its engine for a little boots (until
> docking).
>
> It takes 2 days for the shuttle to climb from 100 miles to 223 miles.
> So on a ISS mission your keps for the shuttle will be junk if they
> are more than a few hours old (until the docking).
> After the docking the keps usually will not change much.
> Unless the use the shuttle to Boost the ISS to a new orbit.
>
> Keps:
> For the shuttle, get the keps from the NASA web directly or
> off the HF rebroadcast (wa3nan??). Most other web pages for the Shuttle
> keps
> will be out of date by the time they are posted. Or just track ISS.
>
> The reverse is true when the shuttle Undocks. it takes 2 days to
> de-orbit
> and thus 2 hour old shuttle keps may be useless.
>
> Miles WF1F MAREX-NA
>
> David Bate wrote:
> >
> > You may be using the latest from USSPACECOMM which looks like they are
> > still off. I would suggest using STS Update version 0020 and use the
> > F11 function and have the latest DOD c-band vectors added via Dave
> > Ransom's site.
> >
> > I tested the latest TLE's from USSPACECOMM and the STS numbers are off.
> > As soon as I updated with STSNEW.TXT it was right on the money with MCC.
> >
> > John Becker wrote:
> > >
> > > Whats wrong? ? ? ?
> > >
> > > right now STSPLUS shows STS-101 over my QTH (Missouri) and
> > > the ISS S-E of Rio de Janeiro?
> > >
> > > I have the last KEMPS posted for STS-101.
> > >
> > > ----
> > > Via the amsat-bb mailing list at AMSAT.ORG courtesy of AMSAT-NA.
> > > To unsubscribe, send "unsubscribe amsat-bb" to Majordomo@amsat.org
> >
> > --
> > David Bate (davebate@home.com)
> > Canadian Space Support Site and
> > Communications Group - CS3CG
> > Bowmanville, Ontario, Canada
> > ICQ 9344489 - NYSING 191
> >
> > Network Analyst (dbate@rci.rogers.com)
> > Rogers Communications Inc.
> >
> > http://members.home.net/davebate
> > http://welcome.to/CS3CG or http://CS3CG.welcome.to
> > ----
> > Via the amsat-bb mailing list at AMSAT.ORG courtesy of AMSAT-NA.
> > To unsubscribe, send "unsubscribe amsat-bb" to Majordomo@amsat.org
--
David Bate (davebate@home.com)
Canadian Space Support Site and
Communications Group - CS3CG
Bowmanville, Ontario, Canada
ICQ 9344489 - NYSING 191
Network Analyst (dbate@rci.rogers.com)
Rogers Communications Inc.
http://members.home.net/davebate
http://welcome.to/CS3CG or http://CS3CG.welcome.to
----
Via the sarex mailing list at AMSAT.ORG courtesy of AMSAT-NA.
To unsubscribe, send "unsubscribe sarex" to Majordomo@amsat.org
AMSAT Home