Showing posts with label Iraq. Show all posts
Showing posts with label Iraq. Show all posts

23 October 2010

25 April 2009

Due to a DOD directive banning military personnel from accessing Wikileaks, I cannot post or link to the site.  However, viewing any of the reports will give you the gist of what they look like.  Take that into consideration, then juxtapose it with an account from someone who has served in Iraq.

Below is the email I sent to my friends and family regarding the events of that day.  I challenge you tell me how the Wikileaks document tells the full story.


GmailXXXX XXX


26 APRIL 2009


XXXXX Sat, May 2, 2009 at 4:54 PM

To: (((OMITTED)))

I originally drafted this email on the 26th, but couldn't send it due to the communications blackout (no emails/calls in or out until next of kin notified...)  The blackout was lifted on the 27th, but we've been busy here, and I haven't had a chance to mail y'all until now...  I want to thank you all for the words of sympathy and encouragement I have received. 
It would have been easier for me to simply not write this email...to hide the raw emotions from y'all.  But the whole point of these emails was to let you in to see what it was like.  I promised you a genuine look at our side of the fight, and here it is.
I kept trying to figure out how I was going to phrase my opening remarks to this email...but nothing eloquent comes to mind.
On 25 April 2009, Thunder Battery lost a member of our family.  SGT Leroy O. Webster was killed in the line of duty.  He was a TC (truck commander) for 3rd Platoon (my sister platoon).  Both 3rd and 4th Platoons (my platoon) were part of the same artillery platoon back at Hood.  SGT Webster was one of my gun chiefs, and I consider myself blessed to have served with him.
It's been more than 24 hours since he died, but I think everyone is still in a state of shock, myself included.
It was late afternoon, and my platoon had just returned to the FOB after completing our patrol.  After refueling the trucks, we headed to the chow hall.  On our way in, we monitored radio traffic from 3rd Platoon: they had a WIA (wounded in action), and were rushing back to the FOB.
My platoon immediately staged the trucks in the parking lot to the chow hall -- not bothering to return to the CP because the FOB gate is closer to the chow hall.  "Send two guys per truck to grab to-go plates, then everyone back here and prepare to roll out."
I called up to battery, and told them that I was standing my platoon up to serve as a QRF (quick reaction force) if necessary.  As we sat there, more details came in over the radio.  SGT Webster had been hit in the shoulder by a sniper shot.  We had no other information.
My initial reactions were anger that someone out there had hurt one of our own.  None of us thought the worst.  We figured SGT Webster would quickly recover, and within a few days, be wandering around mouthing off with his usual wisecracks.
As our guys finished eating, I briefed them on what little information we had: a grid coordinate of where the sniper attack occurred, and a couple of suspect vehicle descriptions.  In the trucks, we have this thing called blueforce tracker (BFT): it's basically a map with icons showing where friendly units are.  Battalion had dropped a green icon at the scene of the attack, and I found myself sitting in my truck, door open, headset on, listening to the radio and staring at the green cone on the screen...waiting for the words "Thunder 46, you are clear to SP FOB and move to following grid..."
Those words never came.  As I was waiting for permission to take my platoon out there, my medic came up to my door.  He was sliding his cellphone into his pocket.  I turned to look at him, pulling one earpiece of my headset away from my head.  I was expecting an update.
"Webster's dead."
I didn't believe him.  I looked at Doc, and said, "You're shitting me."  He shook his head and continued to look at me through his sunglasses.  I looked forward, and put my head in my hand, in shock.
Then, Doc did something that I will always thank him for.  He leaned in, and said, "The guys don't know.  Keep it together, sir."  That was all I needed.
We were still in QRF, and there was still a possibility that we would have to roll out into sector.  I spoke to my platoon sergeant, and we agreed we would not tell the guys until we were fully stood down.  The next hour and a half was perhaps the hardest I've ever experienced: forcing myself to control my emotions, to not let them show.  Trying to focus on the possible mission at hand.  Convincing myself that keeping the knowledge of SGT Webster's death from the guys for the time being was the right decision...
The call to send my platoon out never came.  We parked the trucks back on line, and then I rounded up my platoon so that the commander and first sergeant could talk to them.  At this point, some of the guys (the veterans of previous tours) probably had an idea of what was coming.
The news hit them like a ton of bricks.  The older guys who deployed with Webster last time around broke down and sobbed openly.  All I could do was grit my teeth and clench my jaw.  All I wanted to do was drop to my knees, put my arms around each of them, and cry with them.  But I couldn't.  I had to wait.  The battle NCO (who I work with on a daily basis) came up to me later when we were alone and said, "Sir, I know this is hitting you hard.  As hard as its hitting me.  But everyone here, from the lowest joe on up sees you as the rock of the battery -- they need you to be strong.  At least right now."  Just his words nearly broke me down.  I took advantage of the private moment between both of us to let some of it out before recomposing myself and going back to be with the soldiers.
The entire battery assembled at the CP.  Soldiers were sitting on the ground out front, heads in their hands.  Others were staring off into space, trying to comprehend the loss of one of the battery's largest personalities.  Others sat against the building, heads back, looking up into the night sky, tears rolling down their cheeks.
Late that evening was the ramp ceremony.  The entire battalion, and elements from the brigade as well as the Air Force folks showed up at the airfield to say our final goodbye to SGT Webster in person.  We all assembled in a neat formation.  The guidons and flags were flapping in the wind, and we stood and watched and wept as SGT Webster's flag-draped casket was carefully walked down the aisle between formations and placed in the back of a cargo plane.  It had been hours since I learned of SGT Webster's death, and I couldn't hold it in anymore.  I let the tears flow as we stood there at attention, holding our slow salutes as he passed us and got on the bird to go home back to his family.
Later on, I sat down with my roommate and fellow platoon leader, and we talked about it.  As much as I was hurt, he was hurting even worse.  It was HIS soldier.  It was OUR soldier.  We promised we would look out for each other, watch each other, and make sure that we come out of this mended and healed.
It was 0430 by the time I went to bed.  I slept like a rock, but only for a few hours.
The next day was just as hard.  First Sergeant and I volunteered ourselves to go to the humvee that SGT Webster rode in back to the FOB.  We couldn't bring ourselves to put other soldiers on this work detail.  We cleaned it out the best we could.  Pulled out all of the personal effects of the truck crew -- the body armor, the helmets, the gloves.  We scoured everything, pulling out the items that had blood on them so that they could be cleaned before being returned to the soldiers.  When it was done, Top and I stood at the door, staring at the floor plate between the two back seats where the gunner typically stands.  Despite our best efforts, dried blood could still be seen along some of the edges.  You could still see where undoubtedly the medic worked on SGT Webster while the humvee was speeding back to the FOB.  It was heartbreaking.
My worst fear in coming here had been realized.  There was likely nothing I or anyone else could have done that would've changed anything that day.  But it doesn't change the emotions that wash through you.  I wish I had stayed out in-sector for a little bit longer.  I wish I had the opportunity to find the escaping vehicles by happenstance.  I wish I had the opportunity to be with my brothers in 3rd during their darkest time.
It's a week later, and the healing process has begun.  The mission continues.  The last six days have been the hardest my platoon has ever worked.  Physically, mentally, emotionally...we're drained.  Maybe it's because of what happened last week.  Maybe it's the toll of a non-stop OPTEMPO finally catching up to us.  Regardless, we're going to continue doing what we do.  We have to.
The guys still get edgy a little bit in-sector, but it's not as bad as I feared it would be.  I still dread the prospect of the worst happening...losing one of my guys.  Every day, when my guys assemble for the patrol brief, I look around at them.  I see their faces: from the older, seasoned veterans to the fresh-faced young kids, and I pray that I am able to keep them safe and bring them back today.  And tomorrow.  These soldiers are my life out here: they make me laugh, they put their utmost efforts into the job and the mission at hand.  I am so truly blessed to be a platoon leader for these 23 guys, and blessed to have 107 other Thunder brothers-in-arms who will do anything for each other.
We're hurting (I'm hurting).  But we're healing.  SGT Webster died doing what he loved.  It's not fair (it never is): they always seem to take the best from us.  But we will endure.
Again, I appreciate everyone's thoughts and prayers for SGT Webster's family.  Love and miss you all.  Talk to y'all soon.
-Mike.

