Mazie K. Hirono

07/23/2026 | Press release | Distributed by Public on 07/23/2026 19:20

Hirono Leads Colleagues in Pressing Hegseth on Inaccurate Casualty Reporting, Demanding Transparency on Human Cost of War in Iran

WASHINGTON, D.C. - Today, U.S. Senator Mazie K. Hirono (D-HI), a senior member of the Senate Committee on Armed Services (SASC), led all of her Democratic colleagues on SASC in demanding a full and accurate accounting of all service members who were killed, wounded, and injured in support or in connection with Operation Epic Fury. In a letter to U.S. Department of Defense (DOD) Secretary Pete Hegseth; Chairman of the Joint Chiefs of Staff, General Dan Caine; Commander of United States Central Command, Admiral Brad Cooper; and Under Secretary of Defense for Personnel and Readiness, Anthony Tata, the senators raised alarms about multiple inconsistencies between the Pentagon's public casualty number and official statements. The senators pressed DOD to be transparent with the American people, servicemembers, and their families on the human cost of the ongoing war in Iran.

"The American people, Congress, service members, and their families are entitled to a full and accurate accounting of the human costs of war. The information currently available to the public suggests that the Department has not consistently provided timely and comprehensive public casualty reporting throughout the conflict," wrote the Senators.

While DOD has reported that the Pentagon's Defense Casualty Analysis System (DCAS) is accurate and "regularly updated," the Senators raised inconsistencies both in overall casualty and injury reporting since the beginning of the conflict, and during the month of July. For example, on July 20, DOD spokesman Sean Parnell publicly stated: "While nearly 100 service members were deemed to have some degree of injury since July 7, 2026, 96% have returned to duty." These injuries, however, were not included total casualty count and July's monthly casualty report. In the same report, DCAS listed 14 servicemembers killed, despite wide reporting of 18 service members killed as of July 20, 2026. While the number of service members killed has been updated as of July 23, these inconsistencies raise significant concerns about the DOD's overall transparency and timely reporting.

"This lack of transparency undermines confidence that military families and the American people are receiving a complete and accurate accounting of the sacrifices made by those serving in uniform," the Senators continued.

The Senators requested prompt, detailed responses from DOD by Thursday, July 30, 2026, including an exact casualty breakdown, an explanation for the total and month-of-July reporting discrepancies, data on traumatic brain injuries, undisclosed attacks in Jordan, and an assessment of mass casualty response capabilities and overall readiness in the theater. They concluded their letter by emphasizing the importance of transparency to servicemembers, their families, and the American people.

"We appreciate your prompt attention to these questions and expect a timely and complete response. Our service members and their families deserve nothing less than a full and honest accounting of the costs of this war," they concluded.

In addition to Senator Hirono, the letter was signed by Senators Jack Reed (D-RI) SASC Ranking Member, Jeanne Shaheen (D-NH), Kirsten Gillibrand (D-NY), Richard Blumenthal (D-CT), Tim Kaine (D-VA), Elizabeth Warren (D-MA), Gary Peters (D-MI), Tammy Duckworth (D-IL), Jacky Rosen (D-NV), Mark Kelly (D-AZ), and Elissa Slotkin (D-MI).

The full text of letter is available here and below.

Secretary Hegseth:

We write to express our concern regarding the Department of Defense's (DoD or the Department) public reporting of U.S. military casualties associated with Operation Epic Fury and to formally request a comprehensive accounting of the number of service members who have been killed, wounded, or injured in support of the operation.

The American people, Congress, service members, and their families are entitled to a full and accurate accounting of the human costs of war. The information currently available to the public suggests that the Department has not consistently provided timely and comprehensive public casualty reporting throughout the conflict.

The Pentagon's Defense Casualty Analysis System (DCAS), which the Department has described as being "regularly updated," has reported inconsistent casualty figures, raising additional questions about the transparency and reliability of the Department's public reporting and statements.

For example, on July 20, 2026, the DoD's chief spokesman, Sean Parnell, publicly stated: "While nearly 100 service members were deemed to have some degree of injury since July 7, 2026, 96% have returned to duty" (Statement posted to X, @SeanParnellASW, July 20, 2026). However, DCAS listed 14 service members killed (despite wide reporting of 18 service members killed as of July 20, 2026) and 447 injured during Operation Epic Fury as and recorded zero wounded in action for the month of July as of July 21, 2026. Both the total casualties and the monthly July casualty data do not reflect the Department's public acknowledgment on July 20th of nearly 100 additional injuries in July. We are concerned that DCAS is not being maintained at the granular level and calls into serious question the completeness and reliability of the aggregate totals. Stars and Stripes also reported on this data inconsistency. Such discrepancies prevent Congress and the public from determining the true human cost of the ongoing operation.

Congress has a constitutional responsibility to oversee military operations and ensure that casualty reporting is both timely and accurate. From the start of Operation Epic Fury in February 2026, this administration has failed to provide timely updates on the military readiness, personnel, and financial impacts of this war. Delays or inconsistencies in publicly reporting these casualty figures further impede Congress's ability to conduct oversight and limit the public's understanding of the operation's costs. This lack of transparency undermines confidence that military families and the American people are receiving a complete and accurate accounting of the sacrifices made by those serving in uniform.

