Transporter-17 Rideshare: VSFB SLC-4E : 2026-07-07 07:10 UTC

It is not and according to this post, we were tracking wrong frequency.:

okay.

Using this TLE for Navigator:

1 98270C 26156BH  26188.34443476 -.00015589  00000-0 -30982-2 0  9990
2 98270  97.7571  88.7983 0007635 143.1901 230.9775 14.91796255    10

… there was a close match if I ran my computer’s clock forward 5 minutes.

Of course that’s an approximation when simply going by the SNR of the downlink.

Hi from the Apolink Team!

We are currently trying out this TLE:

1 88206U          26193.97697469 +.00000352 +00000+0 +40657-4 0 00167
2 88206  97.7565  94.3405 0007078 121.5857 238.6054 14.91567747000842

Still haven’t received anything, could we please get updated contacts? Thanks!

Best,
-The Apolink Team

Good afternoon,

It is possible I missed something, but can you share some details on the satellite we are searching for?

Never mind, I found the IPOS-TDSM satellite details.

Jan | PE0SAT

See next post, this analysis is invalid it wasn't after 5min but 5min before that K4KDR seen the signals

Very useful info, from a quick check, after 5 minutes there are three objects near the supposed Navigator position, 88207, 88246 and 88248. From them I’ll choose to try 88246 for now, @K4KDR please also try it and let us know if you have better results.

So, the TLE for Navigator from the analyst list, changed to use the temporary NORAD ID in DB:

Navigator
1 98270U          26193.91277489 +.00000588 +00000+0 +65431-4 0 00167
2 98270  97.7569  94.2694 0004006 108.4639 251.7015 14.90795221000838
1 Like

After communication with the team, we are going to track SENTINEL-1 (OSIRIS-A) with the TLE of analyst object 88262. Thus here is the latest TLE base on the space-track.org analylist list, changed to use the tempory NORAD ID in DB:

SENTINEL-1
1 98261U          26193.84045334 +.00001437 +00000+0 +14641-3 0 00149
2 98261  97.7590  94.2112 0009695 133.1311 227.0720 14.92213362000829
1 Like

Thanks very much. I feel bad if I didn’t explain properly, but the signal arrived 5-minutes AHEAD of where the old TLE placed it. When I applied this latest update, I noticed that the position of Navigator moved substantially farther back.

I originally spotted Navigator’s signal while tracking Marina, so an update to the TLE based on Navigator’s ā€œearlyā€ arrival this morning would, as expected, move it FORWARD up in the area of Marina. Not farther to rear of those T-17 objects.

So sorry if I framed my adjustment poorly!

1 Like

No problem, thanks for pointing it out, I’m checking now what objects are the best to track by fixing this confusion. :slight_smile:

1 Like

So, here is the fixed analysis for Navigator base on @K4KDR observation:

There are 4 possible objects, but one of them seems to fit better the 5min difference. The objects are 88265, 88266, 88267 and 88268. The one that fits better is 88267, so using that for tracking Navigator, here is the space-track.org analyst TLE, changed to use temporary NORAD ID:

Navigator
1 98270U          26194.10805992 +.00001318 +00000+0 +13423-3 0 00137
2 98270  97.7564  94.4749 0010526 130.3049 229.9091 14.92372951000866
1 Like

Thanks so much! Can’t wait to try a pass where I don’t have to adjust my tracking with computer clock changes.

1 Like

The TLE changed to use the temporary NORAD ID:

IPoS-TDsM
1 98287U          26193.97697469 +.00000352 +00000+0 +40657-4 0 00167
2 98287  97.7565  94.3405 0007078 121.5857 238.6054 14.91567747000842
1 Like

Well thank you again for what turned out to be just some spectacular TLE work.

On tonight’s 38° pass, I didn’t even know if I would SEE a downlink from Navigator. No data sidebands this time, of course, but the center residual carrier was plenty powerful enough to see - given some dish tracking that was accurate enough.

I can’t say if this was dead on or a fraction of a degree off, but either way it’s working very well. Much appreciated!

3 Likes

TLE update using the latest analyst TLE list from space-track.org changed to use temporary NORAD IDs from DB:

IPoS-TDsM
1 98287U          26194.91616514 +.00000391 +00000+0 +44549-4 0 00183
2 98287  97.7564  95.2644 0007119 119.0902 241.1030 14.91568605000987
KOYO
1 98273U          26194.91937801 +.00001584 +00000+0 +16647-3 0 00196
2 98273  97.7532  95.2567 0004608 100.2968 259.8770 14.90842244000985
Unknown 1 T17
1 98259U          26194.91865210 +.00001488 +00000+0 +15610-3 0 00163
2 98259  97.7581  95.2617 0005175 106.4647 253.7140 14.91010768000984
Kita-36
1 98275U          26194.71576161 +.00001124 +00000+0 +11815-3 0 00185
2 98275  97.7554  95.0637 0006811 114.0130 246.1802 14.91373412000958
Kita-53
1 98274U          26194.64799869 +.00000396 +00000+0 +45068-4 0 00153
2 98274  97.7563  94.9999 0007037 118.9285 241.2640 14.91527391000943
ANDURIL-216
1 98258U          26194.64799869 +.00000396 +00000+0 +45068-4 0 00155
2 98258  97.7563  94.9999 0007037 118.9285 241.2640 14.91527391000945
CloudCT-Precursor
1 98278U          26194.98546000 +.00000621 +00000+0 +68319-4 0 00156
2 98278  97.7537  95.3242 0006154 102.8838 257.3068 14.91072525000990
SCION-X
1 98266U          26194.91872915 +.00000319 +00000+0 +37874-4 0 00159
2 98266  97.7504  95.2558 0005725  99.6287 260.5578 14.90985937000984
Unknown 2 T17
1 98257U          26194.91878597 +.00000266 +00000+0 +32461-4 0 00160
2 98257  97.7587  95.2617 0004834 107.3192 252.8556 14.90972435000982
CUBY-1
1 98284U          26194.91878597 +.00000266 +00000+0 +32461-4 0 00160
2 98284  97.7587  95.2617 0004834 107.3192 252.8556 14.90972435000982
CUBY-2
1 98283U          26194.91878597 +.00000266 +00000+0 +32461-4 0 00169
2 98283  97.7587  95.2617 0004834 107.3192 252.8556 14.90972435000981
CUBY-3
1 98282U          26194.91878597 +.00000266 +00000+0 +32461-4 0 00168
2 98282  97.7587  95.2617 0004834 107.3192 252.8556 14.90972435000980
CUBY-4
1 98281U          26194.91878597 +.00000266 +00000+0 +32461-4 0 00167
2 98281  97.7587  95.2617 0004834 107.3192 252.8556 14.90972435000989
CUBY-5
1 98280U          26194.91878597 +.00000266 +00000+0 +32461-4 0 00166
2 98280  97.7587  95.2617 0004834 107.3192 252.8556 14.90972435000988
SUCHAI-4
1 98265U          26194.85293777 +.00000676 +00000+0 +74484-4 0 00169
2 98265  97.7550  95.1910 0003625 102.2920 257.8704 14.90685218000975
TOM-1
1 98264U          26194.85293777 +.00000676 +00000+0 +74484-4 0 00168
2 98264  97.7550  95.1910 0003625 102.2920 257.8704 14.90685218000974
MARMOTSat
1 98272U          26194.98631218 +.00000703 +00000+0 +76876-4 0 00176
2 98272  97.7593  95.3262 0004095 115.3926 244.7716 14.90882217000993
TOM-2
1 98263U          26194.98631218 +.00000703 +00000+0 +76876-4 0 00176
2 98263  97.7593  95.3262 0004095 115.3926 244.7716 14.90882217000993
TOM-3
1 98262U          26194.91985872 +.00000630 +00000+0 +69714-4 0 00145
2 98262  97.7572  95.2590 0004471  94.1893 265.9836 14.90731212000982
Marina
1 98293U          26194.91453180 +.00001087 +00000+0 +11282-3 0 00144
2 98293  97.7536  95.2633 0008765 125.2343 234.9697 14.91944501000989
RAFS
1 98268U          26194.91482635 +.00001380 +00000+0 +14198-3 0 00171
2 98268  97.7563  95.2655 0008023 127.3707 232.8244 14.91879120000988
Replicator-2
1 98267U          26194.91342812 +.00000425 +00000+0 +47179-4 0 00100
2 98267  97.7549  95.2659 0009508 131.1230 229.0812 14.92191015000810
SENTINEL-1
1 98261U          26194.91334999 +.00001591 +00000+0 +16150-3 0 00166
2 98261  97.7586  95.2676 0009823 129.7964 230.4121 14.92216630000989
Navigator
1 98270U          26194.91264639 +.00001273 +00000+0 +12977-3 0 00158
2 98270  97.7562  95.2673 0010603 128.0611 232.1566 14.92374984000988
KOSTKA
1 98395U          26194.84519828 +.00001736 +00000+0 +17453-3 0 00159
2 98395  97.7506  95.1995 0011221 123.5944 236.6348 14.92469435000978