Wikileaks madness, Part Deux

They're at it again.  This time, a data-dump of intel reports from Operation Iraqi Freedom, from 2004 to the end of the 2009.

Al-Jazeera TV's British syndicate is running a video that "proves" that U.S. military forces ignored instances of torture committed by Iraqi Security Forces.  Their proof is references to certain FRAGOs (fragmentary orders).  What they don't tell you is that a FRAGO is a modifying order that can be put out at any echelon.  FRAGO 214 or 232 or whatever-the-fuck can be a company FRAGO or a division FRAGO or anything in between.  The takeaway is that without the context (who issued the FRAGO?  To which subordinate units?  What was the content of the remainder of the FRAGO?  What as the base OPORD the FRAGO modifies?), information can be easily spun to be sensationalist and fill whatever political agenda you choose.  A FRAGO put out by one idiot staff officer can easily be rescinded or superceded by the next day's FRAGO.

So, here is what I'm going to do: I am going to demonstrate and prove how these intel reports, taken in isolation outside of the context of what happens on the ground, don't mean anything unless you were there or know the surrounding circumstances.

I'm going to prove it to you.  I know that sounds bold, but audacity is a principle of offensive operations, so let's do this.

I did what undoubtedly a number of fellow officers did: I went to the Wikileaks website and searched for my own unit's actions.  And lo and behold, I found some.  Specifically, the reports documenting the deaths of two soldiers in my battalion.

