Starship Flight Test 7 was the seventh Starship test flight. It was launched at January 16th 2025[1] and had another suborbital profile similar to the previous flights.
It became the second successful catch of a Super Heavy booster.[1] The flight was performed by Booster 14 (B14) and Ship 33 (S33), being the first Block 2 ship used on a flight test.[2]
Starship Flight 7 first appeared on an advisory released on December 27th.[3]
Starship 14/33 left the pad with an on time liftoff. On ascent, a part of the upper stage appeared to wear off. The ship hotstaged as nominal, and separated. The Booster did a successful boostback burn, although one of the 13 inner engines did not relight due to a low-power condition in the igniter system.[4] All thirteen engines were however reignited for the landing burn with the final part being performed by the three innermost engines. Booster 14 was successfully catched by the OLIT-1 tower without damage to it's 4 chine sections nor it's engines becoming the first Super Heavy to be recovered undamaged.
The Ship (S33) continued on its way to orbit, however a small fire was visible in the hinge area of a flap. Under a minute before SECO, the telemetry showed the loss of several engines as well as a fast decrease of CH4 levels. At approximately eight and a half minutes into flight, telemetry with the vehicle was completely lost, and according to the analysis from Scott Manley based on footage from Frank Taylor, it exploded around 3 minutes later.[5] SpaceX confirmed the loss of Ship 33. According to SpaceX, initial data "indicates a fire developed in the aft section of the ship, leading to a rapid unscheduled disassembly".[6] Elon Musk specified that the ship likely experienced an "oxygen/fuel leak in the cavity above the ship engine firewall that was large enough to build pressure in excess of the vent capacity".[7]
SpaceX later explained that approximately 2 minutes into the second stage's burn, a flash was observed in the aft section of the vehicle near one of the Raptor vacuum engines. This aft section, commonly referred to as the attic, is an unpressurized area between the bottom of the liquid oxygen tank and the aft heatshield. Sensors in the attic detected a pressure rise indicative of a leak after the flash was seen. Roughly two minutes later, another flash was observed followed by sustained fires in the attic. These eventually caused all but one of Starship’s engines to execute controlled shut down sequences and ultimately led to a loss of communication with the ship. Telemetry from the vehicle was last received just over eight minutes and 20 seconds into flight. Contact with Starship was lost prior to triggering any destruct rules for its Autonomous Flight Safety System, which was fully healthy when communication was lost. The vehicle was observed to break apart approximately three minutes after loss of contact during descent. Post-flight analysis indicates that the safety system did trigger autonomously, and breakup occurred within Flight Termination System expectations. The most probable root cause for the loss of ship was identified as a harmonic response several times stronger in flight than had been seen during testing, which led to increased stress on hardware in the propulsion system. The subsequent propellant leaks exceeded the venting capability of the ship’s attic area and resulted in sustained fires.[8]
As for the question whether debris of Ship 33 fell outside the previously indicated hazard zone, there were initially conflicting reports from the FAA and SpaceX. While the FAA pointed towards "an anomaly with debris falling outside of the identified closed aircraft hazard areas".[9] SpaceX stated that "any surviving pieces of debris would have fallen into the designated hazard area".[6] There weren't any reported injuries, despite the debris reaching populated areas. However, the FAA confirmed a report of minor damage to a car at the Turks and Caicos Island. As of 1 February 2025, no other damage was reported.[10] Furthermore, the FAA had to activate a Debris Response Area and slowed, diverted or held aircraft next to the area. Some planes requested diverts due to low fuel levels.[11]
Post launch updates[]
28/31 March 2025 - FAA closed Mishap Investigation[]
According to Space.com, the FAA has closed the Mishap Investigation on Flight Test 7 on 28 March 2025 as the agency announced in an emailed statement on 31 March 2025. According the final mishap report, "the probable root cause for the loss of the Starship vehicle was stronger than anticipated vibrations during flight [which] led to increased stress on, and failure of, the hardware in the propulsion system [...]." "SpaceX identified 11 corrective actions to prevent a reoccurrence of the event," the statement continued. "The FAA verified that SpaceX implemented corrective actions prior to Flight 8." The FAA also announced on the same day that they have closed the mishap investigation on Blue Origin's maiden launch of the New Glenn rocket.[12]
24 February 2025 - SpaceX web update[]
NEW YEAR. NEW SHIP. NEW LESSONS.
The seventh flight test of Starship and Super Heavy flew with ambitious goals, aiming to successfully repeat the core capability of returning and catching a booster while launching an upgraded design of the upper stage. While not every test objective was completed, the lessons learned will roll directly into future vehicles to make them more capable as Starship advances toward full and rapid reuse.
On January 16, 2025, Starship successfully lifted off at 4:37 p.m. CT from Starbase in Texas. At launch, all 33 Raptor engines on the Super Heavy booster started up successfully and completed a full duration burn during ascent. After powering down all but the three center engines on Super Heavy, Starship ignited all six of its Raptor engines to separate in a hot-staging maneuver and continue its ascent to space.
Following stage separation, Super Heavy initiated its boostback burn to propel the rocket toward its intended landing location. It successfully lit 12 of the 13 engines commanded to start, with a single Raptor on the middle ring safely aborting on startup due to a low-power condition in the igniter system. Raptor engines on upcoming flights have a pre-planned igniter upgrade to mitigate this issue. The boostback burn was completed successfully and sent Super Heavy back to the launch site for catch.
The booster successfully relit all 13 planned middle ring and center Raptor engines for its landing burn, including the engine that did not relight for boostback burn. The landing burn slowed the booster down and maneuvered it to the launch and catch tower arms at Starbase, resulting in the second ever successful catch of Super Heavy.
After vehicle separation, Starship's six second stage Raptor engines powered the vehicle along its expected trajectory. Approximately two minutes into its burn, a flash was observed in the aft section of the vehicle near one of the Raptor vacuum engines. This aft section, commonly referred to as the attic, is an unpressurized area between the bottom of the liquid oxygen tank and the aft heatshield. Sensors in the attic detected a pressure rise indicative of a leak after the flash was seen.
Roughly two minutes later, another flash was observed followed by sustained fires in the attic. These eventually caused all but one of Starship’s engines to execute controlled shut down sequences and ultimately led to a loss of communication with the ship. Telemetry from the vehicle was last received just over eight minutes and 20 seconds into flight.
Contact with Starship was lost prior to triggering any destruct rules for its Autonomous Flight Safety System, which was fully healthy when communication was lost. The vehicle was observed to break apart approximately three minutes after loss of contact during descent. Post-flight analysis indicates that the safety system did trigger autonomously, and breakup occurred within Flight Termination System expectations.
The most probable root cause for the loss of ship was identified as a harmonic response several times stronger in flight than had been seen during testing, which led to increased stress on hardware in the propulsion system. The subsequent propellant leaks exceeded the venting capability of the ship’s attic area and resulted in sustained fires.
Immediately following the anomaly, the pre-coordinated response plan developed by SpaceX, the FAA, and ATO (air traffic control) went into effect. All debris came down within the pre-planned Debris Response Area, and there were no hazardous materials present in the debris and no significant impacts expected to occur to marine species or water quality. SpaceX reached out immediately to the government of Turks and Caicos and worked with them and the United Kingdom to coordinate recovery and cleanup efforts. While an early end to the flight test is never a desired outcome, the measures put in place ahead of launch demonstrated their ability to keep the public safe.
SpaceX led the investigation efforts with oversight from the FAA and participation from NASA, the National Transportation Safety Board, and the U.S. Space Force. SpaceX is working with the FAA to either close the mishap investigation or receive a flight safety determination, along with working on a license authorization to enable its next flight of Starship.
As part of the investigation, an extended duration static fire was completed with the Starship flying on the eighth flight test. The 60-second firing was used to test multiple engine thrust levels and three separate hardware configurations in the Raptor vacuum engine feedlines to recreate and address the harmonic response seen during Flight 7. Findings from the static fire informed hardware changes to the fuel feedlines to vacuum engines, adjustments to propellant temperatures, and a new operating thrust target that will be used on the upcoming flight test.
To address flammability potential in the attic section on Starship, additional vents and a new purge system utilizing gaseous nitrogen are being added to the current generation of ships to make the area more robust to propellant leakage. Future upgrades to Starship will introduce the Raptor 3 engine, reducing the attic volume and eliminating the majority of joints that can leak into this volume.
Starship’s seventh flight test was a reminder that developmental progress is not always linear, and putting flight hardware in a flight environment is the fastest way to demonstrate how thousands of distinct parts come together to reach space. Upcoming flights will continue to target ambitious goals in the pursuit of full and rapid reusability.[13]
01 February 2025 - FAA statement - damage report[]
The FAA confirmed a report of minor damage to a car from the Starship explosion over Turks and Caicos Islands. That's the only confirmed rpt of damage. No injuries.[10]
17 January 2025 - FAA statement[]
The FAA is requiring SpaceX to perform a mishap investigation into the loss of the Starship vehicle during launch operations on Jan. 16. There are no reports of public injury, and the FAA is working with SpaceX and appropriate authorities to confirm reports of public property damage on Turks and Caicos.
During the event, the FAA activated a Debris Response Area and briefly slowed aircraft outside the area where space vehicle debris was falling or stopped aircraft at their departure location. Several aircraft requested to divert due to low fuel levels while holding outside impacted areas.
Background
A mishap investigation is designed to enhance public safety, determine the root cause of the event, and identify corrective actions to avoid it from happening again. The FAA will be involved in every step of the SpaceX-led mishap investigation process and must approve SpaceX’s final report, including any corrective actions. A return to flight is based on the FAA determining that any system, process, or procedure related to the mishap does not affect public safety.
A Debris Response Area is activated only if the space vehicle experiences an anomaly with debris falling outside of the identified closed aircraft hazard areas. It allows the FAA to direct aircraft to exit the area and prevent others from entering.[11]
17 January 2025 - Elon Musk on RUD cause[]
Preliminary indication is that we had an oxygen/fuel leak in the cavity above the ship engine firewall that was large enough to build pressure in excess of the vent capacity. Apart from obviously double-checking for leaks, we will add fire suppression to that volume and probably increase vent area. Nothing so far suggests pushing next launch past next month.[7]
The booster flight was a success, the ship flight was 1/4 successful, hence cup being ~5/8 full. New ship forward flaps, higher thrust engines and tile adherence on ascent were tested. Improved heat shield performance was the only major thing that wasn’t tested, along with the “Pez” payload dispenser. Probably solved in next month’s launch. The 9 meter diameter version of Starship will probably fly ~10,000 times, so this is barely a bump in the road. Doesn’t change the likely date at which Mars becomes self-sufficient.[14]
17 January 2025 - Web update and summary of the test[]
The first Starship flight test of 2025 flew with ambitious goals: seeking to repeat our previous success of launching and catching the world’s most powerful launch vehicle while putting a redesigned and upgraded Starship through a rigorous set of flight demonstrations.
It served as a reminder that development testing by definition is unpredictable.
On its seventh flight test, Starship successfully lifted off from Starbase in Texas at 4:37 p.m. CT on Thursday, January 16. At launch, all 33 Raptor engines powered the Super Heavy booster and Starship on a nominal ascent. Following a successful hot-stage separation, the booster successfully transitioned to its boostback burn, with 12 of the planned 13 Raptor engines relighting, to begin its return to the launch site.
Super Heavy then relit all 13 planned middle ring and center Raptor engines and performed its landing burn, including the engine that did not relight for boostback burn. The landing burn slowed Super Heavy down and maneuvered itself to the launch and catch tower arms, resulting in the second successful catch of a Super Heavy booster.
Following stage separation, the Starship upper stage successfully lit all six Raptor engines and performed its ascent burn to space. Prior to the burn’s completion, telemetry was lost with the vehicle after approximately eight and a half minutes of flight. Initial data indicates a fire developed in the aft section of the ship, leading to a rapid unscheduled disassembly.
Starship flew within its designated launch corridor – as all U.S. launches do to safeguard the public both on the ground, on water and in the air. Any surviving pieces of debris would have fallen into the designated hazard area. If you believe you have identified a piece of debris, please do not attempt to handle or retrieve the debris directly. Instead, please contact your local authorities or the SpaceX Debris Hotline at 1-866-623-0234 or at recovery@spacex.com.
As always, success comes from what we learn, and this flight test will help us improve Starship’s reliability as SpaceX seeks to make life multiplanetary. Data review is already underway as we seek out root cause. We will conduct a thorough investigation, in coordination with the FAA, and implement corrective actions to make improvements on future Starship flight tests.
The ship and booster for Starship’s eighth flight test are built and going through prelaunch testing and preparing to fly as we continue a rapid iterative development process to build a fully and rapidly reusable space transportation system.[6]
17 January 2025 - Other updates / announcements[]
Bill Nelson: "Congrats to @SpaceX on Starship’s seventh test flight and the second successful booster catch. Spaceflight is not easy. It’s anything but routine. That’s why these tests are so important—each one bringing us closer on our path to the Moon and onward to Mars through #Artemis."[15]
16 January 2025 - SpaceX and FAA[]
SpaceX: "Starship experienced a rapid unscheduled disassembly during its ascent burn. Teams will continue to review data from today's flight test to better understand root cause. With a test like this, success comes from what we learn, and today’s flight will help us improve Starship’s reliability."[16]
FAA to NASASpaceflight: "The FAA briefly slowed and diverted aircraft around the area where space vehicle debris was falling. Normal operations have resumed. A Debris Response Area is activated only if the space vehicle experiences an anomaly with debris falling outside of the identified closed aircraft hazard areas. It allows the FAA to direct aircraft to exit the area and prevent others from entering." The FAA thus confirmed that there was debris was outside of the hazard areas.[9]
Launch[]
Resources[]
- Official SpaceX stream: here
- Official SpaceX recap: here
- Videos from S33 debris: timeline-collage, explosion, debris over Turks and Caicos 1, debris, debris from the seas, debris over Turks and Caicos 2, debris over Turks and Caicos 3
- Everyday Astronaut: Recap
Timeline[]
- 09:06 Road closed
- 10:12 Chopsticks opened to launch position
- 10:19 Pad cleared
- 13:01 Boat clearing offshore underway: "Fast boats Genesis and Hannah Ray are busy in the hazard area offshore from Starbase."[17]
- 13:19 NASA's Gulfstream plane has recently taken off[18]
- 13:34 Pope vent stack active
- 14:21 | -02:15 | SpaceX: "Now targeting 4:37 p.m. CT for liftoff of Starship"[19]
- 15:20 | -01:16 | OLM and OLIT-1 venting began
- 15:32 | -01:05:00 | GO for propellant load. SpaceX: "The Starship team is go for prop load"[20]
- 15:45:52 | -00:51:08 | LOX and CH4 subcoolers venting began
- 15:51:06 | -00:45:54 | Cryo loading on ship began
- 15:43 | -00:41:24 | Cryo loading on booster began
- 15:55 | -00:32:00 | SpaceX stream started
- 16:17 | -00:19:40 | Engine chill. SpaceX: "Starship and Super Heavy’s combined 39 Raptor engines are chilling down in preparation for liftoff"[21]
- 16:37 | 00:00 | Lift off
- | +01:20 | Max-Q passed
- | +02:43 | Hot staging and separation
- | +06:56 | Catch of B14
- 16:51 | T+14:30 SpaceX confirms the loss of S33
- 16:58 Video of S33 debris emerging[22]
- 17:11 Booster transport stand started to roll out
- 17:17-17:21 B14 lowered about 2/3 way down
- 17:24 SpaceX update[16]
- 17:34 BQD opened, possibly for checkouts
- 17:40 Chopsticks centering pins centered B14
- 17:43 B14 lowered down further[1]
- 18:29 | +01:52 | B14 lowered onto OLM
- 18:47 | +02:10 | FAA issued an emergency NOTAM due to debris from S33 which fell outside the posted debris hazard zone[23]
- 22:31 | +05:54 | Vehicles returned to pad; booster transport stand rolling to pad
- 22:36 | +05:59 | Road opened
Stream Timeline[]
Stream Time | T-Time | Event
- 05:00 | none | Intro
- 06:28 | -00:33:38 | Moderated stream started; Kate Tice (Sr Quality Engineering Manager), Dan Huot (Communications), Jessie Anderson (Manufacturing Engineering Manager)
- 09:36 | -00:30:30 | Recap of previous flight, including video
- 11:29 | -00:28:32 | Summary of today's test and mission profile, which is similar to previous tests
- 13:13 | -00:26:53 | Summary of upgrades to the Ship (Forward flaps redesign; 2m taller ship - 52 meters; propulsion upgrades; avionics upgrades; catch fittings; stress testing with removed tiles; reentry experiments); tower upgrades (radar sensonrs on chopsticks for testing); 10 Starlink simulators
- 16:39 | -00:23:27 | Reflight of raptor engine SN314 - confirmation by SpaceX
- 17:15 | -00:22:49 | Status: Everything looks good, not tracking any issues - wheather within limits, vehicles, range will be clear
- 17:55 -00:22:11 | Preparations: Stacking over the weekend; site clearing; range teams deployed; Alignment on navigation, guidance and control; tank purges; pressure checkouts; QD checks; chopsticks tests; hydraulics loading on OLIT
- 19:02 | -00:21:04 | Prop load: 15:30 Go-no-go Poll; Ship [wrongly said booster] LOX load started at -00:45:00, CH4 at -00:43:00; Booster CH4 at -00:41:00, LOX at -00:35:00; will be wrapped up at -00:03:20 on Ship and -00:02:50 on Booster.
- 19:44 | -00:20:20 | Prop load: Currently ~50% on Booster, ~75% on Ship
- 20:55 | -00:19:11 | Info on propellant transfer missions in 2025; first trip to Mars planned for the end of 2026
- 21:55 | -00:18:11 | Basic rocket info on Ship and Booster vehicles; size comparison
- 25:42 | -00:14:24 | Info on Starlink's use on this flight and on Polaris Dawn
- 31:47 | -00:08:19 | Status: Ship main LOX and CH4 tanks fully loaded, header tanks underway; Booster fuelling to be completed soon
- 33:52 | -00:06:14 | Catch recap of Flight Test 5
- 35:31 | -00:04:35 | Status: Booster nearly fully loaded; Ship fully loaded; Range reported GO
- 36:31 | -00:03:35 | Current stat: B-LOX 91%, B-CH4 94%, S-LOX 98%, S-CH4 97%; Weather, Range, Vehicle GO
- 39:26 | -00:00:40 | "Passed through prop load gate"
- 39:36 | -00:00:29 | "Flight director is GO for launch"
- 39:46 | -00:00:21 | Fire suppression system started up
- 40:00 | -00:00:06 | Deluge system started up
- 40:04 | -00:00:02.7 | Inner 13 engines started up
- 40:05 | -00:00:01.63 | 15 out of 20 outer engines started
- 40:06 | -00:00:00.73 | Remaining 5 outer engines egnited
- 40:09 | +00:00:01.8 | Speed 1km/h - lift off!
- 40:10 | +00:00:03 | "We have lift off"
- 40:24 | +00:00:17 | "Vehicle is pitching downrange"
- 40:32 | +00:00:26 | "Booster chamber pressure is nominal"
- 40:51 | +00:00:45 | "Booster and Ship: avionics, power and telemetry nominal"
- 41:12 | +00:01:05 | "Vehicle is supersonic" (Telemetry reading at this timestamp: Speed: 1184 km/h, Altitude 9 km)
- 41:15 | +00:01:07.3 | Speed 1236 km/h
- 41:24 | +00:01:18 | "Max Q"
- 42:29 | +00:02:22 | Manual tower checks looking good
- 42:40 | +00:02:34.43 | 3 outer engines cut off
- 42:41 | +00:02:34.6 | 3 more outer engines cut off
- 42:41 | +00:02:34.77 | 3 more outer engines cut off
- 42:41 | +00:02:34.91 | 4 more outer engines cut off
- 42:41 | +00:02:35.14 | 4 more outer engines cut off
- 42:41 | +00:02:35.35 | last 2 outer engines cut off, 5 inner engines cut off
- 42:42 | +00:02:35.59 | 3 more inner engines cut off
- 42:42 | +00:02:35.79 | 2 more inner engines cut off; just the 3 innermost engines remained
- 42:46 | +00:02:39.2 | 3 Rvac engines on Ship ignited
- 42:47 | +00:02:39.5 | 3 Ship center engines ignited
- 42:48 | +00:02:41 | Stage separation
- 41:51 | +00:02:44.4 | 2 Booster inner (middle) engines started up (Boostback-Burn startup)
- 41:51 | +00:02:44.7 | 1 more inner engines started up
- 41:51 | +00:02:45.35 | 2 more inner engines started up
- 41:52 | +00:02:45.41 | 2 more inner engines started up
- 41:52 | +00:02:45.58 | 1 more inner engine started up
- 41:52 | +00:02:45.76 | 1 more inner engine started up (1 engine didn't ignite)
- tbc at 42:00
Telemetry and Analysis[]
According to SpaceX, initial data "indicates a fire developed in the aft section of the ship, leading to a rapid unscheduled disassembly"[6]. Elon Musk specified that the ship likely experienced an "oxygen/fuel leak in the cavity above the ship engine firewall that was large enough to build pressure in excess of the vent capacity"[7].
As for the question whether debris of Ship 33 fell outside the previously indicated hazard zone, there were initially conflicting reports from the FAA and SpaceX. While the FAA pointed towards "an anomaly with debris falling outside of the identified closed aircraft hazard areas"[9], SpaceX stated that "any surviving pieces of debris would have fallen into the designated hazard area"[6].
Compared to previous flight tests, Starship 14/33 showed a much slower ascent on both flight stages: The same velocity and altituted was only achieved at a later stage. This trend is more extreme in the second part of the flight. This is not explained by the mishap or an underperformance, but rather by the changes of Block 2 ship, specifically the increased propellant mass and the addition of simulation satellites.
Launch information[]
Mission[]
As per the FAA Launch License, the mission was planned to feature an attempted catch of Booster 14 (B14) and a soft splashdown of Ship 33 (S33) in the Indian Ocean[24]. Furthermore, there was going to be an attempted in space re-light demonstration, likely similar to that preformed by Ship 31 (S31) on Starship Flight Test 6 (it was originally intended for flight 3).[25]
In addition the mission carried 10 'Starlink simulators, similar in size and weight to next-generation Starlink satellites as the first exercise of a satellite deploy mission.[26] These dummy sattelites were going to be deployed onto the same suborbital trajectory as the ship and target a splashdown in the Indian Ocean. However, they were destroyed along the ship.
Upgrades[]
- Block 2 Ship (upper stage):
- Forward flaps with reduced size and shifted towards the tip and away from the shield with the goal to reduce exposure to reentry heating
- Redesign in propulsion system, including: 25% increase in propellant volume, vacuum jacketing of feedlines, new fuel feedline system for Rvac engines, improved propulsion avionics module
- Heat shield with latest generation tiles and backup layer
- Avionics redesign adding additional capabilities and redundancy: more powerful flight computer, integrated antennas, redesigned inertial navigation, integrated smart batteries, increase to more than 30 vehicle cameras[1]
- Hardware upgrades to launch and catch tower (OLIT-1), including protections to sensors that were damaged on flight 6 and resulted in the divert
Catch fitting on S33. c Mary
Aims[]
- Deployment of 10 Starlink simulators, which will splashdown in the Indian Ocean
- Relight of a single Raptor engine in space
- Experiments focused on ship return to launch site and catch:
- Removed tiles to stress-test vulnerable areas
- Test of metallic tile options, including one with active cooling
- Catch fittings installed to test their thermal performance
- Reentry profile to stress the structural limits of the flaps
- Test of radar sensors on tower chopsticks
- Reuse of flight proven hardware on the booster, including one Raptor engine flown on Starship flight test 5.[1] In the stream, SpaceX confirmed that the reused engine was SN314.
SpaceX Web Introduction[]
The seventh flight test of Starship is preparing to launch.
The upcoming flight test will launch a new generation ship with significant upgrades, attempt Starship’s first payload deployment test, fly multiple reentry experiments geared towards ship catch and reuse, and launch and return the Super Heavy booster.
A block of planned upgrades to the Starship upper stage will debut on this flight test, bringing major improvements to reliability and performance. The vehicle’s forward flaps have been reduced in size and shifted towards the vehicle tip and away from the heat shield, significantly reducing their exposure to reentry heating while simplifying the underlying mechanisms and protective tiling. Redesigns to the propulsion system, including a 25 percent increase in propellant volume, the vacuum jacketing of feedlines, a new fuel feedline system for the vehicle’s Raptor vacuum engines, and an improved propulsion avionics module controlling vehicle valves and reading sensors, all add additional vehicle performance and the ability to fly longer missions. The ship’s heat shield will also use the latest generation tiles and includes a backup layer to protect from missing or damaged tiles.
The vehicle’s avionics underwent a complete redesign, adding additional capability and redundancy for increasingly complex missions like propellant transfer and ship return to launch site. Avionics upgrades include a more powerful flight computer, integrated antennas which combine Starlink, GNSS, and backup RF communication functions into each unit, redesigned inertial navigation and star tracking sensors, integrated smart batteries and power units that distribute data and 2.7MW of power across the ship to 21 high-voltage actuators, and an increase to more than 30 vehicle cameras giving engineers insight into hardware performance across the vehicle during flight. With Starlink, the vehicle is capable of streaming more than 120 Mbps of real-time high-definition video and telemetry in every phase of flight, providing invaluable engineering data to rapidly iterate across all systems.
While in space, Starship will deploy 10 Starlink simulators, similar in size and weight to next-generation Starlink satellites as the first exercise of a satellite deploy mission. The Starlink simulators will be on the same suborbital trajectory as Starship, with splashdown targeted in the Indian Ocean. A relight of a single Raptor engine while in space is also planned.
The flight test will include several experiments focused on ship return to launch site and catch. On Starship’s upper stage, a significant number of tiles will be removed to stress-test vulnerable areas across the vehicle. Multiple metallic tile options, including one with active cooling, will test alternative materials for protecting Starship during reentry. On the sides of the vehicle, non-structural versions of ship catch fittings are installed to test the fittings’ thermal performance, along with a smoothed and tapered edge of the tile line to address hot spots observed during reentry on Starship’s sixth flight test. The ship’s reentry profile is being designed to intentionally stress the structural limits of the flaps while at the point of maximum entry dynamic pressure. Finally, several radar sensors will be tested on the tower chopsticks with the goal of increasing the accuracy when measuring distances between the chopsticks and a returning vehicle during catch.
The Super Heavy booster will utilize flight proven hardware for the first time, reusing a Raptor engine from the booster launched and returned on Starship’s fifth flight test. Hardware upgrades to the launch and catch tower will increase reliability for booster catch, including protections to the sensors on the tower chopsticks that were damaged at launch and resulted in the booster offshore divert on Starship’s previous flight test.
Distinct vehicle and pad criteria must be met prior to a return and catch of the Super Heavy booster, requiring healthy systems on the booster and tower and a final manual command from the mission’s Flight Director. If this command is not sent prior to the completion of the boostback burn, or if automated health checks show unacceptable conditions with Super Heavy or the tower, the booster will default to a trajectory that takes it to a landing burn and soft splashdown in the Gulf of Mexico. We accept no compromises when it comes to ensuring the safety of the public and our team, and the return will only take place if conditions are right.
The returning booster will slow down from supersonic speeds, resulting in audible sonic booms in the area around the landing zone. Generally, the only impact to those in the surrounding area of a sonic boom is the brief thunder-like noise with variables like weather and distance from the return site determining the magnitude experienced by observers.
This new year will be transformational for Starship, with the goal of bringing reuse of the entire system online and flying increasingly ambitious missions as we iterate towards being able to send humans and cargo to Earth orbit, the Moon, and Mars.[27]
Planned Countdown[]
All Times Approximate
| Hr/Min/Sec | Event |
|---|---|
| 01:15:00 | SpaceX Flight Director conducts poll and verifies GO for propellant load |
| 00:44:59 | Ship LOX (liquid oxygen) load underway |
| 00:42:20 | Ship fuel (liquid methane) load underway |
| 00:41:24 | Booster fuel load underway |
| 00:35:28 | Booster LOX load underway |
| 00:19:40 | Raptor begins engine chill on booster and ship |
| 00:03:20 | Ship propellant load complete |
| 00:02:50 | Booster propellant load complete |
| 00:00:30 | SpaceX flight director verifies GO for launch |
| 00:00:10 | Flame deflector activation |
| 00:00:03 | Raptor ignition sequence begins |
| 00:00:00 | Excitement guaranteed |
Planned flight test timeline[]
All Times Approximate
| Hr/Min/Sec | Event |
|---|---|
| 00:00:02 | Liftoff |
| 00:01:02 | Max Q (moment of peak aerodynamic stress on the rocket) |
| 00:02:32 | Super Heavy MECO (most engines cut off) |
| 00:02:40 | Hot-staging (Starship Raptor ignition and stage separation) |
| 00:02:46 | Super Heavy boostback burn startup |
| 00:03:29 | Super Heavy boostback burn shutdown |
| 00:03:31 | Hot-stage jettison |
| 00:06:26 | Super Heavy is transonic |
| 00:06:35 | Super Heavy landing burn start |
| 00:06:55 | Super Heavy landing burn shutdown and catch |
| 00:08:53 | Starship engine cutoff |
| 00:17:33 | Payload deploy demo |
| 00:37:33 | Raptor in-space relight demo |
| 00:47:14 | Starship entry |
| 01:03:12 | Starship is transonic |
| 01:04:25 | Starship is subsonic |
| 01:06:13 | Landing flip |
| 01:06:19 | Landing burn |
| 01:06:39 | An exciting landing! |
Timeline of Announcements and Updates[]
16 January 2024[]
Flight closure scheduled (9am-10:30pm)
B14 transport stand staged at ring yard
Jeff Bezos: "Good luck today @elonmusk and the whole spacex team!!"[28]
Gav Cornwell: "It appears that the SpaceX employee transport hovercraft service has ceased operations ahead of today's launch."[29]
SpaceX: "Now targeting 4:37 p.m. CT for liftoff of Starship"[19]
15 January 2025[]
Eddie Treviño: "We have received notice that the 7th Starship launch has been postponed until tomorrow, Thursday, January 16th. The Isla Blanca Park Boat ramp will be open today."[30]
SpaceX: "Due to weather, we're now targeting Thursday, January 16 for Starship's seventh flight test. The 60-minute launch window opens at 4 p.m. CT."[31]
14 January 2025[]
LR11000X and LR11000 cranes lowered at the launch site ahead of IFT-7
SpaceX: "Starship's seventh flight test is targeted to launch Wednesday, January 15, with a 60-minute launch window opening at 4 p.m. CT. The Starbase team is keeping a close eye on weather conditions"[32]
Cameron County: Sound advisory issued[33]
13 January 2025[]
Flight closure for Jan 15 cancelled
Flight closure for Jan 15 re-added in a document form; alternatives on Jan 16 and Jan 17
12 January 2025[]
Starship 14/33 restacked
11 January 2025[]
Starship 14/33 destacked
Several navigational warnings for 13 January cancelled[34]
NOTMARs replaced by new ones that still include 13 January.[35]
SpaceX: "Now targeting Wednesday, January 15 for the seventh flight test of Starship"[36]
10 January 2025[]
TFR published for 13 Jan (FAA); NOTAM for US side of Gulf of Mexico published for 13 Jan[37]
FAA advisory: Primary date 13 Jan, backup date 14 Jan[38]
Flight road closures issued for 13-15 January (9am-10.30pm)
Two navigational warnings for Indian Ocean cancelled[39]
Starship 14/33 WDR
09 January 2025[]
IFT-7: NOTAM for 14 Jan updated to 13 Jan[40]
Starship 14/33 stacked; S33 lifted onto B14
08 January 2025[]
Nav warning posted with NET date slipped to January 13th.[41]
OLIT-1: Chopsticks performed additional catch testing for several hours ahead of IFT-7
SpaceX: "The seventh flight test Starship of is preparing to launch as soon as Monday, January 13. Teams at Starbase are keeping an eye on weather conditions for preflight operations"[42]
NOTAM for Indian Ocean issued, starting on 14 Jan[43]
07 January 2025[]
Early morning, the first Starlink mass simulator was loaded into S33 payload bay, after first tests were successful. Later, more simulators followed.
New warnings for flight test issued for the Indian Ocean, still with a first target on 10 Jan.[44]
Newly issued ATO alerts from the FAA show that Starship has slipped to Jan 11th for the primary launch day.[3]
Last, 10th, Starlink simulator loaded into S33's payload bay PEZ.
B14 hot stage ring reinstalled.
On an X live Elon Musk said that Starship's 7th flight is delayed to sometimes next week, by 3/4 days.[45] [46]
06 January 2025[]
SpaceX's LR11000X crane moved to pad A.
"Starlink Simulators spotted inside Starfactory! 10 in total visible that are possibly the 10 to be loaded into Starship 33's PEZ Dispenser for Starship test flight 7." (Starship Gazer)[47]
A DOD 6055 Fire Division 1 Mass Explosion Sign (Orange 1 on left side) has been placed on the entrance to MB2, likely indicating FTS installation has begun on S33
Ship transport stand entered mega bay 2, S33 lifted onto it
Hot staging ring removed from B14 again
05 January 2025[]
SpaceX's LR11000X crane moved to pad A
"Starlink Simulators spotted inside Starfactory! 10 in total visible that are possibly the 10 to be loaded into Starship 33's PEZ Dispenser for Starship test flight 7."[48]
03 January 2025[]
SpaceX released the launch information for flight test 7
NOTAMs were posted for the Mexico side.[49]
- January 10, 22:00-23:38 UTC
- January 11, 13:00-14:38 UTC
- January 12, 22:00-23:38 UTC
- January 13, 22:00-23:38 UTC
- January 14, 22:00-23:38 UTC
- January 15, 22:00-23:38 UTC
- January 16, 22:00-23:38 UTC
The OLM stabilizer pins were removed ahead of the flight attempt.[50]
03 January 2025 - SpaceX Website Update[]
SpaceX published their Flight 6 recap[51] and Flight 7 overview detailing the full mission profile, including the addition of deploying 10 Starlink simulator, and highlighting a large number of upgrades primarily across the Block 2 Ship such as the re-designed forward flaps, new avionics, batteries, star tracking, inertial measurement, vacuum jacketing and a number of other imrpovements.[52] [53]
02 January 2025[]
Flightaware shows NASA Gulfstream arriving in Honolulu[54]
"SpaceX is apparently planning to reuse the 314 Raptor engine."[55]; confirmed by Elon Musk[56]
B14 lifted and installed on OLM of OLIT-1 ahead of IFT-7; FTS installed
30 December 2024 — NET date[]
Elon Musk confirmed the NET date of January 10th 2025.[57]
27 December 2024 — Advisory[]
Starship Flight 7 appeared on an advisory released on December 27th, with a primary date of January 10th 2025 at 22:00 UTC, or 4 pm CDT. There are backup opportunities that extend until the 15th of January 2025. [58] Possible launch times are[59]:
- Jan 10, 4pm
- Jan 11, 7am
- Jan 12-16, 4pm
17 December 2024 — FAA Launch License[]
The FAA approved the Starship Flight 7 mission and allowed for multiple launches of this configuration and flight profile, involving a booster catch and ship soft splashdown in the Indian Ocean.[60] Statement from the FAA to NSF[61]:
"Today, the FAA issued a license modification authorizing SpaceX to launch multiple missions of the Starship/Super Heavy vehicle on the Flight 7 mission profile and vehicle configuration. The FAA determined SpaceX met all safety, environmental and other licensing requirements for the suborbital test flight.
'The FAA continues to increase efficiencies in our licensing determination activities to meet the needs of the commercial space transportation industry,' said the Associate Administrator for Commercial Space Transportation Kelvin B. Coleman. 'This license modification that we are issuing is well ahead of the Starship Flight 7 launch date and is another example of the FAA's commitment to enable safe space transportation!
The Flight 7 mission profile involves launch of the combined Starship/Super Heavy vehicle from Boca Chica, Texas, a return to the launch site of the Super Heavy booster rocket for a catch attempt by the launch tower, and a water landing of the Starship vehicle in the Indian Ocean west of Australia. Please contact SpaceX for information about its planned launch date.
The SpaceX Starship program operates under an FAA-issued Part 450 launch license."
03 December 2024 — FCC approval[]
The FCC approved flight test 7: “License granted: Space Exploration Technologies Corp. (SpaceX) Dates: 12/14/2024-06/14/2025 Purpose: Launch vehicle communications for test flight mission launching from Starbase, TX. Th(…)”[62]
25 November 2024 — NASA Documents filed with FAA[]
Documentation that NASA filed with the FAA suggests that as of November 15 SpaceX were targeting NET January 11, 2025, for a suborbital trajectory flight 7.[63][64]
19 November 2024 — Ship Splashdown[]
According to Elon Musk, SpaceX will perform one more Ocean Splashdown after Flight Test 6. If this goes well, they could try to catch the ship on the next test (Flight test 8): "We will do one more ocean landing of the ship. If that goes well, then SpaceX will attempt to catch the ship with the tower.”[65]
06 November 2024 — Block 2 Ship[]
SpaceX's post on their website ahead of flight test 6 confirmed speculation that on flight test 7, a Block 2 ship will be launched: “Future ships, starting with the vehicle planned for seventh flight test, will fly with significant upgrades including redesigned forward flaps, larger propellant tanks, and the latest generation tiles and secondary thermal protection layers as we continue to iterate towards a fully reusable heat shield.”[2]
Gallery[]
References[]
- ↑ 1.0 1.1 1.2 1.3 https://www.spacex.com/launches/mission/?missionId=starship-flight-7
- ↑ 2.0 2.1 https://www.spacex.com/launches/mission/?missionId=starship-flight-6
- ↑ 3.0 3.1 https://www.cadenaois.org/vpublic_anspdetail.jsp?view=15
- ↑ https://www.spacex.com/updates/#flight-7-report
- ↑ https://youtu.be/vfVm4DTv6lM?si=c-heve2wNIMC33OH&t=677
- ↑ 6.0 6.1 6.2 6.3 6.4 https://www.spacex.com/launches/mission/?missionId=starship-flight-7
- ↑ 7.0 7.1 7.2 https://x.com/elonmusk/status/1880060983734858130
- ↑ https://www.spacex.com/updates/
- ↑ 9.0 9.1 9.2 https://x.com/BCCarCounters/status/1880056482508484631
- ↑ 10.0 10.1 Marcia Smith: https://x.com/SpcPlcyOnline/status/1885750465205248160
- ↑ 11.0 11.1 https://www.faa.gov/newsroom/statements/general-statements
- ↑ https://www.space.com/space-exploration/launches-spacecraft/faa-closes-investigation-into-spacex-starship-flight-7-explosion (Space.com, 31 March 2025)
- ↑ https://www.spacex.com/updates/
- ↑ https://x.com/elonmusk/status/1880159432308408468
- ↑ https://x.com/SenBillNelson/status/1880057863135248587
- ↑ 16.0 16.1 https://x.com/SpaceX/status/1880033318936199643
- ↑ https://x.com/SpaceOffshore/status/1879963793465204876
- ↑ https://www.flightaware.com/live/flight/NASA5
- ↑ 19.0 19.1 https://x.com/SpaceX/status/1879987136268739022
- ↑ https://x.com/spacex/status/1880005238385787336
- ↑ https://x.com/SpaceX/status/1880016917408440398
- ↑ https://x.com/i/status/1880026262254809115
- ↑ https://x.com/DerekdotSpace/status/1880053699667718446
- ↑ https://x.com/BCCarCounters/status/1869146032099188743
- ↑ https://x.com/BCCarCounters/status/1869146809316323719
- ↑ https://www.spacex.com/launches/mission/?missionId=starship-flight-7
- ↑ https://www.spacex.com/launches/mission/?missionId=starship-flight-7
- ↑ https://x.com/JeffBezos/status/1879943522863968306
- ↑ https://x.com/SpaceOffshore/status/1879998047209365750
- ↑ https://x.com/JudgeTrevino/status/1879543356529037573
- ↑ https://x.com/SpaceX/status/1879549071276531906
- ↑ https://x.com/spacex/status/1879290453897724281
- ↑ https://www.cameroncountytx.gov/spacex/
- ↑ Adrian Beil: https://x.com/BCCarCounters/status/1878232546023997653
- ↑ Bryan Starship: https://x.com/bryanstarship/status/1878243223228850528
- ↑ https://x.com/spacex/status/1878281148893102238?s=46
- ↑ FAA: https://notams.aim.faa.gov/notamSearch/createNotamPdf?transactionid=75006102
- ↑ FAA: https://www.fly.faa.gov/adv/adv_spt.jsp
- ↑ Adrian Beil: https://x.com/BCCarCounters/status/1877870659100987707
- ↑ FAA: https://notams.aim.faa.gov/notamSearch/createNotamPdf?transactionid=74993581
- ↑ https://discord.com/channels/577909263012462594/732227281006755922/1326478481378381884
- ↑ https://x.com/SpaceX/status/1877054585388355812
- ↑ https://notams.aim.faa.gov/notamSearch/createNotamPdf?transactionid=74975164
- ↑ https://discord.com/channels/577909263012462594/732227281006755922/1326139691518394390
- ↑ https://x.com/i/broadcasts/1zqKVYPoZaMxB
- ↑ https://fixupx.com/VickiCocks15/status/1876707122244686201
- ↑ https://x.com/StarshipGazer/status/1876139761255211318
- ↑ Starship Gazer: https://x.com/StarshipGazer/status/1876139761255211318
- ↑ https://notams.aim.faa.gov/notamSearch/createNotamPdf?transactionid=74887191
- ↑ https://discord.com/channels/577909263012462594/732227281006755922/1324850911754981578
- ↑ https://www.youtube.com/watch?v=CMGiNKcVSek
- ↑ https://www.spacex.com/launches/mission/?missionId=starship-flight-7
- ↑ https://x.com/spacex/status/1875218268857958468
- ↑ https://www.flightaware.com/live/flight/N95NA
- ↑ Space Sudoer: https://x.com/spacesudoer/status/1860679421625336170
- ↑ https://x.com/elonmusk/status/1874974714680287531
- ↑ https://x.com/elonmusk/status/1873862900915593679
- ↑ https://www.cadenaois.org/vpublic_anspdetail.jsp?view=15
- ↑ https://x.com/lewisknaggs42/status/1872641612129681544
- ↑ https://x.com/BCCarCounters/status/1869146032099188743
- ↑ https://x.com/BCCarCounters/status/1869146032099188743
- ↑ https://x.com/fccspace/status/1863941286979420374
- ↑ https://x.com/Alexphysics13/status/1860842070455246865
- ↑ https://www.regulations.gov/document/FAA-2024-2595-0001
- ↑ https://x.com/elonmusk/status/1859036912348262787