FAA Final Tiered EA / Mitigated FONSI/ROD authorizes expanded Pacific contingency landings and an additional Starbase reentry trajectory. FCC STA reporting points to orbital second-stage / Starlink V3 radio authority. NET ~Sep 15 is a circulating marker — not a firm SpaceX launch announcement. Ship catch remains contested; RTLS authorization is not a confirmed catch.

FAA Huge Update on SpaceX Starship New Landing Trajectory, Ready for Return to Starbase! · GREAT SPACEX

What the video shows

The selected clip is GREAT SPACEX coverage of the FAA’s Final Tiered EA / FONSI/ROD stack for new Starship reentry and contingency landing trajectories. Treat it as a secondary visual of the paperwork story — useful context for the regulatory update, not a SpaceX launch announcement or a confirmed Flight 14 countdown.

What the FAA actually published

On the FAA’s SpaceX Starship stakeholder page (last updated Wednesday, September 2, 2026), the agency lists as Complete the Final Tiered Environmental Assessment and Finding of No Significant Impact/Record of Decision for SpaceX Starship Reentry Contingency Operations in the Pacific Ocean and Additional Starship Landing Trajectory. Under the Proposed Action summarized there, the FAA would modify SpaceX’s vehicle operator license to authorize:

  • expansion of previously evaluated Hawaii/Central Pacific and Southeast Pacific contingency landing areas;
  • addition of a new Northern Pacific Contingency Landing Area for an Eastern Range-to-Starbase trajectory; and
  • temporary airspace closures associated with an additional Starship reentry trajectory to the Boca Chica Launch Site.

A Federal Register notice of availability (dated September 2, 2026; published around September 4) points readers to the same FAA project site. NASA and the U.S. Coast Guard are listed as cooperating agencies. Public comment on the draft ran July 13–August 3, 2026 (37 comments).

House voice: a Mitigated FONSI/ROD is an environmental / license-modification decision pathway. It is not, by itself, a SpaceX press release that Flight 14 will fly on a named day. Authorization of updated RTLS/reentry profiles is not identical to a confirmed ship catch on Flight 14.

FCC STA vs flight license

Secondary reporting (TeslaNorth, Teslarati, TechTimes) describes FCC Special Temporary Authority language covering backup ship radios and, critically, an orbital second stage / Starlink V3 communications profile with a requested window starting around September 15, 2026. Treat that carefully:

Claim (company filings / secondary reads): Flight 14 paperwork now describes orbital insertion rather than a short suborbital arc, with roughly ~20 Starlink V3 satellites as the payload story if insertion holds.

Proof boundary: an STA is radio authority. It is not the FAA vehicle operator flight license clearance, and it does not freeze a launch date.

NET ~Sep 15 is a marker

Airspace-briefing and tracker coverage circulate a no-earlier-than planning marker around September 15. SpaceX has not, in the primary FAA documents above, announced a firm Flight 14 countdown. Starship windows routinely slip while stacking, licensing, and range paperwork line up. Read NET dates as schedule gravity — not a locked clock.

Ship catch: conflicting secondary coverage — do not assert confirmation

Secondary outlets disagree on whether Flight 14 will attempt a tower catch of the ship:

  • TechTimes / related reads say the catch ambition has been deferred, with ocean splashdown still the expected ship profile while orbital insertion leads.
  • Tesla Oracle (Sep 3) claims the FAA “approved” a landing catch for Flight 14 by pointing at the same FONSI/ROD stack.

House rule: do not assert that a ship catch is confirmed for Flight 14. Authorization of RTLS / additional reentry trajectories ≠ SpaceX will catch Ship 41 on this flight. Musk has floated catch language before and later walked timing back; treat catch as unresolved until SpaceX states the mission profile for this specific flight.

Claim vs Proof

Confirmed in primary FAA materials: Final Tiered EA + FONSI/ROD availability for Pacific contingency landing expansions + additional Starbase reentry trajectory / airspace closures; license-mod pathway described on faa.gov.

Reported, not primary-proven here: exact FCC STA text details (rely on TeslaNorth/Teslarati citations until the STA PDF is in hand); NET Sep 15 as a circulating marker.

Not established: firm SpaceX launch announcement date; confirmed Flight 14 ship catch.

Context only (already covered Wed): B21/S41 static fires — mentioned so readers know hardware prep is underway, not as today’s lead.

Why this matters

Wednesday’s AI Shift News pack already covered the hardware beat: Booster 21 / Ship 41 static-fire context, Louisiana Starbase packaging, and the GREAT SPACEX Flight 14 packaging video. Today’s flagship is the paperwork stack that changed after those posts — specifically environmental/license-mod decisions and orbital communications language that did not lead Wednesday’s story. Readers who conflate FONSI/ROD with “FAA approved the launch” will misread the clock.

Bottom Line

Flight 14’s newest primary signal is orbital paperwork — FAA FONSI/ROD for expanded contingency landings and an additional Starbase reentry path, plus secondary FCC STA reads for orbital second-stage radio authority. NET ~Sep 15 is still a marker. A ship catch is not confirmed.

Sources