(Due to a DOD directive banning military personnel from accessing Wikileaks, I cannot post or link to the site.  Which is fine: I understand the OPSEC considerations -- which is why all of us are so enraged by the data-dump.


However, if you, the non-military audience views any of the reports, you will get the gist of what they look like.  Take that into consideration, then juxtapose it with an account from someone who has served in Iraq.


If you are a military reader, do not visit the Wikileaks site.  It is not worth it to be fried for an OPSEC violation.  You will have to consult local directives put out by your chain of command, but better to err on the side of caution.  Just remember you are always subject to UCMJ, both on- or off-duty.)

I want you to read my next two posts: they are verbatim emails that I sent home to friends and family following two incidents.  By the time you have finished reading those emails, you will see how I just proved to you that these Wikileaks extracts mean nothing when viewed isolated from their surrounding context.  I proved it to you because I was there.  And Julian Assange was not.

Once again, I will stress: I have no problems with calling for transparency in our government.  That's a good thing.  That's how we avoid the deathtrap of authoritarian or totalitarian regimes.  But there are more responsible ways to call for change than just data-dumping sensitive information.  Even despite Wikileaks' attempt to sanitize their reports (I will admit they did a better job this time around than with their Afghanistan data-dump), they missed plenty of info in just the small sample of leaks that I read that can provide the enemy valuable information on how to refine their TTPs to continue to kill Iraqi civilians and American soldiers.

23 September 2010

Added to my reading list...

Andrew Exum's got a post from about a week ago, and linked to some books recommended by Gian Gentile, who is a fairly outspoken critic of counterinsurgency (COIN), or perhaps the U.S.'s approach to it.  For those who aren't tracking, ever since the invasion of Iraq in 2003, there has been an ongoing academic debate inside defense policy circles regarding the merits of COIN.  When it became apparent that Iraq was not going to transition to a state of stable peace in anything resembling a timely fashion, the U.S. military found itself desperately treading water.  Counterinsurgency was a dirty word, because no one wanted to admit that an insurgency existed in Iraq: too many comparisons to Vietnam, and too many painful propositions that our failure to conduct stability operations post-invasion may have been a major catalyst for the insurgency and almost-civil war.

Of course, David Petraeus and his hundred-pound-brain (along with other smart guys, like John Nagl) stepped out of the shadows and suddenly COIN lost its stigma and became the messiah of strategies.  History will determine the ultimate effectiveness of America's COIN campaign in Iraq.

In any case, today there is a huge identity crisis in the U.S. military, in the Army and Marine Corps in particular (the service branches most invested in ground combat).  While the Air Force and Navy find themselves affected by the prevalence of stability operations and irregular warfare in the modern operating environment (effects on budgets, equipment programs, etc.), the way they fight is not as profoundly impacted as it is for the grunts and mud-crawlers.  Sure: the Air Force's primary mission of air superiority doesn't get exercised too often nowadays, but an A-10 conducting a close air support (CAS) mission in a conventional high-intensity conflict (HIC) is not terribly different from an A-10 conducting a CAS mission in an irregular warfare stability ops environment.  Yes: there are differences (collateral damage estimates, etc. etc.), but the fundamentals are the same.

