The Container Barge Misallocation
When the real constraint is rail access, barges address symptoms—not system design.
Executive summary
In FY 2025, the Wando Welch Terminal handled approximately 1.15 million containers, while the rail-served Hugh K. Leatherman Terminal handled approximately 76,000 containers.
This imbalance matters. The simplest and most direct way to maximize ship-to-rail efficiency is to work vessels at a rail-served terminal—not to add secondary shuttles to move containers after discharge. A container barge may shift some moves off the road, but it does not change where vessels are worked or how rail is accessed. You can not barge your way out of a bad layout.
Bottom line: If the public goal is to reduce truck dependence and improve rail efficiency, shifting vessel calls to a rail-served terminal is simpler, more direct, and structurally durable than adding a container-moving barge.
Two primary-source anchors
A) SCPA’s own scope disclosure (quoted)
SCPA’s investor-facing material includes this statement:
“The NBIF and barge are not in the SCPA’s projected capital plan and outside of the scope of traditional port operations.”
Source slide: Open the cited SCPA slide →
B) SCPA internal economics summary (readable via link)
The clearest way to view the “~$9M annual loss” table is to open it directly (it renders sharply in a new tab even when the webpage view is compressed).
Exhibit link: Open the barge economics table →
What the record establishes about rail demand at Wando
Independent transportation planning documents establish a clear baseline for truck-to-rail container movements at Wando and the structural reason they exist: Wando operates at scale, but it is not adjacent to rail.
In its 2021 briefing memo prepared with Palmetto Railways, the South Carolina Department of Transportation (SCDOT) documented that in 2019 approximately 237,189 containers were trucked from the Wando Welch Terminal to the inland rail facility via I-526. The same memo states that approximately 23% of containers handled at Wando are destined for rail, requiring truck transfer due to the terminal’s rail-remote configuration.1
- A rail share of ~23% at Wando means nearly one in four containers must be transferred off-terminal to reach rail.1
- As total container volumes grow, the absolute number of truck moves grows mechanically.
- This is a structural outcome of terminal layout, not an operational anomaly.
In short, expanding volumes at a terminal that is not adjacent to rail mechanically increases truck traffic on I-526. A container barge may divert some moves, but it does not alter the underlying geometry of rail access.
I. The “I-526 fix” reality check
If the barge is justified as a congestion strategy, it must be measured against the actual scale of truck-dependent container movements that exist today. The practical question is not whether the barge moves some boxes—it is whether it materially changes the system’s dependence on trucks.
| Metric | Value | What it implies |
|---|---|---|
| Rail-bound share at Wando | ~23% | A structural driver of off-terminal container transfer |
| Assumed barge cap (stress test) | 200,000 / year | A best-case assumption for impact testing |
| System conclusion | Trucks remain a structural requirement | Even at optimistic barge volumes, most container traffic remains on the road network |
Plain-English takeaway: A barge can reduce some moves at the margin, but it cannot remove the underlying truck dependence created by a terminal that is not rail-served.
II. The operating tempo
It helps to translate the “200,000 containers per year” assumption into a simple throughput requirement at the terminal interface.
To move 200,000 containers per year—assuming 10 hours per day, 5 days per week—the terminal interface would need to sustain approximately:
~ONE CONTAINER EVERY 45–47 SECONDS
45 seconds assumes 50 work-weeks/year (250 days). 52 weeks/year (260 days) yields ~47 seconds.
This is not an argument that a barge is “impossible.” It illustrates the sustained operating tempo implied by the volume assumptions. Any credible plan should state hours, staffing levels, dwell time, disruption handling, and berth coordination in writing. That tempo must be sustained day after day, including during peak vessel windows and disruption events.
III. Reliability and operating complexity
Any high-frequency shuttle must show how it performs during peak vessel movements and how delays are managed. The point is not to sensationalize risk; it is to insist on an operations plan that is written, measurable, and accountable.
IV. The financial core: recurring operating losses
Why appropriate $223 million for a barge system that loses money annually and does not eliminate truck-dependent rail transfers from Wando — when a rail-served terminal already exists?A project can be justified for public-policy reasons, but the operating math must still be stated plainly. The linked “barge economics” exhibit summarizes SCPA’s projected recurring losses. If the barge is pursued, the state should require an explicit statement of who absorbs those losses, and under what limits.
Exhibit link (readable): Open the barge economics table →
V. Legislative accountability: three questions that must be answered
- Volume commitment. What container volumes does SCPA commit to moving by barge in FY2026, FY2027, and FY2028? Put the numbers in writing.
- Scope classification. Why is a container-moving barge described as “outside the scope of traditional port operations” in SCPA material? What budget line absorbs recurring operating losses?
- Simpler alternative. If the public goal is to reduce container trucks on I-526, what is the quantified impact of shifting a defined share of Wando’s vessel calls (for example, 20%) to the Leatherman system?
Sources
- 1 SCDOT / Palmetto Railways briefing memo (Traffic impacts on I-526), p. 75. View PDF →
- SCPA slide excerpt (“outside the scope…”): B-01 →
- Barge economics table (~$9M annual loss shown clearly via link): B-02 →