Blog

  • NOAA 15 CFR Part 960 Remote-Sensing Licensing & FCC Debris Plan Handoff

    NOAA 15 CFR Part 960 Remote-Sensing Licensing & FCC Debris Plan Handoff

    Verified against 15 CFR Part 960 (eCFR) and NOAA CRSRA guidance as of 2026-11-16.

    ORBITAL SUSTAINABILITY · DISPOSAL REGIME · FEDERAL REGULATION (15 CFR PART 960)
    NOAA Part 960 & FCC Debris Handoff
    NOAA's 15 CFR Part 960 governs private Earth-observation satellites like Tukwila-based BlackSky; to avoid duplicate technical reviews, NOAA relies on FCC (or other authorized agency) orbital debris oversight while retaining general license conditions.
    Primary Authority / Source: NOAA CRSRA / Dept. of Commerce  |  As-Of / Horizon: Active Nov 2026 (Streamlined FCC Reliance)
    ORBITAL SUSTAINABILITY · PDF & MARKDOWN TWIN
    NOAA Part 960 & FCC Debris Handoff — Reference Brief
    Download the 2-page printable reference PDF or read the clean Markdown twin for AI and briefing workflows.
    Multi-Agency Earth-Observation Licensing Handoff (NOAA + FCC)
    Multi-Agency Earth-Observation Licensing Handoff (NOAA + FCC)

    Documented Instrument & Engineering Record

    • What NOAA licenses: 15 CFR Part 960 regulates private space-based remote-sensing systems—focusing on imaging capabilities, shutter control, and national-security data tiers.
    • Eliminating duplicate debris reviews: Because commercial remote-sensing satellites also require FCC spectrum licenses, NOAA streamlined Part 960 to rely on FCC (or equivalent U.S. agency) orbital debris plan reviews rather than running a parallel technical ODMP assessment.
    • Retained statutory backstop: NOAA still includes standard post-mission disposal compliance conditions in Part 960 licenses, so an FCC violation or unapproved orbit change can trigger multi-agency scrutiny.
    • WA applicability: Directly governs BlackSky's Tukwila-operated optical imaging constellation and any WA Earth-observation payloads.

    15 CFR Part 960 vs. 47 CFR Part 25 Compliance Mapping

    Compliance AreaNOAA Part 960 RoleFCC Part 25 Role
    5-Year LEO DeorbitDefers technical review to FCCPrimary technical & enforcement lead
    Imaging / Shutter ControlPrimary regulator (Tier 1–3)Not regulated
    RF Downlink SpectrumNot regulatedPrimary regulator
    License Condition LinkRequires lawful disposal complianceEnforces ODMP & § 25.283(e)

    Mission Designer, Compliance Lead & Founder Takeaways

    • EO startups cannot skip FCC orbital debris disclosures by citing a NOAA remote-sensing license—NOAA expects the FCC ODMP to carry the technical proof.
    • Changes to operational altitude or constellation replenishment schedules require coordinated updates across both FCC and NOAA filings.
    • Compliance leads should maintain one unified configuration-controlled Orbital Debris & End-of-Mission dossier for both agencies.

    Connected Census Profiles, Segments & Rules

    Primary Sources & Official Records

  • FAA 14 CFR Part 450 Upper-Stage Disposal & Launch-License Debris Conditions

    FAA 14 CFR Part 450 Upper-Stage Disposal & Launch-License Debris Conditions

    Verified against 14 CFR Part 450 (eCFR) and Batch 5 #1966 transition dates as of 2026-11-16.

    ORBITAL SUSTAINABILITY · DISPOSAL REGIME · FEDERAL REGULATION (14 CFR PART 450)
    FAA Part 450 Upper-Stage Disposal
    With FAA's 5-year transition to 14 CFR Part 450 completed on March 9, 2026, all U.S. commercial launch and reentry licenses govern upper-stage orbital debris mitigation, collision avoidance at launch, and stage passivation under unified Part 450 safety rules.
    Primary Authority / Source: FAA AST / eCFR  |  As-Of / Horizon: Mandatory Cutoff March 9, 2026 (Active Nov 2026)
    ORBITAL SUSTAINABILITY · PDF & MARKDOWN TWIN
    FAA Part 450 Upper-Stage Disposal — Reference Brief
    Download the 2-page printable reference PDF or read the clean Markdown twin for AI and briefing workflows.
    FAA 14 CFR Part 450 Launch & Upper-Stage Debris Gates
    FAA 14 CFR Part 450 Launch & Upper-Stage Debris Gates

    Documented Instrument & Engineering Record

    • Unified licensing regime: As of March 9–10, 2026, legacy Parts 415, 417, 431, and 435 were sunsetted into 14 CFR Part 450 for all commercial orbital launches.
    • Upper-stage focus: While FCC regulates satellite payloads, FAA Part 450 regulates the launch vehicle and orbital upper stage—requiring collision avoidance (COLA) screening during ascent/deployment and post-deployment stage disposal.
    • Reusable vs. expendable stages: WA launch developers (Blue Origin New Glenn, Stoke Space Nova) design reusable or rapidly deorbited upper stages that eliminate long-lived spent rocket bodies in LEO.
    • Angle split with Batch 5: Batch 5 Post #1966 documents that Part 450 is LIVE; this brief isolates the upper-stage disposal and COLA obligations inside Part 450.

    FAA Part 450 vs. FCC Part 25 Jurisdiction Split

    Hardware ElementGoverning AgencyPrimary Regulation
    Launch Vehicle & Upper StageFAA (AST)14 CFR Part 450
    Payload RF & Satellite DisposalFCC (Space Bureau)47 CFR Part 25 (§ 25.283)
    Remote-Sensing Payload DataNOAA (CRSRA)15 CFR Part 960
    NASA-Contracted PayloadsNASA SMANASA-STD-8719.14C (Contract)

    Mission Designer, Compliance Lead & Founder Takeaways

    • Spent rocket bodies represent a disproportionate share of total orbital mass (>17,000 tonnes total tracked mass per ESA 2026 Report).
    • WA launch teams operating out of Florida/Vandenberg (Blue Origin, Stoke Space) still engineer upper-stage passivation valves and reentry guidance in Kent and Redmond.
    • Rideshare payload integrators must verify that the launch provider's Part 450 license covers deployment separation and COLA windows.

    Connected Census Profiles, Segments & Rules

    Primary Sources & Official Records

  • Reentry Casualty Risk (< 1:10,000 / 15 J): Design-for-Demise vs. Controlled Ocean Reentry

    Reentry Casualty Risk (< 1:10,000 / 15 J): Design-for-Demise vs. Controlled Ocean Reentry

    Thresholds (< 1:10,000 Ec, > 15 J kinetic energy) verified against NASA-STD-8719.14C and NASA ODPO guidance as of 2026-11-16.

    ORBITAL SUSTAINABILITY · DISPOSAL REGIME · NASA-STD-8719.14C / FCC PART 25 / ODMSP
    Reentry Casualty Risk & Demisability
    Uncontrolled atmospheric reentry is permitted only if predicted human casualty expectation (Ec) across all surviving fragments exceeding 15 joules remains below 1 in 10,000 (0.0001); otherwise, operators must execute a controlled reentry over uninhabited ocean.
    Primary Authority / Source: NASA ODPO / FCC  |  As-Of / Horizon: Active Nov 2026 (15 J Kinetic Energy Gate)
    ORBITAL SUSTAINABILITY · PDF & MARKDOWN TWIN
    Reentry Casualty Risk & Demisability — Reference Brief
    Download the 2-page printable reference PDF or read the clean Markdown twin for AI and briefing workflows.
    Reentry Casualty Risk (Ec < 1:10,000) Compliance Paths
    Reentry Casualty Risk (Ec < 1:10,000) Compliance Paths

    Documented Instrument & Engineering Record

    • The 15-joule threshold: Under NASA-STD-8719.14C and U.S. Government ODMSP, any surviving piece striking Earth with kinetic energy > 15 joules contributes to the human casualty area.
    • Why aluminum demises and titanium survives: Aluminum alloys melt around ~660 °C during peak aerothermal heating, whereas titanium (~1,668 °C), stainless steel (~1,400–1,500 °C), and tungsten balance weights frequently survive to ground impact.
    • Two compliance paths: Designers either substitute demisable materials (Design-for-Demise) or budget enough delta-v for a targeted deorbit burn into the South Pacific Ocean Uninhabited Area (SPOUA).
    • Constellation multiplier: When a single constellation deploys thousands of satellites, regulators scrutinize both per-satellite Ec and aggregate fleet casualty risk.

    Design-for-Demise vs. Controlled Reentry Tradeoffs

    Compliance StrategyEngineering MechanismPrimary Tradeoff
    Design-for-DemiseReplace Ti/SS with Al/composite; thin wallsHigher material/thermal engineering cost
    Controlled Ocean ReentryTargeted perigee burn into SPOUARequires high-thrust prop + large EOL delta-v
    ORSAT High-Fidelity Run3D thermal-structural ablation modelingReplaces conservative DAS sphere assumptions

    Mission Designer, Compliance Lead & Founder Takeaways

    • Never assume a small CubeSat or SmallSat automatically passes 1:10,000; a single dense titanium star-tracker baffle or steel flywheel can fail DAS.
    • WA satellite manufacturers (SpaceX Redmond, Amazon Leo, BlackSky) publish demisability commitments in FCC ODMP filings.
    • Running ORSAT early in preliminary design avoids last-minute ballast or propellant penalties before launch licensing.

    Connected Census Profiles, Segments & Rules

    Primary Sources & Official Records

  • Spacecraft & Upper-Stage Passivation: Propellant Venting, Battery Isolation & 1:1,000 Risk

    Spacecraft & Upper-Stage Passivation: Propellant Venting, Battery Isolation & 1:1,000 Risk

    Breakup count (>660) and 2024 propulsion spike (>3,000 fragments) cited from ESA 2026 Space Environment Report (data through end of 2025).

    ORBITAL SUSTAINABILITY · DISPOSAL REGIME · FCC / NASA-STD-8719.14C / ODMSP
    Spacecraft & Upper-Stage Passivation
    Passivation removes all stored internal energy—residual propellants, pressurants, batteries, and momentum wheels—at end of mission to keep accidental breakup probability below 0.001 (1 in 1,000) across more than 660 historical fragmentation events recorded through end of 2025.
    Primary Authority / Source: NASA ODPO / FCC  |  As-Of / Horizon: Active Nov 2026 (ESA 2026 Report: >660 Historical Breakups)
    ORBITAL SUSTAINABILITY · PDF & MARKDOWN TWIN
    Spacecraft & Upper-Stage Passivation — Reference Brief
    Download the 2-page printable reference PDF or read the clean Markdown twin for AI and briefing workflows.
    Passivation Subsystems & Stored-Energy Depletion
    Passivation Subsystems & Stored-Energy Depletion

    Documented Instrument & Engineering Record

    • Why passivation is enforced: ESA's 2026 Space Environment Report (data through end of 2025) documents more than 660 historical breakups, explosions, and fragmentation events—including a 2024 spike of >3,000 tracked fragments driven by propulsion-related breakups.
    • Propulsion passivation: Operators must burn or vent residual fuel, oxidizer, and pressurant gases (e.g., helium, nitrogen, krypton) to prevent tank over-pressurization from solar heating.
    • Electrical passivation: Batteries must be discharged and permanently isolated from solar arrays (disconnect relays or bleed resistors) so internal cell shorts cannot trigger thermal runaway.
    • Kinetic & thermal stores: Reaction wheels must be spun down and pressurized heat pipes or cryocoolers accounted for in the ODAR.

    Passivation Engineering Checklist by Subsystem

    SubsystemStored Energy HazardRequired EOL Action
    Liquid / Cold-Gas PropulsionHypergolic/pressurant tank ruptureDepletion burn + latch-open vent valves
    Electric Propulsion (Hall/Ion)High-pressure xenon/krypton tankBleed residual gas through thruster/valves
    Power / BatteriesThermal runaway & cell explosionFull discharge + permanent charge-path open
    ADCS Momentum WheelsRotor burst on structural fatigueActive spin-down before bus shutdown

    Mission Designer, Compliance Lead & Founder Takeaways

    • Designing latch-open pyro or solenoid vent valves adds minimal mass early in CDR but is nearly impossible to retrofit after integration.
    • Upper-stage propulsion firms in WA (Blue Origin, Stoke Space, Aerojet Rocketdyne Redmond) must verify passivation sequences under both FAA Part 450 and NASA ODAR deliverables.
    • Passivation sequencing matters: telemetry must confirm disposal burn completion *before* permanent battery disconnect cuts communications.

    Connected Census Profiles, Segments & Rules

    Primary Sources & Official Records

  • NASA ODAR & EOMP Practice (NASA-STD-8719.14C): Contract Deliverable vs. Regulation

    NASA ODAR & EOMP Practice (NASA-STD-8719.14C): Contract Deliverable vs. Regulation

    Primary-source check against NASA-STD-8719.14 and NPR 8715.6B as of 2026-11-16; distinct from Batch 5 status verdict #1963.

    ORBITAL SUSTAINABILITY · DISPOSAL REGIME · AGENCY TECHNICAL STANDARD (CONTRACT DELIVERABLE)
    NASA ODAR & EOMP Contract Deliverable
    Unlike FCC 47 CFR § 25.283(e), NASA-STD-8719.14C and NPR 8715.6B are not federal regulations—they are agency technical standards enforced as binding contract deliverables (ODAR and EOMP) on NASA missions and rideshare payloads.
    Primary Authority / Source: NASA ODPO / Standards  |  As-Of / Horizon: NASA-STD-8719.14C & NPR 8715.6B (Active Nov 2026)
    ORBITAL SUSTAINABILITY · PDF & MARKDOWN TWIN
    NASA ODAR & EOMP Contract Deliverable — Reference Brief
    Download the 2-page printable reference PDF or read the clean Markdown twin for AI and briefing workflows.
    NASA ODAR & EOMP Deliverable Architecture (NASA-STD-8719.14C)
    NASA ODAR & EOMP Deliverable Architecture (NASA-STD-8719.14C)

    Documented Instrument & Engineering Record

    • Contract vs. regulation: NASA-STD-8719.14C binds missions through NASA procurement contracts, Space Act Agreements, and launch-integration requirements—not general civil rulemaking.
    • Two required documents: The Orbital Debris Assessment Report (ODAR) is submitted at Preliminary Design Review (PDR) and updated at Critical Design Review (CDR) / Flight Readiness Review (FRR), paired with an End of Mission Plan (EOMP).
    • Standard analytical tools: Mission teams run NASA's Debris Assessment Software (DAS) for orbital lifetime and collision probability, and ORSAT (Object Reentry Survival Analysis Tool) when DAS flags casualty risk near or above 1:10,000.
    • Angle split with Batch 5: Batch 5 Post #1963 confirms NASA ODAR is LIVE; this brief specifies the PDR/CDR deliverable workflow and DAS/ORSAT engineering inputs.

    NASA ODAR Deliverable Milestones & Software Gates

    Milestone / ArtifactRequirement SourceTechnical Deliverable
    Preliminary ODARNPR 8715.6B / PDRInitial orbital lifetime, passivation & casualty estimate
    Final ODARNPR 8715.6B / CDR-FRRVerified DAS/ORSAT run with as-built component masses
    End of Mission Plan (EOMP)NASA-STD-8719.14CStep-by-step passivation, venting & deorbit execution
    Reentry Casualty GateRequirement 4.7-1Total Ec < 0.0001 (1:10,000) across >15 J fragments
    Explosion Probability GateRequirement 4.4-1Accidental explosion probability < 0.001

    Mission Designer, Compliance Lead & Founder Takeaways

    • WA suppliers building payloads or hosted instruments for NASA missions must supply material/mass breakdowns (titanium, stainless steel, reaction wheels) for ORSAT survivability runs.
    • Contract deliverables cannot be waived by commercial licensing alone; NASA Safety and Mission Assurance (SMA) signs off separately from FCC.
    • Program managers should freeze ODAR component lists before CDR to avoid late-stage demisability redesigns.

    Connected Census Profiles, Segments & Rules

    Primary Sources & Official Records

  • FCC 5-Year Post-Mission Disposal Rule (47 CFR § 25.283(e)): Mechanics & Spacecraft Requirements

    FCC 5-Year Post-Mission Disposal Rule (47 CFR § 25.283(e)): Mechanics & Spacecraft Requirements

    Primary-source check against 47 CFR § 25.283(e) (eCFR) as of 2026-11-16; distinct from Batch 5 status verdict #1960.

    ORBITAL SUSTAINABILITY · DISPOSAL REGIME · FEDERAL REGULATION (47 CFR § 25.283(E))
    FCC 5-Year Disposal Rule Mechanics
    Under 47 CFR § 25.283(e), space stations ending missions in or passing through Low Earth Orbit below 2,000 km must complete atmospheric reentry as soon as practicable and no later than 5 years after end of mission—replacing the legacy 25-year guideline.
    Primary Authority / Source: FCC Space Bureau / eCFR  |  As-Of / Horizon: Effective Sept 9, 2024; Compliance Sept 29, 2024
    ORBITAL SUSTAINABILITY · PDF & MARKDOWN TWIN
    FCC 5-Year Disposal Rule Mechanics — Reference Brief
    Download the 2-page printable reference PDF or read the clean Markdown twin for AI and briefing workflows.
    FCC 47 CFR § 25.283(e) 5-Year LEO Disposal Thresholds
    FCC 47 CFR § 25.283(e) 5-Year LEO Disposal Thresholds

    Documented Instrument & Engineering Record

    • Altitude scope: Applies to all U.S.-licensed satellites (Part 25) and non-U.S. satellites seeking U.S. market access whose missions end in or pass through LEO below 2,000 km.
    • End-of-mission (EOM) trigger: For spacecraft with propulsion and collision avoidance, EOM occurs when the satellite can no longer conduct collision-avoidance maneuvers; for non-maneuverable spacecraft, EOM is completion of the primary mission.
    • Grandfathering boundary: Satellites already in orbit prior to the September 29, 2024 compliance date (and certain grandfathered authorizations) remain under prior license terms unless modified.
    • Angle split with Batch 5: Batch 5 Post #1960 establishes that the rule is LIVE; this brief details the engineering triggers, EOM definition, and waiver/licensing mechanics required of mission designers.

    47 CFR § 25.283(e) Instrument Parameters

    ParameterInstrument RequirementEngineering Impact
    Altitude ScopeLEO region below 2,000 kmCovers nearly all WA constellation & EO orbits
    Disposal DeadlineAs soon as practicable; <= 5 years post-EOMForces propulsion or <=500 km deployment
    EOM Trigger (Propulsive)Loss of collision-avoidance capabilityRequires reserved EOL propellant before depletion
    EOM Trigger (Non-Propulsive)Completion of primary missionPassive drag must decay orbit within 5 years
    Jurisdictional ReachU.S. Part 25 + non-U.S. market accessBinds foreign operators serving U.S. customers

    Mission Designer, Compliance Lead & Founder Takeaways

    • Mission designers cannot treat 5 years as a passive-drag guarantee above ~500–600 km; solar-cycle minima can push unpropelled decay past 5 years.
    • Compliance leads must align FCC Orbital Debris Mitigation Plan (ODMP) disclosures with propellant-reserve telemetry and EOM triggers.
    • WA constellation operators (SpaceX Redmond, Amazon Leo, BlackSky) and servicing providers (Starfish Space) design directly around this 5-year ceiling.

    Connected Census Profiles, Segments & Rules

    Primary Sources & Official Records

  • Site-Selector Decision Matrix: Scoring Washington vs. TX, FL, AL & CO Without Advocacy

    Site-Selector Decision Matrix: Scoring Washington vs. TX, FL, AL & CO Without Advocacy

    Corpus standard: BC ESG does not declare a 'winner' of the state fight; it documents instruments, decisions, and structural facts.

    THE STATE FIGHT · STRUCTURAL FACTORS · NON-ADVOCACY COMPARATIVE SYNTHESIS
    Site-Selector Matrix: WA vs. TX, FL, AL & CO
    This non-advocacy decision matrix places Washington's documented instruments ($350K SRF example, no space-specific tax credit, EO 26-04 Council, >68% preliminary satellite ecosystem) side-by-side against Texas, Florida, Alabama, and Colorado so founders, staffers, and site selectors can weight the tradeoffs themselves.
    Primary Authority / Source: WA / TX / FL / AL / CO Sourced Records  |  As-Of / Horizon: As of Nov 16, 2026
    THE STATE FIGHT · PDF & MARKDOWN TWIN
    Site-Selector Matrix: WA vs. TX, FL, AL & CO — Reference Brief
    Download the 2-page printable reference PDF or read the clean Markdown twin for AI and briefing workflows.
    Five-State Comparison Matrix — Instruments, Ranges & Decisions
    Five-State Comparison Matrix — Instruments, Ranges & Decisions

    Documented Policy & Site-Selection Record

    • No Declared Winner: Consistent with BC ESG's reader-first standard, this matrix presents verified instruments, ceilings, and company decisions without advocating for or against any state or tax proposal.
    • When Washington Wins: High-density satellite engineering, flight software, RF/antennas, in-space servicing, and orbital compute R&D (K2 Space, Agile Space, Cowboy Space, Portal, Starcloud).
    • When Coastal States Win Launch: Orbital pad infrastructure and range-coupled vehicle integration (Florida SIP, Texas ranges), because Washington has zero orbital launch pads.
    • When Inland/Southern States Win Factories: Large-capex engine or second-plant manufacturing where >$50M–$300M state/local incentive ceilings offset greenfield setup (Alabama BE-4, Texas SEARF, Colorado JGITC).

    Five-State Site-Selection Comparison (Verified Record Only)

    StateDocumented Space InstrumentOrbital Range?Recent WA-Relevant Signal
    WashingtonSRF ($350K Portal); EO 26-04 Council; no space tax creditNo (Moses Lake test only)67 core firms; Cowboy/K2/Agile in; Lapsa Sept 2026 warning
    TexasTX Space Comm / SEARF ($150M + $300M ceilings)Yes (Boca Chica / private)Proactive outreach to Stoke Space (Sept 2026)
    FloridaSpace Florida / FDOT SIP (Relativity up to $134M ceiling)Yes (Cape Canaveral / KSC)Hosts WA firms’ launch ops (Blue Origin, Stoke)
    AlabamaPerformance abatements (Blue Origin >$50M Huntsville)No (Marshall Test Stand)Anchored Blue Origin BE-4 plant (2017–2020)
    ColoradoOEDIT JGITC (8-yr), Opportunity Now, AIA ($150K–$250K)No (Inland)Inland workforce-credit benchmark cited in policy debate

    Founder, Staffer & Site-Selector Takeaways

    • Founder Action: Score your next facility across four weights—(1) senior engineering hiring speed, (2) orbital range coupling, (3) gross-receipts vs. income tax exposure, and (4) cash value of milestone-gated incentives.
    • Staffer Action: Use this matrix alongside the 25 companion briefs to separate enacted statutory tools from advisory bodies and headline ceilings.

    Connected Census Profiles, Segments & Valley Corridors

    Primary Sources & Official Records

  • Industrial Real Estate & Utility Power: Kent Valley Retrofits, Eastside Labs & Cleanroom Continuity

    Industrial Real Estate & Utility Power: Kent Valley Retrofits, Eastside Labs & Cleanroom Continuity

    Synthesizes documented 2025–2026 facility leases and Batch 7 utility substation continuity records (#2134).

    THE STATE FIGHT · STRUCTURAL FACTORS · 2025–2026 LEASE & SUBSTATION RECORDS
    Industrial Real Estate & Utility Power
    Washington's space cluster divides between high-bay industrial retrofits in Kent/Bothell/Marysville (Cowboy Space 291,035 sq ft; Stoke 168,000 sq ft; Portal 50,000 sq ft) and Class-A engineering offices in Bellevue/Redmond (Agile ~5,740 sq ft; K2 Space)—with substation power continuity and cleanroom backup critical in both.
    Primary Authority / Source: Regional Utilities / CRE Filings  |  As-Of / Horizon: As of Nov 16, 2026
    THE STATE FIGHT · PDF & MARKDOWN TWIN
    Industrial Real Estate & Utility Power — Reference Brief
    Download the 2-page printable reference PDF or read the clean Markdown twin for AI and briefing workflows.
    Puget Sound Real Estate & Power — Valley vs. Eastside Footprint
    Puget Sound Real Estate & Power — Valley vs. Eastside Footprint

    Documented Policy & Site-Selection Record

    • Two-Tier Real Estate Market: Large-bay industrial shells in Kent (former logistics/distribution centers) enable 150K–300K sq ft rocket and spacecraft retrofits, while Bellevue/Redmond absorb 5K–50K sq ft engineering and R&D hubs.
    • Snohomish & Bothell Growth: Portal Space Systems (50,000 sq ft in Bothell) and Gravitics (Cascade Industrial Center in Marysville) show northern Puget Sound absorbing manufacturing growth outside the Green River Valley.
    • Power & Cleanroom Continuity: Satellite cleanrooms, TVAC chambers, and additive manufacturing cells require uninterrupted 3-phase power and backup generation (#2134).
    • Cost Tradeoff: Puget Sound industrial rents and labor costs exceed Alabama or inland Texas, making engineering productivity and existing shell availability the decisive offsets.

    Puget Sound Space Submarkets Compared

    SubmarketTypical UseDocumented Examples
    Kent / Tukwila Valley100K–300K sq ft manufacturing & integrationBlue Origin, Stoke (168k), Cowboy (291k), BlackSky
    Redmond / BellevueConstellation R&D, flight SW, RF & propulsionSpaceX, Amazon Leo, K2 Space, Agile (5.7k), Starcloud
    Bothell / MarysvilleSpacecraft & orbital module manufacturingPortal Space (50k), ARKA/CACI, Gravitics
    Moses Lake (MWH)Static hot-fire & flight testStoke Space test operations

    Founder, Staffer & Site-Selector Takeaways

    • Founder Takeaway: Verify substation capacity, flood elevation, and backup power timelines (#2134) before signing Valley industrial retrofits.
    • Staffer Takeaway: Industrial land supply outside the 100-year floodplain (Marysville, Bothell, Frederickson/Pierce) is a key lever for retaining Series B+ factories.

    Connected Census Profiles, Segments & Valley Corridors

    Primary Sources & Official Records

  • Freight, OSOW Curfews & the I-90 Moses Lake Corridor: Moving Space Hardware Without a Coastal Pad

    Freight, OSOW Curfews & the I-90 Moses Lake Corridor: Moving Space Hardware Without a Coastal Pad

    Synthesizes Batch 7 freight/corridor records (#2164, #2179, #2182, #2185) into the State Fight site-selection comparison.

    THE STATE FIGHT · STRUCTURAL FACTORS · WSDOT OSOW / NWSA / MWH RECORDS
    Freight, OSOW & Moses Lake Corridor
    Building orbital hardware in Puget Sound without a coastal launch pad means moving stages, tankage, and satellites via NWSA ports (3.16M TEUs in 2025), WSDOT OSOW permits (curfews 6–9 AM and 3–7 PM on I-5/I-90/SR 18), and I-90 Snoqualmie Pass to Moses Lake (MWH)—adding freight friction that coastal Florida avoids.
    Primary Authority / Source: WSDOT / NWSA / Port of Moses Lake  |  As-Of / Horizon: Verified Nov 16, 2026
    THE STATE FIGHT · PDF & MARKDOWN TWIN
    Freight, OSOW & Moses Lake Corridor — Reference Brief
    Download the 2-page printable reference PDF or read the clean Markdown twin for AI and briefing workflows.
    Washington Space Hardware Logistics — Ports, Curfews & MWH
    Washington Space Hardware Logistics — Ports, Curfews & MWH

    Documented Policy & Site-Selection Record

    • Port & Air Access: Puget Sound offers deepwater breakbulk at Tacoma (NWSA 3,156,598 TEUs in 2025, #2164) and Sea-Tac/BFI/Paine Field air cargo (#2170, #2173) for satellite shipments.
    • OSOW & Commuter Curfews: WSDOT self-issue OSOW permits cap at 16ft W x 16ft H x 125ft L x 200,000 lbs, with weekday curfews blocking 6–9 AM and 3–7 PM across I-5, I-90, and SR 18 (#2179, #2182).
    • Moses Lake Test Bottleneck: Moving test stages from Kent to Moses Lake (MWH) crosses I-90 Snoqualmie Pass, where winter chain/traction laws automatically prohibit OSOW moves (#2152, #2185).
    • Coastal Contrast: By contrast, Cape Canaveral factories sit miles from launch pads, explaining why heavy-lift launch vehicles often split final stage integration to the Space Coast.

    Washington Freight Assets vs. Launch-Hardware Friction

    Corridor / RuleCapability or LimitBatch 7 Reference
    NWSA Seattle/Tacoma3,156,598 TEUs (2025); East Blair 1 / Terminal 7 breakbulkPosts #2164 & #2167
    WSDOT OSOW Self-IssueUp to 16’W x 16’H x 125’L x 200,000 lbsPost #2179
    Urban Curfews & I-906–9 AM & 3–7 PM curfews; Snoqualmie chain bans OSOWPosts #2182 & #2152
    Moses Lake (MWH)Eastern WA static test corridor (~180 mi via I-90)Post #2185

    Founder, Staffer & Site-Selector Takeaways

    • Founder Takeaway: Satellite builders shipping by air (SEA/BFI/PAE) face minimal friction; large-diameter rocket builders must model I-90 winter OSOW bans and cross-country transport to FL.
    • Staffer Takeaway: Completing SR 167 to Port of Tacoma (2029–2030) and protecting I-90 freight reliability directly improves Washington's manufacturing competitiveness.

    Connected Census Profiles, Segments & Valley Corridors

    Primary Sources & Official Records

  • Valley Floor vs. Green River Floodplain: The Physical-Continuity Tradeoff in Kent, Tukwila & Auburn

    Valley Floor vs. Green River Floodplain: The Physical-Continuity Tradeoff in Kent, Tukwila & Auburn

    Cross-links directly to Batch 7 Freight, Rail & the Valley primary records (#2104, #2107, #2113, #2119, #2137).

    THE STATE FIGHT · STRUCTURAL FACTORS · DEC 2025 BREACHES & KING COUNTY BASELINE
    Green River Valley Floodplain Tradeoff
    Washington's highest concentration of launch and orbital-compute manufacturing (Blue Origin, Stoke Space, Cowboy Space, Starfish, BlackSky) sits on the Green River Valley floor—where King County estimates a 1-day floodplain shutdown costs >=$46M and December 2025 levee breaches pushed permanent Desimone repairs toward 2031.
    Primary Authority / Source: King County DNRP / USACE / BC ESG B7  |  As-Of / Horizon: Dec 2025 Breaches – 2031 Horizon
    THE STATE FIGHT · PDF & MARKDOWN TWIN
    Green River Valley Floodplain Tradeoff — Reference Brief
    Download the 2-page printable reference PDF or read the clean Markdown twin for AI and briefing workflows.
    Kent Valley Space Cluster vs. Green River Floodplain Exposure
    Kent Valley Space Cluster vs. Green River Floodplain Exposure

    Documented Policy & Site-Selection Record

    • Cluster Concentration on the Valley Floor: Kent (#1388) and Tukwila (#1397) house Blue Origin, Stoke Space, Cowboy Space (291,035 sq ft), Boeing Defense/Space, BlackSky, and Starfish Space.
    • December 2025 Breach Record: On December 15, 2025, the Desimone Levee in Tukwila breached, closing 6 miles of SR 167 and triggering ~1,100 evacuations; permanent repairs extend toward 2031 (#2107, #2137).
    • Economic Exposure: King County estimates a 1-day Green River floodplain shutdown costs at least $46M in lost output across ~65,000 jobs and >1/8th of Washington GDP (#2119).
    • Site-Selector Tradeoff: While the Valley offers unmatched large-bay industrial shells, competitors like Huntsville (Cummings Research Park) and Texas pitch greenfield, non-floodplain campuses.

    Valley Industrial Continuity Factors for Space Site Selectors

    FactorDocumented RecordBatch 7 Deep Dive
    Dec 2025 Desimone BreachClosed 6 mi of SR 167; permanent fix toward 2031Post #2107 & #2137
    Hanson Dam ProtectionCredited with ~$7.8B damage prevented (Dec 2025 prelim)Post #2113
    Daily Shutdown Arithmetic>=$46M/day King County floodplain output lossPost #2119
    Non-Floodplain WA OptionsBothell, Marysville, Redmond, Bellevue, Moses LakePosts #1400–#1409, #1454

    Founder, Staffer & Site-Selector Takeaways

    • Founder Takeaway: When signing a 10-year Kent or Tukwila industrial lease, pair flood-insurance and zero-rise/BFE engineering checks (#2131) with SR 167 detour planning.
    • Staffer Takeaway: State-funded levee and Hanson Dam resilience investments directly protect Washington's primary launch-manufacturing corridor.

    Connected Census Profiles, Segments & Valley Corridors

    Primary Sources & Official Records

  • No Orbital Launch Range in Washington: Geography, Overflight Physics & Why Launch Pads Sit on Coasts

    No Orbital Launch Range in Washington: Geography, Overflight Physics & Why Launch Pads Sit on Coasts

    Structural geography and orbital-mechanics constraint underlying the WA-engineering / FL-launch split.

    THE STATE FIGHT · STRUCTURAL FACTORS · GEOGRAPHY & RANGE PHYSICS
    No Orbital Launch Range in Washington
    Washington has zero orbital launch pads because eastward equatorial launches and clear downrange ocean corridors require open Atlantic/Gulf coasts (Florida/Texas) or unobstructed Pacific south/west corridors (Vandenberg, CA); Washington therefore hosts vehicle manufacturing and Moses Lake static testing while orbital launches depart out of state.
    Primary Authority / Source: FAA / Launch Segment Census  |  As-Of / Horizon: Verified Nov 16, 2026
    THE STATE FIGHT · PDF & MARKDOWN TWIN
    No Orbital Launch Range in Washington — Reference Brief
    Download the 2-page printable reference PDF or read the clean Markdown twin for AI and briefing workflows.
    Why Washington Hosts Factories & Static Tests While Pads Sit on Coasts
    Why Washington Hosts Factories & Static Tests While Pads Sit on Coasts

    Documented Policy & Site-Selection Record

    • Eastward Rotational Advantage & Overflight: Standard prograde orbital launches fly east to capture Earth's rotational velocity, requiring unpopulated ocean downrange corridors—which Washington's inland geography and Puget Sound population centers lack.
    • Polar/Sun-Synchronous Constraint: Even southward polar trajectories from Washington face coastal/maritime and Canadian/US West Coast overflight constraints already served by Vandenberg Space Force Base in California.
    • Moses Lake Role: Grant County International Airport (MWH) in Moses Lake supports static engine/stage hot-fire testing (e.g., Stoke Space) and flight-test infrastructure, not orbital pad launches.
    • Policy Clarity: Because no tax incentive can create an eastern coastal range in Washington, losing launch-pad operations to Florida is a geographic certainty—whereas losing *factories* to Texas or Alabama is a policy contest.

    Launch Value Chain: Geographic Constraint vs. Contestable Policy

    StageWhere It HappensDriven By
    Vehicle Design & Propulsion R&DKent, Redmond, Bellevue, TukwilaTalent density (Contestable by WA policy)
    Factory & Tankage ManufacturingKent (Blue Origin, Stoke, Cowboy), BothellIndustrial space & incentives (Contestable)
    Static Hot-Fire TestingMoses Lake (MWH), Grant CountyInland buffer & I-90 corridor (#2185)
    Orbital Pad LaunchCape Canaveral FL / Vandenberg CA / TXOrbital range geography (Non-contestable)

    Founder, Staffer & Site-Selector Takeaways

    • Staffer Takeaway: Do not score Florida's pad wins as Washington policy failures; focus policy on retaining R&D, satellite assembly, and rocket factories.
    • Founder Takeaway: Plan East-West hardware logistics early (see Batch 7 OSOW & Moses Lake corridor briefs).

    Connected Census Profiles, Segments & Valley Corridors

    Primary Sources & Official Records

  • Talent & Supplier Density: The >68% Active-Satellite Ecosystem (Preliminary) Pulling Firms to Puget Sound

    Talent & Supplier Density: The >68% Active-Satellite Ecosystem (Preliminary) Pulling Firms to Puget Sound

    Combines BC ESG Step 0 Census (67 core companies) with Space Northwest / BERK 2026 PRELIMINARY satellite-share estimate.

    THE STATE FIGHT · STRUCTURAL FACTORS · 67-COMPANY CENSUS + PRELIMINARY BERK 2026
    Talent & Supplier Density Pull
    Washington's primary structural advantage in the state fight is engineering and supplier density—67 publicly enumerable core space companies (17 components/suppliers, 14 ground/software, 11 satellite builders, 7 launch, 7 propulsion, 8 servicing, 3 orbital compute) anchored by a preliminary >68% share of active satellites in orbit.
    Primary Authority / Source: BC ESG Census / Space NW BERK (Prelim)  |  As-Of / Horizon: As of Nov 16, 2026
    THE STATE FIGHT · PDF & MARKDOWN TWIN
    Talent & Supplier Density Pull — Reference Brief
    Download the 2-page printable reference PDF or read the clean Markdown twin for AI and briefing workflows.
    Puget Sound Space Cluster — Talent & Supplier Density
    Puget Sound Space Cluster — Talent & Supplier Density

    Documented Policy & Site-Selection Record

    • Constellation Anchor Gravity: SpaceX's Starlink campus in Redmond (#1418) and Amazon Leo in Redmond/Kirkland (#1421) create a deep pool of RF, FPGA, flight-software, and high-rate manufacturing engineers.
    • Preliminary BERK 2026 Scale: Space Northwest and BERK Consulting (Sept 2026, preliminary) estimate >68% of all active satellites in Earth orbit were built in Washington, supporting 34,200 total jobs (~12,300 direct).
    • Supplier & Tooling Ecosystem: 17 core component/material suppliers (Janicki, Electroimpact, Karman/Systima, Crane, Honeywell, Space Valves, Kymeta) plus 4 adjacent precision aerospace suppliers anchor local sourcing.
    • Why Inbound Firms Pay the Premium: K2 Space, Agile Space, and Shield AI opened or scaled Puget Sound hubs specifically to hire experienced engineers without relocating families.

    Washington Core Space Cluster Density (Step 0 Census)

    SegmentEnumerated Core FirmsRepresentative Anchors
    Components & Suppliers17 (+4 adjacent)Electroimpact, Janicki, Karman, Crane, Space Valves
    Ground Systems / Software14AWS Aerospace, Azure Space, RBC Signals, Integrate
    Satellite Manufacturing11SpaceX Redmond, Amazon Leo, Portal, BlackSky, K2 Space
    Launch & Propulsion7 + 7 (14)Blue Origin, Stoke Space, Aerojet Rocketdyne, Agile Space
    In-Space Servicing & Compute8 + 3 (11)Starfish Space, Gravitics, Starcloud, Cowboy Space

    Founder, Staffer & Site-Selector Takeaways

    • Founder Takeaway: Talent density lowers time-to-hire for senior propulsion, RF, and flight-software engineers—often outweighing multi-year tax credits for early-stage R&D.
    • Staffer Takeaway: Preserving this density requires keeping early-stage founders from relocating Series A/B manufacturing lines out of state.

    Connected Census Profiles, Segments & Valley Corridors

    Primary Sources & Official Records

BC ESG

ESG Strategy, Sustainability Intelligence, and Business Continuity for Forward-Thinking Organizations

© 2026 BC ESG — Business Continuity, ESG & Sustainability Intelligence