---
type: source
title: "Starship Flight 12: 33-Engine Static Fire Still Needed, Launch Now Late April at Earliest"
author: "NASASpaceFlight / Tesla Oracle / autoevolution"
url: https://www.nasaspaceflight.com/2026/03/ship-39-preflight-test-objectives/
date: 2026-03-21
domain: space-development
secondary_domains: []
format: article
status: null-result
priority: medium
tags: [Starship, SpaceX, Flight-12, static-fire, V3, timeline, Raptor-3]
extraction_model: "anthropic/claude-sonnet-4.5"
---

## Content

Starship Flight 12 (Booster 19 / Ship 39, V3/Block 3 configuration) status as of March 21, 2026:

- March 16: B19 conducted a 10-engine Raptor 3 static fire that ended abruptly due to a ground-side (GSE) issue — not an engine issue. This was the first V3 static fire on Pad 2.
- 23 additional engines still need to be installed on B19 (10 of 33 were present for the abbreviated test)
- A full 33-engine static fire is still required before B19 can be stacked with Ship 39
- Launch now "likely no earlier than the second half of April" — the April 9 NET target is essentially eliminated
- Ship 39 is progressing through its own preflight test objectives in parallel

V3 capabilities: B19 is the first Block 3 Super Heavy booster, featuring Raptor 3 engines throughout. V3 is designed for ~100-tonne payload to LEO (vs. ~150 tonnes in fully reusable V3 at design spec). This is a major capability step up from V2's demonstrated ~21-tonne performance.

Previous context (from session 2026-03-20): The 10-engine fire was confirmed as "ended early due to ground-side issue" — SpaceX is preparing for the full 33-engine fire as the next step.

## Agent Notes
**Why this matters:** Starship V3's operational readiness is a gate event for multiple downstream activities: (1) Starlab's 2028 single-launch architecture, (2) Commercial station deployment generally, (3) Artemis lunar surface access, (4) SpaceX's own cost reduction trajectory (V3 is the first vehicle that could approach the economics needed for the $100/kg threshold). Each flight slip extends the uncertainty.

**What surprised me:** Nothing dramatically new this session — the April 9 slip was anticipated from the prior session's data. The "second half of April" framing from NSF is more specific than expected. B19 still has 23 engines to install, suggesting the full static fire is weeks away, not days.

**What I expected but didn't find:** Any anomaly detail from the 10-engine fire. SpaceX hasn't disclosed what the "ground-side issue" was specifically. If it's a deluge system problem (water flow), it could be quick to fix. If it's a propellant system issue, it's potentially longer.

**KB connections:**
- [[Starship achieving routine operations at sub-100 dollars per kg is the single largest enabling condition for the entire space industrial economy]] — V3 is the first vehicle that might achieve this threshold; every slip delays the threshold crossing
- [[Starship economics depend on cadence and reuse rate not vehicle cost because a 90M vehicle flown 100 times beats a 50M expendable by 17x]] — V3's higher capability is useless without cadence

**Extraction hints:** No new extractable claims this session — this is a status update. The prior session's claim about "April 9 at risk" is confirmed. The new datum is "second half of April" as the realistic NET.

**Context:** Starship V3 is the first vehicle designed to carry payloads of commercial station scale (100+ tonnes). Its operational readiness by 2027-2028 determines whether Starlab and other Starship-dependent architectures stay on schedule. Flight 12's timing (late April at earliest) means the first V3 operational data won't arrive until at least Q2 2026.

## Curator Notes
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: V3 operational readiness update — late April launch vs. April 9 target. Routine cadence tracking for the keystone variable.
EXTRACTION HINT: This is context/update for the keystone belief, not a new claim. Extractor should note timeline slip but not extract a new claim unless combined with other session data.
