0:00
/
Generate transcript
A transcript unlocks clips, previews, and editing.

Two U.S. Troops Were Killed in Jordan. Who Authorized This War?

Iran fired the missiles, but Washington owns the mission that placed more than 50,000 Americans inside an expanding regional battlefield without a publicly coherent objective or exit condition.

Thank you Jo Kooser, Karin Chrostowski, Marti Williams, JMull, Susan Ferry, and many others for tuning into my live video! Join me for my next live video in the app.


Opening Note to Readers

This is the Reader’s Cut of my July 18 breaking report, reorganized from the livestream transcript into a complete written record. I have removed the sound check, production talk, repetition, viewer roll call and closing music while preserving the evidence and the argument. I have also added documentation and late-breaking updates so that no reader has to press play to understand what happened, what remains unknown and what Washington still owes the country.

I served in the U. S. Army and later spent 20 years working county patrol as a police officer. I know what it means for people in uniform to carry out a mission designed by people far from the danger. Respect for service begins with demanding that civilian leaders define the mission, establish lawful authority, protect the force and name the way home.

Two U.S. service members are dead. A third remains missing in action. Four more had to be medically evacuated. The first obligation is to the families, but honoring those families requires more than solemn language from officials. It requires an accounting of the decisions that placed their loved ones inside this war.

TLDR

  • Two were killed and one remains missing. CENTCOM says two U.S. service members were killed in action in Jordan on July 17 while American and partner forces defended against Iranian ballistic-missile and drone attacks. One service member remains missing in action.[1]

  • The public record is still incomplete. Four Americans were medically evacuated and later discharged, while others with minor injuries returned to duty. CENTCOM withheld the identities of the fallen pending next-of-kin notification.[1]

  • This war has already produced a much larger toll. Sixteen U.S. service members have died during the conflict, including deaths not classified as hostile-action fatalities, and the latest Associated Press count places the wounded above 430.[2]

  • More than 50,000 Americans are already exposed. CENTCOM says that force is operating across the Middle East as the United States completed a seventh consecutive night of strikes and enforced a naval blockade against Iranian ports.[3]

  • Congress voted to direct withdrawal. The House passed H. Con. Res. 86 by 215 to 208, and the Senate agreed to the same measure by 50 to 48, but the concurrent resolution did not itself become binding law.[4][5][6]

  • The central questions remain unanswered. Iran bears responsibility for the missiles, while Washington bears responsibility for the mission, its legal basis, its force-protection plan and the condition that will bring American forces home.

Restack or share this report, and send it to one person who needs the full record before another casualty announcement is reduced to a ritual of grief and resolve. The machinery of an expanding war benefits when each death arrives as an isolated bulletin, disconnected from the mission, the legal authority and the decisions that placed more than 50,000 Americans across this regional battlefield. Circulation keeps those facts joined together.

Paid subscriptions are the dependable base that allows XVOA to verify official statements, follow Congress’s actions and keep this reporting public.

Keep This Work Keepin On

If another recurring subscription is not possible, or simply not how you want to help, Buy Me a Coffee is the flexible direct-support lane.

Buy Me A Coffee

It works for a few dollars, a substantial one-time contribution or additional support from readers who already pay. Thank you to everyone whose support keeps this desk working.

Video Chapters

0:00 🚨 BREAKING NEWS: 2 U.S. Troops Killed in Jordan
1:06 🎖️
ARMY VETERAN ANALYSIS: Why This Matters
1:48 🎯
TONIGHT’S FOCUS: Mission, Authority and Escalation
2:34 ▶️
ABC NEWS REPORT: Iran Attack on U.S. Troops
6:13 📋
CENTCOM UPDATE: 2 Killed, 1 Missing
10:43 ⚠️
TROOPS AT RISK: 50,000 Across the Middle East
12:28 🏛️
WAR POWERS: Congress Votes to End Trump’s Iran War
13:19 🌍
WAR EXPANDS: Jordan, Kuwait and Bahrain
14:41 🗣️
HEGSETH RESPONDS: “Stiffen Our Resolve”
15:35 ❓
FOUR QUESTIONS: Who Authorized This War?
16:13 🕯️
HONOR THE FALLEN: Demand Accountability
17:29 💬
VIEWER Q&A: The Mission, Authority and Exit Plan


