For Eleven Years, a Federal Building Flew the Wrong State's Flag — and the Government's Fix Was Somehow Weirder
There's a version of bureaucratic failure that's annoying — the wrong form, the misspelled name, the check sent to the wrong address. And then there's a version that's so complete, so sustained, and so thoroughly unnoticed that it stops being a failure and starts being a philosophical statement about how institutions actually function.
For eleven years, a federal building in Washington D.C. flew the flag of the wrong state. Officially. On a flagpole. Outside. Where people walk past it every single day.
This is a real thing that happened.
How You Order a Flag for the Federal Government
In the 1960s, federal procurement — the process by which the government purchased everything from paper clips to aircraft carriers — ran on paperwork. Enormous quantities of paperwork, processed by clerks working through stacks of requisition forms, purchase orders, and specification sheets that described, in meticulous bureaucratic language, exactly what was being ordered and where it was going.
Flags were a routine procurement item. Government buildings flew them constantly, replaced them on regular schedules, and maintained inventories of state and territorial flags for ceremonial display purposes. The General Services Administration and its predecessors handled the logistics, and the system worked fine in the aggregate — which is to say, most of the flags ended up being the right flags.
Most of them.
The precise mechanism of the error that sent an incorrect state flag to a Washington D.C. federal building has never been fully reconstructed, which is itself a revealing fact. Somewhere in the chain — a transposed code number, a misfiled specification sheet, a clerk who grabbed the wrong item from a storage shelf — the wrong flag got packaged, labeled, and shipped to the wrong destination.
And then it got installed.
The Flag Goes Up
Installing a flag outside a federal building is not a complicated operation, but it is a documented one. There are work orders, sign-off sheets, maintenance logs. Someone physically attached the flag to the halyard, ran it up the pole, and presumably noted the completion of the task in whatever record-keeping system the building used.
At no point in this process did anyone apparently look at the flag and think: wait, that's not right.
This is less surprising than it sounds. State flags, particularly in the 1960s, were not the kind of thing most Americans could identify on sight with confidence. The Stars and Stripes is universal; individual state flags are a different matter. Unless you happened to be from the state whose flag was supposed to be flying — or the state whose flag was actually flying — the distinction probably wasn't obvious to the average maintenance worker, security guard, or administrative staffer going about their day.
So the flag went up. And it stayed up.
Eleven Years of Non-Noticing
What followed was a masterclass in institutional invisibility. Federal buildings don't stay static — staff turn over, administrators rotate, inspectors visit, budget auditors review expenditures, and facilities management teams conduct routine assessments. All of these processes happened, presumably, at the building in question over the course of eleven years.
None of them caught the flag.
This is worth sitting with for a moment. Eleven years is not a brief oversight. It's longer than most presidential administrations. It's enough time for the original procurement clerk who made the error to have been promoted, transferred, retired, or some combination of all three. The building itself would have seen multiple facility managers, multiple maintenance crews, multiple rounds of visitors.
The flag just kept flying.
It's tempting to imagine that someone, somewhere along the line, noticed something slightly off but couldn't quite articulate what it was — the vague sense that the colors weren't quite right, or the design wasn't matching some half-remembered image. But if anyone had that reaction, they didn't act on it, and no record of any internal flag-related concern from those eleven years has surfaced.
The Legislator Who Looked Up
The end of the flag's eleven-year run came courtesy of a visiting state legislator who happened to be in Washington D.C. for meetings related to his state's congressional delegation. The details of the visit itself were routine — the kind of trip state officials make regularly to maintain relationships with federal contacts and advocate for local interests.
At some point during a tour of the building, he looked at the flagpole.
He recognized the flag immediately, for the obvious reason that it was his state's flag — and it was flying outside a building that had no particular connection to his state. He raised the issue with his hosts, who apparently did not immediately understand what he was telling them. A flag is a flag. What exactly was the problem?
He explained. They looked. He was right.
The Government's Response, Which Was A Lot
What happened next is where the story takes its strangest turn. A reasonable institutional response to this discovery might have been: quietly replace the flag, update the records, and move on. Bureaucratic errors get corrected all the time without fanfare, and there was no particular reason this one needed to be anything other than a footnote in a facilities management log.
Instead, the correction triggered a formal internal review — which, in the process of trying to document how the error had occurred, discovered that the original procurement records were either missing or ambiguous enough that a definitive explanation couldn't be established. The review generated more paperwork than the original installation had. Multiple offices weighed in on questions of jurisdiction and responsibility.
The flag was eventually replaced with the correct one. The review concluded without assigning specific blame, which in federal bureaucratic terms is a kind of outcome. The building's flag log was updated.
And the wrong flag — the one that had been officially representing a state it had no connection to for eleven years — was, according to the most detailed accounts of the incident, placed into storage rather than disposed of, because disposing of government property also requires paperwork.
Somewhere, in some federal storage facility, it may still be there.
Flying nothing. Representing no one. Filed correctly, at last.