Not so with Army/Marine units.  An old-school attack conducted by an infantry rifle company is very different from the new-school cordon and search.  A battery volley of M26 MLRS rockets (each capable of destroying an entire 1 x 1 kilometer square on the ground) is very different from a low-yield GPS-guided rocket or Excalibur artillery round shot in Iraq most recently.

The effects of operating in a drastically changed operating environment can be seen even at the unit level: Army units will spend half a year training up for a deployment in COIN and stability tasks, and then spend a year executing those tasks.  When they come home, they unlearn everything so they can regain their competencies at fighting a conventional warfare fight (or HIC or major combat operations -- the label is not important).  Then, when a deployment appears on the horizon, gears shift back towards irregular warfare and COIN/stability ops.

But this is delving into a topic that can be its own blog post.  Let's get back to the recommended reading.

One of the books on Gentile's list is Abandoning Vietnam: How America Left and South Vietnam Lost its War by James H. Wilbanks.  I have not read this book (yet), but the blurb on Amazon.com indicates that it is a study of our Vietnamization policy and the argument that it was "designed to transfer full responsibility for the defense of South Vietnam to the South Vietnamese, but in a way that would buy the United States enough time to get out with appearing to run away."

The very obvious question is this: is there an analog to today's situation in Iraq?  Is Operation NEW DAWN a modern day "Iraqization"?  Right now, there is a lot of political pressure in favor of us just pulling everyone the hell out, but I would like to see if anyone has put any serious academic or analytical thought into what the projected security environment in Iraq will be when we "leave" in 2011...

17 September 2010

Assessing results in Iraq: too soon?

With the declared end to "major combat operations" in Iraq, it is only a matter of time before we start seeing more and more attempts by people to answer the question that Professor Kamena of the Air War College poses: "Did we win and was this effort worthwhile?"

Prof. Kamena's short piece (it's only a page) does not so much answer the posed question as it puts forth his hopes and expectations.  But this ultimately lends itself to the question: when can we begin to usefully assess the situation in Iraq?  When can we start measuring the effects of our efforts in Iraq?

My answer: not anytime soon.  While we can certainly put our finger on easy metrics (x murders this year versus y murders last year, or economic growth by z percent), these metrics have to be tied in to a purpose or endstate in order to mean anything.  Bottom line up front: the nature of Army operations in Iraq (counterinsurgency vice major combat operations or HIC) means that desired endstates more often than not are defined internally by the host nation (not us), and tangible progress (or lack thereof) may take years or decades to manifest and become apparent.

As a student in his first weeks of small group instruction at the Captain's Career Course, I have been inundated by Army doctrine.  Field Manual (FM) 3-0, simply titled Operations, is the Army's primary doctrinal publication that discusses the Army's way of fighting.  With the latest edition being released in 2008, it is the result of the Army's having looked in the mirror after nearly a decade of continuous engagement in conflict abroad.  Understanding how the Army views itself and its way of war will help us frame the conflicts we are currently engaged in; conceptualizing and visualizing this framework will in turn help us figure out if we can even begin to discuss whether our involvement in Iraq has been a success or failure.

Let's take Prof. Kamena's question and break it down into its two elements: (1) Did we win? and (2) Was this effort worthwhile?

(1) DID WE WIN?

Typically, a pre-requisite to the assignment of a label of success or failure, win or loss, is the identification of the goals or objectives.  From there, analysis should be simple: were the goals or objectives achieved?  Yes = success.  No = failure.  The obvious question then becomes: what were/are our goals in Iraq?  For the moment, let's keep ourselves out of conspiracy theories or controversy that will simply bog us down.  Still, it's a difficult question, and the best way to answer it is to work backwards and find a way to categorize our presence in Iraq: describe our actions there, and then correlate it to doctrinal purposes or endstates.  We're going to confine ourselves to the narrower perspective of military doctrine because it's faster and easier than trying to do an all-encompassing analysis or study: after all, this is a blog, not a Ph.D. dissertation or a funded think-tank.