The First Duty Is to the Families

CENTCOM’s public statement is brief and careful. It says the service members were killed in Jordan on July 17 while U.S. and partner forces defended against Iranian ballistic missiles and drones. One additional service member was listed as missing in action, four were evacuated to Jordanian hospitals and later discharged, and other personnel treated for minor injuries returned to duty.[1] At publication time, the military had not publicly released the identities, branches, ranks or units of the dead and missing.

“Missing in action” is a formal status, not an invitation to fill the silence with rumors. Nothing in CENTCOM’s statement establishes that the missing service member was captured or killed. Until the military or the family provides more information, responsible reporting must preserve that uncertainty rather than turn a family’s worst hours into speculation.

After the livestream ended, CBS News reported that a U.S. official identified the location as Muwaffaq Salti Air Base in Jordan.[7] CENTCOM’s own statement still did not name the installation, explain the sequence of the attack, disclose how many weapons reached the base or describe what happened to the missing service member. The ABC report used in the broadcast opened with contextual nighttime missile imagery, not verified footage of the fatal attack, and it did not supply those missing operational details.

The War Was Already Larger Than This Headline

The two deaths in Jordan were the 15th and 16th American military deaths of the Iran war. That total must be described precisely because it includes service members who died in aircraft accidents as well as those killed by hostile fire. The Associated Press reports that more than 430 U.S. service members have been wounded since the conflict began.[2] This is not a new danger that suddenly appeared in a single breaking-news alert.

CENTCOM disclosed that more than 50,000 American service members are operating across the Middle East. In the same July 17 statement, the command announced the end of a seventh consecutive night of strikes against Iran, naming surveillance sites, military-logistics infrastructure, underground weapons storage and maritime capabilities among the targets. It also said U.S. forces were fully enforcing a naval blockade against Iranian ports at the president’s direction.[3]

A military can execute an order with extraordinary competence. Competence does not create a coherent political objective. Service members accept risk, but civilian leaders owe them a mission worthy of that risk, with operational limits, lawful authority, force protection and an exit condition that the public can understand.

Iran Fired the Missiles. Washington Chose the Mission.

There is no contradiction in holding two governments responsible for different parts of the same disaster. Iran bears responsibility for launching ballistic missiles and drones toward U.S. and partner forces. Washington bears responsibility for assigning the mission, positioning American forces across the region, defining the objective and deciding how long those forces will remain exposed.

The ABC segment included an analyst’s prediction that the United States might not increase troop numbers substantially. That was an assessment, not a Pentagon announcement. The operative fact is more consequential: more than 50,000 American service members are already inside the regional battlespace.[3] Washington needs no dramatic deployment announcement for the war to widen because those forces and the allied countries hosting them are already within range.

The immediate accountability question is therefore larger than how many more troops might go. The country deserves to know why the forces already there remain exposed, what achievable outcome justifies that exposure and what condition brings them home. Asking those questions is not an attack on the military. It is part of the civilian responsibility owed to every person ordered into danger.

Congress Voted for Withdrawal. The Administration Kept Fighting.

Congress has not declared war on Iran or enacted a specific authorization for this campaign. Instead, the House approved H. Con. Res. 86 on June 3 by a vote of 215 to 208, and the Senate agreed to the same measure on June 23 by 50 to 48.[4][5][6] The resolution directed the president to remove U.S. forces from hostilities against Iran, except forces necessary to defend the United States, an ally or a partner from imminent attack.

That vote carried political weight but not the uncomplicated force of a statute. Congress used a concurrent resolution, which is not presented to the president and does not become law. The administration argued that the mechanism was an unconstitutional legislative veto and lacked the force of law. It also said the hostilities that began February 28 had ended with an April ceasefire.[8] The honest formulation is that majorities in both chambers voted to direct withdrawal, while the legal enforceability of the vehicle they used remained disputed.

