$ASTS Confirmed that this was not public knowledge before this PR: DPAS program gives payloads priority to launch over others.
ULA is part of the DPAS program. I'm guessing 2027 sees multiple BB payloads bump ahead of Amazon Leo's booked flights.
Wow wow. I was right. At the bottom of the PR: 🚨🚨. “The company also has access to further launches for U.S. Government missions alongside its Defense Priorities and Allocations System (DPAS) rated program.”🚨🚨
This means very specific purchase orders were made by the USG. THEY ARE DEFINITELY ANNOUNCING MORE THINGS ON EARNINGS. This is new information.
🚨🚨🚨🚨🚨🚨🚨
$ASTS
Correction: this was at Blue Origins Lunar Plant 1, NOT AstroTech. Points are still valid, though.
Replying to @Akslfak
But also, because they've done it before. BB7 (rip) was launched a full 59 days after integration was complete - by AstroTech, no less.
I guess you can consider this technically "in storage" but don't assume that they're just parked in their shipping crates the whole time.
27
1,919
$ASTS A little more of what I think might be happening here to clear up some questions:
1. If I'm right, ASTS would not perform this testing. They're a platform across which this testing would take place. Someone would be paying them to use their platform (gov't/contractor/etc.)
$ASTS Let's talk about the Grain 800MHz testing that ASTS is coordinating. They just renewed the STA weeks after SPCX announced their DA with Grain, which is... weird.
Easy to assume they're just running commercial testing, but the facts make this far more interesting
A thread:
$ASTS Let's talk about the Grain 800MHz testing that ASTS is coordinating. They just renewed the STA weeks after SPCX announced their DA with Grain, which is... weird.
Easy to assume they're just running commercial testing, but the facts make this far more interesting
A thread:
Below the noise floor. Pull The DD™️ and do a word search and you’ll see we’ve studied this before. $ASTS
Big things are happening, panic notwithstanding
Correction: flipped the probability translations: FM1-23 is less than 1 in 10000 and FM24+ is less than 1 in 5000.
Replying to @Akslfak
That said, there's plans for powered deorbit: moving the sats below 530KM into a high-drag orientation will deorbit under 5 years.
Odds of failure preventing controlled deorbit calculated at 9.57E-05 (FM1-23) and 1.97E-04 (FM24+) - Less than 1 in 5000 and 10000, respectively.
5
910
Correct.
Orbit Alt (h) = 690km
Coef Drag (CD) = 2.2
X-Sec Area (A) = 126m²
Sat Mass (M) = 4120kg
Orbit Radius (r) = 7,061km
Ballistic Coef (BC) = M/CD*A
Atm. Dens (rho) = rho0*e^(-h / H) = 4.154e-14
Decay = -2*pi*rho*r^2 / BC = 12.81m/day
Orbit Life = Alt/Decay = ~147 Years.
$ASTS Just to give you an idea about longevity in space.
In September 2008.
For Falcon 1 4th flight, Stage 2 achieved orbit at 621/643km altitude.
The Stage 2 is still in orbit to this day and has likely 5-10 years more to go.
Bluebirds will be orbiting at 690km. Depending on design margins, we could have birds flying for 20+ years.
$ASTS Some corrections/clarifications to my previous post, after chatting with some folks in-the-know.
$ASTS Been thinking over the timing of the last shipment and various comms, and am now thinking that ASTS may have iterated their shipping processes a bit.
Warning: A lot of conjecture here.
A thread.
$ASTS Busy times at the Cape.
Launch today made room for a customer in SX integration. Curious if ASTS will grab it this week.
If not, Bandwagon launches 10/19, so another spot opens in about a week.
This math checks out. That's a crazy amount of broadcast power, definitely capable of generating jam-resistant signals or overwhelming local signals to jam other comms/radar.
People are focused on consumer ARPU, but I think major money will come from the military first.
$ASTS Lets focus on this filing for a second as it is import going backwards from what we already know as I think this test is sand bagging it 🧵
Arrived a week ago based on traffic cams. Still a nice update.
No update on BB17-19. If you're on board with my previous statements (SX NDA means no updates on completed batches because it means they're waiting on SX)... no update means the sats are ready.
This quoted post is unavailable.
I also don't blame anyone for disagreeing with me on that idea. It's conjecture. But we've never seen an update that a BB2 batch was ready to ship, so what little evidence we have lines up.
Replying to @Akslfak
Why not announce the stack was ready to launch while everyone's waiting around for a month?
See the previous NDA. I believe ASTS is being extremely cautious not to piss off their one available launch provider by stating any info that could be misconstrued to make SX look bad.
$ASTS I don't expect another BB11-style deploy delay in future launches... not exactly, at least.
BB11/12 were likely spaced out for testing handoffs and non-comms tech requiring two sats.
(Pic: BB11 leading BB12 (pink), as BB10 (blue) passes on its own orbital plane)
A thread
First: see my previous post about how BB11's deployment was delayed due to efficient fuel usage/drag control in flying the sats, not due to technical issues. Before this, though, BB8-10 were all deployed at the roughly the same time.
$ASTS New GP TLEs haven't quite hit the ASTSats site but show drag on BB11 closing in on BB12.
First image: BB11 6.3e-5, second image BB12 8.9e-5. TLEs about 8 hours apart so BB12 is likely slightly higher than this at the same time as 11 but the delta continues to narrow.
Another breadcrumb of BB11 activity: SupGP updates are coming infrequently.
Sep 19-27
BB12: 42 TLEs
BB11: 25 TLEs
Delayed SupGPs likely means they are gathering new telemetry and recalculating TLEs. Guessing drag data is variable as the deployment settles, slowing calculations





















