Investigation · MH-APT
Built for the hub that left
A $1.7 billion terminal, its budget up 54 percent, opened in Pittsburgh for a level of traffic the region has not seen in twenty years.
Pittsburgh International opened a $1.7 billion terminal whose budget rose 54 percent, about $600 million, across four revisions. It was built for 13 to 15 million passengers a year. In 2024 the airport served 9.95 million. The Authority named $129.7 million in federal and $80 million in state money at the ribbon-cutting and stopped counting; its own audited report puts $1.25 billion in bonds outstanding and $2.5 billion in debt service running to 2056.
Pittsburgh International cut the ribbon on a new terminal in October 2025. The budget had risen 54 percent since it was announced, about $600 million across four revisions. The building was designed to handle 13 to 15 million passengers a year. In 2024 the airport served 9.95 million.
The gap is not a forecasting error so much as a legacy. Pittsburgh moved something near 20 million passengers in the late 1990s as a US Airways hub, and lost that status in 2004. The terminal is sized against a version of the region’s air traffic that has not existed in twenty years.
At the ceremony the Authority named the public money: $129.7 million federal, $80 million state. It stopped there. The rest of the financing is bonds, and the Authority did not total them at the podium or state what servicing them costs each year.
Its own audited report does. The 2024 figures put $1.25 billion in modernization bonds outstanding and $2.5 billion in debt service running out to 2056, against near-term annual service in the range of $77 to $81 million.
That figure carries a caveat that belongs in the body of the story rather than a footnote: the audited schedule is Authority-wide, covering both Pittsburgh International and Allegheny County Airport, and the report describes both bond series as financing the terminal program without separating them. The claim is graded accordingly below.
What the Authority says, and what has been checked
The Authority’s commissioned study puts the project at 14,300 jobs and $2.5 billion in economic impact. Those are its figures, archived and attributed, and nothing in this package tests them. They are reported as claims rather than adopted as findings, and the grade below says so.
What has not been disclosed is how many of the construction jobs become permanent. Airport Authority spokesman Bob Kerlik did not respond by deadline to questions on the total bonds, the annual debt service, or the permanent-job conversion. The non-response is recorded as a non-response.
What was withdrawn
The undisclosed bond total was first published here as an inferred residual of roughly $1.49 billion, reasoned backward from the disclosed grants. The audited 2024 report supplied the real figure and the inference was replaced with it. A stale $1.5 billion figure survives in one of the package’s own summary files and is superseded by the audited $1.25 billion outstanding.
The ribbon-cutting headline carried $1.75 billion, against a final cost of record of $1.7 billion.
Reading the archive
The published package carries the cost-revision series, the capacity dataset, the financing ledger, the debt-service schedule, a seventeen-claim fact-check, and eight sources captured and hashed. What it does not carry is any third-party timestamp on those sources, and no record of the verification gate actually being run. Both are set out in the reader contract at the foot of this page.
The 7 claims this piece carries
Each is graded, shown with the source it rests on, and marked with the one thing that would overturn it.
The terminal's budget rose 54 percent, about $600 million, across four revisions between September 2017 and April 2025.
ReceiptThe only two figures in this package pinned by equality rather than by a tolerance band, asserted at build.py lines 87 and 88 and re-derived from the cost-revision series on every run. The arithmetic actually yields 54.5 percent; the package floors it to match the published figure rather than rounding up, and says so.
Breaks ifA budget revision is missing from the series, or the announced 2017 figure of $1.1 billion is not the correct baseline for the program as built.
The terminal was designed for 13 to 15 million passengers a year. In 2024 the airport served 9.95 million.
ReceiptBoth figures are re-derived from the capacity dataset and byte-diffed against the committed summary, which fails the build on any difference. The package treats this pairing as the spine of the story rather than as a statistic.
Breaks ifThe design capacity was stated for a different measure than annual enplaned passengers, making the two numbers non-comparable.
The Authority disclosed $129.7 million in federal and $80 million in state money at the ribbon-cutting, and did not total the bond debt behind the rest.
ReceiptThe $209.7 million sum is re-derived and byte-diffed against the committed summary. The soft spot is the second half of the claim, which rests on the record of what was said at a public ceremony rather than on a document that can be re-derived.
Breaks ifA transcript or recording of the event shows the Authority did state a bond total or an annual debt-service figure.
The Authority's own audited 2024 report shows $1.25 billion in modernization bonds outstanding and $2.5 billion in debt service running to 2056.
ReceiptBoth are asserted from the audited report, at build.py lines 90 and 91, though as tolerance bands rather than exact equalities. The soft spot is scope, and it is a real one: the debt schedule is Authority-wide, covering both Pittsburgh International and Allegheny County Airport, and the 2024 report describes both bond series as financing the terminal program without isolating it.
Breaks ifA breakdown separating Allegheny County Airport's share shows a materially smaller figure attributable to the terminal program.
2024 demand ran 31 to 51 percent below the terminal's design capacity.
ReceiptRe-derived from the capacity dataset and byte-diffed. The soft spot is in how it is checked: the assertion at build.py line 89 bounds the low end only from below and the high end only from above, so the published range is not actually pinned to 31 and 51 the way the escalation figures are pinned to 54 and 600.
Breaks ifThe design capacity is a peak-hour or gate-count measure rather than an annual passenger figure, which would make the percentage comparison invalid.
The Authority says the project supports 14,300 jobs and $2.5 billion in economic impact.
ReceiptCarried from the Authority's own commissioned economic-impact study, archived and hashed, and attributed to them throughout. No assertion in the harness touches these figures and the package explicitly declines to adopt them as findings. They are what the Authority says, reported as such.
Breaks ifAn independent estimate, or the study's own methodology, returns a materially different figure, which nothing here has tested.
How many of the construction jobs become permanent has not been disclosed, and the Authority did not answer questions on it.
ReceiptAn open gap the package names as a gap. The Authority's spokesman, Bob Kerlik, did not respond by deadline to questions on total bonds, annual debt service, and permanent-job conversion. The non-response is recorded in the sources page rather than described as a refusal.
Breaks ifThe Authority publishes a permanent-jobs figure, or shows it answered before deadline.
The honesty flag
The conclusion turns on the pairing of a $1.7 billion build against 9.95 million passengers, and both figures are re-derived and byte-diffed. The weakest load-bearing element is the debt: $1.25 billion outstanding and $2.5 billion in service are graded Supported rather than Established because the audited schedule is Authority-wide and covers a second airport alongside this one. If a breakdown attributes materially less of that debt to the terminal, the financing half of the piece weakens and the capacity half stands untouched.
The reader contract
You are not asked to trust this. Every source behind the claims above was archived where it was read and fingerprinted with a SHA-256 hash, so you can confirm the copy you pull is the copy the reporting used. The dataset, the code that re-derives every figure, and the chain of custody are published in full.
How this record reached you
| Date | Released by | Received by | Purpose of change of custody |
|---|---|---|---|
| 2017-09 → 2025-04 | Allegheny County Airport Authority (budget revisions, audited reports) | B. Nuckols | Compilation of the cost-revision series and the financing ledger. |
| 2025-10-11 | B. Nuckols | West Hills Gazette | Publication of the ribbon-cutting story. |
| 2026-07-14 → 2026-07-16 | B. Nuckols | Public archive | Eight sources captured and SHA-256 hashed; harness built to re-derive the figures. |
The final row is blank because the chain has not closed.
- Archive and dataset
- https://bnuckols13.github.io/pittsburgh-airport-terminal-record/
- State of the archive
- All eight cited sources are captured and SHA-256 hashed, with a sidecar beside each file and a generated manifest, which is the part of this archive that holds.
- None of the eight carries a third-party archive snapshot. The archive is hash-fixed and self-hosted, with no independent timestamp: if an origin URL rots, the hashed local copy survives and no public mirror corroborates it. This is weaker than the water package, which carries nine.
- No capture dates are recorded. The manifest and the hash sidecars fix what was captured and not when, which is a gap in the chain of custody rather than in the hashing.
- Five of the eight archived sources are cited nowhere the harness reads. They are captured and hashed, but the verification script never resolves a claim against them.
- The debt figures are Authority-wide, covering both Pittsburgh International and Allegheny County Airport, rather than the terminal in isolation. The package states this; it is repeated here because it is the single most load-bearing caveat in the piece.
- Corrections ledger: no corrections recorded.
- If we got something wrong
- Corrections are appended, never silent, and each one has its own permanent address. See thecorrections ledger and the EJ-1 standard.
Get the next investigation
One email when a piece runs, plus the weekly wire. Every claim in it will carry its grade and the thing that would prove it wrong, the same as everything else here.
Not yet wiredNo email provider is configured, so this form is not rendered rather than shown as a control that silently does nothing. Set NEWSLETTER.endpoint in src/site.tsonce a provider is chosen.
No tracking pixels, no list sales, and one click unsubscribes without a survey.