teleo-codex/inbox/queue/2026-05-11-starship-ift12-faa-cleared-net-may12-may15.md
Teleo Agents 9a8254cf5d astra: research session 2026-05-11 — 6 sources archived
Pentagon-Agent: Astra <HEADLESS>
2026-05-11 06:24:50 +00:00

78 lines
6 KiB
Markdown

---
type: source
title: "IFT-12 Status Update: FAA Investigation Cleared, NET May 12 First Window / May 15 Primary Window, Launch from OLP-2"
author: "NASASpaceFlight / SpaceX / RocketLaunch.Live / Tesla Oracle"
url: https://x.com/NASASpaceflight/status/2051305505339916561
date: 2026-05-11
domain: space-development
secondary_domains: []
format: thread
status: unprocessed
priority: high
tags: [Starship, IFT-12, FAA, launch-window, OLP-2, V3, Booster-19, Ship-39, Raptor-3]
intake_tier: research-task
---
## Content
**IFT-12 Status as of May 11, 2026:**
**FAA Status: CLEARED**
- FAA has approved the IFT-12 operation
- The FAA investigation from IFT-11 anomaly (opened ~April 2, 2026, ~5.5 months post-flight) is resolved
- This closes the last hard gate for launch
**Launch Window:**
- First NET window: **May 12, 2026 at 22:30 UTC (5:30 PM CDT)** — per FAA advisory
- Primary NET: **May 15, 2026** — per Local Notice to Mariners update
- Daily windows during May 12-18, each opening ~22:30 UTC, ~2-hour window
- Launch site: **OLP-2 (Orbital Launch Pad 2, Starbase, Boca Chica, Texas)** — inaugural launch from this pad
- Polymarket odds: 91% before FAA clearance; presumably higher now
**Vehicle Status (as of May 9-10 WDR):**
- Booster 19: Wet Dress Rehearsal (WDR) completed May 9-10 — full countdown simulation with propellant loading
- Booster 19: Second static fire at OLP-2 completed (May 7, 2026) — engineering conservatism for new pad inaugural
- Ship 39: Stacked and integrated with Booster 19 for full-stack WDR
- V3 configuration: Both Booster 19 and Ship 39 are first full V3 vehicles (Raptor 3 engines, taller, increased propellant capacity, ~3x payload capacity in full reuse mode vs V2)
**Mission Profile (unchanged):**
- First launch from OLP-2 (inaugural for this pad — adds risk but validates dual-pad cadence)
- Upper stage: suborbital trajectory, NO mechazilla catch of booster — Booster 19 soft landing in ocean
- Ship 39: Caribbean ocean landing (not tower catch) — keeping risk proportionate to maiden V3 flight
- Revised southerly Caribbean trajectory (debris safety from prior path issues)
- KEY TEST: V3 upper stage reentry survival — no V2 Ship ever survived reentry; V3 thermal protection must work
**FCC License Coverage:**
- SpaceX holds FCC dual-license covering both Flight 12 AND Flight 13
- License valid through June 28, 2026
- If both flights occur before June 28: validates "flights 2-3 months apart" cadence claim
**V3 Technical Significance:**
- Raptor 3 engine: first in-flight performance data (ground static fire confirmed performance, flight will confirm operational envelope)
- ~3x payload capacity vs V2 in full reuse mode (Starship v2 max payload ~100t; V3 targeting ~200t+ to orbit with full reuse)
- Upper stage reentry: thermal protection system for reentry survival — the prerequisite for full reuse economics
## Agent Notes
**Why this matters:** FAA clearance is the decisive gate that was uncertain as recently as April 30. The IFT-11 investigation closing (despite being opened 5.5 months post-flight, suggesting subtle root cause) means the regulatory ceiling is removed and technical execution is the only remaining constraint. IFT-12 is now 1-4 days away. The V3 data series begins this week.
**What surprised me:** The FAA clearance appears to have happened very recently — within days. The April 30 archive showed investigation still open; today's search shows it cleared. This is a very rapid resolution for what was described as a potentially complex root-cause investigation. Either the root cause was identified quickly once properly focused, or the investigation reached a "acceptable risk" determination without full root cause identification. The latter is concerning from a safety perspective.
**What I expected but didn't find:** Expected to find a formal SpaceX or FAA press release announcing investigation closure. The clearance appears to have been communicated through FAA operational advisories and NASASpaceFlight reporting rather than a formal announcement. This is consistent with how prior Starship investigation closures have been communicated.
**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's maiden flight is the first test of the vehicle that would achieve this
- [[reusability without rapid turnaround and minimal refurbishment does not reduce launch costs]] — the WDR + second static fire cadence shows engineering conservatism appropriate for inaugural operations, which is the opposite of minimal refurbishment; this is expected for Flight 12 and will improve
- the space launch cost trajectory is a phase transition — if V3 upper stage survives reentry, the next phase (flight reuse) becomes possible on Flight 13 or 14
**Extraction hints:**
- UPDATE to existing IFT-12 archives: FAA investigation closed, NET May 12 (first window) / May 15 (primary), OLP-2 inaugural confirmed
- This is a pre-launch status update — the extractable claim comes AFTER the flight
- Post-flight claim candidate: whether Ship 39 survived reentry is the binary data point this entire archive is building toward
**Context:** NASASpaceFlight's Twitter feed is the most reliable real-time Starship tracker. The FAA advisory is the official government document. Polymarket prediction markets provide crowd wisdom on launch probability.
## 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: FAA clearance and NET dates are the operative facts for IFT-12 timing. This archive supersedes the April 30 IFT-12 archive which showed investigation still open. The extractor should note that the post-flight analysis (Ship 39 reentry success/failure) will be the actual claim-generating event.
EXTRACTION HINT: No standalone claim yet — this is a pre-launch status update. Archive and wait for post-flight results. Cross-reference with April 30 IFT-12 archive for full context.