The diplomatic pause did not hold. The United States and Iran signed a memorandum of understanding on June 17, but Trump declared the ceasefire over on July 8. His July 10 notice to Congress described renewed U.S. strikes beginning July 7, and the administration treated that notice as the beginning of a new 60-day War Powers period.[9] Lawmakers have disputed that interpretation, arguing that the original clock never stopped, and the War Powers deadline is not itself an affirmative authorization to wage war.

The machinery matters because it turns a constitutional dispute into a battlefield fact. Congress has neither declared this war nor passed an Iran-specific authorization, yet more than 50,000 service members remain inside the region while strikes, counterstrikes and a naval blockade continue. Iran is responsible for the attack, but that responsibility cannot erase Washington’s obligation to explain the authority and purpose of the mission.

A Regional War Reaches the Water Tap

The danger has spread beyond one installation in Jordan. Reuters reported Iranian attacks and warnings involving Jordan, Kuwait and Bahrain, along with more cautiously sourced missile activity toward Saudi Arabia.[10] The strongest documented civilian-infrastructure evidence came from Kuwait, where authorities reported strikes affecting a desalination plant, power generation and an oil facility. CBS reported that Kuwait relies on desalination for about 90 percent of its drinking water.[7]

When warring states attack systems that keep civilians alive, escalation moves from military installations into daily survival. Drinking water becomes leverage, energy becomes leverage, and people living near American bases or strategic infrastructure are drafted into the consequences without their consent. Every allied government hosting U.S. forces must then calculate the risk that its territory, economy and civilian population will become part of the target set.

That is what a regional war means in practice. It is not simply a larger map in a briefing room. It is families waking under missile warnings, workers confronting fires at oil facilities, and entire cities depending on water and power systems that have become instruments of pressure while political leaders continue to describe escalation as resolve.

When Sacrifice Becomes Permission for More War

Defense Secretary Pete Hegseth responded to the deaths by writing, “Godspeed, heroes. Their sacrifice only stiffens our resolve.”[7] The first sentence mourns. The second performs a political function by converting the deaths into evidence that the existing policy must continue.

That is the psychological mechanism worth examining. Grief becomes fuel, and death becomes proof of commitment. As the sacrifice grows, leaders insist that changing course would dishonor those already lost, creating an emotional prison in which every new casualty becomes an argument for the next operation.

I served in the Army, and I reject the idea that honoring service requires suspending judgment about the mission. Honor demands a mission worthy of the people ordered to carry it. Resolve is a feeling; strategy names an objective, a cost, a legal authority and a way home. A vow of resolve without those elements is an IOU written against another military family.

Four Answers Washington Still Owes

The public does not need another slogan. It needs four answers, stated plainly enough that military families and the country paying for this conflict can judge whether the mission is coherent.

  1. What is the achievable military objective? Preventing a nuclear weapon, protecting shipping, punishing attacks, forcing negotiations and changing a government are not interchangeable missions. Leaders must identify the objective they are actually pursuing and explain how military action can achieve it.

  2. What legal authority permits this campaign? The administration must explain how its position accounts for the absence of a declaration of war or specific authorization, the War Powers timeline and the bicameral vote directing withdrawal.

  3. How are more than 50,000 service members being protected? The answer must address missile and drone defense, dispersed bases, civilian infrastructure, allied-country exposure and the lessons of the fatal Jordan attack without disclosing information that would endanger operations.

  4. What exact condition ends U.S. operations and brings them home? A strategy without an exit condition allows every setback to become a reason for expansion and every casualty to become a reason to stay.

These are not questions asked after the military has failed. They are the questions civilian leaders should answer before ordering the military to bear more risk. Until those answers exist, declarations of resolve cannot substitute for accountability.

What Remains Unresolved

One viewer asked during the livestream whether there was anything people could do to stop Trump. The written answer is less comforting than a football analogy and more concrete than despair. Congress controls authorization, appropriations, oversight, hearings and the public record, while voters control whether members who surrender those powers remain in office.

