6.2 KiB
| type | title | author | url | date | domain | secondary_domains | format | status | priority | tags | intake_tier | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| source | Starship IFT-12 Pre-Launch Update: Booster 19 Second 33-Engine Static Fire (May 9), NET Confirmed May 15 | Tesla Oracle / NASASpaceFlight (@NASASpaceflight) / SpaceLaunchSchedule | https://www.teslaoracle.com/2026/05/09/flight-12-starship-booster-19-performs-a-full-duration-33-engine-static-fire-test-ahead-of-launch/ | 2026-05-09 | space-development | thread | unprocessed | high |
|
research-task |
Content
As of May 12, 2026 (today):
IFT-12 (Starship Flight 12) has NOT yet launched. The first window (May 12 at 22:30 UTC) was not used. The NET (No Earlier Than) date is confirmed as May 15, 2026 at 22:30 UTC.
New development: Second static fire of Booster 19 (May 9, 2026):
- Booster 19 performed a second full-duration 33-engine static fire on May 9, 2026
- First static fire was April 15-16, 2026 (also 33 engines, all Raptor 3)
- This is unusual: prior V2 Super Heavies typically performed one static fire before flight
- No official explanation from SpaceX for the second test
- Interpretation: Either (A) the April static fire surfaced marginal data requiring verification, or (B) this is SpaceX's standard V3 diligence protocol for the all-Raptor-3 configuration debut
Current launch status (May 12, 2026):
- FAA clearance: Confirmed (May 8 investigation closure)
- Vehicle: Booster 19 + Ship 39, both V3 / Block 3 configuration
- Site: OLP-2 (Orbital Launch Pad 2) — inaugural launch from this pad
- Trajectory: Revised southerly Caribbean corridor (debris into open ocean rather than near populated areas)
- No booster catch attempt: Booster 19 to splashdown in Gulf of Mexico; Ship 39 to Indian Ocean powered splashdown
- FCC license: Valid through October 2026, covers Flights 12 and 13
Launch window schedule (per Local Notice to Mariners):
- NET May 15 at 22:30 UTC (5:30 PM CT)
- Daily ~2-hour windows available May 15-18
What IFT-12 will tell us:
- Raptor 3 in-flight performance (first ever — all prior flights used Raptor 2)
- V3 upper stage reentry survival (no V2 Ship ever survived reentry intact)
- OLP-2 inaugural performance
- Vehicle mass fraction and Isp measurements (derivable from telemetry)
- SpaceX booster reuse declaration post-flight (when will they attempt first V3 booster catch?)
IPO context:
- SpaceX IPO roadshow targeting June 2026 (Nasdaq)
- IFT-12 success/failure is the most visible near-term data point for the IPO narrative
- A successful reentry survival demonstration would directly validate V3 full-reuse economics claims
Agent Notes
Why this matters: The second static fire on May 9 is new information not in prior IFT-12 archives (which covered through May 8). A second 33-engine static fire 3.5 weeks before NET May 15 suggests additional pre-flight verification was required. The most plausible reason: V3's all-Raptor-3 configuration (33 new-gen engines) has never operated simultaneously in flight, and the April static fire may have revealed engine interactions or thermal patterns requiring confirmation. This adds uncertainty — if the second static fire itself revealed issues, a further delay is possible.
What surprised me: The shift from May 12 to May 15 NET is not explained in any source. The second static fire (May 9) could be the proximate cause: performing the static fire 3 days before the first window means SpaceX needed several days to assess results before declaring launch readiness. The NET shift from May 12 to May 15 maps closely to this timeline (static fire results → 3-4 day evaluation → launch readiness declaration).
What I expected but didn't find: A specific technical explanation for either the NET shift or the second static fire. SpaceX does not publicly disclose pre-flight anomalies or hold-points in real time.
KB connections:
- Starship achieving routine operations at sub-100 dollars per kg is the single largest enabling condition for the entire space industrial economy — IFT-12 is the primary 2026 test of this claim; second static fire adds pre-launch uncertainty
- reusability without rapid turnaround and minimal refurbishment does not reduce launch costs — V3's pre-launch process (2 static fires, extensive checks) suggests turnaround time for early V3 flights will not yet be "airline-like"
- the space launch cost trajectory is a phase transition not a gradual decline analogous to sail-to-steam in maritime transport — V3 maiden flight is the next data point on this trajectory
Extraction hints:
- STATUS UPDATE (not standalone claim): Update existing IFT-12 archives with the second static fire data point and NET May 15 confirmation. Do NOT create a standalone claim — this is procedural data.
- POTENTIAL FUTURE CLAIM (post-flight): If post-flight analysis reveals the reason for the second static fire (anomaly vs. protocol), that would be claim-worthy. Currently unknown.
- TURNAROUND NOTE: Two static fires before V3 maiden flight vs. one before V2 flights — this may indicate V3's increased complexity requires more extensive pre-flight validation. Flag this when assessing the "airline-like turnaround" claim timeline.
Context: NSF (NASASpaceFlight.com) posted the May 12 first-window scrub confirmation. Tesla Oracle covered the May 9 static fire with technical detail. SpaceLaunchSchedule and RocketLaunch.Live both show May 15 as current NET. Polymarket odds were at 91% as of May 7 and are likely higher given FAA clearance and second static fire completion.
Curator Notes (structured handoff for extractor)
PRIMARY CONNECTION: Starship achieving routine operations at sub-100 dollars per kg is the single largest enabling condition for the entire space industrial economy WHY ARCHIVED: The second static fire before flight is a new data point not in prior archives. Combined with the May 12 → May 15 NET shift, this archive completes the pre-launch status picture. Post-flight: this archive will serve as the pre-flight baseline for comparison with actual results. EXTRACTION HINT: This is a procedural status archive — extract only after the flight, when post-flight data can be compared to these pre-flight conditions.