Three months after the Pentagon declared an end to 'Operation Epic Fury,' military officials quietly instructed personnel to stop using the operation's name — a directive that arrived just as four service members killed in July were being reclassified away from a conflict officially concluded in May. The gap between declared endings and continued fighting raises an older, harder question: when a government controls the language of war, it shapes not only the record of sacrifice but the public's capacity to reckon with it. In Echo Harbor, as in every community that has sent its people abroad, t
Pentagon quietly ends 'Operation Epic Fury' naming, raising questions about casualty counts
Why instruct people to stop using a name three months after the operation ended?
So the Pentagon says the operation ended May 5, but then in August they're telling people to stop calling it by its name. That's a three-month gap. Why would that matter?
Because it suggests the operation didn't actually end in the way we normally understand military operations ending. If it was truly over, there'd be no need for guidance in August. The fact that they had to instruct people to use different language suggests ongoing activities that looked too much like the old operation to keep calling it that.
But we should be careful here. The Pentagon says the guidance was about public messaging, not about what was actually happening operationally. They could argue those are different things—that the operation ended but the conflict continued under a different framework.
That's fair, but then why hide the May 5 date for three months? The military has always published these dates. It's standard practice. The secrecy itself is unusual.
And the casualty numbers changed, right? Four service members were killed in July but initially listed as killed during an operation that ended in May?
Yes, but the Pentagon called that a data error. The question is whether it was actually an error or whether the categorization system itself was confused about what Operation Epic Fury was supposed to include.
The timing is suspicious though. Those four were killed, categorized under Epic Fury, then moved to a generic category within days. And when reporters asked why, Parnell said it was a "temporary data disruption." But if the operation ended in May, why would July deaths ever be in that category to begin with?
So we don't actually know if those four deaths should count toward Operation Epic Fury's total or not?
Correct. And that matters because it affects how we understand the scope and cost of the operation. The Pentagon moved them from 18 total deaths to 14. That's not a small correction.
And as of now, the system still shows casualties listed under Epic Fury even though it supposedly ended. The Pentagon hasn't resolved the contradiction.
Is there any chance this is just bureaucratic confusion rather than intentional?
Possible, but the August guidance was explicit and came from the top—Hegseth's office. That's not confusion. That's a directive. Whether it was meant to obscure something or just to standardize messaging, we can't say for certain from the reporting.
Il Polso
- The Pentagon's own casualty database listed service members killed and wounded months after Operation Epic Fury's declared May 5 end date, exposing a direct contradiction between official statements and the military's own records.
- Four service members — including First Lieutenant Tyler James Feehan, Staff Sergeant Angel Rampersad, and Private First Class Isabella Gonzales — were killed in July, initially categorized under a concluded operation, then quietly reclassified within days.
- When pressed, Pentagon spokesman Sean Parnell dismissed the discrepancies as a 'temporary data disruption,' offering no explanation for why an ended operation was absorbing new casualties in the first place.
- The U.S. and Iran have continued exchanging fire well past May 5, with President Trump formally notifying Congress of restarted military action in July — yet the Pentagon has not briefed the press on the Iran conflict since that original end date.
- The renaming directive, distributed department-wide from Hegseth's public affairs office, effectively reduced the official death toll attributed to Operation Epic Fury from 18 to 14, reshaping the public ledger of the war's human cost.
Three months after the Pentagon declared an end to 'Operation Epic Fury,' military officials quietly instructed personnel to stop using the operation's name — a directive that arrived just as four service members killed in July were being reclassified away from a conflict officially concluded in May. The gap between declared endings and continued fighting raises an older, harder question: when a government controls the language of war, it shapes not only the record of sacrifice but the public's capacity to reckon with it. In Echo Harbor, as in every community that has sent its people abroad, the names given to operations are not merely administrative — they are the architecture of accountability.
Three months after the Trump administration declared an end to military operations against Iran, the Pentagon quietly told its personnel to stop using the operation's name. An Air Force email obtained by CBS News, dated August 7, directed senior leaders to replace 'Operation Epic Fury' with the phrase 'overseas operations in the U.S. Central Command Area of Responsibility.' The directive came from Defense Secretary Pete Hegseth's public affairs office and was distributed across the entire Defense Department.
Operation Epic Fury was officially declared concluded on May 5 — a date the Pentagon resisted disclosing for months, departing from the military's longstanding practice of publishing clear start and end dates for named operations. Secretary of State Marco Rubio confirmed the end date publicly that same day, and President Trump announced a pause in military action to allow for negotiations. But the silence from the Pentagon on the matter persisted long after.
The central tension emerged in July, when four U.S. service members were killed during operations that the Pentagon's own website initially classified under Operation Epic Fury — two months after its supposed conclusion. First Lieutenant Tyler James Feehan, Staff Sergeant Angel Rampersad, and Private First Class Isabella Gonzales died on July 18 at Muwaffaq Salti Air Base in Jordan; a fourth service member was killed the following day in Iraq. Within days, all four were reclassified under the new 'overseas operations' category, quietly reducing the official death toll of Operation Epic Fury from 18 to 14.
When questioned, Pentagon spokesman Sean Parnell attributed the changes to a 'temporary data disruption,' without explaining why casualties from a concluded operation appeared under its name at all. The military's own casualty database continued to list service members killed and wounded after May 5 under Operation Epic Fury, directly contradicting the Pentagon's stated position. No end date for the operation appeared in the system.
Meanwhile, the conflict itself had not ended. The U.S. and Iran continued exchanging fire through the summer, and President Trump formally notified Congress on July 7 that military action against Iran had restarted. The Pentagon has conducted multiple rounds of strikes in recent days, drawing Iranian counterattacks — yet May 5 remains the last date on which the Pentagon briefed the press about the war. The question left hanging is whether the renaming of an operation, months after its declared end, was an act of administrative tidiness or something more deliberate: a quiet rewriting of the record of American involvement in a war that, by any measure, has not stopped.
Three months after the Trump administration declared an end to military operations against Iran, the Pentagon quietly instructed its personnel to stop using the operation's name. An Air Force email dated August 7, obtained by CBS News, directed senior leaders attending a conference in Orlando to refer instead to "overseas operations in the U.S. Central Command Area of Responsibility" when discussing the conflict. The directive came from Defense Secretary Pete Hegseth's public affairs office, led by Pentagon spokesman Sean Parnell, and was distributed across the entire Defense Department, according to military officials who spoke on condition of anonymity.
The operation in question, called "Operation Epic Fury," officially ended on May 5, according to the Pentagon's response to CBS News inquiries. That same day, Secretary of State Marco Rubio told reporters at the White House that the operation was finished, and President Trump announced a temporary pause in military action to allow for negotiations. Yet the Pentagon had resisted disclosing this end date for months, breaking from the military's historical practice of publishing clear start and end dates for named operations—a practice that creates a public record of American military involvement abroad and determines eligibility for service members' awards.
The timing raises a fundamental question: if Operation Epic Fury ended in May, why did the Pentagon need to instruct personnel three months later to stop using its name? The answer may lie in how the military has classified casualties. In July, four U.S. service members were killed in operations that the Pentagon's own website initially categorized as deaths occurring during Operation Epic Fury—two months after the operation had supposedly concluded. First Lieutenant Tyler James Feehan, Staff Sergeant Angel Rampersad, and Private First Class Isabella Gonzales were killed on July 18 at Muwaffaq Salti Air Base in Jordan. Staff Sergeant [name withheld in source] was killed the following day in Iraq during a controlled detonation of an Iranian attack drone. Within days, all four were reclassified into the new "overseas operations" category, a move that technically reduced the number of deaths attributed to Operation Epic Fury from 18 to 14.
When news organizations, including CBS News, questioned these changes, Pentagon spokesman Sean Parnell attributed them to a "temporary data disruption" and "site anomalies." He did not explain why service members killed months after an operation's official end date would have been categorized under that operation in the first place, nor did the Pentagon clarify at that time when Operation Epic Fury had actually ended. The military's historical precedent suggests such clarity should be routine. Operation Enduring Freedom in Afghanistan, for instance, had clearly marked dates—October 7, 2001, to December 31, 2014—before transitioning to Operation Freedom's Sentinel.
The broader context complicates the picture further. The U.S. and Iran have continued exchanging fire since May 5, despite lengthy pauses and an April ceasefire. President Trump formally notified Congress on July 7 that military action against Iran had restarted, and talks between the two nations collapsed around that time. The Pentagon has conducted strikes in multiple rounds this week alone, drawing Iranian counterattacks. Yet the May 5 date remains the last time the Pentagon briefed the press on the war with Iran.
As of the time this story was published, the Pentagon's Defense Casualty Analysis System still listed five service members as wounded in June and one as killed in July under Operation Epic Fury—despite the Pentagon's assertion that the operation ended in May. No end date for the operation appears on the system. A Pentagon official told CBS News that since Operation Epic Fury concluded, the Department classifies casualties as "overseas operations in the CENTCOM area of responsibility," yet the system itself contradicts this statement. The discrepancy raises questions not only about administrative consistency but about the purpose of renaming an operation months after its declared conclusion, and whether the change was designed to reshape the public record of American military involvement in the conflict.
Citazioni salienti
The operation is over. Epic Fury is—the president notified Congress—we're done with that stage of it.— Secretary of State Marco Rubio, May 5, 2026
Pentagon spokesman Sean Parnell attributed casualty reclassifications to a 'temporary data disruption' and 'site anomalies'— Sean Parnell, Pentagon spokesman