Minotaur IV : STP-S29A - 2026-04-07 11:30 UTC

Our first local ground station pass is at 23:40 UTC today. We will keep you updated. Is it possible to decode anything like callsign from either the MAMBO listings or the ASTRA-HyRAX listings?

1 Like

Unfortunately we need IQ to perform further analysis on the observed signals. If you can provide this from your own observation, it would be very helpful.

We will record when we have a pass

1 Like

In search of more detailed LoRa parameters, I reached out to the USNA-16 Team today. Sadly, we can scratch that from this deployment.

The reply was:

Unfortunately, USNA16 was de-manifested from the recent launch and will instead fly at a later date.

2 Likes

With so many SatNogs observations seeing solid signals on 401.500, I’ve been trying to ID what those signals were.

Using Observation SatNOGS Network - Observation 13759632 , there were clean 2k4 decodes w/ ā€˜Light-1’ framing:

… I don’t know if these frames match any known sats or what, but wanted to chime in on what we might be seeing there.

3 Likes

I’ve updated the first post and the DB according to the latest updates and by also using this press release:

https://www.ssc.spaceforce.mil/Newsroom/Article-Display/Article/4453711/us-space-force-launches-dow-stp-s29a-mission-delivers-experimental-and-research

So, INCA-2, MOCI, USNA-16 have their status changed to ā€œfutureā€, all the future observations in Network has been removed.

MAMBO entry is now for the unknown satellite (one of STPSat-7, Rawhide, MISR-C, AggieSat6, or ASTRA-HyRAX ) and it is named ā€œUnknown 1 - MinoTaur IVā€. My guess would be MISR-C but haven’t found many details about this mission, so Iet’s keep observing to find out.

EDIT: MISR-C according to the related ITU entry is only transmitting in S-band

4 Likes

As others have posted, CANVAS looks good. Ahh, the simple days of plain ol’ 9k6 decoding. So now I guess it’s time to move on to help locate some of the objects that aren’t as straight-forward!

2 Likes

That is quick, we have TLE CelesTrak: International Designator 2026-074

STP-S29A OBJECT A       
1 68627U 26074A   26097.91706032  .00004294  00000+0  19197-3 0  9998
2 68627  60.0189  87.7223 0014676 297.1477  62.8106 15.23090715    78
STP-S29A OBJECT B       
1 68628U 26074B   26097.91703438  .00002001  00000+0  95544-4 0  9991
2 68628  60.0213  87.7179 0015323 307.5634  52.4054 15.23216244    61
STP-S29A OBJECT C       
1 68629U 26074C   26097.91691434  .00002055  00000+0  96632-4 0  9992
2 68629  60.0169  87.7048 0017930 312.2375  47.7183 15.23617771    79
STP-S29A OBJECT D       
1 68630U 26074D   26097.85121279  .00002133  00000+0  98955-4 0  9999
2 68630  60.0175  87.9509 0010752 306.1889  53.8196 15.23975335    52
STP-S29A OBJECT E       
1 68631U 26074E   26097.85121689  .00002126  00000+0  98563-4 0  9992
2 68631  60.0200  87.9620 0016392 317.0808  42.8992 15.23975913    69
STP-S29A OBJECT F       
1 68632U 26074F   26097.85111469  .00002002  00000+0  92387-4 0  9999
2 68632  60.0333  87.9594 0016443 317.9536  42.0281 15.24400618    59
STP-S29A OBJECT G       
1 68633U 26074G   26097.85101413  .00002187  00000+0  98455-4 0  9994
2 68633  60.0233  87.9661 0017521 330.0565  29.9512 15.24870914    51
STP-S29A OBJECT H       
1 68634U 26074H   26097.85093502  .00002127  00000+0  95039-4 0  9993
2 68634  60.0231  87.9632 0020139 334.8183  25.1914 15.25223134    67
STP-S29A OBJECT J       
1 68635U 26074J   26097.85124475  .00000506  00000+0  32579-4 0  9997
2 68635  60.0274  87.9804 0017925 317.0045  42.9633 15.23828546    66
68629: 0.257 kHz 437.249770 MHz | TBA - TO BE ASSIGNED
68630: 0.168 kHz 437.249938 MHz | TBA - TO BE ASSIGNED
68631: 0.169 kHz 437.249952 MHz | TBA - TO BE ASSIGNED
68632: 0.332 kHz 437.250196 MHz | TBA - TO BE ASSIGNED
68635: 0.176 kHz 437.249896 MHz | TBA - TO BE ASSIGNED

At the moment CANVAS seems 68630 based on last nights STRF data, but 68631 is also a candidate.

Jan | PE0SAT

3 Likes

That’s interesting, 9 objects but 6 satellites, if I’m not mistaken, are announced in the press release. So, we have 3 more objects, which may be parts of the rocket.

Indeed the two objects are very close, I’ve updated in DB to follow 68630 for now, let’s keep an eye as the TLE will be assigned and change their TBA (to be assigned) status.

For the unknown object it seems that 68629 fits better, so I’ve updated in DB to follow this for now, but let’s keep watching.

For ASTRA-HyRAX I’ve randomly chosen to follow 68631 as it is in the middle of this launch objects, unfortunately still no signal received from it.

1 Like

401.500 MHz – Replay of IQ recording at 17:05:55 UTC
Has anyone ever seen anything like this? :thinking:

3 Likes

