T.S. Kelso
@tskelso.bsky.social
Operator of CelesTrak, the world's first source for orbital element sets and related software and educational materials.
Elevated conditions continue. Perhaps a good time to look for enhanced Northern & Southern Lights.
November 12, 2025 at 9:03 PM
Elevated conditions continue. Perhaps a good time to look for enhanced Northern & Southern Lights.
No GP data yet available, when it is see: celestrak.org/NORAD/elemen....
November 12, 2025 at 2:28 AM
No GP data yet available, when it is see: celestrak.org/NORAD/elemen....
No GP data yet available, when it is see: celestrak.org/NORAD/elemen....
November 12, 2025 at 1:58 AM
No GP data yet available, when it is see: celestrak.org/NORAD/elemen....
No GP data yet available, when it is see: celestrak.org/NORAD/elemen....
Note: For some reason, 18 SDS incorrectly shows the first 3 objects launched from JSC instead of YSLA, like the rocket body.
Note: For some reason, 18 SDS incorrectly shows the first 3 objects launched from JSC instead of YSLA, like the rocket body.
November 12, 2025 at 1:37 AM
No GP data yet available, when it is see: celestrak.org/NORAD/elemen....
Note: For some reason, 18 SDS incorrectly shows the first 3 objects launched from JSC instead of YSLA, like the rocket body.
Note: For some reason, 18 SDS incorrectly shows the first 3 objects launched from JSC instead of YSLA, like the rocket body.
That means we have no GP data from USSF for the last SIX launches--except for the SupGP produced by CelesTrak for the last 3 Starlink launches. And there are 5 more launches--3 of them Starlink--scheduled before the end of the week: new.nextspaceflight.com/launches/?q=....
November 11, 2025 at 1:00 AM
That means we have no GP data from USSF for the last SIX launches--except for the SupGP produced by CelesTrak for the last 3 Starlink launches. And there are 5 more launches--3 of them Starlink--scheduled before the end of the week: new.nextspaceflight.com/launches/?q=....
The latest 18 SDS GP data meltdown continues. Almost all of the data is over 2 days old and the mean age is at 3.07 days old. And 4,437 of the 10,087 RSOs we have SupGP data for have an 18 SDS RMS of over 25 km. No doubt the other 18,872 RSOs have data just as bad. Why is this even condoned?
November 11, 2025 at 12:27 AM
The latest 18 SDS GP data meltdown continues. Almost all of the data is over 2 days old and the mean age is at 3.07 days old. And 4,437 of the 10,087 RSOs we have SupGP data for have an 18 SDS RMS of over 25 km. No doubt the other 18,872 RSOs have data just as bad. Why is this even condoned?
The current GP statistics can be found at: celestrak.org/NORAD/elemen.... The current SupGP vs. GP Comparisons can be found at: celestrak.org/NORAD/elemen....
November 10, 2025 at 8:31 AM
The current GP statistics can be found at: celestrak.org/NORAD/elemen.... The current SupGP vs. GP Comparisons can be found at: celestrak.org/NORAD/elemen....
I'll end this thread with this: When you--and especially USSF leadership--dismiss these 'little' errors, you are enabling complacency. There are serious issues with the GP, SP, and CDM data being ignored, as well, as shown at: celestrak.org/publications.... This won't end well for space safety...
November 6, 2025 at 11:18 PM
I'll end this thread with this: When you--and especially USSF leadership--dismiss these 'little' errors, you are enabling complacency. There are serious issues with the GP, SP, and CDM data being ignored, as well, as shown at: celestrak.org/publications.... This won't end well for space safety...
And then 18 SDS effectively changed the catalog numbers for the cross-tag. Once SpaceX changes to use those, the data STILL won't match. SpaceX knows which object is which and 18 SDS needs to match their IDs.
This stuff makes my head hurt. And it happens almost every day. Now you know, too...
This stuff makes my head hurt. And it happens almost every day. Now you know, too...
November 6, 2025 at 11:10 PM
And then 18 SDS effectively changed the catalog numbers for the cross-tag. Once SpaceX changes to use those, the data STILL won't match. SpaceX knows which object is which and 18 SDS needs to match their IDs.
This stuff makes my head hurt. And it happens almost every day. Now you know, too...
This stuff makes my head hurt. And it happens almost every day. Now you know, too...
Today's other errors include "STATLINK" for SSC 66146 and assigning the wrong launch site for all of 2025-240 and adding an extra "9" in the name for SSC 66193 (manual editing rather than M2M).
November 6, 2025 at 11:01 PM
Today's other errors include "STATLINK" for SSC 66146 and assigning the wrong launch site for all of 2025-240 and adding an extra "9" in the name for SSC 66193 (manual editing rather than M2M).
18 SDS 'fixed' this problem by changing SSC 66177 to STARLINK-35352. But they didn't change 2025-242C to 2025-243A, the Owner to US, or the launch site to AFETR.
In our update process, yellow shows changes, which is how we catch most errors. The non-changes almost slipped through...
In our update process, yellow shows changes, which is how we catch most errors. The non-changes almost slipped through...
November 6, 2025 at 10:45 PM
18 SDS 'fixed' this problem by changing SSC 66177 to STARLINK-35352. But they didn't change 2025-242C to 2025-243A, the Owner to US, or the launch site to AFETR.
In our update process, yellow shows changes, which is how we catch most errors. The non-changes almost slipped through...
In our update process, yellow shows changes, which is how we catch most errors. The non-changes almost slipped through...