Senator Adam Schiff filed another War Powers resolution after the ceasefire collapsed, explicitly challenging the administration’s claim that a new 60-day clock had begun.[11] A resolution alone cannot locate the missing service member or reverse the deaths already suffered, but sustained congressional action can force votes, expose the mission’s assumptions, restrict funding and make evasion politically costly. The public’s role is to insist that the record remain visible after the breaking-news banner disappears.

Closing Argument

The established facts are grave enough without embellishment. Two U.S. service members were killed in Jordan, one remains missing in action, four were evacuated and discharged, and more than 50,000 Americans are operating across a region in which missile attacks and strikes on vital infrastructure are widening the danger. Congress voted to direct withdrawal, but it used a legally contested concurrent resolution, and the administration continued the campaign under its own disputed reading of the War Powers clock.

The evidence strongly suggests that the conflict’s geographic and human exposure is growing faster than Washington’s public explanation of its purpose. What remains unknown includes the full sequence of the Jordan attack, the circumstances of the missing service member, the defensive sequence that allowed the attack to reach U.S. personnel, and the exact condition the administration believes would end the war. Those unknowns must not be filled with rumor, but neither should they be buried beneath ritual language.

Honor the dead, find the missing and care for the wounded. Then require the political leaders who chose and continued this mission to answer for every life they keep inside it. Iran fired the missiles, but Washington still owes the country the mission, the authority, the protection plan and the way home.

Support XVOA

Washington’s promises of resolve travel quickly. Checking the mission underneath them takes time. This Reader’s Cut required reviewing CENTCOM’s statements, separating 16 total wartime deaths from hostile-action fatalities, confirming the presence of more than 50,000 service members, tracing Congress’s resolution through both chambers and distinguishing what the public record proves from what military families still have not been told. Paid subscriptions give XVOA the dependable foundation to keep doing that work instead of allowing official ritual to close the story.

Give XVOA The Foundation

Current paid subscribers helped make this public report possible, and I thank you. Buy Me a Coffee remains available for readers who cannot or do not want another recurring subscription, current paid supporters who want to contribute again, and anyone choosing anything from a few dollars to a substantial one-time contribution.

Buy Me A Coffee

Like, comment, share and Restack this report so the documented record travels farther than the slogans surrounding the war.


Sources

  1. CENTCOM statement on fallen and missing U.S. service members⁠. Supports the July 17 casualty facts, medical evacuations, missing-in-action status and next-of-kin withholding policy.

  2. Associated Press overview of U.S. military deaths in the Iran war⁠. Supports the total of 16 U.S. military deaths, the distinction among causes and the current wounded count.

  3. CENTCOM statement on the seventh consecutive night of strikes⁠. Supports the strike targets, blockade enforcement and presence of more than 50,000 U.S. service members across the Middle East.

  4. Enrolled text of H. Con. Res. 86⁠. Supports the resolution’s directive and imminent-attack exception.

  5. U.S. House roll call 199⁠. Supports the June 3 House vote of 215 to 208.

  6. U.S. Senate roll call 184⁠. Supports the June 23 Senate vote of 50 to 48.

  7. CBS News live updates on the Iran war⁠. Supports the attributed late identification of Muwaffaq Salti Air Base, Hegseth’s statement and details about attacks on Kuwaiti infrastructure.

  8. White House statement of administration policy on H. Con. Res. 86⁠. Supports the administration’s argument that the concurrent resolution lacked force of law and its account of the April ceasefire and June 17 memorandum.

  9. Reuters report on Trump’s notice that the Iran conflict had resumed⁠. Supports the July 7 resumption date, July 10 notice, blockade order and administration’s disputed new 60-day War Powers position.

  10. Reuters report on the July 18 regional escalation⁠. Supports the qualified account of danger across Jordan, Kuwait, Bahrain and possible missile activity toward Saudi Arabia.

  11. Senator Adam Schiff’s announcement of a new War Powers resolution⁠. Supports the renewed congressional challenge to the administration’s 60-day-clock interpretation.

Get more from Xplisset in the Substack app
Available for iOS and Android

Discussion about this video

User's avatar

Ready for more?