As Jonathan McDowell noted in this post, one of the object is Minotaur stage 4 and what I missed is that there is a pair of Rawhide satellites, so we have 7 satellites, 1 rocket stage and one unknown object.

4 Likes

CANVAS is obviously in grand shape and several others ended up not actually being on this deployment.

So, what’s next? Which object(s) should we prioritize from this deployment at this point?

Thanks!

3 Likes

I think we should try to get ASTRA-HyRAX and try to identify which one is Unknown 1 - MinoTaur IV.

2 Likes

Able to decode the Unknown 1 - MinoTaur IV with gr_satellites.

Work in progress, at the moment also looking at csp telemetry decode.

name: UNKNOWN-1
norad: 98337
data:
  &tlm unknown telemetry:
    unknown
  &csp CSP Telemetry:
    telemetry: csp
transmitters:
  2k4 FSK downlink:
    frequency: 401.500e+6
    modulation: FSK
    baudrate: 2400
    deviation: 600
    framing: Light-1
    data:
    - *tlm
    - *csp

gr_satellites UNKNOWN-1.yml --wavfile 13764253.ogg --samp_rate 48e3

***** VERBOSE PDU DEBUG PRINT ******
((transmitter . 2k4 FSK downlink))
pdu length =         65 bytes
pdu vector contents = 
0000: 00 02 21 d4 00 fd fc f7 ce 6c 50 9e ee b2 86 1d 
-> Packet from 2k4 FSK downlink
0010: 61 f6 19 9e d6 48 83 39 45 ac e0 5d 61 97 46 15 
0020: 83 58 5d ab 46 65 1c 32 23 0e 07 15 48 50 65 88 
0030: 3f d5 e6 da b3 ae 64 9f f7 4f 70 cb b5 80 eb 02 
0040: 55 
************************************
Container: 
    header = Container: 
        priority = 0
        source = 0
        destination = 0
        destination_port = 8
        source_port = 33
        reserved = 6
        fragmentation = True
        hmac = False
        xtea = True
        rdp = False
        crc = False
    payload = b'\x00\xfd\xfc\xf7\xcelP\x9e\xee\xb2\x86\x1da\xf6\x19\x9e\xd6H\x839E\xac\xe0]a\x97F\x15\x83X]\xabFe\x1c2#\x0e\x07\x15HPe\x88?\xd5\xe6\xda\xb3\xaed\x9f\xf7Op\xcb\xb5\x80\xeb\x02U' (total 61)
***** VERBOSE PDU DEBUG PRINT ******
((transmitter . 2k4 FSK downlink))
pdu length =         65 bytes
pdu vector contents = 
0000: 00 02 21 d4 00 13 6b f1 dc 5e 32 19 6d 2f 35 a2 
0010: 1e 1b 83 83 8a 9e 21 5a cb c6 49 4a 3c c8 d1 3a 
0020: ac 2e 47 e8 9a cf 80 19 a5 fd af 83 dc 42 61 19

All frames start with 00 02 21 d4 00 this could be an identifier.

Jan | PE0SAT

4 Likes

Hey, this is the ASTRA-HyRAX team. Unfortunately, we still have not made contact with ASTRA-HyRAX. We are most likely dead at this point. However, we would appreciate y’all continuing to look out for it. We are expecting a beacon at 80 second intervals at 401.475 MHz GSFK 9600. We have continued to monitor the reports that people have been posting in observations for ASTRA-HyRAX and there were some promising ones, but nothing was actually us. Thanks!

2 Likes

Sorry to hear that!

It’s a long-shot, but does your radio hardware have a factory-default frequency and mode that it might have reverted back to from low voltage, radiation, etc?

1 Like

Unfortunately, no it does not have a factory-default frequency. It should have stayed at the 401.475.

1 Like

A quick update:

CANVAS is object 68635.

Unknown 1 - MinoTaur IV is object 68629

Unfortunately no reception from ASTRA-HyRAX, we continue randomly to follow 68631 but if the team want to follow any other object let me know.

Additionally with Unknown 1 - MinoTaur IV there is another Unknown object from this launch that follows 68632 transmits at the same frequency as Unknown 1, 401.500 MHz and it looks like the same kind of transmission. You can take a look of both objects in this observation: SatNOGS Network - Observation 13765278 and there are many others similar to this one.

It seems that both of them have stopped (after command?) to beacon at UHF but from time to time there are some transmissions (maybe after command). I’ve added the second object to track it and verify its transmissions as Unknown 2 - MinoTaur IV.

Given that both transmit at the same frequency and their transmissions are similar, my guess is that they are the only pair of this launch Rawhide-1 and Rawhide-2, however there isn’t any other information verifying it so we’ll keep them as unknown in DB for now.

The changes in the NORAD IDs in DB will be performed tomorrow with links to identification evidence.

4 Likes

@fredy Since we have still not received reception from ASTRA-HyRAX we are interested in using our ground station to track other satellites if needed. Do you know how we go about registering the ground station for that purpose for SatNOGS? We have had success with see other satellites and objects in our waterfall plots while we were watching for ASTRA-HyRAX.

1 Like

@eam0052 Hi! I’m from the CU Boulder/LASP Ops team, we could use some extra observation time for one of our Cubesats we launched on Transporter 16 a couple weeks ago. It’s transmitting on 401.2MHz; GMSK 9600. Sounds like your antenna would be a great fit :slight_smile:

2 Likes