The Hidden Arteries
The INCO Reform — Centralized Management vs. Project-by-Project Fragmentation
Three Projects in Twenty-Eight Years
The United States Army Corps of Engineers has completed approximately three major inland lock and dam modernization projects in the past 28 years. The Corps manages the inland waterway system that moves 500 million tons of freight annually — a system whose deferred maintenance backlog exceeds $100 billion, whose locks are operating decades past design life, and whose critical minerals and agricultural export functions are growing more strategically important by the year. The gap between the urgency of the problem and the pace of the solution is a governance problem, not a funding problem. The Inland Navigation Construction Organization proposal is the governance solution. It has not been enacted. This post explains why it should be.
The problem with the American inland waterway system's infrastructure investment is not primarily that Congress does not appropriate enough money. It is that the money Congress does appropriate — consistently less than what the system requires, but not negligible — is spent through a project management structure that virtually guarantees cost overruns, schedule delays, and a pace of completion that is incompatible with the urgency of the maintenance backlog.
The U.S. Army Corps of Engineers manages inland navigation infrastructure through its district system — nine districts, each responsible for a geographic portion of the inland waterway network, each with its own project management staff, its own contracting relationships, its own budget allocation, and its own reporting structure. A major lock modernization project — a new 1,200-foot lock chamber to replace a 600-foot chamber whose design life has expired — is managed by the district whose geographic territory contains the lock. The district competes for annual appropriations against every other district project and every other Corps mission (flood control, environmental restoration, harbor maintenance) in the annual appropriations cycle. If the project receives partial funding in one year, it must re-compete for its next year's funding increment against the same field of competing priorities. If the project is underfunded in a given year, the contractor holds, the mobilization costs accumulate, and the schedule extends — adding cost that future appropriations must absorb in addition to the original project budget.
How Project-by-Project Appropriations Turned a $775 Million Project into a $3 Billion One
The Olmsted Lock and Dam on the Ohio River — located near the confluence of the Ohio and Mississippi Rivers at the downstream end of the Ohio system — is the definitive case study of what the project-by-project appropriations structure produces when applied to a major inland navigation project. The project was authorized in 1988 to replace two aging lock and dam structures with a single modern facility. The original cost estimate was approximately $775 million. Construction began in the late 1990s. The project was completed in 2018. Final cost: approximately $3.1 billion — four times the original estimate, over a construction timeline that stretched 26 years.
The cost growth and schedule extension were not primarily products of engineering surprises or contractor failures. They were products of the appropriations structure. The project received annual funding allocations that were consistently below what efficient construction progress would require. When funding was insufficient to maintain contractor mobilization — the equipment and labor force on site — the contractor demobilized, the project paused, and the costs of remobilization in subsequent years added to the total. Interest on borrowed project financing accumulated over the extended timeline. Inflation increased material and labor costs relative to the original estimate. Each year of delay added cost that the original estimate had not included because the original estimate assumed a construction timeline that continuous funding would have supported.
The Olmsted experience is not unique. The Chickamauga Lock on the Tennessee River — a modernization project that has been in the project queue for decades — has followed a similar pattern: authorized, partially funded, construction started, funding insufficient for efficient progress, timeline extended, cost growing. The Kentucky Lock on the Tennessee-Tombigbee Waterway has experienced similar dynamics. The pattern is systemic, not exceptional, because it is the product of a systemic governance structure rather than project-specific mismanagement.
II. The INCO ProposalWhat a Programmatic Management Model Would Actually Change
The Inland Navigation Construction Organization proposal — developed in a white paper published jointly by the Waterways Council and HDR Engineering in early 2026 — recommends the establishment of a centralized programmatic management office within the U.S. Army Corps of Engineers at the headquarters level. The INCO would function as a dedicated program office for inland navigation construction, with a single Inland Program Manager accountable for the overall project portfolio, unified planning across all districts, lessons-learned sharing between projects, and the ability to treat the inland waterway system as a national asset rather than a collection of competing district projects.
The INCO model draws explicitly from successful examples of programmatic management within the Corps itself and in comparable federal infrastructure programs. The Corps' Dam Safety Program — which manages the safety inspection and remediation of federal dams across all Corps districts — uses a programmatic approach that sets national priorities, allocates resources across districts based on risk and urgency, and maintains a headquarters-level program office that provides technical standards, contracting templates, and management accountability for the entire portfolio. The Dam Safety Program has delivered projects more efficiently and more consistently than the project-by-project inland navigation construction process. INCO would apply the same management model to inland navigation construction.
What INCO Does Not Require
The INCO proposal's most important political characteristic is what it does not require: no new major funding authorization, no new agency creation, no legislative restructuring of the Corps of Engineers. The Waterways Council and HDR white paper explicitly frames INCO as an administrative reform achievable within existing statutory authority — a reorganization of how the Corps manages its existing inland navigation construction mission, not a new program requiring new law. Congress could direct the Corps to establish INCO through language in the Water Resources Development Act of 2026 — the biennial authorization bill that is already in process as of 2026 — without the appropriations fight that a new spending program would require.
This political characteristic is the INCO proposal's greatest strength and its most underappreciated feature. The inland waterway investment debate is typically framed as a funding argument — advocates arguing for more money, appropriators citing competing priorities, the system getting incrementally less than it needs in each annual cycle. The INCO proposal reframes the argument: the question is not only how much money, but how the money that is appropriated is managed. A Congress that is unwilling to significantly increase inland navigation appropriations might be willing to require that the Corps manage what it does appropriate more effectively — and INCO is the instrument for that requirement.
Adding Strategic Priority to the Project Selection Framework
The INCO white paper focuses primarily on the efficiency and delivery pace problem — the three completions in 28 years, the Olmsted pattern, the need for programmatic management. The series' contribution is to add a second dimension to the INCO framework: explicit integration of critical minerals logistics priorities into the project selection and resource allocation criteria that INCO would use to set its portfolio priorities.
Under the current project-by-project system, lock and dam projects are evaluated and prioritized based on benefit-cost analysis — primarily the economic value of the freight that the improved infrastructure would move more efficiently, measured in terms of transportation cost savings and reduced delay costs. This framework produces priorities that reflect the current commodity mix of the waterway system: projects that improve throughput on high-tonnage grain and coal corridors rank highly; projects on lower-volume corridors with emerging critical minerals freight rank lower, because their current freight value is smaller even if their strategic importance is larger.
An INCO framework with an explicit critical minerals resilience scoring element would correct this bias. A lock modernization project on the McClellan-Kerr Arkansas River Navigation System that enables the Inola aluminum smelter's long-term logistics viability — and creates the infrastructure platform for future rare earth and lithium processing facilities at MKARNS-connected locations — has a strategic value that pure benefit-cost analysis based on current freight does not capture. The INCO critical minerals overlay would require the program office to evaluate projects on a composite criterion that includes transportation cost savings, strategic resilience value for critical minerals supply chains, and national security benefits for Project Vault distribution and Battery Belt manufacturing logistics.
The WRDA 2026 Window
The Water Resources Development Act of 2026 — the biennial reauthorization bill that is in Congressional process as of this writing — is the most proximate legislative vehicle for INCO establishment. WRDA bills are among the most reliably bipartisan legislation in Congress: the inland waterway system serves agricultural, industrial, and energy constituents across both parties' coalition, and the infrastructure investment argument cuts across normal partisan divisions. A WRDA 2026 provision directing the Corps of Engineers to establish the Inland Navigation Construction Organization — with an explicit requirement to develop critical minerals resilience metrics for project prioritization — is achievable within the current legislative environment in a way that a separate standalone infrastructure bill might not be.
| Dimension | Current Project-by-Project System | INCO Programmatic Model | Expected Improvement |
|---|---|---|---|
| Project management | District-level; each project managed independently by geographic district | Headquarters-level program office; single Inland Program Manager; unified portfolio management | Consistent technical standards; lessons-learned sharing; reduced redundant overhead; accountability concentration |
| Funding continuity | Annual appropriations competition; projects compete against each other and other Corps missions | Programmatic budget allocation; multi-year project plans with defined funding profiles | Reduced start-stop cycles; lower remobilization costs; schedule predictability for contractors |
| Project selection criteria | Benefit-cost ratio based on current freight value; favors high-volume commodity corridors | Composite criterion: transportation savings + resilience value + critical minerals strategic importance | MKARNS and emerging critical minerals corridors receive priority weighting; strategic value captures forward-looking importance |
| Cost performance | Olmsted pattern: $775M estimate → $3.1B final; 26-year construction | Dam Safety Program pattern: consistent delivery within defined cost ranges; accountability for overruns | Estimated 20–40% cost reduction on comparable projects through elimination of start-stop inflation and remobilization costs |
| Legislative vehicle | Annual energy and water appropriations; WRDA biennial authorization | WRDA 2026 direction to establish INCO within existing Corps authority; no new funding authorization required | Achievable without new appropriations fight; bipartisan WRDA vehicle; implementation within 12–18 months of enactment |
| Pace of modernization | ~3 major projects in 28 years (1997–2025) | Modeled on Dam Safety Program delivery pace; target 2–3 major projects per 5-year cycle | 3–4x improvement in delivery pace; 1,200-ft lock modernizations on priority corridors within current decade |
| FSA Wall | The "20–40% cost reduction" and "3–4x improvement in delivery pace" estimates are analytical projections based on the comparison between current inland navigation construction performance and the Dam Safety Program's documented delivery performance. They are not from a published INCO cost-benefit analysis; the Waterways Council / HDR white paper does not provide specific quantified estimates of these improvements. The estimates are analytical inferences from the governance structure comparison, not audited projections. | ||
The Inland Waterways Trust Fund and the Cost-Sharing Framework
The Inland Waterways Trust Fund — funded by a per-gallon fuel tax on commercial vessels operating on designated inland waterways — provides half the construction cost of inland navigation projects, with the federal Treasury providing the other half. The Trust Fund was established in 1978 as a user-fee mechanism to ensure that the commercial waterway industry contributes to the capital cost of the infrastructure it uses. The current fuel tax rate is $0.29 per gallon — a rate that has not been increased since 2015 and has lost significant purchasing power to inflation over the intervening decade.
The Trust Fund balance and revenue have been a source of ongoing tension between the waterway industry and Congress. Industry advocates argue that the Trust Fund rate should be increased to provide more capital for navigation projects; fiscal conservatives argue that the existing rate already imposes a burden on an industry that competes with subsidized foreign waterway systems. The practical result is a Trust Fund that provides a meaningful but insufficient contribution to the project pipeline — enough to signal industry cost-sharing commitment, not enough to eliminate the appropriations gap.
The INCO reform does not require Trust Fund restructuring to be effective. But a Trust Fund rate increase — indexed to construction cost inflation so that the user fee maintains its real value over time — would provide a stable, predictable funding stream that complements the programmatic management that INCO provides. A programmatic management office that knows it will receive a defined annual Trust Fund contribution can plan its project pipeline and contractor relationships accordingly. A programmatic management office subject to annual Trust Fund revenue uncertainty cannot.
V. The Political Economy of ReformWhy This Has Not Happened — and What Has Changed
The INCO proposal is not new. Variants of the centralized programmatic management concept have been discussed in waterway infrastructure policy circles for years. The Waterways Council's early 2026 white paper represents the most developed and policy-ready formulation of the concept, but the underlying argument — that the Corps' district-based, project-by-project system is structurally incapable of delivering inland navigation projects efficiently — has been documented in Corps Inspector General reports, Government Accountability Office analyses, and Congressional Research Service studies for at least two decades.
It has not been enacted for the same reason that most administrative reform proposals in federal agencies are not enacted: the reform threatens the district-level autonomy and Congressional district-level earmarking that the existing system accommodates. A member of Congress from a state with a Corps district has a direct relationship with that district's project pipeline — the ability to advocate for specific projects that benefit constituents in specific geographic areas. A headquarters-level programmatic management office that sets national priorities based on composite criteria including strategic resilience value would reduce the district-by-district political influence over project selection that the current system preserves. Reform requires accepting that tradeoff.
What has changed as of 2026 is the strategic context. The Inola aluminum smelter's $4 billion investment and its explicit dependence on the MKARNS is the most powerful argument the waterway infrastructure reform community has had in decades: a documented, high-profile, nationally significant industrial investment whose long-term viability depends on waterway infrastructure that the current system is not maintaining or improving at an adequate pace. The Iron Loop series documented the merger as an act of infrastructure statecraft. The Inola project makes the MKARNS — and by extension the inland waterway system — an equivalent act of statecraft. That framing changes the political economy of the INCO argument from a transportation efficiency debate into a national competitiveness and critical minerals security debate.
The Olmsted Lock and Dam cost figures — original estimate ~$775 million, final cost ~$3.1 billion, 26-year construction timeline — are drawn from publicly documented Corps of Engineers project records, Congressional testimony, and published analyses of the project history. Precise cost figures may vary slightly depending on the accounting methodology and whether indirect costs are included; the figures cited reflect the range consistently cited in public documents.
The "three major projects completed in 28 years" characterization is based on the Waterways Council / HDR white paper's analysis of USACE inland navigation project delivery history. The specific count depends on the definition of "major project"; the characterization is used as an indicator of the delivery pace problem, consistent with how the proposal's authors characterize it.
The INCO proposal described in this post is based on the Waterways Council / HDR Engineering white paper released in early 2026. The specific governance structure, staffing model, and legislative vehicle proposed may evolve as the proposal advances through the policy process. The description here reflects the proposal as publicly documented as of early 2026.
The "20–40% cost reduction" and "3–4x improvement in delivery pace" performance estimates are analytical inferences from the governance structure comparison, not from a published INCO cost-benefit analysis or audited projection. They are presented as analytical estimates to illustrate the potential magnitude of improvement, not as precise projections.
Primary Sources & Documentary Record · Post 6
- Waterways Council, Inc. / HDR Engineering — "Inland Navigation Construction Organization" white paper, early 2026 (WaterwaysCouncil.org, public)
- U.S. Army Corps of Engineers — Olmsted Lock and Dam project history; cost and schedule documentation (USACE public project records)
- U.S. Army Corps of Engineers — Dam Safety Program structure and management model; programmatic delivery documentation (USACE.army.mil, public)
- Government Accountability Office — Reports on USACE project management and cost overruns; inland navigation construction delivery analysis (GAO.gov, public)
- U.S. Army Corps of Engineers Inspector General — Project management efficiency reports; district system documentation (USACE IG public reports)
- Congressional Research Service — Inland Waterways Trust Fund structure; WRDA legislative history; waterway infrastructure funding analysis (CRS Reports, public)
- Water Resources Development Act (WRDA) 2026 — Legislative process as of April 2026; navigation project authorizations under development (Congress.gov, public)
- Inland Waterways Trust Fund — Revenue and balance data; fuel tax rate history (Treasury/OMB public documentation)
- American Society of Civil Engineers — Infrastructure Report Card; inland waterways funding gap analysis (ASCE.org, public)
- Hidden Arteries: FSA Inland Waterways Architecture Series, Posts 1–5 — Trium Publishing House Limited, 2026 (thegipster.blogspot.com) — the project delivery context and strategic importance arguments developed across this series constitute the analytical foundation for the INCO critical minerals overlay proposal in this post