Everything that follows will be a no-brainer for guys that have experience at the operational levels of war and higher.  For the tactical guys like me (platoon, company), this can be a bit of an eye-opener, but more importantly, a lens that clarifies and puts into context what we accomplish at our levels.  For the non-military folks, this could end up being total gibberish, or perhaps a revealing look at how the Army thinks and operates.  To some, it may come as a surprise to know that the Army as an institution has an academic side to it that goes far beyond the popular (but flawed) "just kill more of the bad guys than they kill ours" characterization.


Figure 2-2 from FM 3-0 (above) illustrates different operational themes that characterize Army actions against the spectrum of conflict.  FM 3-0 defines the spectrum of conflict as "the backdrop for Army operations....an ascending scale of violence ranging from stable peace to general war."  Keep in mind that violence can jump around the spectrum of conflict: it is not a linear scale.   As FM 3-0 reminds us, "unstable peace may erupt into general war, or general war may end abruptly in unstable peace."  The spectrum allows us to describe the security environment.  

While the spectrum of conflict describes the environment, operational themes describe Army actions.  FM 3-0 defines operational themes as describing "the character of the dominant major operation being conducted....[it] helps convey the nature of the major operation to the force to facilitate common understanding of how the commander broadly intends to operate."

Operational themes may be further broken down into the joint military operations that are conducted in support of the over-arching operational theme.  "Grouping military operations with common characteristics under operational themes allows doctrine to be developed for each theme rather than for a multitude of joint operations." (FM 3-0)

Below you will find FM 3-0's Table 2-1 (Examples of joint military operations conducted within operational themes) overlaid onto Figure 2-2.  For example, within the framework of an Irregular Warfare operational theme, conceivable joint operations include FID (foreign internal defense), COIN (counterinsurgency), CT (counterterrorism) and UW (unconventional warfare).  It is important to remember that the array of joint operations available for each operational theme are not mutually exclusive: "[f]or example, noncombatant evacuation operations may be conducted during [irregular warfare], or support to an insurgency may occur during major combat operations."


Each type of joint military operation, whether it's counterdrug, foreign humanitarian assistance, peacekeeping, counterinsurgency or an all-out conventional fight like the 2003 initial invasion named Operation IRAQI FREEDOM I (OIF I), has its own doctrinal set of purposes and objectives.

Now that we've identified ways to describe the overall environment/levels of violence (spectrum of conflict), the general categories of military operations (operational themes), and the types of actions that comprise those themes (joint military operations), we can now try to determine the current state of affairs in Iraq: both the environment on the spectrum of conflict, and the type of operations we are engaged in.  This will aid us in determining what our doctrinal operational objectives are, and maybe in turn help us figure out if our efforts have been effective.


Few will dispute that during the initial invasion of Iraq in 2003, we were engaged in major combat operations (MCO) in a state of General War.  Granted, the campaign was short, but the conventional nature of the fight and the organization of Coalition Forces (CF) and their assigned mission objectives support the characterization of OIF I as MCO/General War.

Post-invasion was when we saw a shift in the security environment in Iraq.  Although everyone was hoping that the conclusion of invasion operations would somehow spur a jump from a state of General War to Stable Peace, what we saw instead was a slow slide into Insurgency.  Religious sectarian violence exploded in Iraq.  In Baghdad,  entire neighborhoods of Sunnis or Shi'as were ravaged and vice versa.  Sunni-dominated al-Qaeda in Iraq (AQI) was engaged in an all-out fight with Shi'a-dominated Jaysh al-Mahdi (JAM), Moqtada al-Sadr's Shi'a militia -- while everyone else, to include CF, were caught in the middle.  

The response to this incredible spike in violence was "The Surge": the insertion of five additional brigades into Baghdad to help quell violence and re-establish security in the capital.  All of this fell within the 2004-2008 time-frame, and although there were large operations conducted (like the battles of Fallujah), by this point Iraq had slid into a state of insurgency on the spectrum of conflict.  Likewise, we shifted operational themes from MCO to irregular warfare, and counterinsurgency (COIN) became the predominant joint operation.

With the end of the Surge in 2008, execution of the Status of Forces Agreement (SOFA) in 2009 and the transfers of authority and sovereignty to the host nation in 2010, we are trying to push or slide things to the left.  "Advise and assist" has become the catchphrase in the media, but we need to examine things in the framework that we have already established.

