After a two day stand down thanks to weather, SpaceX launched its first Falcon Heavy in 18 months from Pad LC-39A at Kennedy Space Center. It was the 12th Falcon Heavy mission overall and the 31st launch overall this year from Florida.
On a day that saw SpaceX scrub a Falcon Heavy launch inside the last minute thanks to a nearbyh shower, United Launch Alliance had far better weather conditions later as the dusk faded into the night. They launched an Atlas V 551 at 8:53:30 PM EDT, sending another 29 broadband satellites toward low Earth orbit for the Amazon Leo constellation. ULA confirmed deployment of all 29 spacecraft shortly after.
Today’s launch was the first commercial payload for New Glenn, the first time it has reused a booster, and the second time it has successfully landed a booster aboard Blue Origin’s drone ship, Jacklyn. Unfortunately, later in the mission, New Glenn’s second stage failed to deliver the payload into its intended orbit.
While the initial ascent was picture perfect, the end result was not. At roughly T+2h 15m into the mission, Blue Origin reported that the satellite was delivered into an off-nominal orbit.
As seen from KARS Park. This is a great place to see a launch if you are visiting the Space Coast.
United Launch Alliance successfully launched its Vulcan Centaur rocket early Thursday morning, carrying a national security payload for the U.S. Space Force on the USSF-87 mission.
Liftoff occurred at 4:22 AM ET from Space Launch Complex 41 at Cape Canaveral Space Force Station, about midway through a two-hour window that opened at 3:30 AM.
Yesterday after the launch of Starlink 17-32 from Vandenberg Space Force Base in California, SpaceX deployed its payload of Starlink satellites as planned, but was apparently unable to complete a deorbit burn of the second stage used for the mission. That burn allows the company to precisely place the re-entry zone for safe disposal of the second stage. That in turn has led SpaceX to pause Falcon 9 flights while it investigates the issue.
For its part, SpaceX said on X last night that “During today’s Falcon 9 launch of Starlink satellites, the second stage experienced an off-nominal condition during preparation for the deorbit burn. The vehicle then performed as designed to successfully passivate the stage. The first two MVac burns were nominal and safely deployed all 25 Starlink satellites to their intended orbit. Teams are reviewing data to determine root cause and corrective actions before returning to flight.”
UPDATE: Talk of Titusville asked the FAA whether an investigation would be required and whether it would pause Falcon 9 licenses until the investigation was completed, and after the latest government shutdown was resolved, they replied on February 5th, “Safety is our top priority. SpaceX is required to conduct a mishap investigation. The FAA will oversee every step of the investigation, approve the final report and any corrective actions.”
| Mission | Incident Date | Return to Flight |
|---|---|---|
| Starlink Group 9-3 | July 2024 | 15 days later |
| Crew-9 | September 2024 | ~2 weeks later |
| Starlink 10-12 | February 2025 | Undetermined |
As of: February 3, 2026 at 8:32 AM EST
Spaceflight expert Dr. Jonathan McDowell noted yesterday that the second stage for Starlink 17-32 won’t be in orbit long. He posted on the X platform late last night, saying “[The US] Space Force has cataloged the errant Starlink 17-32 Falcon 9 upper stage as object 67673 [and it is] in a 110 x 241 km x 97.3 deg orbit. It will reenter quickly.”
The payload deployed normally, so there is no danger of uncommanded reentry of the 25 Starlink satellites. According to Dr. McDowell, “The Starlinks report themselves in the target 246 x 260 km orbit. The second stage did not make a deorbit burn, but it did passivate by venting prop, and this lowered the perigee to 110 km.”
With launches delayed for the time being, it is fair to say that the first three of the four Falcon 9 launches SpaceX has planned for Cape Canaveral may not be launched on their planned launch dates:
Cape Canaveral Space Force Station, Florida
| Date | Mission | Window | Pad | Notes |
|---|---|---|---|---|
| Feb 5 | Starlink 6-103 | 4:46 PM EST | SLC-40 | 29 Starlink sats; B1095 (5th); ASOG |
| NET Feb 6 | Starlink 6-104 | TBD | SLC-40 | 29 Starlink sats; B1077 (26th); JRTI |
| NET Feb 11 | Crew-12 | 6:00 AM EST | SLC-40 | Crew Dragon to ISS; RTLS landing |
| Late Feb | Starlink (TBD) | TBD | SLC-40 | Additional missions expected |
Legend: NET = No Earlier Than • ASOG/JRTI = Drone ships • RTLS = Return to Launch Site
Note: Schedule subject to change. Additional Starlink flights typically added throughout the month.
As of: February 3, 2026 at 8:32 AM EST
That includes Crew 12, which was planned for NET February 11. Before yesterday’s Artemis II Wet Dress Rehearsal and subsequent schedule shift to NET March 6 for NASA’s moon mission, the February 11 date was in question due to Artemis II, now that date is in peril while SpaceX investigates its latest anomaly.
This story is evolving. Stay tuned.
A few photos from February 1, 2026, of Artemis II from Beach Road at Kennedy Space Center.
On one of those rare nights where it is actually winter on the Space Coast, SpaceX launched a Falcon 9 from Space Launch Complex 40 at Cape Canaveral Space Force Station carrying the GPS III SV09 satellite to orbit for the US Space Force. Liftoff was at 11:53 PM ET into clear, chilly skies.
You must be logged in to post a comment.