SpaceX completed a full-stack wet dress rehearsal and launch-countdown simulation on Booster 21 and Ship 41 at Starbase Pad 2 on September 24, 2026 — after stacking on September 23. SpaceX framed opportunistic full-stack testing as keeping Flight 14 “on track for Monday, Sept. 28, pending regulatory approval.” SpaceX confirmed on X on September 24 that the launch rehearsal was complete. A wet dress fuels the vehicle and walks launch-day steps without lighting engines. That is reportable pad readiness. It is not a countdown clock, not an FAA flight license in hand, and not proof Starship will lift on September 28.

NASASpaceflight — SpaceX Conducts Launch Rehearsal ahead of Starship Flight 14

What the video shows

Required embed for this package: NASASpaceflight — “SpaceX Conducts Launch Rehearsal ahead of Starship Flight 14” (YouTube NfbDAOR5NSU), published about September 23, 2026, with coverage running into the September 24 wet dress window. House note: this is launch-rehearsal / WDR desk coverage — propellant load, countdown simulation, and pad operations on the stacked Booster 21 + Ship 41 vehicle at Orbital Launch Pad 2 — not a SpaceX webcast of liftoff and not an FAA license grant. Use it as the viewer’s look at the readiness step that moved after stacking. Prefer this embed with hedges over NONE because it matches the locked SpaceX Friday Flagship 1 mix. Do not let the title or livestream chat upgrade “rehearsal” into “launched,” and do not substitute the Sep 23 stack video c11hl-VAtN8 as this pack’s lead.

What NSF typically surfaces on a WDR day is the visual language of a launch campaign without the irreversible step: frost on tanks, pad activity, countdown clocks that stop short of engine start, and commentary that separates “practice the timeline” from “commit to flight.” That distinction is the whole point of this flagship. Readers who only skim YouTube titles will miss it. AISN’s job is to keep the practice label glued to the footage.

What’s new

AI Shift News already published a September 23 package when Ship 41 stacked on Booster 21 at Pad 2: integration progress is not a September 28 orbit receipt. That post is a soft-re-cover ban for the lead. What is new is the full-stack wet dress / launch rehearsal on that same stack — SpaceX’s “Sunrise at Starbase” framing of opportunistic full-stack testing ahead of Flight 14, and Space.com’s September 24 reporting that SpaceX later announced the launch rehearsal complete. The scarce journalistic job is to put “rehearsal done” and “pending regulatory approval” in the same paragraph without pretending either line is a range go or a license stamp.

The schedule context also hardened in public desks: Monday, September 28, 2026, with a 75-minute window opening at 7:15 a.m. Central (8:15 a.m. Eastern). That window is still conditional. SpaceX’s own quoted language keeps the regulatory clause explicit. AISN will not quietly drop that clause because a wet dress looked clean on camera.

What evidence supports

Stack then WDR — the readiness sequence. Spaceflight Now and Space.com establish the September 23 stack of Ship 41 on Booster 21 at Pad 2. Space.com’s September 24 live file then documents wet dress rehearsal underway, quoting SpaceX: opportunistic full-stack testing planned, Flight 14 on track for Monday, September 28, pending regulatory approval. A later Space.com story reports SpaceX’s afternoon announcement that the launch rehearsal was complete. House fence: completion of a wet dress is a real readiness receipt. It is not engine ignition and not a flight license.

What a wet dress actually tests. In plain English, teams load cryogenic propellant, walk the countdown timeline, verify ground systems and vehicle responses, and stop short of lighting Raptors. Space.com’s rehearsal explainer matches that definition. For Flight 14 specifically, the test matters because the vehicle is now the full orbital-attempt stack — not a prior static-fire campaign treated as today’s news. Soft-touch earlier static fires and the Booster 21 pad roll only as background. They are not the lead.

NET Sep 28 still carries the regulatory hedge. Every honest schedule sentence in this pack must keep “pending regulatory approval” or equivalent FAA-license-modification language beside September 28. The FAA’s Starship stakeholder materials and major-desk reporting distinguish environmental paperwork (including Final Tiered EA / FONSI/ROD items discussed around Pacific contingency trajectories) from the launch authorization itself. House fence: FONSI ≠ flight license. Temporary flight restrictions around Starbase are also not a license. WDR success does not fill that gap.

