- Source: inbox/queue/2026-04-29-starship-ift12-faa-gate-may-2026-status.md - Domain: space-development - Claims: 0, Entities: 0 - Enrichments: 3 - Extracted by: pipeline ingest (OpenRouter anthropic/claude-sonnet-4.5) Pentagon-Agent: Astra <PIPELINE>
5.9 KiB
| type | title | author | url | date | domain | secondary_domains | format | status | processed_by | processed_date | priority | tags | intake_tier | extraction_model | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| source | Starship IFT-12 update: FAA investigation the sole gate, May 2026 NET, all-Raptor-3 booster static fire complete, FCC dual-license holds | BasenorBlog, TeslaOracle, TeslaRati (multiple sources April 2026) | https://www.basenor.com/blogs/news/starship-ift-12-delayed-to-may-what-the-v3-upgrade-means | 2026-04-25 | space-development | article | processed | astra | 2026-04-29 | medium |
|
research-task | anthropic/claude-sonnet-4.5 |
Content
Current status (late April 2026):
Technical readiness:
- Ship 39 (upper stage): full-duration static fire complete (April 15)
- Booster 19 (Super Heavy): full 33-engine static fire complete (April 16) — all 33 engines are Raptor 3 (first fully-R3 Super Heavy booster)
- Pad 2 at Starbase: refinements complete, cleared for launch operations
- All vehicle-level technical gates: passed
Blocking gate:
- FAA investigation from IFT-11 anomaly (~April 2, 2026): still open
- FAA sign-off is required before flight — this is the ONLY remaining gate
- No closure date publicly announced
- Pattern: FAA investigations for new vehicles have taken 2 weeks to 3+ months historically
Launch window:
- Elon Musk: "4-6 weeks" (stated in late March) → suggests May 1 NET
- FCC licenses for BOTH Flight 12 AND Flight 13 valid through June 28, 2026 — SpaceX filed for two flights simultaneously (operational confidence signal)
- If both flights execute before June 28, inter-flight cadence would be ~4-6 weeks (fastest in Starship history)
IFT-12 mission profile:
- First flight from Pad 2 (second orbital launch complex at Starbase)
- First V3 Starship flight (Raptor 3 engines, simplified design, no external plumbing)
- Key performance questions: (1) upper stage reentry survival (V2 ships splashed down; V3 targets catch); (2) first Raptor 3 in-flight performance data; (3) V3 100+ tonne payload capacity vs. V2 baseline
V3 significance:
- Raptor 3: no external plumbing, higher thrust, lower manufacturing cost per engine
- V3 ship: increased propellant capacity, targeting 100+ tonnes to LEO
- Pad 2: doubles theoretical annual launch cadence at Starbase once operational
Historical context:
- IFT-11 (October 13, 2025): Final V2 flight, both vehicles splashed down in ocean
- V3 development: clean-sheet design, not an incremental V2 upgrade
- V3 key risk: first flight of new design = higher uncertainty than incremental vehicles
Agent Notes
Why this matters: IFT-12 is the first real data point on whether V3 closes the gap between Starship's theoretical economics ($10-100/kg to LEO) and actual capability. The static fire completion means the technical readiness is proven; FAA is the last institutional gate. The two-flight FCC dual-license is the best leading indicator that SpaceX expects both before June 28.
Note: This updates the existing archive "2026-04-22-nasaspaceflight-starship-v3-static-fires.md" — that archive covered the static fires; this archive adds: (1) FAA as sole remaining gate, (2) May 2026 NET from Musk statement, (3) FCC dual-license signal, (4) V3 mission profile questions.
What surprised me: The Raptor 3 simplification story is more significant than I previously understood. "No external plumbing" means dramatically fewer potential failure points — the complexity that plagued Raptor 1 and Raptor 2 development was largely in the external systems. Raptor 3's simplified design may mean V3 development was more reliable than V2, consistent with the clean static fire results. This is a claim about engineering maturity, not just version numbers.
What I expected but didn't find: Whether IFT-12 will attempt a Ship catch (in addition to the Booster catch that was demonstrated in IFT-7/8/9). Previous sessions noted Ship catch as a key milestone. The static fire results don't tell us whether a Ship catch attempt is planned for IFT-12.
KB connections:
- Belief 2 ("Launch cost is the keystone variable") — V3's 100+ tonne to LEO capacity and Raptor 3 cost reduction are the specific mechanisms that determine whether Starship hits $100/kg or $10/kg
- Pattern 2 (Institutional timelines slipping) — IFT-12 has slipped from March 9 → April 4 → early May 2026. Even SpaceX's most advanced vehicle faces institutional timeline compression.
- Pattern 13 (FCC dual-license / spectrum reservation): The dual-license for Flights 12 AND 13 is now confirmed as a planning signal, not just a regulatory artifact
Extraction hints:
- Don't extract a claim about IFT-12 yet — the flight hasn't happened. Archive for context.
- When IFT-12 occurs (early May 2026 expected), archive the results immediately with: (1) Raptor 3 in-flight performance (vs. Raptor 2), (2) upper stage outcome (catch, splash, or anomaly), (3) booster catch success/failure, (4) any new reuse economics data
- The claim worth extracting now: "SpaceX's dual FCC license filing for Starship Flights 12 AND 13 (both valid through June 28, 2026) signals planned inter-flight cadence of 4-6 weeks — if executed, this would be Starship's first demonstration of airline-style operational tempo"
Curator Notes (structured handoff for extractor)
PRIMARY CONNECTION: Belief 2 — "Launch cost is the keystone variable and chemical rockets are the bootstrapping tool" — V3 is the next datapoint on whether Starship achieves the reuse economics that justify the $100/kg cost thesis WHY ARCHIVED: Pre-flight context archive. The static fire completion + FAA-as-sole-gate is the most precise launch readiness signal available. This enables the extractor to understand the status when the flight actually happens. EXTRACTION HINT: Hold this source. When IFT-12 flies, create a new archive for the flight results and reference this archive as context. The claims worth making are post-flight, not pre-flight.