Arguably, Iraq is probably in a state somewhere between insurgency and unstable peace.  Violence dropped dramatically in 2009, but we are now seeing spikes again as U.S. forces begin to reduce their footprint in Iraq.  Our operational theme probably remains irregular warfare: however the dominating joint operation will probably shift from COIN to foreign internal defense (FID).  As time moves on, I think one goal is to see our residual force of advisors shift to an operational theme of peace operations -- but whether that transition can be made anytime soon is up in the air.

But let's back up for a moment.  We spent several years engaged in COIN operations.  FM 3-0 defines counterinsurgency as those "actions taken by a government to defeat insurgency."  Here, the "government" is the host nation (HN), specifically the government of Iraq (GOI).  FM 3-0 goes on to say that "in COIN, HN forces and their partners [the U.S. and CF] operate to defeat armed resistance, reduce passive opposition, and establish or reestablish the HN government's legitimacy."  Finally, we have stumbled across the reason why it is so difficult (and perhaps too soon) to usefully assess the results of our efforts in Iraq.

The defeat of armed resistance may be quantifiable in terms of number of enemy killed or metrics illustrating lesser and lesser levels of violence.  And on a macro scale, perhaps that goal has been achieved: violence in Iraq today is nowhere near the levels seen in 2006 or 2007, the height of the insurgency.  However, as aforementioned, we are in a transition phase now, and with our withdrawal of forces may come a spike in violence, or in the worst case scenario, a return to civil war.

It is similarly difficult to say whether the goal of establishing the HN government's legitimacy has been achieved.  The elections process in Iraq has been an ongoing nightmare.  Additionally, corruption is rampant at all levels of politics: from the municipal all the way up to national.  Perhaps more striking is the populace's awareness of the corruption, which causes the varying levels of distrust in their government and security forces.  The never-ending struggle to repair the infrastructure and bring some kind of consistency to the delivery of essential services to the populace is another hit against government legitimacy.  

Finally, the most tangible, and perhaps simplest indicator, is violence.  Although we no longer see entire Sunni or Shi'a neighborhoods getting wiped out or cleansed, we are still seeing markets being blown up and acts of violence committed by terrorists and insurgents that will cause the populace to doubt the GOI's ability to provide security for them.

So it is now easy to see why it is so difficult to begin discussing whether we "won" in Iraq.  Keep this in mind the next time you see a talking head on the TV drawing bold conclusions.  We still have a lot of soldiers in Iraq, and we will continue to have soldiers there for a long time.  It may very well be ten or 20 years before we can definitively say, "Yes, we made Iraq a better place," or "No, it was a waste of time that made the global security environment worse: the country tore itself apart five years after we left, and now we have the Middle East version of Somalia."


The importance of using the correct words to say what you mean and mean what you say.  The reason I have led you on this meandering journey to simply find a way to correctly label or characterize the nature of the conflict is because of the confusion that exists in the media, in the government and even within the military.  In all three arenas, terms are thrown around and used too often without regard to their doctrinal meanings or definitions.  The ensuing confusion not only has a disruptive effect on the military's ability to see itself, but also on the public's ability to see what's going on and formulate an informed opinion.

I will be honest and admit that until I came to the Career Course and actually sat down with Army doctrine, I was also guilty of the carelessly-throw-words-around crime.  I was guilty because I was ignorant of Army doctrine: I figured I was a smart guy that knew a lot of fancy terms, but my ignorance only contributed to the problem of this institutional fog concerning our role in the contemporary operating environment.

I used to use the terms counterinsurgency and stability operations interchangeably because I didn't know any better.  Now, I understand that COIN is a type of joint operation, and stability ops is an element of full spectrum ops (along with offensive and defensive operations).  Each type of joint operation, including COIN, is a combination of all three elements in varying ratios.  A raid or a major combat operation might be heavier on offensive elements, while humanitarian assistance or COIN might be heavier on stability elements.

(2) WAS THIS WORTHWHILE?

I hate to disappoint, but there is no military metric for this.  All military action is a means to political ends.  Public opinion and society (and ultimately history) will determine whether our efforts in Iraq were worthwhile.