To better understand the Department's casualty reporting practices during Operation Epic Fury, we request responses to the following questions no later than Thursday, July 30th, 2026:

  1. As of the date of your response, what is the total number of U.S. service members who have been killed, wounded in action (or received care for injuries sustained while supporting Operation Epic Fury, including those who returned to full duty after care?
    1. As reported in DCAS, please provide details on the casualty types (hostile vs. non-hostile), and all DCAS reporting categories (Grade, Age, Sex, Component, Race, Ethnicity) across each Service.
    2. Do these numbers include all battle injury (BI) and disease and non-battle injury (DNBI) reporting provided to the Services by U.S. Central Command?
    3. If not, please provide the corresponding figures from U.S. Central Command.
  2. According to The New York Times, a U.S. military official stated that U.S. Central Command is not required to publicly disclose information about injured service members, particularly when they quickly return to duty. Does the Department still receive this information from CENTCOM, even if it's not posted publicly on DCAS? Please explain the communication and updates OSD receives from CENTCOM, including the frequency and timing.
    1. How does U.S. Central Command determine whether a service member has returned to duty 'quickly enough' to not publicly disclose this injury?
    2. In how many cases has U.S. Central Command determined that a service member has returned to duty 'quickly enough' for it to not disclose those injuries to the public?
  3. Are there service members who were killed or wounded in action while deployed to the region in support of another named operation (e.g., Operation Inherent Resolve) who are not included in the Defense Casualty Analysis Systems' accounting for Operation Epic Fury?
    1. If so, how many by category? Please specify for each DoD casualty reporting category in detail, as of the date of your response.
  4. As referenced earlier in this letter, why does the DCAS "Casualties by Month" report not reflect the July 2026 injuries the Department has publicly acknowledged, as of July 21, 2026?
    1. Has the underlying July casualty data been entered into DCAS? If so, why is it not displaying? If not, when will it be publicly available?
    2. Given that the granular monthly data is incomplete, what specific assurance can the Department provide that the aggregate operation totals are complete and accurate?
    3. What is the Department's standard process and timeline for entering monthly casualty data into DCAS, and who is responsible for ensuring its accuracy?
    4. How frequently is DCAS updated for Operation Epic Fury? What is the average lag between a casualty event and its entry into DCAS, and what accounts for the July wounded-in-action figure still displaying zero (as of July 21, 2026)?
  5. Provide a breakdown of all Operation Epic Fury casualties that separates hostile-fire wounded in action from non-battle injuries. Given the Department's statement that the wounded total includes injuries "entirely unrelated to combat operations," how does the Department define "injury," "wounded in action," and "casualty" for the purpose of Operation Epic Fury reporting?
  6. How many service members have been screened for, and diagnosed with, a concussion or traumatic brain injury (TBI) in connection with Operation Epic Fury? Are those cases counted within the wounded-in-action total, and what is the Department's process for updating casualty counts as delayed TBI diagnoses emerge?
  7. With respect to the three Iranian attacks on U.S. forces in Jordan reported to have occurred in the week before the July attack:
    1. How many service members were injured in each attack?
    2. Are those injuries reflected in DCAS? If not, why not?
    3. Who authorized the decision not to publicly disclose those attacks or the associated injuries, and on what legal or policy basis?
  8. Given the number of casualties sustained to date, what is the Department's and CENTCOM's current assessment of the operation's impact on personnel, unit readiness, and operational capability in the U.S. Central Command area of responsibility? Please include the following in your response or in a classified annex:
    1. The readiness and manning of affected units, including any degradation resulting from casualties;
    2. Availability and sustainability of medical and personnel resources in theater; and
    3. Overall operational capability to sustain current and projected mission requirements.
  9. Given the number of casualties sustained to date, does the Department and U.S. Central Command assess that sufficient medical, evacuation, personnel recovery, and other support resources are in place to respond to a mass casualty scenario in the theater?
    1. If yes, please describe the capabilities, resources, and contingency plans currently in place, including any recent adjustments made based on casualty trends observed during the operation.
    2. If no, what are the capability gaps, resource constraints, or additional requirements needed to ensure an adequate response to a mass casualty event?
  10. Will the Department commit to providing Congress with a comprehensive written casualty accounting on a recurring, weekly basis that draws directly on U.S. Central Command's casualty reporting? If so, which office will be responsible for producing it?

We appreciate your prompt attention to these questions and expect a timely and complete response. Our service members and their families deserve nothing less than a full and honest accounting of the costs of this war.

Sincerely,

###

  • Print
  • Email
  • Share
  • Tweet
Mazie K. Hirono published this content on July 23, 2026, and is solely responsible for the information contained herein. Distributed via Public Technologies (PUBT), unedited and unaltered, on July 24, 2026 at 01:20 UTC. If you believe the information included in the content is inaccurate or outdated and requires editing or removal, please contact us at [email protected]