SpaceX has a new launch window for Starship, and this one matters beyond the usual spectacle from Starbase. The Federal Aviation Administration closed its required investigation into Starship Flight 12 on July 13, saying there were no reports of public injury or public property damage and clearing SpaceX to proceed with Flight 13. The target is no earlier than Thursday, July 16. The mission is not going to the Moon, and it will not carry a lunar lander. Still, it is one of the most direct near-term tests of the vehicle family NASA is counting on for Artemis. Flight 13 is where Starship V3 has to show that fixes to hot staging, engine relight logic, Raptor reliability, payload operations, and controlled descent are moving from analysis into flight behavior. AI-generated image Flight 13 will carry 20 Starlink V3 test satellites on a suborbital trajectory, a payload operations step that also tests Starship's bay, deployment, and inspection workflow. Credit: AI illustration What Changed After Flight 12 Flight 12 launched on May 22 with the first Starship V3 hardware, an upgraded version of the vehicle with larger tanks, revised structures, Raptor 3 engines, and design changes aimed at higher launch efficiency. It reached several important objectives, including stage separation and an upper-stage trajectory that survived the loss of one vacuum-optimized engine about 40 seconds after separation. That engine-out performance was useful data. The problem was the booster return. SpaceX's post-flight analysis, summarized in public updates, traced a major Super Heavy attitude error to the timing and sequencing of Ship engine startup during hot staging. After separation, the booster ended up roughly 90 degrees from its expected orientation. Five of 33 engines then failed to relight for the boostback burn, which ended early. Super Heavy did not reach the planned Gulf splashdown zone. The upper stage had its own unfinished business. Ship made it to its planned suborbital trajectory, but the engine loss prevented a planned in-space relight attempt. That relight is not a nice-to-have item. A vehicle that has to perform complex orbital operations, rendezvous, docking, tanker flights, and eventual lunar transport has to prove that engines can restart reliably after coast phases, thermal changes, and propellant settling events. Why the FAA Closure Matters The FAA's July 13 closure does not certify Starship as operational. It means the agency accepted the investigation path and corrective actions well enough for Flight 13 to proceed under SpaceX's license process. For Artemis, that distinction matters: the regulatory gate reopened, but the engineering proof still has to happen in flight. For Flight 13, SpaceX says it has modified the Ship startup sequence, made hardware updates to Super Heavy, and updated engine alarms and abort settings to better match the multi-engine conditions seen in flight. The company also plans further Raptor reliability improvements in later versions, which is a reminder that Flight 13 is not the end of V3 development. It is the next data point in a compressed campaign. The Flight 13 Checklist SpaceX's public objectives for Flight 13 read like a test plan for the whole Starship transportation system. The first goal is straightforward ascent and clean stage separation. After that, Super Heavy is expected to perform a complete boostback burn and target a soft splashdown in the Gulf. Ship will deploy 20 Starlink V3 satellites, attempt an in-space Raptor relight, then descend for a soft splashdown in the Indian Ocean. July 16 No-earlier-than target for Flight 13 20 Starlink V3 test satellites planned 6 Payload cameras for heatshield inspection 33 Super Heavy Raptor engines 1 Planned in-space Raptor relight 2027 Target year for Artemis III docking tests The payload piece is new. Flight 12 carried Starlink V3 mass simulators and two camera-equipped satellites for inspection work. Flight 13 is expected to carry the first functional Starlink V3 test satellites on Starship, including six with cameras to inspect Ship's heatshield tiles and exterior condition while in space. Because the vehicle is flying a suborbital path, the satellites are expected to reenter and burn up shortly after deployment. That may sound distant from lunar landing. It is not. Payload deployment checks door timing, bay environment, attitude control, sequence automation, telemetry, power behavior, and vehicle pointing. A lunar Starship will need all of those disciplines, plus more. Before Starship can be a lander, it has to be a reliable spacecraft that opens, points, relights, navigates, survives heating, and returns data without drama. Why NASA Is Watching NASA's current Artemis plan gives Starship two different jobs. First, a boilerplate Starship V3 equipped with a docking adapter is expected to support Artemis III in 2027, when Orion astronauts will practice rendezvous and docking operations in low Earth orbit with commercial lunar lander test articles. Then, for Artemis IV in 2028, NASA expects a crew-capable Starship-derived Human Landing System to be ready for the first Artemis lunar surface mission. AI-generated image Artemis III is now expected to test docking and crew interfaces with commercial lander hardware in low Earth orbit before NASA attempts the next crewed lunar landing. Credit: AI illustration Flight 13 does not directly demonstrate docking. It does not transfer propellant. It does not enter a stable orbit. It does not test crew systems. But the mission touches several layers beneath those requirements. Hot staging has to be predictable. Engines have to relight. The upper stage has to hold attitude and thermal margins. The heatshield inspection workflow has to produce useful data. Descent guidance has to keep improving if SpaceX wants to move from ocean splashdowns to tower catches. The Artemis version of Starship also depends on orbital refilling, one of the hardest remaining elements in the architecture. A lunar landing mission requires many tanker flights to fill a depot or directly refuel the lander before it leaves Earth orbit. That chain assumes Starship can launch repeatedly, reach orbit, rendezvous, manage cryogenic propellants, transfer them in microgravity, and keep them usable long enough to depart for the Moon. A clean Flight 13 will not prove that chain, but a messy one would push it further away. Flight 13 Objective Near-Term Test Artemis Relevance Clean hot staging Stage separation without major booster attitude error Required for high-cadence launches and tanker flights Booster boostback Complete relight and controlled Gulf splashdown Builds toward recoverable, repeatable launch operations Payload deployment Release 20 Starlink V3 test satellites Validates bay operations, sequencing, pointing, and telemetry Ship relight Restart one Raptor engine after coast Foundational for orbital operations and future departure burns Ship splashdown Controlled descent and Indian Ocean soft landing Feeds reentry, thermal protection, and recovery confidence The Schedule Pressure Is Real NASA has already changed the Artemis sequence to reduce mission risk. Artemis III is now a low Earth orbit docking rehearsal, not a Moon landing. The current plan calls for Orion to meet Blue Origin's Blue Moon test article first, then a Starship V3 boilerplate with a docking adapter. If the sequence works, Artemis IV would carry the first crewed lunar landing attempt in late 2028. That schedule leaves little slack. SpaceX still has to demonstrate a stable orbital Starship mission, propellant transfer, docking-related hardware, repeated tanker operations, lander-specific systems, and an uncrewed lunar landing demonstration before crew rides the system to the surface. Blue Origin has its own parallel path with Blue Moon. NASA wants competition and redundancy, but redundancy only helps if both vehicles mature fast enough to enter the flight program. AI-generated image Flight 13 fol