What is still missing (confirmed fence). No AISN claim in this pack that the FAA has granted the Flight 14 orbital license modification; no claim weather or range are go for Monday; no claim Flight 14 has lifted or orbited; no treatment of NSF chat speculation as SpaceX IR; no soft-re-lead of the Sep 23 stack video as if stacking were still the fresh headline.

What it does not prove

  • It does not prove Starship will launch on September 28. NET plus a completed wet dress is still conditional on regulatory approval, range, weather, and vehicle health.
  • It does not prove the FAA has cleared the orbital flight profile. Environmental findings and stakeholder processes are not the same instrument as launch authorization.
  • It does not prove WDR “clears the path” in a legal sense. It clears a pad-operations box. Licensing and range remain separate boxes.
  • It does not authorize redoing the Sep 23 stack flagship as today’s lead or swapping in c11hl-VAtN8 for this slot’s video.
  • It does not prove orbit, Starlink V3 deploy, or heatshield performance. Those belong to the mission-architecture and bakery flagships — still planned, not flown.

Why this matters

For practical readers following Starship as an operations and evidence story — not as countdown-culture entertainment — the scarce signal is often which pad step actually changed. This week clears that bar: after stacking, SpaceX completed a full-stack wet dress on September 24 and publicly tied the Monday window to regulatory approval. That is useful planning context for anyone watching the first planned Starship orbital attempt — if you refuse to confuse fueling practice with a launch commit.

It also matters for the SpaceX Friday franchise specifically. AISN’s house rule on Flight 14 has been consistent: hardware progress ≠ launch. Stack ≠ countdown clock. WDR ≠ license. This flagship updates the rule without abandoning it: rehearsal is real; Monday liftoff is still unproven.

What happens next

  1. FAA / license modification track — whether public desks report an approved orbital-profile authorization before the Monday window.
  2. Pad recycle after WDR — safing, inspections, any anomaly work SpaceX or NSF surface before a real countdown.
  3. Range, weather, and TFR posture — operational constraints that sit beside licensing.
  4. SpaceX NET language — whether “pending regulatory approval” stays attached to September 28 or the date slips again.
  5. Mission objectives still unflown — first planned orbit, 26 Starlink V3 deploy, Pacific Ship splashdown, Gulf booster splashdown — tracked in Flagship 2, not asserted here as done.

How to read SpaceX’s “on track” language. “On track for Monday, Sept. 28, pending regulatory approval” is a compound sentence. The first clause is targeting. The second clause is a condition. AISN treats both halves as Confirmed company messaging as quoted by major desks — and refuses to promote the first half into a guarantee by deleting the second. Creator packaging that truncates the hedge is Claim, not Confirmed. The same discipline applies to NSF titles that say “launch rehearsal” without repeating the regulatory gate in every lower-third.

Pad 2 context without redoing the stack lead. Readers who missed Wednesday’s stack file need one clean sentence of background: Ship 41 sits on Booster 21 at Orbital Launch Pad 2 after the September 23 mate. That sentence is scaffolding. It is not permission to rebuild the stack narrative, recycle c11hl-VAtN8, or lead with older Booster 21 roll footage. The fresh receipt is the wet dress on that stack. Integration got the vehicle to the rehearsal; rehearsal is what this Friday flagship is for.

Why splashdown and catch language stays out of the WDR lead. Flight 14’s published profile plans Gulf soft splashdown for Super Heavy and Pacific splashdown for Ship — no tower catch on this attempt. That architecture matters, and Flagship 2 owns it. Inserting catch nostalgia into a WDR story is how desks accidentally imply Monday’s attempt is an operational catch flight. It is not. Keep catch history as optional color only if needed to explain why splashdowns are still planned; do not let it steal the rehearsal fence.

Operator checklist while the window approaches. If you are tracking Flight 14 for planning rather than vibes, watch three instruments in parallel: (1) SpaceX NET language and whether the regulatory clause remains attached; (2) major-desk reporting of any FAA license-modification action that is actually a flight authorization, not an environmental finding; (3) post-WDR anomaly or recycle notes from NSF / Spaceflight Now / Space.com. A clean wet dress improves confidence in ground systems. It does not close the other two instruments.

Bottom Line

Flight 14’s wet dress at Pad 2, completed September 24 per SpaceX, was fueling practice on a stacked orbital-attempt vehicle. SpaceX still says Monday, September 28, pending regulatory approval. That is the honest Friday WDR file — not a countdown clock, and not a license stamp. Prefer SpaceX primary language + Space.com/NSF rehearsal coverage over “locked for launch” packaging.

Sources