31JUL

Four dead Americans put back on the list

2 min read

09:33UTC

The Department of War restored its Iran war death toll to 18 on 26 July, four days after cutting it to 14, and moved the wounded count from 420 back to 624.

← Back to Insurers shut Bab el-Mandeb to Saudi hulls Jump to analysis ↓

EconomicDeveloping

Key takeaway

The Pentagon restored 18 dead and 624 wounded on 26 July, citing unspecified site anomalies.

The Department of War put the US death toll for the Iran war back at 18 on Sunday 26 July, reversing the cut to 14 it had made two days earlier ¹. The wounded figure moved the same way: 624 since the fighting began in February, against the 420 the same system published on 24 July ². Of that Total, 207 were hurt since 7 July. No cutoff rule accompanied either revision.

The figures live in the Defense Casualty Analysis System, the Pentagon's public database of US military dead and wounded, which is where reporters, veterans' organisations and congressional staff go for a number nobody has to be briefed on. Acting press secretary Joel Valdez offered one sentence about how it had moved: "site anomalies are currently being resolved in coordination with the military services"³.

The four names taken off last week belonged to service members the Pentagon had itself named and honoured, killed at Muwaffaq Salti Air Base in Jordan on 17 July. A database that removes a dead airman and then returns him has told two contradictory things to the same family in the space of four days, and neither statement came with a signature.

Restoring the count also restores the arithmetic Congress works from. Every casualty-linked entitlement, from hostile-fire pay to Department of Veterans Affairs casework, keys off a published figure attached to a named operation, so a number that oscillates is not merely embarrassing bookkeeping. It leaves the claimant carrying the burden of proving which version applied on the day.

Deep Analysis

In plain English

The Department of War, the Pentagon's own name for the US defence department, keeps a running count of American troops killed and wounded in the Iran war. On 24 July it quietly lowered that count. Two days later it put the number back up, plus 624 wounded, higher than before the cut. Nobody has explained the four dead by name or said what happened to them. For a war Congress never formally declared, this running number is one of the few concrete measures the public has of how costly it has become, so seeing it move up and down without explanation matters.

Deep Analysis

Root Causes

The Defense Casualty Analysis System pulls figures from separate Army, Navy, Air Force and Marine reporting chains, each with its own lag between a death occurring and its classification moving from duty-status-unknown through confirmed killed-in-action.

Sergeant Angel Rampersad's status changed from Duty Status Whereabouts Unknown to believed deceased four days after his 17 July attack, the same kind of reclassification lag that can make a cumulative total jump or drop without any new incident behind it.

The four names cut on 24 July and restored on 26 July died after Trump's late-April ceasefire declaration, according to three military officials cited by the New York Times, meaning their inclusion or exclusion depends on where the Pentagon draws the line between the declared end of major operations and the unofficial fighting reflected in later strikes.

What could happen next?

Meaning
A public casualty count that moves without explanation twice in a week signals the Pentagon's own accounting system, not just the war, is under strain.
Risk
Continued unexplained revisions give critics grounds to challenge the administration's public narrative about the war's cost, regardless of the true cause.

Source Landscape

This story draws on centre-left-leaning sources from United States

United States

Primary parallel: The Pentagon's Vietnam-era body count reporting, where local commanders faced pressure to hit favourable kill ratios and headline figures were repeatedly revised for political effect, shares the same structural flaw as this week's swings: a single institution both fighting the war and certifying its own cost.

Counter-parallel: The 2004 Lancet mortality study of Iraq, which put civilian deaths at roughly 100,000 against far lower official Coalition estimates, shows the opposite failure mode: independent and official tallies diverging so far they were never reconciled at all, unlike this week's single-source correction.

Consensus view: Neta Crawford, co-director of the Costs of War Project at Brown University, says repeated revisions to a headline casualty count without named individuals or incident reports are consistent with reporting lag rather than concealment, but that the Pentagon has not published the methodology fix it promised after the first cut.

Counter-view: Mohammad Marandi, a University of Tehran professor who frequently briefs Western outlets on Iran, argues the swings show Washington manages its own casualty narrative to control domestic tolerance for the war, a practice he says Tehran cannot match because its own losses draw less international scrutiny.

Key tension: Whether the volatility reflects an honest data pipeline problem or a deliberate instrument for shaping how much war the American public will accept.

Sources:ABC News

Mentions:Pentagon →Joel Valdez →Vietnam →Coalition →Tehran →Jordan →Iran →Washington →Iraq →Defense Casualty Analysis System →Azraq airbase →

First Reported In

Update #163 · Pentagon puts four dead back, renames war

ABC News· 28 Jul 2026

Read original →

Causes and effects

Caused by

Pentagon cuts Iran war toll to 14

The 26 July restoration to 18 dead reverses the Pentagon's own cut to 14 on 24 July.

Occurred 24 Jul 2026

Read story →

62 wounded vanish from Pentagon toll

The restored 624 wounded figure reverses the unexplained fall to 420 published on 24 July.

Occurred 24 Jul 2026

Read story →

This Event

Four dead Americans put back on the list

Four families watched a federal database carry their relatives into the war, out of it, and back in again inside a fortnight, with one sentence of explanation.

Different Perspectives

Sanctions compliance officer reviewing a Lukoil International GmbH bid

OFAC's amended FAQ 1224 gives a compliance desk its first published standard: full severance from Lukoil and a US-jurisdiction blocked account for sale proceeds. The conditions name neither ISAB nor Italy, so a Priolo Gargallo-linked bid answers a different question than a Neftochim Burgas or Petrotel Ploiesti one.

Managed-money funds on Brent Last Day

CFTC data for the week to 21 July showed managed money flipping 74,400 contracts to a net long of 15,665 against 1,410 short on the Brent Last Day contract, code 06765T. A fund that held that short through July has now covered it, and the spent short base raises the bar for the next leg higher.

Saudi crude exporters

Saudi-linked tanker transits through Bab el-Mandeb fell to about 7.5 a day after the 24 July underwriting withdrawal, pushing more barrels onto the longer route round the Cape or through the Yanbu terminal. Every diverted barrel ties up a ship for longer, and a fleet that turns slower charges more.

Tanker owners on the Bab el-Mandeb route

Lloyd's-market syndicates withdrew war-risk cover from Saudi-linked hulls on 24 July, leaving owners of that class of vessel to sail Bab el-Mandeb uninsured or not at all. Tanker transits on the route fell to roughly 7.5 a day, and cover, once withdrawn, does not return on a shipowner's timetable.

Eni

Eni's board approved second-quarter results on 29 July, swinging refining EBIT to a EUR0.08bn profit from a year-earlier loss even as group profit doubled, and named Red Sea freight cost as a cap on that improvement. A refiner absorbing higher shipping costs on Saudi-linked crude while its numbers improve treats the freight line as a drag, not a crisis.

Asian buyers (India, Japan, China, South Korea)

Asian refiners are absorbing 62% of Yanbu's 3.75m b/d flow, the bulk of Saudi Arabia's rerouted crude now clearing east rather than into the Atlantic basin. That destination split leaves Asian buyers more exposed to any single Yanbu-specific disruption than under the kingdom's normal multi-terminal export pattern.