TLE chosen from the last analysis from previous posts.

Unfortunately due to traveling I haven’t any updates on the fits, I’ll try later today or tomorrow. If there is any suggestions for changes let me know.

3 Likes

Looks like Navigator is active on 401.25MHz:



1 Like

Navigator is not expected to transmit on UHF, so probably it is one of the other satellites, maybe one of the LEMUR sats.

I’m going to add it as Unknown 3 T17 in DB and use the TLE we used for Navigator and try to track it:

Unknown 3 T17
1 98255U          26194.91264639 +.00001273 +00000+0 +12977-3 0 00151
2 98255  97.7562  95.2673 0010603 128.0611 232.1566 14.92374984000981
1 Like

Hi from the Apolink Team!

Here is the latest TLE that we will be using:

1 88246U          26193.91277489 +.00000588 +00000+0 +65431-4 0 0016
2 88246  97.7569  94.2694 0004006 108.4639 251.7015 14.9079522100083

Could we please get new contacts? That would be great!

Best,
-The Apolink team

TLE changed to use temporary NORAD ID:

IPoS-TDsM
1 98287U          26193.91277489 +.00000588 +00000+0 +65431-4 0 00165
2 98287  97.7569  94.2694 0004006 108.4639 251.7015 14.90795221000836

One more update from the space-track.org analyst TLE list:

SUCHAI-4
1 98265U          26195.59130917 +.00000708 +00000+0 +77792-4 0 00191
2 98265  97.7549  95.9161 0003639 100.9537 259.2091 14.90686294001086
TOM-1
1 98264U          26195.59130917 +.00000708 +00000+0 +77792-4 0 00190
2 98264  97.7549  95.9161 0003639 100.9537 259.2091 14.90686294001085
IPoS-TDsM
1 98287U          26195.65788755 +.00000635 +00000+0 +70148-4 0 00200
2 98287  97.7565  95.9839 0004040 104.9072 255.2594 14.90797323001096
MARMOTSat
1 98272U          26195.92593358 +.00000737 +00000+0 +80338-4 0 00190
2 98272  97.7592  96.2498 0004119 113.3622 246.8030 14.90883557001138
TOM-2
1 98263U          26195.92593358 +.00000737 +00000+0 +80338-4 0 00190
2 98263  97.7592  96.2498 0004119 113.3622 246.8030 14.90883557001138
TOM-3
1 98262U          26195.65820734 +.00000669 +00000+0 +73739-4 0 00168
2 98262  97.7570  95.9845 0004467  92.4221 267.7508 14.90732238001099
Marina
1 98293U          26195.65228090 +.00001079 +00000+0 +11209-3 0 00168
2 98293  97.7535  95.9891 0008770 123.0074 237.1989 14.91946121001096
RAFS
1 98268U          26195.98796130 +.00001637 +00000+0 +16742-3 0 00191
2 98268  97.7561  96.3216 0008091 124.4578 235.7406 14.91883298001142
Replicator-2
1 98267U          26195.78516996 +.00000461 +00000+0 +50776-4 0 00121
2 98267  97.7547  96.1240 0009541 128.5112 231.6964 14.92191875000945
Sentinel-1
1 98261U          26195.78507578 +.00001615 +00000+0 +16388-3 0 00189
2 98261  97.7585  96.1262 0009881 127.2556 232.9566 14.92219643001116
Navigator
1 98270U          26195.71723136 +.00001334 +00000+0 +13575-3 0 00174
2 98270  97.7561  96.0597 0010651 125.6582 234.5631 14.92377320001105
Unknown 3 T17
1 98255U          26195.71723136 +.00001334 +00000+0 +13575-3 0 00177
2 98255  97.7561  96.0597 0010651 125.6582 234.5631 14.92377320001108
KOSTKA
1 98395U          26195.71677689 +.00001762 +00000+0 +17706-3 0 00178
2 98395  97.7504  96.0573 0011265 121.0466 239.1861 14.92472224001102
2 Likes

Hello Daniel, UHF Digipeater on MARINA received my messages, according the UHF beacon counter increased from 0 to 31 and my callsign was added to the beacon as last op. Unfortunatelly I didn’t receive the repeated message back, but other GS sent the telemetry with the repated messages. So it seems to be operational.

But I think there is some issue with the Digipeater Dashboard for UHF - it says UHF Total Digipeated Messages: 31, but UHF Last User:No data:

image

However in the Marina Telemetry Dashboard, there is the callsign decoded from last UHF beacon:
image

3 Likes