Category: Federal Agencies & Oversight

  • The Third Inspection: Krome Fails the Same Test Again, and Nobody Is Held Back a Grade

    Some institutions learn from their mistakes. Others simply learn to write better memos about them. The Department of Homeland Security’s Office of Inspector General has now inspected the Krome North Service Processing Center in Miami three times since 2023, and each time the findings read like a photocopy of the last, just with the dates changed and a few new appendices explaining why nothing much has improved. The latest report, OIG-26-29, documents an unannounced inspection conducted May 28 to 29, 2025, and covers overcrowding, food safety, use of force, medical neglect, and a facility that appears to be inventing new places to warehouse people faster than it can process the ones it already has. Notably, the report was not released until September 11, 2026, nearly sixteen months after the inspection itself, a delay the OIG attributes to three separate government shutdowns that ate up 123 days of the fiscal year. Apparently the government can furlough its watchdogs even while it keeps running the kennel.

    Building 9 and the Art of Improvisational Incarceration

    The headline number is simple enough to fit on a bumper sticker: on the first day of the inspection, Krome held 1,102 detainees against a maximum capacity of 882, a full 25 percent over. Six of fourteen intake hold rooms were over their posted limits, one by 56 percent, and inspectors found detainees standing or lying on the floor because there was nowhere else to put them. Krome had also converted two visitation rooms into overflow intake space, which is one way to solve a capacity problem, provided you don’t mind that it violates the standard meant to prevent exactly that.

    More striking is the twelve-hour rule. Detention standards cap how long someone can be held in an intake hold room before being processed and moved, precisely because hold rooms are not designed for extended stays. OIG inspectors found intake processing sheets, taped to the outside of hold rooms on May 28, dated May 26. An intake officer confirmed the obvious: people were being held well past the limit, in some cases for days, with a single opportunity to shower or brush their teeth regardless of how long they stayed. Krome’s explanation involved medical screening bottlenecks (no full-time X-ray technician, evidently a luxury) and general staffing shortfalls, which is a candid enough admission that the problem is structural rather than incidental.

    Then there is Building 9, a tent-like structure erected after the prior inspection cycle to serve as overflow housing during the intake crunch. Inspectors found detainees classified at different risk levels (low, medium-low, and high, denoted by wristband color) commingled inside it, which is precisely the scenario the classification system exists to prevent. Some classification forms were incomplete or missing supervisory sign-off entirely. Krome’s given reason, again, was volume: too many people coming and going for staff to finish the paperwork. It is worth noting that a companion report released the same day, OIG-26-22, found even more severe conditions at Florida’s now-shuttered “Alligator Alcatraz” facility, including detainees held in four-by-four-foot outdoor metal enclosures. Whatever is driving Florida’s detention system to improvise structures and shortcuts, it is not confined to one address. See The Calming Area and Whose Facility Is It Anyway for our full coverage of the Alligator Alcatraz inspection.

    Chicken, Grievances, and Fifteen Vacancies

    If the housing findings suggest a facility straining under volume, the food service findings suggest one that has simply stopped paying attention. Inspectors observed raw chicken thawing in three large vats, one with water running continuously over the sides and onto the floor, the other two with chicken submerged, uncovered, and out of its original packaging, sitting in standing water with no temperature control whatsoever. Two freezer gauges read 20 degrees Fahrenheit over the required maximum. A pallet of food marked “Keep Frozen” sat outside in direct sunlight for more than two hours while ambient temperatures ran between 82 and 90 degrees. None of this requires an advanced food safety credential to recognize as a problem; it requires someone walking through the kitchen occasionally.

    The medical findings follow a similar shape: real improvement in one narrow area, framed by neglect everywhere else. Sick call wait times dropped from five to seven days down to two or three, thanks to a new sign-up system, which OIG credits fairly. But medical grievances were not being logged or filed, a problem the OIG first flagged back in its 2023 inspection and which persists unchanged. There has been no Continuous Quality Improvement program since the position responsible for running one went unstaffed in April 2024. And the facility’s medical staff had fifteen vacancies at the time of inspection, including a Health Services Administrator position empty since February 2025 (its Assistant has been serving in an “acting” capacity ever since), one dental assistant for the entire detainee population, and eight recently departed nurses. A facility can build all the temporary tents it wants; it cannot conjure medical staff from an org chart with strikethroughs on it.

    Use of force fares no better on inspection. Of a five-incident sample drawn from 44 reported incidents over six months, two were flatly non-compliant: pepper spray deployed against a detainee described in Krome’s own after-action review as “offering no resistance,” with no follow-up medical evaluation and incomplete documentation of who was even involved; and a choke hold used during a cell search under circumstances that did not remotely meet the threshold requiring deadly force. Both incidents, notably, were caught and described honestly by Krome’s own internal review process, which raises an uncomfortable question the OIG report does not quite ask directly: if the facility’s own paperwork identifies the violation, why does the violation keep recurring?

    Grading Its Own Homework

    Appendix B of the report is where the real theater happens. ICE concurred with all nine recommendations, as agencies reliably do, and the OIG’s own scorekeeping tells the real story. Three recommendations (hold room capacity, classification commingling, and SMU recreation equipment) were closed based on evidence ICE supplied, largely photographs and inspection checklists. Six remain open, including the food safety and use-of-force recommendations, because ICE’s paperwork showed intentions and new procedures but not yet the sustained compliance the OIG wants to see documented over time. To its credit, the OIG is not simply rubber-stamping ICE’s self-assessment; it is explicitly withholding closure on the more serious findings pending better proof. That is more scrutiny than many oversight relationships manage. It is also, worth remembering, the third time this particular dance has been performed at this particular address, following near-identical findings in 2023 and again in OIG-24-21 in April 2024, both of which also ended in “concur” and a list of process fixes.

    None of this happens in a vacuum, either. Staff-detainee communication showed nearly a quarter of requests to ICE going unanswered past the three-day window, and 17 percent of facility responses marked “complete” contained no actual response at all, a bureaucratic sleight of hand that deserves its own category of dishonesty. Special Management Unit detainees, meanwhile, got an empty fenced lot with no recreational equipment while the general population played basketball and volleyball nearby, a distinction that says a good deal about what “special management” actually means in practice.

    Krome did get credit where it was due (the law library, legal materials, and attorney visitation rooms were all found compliant, an improvement from the prior cycle) so it is not as though the facility fails every category. But a facility that can fix its law library and still cannot keep chicken below room temperature, log a medical grievance, or finish a classification form on time is not suffering from a resource problem so much as a priorities problem. The paperwork trail from 2023 through 2026 tells a consistent story: identify the failure, promise the fix, provide a photograph of a checklist, and wait for the next unannounced visit to do it all again.

  • The Pentagon Spent Four Years Losing Track of $141 Million Meant to Arm Iraq Against ISIS

    There is a certain genius to a bureaucracy that can build an entire apparatus, complete with memoranda, standard operating procedures, and a coordination group that meets twice annually (on paper), and still lose track of $141 million. The Department of War’s Inspector General released a report on September 10 documenting exactly that: a program built to equip vetted Iraqi forces against ISIS that spent years shuffling paperwork between rotating officers who had, on average, ten days of handoff briefing before assuming responsibility for a multi-year, nine-figure equipment pipeline.

    The program is called the Counter-ISIS Train and Equip Fund for Iraq, or CTEF-I, and Congress has appropriated $414.7 million for its equipment component since fiscal year 2022. The findings, delivered with the OIG’s trademark flat affect, describe an institution that built the paperwork and then forgot to watch what happened to it.

    Endorsement at the Speed of Bureaucracy

    The USCENTCOM Syria-Iraq Train and Equip Cell’s own standard operating procedure, dated May 2020, allows 30 days to endorse an equipment request package once it clears initial submission; officials told auditors the real target, absent complications, is seven days. From October 2021 through May 2025, USCENTCOM missed that window on 53 of 80 packages, or 66 percent of everything submitted, worth $473 million. The average endorsement for those 53 took 131 days. One package, worth $8 million, took 592 days: nearly a year and a half spent bouncing a request back and forth over a missing mission statement and an unidentified vetted officer, a delay that survived two full personnel rotations before anyone resolved it.

    The report’s timeline reconstructions read like a workplace comedy with body armor at stake. A package submitted in April 2022 sat untouched for a year because nobody on either side followed up, during which the CJTF-OIR staff assigned to it rotated out twice. When someone finally looked again, the fix required months of back-and-forth over a single missing detail: an officer’s job title.

    None of this is because the underlying paperwork was bad. Auditors reviewed all 80 justification letters submitted over the audit period and found every one contained the required justification and capability gap analysis. The problem was never the writing; it was what happened to the writing after it was submitted.

    An Institutional Memory That Rotates Out Every Six Months

    The report’s central diagnosis is almost sympathetic, in the way autopsies are sympathetic: CJTF-OIR’s Directorate of Military Assistance, the unit actually responsible for tracking equipment through a process that can run more than four years, is staffed entirely by individually deployed service members on six to twelve month rotations. Do the math and a single equipment request can pass through the hands of eight different people before it reaches an Iraqi unit. The handoff between each of them, per the Directorate’s own Director, consisted of ten days of briefing from the outgoing officer.

    USCENTCOM’s civilian contractor staff, by contrast, do not rotate and could in theory provide the institutional continuity the military side lacks. Except the OIG found that USCENTCOM’s own SITEC office quietly stopped performing duties its 2020 SOP explicitly assigns it, including maintaining a tracker of procurement status and liaising with procurement commands, and let those responsibilities drift onto the rotating military personnel it was supposed to be backstopping. The one CTEF-I-specific training event that did exist, an annual conference, was not scheduled around rotation dates and was designed to build the next budget request rather than teach anyone how to track equipment already in the pipeline.

    The result is a program tracked across at least four separate, non-interoperable systems (a USCENTCOM tracker, the Security Cooperation Information Portal, a Defense Security Cooperation Agency tracker, and a CJTF-OIR demand tracker), each using its own case numbers, with no end-to-end view of where any given shipment actually stands. CJTF-OIR personnel told auditors they did not even have system access to see what equipment was scheduled to arrive in Kuwait; they found out when it showed up.

    Where the $141 Million Went

    The consequences arrived in three flavors. First, $64 million in equipment sat in Kuwaiti warehouses as of May 2025 awaiting reallocation because the original requirement had lapsed, including body armor and Soviet-style machine guns that have been in storage since 2017. CJTF-OIR trimmed that pile to $19 million by February 2026, an improvement the OIG credits while noting the remainder still needs a plan: reassign it, return it, or dispose of it.

    Second, $25 million in fiscal year 2024 equipment funds simply expired on September 30, 2025, unobligated, because the endorsement backlog ate the clock. CJTF-OIR had to raid fiscal year 2025 money to cover the requirements the expired funds were supposed to fund, a shell game the OIG classifies, without euphemism, as waste.

    Third, and worst, $52 million worth of equipment across 128 line items was still sitting somewhere in the procurement pipeline as of August 2025, never having shipped to Kuwait, with nobody able to say whether the original requirements were still valid. Eighteen of those line items were endorsed and funded at least five years ago and still have not reached a Partner Force unit. The tracker that surfaced this figure was compiled manually by a separate Army command and had not been updated in six months when investigators found it; it also only goes back to 2019, meaning the true backlog could be larger and simply invisible.

    Layered on top of the equipment mess is Finding B, which is almost a separate scandal wearing the same report’s clothes: the policy office responsible for aligning CTEF-I with strategic goals convened zero coordination-group meetings in all of 2025, despite a 2022 memo requiring two per year, and the operational command responsible for quarterly campaign assessments completed exactly two of them between fiscal year 2022 and the third quarter of fiscal year 2025. Both processes were, in the OIG’s careful phrasing, “initiated, but later suspended.” Nobody documented the decision to stop.

    Six Recommendations, Two of Which USCENTCOM Would Rather Not Discuss

    The OIG issued six recommendations. Four landed as “resolved”: the policy office agreed to restart its coordination group, and CJTF-OIR agreed to sort out the reallocation backlog and the stalled shipments, with an internal deadline of September 30, 2026. The other two, both aimed at USCENTCOM and asking for a comprehensive tracking mechanism and a real standard operating procedure, were met with responses the OIG describes as neither agreeing nor disagreeing, and which “did not address the specifics of the recommendation.” USCENTCOM’s counteroffer was a promise to stop accepting incomplete packages by October 1, 2026, which the OIG points out does nothing about the four years of packages already lost in the machinery. Both recommendations remain open and unresolved, and the OIG has given USCENTCOM 30 days from the report’s release to try again.

    At least $71 million of the money involved is, in the OIG’s own accounting language, funds that could still be put to better use. Whether it gets there depends on an institution that has already demonstrated it can build a tracking system, forget to use it, and still call the paperwork complete.

  • Five Billion Dollars for the Bureau of Prisons, and a Watchdog on a Diet

    Every so often Congress does something almost touching in its honesty. Buried in the reconciliation act it passed last July, the same 800-plus page monument to legislative multitasking that reshaped Medicaid, tax brackets, and the national debt ceiling in a single afternoon, lawmakers also found room to hand the Federal Bureau of Prisons five billion dollars. They then, in the very next breath, ordered their own watchdog to make sure the Bureau did not blow it.

    That watchdog, the Department of Justice’s Office of Inspector General, announced in April that it was standing up a new oversight effort to track how BOP spends the money. Its first product is a public dashboard, the kind of thing that looks reassuring right up until you notice how much of the actual accounting still has to be taken on faith. The rest of the story lives in the fine print: a Senate committee report that reads less like appropriations boilerplate and more like a parent handing a teenager the car keys along with a very specific list of rules about curfew.

    The Fine Print of a Windfall

    Section 100056 of Public Law 119-21 is admirably specific for a document buried in a bill mostly concerned with tax brackets and Medicaid work requirements. It appropriates five billion dollars to BOP, available through fiscal year 2029, and it splits the money with the precision of a divorce settlement: not less than three billion for hiring and training new employees, not more than two billion for maintenance and repairs. Congress, in other words, built its own priorities into the statute rather than trusting the Bureau to sort it out.

    That specificity is not decoration. It is a tacit admission of where BOP has been failing for years. The correctional officer shortage has been a fixture of oversight reporting since before the pandemic, and the Senate Appropriations Committee’s own report accompanying the bill spends paragraphs on “augmentation,” the practice of pulling teachers, psychologists, and other non-custodial staff into cellblocks to cover shifts. The Committee has been complaining about this since 2017. Nine years is a long time to keep writing the same sentence into a report and expecting a different result.

    The maintenance side is no less telling. BOP’s own facilities director told a Senate Judiciary hearing in 2024 that the repair backlog had grown to roughly three billion dollars, a figure driven by roofs that, in her memorable phrasing, keep crumbling. Two billion dollars against a three billion dollar backlog is progress, arguably, though it is also an admission that the hole is deeper than the shovel.

    A Base Budget That Refuses to Move

    Here is the detail that ought to embarrass everyone involved. While Congress was carving out five billion dollars in emergency supplemental funding, it also passed BOP’s ordinary fiscal year 2026 budget in that same Senate report, and that budget did not move an inch. Salaries and Expenses: $8,392,588,000, identical to the year before. Buildings and Facilities: $179,762,000, also identical. The entire burst of new money for staffing and repairs is arriving through a one time, off cycle appropriation that expires in 2029, while the underlying, permanent budget line for facility maintenance remains smaller than a single semiconductor plant’s monthly grocery bill.

    This is not how a healthy institution gets funded. It is how you patch a hole in the hull without ever addressing why the ship keeps taking on water. When the five billion dollars runs out, whatever the Bureau has built or hired will need to be sustained on a base budget that, as of this writing, Congress has shown no interest in growing. The supplemental is not a fix. It is a loan against a problem nobody has committed to solving permanently.

    The Watchdog Gets a List of Chores, Not a Raise

    The Committee did not simply hand BOP the money and walk away, to its credit. Section 100056 comes with an explicit oversight mandate: BOP must deliver a spend plan to the Inspector General and the relevant committees within 120 days of enactment, broken out by fiscal year, and the OIG must then assess whether the money is going where it is supposed to, flag risks, and report back, in one document or several, as it sees fit. That deadline landed around the first of November. Whether BOP hit it is, as of this writing, an open question, and one worth a formal records request rather than a press release.

    What makes the arrangement almost darkly comic is the OIG’s own budget. The same report that ordered this new layer of scrutiny also notes that the Inspector General’s office has fielded more than 27,000 complaints about BOP misconduct over the past three years, that roughly 57 percent of all OIG investigations already concern the Bureau, and that the office’s total appropriation for the coming year is a flat $139,000,000, not one dollar more than last year. Congress has, in effect, assigned its watchdog a second job and declined to adjust the salary. The gap between what oversight is tasked to do and what it is resourced to accomplish runs through federal oversight broadly — see The Inspectors General Say They Returned $17 for Every $1 Spent, our examination of what the federal IG community’s headline return-on-investment figure actually measures. If the review is thin, if it takes longer than anyone would like, the reason will not be a mystery.

    A Track Record That Argues for Skepticism

    None of this occurs in a vacuum, and BOP has not exactly earned the benefit of the doubt. A GAO report from last year found the Bureau had implemented only 33 of 87 recommendations from restrictive housing reviews conducted back in 2014 and 2016, a full decade of foot dragging on its own watchdog’s advice. A separate GAO report, issued just weeks before this piece went to press, is already circling the same five billion dollar appropriation, which suggests the Government Accountability Office does not share the confidence implied by a shiny new dashboard either.

    Meanwhile, the infrastructure money is not flowing into an oversight vacuum so much as a politically charged one. BOP’s own fiscal year 2027 budget documents request another $152,000,000 to plan the reactivation of USP Alcatraz as a working prison, a proposal that generates headlines far more easily than it generates cell capacity, while simultaneously rescinding $400,000,000 in prior year construction balances, most of it from the long contested Letcher County, Kentucky project. Money is being pulled from one embattled site and pushed toward a defunct national landmark, all while the base maintenance budget sits frozen and the emergency supplemental is supposed to cover the difference.

    The Inspector General’s dashboard is a start. It is not, on its own, an answer to the question Congress ought to be asking itself: why does an agency with a documented decade of ignored recommendations, a stagnant base budget, and a watchdog running on last year’s allowance keep getting bailed out with emergency cash instead of a permanent fix. Five billion dollars buys a great deal of goodwill. It does not, on the evidence so far, buy a plan.

    See also Forty Reports, Zero Referrals — on a six-month OIG period that produced 40 investigative reports on theft and fraud at federal grantees and zero criminal referrals to DOJ — and The Auditors Said Fine. The Administration Said Gone. Congress Said Neither. — on the Legal Services Corporation’s clean FY2025 audit conducted while the White House was trying to eliminate the agency.

    This is the first in an ongoing series tracking BOP’s implementation of Public Law 119-21. A records request regarding the Bureau’s spend plan submission is pending; a follow up will run when it is resolved.

  • The $664 Million SSA Chose Not to Collect

    A federal agency losing money to fraud is a story as old as the ledger. A federal agency losing money because it declined, for years at a stretch, to open its own mail is something rarer, and considerably more damning. That is the finding buried inside the Social Security Administration Office of the Inspector General’s latest audit, “Supplemental Security Income Earnings Alerts” (Report 022310, September 2026), a document that manages to be both bone dry and quietly incendiary.

    The Alert Nobody Answered

    SSI recipients are supposed to report their income every month, since the program exists for people with limited means and the payment shrinks as earnings rise. When the IRS or a state agency reports wages that don’t match what SSA has on file, the system throws an earnings alert. An employee is then required to contact the recipient, verify the discrepancy, and adjust the record accordingly. This is not an exotic obligation; it is described in plain terms in SSA’s own Program Operations Manual System (POMS SI 02310.005, SI 02310.062).

    OIG pulled a random sample of 100 SSI recipients out of a population of 417,291 who had at least one earnings alert pending as of September 2024. The results were not flattering. Employees fully resolved alerts for 20 of the 100. For 63 recipients, reviews were either never started or never finished, and as of April 2025 those alerts had been sitting for an average of 733 days, roughly two years of an unopened envelope. Nine of them had been pending for more than five years. For another 17 recipients, staff cleared the alert but failed to record all the earnings that should have changed the payment, which is less “resolved” and more “closed and mislabeled.”

    The Fine Print That Makes Delay Profitable

    Here is where the report stops being merely embarrassing and becomes structurally interesting. SSA operates under an administrative finality rule, and absent a finding of fraud, the agency generally cannot reopen and revise eligibility determinations more than 24 months old. If an employee reviews an alert within six months of its creation, that counts as diligent pursuit, and SSA can reach back a full 24 months from the original alert date to recover an overpayment. If the employee does not meet that standard, the 24 month window instead runs from whenever the review finally happens, however late. Every month of institutional foot dragging is a month of debt quietly aging out of collectability.

    OIG’s own example makes the mechanism vivid. A father’s 2017 earnings discrepancy triggered an alert in July 2018. An SSA employee scheduled two appointments in 2019, the father missed both, and the file simply sat there. By 2026, the alert had gone unresolved for over seven years, and the agency estimated it had paid the child recipient roughly $36,000 that hinged on the father’s unreported income. Because nobody picked the file back up until 2026, SSA could only recover approximately $19,000 of it. The other $19,000 became, in the agency’s own language, correct, a status it acquired not through verification but through neglect.

    A Billion Dollars, Filed Under Never Mind

    Projected across the full population, OIG estimates SSA paid about 333,800 recipients roughly $1 billion they were not eligible to receive, because employees did not complete, or did not correctly complete, the earnings reviews required to catch it. Of that billion, the administrative finality clock has already rendered approximately $664 million permanently uncollectable, absent a fraud determination the agency has shown no particular urge to pursue. The remaining $344 million is, for now, still theoretically recoverable, assuming anyone gets around to it.

    It is worth sitting with that arithmetic for a moment. Two thirds of the overpayment total identified in this single sample projection is not merely uncollected; it is uncollectable by design, a feature of the agency’s own finality doctrine rather than a bug in enforcement. SSA did not lose this money to a sophisticated fraud ring. It lost it to a filing cabinet.

    Nobody Home

    Perhaps the most telling line in the entire report is the one OIG offers almost in passing, that auditors “could not determine why employees did not initiate or complete reviews of earnings alerts in accordance with Agency policies, and Agency subject-matter experts could not provide an explanation.” Not a bad explanation. No explanation. The people whose job it is to know why their own agency’s controls failed had nothing to offer.

    This is also not SSA’s first rodeo with this exact problem. A 2012 OIG review found the agency was not timely developing earnings alerts and estimated roughly $110 million in preventable or recoverable SSI overpayments. SSA responded then with the standard bureaucratic liturgy, reminders issued, guidance reissued, a promise to do better. Fourteen years later, the same failure mode reappears at nearly ten times the estimated cost. SSA has once again agreed to implement OIG’s three recommendations, namely clean up the 63 unresolved cases and the 17 incomplete ones, figure out why staff aren’t pursuing alerts, and implement corrective action. The agency’s official comment, from Chief Risk Officer Chad Poist, characterizes some of the flagged cases as simply not yet due for redetermination under existing timelines, and notes that corrective action has already been completed on a portion of the cited cases, a caveat OIG’s own report does not credit.

    Whether this round of promises fares any better than the last is not a question this audit answers, and it is not one the agency seems especially eager to answer either. What the report does establish, in the agency’s own numbers, is that the cost of that uncertainty is not abstract. It has a dollar figure, it has a 24 month expiration date, and as of the report’s own projections, most of it will be gone before anyone in Baltimore gets around to reading the file.

    Source: SSA Office of the Inspector General, “Supplemental Security Income Earnings Alerts,” Report 022310 (September 2026).

    For related coverage, see The Actuary's Gift — on how SSA's chief actuary pre-scored a $316 billion SSI expansion for Speaker Emerita Pelosi's office the same week this audit landed, including a provision that would quintuple the resource limit SSA already cannot reliably verify.

    Fediverse Reactions
  • Congress Wants AM Radio Back in Your Car. It Isn’t About the Music

    In an age when a car dashboard can stream Spotify, display satellite imagery, make phone calls, provide turn-by-turn directions and occasionally demand a software update before breakfast, Congress has decided there is one piece of technology American motorists still need.

    AM radio.

    The House of Representatives passed the AM Radio for Every Vehicle Act of 2025, H.R. 979, by voice vote on September 15. The legislation would require automakers to provide access to AM broadcast stations in new passenger vehicles sold in the United States without charging consumers an additional fee.

    At first glance, the legislation has the unmistakable appearance of Congress riding to the rescue of a technology that predates commercial television.

    The reason for the bill is considerably more practical.

    The EV Problem

    Automakers have increasingly removed AM receivers from some electric vehicles. Electric motors, high-voltage systems and other components can generate electromagnetic interference that degrades AM reception.

    Rather than engineer around the interference, some manufacturers simply stopped providing AM reception in certain models.

    Congress noticed.

    The Congressional Budget Office says the legislation would primarily affect electric vehicle manufacturers that have already removed AM equipment or announced plans to do so. CBO estimates that roughly 2 million to 2.5 million vehicles per year would require updated radio equipment under the legislation.

    The agency does not expect compliance to break the automotive industry’s piggy bank. CBO estimates the mandate would cost manufacturers several million dollars annually, primarily for software updates and modifications to radio components. [Congressional Budget Office, March 16, 2026]

    The automobile industry has nevertheless objected to the mandate. The Alliance for Automotive Innovation has argued that Congress is requiring manufacturers to preserve a particular technology rather than focusing on the broader capability of delivering emergency information to motorists.

    That distinction gets to the heart of the debate.

    AM Radio Is Part of the Emergency System

    Congress is not preserving AM because lawmakers are worried Americans might lose access to talk radio, baseball games or the peculiar experience of driving through three states while listening to the same distant station after sunset.

    The primary argument is emergency communications.

    Broadcast radio remains part of the federal Emergency Alert System and the broader Integrated Public Alert and Warning System. The FCC identifies analog AM and FM stations among Emergency Alert System participants, and says FEMA’s national emergency message is distributed through a network that includes highly resilient AM broadcast stations and satellite services. [Federal Communications Commission, FCC 25-50]

    That matters for reasons that extend beyond disasters knocking modern communications systems offline.

    Some Places Start With the Backup System

    Emergency communications discussions often begin with a familiar scenario. A hurricane, wildfire, earthquake or widespread power failure damages cellular and internet infrastructure, leaving residents searching for another way to receive information.

    But there is another category of American community where the problem exists before the emergency begins.

    Large rural and remote areas still have uneven access to cellular voice and broadband service. The FCC continues to collect and map mobile coverage by technology, speed and even whether the user is stationary outdoors or traveling inside a vehicle. The existence of those federal coverage datasets reflects a simple reality. Modern wireless service is extensive, but it is not universal. [Federal Communications Commission, Broadband Data Collection]

    AM broadcasting has historically filled some of those geographic gaps. The FCC itself has described AM stations as frequently providing the only radio service available to listeners in certain circumstances, particularly people living in or traveling through rural areas. The Commission has also called AM a crucial service to rural communities and noted its role in providing information during emergencies and natural disasters. [Federal Communications Commission, FCC 07-218]

    That creates an important distinction in the debate over removing AM receivers from automobiles.

    In one community, AM may become useful because the cellular network failed.

    In another, AM may already be the communications system with the greatest practical reach.

    A smartphone can contain extraordinary communications technology and still display “No Service” when the nearest functioning network is beyond reach. Internet-based emergency systems face the same geographic limitation when connectivity is unavailable. FM radio generally operates over shorter practical distances than lower-frequency AM broadcasting.

    For emergency planners, this means the value of AM cannot necessarily be measured by asking how many Americans listen to it during an ordinary morning commute. The smaller population living or traveling beyond reliable cellular, broadband or FM coverage may be precisely the population for whom an AM receiver remains most valuable.

    And disasters can make the distinction worse. FEMA maintains communications-impact data showing cell-tower outages during major incidents using information collected through the FCC’s Disaster Information Reporting System. During Hurricane Helene, for example, the FCC separately tracked outages affecting wireless infrastructure and broadcast stations across the affected states. [Federal Emergency Management Agency, TEMPO Communications Impacts]

    The argument for AM, then, is not simply that it survives when newer technology fails. In some parts of the country, newer technology may never have provided equivalent coverage in the first place.

    Congress Built an Expiration Date Into the Mandate

    The legislation does something else that makes it more interesting than a simple technology-preservation bill.

    The requirement expires.

    H.R. 979 directs the Department of Transportation to issue the AM-access rule within one year of enactment. The rule would sunset eight years after the legislation becomes law.

    Congress also wants someone to determine whether AM is actually as important to emergency communications as its defenders maintain.

    The bill directs the Government Accountability Office to examine the role AM broadcasts received in passenger vehicles play in disseminating emergency alerts through IPAWS. GAO would have one year to report its findings.

    DOT would also be required to report to Congress at least every five years on the effects of the regulation.

    CBO estimates that implementing the federal portions of the legislation, including work by DOT and GAO, would cost approximately $1 million between 2026 and 2031. [Congressional Budget Office, March 16, 2026]

    The structure effectively creates a temporary preservation order while the government studies the technology it is preserving.

    Keep the radios. Study whether they are still necessary. Revisit the question later.

    There are worse approaches to infrastructure policy.

    Old Does Not Necessarily Mean Obsolete

    The automobile industry’s objection deserves consideration.

    If emergency warnings can reliably reach motorists through cellular networks, satellite systems, FM broadcasting and newer digital technologies, permanently requiring one specific communications technology could eventually become difficult to justify.

    Congress appears to have left room for that possibility through the sunset provision and GAO study.

    But the legislation also raises a broader question about the country’s increasingly interconnected infrastructure.

    Technological progress usually rewards efficiency, speed and capability. Emergency preparedness sometimes rewards something different.

    Redundancy.

    A communications system does not necessarily have to be sophisticated to remain useful. Sometimes its value comes from the fact that it operates differently from everything surrounding it.

    AM broadcasting is approaching its second century as a mass communications technology. It is noisy. It is susceptible to interference. Its audio quality will not inspire anyone shopping for premium speakers.

    Yet Congress is now considering whether that stubborn old signal may still deserve a place inside one of the most technologically sophisticated machines most Americans own.

    The House has made its decision for now.

    The Senate gets the next turn of the dial.

    Fediverse Reactions
  • Whose Facility Is It Anyway

    The Department of Homeland Security has a defense for what happened at Alligator Alcatraz, and it is a good one, in the sense that lawyers use the word good. DHS told its own inspector general that it never held a contract to manage detention space at the Florida Soft-Sided Facility. Florida, the department says, detained people there under authority delegated through Section 287(g) of the Immigration and Nationality Act, and Florida ran the place day to day. It is a tidy argument. It is also contradicted, point by point, by evidence gathered during the same inspection that produced it, evidence that happens to include a paper trail worth over six hundred million dollars.

    The Argument From Absence

    Section 287(g) is the mechanism by which the federal government deputizes state and local authorities to perform immigration enforcement functions they would otherwise lack the power to perform. It is a genuinely useful tool for describing how Florida came to be in the detention business at all. What it does not do, on its own, is answer the question OIG actually asked, which is not “who had legal authority to detain these people” but “who was actually running this facility, and who is accountable for what happened inside it.” DHS answered a question nobody put to it and left the one that mattered sitting on the table.

    The department’s response, as recorded in the report, amounts to three moves: no direct contract existed, Florida held operational authority, and the facility has since closed anyway so the point is largely academic. Each of these statements can be true and still fail to describe reality. OIG did not simply accept the framing. It went and checked.

    There is also something worth noticing in the timing of the third move. DHS’s response leans on the fact that the facility had already closed by the time the report came out, as though a closed facility retroactively becomes nobody’s responsibility. This is precisely backward. The facility’s closure does not answer who ran it while it was open. It only ensures that whoever did will never have to answer under active operational pressure, since there is no longer an operation to pressure.

    What the Inspectors Actually Found

    The report documents ICE personnel present on site. It documents ICE informational materials posted throughout the facility, the kind of signage that exists precisely so detainees and staff both understand whose rules apply. It documents ICE’s own involvement in facilitating the inspectors’ entry to conduct the inspection in the first place, which is an odd thing for an agency to arrange on behalf of a facility it claims not to run. None of this required subpoenas or forensic accounting. It required inspectors to look around the building DHS says was not its concern and write down what they saw.

    Then there is the money, which tends to settle arguments that language cannot. FEMA obligated $608.4 million to the Florida Division of Emergency Management for the temporary detention facility on September 30, 2025, and disbursed $58.3 million of that sum on May 15, 2026, categorized as allowable operational costs. Operational costs is doing a great deal of quiet work in that sentence. Money does not get classified as an allowable operational cost for a facility the paying agency considers someone else’s problem. FEMA is a component of DHS. The department that told its own watchdog it had no direct hand in managing this facility was, at the same time, the one holding the checkbook and deciding which of the facility’s expenses counted as legitimate.

    Six hundred million dollars is not a rounding error in anyone’s budget, and it is certainly not the kind of sum a federal agency disburses to an operation it regards as arm’s length. Obligating funds requires someone inside DHS to review a cost estimate, judge it reasonable, and sign off on the disbursement schedule. Every one of those steps is an act of active federal involvement in how the facility ran, not merely in whether it existed. A landlord who reviews and approves the tenant’s monthly expenses is not a bystander to what happens on the property, whatever the lease says about who holds the keys.

    Jurisdiction as a Liability Shield

    None of this is unique to Florida or to immigration detention specifically. It is a structure familiar to anyone who has watched a federal agency route politically inconvenient work through a state partner, a contractor, or a hybrid arrangement that keeps the agency’s name off the most visible parts of the operation while keeping its funding, personnel, and branding embedded throughout it. The 287(g) program exists for legitimate reasons, and states genuinely do run day to day operations at facilities like this one. But “genuinely involved” and “solely responsible” are different claims, and DHS’s response conflates them in exactly the direction that reduces its own exposure.

    The report itself does not resolve the dispute so much as document both sides of it and let the funding figures speak. OIG did not accuse DHS of bad faith. It did something more useful: it built a record. Personnel on site, signage throughout, participation in arranging its own inspection, and $58.3 million in operational disbursements are not accusations. They are facts a future accountability proceeding, a congressional inquiry, or simply a more careful piece of journalism can build on without having to reconstruct any of it from scratch. The State of Florida, notably, offered no response of its own in the report at all, which leaves DHS’s framing standing unopposed on one side and directly undercut by its own funding trail on the other.

    That is the real finding here, more durable than any single square footage measurement or enclosure log. When something goes wrong at a facility built from a patchwork of state authority, federal money, and shared personnel, the patchwork itself becomes the first line of defense. Responsibility gets diffused across every seam in the arrangement, and each party can, with a straight face, point to the others. The inspector general’s job in this instance was not to settle who is right. It was to make sure the seams were visible to anyone willing to look, and on that count, ironically, it is the one part of this story that actually worked as intended.


    Source: DHS Office of Inspector General, Unannounced Inspection of ICE’s Florida Soft-Sided Facility (“Alligator Alcatraz”) in Ochopee, Florida, OIG-26-22, September 11, 2026.

    For more on conditions at Alligator Alcatraz and related facilities, see The Calming Area — a close read of the eighteen-square-foot outdoor metal enclosures OIG called unprecedented — and The Third Inspection: Krome Fails the Same Test Again, on how the Krome North detention center has now failed three consecutive OIG inspections with the same findings.

  • Federal Register Watch: September 17, 2026

    EPA moved to unwind its own legal basis for regulating power-plant greenhouse gases, finalizing a repeal of its 2024 carbon standards for electric generating units while, on the same day, proposing to rescind the underlying 2015 findings that justified regulating those emissions at all.

    • EPA proposes rescinding the 2015 findings behind power-plant climate rules. EPA proposed rescinding the 2015 findings that greenhouse gases from fossil-fuel power plants endanger public health, the legal foundation beneath a decade of federal climate regulation for the sector. The agency offers three separate arguments for reversing itself, including that Congress never clearly authorized EPA to regulate power plants over climate change under the “major questions doctrine,” and that eliminating the entire U.S. power sector’s emissions would have only a negligible effect on global temperatures. Because this is a proposed rule rather than a final one, it opens debate instead of closing it: comments are due November 2 and a virtual public hearing is set for October 1, giving utilities, states, and advocacy groups a real chance to contest the reasoning before it can take legal effect. Read the proposal.
    • EPA finalizes repeal of most of the 2024 Carbon Pollution Standards. In a companion action published the same day, EPA finalized the repeal of most of its 2024 Carbon Pollution Standards, including emission guidelines for existing coal- and gas-fired power plants and carbon-capture requirements the agency itself adopted only two years earlier. Unlike the proposal above, this one is already final, meaning it takes legal effect without any further public comment. Pairing a final repeal with a still-pending proposal to erase the legal findings underneath it is an unusual sequence, since it leaves EPA’s authority to write any future power-plant rule resting on a foundation the agency has separately proposed to tear down. Read the final rule.
    • FDIC calls a merger-policy board meeting on unusually short notice. The FDIC gave notice of a board meeting held with less than seven days’ advance warning, short of the one week of public notice its Sunshine Act procedures normally require, to take up two proposed rules on bank merger transactions and “state bank parity” plus a vote to rescind an existing supervisory guidance document. Federal open-meeting law expects an agency to state why a shortened notice period was necessary, and this notice offers no reason, which matters because that explanation is the only real check on how much warning the public and affected banks get before a board acts on merger policy. Read the notice.
    • FDA denies exemption for AI radiology software, despite a title that reads the other way. FDA denied a device maker’s petition to exempt certain AI-based radiology software, including cancer-detection and triage tools, from the premarket notification process that normally requires FDA clearance before a device can be sold. The agency found that relying on the company’s prior clearances and a proposed post-market monitoring plan wasn’t enough to show that skipping that clearance review would leave patients just as safe. It’s worth flagging because the document’s own title, “Exemption From Premarket Notification,” names the type of request under review rather than its outcome; read quickly, it can look like FDA loosened oversight of AI diagnostic tools when the agency in fact declined to. Read the notice.
    • Commerce renews export ban on Aeroflot, citing an active violation. The Commerce Department’s Bureau of Industry and Security renewed its temporary denial of export privileges against Russia’s PJSC Aeroflot, citing evidence the airline kept operating U.S.-regulated aircraft components in violation of the denial order Commerce had renewed just last September. A temporary denial order cuts a company off from anything subject to U.S. export rules, and a finding that Aeroflot defied the prior renewal, rather than the agency simply extending it as a precaution, signals that the restriction isn’t achieving compliance and that Commerce is now treating the airline as an active violator rather than a monitored risk. Read the order.

    This edition draws on the Federal Register’s full docket of 72 documents published on September 17, 2026. Set aside as routine: airworthiness directives, OMB/PRA information-collection notices, Coast Guard drawbridge and safety-zone notices, SEC self-regulatory-organization filings, FERC combined filings and blanket-authorization notices, cultural-property exhibition determinations, Postal Service product notices, and other standard administrative filings that didn’t trip an institutional-significance or anomaly signal.

    Fediverse Reactions
  • The Pentagon Audited Its Clocks. Everything Interesting Is Classified.

    The Pentagon’s inspector general recently released an audit concerning the security of the military’s clocks.

    Then it classified essentially everything interesting about it.

    All 10 recommendations in the September 9 audit are classified. No redacted public version of the report is available. What remains publicly visible is little more than the title, administrative metadata and one particularly intriguing fact…the investigation began because somebody made allegations to the Department of Defense Hotline.

    These, however, are not ordinary clocks.

    The Military Has Some Very Important Clocks

    Defense Regional Clocks are part of the Pentagon’s Critical Time Dissemination program, a geographically distributed precision-timing capability intended to keep mission-critical systems synchronized when normal external timing sources are degraded or unavailable.

    The Defense Department created the Critical Time Dissemination effort after recognizing the vulnerability created by dependence on the Global Positioning System. Modern military operations rely on precise positioning, navigation and timing for far more than telling soldiers what time it is. Communications networks, navigation systems, sensors and other systems can depend on extraordinarily precise synchronization.

    The clocks therefore provide part of the resilience needed when GPS or other timing sources are disrupted, jammed, spoofed or lost.

    That makes an audit of their security controls considerably less whimsical than its title initially suggests.

    A Program Years in the Making

    The Critical Time Dissemination program traces back to a fiscal 2012 Defense Department decision intended to address vulnerabilities associated with reliance on GPS.

    Its rollout was not particularly clocklike.

    Defense Department performance records show Defense Regional Clock installation at 63 percent in 2018 and 85 percent in 2019. The department expected to reach 100 percent installation in fiscal 2021.

    It did not.

    During fiscal 2020, installation remained at 87 percent through all four quarters. Subsequent Defense Department planning documents continued moving the finish line, eventually targeting completion of initial operational capability by the end of fiscal 2024.

    The publicly stated schedule therefore appears to have slipped roughly three years from the earlier fiscal 2021 target.

    GAO Finds an Incomplete Business Case

    The deployment history was not the only warning sign in the public record.

    In 2022, the Government Accountability Office examined several Defense Department programs intended to provide alternatives to GPS-based positioning, navigation and timing. Critical Time Dissemination was among them.

    GAO reported that the Office of the DoD Chief Information Officer planned to transition Critical Time Dissemination into the major capability acquisition pathway. But several pieces of its acquisition business case were still unfinished. Requirements were being drafted, and although a technology-risk assessment had been completed, an acquisition strategy, schedule-risk assessment and independent cost estimate had not.

    GAO’s formal business-case recommendation concerned Navy alternative-PNT programs rather than Critical Time Dissemination specifically. But the review nevertheless documented that, roughly a decade after the program began, CTD still lacked several elements of a complete acquisition business case.

    Then the Modernization Became Classified

    Classification surrounding the clock program did not begin with the inspector general’s latest audit.

    DISA’s fiscal 2023 budget justification included a $10 million increase for “Critical Time Dissemination Defense Regional Clocks Modernization.”

    The public explanation for the increase consisted of one word: “Classified.”

    That does not necessarily indicate anything improper. Military timing infrastructure has obvious national-security implications, and publishing technical vulnerabilities, architecture or precise capabilities could itself create risk.

    But then somebody called the Hotline.

    The Hotline Allegation

    On February 20, 2025, the DoD Office of Inspector General announced an audit of security controls protecting Defense Regional Clocks.

    The project announcement was unusually explicit about why the audit existed: “We are initiating the subject audit in response to allegations to the DoD Hotline.”

    The publicly stated objective was to determine whether security controls protecting the clocks were effective.

    The announcement directed work toward the Office of the DoD Chief Information Officer, the U.S. Naval Observatory, the Defense Information Systems Agency and selected Defense Regional Clock locations. It also instructed participating organizations to identify both a knowledgeable GS-15-equivalent point of contact and a Senior Executive Service or General/Flag Officer familiar with DRC security who could engage with senior OIG leadership if necessary.

    The allegation itself remains out of public view. The available records do not identify who made it, what specific weakness was alleged or when the underlying concern first arose.

    What Happened While OIG Was Looking?

    This is where the public chronology becomes particularly interesting.

    While the OIG audit was underway, Defense Department budget and procurement records began describing substantial additional work involving the timing infrastructure.

    DISA’s fiscal 2027 procurement justification requests more than $20 million for Critical Time Dissemination, including nearly $14 million for a Monitor and Control capability covering 46 Defense Regional Clocks and 30 Timing and Synchronization Support Center suites.

    The budget document contains a revealing description of the existing architecture: “The DRCs and TSSCs are currently independent and there is no existing connective network.”

    The proposed capability would connect the systems for centralized calibration and monitoring.

    Other fiscal 2027 budget material describes funding for a permanent test laboratory supporting system optimization and security compliance, anti-spoofing technology upgrades, GPS-independent time-holding capabilities and additional personnel.

    Those personnel would help inspect, operate and upgrade the globally deployed systems and maintain a watch-floor presence monitoring mission-critical timing assets.

    In June 2026, meanwhile, the Navy sought a firmware upgrade from FEI-Zyfer for 50 Time and Frequency Reference Measurement Systems supporting the Critical Time Dissemination project at the U.S. Naval Observatory. Procurement records describe capabilities involving additional external timing inputs, processing multiple streams, weighting and prioritizing timing sources and seamless failover.

    There is currently no public evidence establishing that these subsequent upgrades resulted from the Hotline allegations or from findings developed during the OIG audit.

    The timing is noteworthy, but chronology is not causation.

    What the documents do provide is a before-and-after silhouette worth examining further.

    Ten Recommendations, Ten Secrets

    On September 9, 2026, the DoD OIG finally released the audit.

    Sort of.

    Oversight.gov lists 10 recommendations associated with the audit. All 10 are classified. All 10 are listed as open. The OIG says the report contains classified information and that no redacted version is available.

    The public can therefore establish that allegations were made, that the inspector general considered them sufficient to initiate an audit of security controls, that the audit ran for roughly 19 months and that it resulted in 10 recommendations requiring corrective action.

    What the public cannot establish is what OIG found.

    The Record That Classification Can’t Erase

    There may be entirely legitimate national-security reasons why the vulnerabilities identified by the inspector general cannot be made public. Publishing locations, architectures or exploitable weaknesses in military timing infrastructure would hardly constitute responsible transparency.

    But classification does not make the surrounding public record disappear.

    That record shows a military timing program created to reduce dependence on GPS; a deployment that missed earlier completion targets; an acquisition effort that GAO found was still missing several business-case elements years after the program began; classified modernization spending; a subsequent Hotline allegation concerning security controls; and, while the resulting audit was underway, plans for centralized monitoring, security-compliance testing, anti-spoofing improvements, additional personnel and firmware upgrades.

    None of that tells us what the Hotline complainant alleged.

    It tells us why the question is worth asking.

    Someone saw enough of a problem with the Defense Regional Clock program to contact the Defense Department Hotline. The inspector general considered the allegations sufficient to launch an audit. That audit ultimately produced 10 recommendations.

    The public is permitted to know that much.

    What happened in between remains classified.

    Bureaucracy.news is continuing to examine the contracting, deployment and security history of the Defense Regional Clock program and the circumstances surrounding the Hotline allegations that prompted the audit.

  • The Inspectors General Say They Returned $17 for Every $1 Spent. We Went Looking for the $17.

    CIGIE says the federal Inspector General community generated about $65.6 billion in potential savings in fiscal 2025 against roughly $3.9 billion in OIG budgets. The arithmetic works. What the arithmetic means is considerably less simple.

    The federal government’s inspectors general had a very good year. At least according to the accounting used by the organization that represents them.

    In its fiscal 2025 annual report, the Council of the Inspectors General on Integrity and Efficiency, or CIGIE, reported approximately $65.6 billion in “potential savings” produced by the federal Inspector General community. Against approximately $3.9 billion in total OIG budgets, CIGIE said that represented roughly $17 in return for every $1 invested.

    Seventeen dollars back for every dollar spent would be an extraordinary investment.

    So Bureaucracy.news went looking for the seventeen dollars.

    The $65.6 Billion Is Not One Kind of Money

    CIGIE’s published figures show exactly how the $65.6 billion is assembled. The largest component is $22,880,509,833 in recommendations that funds be put to better use. Another $22,120,759,545 consists of questioned costs. The remaining $20,583,815,010 is classified as investigative receivables and recoveries.

    Add them together and the result is approximately $65.6 billion. Divide that by approximately $3.9 billion and the advertised ratio is roughly correct.

    The problem is not the division. It is what is being divided.

    Those three categories describe fundamentally different things. They should not be read as $65.6 billion in cash recovered and deposited back into the Treasury.

    A Recommendation Is Not a Recovery

    The first $22.9 billion represents recommendations that funds be put to better use. In federal audit terminology, that generally means an inspector general has concluded that money could be used more efficiently if agency management takes and completes a recommended action.

    The operative word is “could.”

    A recommendation can be accepted, rejected, modified, left open or eventually implemented. Even an accepted recommendation does not automatically mean the estimated monetary effect materialized dollar for dollar.

    That makes the category valuable as an oversight measure. It does not make it equivalent to money already saved.

    A Questioned Dollar Is Not Necessarily a Misspent Dollar

    The next $22.1 billion consists of questioned costs.

    Questioned costs can include expenditures auditors believe violated a law, regulation, contract, grant or other governing requirement. They can also include costs lacking adequate supporting documentation or expenditures auditors consider unnecessary or unreasonable.

    That is an important audit finding. But “questioned” is not synonymous with “recovered,” “disallowed,” “fraudulent” or even ultimately “improper.” Agency management still has to resolve the finding.

    This distinction is hardly new. The Government Accountability Office warned decades ago about the disparity between costs auditors question and amounts agencies ultimately disallow and recover. GAO noted that only a fraction of questioned costs may ultimately be disallowed and that even disallowed costs do not necessarily result in money being returned to the government.

    Yet in CIGIE’s headline calculation, the full $22.1 billion enters the potential-savings side of the ledger.

    Even “Receivables and Recoveries” Requires an Asterisk

    The remaining $20.6 billion initially looks more straightforward. CIGIE labels it “investigative receivables and recoveries.”

    But that category, too, can encompass different stages of the financial process. Federal OIG reporting has historically included judicial recoveries, fines, court-ordered restitution, settlements, forfeitures and other monetary outcomes. An amount ordered to be repaid is not necessarily an amount collected.

    Restitution provides the obvious example. A court can order a defendant to repay millions of dollars. The government may then spend years attempting to collect it, and defendants may never possess sufficient assets to satisfy the judgment.

    Until the underlying FY2025 data are reconciled, the $20.6 billion cannot safely be described as $20.6 billion that taxpayers actually received back.

    Then There Is the Double-Counting Question

    CIGIE’s annual report contains another qualification that deserves attention.

    Defense Contract Audit Agency work can be incorporated into Inspector General reporting, and CIGIE acknowledges circumstances in which DCAA audit results may be reported by more than one OIG because of the reporting process.

    That does not establish that the FY2025 $65.6 billion contains material double counting. Bureaucracy.news has not found evidence sufficient to make that claim.

    It does, however, create a straightforward accounting question: when CIGIE aggregates monetary results from across the Inspector General community into a government-wide total, how are overlapping DCAA results identified and removed, if they are removed at all?

    The distinction is especially notable because CIGIE says its methodology for investigative statistics attempts to eliminate duplicate reporting when multiple OIGs participate in the same investigation.

    Whether comparable controls are applied to the audit dollars contributing to the $17 calculation is something we intend to find out.

    The Auditors Have Been Working on Their Accounting

    There is another reason to examine the figures carefully, and that is that CIGIE itself has worked in recent years to improve consistency in the way inspectors general identify and report monetary impact.

    Its Audit and Inspection and Evaluation committees established a Monetary Impact Working Group, and in June 2024 CIGIE issued a Toolkit for Identifying and Reporting Monetary Impact. The effort was designed to improve consistency, quantification and transparency in reporting categories including questioned costs and recommendations that funds be put to better use.

    That is not evidence that earlier figures were wrong. Standardizing definitions across a sprawling federal oversight community is a legitimate undertaking.

    But it raises an obvious historical question: how comparable are CIGIE’s annual monetary-impact figures across years if the organization concluded that additional guidance was necessary to promote consistency in the first place?

    The language has also evolved. CIGIE’s FY2024 report described its aggregate figures as “monetary accomplishments.” The FY2025 report uses the more cautious phrase “potential savings.”

    That may be nothing more than improved terminology. It may also be an acknowledgement that an audit recommendation and a dollar recovered are not the same thing.

    Another Federal Watchdog Draws a Sharper Line

    GAO provides a useful comparison — and also a warning against oversimplifying this issue.

    GAO itself routinely advertises a return on investment based on financial benefits attributed to its work. But GAO distinguishes benefits it records after congressional or agency action from the potential future benefits associated with recommendations that remain open.

    In a 2023 analysis, for example, GAO separately estimated that implementing thousands of still-open recommendations could produce another $92 billion to $182 billion in future financial benefits. It did not treat those prospective benefits as though they had already occurred.

    DCAA provides another instructive comparison. GAO reported in 2025 that DCAA calculates return on investment for incurred-cost audits using “questioned costs sustained” — excess costs agreed upon by the government and contractor after completion of the audit — rather than simply the original amount auditors questioned.

    There are legitimate differences among these organizations and their statutory reporting requirements. The comparisons do not prove CIGIE’s calculation is improper.

    They do demonstrate that federal watchdogs have more than one way to decide when a potential dollar becomes a financial benefit.

    We Are Asking CIGIE for the Receipt

    None of this diminishes the importance of inspectors general. Their work uncovers fraud, identifies waste, exposes broken controls, produces criminal cases and regularly forces federal agencies to correct practices that should have been corrected long before an auditor arrived.

    Nor does the evidence currently establish that CIGIE’s $17 figure is false.

    What it establishes is that the phrase “$17 return on every dollar invested” sounds considerably simpler than the accounting beneath it.

    Bureaucracy.news is asking CIGIE to provide the methodology and underlying accounting behind the FY2025 calculation. Among other things, we are seeking clarification of how the approximately $65.6 billion numerator was constructed; how much represents amounts actually recovered, collected or demonstrably saved; how investigative receivables are distinguished from recoveries; how overlapping DCAA audit results are handled; and exactly what expenditures comprise the approximately $3.9 billion OIG-budget denominator.

    We also intend to seek the underlying records through the Freedom of Information Act.

    CIGIE may have perfectly reasonable answers. If its accounting substantiates the characterization, we will report that. If the underlying records materially change the picture, we will report that too.

    For now, what we know is considerably narrower.

    The federal Inspector General community reported $65.6 billion in potential monetary impact against roughly $3.9 billion in OIG budgets. But potential savings, questioned expenditures, money ordered to be repaid and money actually recovered are not interchangeable.

    Seventeen dollars is an extraordinarily good return on a one-dollar investment.

    We would simply like to see the receipt.

    For related coverage on what federal oversight actually produces in practice, see Five Billion Dollars for the Bureau of Prisons, and a Watchdog on a Diet — on Congress giving BOP $5 billion to oversee while giving the watchdog the same budget as last year — and Forty Reports, Zero Referrals, on a six-month OIG period that produced 40 investigative reports on theft and fraud and zero criminal referrals.

    Fediverse Reactions
  • Eleven Safeguards, One Wrong Valve, and a $95 Million Explosion at Shell

    A worker clicked the wrong valve.

    Six minutes later, a furnace exploded.

    That is the shortest possible version of what happened at Shell Polymers Monaca in Pennsylvania on June 4, 2025. But a newly released investigation by the U.S. Chemical Safety and Hazard Investigation Board makes clear that reducing the accident to human error would miss almost everything important about it.

    The CSB found that Shell had identified the possibility of a potentially fatal explosion, had 11 administrative controls that it believed would prevent such an event, and had access to engineered protections that could have made the mistake substantially harder to commit.

    The 11 controls failed. Furnace 5 exploded. Shell estimated the property damage at $95 million.

    Remarkably, nobody was injured.

    The Setup: A First-Time Task, a Confusing Screen

    The Monaca complex, which began operating in 2022, converts ethane into ethylene for plastics production. Its ethane cracking unit contains seven furnaces.

    Furnace 5 had been taken offline so workers could clean its coke trap. None of the facility’s seven coke traps had previously been cleaned since operations began. When the work was finished, Shell began returning Furnace 5 to operation.

    That required reopening large motor-operated valves separating the furnace from the downstream process.

    The engineer assigned to open one of those valves had never performed the task before.

    The computer interface did not make matters easier.

    Three valves appeared on the same safety-system logic screen. Their identifiers differed only by their final digit: 511, 512 and 513. The furnace-side valve was displayed near the top of the screen; the tower-side valve the engineer intended to open was near the bottom.

    After the engineer entered the system’s debug mode, the screen refreshed and returned to the top.

    The engineer inadvertently commanded the wrong valve open.

    The Alarm That Told Nobody Anything

    Even then, the system had another opportunity to reveal the mistake. An alarm activated when the unexpected valve began moving. But its description was essentially identical to that of the expected valve, again differing principally by the last digit. Because operators knew a valve was supposed to be opening, the alarm was acknowledged without corrective action.

    Eventually the intended valve was opened as well.

    That created a path allowing flammable cracked gas to flow backward into Furnace 5, where the pilots were still burning.

    At 2:21 p.m., the gas ignited.

    The explosion severely damaged the furnace and released an estimated 5,100 pounds of ethylene and combustion products. Fifteen employees were evacuated. A contractor became trapped in an elevator beside Furnace 5 and had to be rescued. Other workers were also in the vicinity.

    There was no exclusion zone around the furnace because Shell did not consider the operation a startup activity or abnormal situation.

    They Knew. They Chose Paperwork Anyway.

    The more consequential finding, however, concerns what Shell knew before the explosion.

    According to the CSB, Shell’s process hazard analysis had already identified cracked-gas backflow as a potentially fatal explosion scenario.

    Shell nevertheless relied on 11 administrative controls — things dependent upon policies, procedures, alarms, training and workers correctly carrying them out — rather than an engineered control capable of physically or automatically preventing the dangerous valve configuration.

    The report becomes particularly uncomfortable when it examines Shell’s earlier risk analysis.

    Shell had identified two administrative safeguards against an explosion: operator response to a high-methane alarm and a startup procedure.

    Neither was functioning as assumed on the day of the accident.

    The alarm was suppressed, and the startup procedure considered during the hazard analysis wasn’t being used.

    The Protections Were Right There

    Shell’s hazard-analysis team had previously concluded that adding engineering controls would be “grossly disproportional to the risk reduction” they would provide. CSB reached a rather different conclusion, finding that Shell had actively chosen to rely solely upon administrative controls to prevent a potentially fatal explosion.

    Perhaps most strikingly, engineered protections were not some technology waiting to be invented.

    Shell licensed the furnace technology from Linde, whose original design incorporated engineered safeguards. One involved a sequenced-key interlock intended to prevent an incorrect valve opening. Another was designed to automatically close the furnace-side valve when conditions associated with backflow were detected.

    Those protections were not implemented for the double-isolated configuration involved in the accident.

    Nineteen Times It Worked. Once It Didn’t.

    Meanwhile, Shell had successfully performed essentially the same isolation-and-return operation 19 times before the explosion.

    Nineteen successes apparently demonstrated that the procedure could work.

    The twentieth demonstrated what happened when it didn’t.

    $26,480 in Fines. $95 Million in Damage.

    Afterward, Shell changed the system. Operations personnel can now manipulate the valves from a local control panel rather than requiring a process-control engineer to override the safety system. New logic prevents the tower-side valve from opening if the furnace-side valve has mistakenly been opened, and Shell developed a new step-by-step operating procedure.

    OSHA also issued three citations stemming from the accident. They addressed shortcomings in the process hazard analysis, inadequate consideration of human factors and the absence of clear operating procedures for returning the valves to normal operation.

    The proposed penalty was $26,480.

    The estimated property damage was $95 million.

    The CSB’s report therefore provides a useful distinction between the person who made the final mistake and the system that determined what would happen when someone inevitably made one.

    A worker selected the wrong valve.

    But before that click ever occurred, the explosion hazard had been identified, administrative safeguards had been chosen, engineered protections had gone unused in this configuration, alarms could be suppressed, an inexperienced engineer could manipulate nearly identical controls, and the interface provided precious little assistance in distinguishing one valve from another.

    Human error explains the click.

    It does not explain the system that allowed one wrong click to become a $95 million explosion.