Three launches, one abort, Starship on the pad again: the week in spaceflight
Three launches, one abort, and one more still to come. That's the shape of the week in spaceflight — and the story is cadence. SpaceX ended the week with a post-ignition abort that became a successful launch 24 hours later, a military constellation contract milestone that barely made the news, and a Starship sitting on a Texas pad that will try again this afternoon.
This Week's Launches
Here's the full accounting of the week that was, sourced from Spaceflight Now, Space Launch Live, and SpaceX's own Starship page:
| Date | Vehicle | Payload | Customer | Site | Outcome |
|---|---|---|---|---|---|
| Jul 16 | Falcon 9 | SDA Tranche 1 Transport Layer (21 sats) | Space Development Agency | Vandenberg SLC-4E | Success |
| Jul 16 | Starship–Super Heavy | 20 Starlink V3 simulator payloads | SpaceX | Starbase Pad 2, TX | Abort at ignition |
| Jul 21 | Falcon 9 (B1082) | 24 Starlink Group 17-39 satellites | SpaceX | Vandenberg SLC-4E | Success (retry from Jul 20 abort) |
| Jul 24 | Starship–Super Heavy | 20 Starlink V3 simulator payloads | SpaceX | Starbase Pad 2, TX | Window open 5:45 PM CT / 6:45 PM EDT today |
Sources: Spaceflight Now — SDA T1TL-E; Space.com — Falcon 9 Starlink 17-39 launch; SpaceX — Starship Flight 13; Wikipedia — Starship flight test 13.
---
What Actually Happened This Week
The abort that turned into a launch story
On Monday morning, July 20, SpaceX's Falcon 9 booster B1082 lit all nine Merlin engines at Vandenberg's Space Launch Complex 4E. They burned for less than a second. The flight computer commanded shutdown, and the vehicle stayed on the pad. This was a post-ignition abort — the engines fired, the rocket didn't move. SpaceX's own telemetry recorded it and called the next attempt within 24 hours.
That next attempt was Tuesday, July 21. Liftoff at 7:49 AM PDT (10:49 AM EDT). The booster landed on the droneship Of Course I Still Love You in the Pacific. The 24 Starlink satellites were deployed. By any operational measure, the week was fine. By the standard of two years ago, it would have been the lead story. By SpaceX's current standard, it's a Tuesday.
The pattern matters more than the individual event. Falcon 9 has now had two post-ignition aborts within a week of each other — the first at Starbase on July 16 during Starship Flight 13's attempted launch, the second at Vandenberg on July 20 during the Starlink 17-39 countdown. Neither vehicle flew. Neither caused damage. Both were handled by automated systems that did exactly what they were designed to do. The question the pattern raises is whether the cadence itself is creating a frequency of edge cases that would have been invisible at lower flight rates. At 85 Falcon 9 launches in 2026 (through late July), even a 1% anomaly rate produces a meaningful number of notable events in any given week.
The constellation milestone that slipped past
On July 16, the same day Starship sat down on its abort at Starbase, a Falcon 9 cleared Vandenberg carrying 21 communications satellites for the Space Development Agency's Tranche 1 Transport Layer. SDA confirmed deployment at 8 PM EDT. That launch brought the constellation to 21 operational satellites, with the full Tranche 1 Transport Layer design calling for 126 transport layer satellites, 28 tracking layer satellites, and 4 missile defense demonstration spacecraft — 154 total. York Space Systems builds the satellites. SpaceX provides the launch. The architecture is the product.
By this point in the build-out, SDA launches have become almost routine — which is exactly the point. The Proliferated Warfighter Space Architecture is designed to be resilient through redundancy: lots of satellites, any one of which can fail without degrading the network. Thursday's launch was another proof of that architecture working as designed. It's also, quietly, one of the more consequential things SpaceX did this week. The SDA contract represents a long-term, operational revenue stream that is separate from Starlink and commercial payloads — it's the kind of government services business that doesn't show up in launch counts but shows up in the durability of the manifest.
---
Today's: Starship Flight 13 Retry
The window for the Flight 13 retry opens at 5:45 PM CDT (6:45 PM EDT) today from Pad 2 at Starbase, Texas. That's in about — depending on when you're reading this — either a few hours or right around the corner.
SpaceX confirmed the delay to July 24 on July 23, citing weather at the launch site. The vehicle is the same hardware: Booster 20 and Ship 40, both first-flight articles, both explicitly written off for recovery. The payload — 20 Starlink Version 3 simulator satellites — was not carried on the July 16 attempt and was not deployed. Today's suborbital profile still ends with splashdowns: the Gulf of Mexico for the booster, the Indian Ocean for the ship.
What changed between July 16 and today: SpaceX modified the propulsion system after the Raptor engine issue that caused the abort. Musk's post-July-16 phrasing was "To be confident of a [launch], we need to understand why the engines didn't start." Eight days of analysis and modification later, the vehicle is ready to try again. Whether it clears the pad today is a function of weather, upper-level winds, and whatever else SpaceX's engineers find in their pre-launch reviews.
The thing worth watching, if you're following the launch at Spaceflight Now or the SpaceX webcast: the abort system worked as designed on July 16. The question for today is whether the fix did what it was supposed to do — and whether we get a launch, or another week of analysis followed by another attempt. Both outcomes tell us something useful about where Starship is in its development arc.
---
Next Week: Three Things to Watch
Starship Flight 14 — If Flight 13 flies today and the data looks clean, SpaceX will begin processing for Flight 14. The program's cadence has been running every six to eight weeks, consistent with its historical pattern across Flights 11 through 13; Flight 14 would be the next milestone. Shotwell's stated goal remains getting Starship to orbital capability, and that threshold is still ahead.
Falcon 9 continues its pace — At 85 launches through late July, the vehicle is tracking toward 140-plus Falcon 9 flights in 2026. That cadence is not slowing down. Every week produces multiple Starlink missions, commercial payloads, and government missions.
Voyager 1 crosses one light-day from Earth — On November 18, 2026, NASA's Voyager 1 spacecraft will be exactly one light-day away from Earth — 24 hours of light-travel time between here and the most distant human-made object ever launched. NASA announced the milestone on June 17, 2026. It's still almost four months away, but it's worth knowing it's coming: the spacecraft that left Earth in 1977 will cross a distance threshold that puts it farther from us than most science fiction imagined in the 1970s. (EarthSky has the full story.)
---
All times Eastern. Launch times sourced from Spaceflight Now, Space Launch Live, and SpaceX at time of writing. Starship Flight 13 status pending today's launch attempt. Bookmark spaceorbitals.com/newsletters/ for the daily tracker, published every weekday morning.