Blog

  • Rail Disruption & Auburn Yard Delay Playbook: Buffering Heavy Raw Stock and Tooling

    Rail Disruption & Auburn Yard Delay Playbook: Buffering Heavy Raw Stock and Tooling

    Operational playbook grounded in shared-trackage and 2014 rail-loss precedents.

    FREIGHT, RAIL & VALLEY · CLOSURE PLAYBOOK · OPERATIONAL PLAYBOOK
    Rail Disruption & Auburn Yard Playbook
    Because BNSF and Union Pacific share the same Green River Valley tracks and Auburn Yard sits on the floodplain, procurement leads need safety-stock buffers and upland transload options for rail-dependent metals and tooling.
    Primary Agency / Source: WSDOT / BNSF / BC ESG Procurement  |  As-Of / Horizon: 2026-11-16
    FREIGHT, RAIL & VALLEY · PDF & MARKDOWN TWIN
    Rail Disruption & Auburn Yard Playbook — Reference Brief
    Download the 2-page printable reference PDF or read the clean Markdown twin for AI and engineering workflows.
    BNSF / UP Rail Delay: Buffer Stock & Transload Options
    BNSF / UP Rail Delay: Buffer Stock & Transload Options

    Documented Corridor Facts & Continuity Record

    • Verify which tier-1 aluminum/titanium plate, forging, or chemical suppliers rely on BNSF or Union Pacific carload deliveries through Auburn Yard.
    • Maintain 15–30 days of critical-alloy safety stock on site (above flood elevation) to absorb 1–2 week rail washouts or derailment delays.
    • Pre-qualify an upland rail-to-truck transload terminal (e.g., Spokane or Tacoma upland) for emergency flatbed conversion.

    Rail Continuity Controls for Space Procurement

    VulnerabilityWhy Dual-Carrier FailsMitigation
    Valley Mainline WashoutUP runs on BNSF tracks15–30d on-site alloy safety stock
    Trans-Cascade Derailment2014 Clark Fork precedentFull-replacement transit insurance + spare

    Operational Exposure & Facility Playbook

    • Require suppliers to flag any raw-material shipments routed by rail rather than dedicated truck.
    • Audit DFARS 252.225-7009 specialty-metals traceability before buying emergency spot-market replacements.
    • Review rail-siding flood history if your facility uses direct spur delivery.

    Connected Valley Cities, Segments & Role Briefs

    Primary Sources & Agency References

  • Winter Pass Closure & OSOW Staging Playbook: I-90 Snoqualmie and Eastbound Test Hardware

    Winter Pass Closure & OSOW Staging Playbook: I-90 Snoqualmie and Eastbound Test Hardware

    Grounded in WSDOT OSOW pass rules and ITAR physical-custody requirements.

    FREIGHT, RAIL & VALLEY · CLOSURE PLAYBOOK · OPERATIONAL PLAYBOOK
    Winter Pass & OSOW Staging Playbook
    A practical staging playbook for hardware moving between Puget Sound and Moses Lake when WSDOT traction/chain laws automatically ban oversize loads on I-90 Snoqualmie Pass.
    Primary Agency / Source: WSDOT Mountain Passes / CVO  |  As-Of / Horizon: 2026-11-16
    FREIGHT, RAIL & VALLEY · PDF & MARKDOWN TWIN
    Winter Pass & OSOW Staging Playbook — Reference Brief
    Download the 2-page printable reference PDF or read the clean Markdown twin for AI and engineering workflows.
    I-90 Winter Pass Closure: OSOW Staging & Hold Rules
    I-90 Winter Pass Closure: OSOW Staging & Hold Rules

    Documented Corridor Facts & Continuity Record

    • Because WSDOT automatically voids OSOW travel during chain/traction restrictions on Snoqualmie Pass, every winter oversize move needs a pre-vetted staging yard.
    • Do not release an oversize load from Kent if the 24-hour WSDOT pass forecast shows incoming snow levels below 3,000 feet.
    • For ITAR/flight hardware, staging yards must provide gated, badged, or manned-security parking—never unguarded highway pullouts.

    I-90 Winter OSOW Go / No-Go Protocol

    ConditionDecisionAction
    Dry / Wet, No RestrictionsGORelease at 9:00 AM to clear SR 18 curfew
    Traction Tires / Chains ForecastHOLD AT ORIGINKeep hardware inside Kent/Auburn bay
    Unexpected Mid-Transit Chain LawSTAGE SECUREPark at pre-vetted North Bend/Cle Elum yard

    Operational Exposure & Facility Playbook

    • Add a 48–72 hour weather buffer to November–March Moses Lake test schedules.
    • Keep Oregon OSOW contingency contacts on file only if a multi-day I-90 closure justifies re-permitting via I-5/I-84.
    • Verify heated battery/nitrogen-purge support if sensitive payloads sit overnight in freezing temperatures.

    Connected Valley Cities, Segments & Role Briefs

    Primary Sources & Agency References

  • SR 167 Closure Reroute Playbook: Operating When I-5 Saturates

    SR 167 Closure Reroute Playbook: Operating When I-5 Saturates

    Combines Dec 15, 2025 6-mile SR 167 closure precedent with WA EMD Transportation Recovery Annex modeled I-5 saturation.

    FREIGHT, RAIL & VALLEY · CLOSURE PLAYBOOK · OPERATIONAL PLAYBOOK
    SR 167 Closure & I-5 Reroute Playbook
    When SR 167 closes (as on Dec 15, 2025) and I-5 saturates (as modeled in the County Recovery Annex), Kent and Auburn facilities must split traffic between local upland exits, SR 18 east, and off-peak dispatch.
    Primary Agency / Source: WSDOT / WA EMD Recovery Annex  |  As-Of / Horizon: 2026-11-16
    FREIGHT, RAIL & VALLEY · PDF & MARKDOWN TWIN
    SR 167 Closure & I-5 Reroute Playbook — Reference Brief
    Download the 2-page printable reference PDF or read the clean Markdown twin for AI and engineering workflows.
    SR 167 Closed: I-5 Saturation & East-Side Bypass
    SR 167 Closed: I-5 Saturation & East-Side Bypass

    Documented Corridor Facts & Continuity Record

    • Do not send daytime non-urgent box trucks onto I-5 when SR 167 closes; modeled Recovery Annex gridlock turns 20-minute runs into 3-hour stalls.
    • For Eastside deliveries (Kent/Auburn to Redmond/Bothell), route east via SR 18 -> I-90 -> I-405 if Tukwila/Renton SR 167 is shut.
    • Shift standard freight receiving/shipping to 7:00 PM–5:30 AM until SR 167 reopens.

    SR 167 Closure Dispatch Decision Table

    Origin–DestinationPrimary BlockedFallback RouteTiming Rule
    Kent -> Redmond / BothellSR 167 N -> I-405 NSR 18 E -> I-90 W -> I-405 NCheck OSOW curfews
    Kent -> Sea-Tac (SEA)SR 167 N -> I-405 -> 518Local upland arterials / I-5 NVerify Tukwila flood map
    Auburn -> Port of TacomaSR 167 S / I-5SR 18 W -> I-5 S (off-peak)Night window preferred

    Operational Exposure & Facility Playbook

    • Pre-authorize 24-hour receiving dock staffing during declared corridor emergencies.
    • Verify bridge weight limits on any municipal surface-street detour before releasing heavy trucks.
    • Communicate revised ETA windows to prime customers immediately.

    Connected Valley Cities, Segments & Role Briefs

    Primary Sources & Agency References

  • 72-Hour Valley Flood & Levee-Breach Playbook for Green River Space Facilities

    72-Hour Valley Flood & Levee-Breach Playbook for Green River Space Facilities

    Playbook anchored to Dec 15–16, 2025 historical breach sequence and King County Flood Services alert phases.

    FREIGHT, RAIL & VALLEY · CLOSURE PLAYBOOK · OPERATIONAL PLAYBOOK
    72-Hour Valley Flood Playbook
    A three-phase 72-hour playbook built from the Dec 15–16, 2025 Desimone and Pacific breaches—covering Flood Phase alerts, generator top-offs, hazmat elevation, shift release, and dock-isolation protocols.
    Primary Agency / Source: King County Flood Services / BC ESG Ops  |  As-Of / Horizon: 2026-11-16
    FREIGHT, RAIL & VALLEY · PDF & MARKDOWN TWIN
    72-Hour Valley Flood Playbook — Reference Brief
    Download the 2-page printable reference PDF or read the clean Markdown twin for AI and engineering workflows.
    72-Hour Valley Flood & Levee-Breach Response
    72-Hour Valley Flood & Levee-Breach Response

    Documented Corridor Facts & Continuity Record

    • T-24h (Atmospheric River / Phase 2–3 Alert): Top off backup generator diesel for 72+ hours, stage portable pumps, and move floor-level tooling and WAC 173-303 drums above +3 ft BFE.
    • T-0h (Levee Breach / SR 167 Closure): Account for all personnel, suspend non-essential inbound trucks, and verify UPS/generator transfer before grid sags.
    • T+24h to T+72h: Redirect inbound urgent shipments to pre-designated upland staging outside the valley (SeaTac CFS or Tacoma/Fife upland yards) until evacuation orders lift.

    72-Hour Valley Flood Action Matrix

    WindowTriggerFacilities / EHS ActionLogistics Action
    T-24 HoursKC Flood Phase 2/3Top off diesel; seal dock doors; elevate hazmatAccelerate critical pickups
    T-0 HoursBreach / Evacuation OrderLife-safety muster; verify cleanroom powerHold valley-bound trucks
    T+24–72 HoursSR 167 ClosedDocument outage & inspect perimeterReroute to upland staging

    Operational Exposure & Facility Playbook

    • Assign a single Incident Commander across Facilities/EHS (#2061) and Supply-Chain (#2052) before November.
    • Keep waterproof physical copies of KCC 21A.24 Elevation Certificates and emergency contacts in the security shack.
    • Conduct one tabletop drill each October before atmospheric-river season peaks.

    Connected Valley Cities, Segments & Role Briefs

    Primary Sources & Agency References

  • What Is Not in Our Data: Private Space Logistics Routes, Carrier Contracts, and Non-Public Manifests

    What Is Not in Our Data: Private Space Logistics Routes, Carrier Contracts, and Non-Public Manifests

    Explicit Stop-and-Report transparency page: never reconstruct or guess private company logistics routes.

    FREIGHT, RAIL & VALLEY · SPACE HARDWARE · MISSING / NOT-IN-OUR-DATA BOUNDARY
    Boundary: Private Routes Not in Our Data
    Public agency records document the Green River Valley's levees, SR 167, I-5, BNSF, NWSA, and SEA/BFI/PAE—but individual private space companies' exact truck routes, carrier contracts, and shipment schedules are not in our data.
    Primary Agency / Source: BC ESG Evidence-Only Standard  |  As-Of / Horizon: 2026-11-16
    FREIGHT, RAIL & VALLEY · PDF & MARKDOWN TWIN
    Boundary: Private Routes Not in Our Data — Reference Brief
    Download the 2-page printable reference PDF or read the clean Markdown twin for AI and engineering workflows.
    Evidence Boundary: Public Corridors vs. Private Routes
    Evidence Boundary: Public Corridors vs. Private Routes

    Documented Corridor Facts & Continuity Record

    • Per William's reader-first and evidence-only standard, BC ESG documents only what primary public sources (USACE, King County, WSDOT, BNSF/NWSA, Port of Seattle) actually publish.
    • Public records establish where space facilities sit (Census #1382–#1565) and which shared corridors serve those cities (SR 167, I-5, I-90, BNSF, NWSA, SEA/BFI/PAE).
    • NOT IN OUR DATA: Exact carrier names, private truck schedules, barge/rail manifests, and proprietary routing for Blue Origin, Stoke Space, SpaceX Redmond, Amazon Leo, or any other private operator.

    Publicly Documented vs. Not-In-Our-Data Logistics Boundary

    CategoryStatusWhat We Publish
    Facility Cities & AddressesDocumented (Census)Publicly enumerable locations (Kent, Tukwila, Redmond, etc.)
    Flood, Dam & Levee EventsDocumented (USACE / KC)Dec 2025 breaches, 2009 seepage, 2031 repair horizon
    737 Rail & NWSA/SEA VolumesDocumented (BNSF / NWSA)1,700–1,800 mi rail, 2014 crash, 3.16M TEUs, 69% air
    Private Company Truck RoutesNOT IN OUR DATAExplicitly withheld rather than reconstructed

    Operational Exposure & Facility Playbook

    • Facilities and logistics leads should apply our corridor and flood-exposure baselines against their own confidential carrier routing.
    • When prime customers ask for sub-tier route resilience, disclose the shared valley corridor facts without fabricating private-carrier data.
    • Any future primary-source disclosure (e.g., public NEPA/FAA environmental transport filings) will be added only with dated receipts.

    Connected Valley Cities, Segments & Role Briefs

    Primary Sources & Agency References

  • Shock, Vibration & Cleanroom Integrity in Transit: Protecting Satellites Across Rough Valley Detours

    Shock, Vibration & Cleanroom Integrity in Transit: Protecting Satellites Across Rough Valley Detours

    Engineering transit controls aligned with AS9100D/NASA-STD-8739 quality gates in Batch 4/6; no specific company incident claimed.

    FREIGHT, RAIL & VALLEY · SPACE HARDWARE · ENGINEERING / PROGRAM PRACTICE
    Shock, Vibration & Cleanroom Transit
    Diverting delicate satellite buses, optics, or solar arrays off smooth freeways onto rutted valley surface-street detours during SR 167 closures increases shock/vibration and moisture-intrusion risks.
    Primary Agency / Source: BC ESG Segment & Quality Corpus  |  As-Of / Horizon: 2026-11-16
    FREIGHT, RAIL & VALLEY · PDF & MARKDOWN TWIN
    Shock, Vibration & Cleanroom Transit — Reference Brief
    Download the 2-page printable reference PDF or read the clean Markdown twin for AI and engineering workflows.
    Flight Hardware Transit: Air-Ride, Nitrogen Purge & Monitors
    Flight Hardware Transit: Air-Ride, Nitrogen Purge & Monitors

    Documented Corridor Facts & Continuity Record

    • Satellite manufacturers in Redmond, Kent, Tukwila, and Bellevue ship precision optics, star trackers, and reaction wheels sensitive to road-shock and humidity.
    • When SR 167 or I-5 closes, emergency detours push trucks onto uneven industrial surface streets with railroad grade crossings.
    • Atmospheric-river flood events also spike ambient relative humidity, stressing unpurged shipping containers.

    Flight-Hardware Transit Protection Matrix

    RiskTriggerContainer / Carrier Control
    Vertical Shock / Grade CrossingsSurface-street flood detoursAir-ride trailer + damped shipping skid
    Humidity / CondensationAtmospheric-river delaysDry N2 purge + sealed barrier bag + RH logger
    Undetected ImpactRough handling / potholeCalibrated 3-axis shock & tilt indicators

    Operational Exposure & Facility Playbook

    • Require continuous GPS-stamped tri-axial shock logging on all flight-hardware moves between Kent, Tukwila, Redmond, and SEA/BFI.
    • Inspect shock indicators at receiving before breaking cleanroom double-bag seals.
    • Avoid shipping unsealed optical assemblies during active flood-watch periods.

    Connected Valley Cities, Segments & Role Briefs

    Primary Sources & Agency References

  • ITAR & EAR Physical Transit Custody: Chain-of-Custody When Trucks Detour or Stage Overnight

    ITAR & EAR Physical Transit Custody: Chain-of-Custody When Trucks Detour or Stage Overnight

    Export-control framework per 22 CFR Subchapter M (ITAR); links to BC ESG Batch 6 Export-Control briefs (#2070, #2073).

    FREIGHT, RAIL & VALLEY · SPACE HARDWARE · FEDERAL REGULATION (22 CFR)
    ITAR/EAR Physical Transit Custody
    When a flood closure on SR 167 or a chain ban on Snoqualmie Pass forces an ITAR-controlled spacecraft or propulsion assembly to stage overnight, physical custody, U.S.-person escort, and bonded-yard security remain mandatory.
    Primary Agency / Source: U.S. Dept. of State DDTC (22 CFR) / BIS  |  As-Of / Horizon: 2026-11-16
    FREIGHT, RAIL & VALLEY · PDF & MARKDOWN TWIN
    ITAR/EAR Physical Transit Custody — Reference Brief
    Download the 2-page printable reference PDF or read the clean Markdown twin for AI and engineering workflows.
    22 CFR ITAR/EAR Custody During Corridor Delays
    22 CFR ITAR/EAR Custody During Corridor Delays

    Documented Corridor Facts & Continuity Record

    • ITAR (22 CFR Parts 120–130) and EAR 9A515/9E515 controls govern not only digital drawings, but physical custody and export-controlled hardware in transit.
    • If I-90 Snoqualmie Pass closes or SR 167 floods, drivers hauling USML Category IV/XV hardware cannot leave unguarded trailers at public rest stops.
    • Ocean or air imports/exports through NWSA or SEA require pre-cleared customs brokers to prevent unmonitored terminal dwell.

    Transit Disruption ITAR/EAR Custody Checklist

    ScenarioCustody RiskRequired Control
    Snoqualmie Pass HoldUnsecured overnight trailerPre-contracted gated/badged staging yard
    SR 167 Flood RerouteDriver swap / carrier handoffU.S.-person verification + tamper seals
    SEA / NWSA Terminal DwellMisrouted or unguarded freightDesignated ITAR-capable customs broker

    Operational Exposure & Facility Playbook

    • Include flood and mountain-pass staging protocols in every carrier Statement of Work for USML/9A515 hardware.
    • Require dual-driver teams or GPS-monitored sealed vans for high-value flight hardware.
    • Coordinate with Export-Control Officer (#2070) before authorizing emergency third-party cross-docking.

    Connected Valley Cities, Segments & Role Briefs

    Primary Sources & Agency References

  • Cryogenic & Hazardous Propellant Movement: 49 CFR Rules Across Valley Arterials

    Cryogenic & Hazardous Propellant Movement: 49 CFR Rules Across Valley Arterials

    Federal regulatory framework per 49 CFR (eCFR); individual facility delivery schedules are not in our data.

    FREIGHT, RAIL & VALLEY · SPACE HARDWARE · FEDERAL REGULATION (49 CFR)
    Cryo & Propellant 49 CFR Transit
    Propulsion and launch facilities in Kent, Auburn, and Redmond receive liquid oxygen, methane, hydrogen, or specialty propellants governed by 49 CFR PHMSA/FMCSA hazardous-materials routing, placarding, and tunnel restrictions.
    Primary Agency / Source: U.S. DOT PHMSA / FMCSA (49 CFR)  |  As-Of / Horizon: 2026-11-16
    FREIGHT, RAIL & VALLEY · PDF & MARKDOWN TWIN
    Cryo & Propellant 49 CFR Transit — Reference Brief
    Download the 2-page printable reference PDF or read the clean Markdown twin for AI and engineering workflows.
    49 CFR Hazmat & Cryogenic Transit Through the Valley
    49 CFR Hazmat & Cryogenic Transit Through the Valley

    Documented Corridor Facts & Continuity Record

    • Liquid cryogens and hazardous propellants (LOX, LNG/methane, LH2, hydrazine/monopropellants where used) move under 49 CFR Parts 171–180 (PHMSA) and Part 397 (FMCSA).
    • During SR 167 or I-5 flood closures, hazmat carriers cannot simply divert onto arbitrary residential or unrated local streets.
    • Individual space companies' propellant supplier contracts and tanker frequencies are not in our data.

    49 CFR Propellant Transit Continuity Controls

    ControlRegulatory AnchorValley Flood / Detour Action
    Authorized Hazmat Routing49 CFR Part 397Pre-approve non-flooded alternate truck routes
    Cryo Venting / Hold Time49 CFR Parts 173 / 178Account for I-5/I-90 gridlock boil-off margins
    On-Site Storage BufferWAC 173-303 / IFCMaintain safe buffer above BFE + 3ft

    Operational Exposure & Facility Playbook

    • Verify that your gas/cryogen supplier has pre-vetted flood-detour routes that comply with 49 CFR Part 397.
    • Account for boil-off hold times if a tanker is delayed for hours on a saturated I-5 or closed Snoqualmie Pass.
    • Coordinate hazmat receiving windows with EHS (#2061) and local fire-marshal requirements.

    Connected Valley Cities, Segments & Role Briefs

    Primary Sources & Agency References

  • The Moses Lake Test Corridor (MWH): Moving Hardware From Puget Sound to Grant County

    The Moses Lake Test Corridor (MWH): Moving Hardware From Puget Sound to Grant County

    Stoke Space's Moses Lake test presence is documented in Census #1409 & #1415; Stoke's specific carrier contracts and truck schedules are NOT IN OUR DATA.

    FREIGHT, RAIL & VALLEY · SPACE HARDWARE · CENSUS + AGENCY CONTEXT (BOUNDARY NOTED)
    Moses Lake (MWH) Test Corridor
    Moses Lake's Grant County International Airport (MWH) anchors eastern Washington flight and propulsion testing (including Stoke Space's documented test site), connected to Kent solely via SR 18 / I-90 over Snoqualmie Pass.
    Primary Agency / Source: Port of Moses Lake / WSDOT / BC ESG Census  |  As-Of / Horizon: 2026-11-16
    FREIGHT, RAIL & VALLEY · PDF & MARKDOWN TWIN
    Moses Lake (MWH) Test Corridor — Reference Brief
    Download the 2-page printable reference PDF or read the clean Markdown twin for AI and engineering workflows.
    Puget Sound to Moses Lake (MWH): I-90 Corridor & Limits
    Puget Sound to Moses Lake (MWH): I-90 Corridor & Limits

    Documented Corridor Facts & Continuity Record

    • BC ESG Census #1409 (Moses Lake) and #1415 (Stoke Space) document Stoke Space's rocket-testing operations at Moses Lake alongside Kent manufacturing.
    • Port of Moses Lake (Grant County International Airport, MWH) provides long-runway air-cargo capacity and remote test infrastructure east of the Cascades.
    • NOT IN OUR DATA: Exact truck-by-truck routes, third-party heavy-haul carrier names, and shipment frequencies used by Stoke Space or other private operators are not publicly documented and are not reconstructed here.

    Puget Sound to Moses Lake Corridor: Documented vs. Not-In-Our-Data

    ElementStatusDetail
    MWH Test Site PresenceDocumented (#1409/#1415)Stoke Space test operations at Moses Lake
    Public Highway LinkDocumented (WSDOT)SR 18 / I-90 over Snoqualmie Pass (curfews + chain bans)
    Private Carrier / SchedulesNOT IN OUR DATANo public manifest of company-specific truck routes

    Operational Exposure & Facility Playbook

    • Any program relying on Puget Sound manufacturing + Moses Lake testing depends on I-90 Snoqualmie Pass staying open to oversize loads.
    • Winter test campaigns should pre-position spares and ground-support equipment at MWH before November pass restrictions.
    • Treat Columbia River / I-84 detour options as multi-hour emergency fallbacks subject to Oregon/Washington dual permitting.

    Connected Valley Cities, Segments & Role Briefs

    Primary Sources & Agency References

  • Urban Commuter Curfews (6–9 AM & 3–7 PM): Scheduling Oversize Space Moves Across I-5, I-90, and SR 18

    Urban Commuter Curfews (6–9 AM & 3–7 PM): Scheduling Oversize Space Moves Across I-5, I-90, and SR 18

    Curfew hours per WSDOT Commercial Vehicle Operations; exact milepost boundaries must be checked on each issued permit.

    FREIGHT, RAIL & VALLEY · SPACE HARDWARE · AGENCY REGULATION
    Urban OSOW Commuter Curfews
    WSDOT prohibits vehicles displaying 'Oversize Load' signs from operating during weekday 6:00–9:00 AM and 3:00–7:00 PM commuter curfews across Seattle-Everett corridors including I-5, I-90, SR 2, and SR 18.
    Primary Agency / Source: WSDOT Commercial Vehicle Operations  |  As-Of / Horizon: 2026-11-16
    FREIGHT, RAIL & VALLEY · PDF & MARKDOWN TWIN
    Urban OSOW Commuter Curfews — Reference Brief
    Download the 2-page printable reference PDF or read the clean Markdown twin for AI and engineering workflows.
    Puget Sound OSOW Curfews: 6–9 AM & 3–7 PM Windows
    Puget Sound OSOW Curfews: 6–9 AM & 3–7 PM Windows

    Documented Corridor Facts & Continuity Record

    • Special-permit vehicles required to display 'Oversize Load' signs face strict weekday peak commuter curfews in the Seattle-Everett metro region.
    • Standard curfew windows run 6:00–9:00 AM and 3:00–7:00 PM on major corridors including portions of I-5, I-90, SR 2, and SR 18.
    • A truck leaving Kent at 2:15 PM for Moses Lake risks hitting the 3:00 PM SR 18 / I-90 curfew before clearing the metro boundary.

    Daily Dispatch Windows for Oversize Space Hardware

    Time Window (Weekday)StatusDispatch Strategy
    09:00 AM – 03:00 PMOpen (6 hours)Primary daytime clear window for Kent -> I-90
    06:00 AM – 09:00 AMCURFEW BLOCKEDHold at origin or pre-staged yard
    03:00 PM – 07:00 PMCURFEW BLOCKEDDo not release; risk roadside citation

    Operational Exposure & Facility Playbook

    • Build 9:00 AM gate releases into launch-test and satellite-delivery SOPs so drivers clear SR 18 and North Bend well before 3:00 PM.
    • Combine curfew planning with Snoqualmie Pass avalanche-control schedules during winter.
    • Check permit-specific night-travel allowances before scheduling post-7:00 PM departures.

    Connected Valley Cities, Segments & Role Briefs

    Primary Sources & Agency References

  • WSDOT Oversize / Overweight (OSOW) Permits & Superloads: Moving Launch Stages and Tankage

    WSDOT Oversize / Overweight (OSOW) Permits & Superloads: Moving Launch Stages and Tankage

    Thresholds per WSDOT Commercial Vehicle Operations and WA RCW 46.44.

    FREIGHT, RAIL & VALLEY · SPACE HARDWARE · AGENCY REGULATION
    WSDOT OSOW Permits & Superloads
    WSDOT allows self-issued OSOW permits up to 16 ft wide, 16 ft high, 125 ft long, and 200,000 lbs GVW where routes clear—while heavier or taller space hardware triggers multi-week superload engineering reviews.
    Primary Agency / Source: WSDOT Commercial Vehicle Operations / RCW 46.44  |  As-Of / Horizon: 2026-11-16
    FREIGHT, RAIL & VALLEY · PDF & MARKDOWN TWIN
    WSDOT OSOW Permits & Superloads — Reference Brief
    Download the 2-page printable reference PDF or read the clean Markdown twin for AI and engineering workflows.
    WSDOT OSOW Thresholds: Self-Issue vs. Superload
    WSDOT OSOW Thresholds: Self-Issue vs. Superload

    Documented Corridor Facts & Continuity Record

    • Under WA RCW 46.44 and WSDOT Commercial Vehicle Operations rules, carriers moving non-divisible extra-legal loads require Single-Trip, monthly/annual, or Superload permits.
    • Routine self-issue single-trip permits generally cover up to 16 feet wide, 16 feet high, 125 feet long, and 200,000 lbs gross vehicle weight, subject to route clearances.
    • Loads exceeding 200,000 lbs or extreme dimensions require special WSDOT bridge/structural engineering reviews before permit issuance.

    WSDOT OSOW Permit Tiers for Space Hardware

    Permit TierTypical EnvelopeReview Lead TimeHardware Examples
    Self-Issue Single-Trip<=16' W, <=16' H, <=125' L, <=200k lbsSame-day (route clear)Upper stages, small-sat containers
    Superload Permit>200,000 lbs GVW or extreme dimsMulti-week engineeringLarge boosters, autoclaves, GSE

    Operational Exposure & Facility Playbook

    • Design shipping fixtures and transport cradles to stay within the 16' × 16' × 125' × 200k lb envelope whenever possible to avoid superload delays.
    • Never assume a route permitted in summer remains clear in winter when I-90 chain laws or SR 167 flood detours activate.
    • Verify pilot-car / escort and night-move lighting requirements on every permit.

    Connected Valley Cities, Segments & Role Briefs

    Primary Sources & Agency References

  • The Boeing 737 Fuselage Rail Precedent: ~1,700–1,800 Miles and the July 3, 2014 Clark Fork Derailment

    The Boeing 737 Fuselage Rail Precedent: ~1,700–1,800 Miles and the July 3, 2014 Clark Fork Derailment

    Primary-source check records ~1,700–1,800 miles (vs. 1,800–2,000 frame shorthand). July 3, 2014 derailment: 19 cars, 6 737 fuselages, 3 down embankment/river, all 6 scrapped.

    FREIGHT, RAIL & VALLEY · SPACE HARDWARE · HISTORICAL EVENT (DATED PRECEDENT)
    737 Fuselage Rail & 2014 Derailment
    Every Boeing 737 fuselage travels ~1,700–1,800 miles by rail from Wichita to Renton; on July 3, 2014, a 19-car Montana Rail Link derailment put three 737 fuselages into the Clark Fork River—the region's benchmark aerospace rail loss.
    Primary Agency / Source: BNSF / Montana Rail Link / Boeing Public Record  |  As-Of / Horizon: 2026-11-16 (Primary check: ~1,700–1,800 mi)
    FREIGHT, RAIL & VALLEY · PDF & MARKDOWN TWIN
    737 Fuselage Rail & 2014 Derailment — Reference Brief
    Download the 2-page printable reference PDF or read the clean Markdown twin for AI and engineering workflows.
    737 Rail Precedent: Wichita-Renton & July 3, 2014 Crash
    737 Rail Precedent: Wichita-Renton & July 3, 2014 Crash

    Documented Corridor Facts & Continuity Record

    • Every Boeing 737 fuselage moves approximately 1,700–1,800 miles by rail from Spirit AeroSystems in Wichita, Kansas, to Boeing's Renton final assembly plant (note: primary-source range is ~1,700–1,800 mi vs. 1,800–2,000 mi informal shorthand).
    • On July 3, 2014, 19 cars of a 90-car Montana Rail Link train derailed near Alberton/Superior, Montana, carrying six 737 fuselages plus 777/747 structures.
    • Three 737 fuselages plunged down the embankment into or beside the Clark Fork River; zero injuries occurred, but all six 737 fuselages were scrapped locally due to structural compromise.

    July 3, 2014 Clark Fork River Aerospace Rail Precedent

    DimensionDocumented FactLesson for Space Hardware
    Route & DistanceWichita, KS to Renton, WA (~1,700–1,800 mi)Long-haul out-of-gauge rail exposes structures to canyon/grade risk
    Derailment ScopeJuly 3, 2014; 19 of 90 cars near Alberton, MTTrack-alignment failures can occur far from origin/destination
    Cargo Loss6 737 fuselages (3 in/by river); all 6 scrappedZero-repair tolerance on flight-critical primary structures

    Operational Exposure & Facility Playbook

    • For Washington launch-vehicle and large-structure builders, the 2014 Renton-bound derailment is the closest public precedent for oversized aerospace rail risk.
    • Primary flight structures subjected to rail shock or water immersion typically cannot be recertified and must be written off as total losses.
    • Ensure transit insurance covers full replacement cost plus schedule-delay spares rather than standard carrier per-pound liability.

    Connected Valley Cities, Segments & Role Briefs

    Primary Sources & Agency References

BC ESG

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

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