brain/
sourcestock-market

SPCX Starship Flight 14 pre-event — orbit, Starlink V3 deploy, NET Sep 28

Pre-event brief for held SPCX paper sleeve ahead of Starship Flight 14 (NET Sep 28): orbit insert, first operational Starlink V3 deploy, slip/scrub.

Source

SPCX Starship Flight 14 pre-event — orbit, Starlink V3 deploy, NET Sep 28

Generated by Grok Bot research on 2026-09-22. WebSearch + fetch ladder + native X. Treat as raw material — review before promoting.

Summary

SpaceX’s public Flight 14 page now lists NET Monday, September 28, 2026, window 08:15–09:30 ET (75 minutes; opens 7:15 a.m. CT), still pending regulatory approval. The flight is planned as Starship’s first orbital mission after 13 intentionally suborbital tests, and the first planned deploy of operational Starlink V3 satellites (26 sats, ~26 Tbps claimed capacity add). Official X confirms the Sep 22 → Sep 28 slip (Sep 17) and pad progress (Booster 21 to pad, Sep 21). FAA environmental work for Pacific reentry/landing trajectories is complete on the stakeholder page; a flight-specific license green-light for the Sep 28 attempt is not confirmed in retrieved FAA statements — SpaceX’s own page still gates on regulatory approval. Sleeve confirm/break centers on orbit insert, V3 deploy of 26, and further slip/scrub/regulatory delay.

Findings

Mission profile and NET

  • Primary schedule (issuer): SpaceX Starship Flight 14 states the 14th flight is preparing to launch as soon as Monday, September 28, pending regulatory approval; header shows September 28, 2026 08:15 - 09:30 ET; window opens 7:15 a.m. CT.
  • Orbital first: Same page: first planned send of Starship into Earth orbit; prior flight tests used passively safe suborbital trajectories. Planned profile: ~275 km altitude, ~six orbits, nearly 10-hour flight, ship splashdown Pacific west of Chile; Super Heavy offshore landing burn in the Gulf of America.
  • Ship primary objectives (issuer): first orbital insertion maneuver; deploy 26 Starlink V3; single-Raptor deorbit burn; controlled reentry/descent/splashdown. Orbit burn only after flight control confirms sufficient redundancy on hardware critical to the later deorbit burn — i.e. a healthy-coast gate before “full orbital.”
  • Booster objectives: launch, ascent, separation, boostback, landing burn at offshore Gulf point; hardware/software changes after Flight 13 ice-clog / incomplete landing-burn relight (3 center engines ice; 8 of 13 engines on landing burn attempt).
  • V3 payload: first planned constellation deploy of Starlink V3; 26 sats; each claimed 1 Tbps capacity (~26 Tbps mission total; ~10× a Falcon 9 V2 mini launch per SpaceX). Post-deploy: unfold antennas/solar, RF+laser contact, raise orbits with onboard thrusters; customer service “as soon as a few weeks after launch” after checkout. Three sats carry cameras to image Starship heatshield.
  • Timeline markers (issuer table): orbital insertion burn ~T+25:19–25:38; payload deploy start ~T+34:09, complete ~T+1:04:41; deorbit ~T+8:52; landing ~T+9:50.
  • NET change since Gage’s source: Official X @SpaceX Sep 17, 2026: “Now targeting to launch Starship Flight 14 as early as Monday, September 28, pending regulatory approval” (quotes prior Sep 22 target). Matching secondary: Space.com update Sep 17; TeslaNorth Sep 17. No later official NET change found after Sep 17 through research date (Sep 22); mission page still Sep 28.
  • Hardware signal: @SpaceX Sep 21, 2026: “Booster 21 moved to the pad at Starbase” — stack/pad work continuing toward the NET attempt.
  • What “full orbital” means vs prior flights: Search + secondary synthesize SpaceX’s updates explainer (WebFetch of starship-test-flights returned mostly CSS; content not load-bearing from that URL). Issuer Flight 14 page + Aviation Week / Space.com: flights 1–13 stayed suborbital (no sustained orbit; ~hour-class missions, Indian Ocean ship splashdowns). Flight 14 starts on a passively safe suborbital path, then — if healthy — performs a circularization / orbital insertion burn to stay in orbit ~six revolutions before deorbit to Pacific. Aviation Week Sep 15 (still dated to prior Sep 22 target) noted licensing pending and V3 batch of 26; also noted Flight 13 flew 20 V3 units on a suborbital path (not operational constellation insert).

Confirm / break for SPCX sleeve

