{"id":27171,"date":"2026-05-23T08:01:58","date_gmt":"2026-05-23T08:01:58","guid":{"rendered":"https:\/\/readtrends.com\/en\/starship-v3-flight-12-splashdown\/"},"modified":"2026-05-23T08:01:58","modified_gmt":"2026-05-23T08:01:58","slug":"starship-v3-flight-12-splashdown","status":"publish","type":"post","link":"https:\/\/readtrends.com\/en\/starship-v3-flight-12-splashdown\/","title":{"rendered":"SpaceX Starship Flight 12 launch updates: Starship V3 Ship makes fiery splashdown in Indian Ocean as planned &#8211; Space"},"content":{"rendered":"<article>\n<p>On May 22, 2026, SpaceX launched its first Starship V3 test flight (Flight 12) from Starbase, Texas. The 408-foot vehicle lifted off in the evening, deployed 22 dummy Starlink satellites, and the Ship 39 upper stage reentered and made a planned fiery splashdown in the Indian Ocean after a controlled landing burn. The Super Heavy booster separated but did not complete a boost-back and impacted the Gulf of Mexico; neither stage was recovered. SpaceX deemed the core objectives of this suborbital qualification flight met, and teams celebrated at mission control.<\/p>\n<h2>Key Takeaways<\/h2>\n<ul>\n<li>Launch date\/time: May 22, 2026, no earlier than 6:30 p.m. EDT (2230 GMT); webcast began ~6:00 p.m. EDT (2200 GMT).<\/li>\n<li>Vehicle: Starship V3 configuration: Ship 39 atop Super Heavy Booster 19; first flight of V3 and first Starship launch since Oct. 2025 (seven-month gap).<\/li>\n<li>Engines: Booster powered by 33 Raptors; one first-stage Raptor and one upper-stage Raptor experienced outages during ascent; Ship completed mission with two of three planned landing engines firing for splashdown.<\/li>\n<li>Payload: 22 dummy Starlink satellites (including two \u2018Dodger Dogs\u2019 with cameras) were deployed successfully in a rapid sequence.<\/li>\n<li>Flight timeline: Booster separated and crashed in Gulf of Mexico roughly seven minutes after liftoff; Ship coasted in space then reentered, reaching peak heating near Mach 7, and splashed down off Western Australia ~65 minutes after liftoff.<\/li>\n<li>Recovery intent: No recovery was planned for Ship 39; splashdowns were nominal for test objectives and allowed thermal and reentry assessments.<\/li>\n<li>Operational tests: Teams skipped an in-space Raptor relight experiment; they exercised payload deployment speed, updated fuel transfer plumbing on Booster 19, and validated Pad 2 fueling and launch procedures.<\/li>\n<\/ul>\n<h2>Background<\/h2>\n<p>Flight 12 marked the debut of Starship Version 3, the latest iteration of SpaceX&#8217;s fully reusable heavy-lift vehicle intended for Moon landings and large payload launches. V3 incorporates several design changes from earlier vehicles, including upgraded Raptor 3-class engines, larger propellant tanks and a revised internal fuel-transfer architecture to feed 33 engines on the Super Heavy first stage. The program&#8217;s broader goal remains qualification for NASA&#8217;s Artemis lunar lander role and to provide high-volume Starlink and commercial launch capacity.<\/p>\n<p>Starship flight testing has been iterative since 2023, with a stepped approach: suborbital flights to exercise separation, deployment and reentry before orbital missions and routine recovery attempts. Pad 2 at Starbase was introduced to speed propellant loading and enable faster turnarounds; Flight 12 used Pad 2 and a refined wet dress rehearsal cadence that SpaceX said reduced tanker operations time by approximately 20% compared with Pad 1. The company also continues to use dummy payloads to evaluate deployment mechanisms and to fly instrumentation that photographs the vehicle during reentry.<\/p>\n<h2>Main Event<\/h2>\n<p>At T=0 on May 22, 2026, Starship V3 lifted off from Pad 2 and climbed on a powered ascent. Telemetry indicated one of the 33 Super Heavy engines was offline early in flight; controllers extended burn time on the remaining engines and maintained a trajectory within preflight bounds. Stage separation occurred as planned and Ship 39 continued on the planned suborbital arc despite losing one of its six upper-stage engines.<\/p>\n<p>Booster 19 did not complete its boost-back burn and impacted the Gulf of Mexico; this uncontrolled splashdown was not a recovery objective for Flight 12. Ship 39 achieved space, then deployed all 22 dummy Starlink satellites more quickly than on previous flights. Two of those satellites\u2014nicknamed the &#8216;Dodger Dogs&#8217;\u2014carried cameras and illumination to image the Ship&#8217;s heat shield during coasting and reentry phases.<\/p>\n<p>During reentry, SpaceX reported Ship 39 passed peak heating near Mach 7 and executed attitude and flap maneuvers to control aerodynamic loading. With two of its three landing engines operable, Ship performed a landing burn and deliberately tipped and broke up on impact with the ocean surface, producing a fiery splashdown as anticipated. Onboard sensors showed no obvious catastrophic heat-shield breach before impact.<\/p>\n<h2>Analysis &#038; Implications<\/h2>\n<p>This flight advanced several technical objectives despite partial engine losses. Rapid payload deployment demonstrated a maturing Starlink integration with Starship, shortening deployment timelines and validating the narrow slit-style payload bay for flat-stack satellites. The ability of Ship 39 to survive peak reentry heating without an obvious heat-shield burnthrough is significant for thermal protection development, though full recovery and refurbishment remain future steps.<\/p>\n<p>Engine-out performance on both stages underlines the program&#8217;s acceptance of non-nominal engine behavior during early test flights. SpaceX had analyzed engine-out scenarios; the vehicle remained within predicted trajectories, allowing planned downstream tests to continue. Still, repeated engine anomalies will be a focus for engineering teams as they push toward consistent, reusable operations.<\/p>\n<p>Operationally, Pad 2 and the revised fueling and transfer plumbing showed improved ground throughput, which SpaceX needs to meet cadence goals for Starlink production launches and Artemis mission timelines. However, the flight reinforced that achieving routine booster catch-and-reuse at Starbase remains an outstanding challenge: neither stage was recovered, and controlled returns to the pad will require further refinement of boost-back, entry and capture systems.<\/p>\n<h2>Comparison &#038; Data<\/h2>\n<figure>\n<table>\n<thead>\n<tr>\n<th>Parameter<\/th>\n<th>Starship V2 (typical)<\/th>\n<th>Starship V3 (Flight 12)<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Height<\/td>\n<td>~400 ft<\/td>\n<td>408 ft<\/td>\n<\/tr>\n<tr>\n<td>First-stage Raptors<\/td>\n<td>~33 (Raptor 2)<\/td>\n<td>33 (Raptor 3-class)<\/td>\n<\/tr>\n<tr>\n<td>Upper-stage Raptors<\/td>\n<td>3<\/td>\n<td>3 (one engine out during Flight 12)<\/td>\n<\/tr>\n<tr>\n<td>Payload deployed<\/td>\n<td>Up to 22 dummy Starlinks<\/td>\n<td>22 dummy Starlinks (including 2 camera-equipped)<\/td>\n<\/tr>\n<tr>\n<td>Planned flight duration<\/td>\n<td>~65 minutes (suborbital)<\/td>\n<td>~65 minutes (actual coast and reentry timeline)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n<p>The table highlights the incremental but material changes in V3: propulsion upgrades, refined ground operations and faster payload ejection. These metrics place Flight 12 in the context of iterative verification rather than full operational certification.<\/p>\n<h2>Reactions &#038; Quotes<\/h2>\n<blockquote>\n<p>&#8220;I wouldn&#8217;t call it nominal orbital insertion, but we&#8217;re in on a trajectory that we had analyzed, and it&#8217;s within bounds,&#8221;<\/p>\n<p><cite>Dan Huot, SpaceX spokesperson (live commentary)<\/cite><\/p><\/blockquote>\n<p>Huot offered real-time context after an engine dropout, emphasizing the flight-control team&#8217;s preparedness for off-nominal engine performance. His comments framed the remainder of the mission as a planned, analyzable outcome rather than an outright failure.<\/p>\n<blockquote>\n<p>&#8220;Ship 39 passed peak heating and executed its landing maneuvers; splashdown was as planned,&#8221;<\/p>\n<p><cite>SpaceX mission commentary<\/cite><\/p><\/blockquote>\n<p>That official commentary underscored that the company did not intend to recover the upper stage on this test flight and instead prioritized data collection on reentry and thermal performance.<\/p>\n<blockquote>\n<p>&#8220;This is historic. This is a major moment, y&#8217;all,&#8221;<\/p>\n<p><cite>Nicki Minaj (on-site attendee)<\/cite><\/p><\/blockquote>\n<p>Public figures and employees alike reacted enthusiastically; SpaceX teams were observed cheering after deployment and during post-reentry telemetry checks.<\/p>\n<aside>\n<details>\n<summary>Explainer: Starship testing and terms<\/summary>\n<p>Starship testing proceeds in iterative suborbital and orbital steps to validate separation, payload deployment, reentry heating and recovery techniques. The Super Heavy booster is the 1st stage with dozens of Raptor engines; the upper-stage Starship (the &#8220;Ship&#8221;) houses payloads and its own Raptor engines for orbital insertion and deorbit burns. A wet dress rehearsal is a full fueling and countdown simulation without ignition, used to validate ground systems and procedures. The &#8220;Dodger Dogs&#8221; are small Starlink prototypes fitted with lights\/cameras to photograph the Ship during coasting and reentry.<\/p>\n<\/details>\n<\/aside>\n<h2>Unconfirmed<\/h2>\n<ul>\n<li>Details and quality of imagery taken by the two camera-equipped &#8216;Dodger Dog&#8217; satellites remain to be verified publicly; SpaceX commentary indicated an attempt but full image release was not confirmed.<\/li>\n<li>An announced private Mars flyby commander (reported as Chun Wang) was mentioned in prelaunch commentary; the mission plan and timeline for that commercial announcement have not been publicly corroborated by SpaceX at the time of this report.<\/li>\n<li>Long-term heat-shield performance under repeated reentry cycles is still unproven; current telemetry suggests no obvious burnthrough for Ship 39 on Flight 12, but full inspection data is pending.<\/li>\n<\/ul>\n<h2>Bottom Line<\/h2>\n<p>Flight 12 successfully exercised multiple priority objectives for Starship V3: rapid payload deployment, Pad 2 fueling and operations, and reentry\/thermal performance data collection. While neither stage was recovered, the mission yielded engineering data that SpaceX will use to refine engine reliability, reentry protection and recovery procedures.<\/p>\n<p>The next steps will be thorough post-flight analysis of engine anomalies, heat-shield telemetry and imagery from the two camera-equipped payloads. Future flights will need to demonstrate consistent boost-back and pad-capture recoveries to meet SpaceX&#8217;s reusability and Artemis lunar lander timelines.<\/p>\n<h2>Sources<\/h2>\n<ul>\n<li><a href=\"https:\/\/www.space.com\/news\/live\/spacex-starship-flight-12-launch-updates-may-22-2026\" target=\"_blank\" rel=\"noopener\">Space.com live coverage<\/a> \u2014 Media: comprehensive live reporting and mission timeline.<\/li>\n<li><a href=\"https:\/\/www.spacex.com\/\" target=\"_blank\" rel=\"noopener\">SpaceX official website<\/a> \u2014 Official: mission commentary, webcast and company statements.<\/li>\n<li><a href=\"https:\/\/www.vantor.com\/\" target=\"_blank\" rel=\"noopener\">Vantor WorldView Legion imagery<\/a> \u2014 Commercial satellite imagery provider referenced for pad imagery prior to launch.<\/li>\n<\/ul>\n<\/article>\n","protected":false},"excerpt":{"rendered":"<p>On May 22, 2026, SpaceX launched its first Starship V3 test flight (Flight 12) from Starbase, Texas. The 408-foot vehicle lifted off in the evening, deployed 22 dummy Starlink satellites, and the Ship 39 upper stage reentered and made a planned fiery splashdown in the Indian Ocean after a controlled landing burn. The Super Heavy &#8230; <a title=\"SpaceX Starship Flight 12 launch updates: Starship V3 Ship makes fiery splashdown in Indian Ocean as planned &#8211; Space\" class=\"read-more\" href=\"https:\/\/readtrends.com\/en\/starship-v3-flight-12-splashdown\/\" aria-label=\"Read more about SpaceX Starship Flight 12 launch updates: Starship V3 Ship makes fiery splashdown in Indian Ocean as planned &#8211; Space\">Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":27170,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rank_math_title":"Starship V3 Flight 12: Indian Ocean splashdown \u2014 Space.com","rank_math_description":"SpaceX's Starship V3 (Ship 39) launched May 22, 2026 from Starbase, deployed 22 dummy Starlinks and executed a planned fiery splashdown in the Indian Ocean after reentry.","rank_math_focus_keyword":"Starship V3,Flight 12,splashdown,SpaceX,Starlink","footnotes":""},"categories":[2],"tags":[],"class_list":["post-27171","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-top-stories"],"_links":{"self":[{"href":"https:\/\/readtrends.com\/en\/wp-json\/wp\/v2\/posts\/27171","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/readtrends.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/readtrends.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/readtrends.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/readtrends.com\/en\/wp-json\/wp\/v2\/comments?post=27171"}],"version-history":[{"count":0,"href":"https:\/\/readtrends.com\/en\/wp-json\/wp\/v2\/posts\/27171\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/readtrends.com\/en\/wp-json\/wp\/v2\/media\/27170"}],"wp:attachment":[{"href":"https:\/\/readtrends.com\/en\/wp-json\/wp\/v2\/media?parent=27171"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/readtrends.com\/en\/wp-json\/wp\/v2\/categories?post=27171"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/readtrends.com\/en\/wp-json\/wp\/v2\/tags?post=27171"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}