Time check, please? 2200utc has passed.
oops my bad… this was the BRT time, the right utc time is 2025-12-23 01:00 UTC
TLE for 2025-12-23 01:00 UTC
SOLARAS S2
1 98461U 25357.04513889 .00000000 00000-0 50000-4 0 00
2 98461 40.0000 66.4597 0001497 0.0000 356.4413 15.90816786 09
FLORIPASAT-2A
1 98456U 25357.04513889 .00000000 00000-0 50000-4 0 04
2 98456 40.0000 66.4597 0001497 0.0000 356.4413 15.90816786 03
FLORIPASAT-2B
1 98455U 25357.04513889 .00000000 00000-0 50000-4 0 03
2 98455 40.0000 66.4597 0001497 0.0000 356.4413 15.90816786 02
JUSSARA-K
1 98454U 25357.04513889 .00000000 00000-0 50000-4 0 02
2 98454 40.0000 66.4597 0001497 0.0000 356.4413 15.90816786 01
PION-BR2
1 98453U 25357.04513889 .00000000 00000-0 50000-4 0 01
2 98453 40.0000 66.4597 0001497 0.0000 356.4413 15.90816786 00
In total 656 observations have been scheduled for the first 24h after deployment of the satellites. We have used the TLE sets of the previous post.
The difference in the number of scheduled observations is based to:
- Frequency of transmission of the satellite
- Orbit of the satellite/TLE set
- Request by or communication with the satellite team
- Spectrum misuse or violation of regulations
| Temp NORAD ID | Satellite | Scheduled Observations |
|---|---|---|
| 98461 | SOLARAS S2 | 386 |
| 98454 | Jussara-K | 91 |
| 98455 | FloripaSat-2B | 90 |
| 98456 | FloripaSat-2A | 89 |
| Total | 656 |
Unfortunately for “Pion-BR2” there isn’t any hint of its frequency, so is not scheduled for now.
To station owners, have in mind that the TLE are not accurate and may change, so for better results don’t scheduled too far in future ![]()
Not sure if the stream is delayed, but from the countdown clock on the stream it seems that the launch time is 01:13 UTC… However I’ll stay to the announcement just to be sure.
@pu4elt if just in case have any info about the update time please let us know, thanks!
Yep, I’ll keep you informed… It seems that if it doesn’t work out this time, we’ll only have a new window in April of next year (Unofficial information).
Also, pay attention to FloripaSat-2B
It seems that the launch date is changed so here are the new TLE sets for 2025-12-23 01:13 UTC:
SOLARAS S2
1 98461U 14900A 25357.05416667 .00000000 00000-0 50000-4 0 01
2 98461 40.0000 69.7186 0001497 0.0000 356.4413 15.90816786 09
FLORIPASAT-2A
1 98456U 14900A 25357.05416667 .00000000 00000-0 50000-4 0 05
2 98456 40.0000 69.7186 0001497 0.0000 356.4413 15.90816786 03
FLORIPASAT-2B
1 98455U 14900A 25357.05416667 .00000000 00000-0 50000-4 0 04
2 98455 40.0000 69.7186 0001497 0.0000 356.4413 15.90816786 02
JUSSARA-K
1 98454U 14900A 25357.05416667 .00000000 00000-0 50000-4 0 03
2 98454 40.0000 69.7186 0001497 0.0000 356.4413 15.90816786 01
PION-BR2
1 98453U 14900A 25357.05416667 .00000000 00000-0 50000-4 0 02
2 98453 40.0000 69.7186 0001497 0.0000 356.4413 15.90816786 00
I’m going to reschedule the observations…
In total 604 observations have been scheduled for the first 24h after deployment of the satellites. We have used the TLE sets of the previous post.
The difference in the number of scheduled observations is based to:
Frequency of transmission of the satellite
Orbit of the satellite/TLE set
Request by or communication with the satellite team
Spectrum misuse or violation of regulations
| Temp NORAD ID | Satellite | Scheduled Observations |
|---|---|---|
| 98461 | SOLARAS S2 | 304 |
| 98456 | FloripaSat-2A | 100 |
| 98454 | Jussara-K | 100 |
| 98455 | FloripaSat-2B | 100 |
| Total | 604 |
Okay, apparently there were problems with the flight… Two loud explosions were heard (The first one approximately 50 seconds after launch) ![]()
Thanks for your efforts @fredy in calculating the TLE’s for us and adding the satellites to the SatNOGS network ![]()
Sure hate to see that - so much work by those involved in the various sats.
Yes - thanks so much for helping us all get ready.
Space is hard, especially for the first launches, I remember the firefly first one that failed which had LSF’s PICOBUS and QUBIK 1 and 2 mission.
I guess people in innospace will have a lot of data to process. Hopefully for the satellite teams, they may have the opportunity to fly on the next launch.
So sad for everyone involved. Thanks also helping us get ready.
Just out of curiosity
It appears that the rocket suffered a premature disassembly in flight (the structure could not withstand the aerodynamic force)… Again, unofficial information.
https://x.com/MundoEConflicto/status/2003278414191677739 here there is a better view of the explosion.
@pu4elt keep in mind that the disassembly/explosion is sometimes a safety measure triggered if something isn’t nominal, so it may not be the cause of the fail.
Of course all these are speculations, I guess in the next days and after data analysis, there will be a more detailed announcement from innospace.
Yes, just speculation that’s popping up, hehehehe… Now there are reports that there was a trajectory error and then an explosion… Anyway, what a shame.
My eyes are now fixed on the launch on the 28th ![]()
![]()