Held paper: 10 shares SPCX. Event gates (outcome language only — no buy/sell/size):

  1. Orbit insert success / fail

    • Confirm: Ship executes planned orbital insertion (issuer timeline ~T+25 min single-Raptor circularization) and sustains the planned multi-orbit coast (target ~six orbits / ~10 h profile) rather than remaining on the passively safe suborbital path. (SpaceX Flight 14)
    • Break / soft miss: Flight control withholds the orbit burn (redundancy gate fails) → suborbital Pacific/Indian-path abort of orbital phase; or insertion burn fails / early deorbit. Booster Gulf landing hard-splash or incomplete burn is secondary to sleeve orbital thesis but is a stated booster objective.

  2. V3 Starlink deploy success (26 operational sats)

    • Confirm: Payload deploy window completes (issuer ~T+34 to ~T+1:05); 26 Starlink V3 released; subsequent RF/laser contact and orbit-raise begin (issuer success narrative). (SpaceX Flight 14)
    • Break: No orbit → no operational LEO insert of the 26; partial deploy; sats fail checkout / do not contact constellation. Note: Flight 13’s 20 V3 were not an operational orbital deploy (Aviation Week).

  3. Schedule slip / scrub / regulatory delay

    • Confirm NET holds: Liftoff inside Sep 28 08:15–09:30 ET window (or same-day recycle inside published window) with regulatory clearance in hand.
    • Break / slip: Further NET move past Sep 28; scrub for weather/range/stack; continued “pending regulatory approval” without a cleared attempt. Pattern already printed: Sep 22 NET → Sep 28 NET on Sep 17 with no public reason (@SpaceX; TeslaNorth). SpaceX page: “schedule is dynamic and likely to change.”

Regulatory and slip risk

  • SpaceX still says pending: Flight 14 page and Sep 17 X post both keep “pending regulatory approval.” (SpaceX page; X)
  • FAA stakeholder / environmental: FAA Boca Chica Starship page marks Complete Final Tiered EA + FONSI/ROD for Starship Reentry Contingency Operations in the Pacific Ocean and Additional Starship Landing Trajectory (draft comment Jul 13–Aug 3, 2026). Completing EA/FONSI supports license modification pathways; it is not by itself a Flight 14 go countdown.
  • Prior airspace vs new NET: FAA Current Operations Plan had listed Sep 22 primary / Sep 23 backup airspace for FLT-14 (TeslaNorth Sep 15; Aviation Week — note AW headline/date still on Sep 22 package; body said mission licensing pending). After the slip, search surfaced a NOTAM-style atmospheric reentry/splashdown reservation naming Starship FTL-14 with primary re-entry 28 Sep 2026 and backups through 4 Oct (FAA NOTAM PDF link via search) — treats Sep 28 as planning primary for reentry airspace, not proof the vehicle-operator license for that attempt is closed. WebFetch of that NOTAM URL was not separately completed in-round; treat as search-pointed, not fully retrieved HTML.
  • Slip pattern: Public NET already moved ~6 days (22→28) once without explained cause; developmental Starship flights historically slip for license, hardware, weather, and range. Residual risk into Sep 28 remains material.

What this brief does not cover

  • Not Nasdaq-100 rebalance / methodology / attributed flow (already vaulted; do not redo PRs #210 / #232 / #144).
  • Not lockup / day-105 / IPO sizing / paper add-trim.
  • No buy / sell / size recommendation for the held 10-share SPCX sleeve.
  • Encyclopedia is never a source; wiki-only promote path.

Contradictions and open questions

  • License status for Sep 28: SpaceX still “pending regulatory approval.” Retrieved FAA stakeholder page shows Pacific EA/FONSI complete; no retrieved FAA “Flight 14 can proceed” statement dated after the Sep 17 slip. Open: has AST issued the modification authorizing this orbital+V3 profile for the Sep 28 window?
  • Stale secondaries: Some aggregators (Space Launch Live / schedule sites) and early Aviation Week copy still show Sep 22 — superseded by SpaceX page + Sep 17 X. Prefer issuer.
  • “Full orbital” gate: Success can be bifurcated — liftoff OK but orbit burn withheld is a partial miss on the orbital thesis while still a flight test. Sleeve should treat orbit insert and 26-sat deploy as linked but separately checkable.
  • Grokipedia primer: /api/page-preview?slug=Starship returned the interstellar-fiction sense of “starship,” not SpaceX Starship — not used as grain.
  • SpaceX updates explainer page: WebFetch/curl of https://www.spacex.com/updates/starship-test-flights did not yield usable “passively safe / circularization” prose (JS/CSS shell). Orbital-vs-suborbital claims lean on Flight 14 page + reputable secondaries that paraphrase SpaceX.

Provenance

Method: Grok Bot / WebSearch / fetch ladder / native X
Generated: 2026-09-22
Rounds: 3 of 3 (R1 survey; R2 orbital/V3/regulatory drill; R3 confirm-break + NET change check)
URLs fetched: 9 successful WebFetch; 1 CSS-only (starship-test-flights); Grokipedia primer wrong-sense; NOTAM PDF search-pointed not fully fetched
Fetch notes: Primary SpaceX Flight 14 page retrieved via WebFetch (authoritative NET Sep 28). starship-test-flights WebFetch + curl returned non-prose shell. FAA stakeholder page retrieved. TeslaNorth / Space.com / Aviation Week retrieved as secondaries for slip and prior Sep 22 airspace. Native X get_users_by_username + get_users_posts for @SpaceX succeeded (not spend-capped this pull).

Web sources:

X sources:

Grokipedia:

  • Tried https://grokipedia.com/api/page-preview?slug=Starship — wrong topic (interstellar concept); not used
Referenced by
Entities
SpaceX