STB Launches Probe into BNSF–Union Pacific Dispute in the US

STB initiates formal review of BNSF complaint over unequal dispatch

The Surface Transportation Board (STB) has opened a formal proceeding after BNSF claimed that Union Pacific (UP) does not afford equal dispatch priority on jointly used trackage originating from the 1996 UP–Southern Pacific merger protections. In FD 32760 (Sub-No. 52) the STB found that the dispute raises regulatory issues beyond a pure contract fight and asked both carriers to propose a joint procedural schedule by December 3, 2026. The Board’s decision does not yet find a violation or impose remedies; it sets the path for evidence collection and regulatory review.

What BNSF alleges and which RASA provisions are in dispute

BNSF contends that UP has prioritized its own trains in ways that conflict with the Revised and Amended Settlement Agreement (RASA) — specifically Section 9(d) and Appendix D dispatch protocols that emphasize first-in-first-out (FIFO) movement where applicable. BNSF claims examples of delayed windows, withheld pathing, and restrictive access windows on joint segments. The complaint lists operational points where BNSF trains experienced extended dwell times, and requests enforcement of the dispatch rules plus access to movement records to substantiate systemic bias.

Why STB treated the matter as regulatory rather than purely contractual

The STB explained that alleged conduct affecting access to border interchange points and shared corridors can implicate the merger conditions that were intended to preserve competition after the 1996 transaction. If proven, discriminatory dispatch that disadvantages a competing carrier could undermine the merger’s competitive protections—so the Board determined regulatory oversight is warranted to determine whether remedies beyond private arbitration are appropriate.

Specific lines and operational harms BNSF identifies

BNSF flagged multiple geographic and functional hotspots: the Eagle Pass border crossing into Mexico (and northern Spofford approach), Houston-area trackage, the Baytown corridor near Dayton, and the Rockport–Elmendorf segment. Its examples include trains held outside of authorized windows, lack of reciprocal reservation opportunities, and apparent preferential slotting favoring UP unit and manifest movements. BNSF characterizes these as not isolated anecdotes but patterns that, if corroborated by dispatch logs and timing data, would demonstrate systemic deviations from RASA protocols.

Union Pacific’s defense and arbitration argument

UP replied that BNSF’s examples are selective, dated, or anecdotal, and that UP has adhered to its obligations. Importantly, UP invoked the RASA’s Section 15 binding arbitration clause and asked the STB to dismiss or decline regulatory intervention in favor of arbitration under American Arbitration Association rules. UP argues arbitration is the contractually prescribed avenue for resolving operational disputes between the carriers.

How the STB weighed contract-based arbitration versus public interest review

The STB acknowledged the arbitration clause but distinguished disputes that, when proven, could alter the competitive balance the merger conditions were intended to protect. The Board indicated that the question is not whether a private contract remedy exists but whether the alleged conduct could affect the public interest in preserving competitive access on shared lines. In conclusion, STB maintained jurisdiction to develop a factual record on whether RASA obligations were honored in practice.

Remedies sought by BNSF and what STB has not decided

BNSF asked the Board to compel adherence to dispatch protocols, assess civil penalties for past breaches, require quarterly and annual compliance reports from UP, and grant access to movement data and records. The STB’s procedural order does not grant those remedies; it only recognizes that such regulatory tools could be within the Board’s authority if violations are proven. The Board has not yet ordered fines, mandated data sharing, or implemented forced dispatch changes.

What evidence and procedural steps are likely to be required

By asking for a procedural schedule, the STB signaled that discovery and document production will follow. Expected evidence niches include:

Dispatch logs and event tapes: timestamped records showing arrival/clearing times at control points to compare FIFO adherence.

Reservation and route records: formal requests for train slots and the disposition of those requests across carriers.

Operational policies and internal communications: instructions, bulletins, or exception approvals that indicate discretionary prioritization.

Performance metrics and dwell-time statistics: time-in-terminal and on-main metrics across comparable train types and corridors, presented as aggregated and train-level samples to test for systematic bias.

The Board will determine the scope of required production once parties submit their coordinated or competing schedules.

Why Eagle Pass is central and how border access differs from ordinary dispatch

Eagle Pass is a gateway to Mexico whose capacity and slot allocation directly affects cross-border traffic flows and shippers relying on binational chains. Access to border interchanges involves not only track time but coordination with Mexican rail operators, customs, and terminal windows. Discriminatory handling at a crossing can have ripple effects: missed interchange windows, missed vessel loads, and lost multimodal connections. The STB’s inclusion of RASA Section 4(a), which covers border access parity, reflects the Board’s recognition that border-related access disputes carry broader economic consequences than interior line skirmishes.

How a finding against UP could affect rail competition and shippers

A proven pattern of discriminatory dispatch can reduce a rival’s effective capacity, raise transit times, and degrade service reliability—outcomes that compress options for shippers and can entrench a dominant carrier’s market power on shared corridors. If the STB finds violations and imposes remedies (eg, enforceable dispatch protocols, reporting requirements, or penalties), the result could restore predictable slot access and create a compliance trail carriers must follow, which benefits competing carriers and shippers seeking choice.

Practical examples of data analyzes regulators will use

Regulators will likely employ comparative time-series and matched-pair methodologies. Examples include:

Matched-train comparison: Pairing BNSF and UP manifests of the same class and origin–destination over the same week to compare wait times and average transit speed.

Window-reservation fulfillment rate: Calculating the percentage of requested slots honored within a given corridor and comparing across carriers and months.

Regression analysis controlling for operating conditions: Modeling dwell time as a function of train type, length, crew availability, and track work to isolate an effect attributable to carrier identity.

Timeline and what to expect next

Both carriers must confer and propose a joint procedural schedule by December 3, 2026; absent agreement, they may file separate proposals. After the schedule is set, expect phased discovery, data production, deposits or written affidavits from operational witnesses, expert analysis submissions, and eventual hearings if disputes over facts persist. The Board will then decide whether to impose remedies based on the record it receives.

Implications beyond this case

The STB’s decision to exercise regulatory oversight signals that merger-condition protections remain enforceable and that the Board will scrutinize conduct that may subvert competitive access on shared lines. The outcome could set precedent for how dispatch disputes tied to merger safeguards are resolved and what evidence suffices to trigger regulatory interventions or enforcement tools.