Follow us on social

Iraq war Army soldiers Baghdad

The ghosts of the Iraq War still haunt me, and our foreign policy

As a young National Guardsman I reported for duty on March 21, 2003. Why are there still troops there today?

Analysis | Middle East

On St. Patrick’s Day, March 17, 2003, President Bush issued his final ultimatum to Saddam Hussein. Two nights later, my Iraq War started inauspiciously. I was a college student tending bar in New York City. Someone pointed to the television behind me and said: “It’s begun. They’re bombing Baghdad!” In Iraq it was already early morning of March 20.

I arrived home a few hours later to find the half-expected voice message on my answering machine: “You are ordered to report to the armory tomorrow morning no later than 0800, with all your gear.”

At the time, I served in an infantry unit of the New York Army National Guard. By mid-day, our gear loaded, most of my company headed up the Hudson River to New York’s military training site, Camp Smith. The state had activated us for a homeland security mission. As the war began, one of the biggest unknowns was whether Saddam had the resources and connections to conduct terrorist strikes in the U.S. Less than two years after September 11, 2001, many feared New York City could be struck again.

Our unit spent about a week training for various scenarios that could take place on New York City’s transit system. By night we watched news reports and evaluated our military’s progress in Iraq. Before April, we were executing a mission guarding the subways alongside the New York City Police Department. I led a four-man team securing the platform under City Hall.

By the time President Bush staged his “Mission Accomplishment” moment on May 1, I was back in class, studying international relations. I expected to graduate the following January. But the mission wasn’t quite accomplished.

In August, as I prepared to begin my final semester, my unit received a verbal warning order that we would be mobilizing to deploy to Iraq. Graduation was delayed. In October I found myself at Fort Drum, New York, training for Iraq.

It wasn’t until early March that our battalion task force, including my company, was deployed into Iraq itself. On the evening of March 17, 2004, just a few days short of the war’s first anniversary, I came under and returned fire, alongside a few dozen of my battle buddies.

At the end of October, while driving the lead HMMMV of a patrol returning to base, I received a frantic call from our Battalion Commander, advising of enemy contact and calling for reinforcement and casualty evacuation. In the patrol’s lead vehicle, I didn’t wait for orders, I simply turned around and headed toward the fight.

A complex attack by insurgents with small arms and an IED killed Segun Akintade. We got there too late. It was October 28. Segun had immigrated to New York from Nigeria a few years earlier. Nicknamed Obi Wan, he was a giant man with a larger laugh. He worked at Bear Stearns to afford school and, like me, he studied at the City University of New York. He served in my fire team during that mission securing the subway at the beginning of the war.

His death was not the first for our battalion. Officially, it was the last, but tragedy struck again a month later and a few dozen kilometers away. Several soldiers we left behind in 2003 had been reassigned to another New York unit and then mobilized for the next cycle of deployments. In late November, another IED killed two more of my friends, both New York firefighters. Men we had trained with and knew well had their lives taken too soon. Several others suffered devastating wounds but survived.

All of this happened more than two decades ago. In the intervening years, more soldiers from that deployment died in Iraq and Afghanistan. Several took their own lives back at home.

In 2010, President Obama “brought all military combat personnel” home from Iraq. There are multiple problems with that statement, but the most obvious is: The enemy gets a vote as we say. If you come under fire while serving in the military, you’re a combatant (rare exceptions like chaplains prove the rule).

On March 20, 2025, we still have American soldiers in Iraq. There are roughly 2,500 U.S. troops serving overtly in a “train and advise” mission. These American service members, like their current counterparts in Syria and the greater Middle East, are at risk. The attack on Tower 22 in Jordan last year, which killed three young American reservists, demonstrates the vulnerability of thinly stretched U.S. forces, deployed with no clearly elaborated national interest to the United States. This vulnerability will sooner or later be exploited again to the detriment of our troops.

In the 22 years since I received the news that I would be mobilized to support the war in Iraq, over 4,000 American troops have fought and died there. Some of these deaths were deeply personal. The costs to families have been tragic. With the Islamic State’s caliphate long-since defeated, the so-called logic for U.S. forces to be in Iraq is gone.

After 22 years, it’s time to put an end to our “boots on the ground” mission in Iraq, draw down our presence in the Middle East, and only risk the lives of American military men and women when there is an undeniable national interest.


Top photo credit: U.S. Army Soldiers assigned to weapons squad, 1st Platoon, C Company, 1st Battalion, 504th Parachute Infantry Regiment, pose for a photo before patrolling Rusafa, Baghdad, Iraq, Defense Imagery Management Operations Center/Photo by Staff Sgt. Jason Baile
Analysis | Middle East
Here is why US troops may be in Iraq indefinitely
Top photo credit: Iraqi Prime Minister-designate Mohammed Shia al-Sudani, appears during a vote in Sudani's cabinet at the parliament in Baghdad, Iraq, October 27, 2022.

Here is why US troops may be in Iraq indefinitely

Middle East

When Arab leaders arrived in Iraq last week for the Arab League Summit, they were greeted by a city determined to impress.

Driving into the city from Baghdad International Airport, they passed the statue marking the spot where, on January 3, 2020, a U.S. drone strike killed Maj. Gen. Qassem Soleimani, commander of Iran’s Quds Force, and Abu Mahdi al-Muhandis, commander of Iraq’s Kata’ib Hezbollah militia. The strike, carried out on Iraqi soil without the consent of the government, amplified demands for the withdrawal of U.S. and coalition forces.

keep readingShow less
Keir Starmer UK
Top photo credit: Britain's Prime Minister Keir Starmer ( Benjamin Cremel/Pool)

The UK hits peak feebleness on Israel–Gaza

Europe

On May 19, the British and Canadian prime ministers and French president issued a joint statement against Israel’s actions in Gaza. Beyond the grand gestures, the statement was weakly worded and will have no impact.

It is consistent with the British government’s policy of going soft on Israel since 2023 and shows the weakness of parliamentary accountability in Britain.

keep readingShow less
Trump and Ramaphosa: Awkward meeting could have upsides
Top photo credit: President Cyril Ramaphosa (Photo: GCIS/Flickr) and Donald Trump (Gage Skidmore/Flickr)

Trump and Ramaphosa: Awkward meeting could have upsides

Africa

Set to the background of increased diplomatic tensions between their two countries, South African president Cyril Ramaphosa will be making a much-anticipated visit to the White House today to meet Donald Trump.

Ramaphosa is reportedly eyeing the meeting as an opportunity to reset relations, both economically and diplomatically.

keep readingShow less

LATEST

QIOSK

Newsletter

Subscribe now to our weekly round-up and don't miss a beat with your favorite RS contributors and reporters, as well as staff analysis, opinion, and news promoting a positive, non-partisan vision of U.S. foreign policy.