Wednesday, December 26, 2007

FOB Pacesetter

In the last few posts, I asked several questions about what to me seemed like odd choices that Kirk von Ackermann made shortly before he disappeared. This post looks at the area surrounding the last base he visited for context.

Excerpt from Death of a Contractor

On October 9th, not long after he and Phillips tried to take half of Ultra Services from Dawkins and create a rival company, Kirk von Ackermann visited FOB McKenzie, a U.S. forward operating base near Samarra. After meeting with a Turkish subcontractor, he left the base behind the wheel of his Nissan Patrol SUV. He was alone.
Prior to December of 2003, Forward Operating Base (FOB) McKenzie was known as FOB Pacesetter.


An aerial photo of FOB Pacesetter originally posted online at webshots.com by a member of the US Army, kinard_r.

Map inset showing the general location of Pacesetter originally published in the New York Times on December 29, 2003.

FOB Pacesetter was home to an artillery battalion of the 4th Infantry Division. The base has also been referred to as Camp Pacesetter, Samarra East Air Base and/or Al Bakr Airfield. Pacesetter is probably most notable as the first home of the Stryker Brigade in December 2003 (ref). The region immediately surrounding the base is flat and dry and quickly changes to mud under winter rains.

Interview with MAJ Deverick Jenkins
Combat Studies Institute Fort Leavenworth, Kansas, February 21, 2007
JENKINS: We ended up on Forward Operating Base (FOB) Pacesetter and there was just an artillery battalion there. They were responsible for this entire airbase which was possible because it was a pretty wide open space. All you could see for miles was sand and farmers. It was pretty doable security wise. We did visit the 4th Infantry Division in Tikrit one day to pick up commander’s emergency response program (CERP) funds and we were salivating at how good they had it. Of the month we were at FOB Pacesetter, we only had electricity in tents for about four days. We were there when Saddam was captured in December 2003. I spent my worst Christmas ever there.
Capsized in the canal
by Michael Gilbert, News Tribune, February 20, 2005
So many U.S. convoys had been attacked along the highway through Duluiyah that they’d taken to calling it Ambush Alley. A cemetery north of town was the suspected launch site for mortar and rocket attacks on the American camp at Saddam’s old air base nearby, dubbed Forward Operating Base Pacesetter by its new American occupants.

A field artillery battalion from the 4th Infantry Division out of Fort Hood, Texas, was the lone occupant at Pacesetter before the Strykers showed up. With a few hundred artillerymen, the battalion didn’t have the numbers to make a major push into Duluiyah. And the 4th I.D. was concentrating on problems elsewhere – Tikrit, Samarra and Balad.
Map of the region surrounding Samarra from Maps.com (see 'click here to zoom')

It's not clear which direction von Ackermann travelled after he left FOB Pacesetter.

To the north of FOB Pacesetter is the historic city of Samarra, population approx 300,000.

To the south of FOB Pacesetter is the city of Ad Duluiyah, population approx 50,000. It's about 20 miles between Ad Duluiyah and Samarra.

In 2003, a number of other small American bases were scattered through out the area: in Samarra - Camp Brassfield-Mora, Patrol Base Casino, Civil-Military Operations Center in Samarra; further south in Balad - Camp Anaconda, FOB Lion, Camp Balad, FOB Carpenter, FOB Omaha, FOB Eagle. Von Ackermann's colleague, Ryan Manelick, was killed shortly after leaving Anaconda for Baghdad.

Looking north of Samarra is the city of Tikrit, population approx 200,000, home to the tribe of Saddam Hussein. There were several American bases in Tikrit in 2003. To the south - Camp Packhorse (renamed FOB Remagen) and to the east - FOB Speicher. Inside the Tikrit Presidential Palace, Camp Ironhorse (renamed FOB Danger) and nearby Camp Raider (renamed FOB Dagger). Just south of Tikrit, Camp Arrow in the small city of Ad Dawr. Ad Dawr was where Hussein was captured in December 2003.

It is my understanding that John Dawkins was in a meeting at one of the bases in Tikrit when the call came through that von Ackermann was missing.

For more information on Pacesetter:
Global Security
Photos
If you know anyone who was stationed at FOB Pacesetter in the fall of 2003, please email me. I'd like to hear about access and restrictions getting on and off the base, local patrols, curfews and travel restrictions, etc.

Update - satellite photo of Balad

Northeast of Balad, on the other side of the river Tigris, you should be able to spot the air base.


View Larger Map

Sunday, December 09, 2007

Safa Shukir & the Phone Call

Excerpt from Death of a Contractor

On October 9th, not long after he and Phillips tried to take half of Ultra Services from Dawkins and create a rival company, Kirk von Ackermann visited FOB McKenzie, a U.S. forward operating base near Samarra. After meeting with a Turkish subcontractor, he left the base behind the wheel of his Nissan Patrol SUV. He was alone.

A short time after leaving the base, von Ackermann called Safa Shukir, an Iraqi employee of Ultra Services, to say he had a flat tire and needed help. Shukir drove out to meet him at the mountain pass where he had pulled over. It was a dangerous place -- von Ackermann had warned his co-workers that it was an ideal site for an ambush. When Shukir arrived, forty-five minutes after von Ackermann called, he found the SUV on the side of the road, abandoned. There was no sign of struggle. Von Ackermann's laptop, his satellite phone and $40,000 in cash he had been carrying were still in the car. But there was no sign of von Ackermann.
Not much is known about Safa Shukir. More questions.

Why did von Ackermann call Safa Shukir?

How old is Shukir? Is he fluent in English? Did von Ackermann try to call any one else first? Did he call any one else after he spoke with Shukir? CID must have looked at his satellite phone service records but as far as I know, that information has never been divulged.

Why did von Ackermann choose to call an Iraqi employee instead of one of his contacts at the local US bases. Does that sound like a stretch? Von Ackermann was former US Army and US Air Force and, my understanding is, he wasn't shy about letting officers he was doing business with know his past experience. I understand he even crashed on base a couple of times when it got a little too late.

Why didn't he call someone at FOB McKenzie for help?

When I was a teenager, one of my best friends and I looked a lot alike. I'll call her Jane. Jane and I were both the same height. Same weight. Same color and length of hair -- although hers was a bit sleeker than mine. Jane and I dressed in the same brands of clothes, wore the same shoes. And I could do a great impression of Jane's voice and pattern of speech. One of Jane's favorite pranks was to have me call another close friend of ours and pretend to be Jane. We never got caught. I think I even fooled her mother once. Lots of giggles at the time... But today, those pranks make me wonder about Kirk's phone call to Safa Shukir.

Could Shukir recognize another American man's voice if that person identified themselves first as Kirk?

I don't doubt that someone made a phone call from Kirk von Ackermann's satellite phone to Safa Shukir and that Safa Shukir believed he was speaking with Kirk von Ackermann. But there's this little question in my mind -- could Shukir really recognize different American men's voices over the phone?

Car Photo


Continuing the thread of my last post on Kirk's Car. Photo of a 2003 Nissan Patrol SUV in Australia, similar to the car Kirk von Ackermann is reported to have been driving when he disappeared. Don't actually know which year or color but thought you'd like to see one for reference.

Tuesday, December 04, 2007

Kirk's Car

In my last post, I asked a relatively simple question, albeit one that's kept me awake on occasion: Where did Kirk von Ackermann get his car? The answer, it turns out, is far from simple.

According to the CID, Kirk bought that car in Iraq. Further than that I do not know. They also told me that the car he bought was supposedly the type that Iraqis think CIA agents drive (or that CIA agents actually do drive - can't tell which from my notes). This sounds odd to me as A. if it were true Kirk would know this and would not purchase the car and B. why on earth would the CIA drive consistent types of cars?
That doesn't make sense on so many levels, it's mind boggling. Kirk von Ackermann was a former Air Force Captain with extensive experience in counter-terrorism which required and demanded thinking like a terrorist. Why would he want a car that might be mistaken as belonging to the CIA?

Remember, von Ackermann was traveling for work in the Tikrit region. In the fall of 2003, Tikrit was awash with Americans looking for Saddam Hussein who was from nearby Ouja. It's a very safe assumption CIA personnel were in the area at that time. It simply defies logic that von Ackermann willingly bought a car with even a hint that an American might be inside let alone one that would identify him as CIA.

My second question is, for me, the dog that didn't bark. It's the one detail that has bothered me since the very first time I read Colin Freeman's first article: Why did von Ackermann leave his satellite phone in his car?

Why didn't von Ackermann take a more defensive position, take the satellite phone -- probably similar to a Thuraya with GPS -- and wait a safe distance a way from the car? That response would have been more consistent with his background and training as described in the blog entry: No One Left Behind.

From von Ackermann's family:
I can go one further - why did Kirk not drive on the flat tire to the checkpoint? Yes, the rim would be ruined and he wouldn't make great time but he would not be sitting stranded on an area of road he had himself identified as particularly dangerous.
To better understand the environment these decisions were made in, it would be helpful to reconstruct day to day life in Iraq in 2003.

Saturday, November 24, 2007

Testimony at Oversight Hearing

Old news...

Brief mention of von Ackermann and Manelick in an appendix provided with testimony at an Oversight Hearing for the House Judiciary Committee. Quotes and cites the 2005 article, Foul Play in Iraq? by Doug Waller in Time magazine.
Hearing on: War Profiteering and Other Contractor Crimes Committed Overseas
Tuesday 06/19/2007 - 2:00 PM
2141 Rayburn House Office Building
Subcommittee on Crime, Terrorism, and Homeland Security

Testimony of Scott Horton (PDF), Adjunct Professor of Law Columbia University School of Law New York, NY, page 10

Appendix

Incidents Involving Military Contractors Where Investigation and Potentially Law Enforcement Action is Indicated


Disappearance of American Contractor

“On Oct. 9, 2003, Kirk von Ackermann, 37, was driving alone in northern Iraq when he pulled off the road with a flat tire and phoned the Kirkuk office of his employer - Ultra Services, based in Winters, Calif. - for help. A colleague arrived later to find the car but not Von Ackermann.”11

“Two months later, north of Baghdad, gunmen in an SUV shot and killed Ryan Manelick, 31, another Ultra Services employee, and an Iraqi traveling with him by car.

More...
You'd probably like an update on where things stand these days. In my corner of the world, it's been fairly quiet behind the scenes. As far as I know, there's only one new project still due for release that looks into the events surrounding von Ackermann and Manelick. The investigation sounds like it is at a dead end for the time being.

I still have a lot of mundane questions and am thinking of just going ahead and posting them. Here's one question, just to give you an idea of what keeps me awake some times:
Where did Kirk von Ackermann get his car?
Did he drive it from Istanbul and if so, was it a company car? Personal, borrowed, rental, lease, purchase, Istanbul, etc.

Thursday, September 27, 2007

Majid Kadom

It still surprises me that I stumble on news articles that, for whatever reason, managed to escape three years of previous search attempts. A link to the online version of this article eluded me for years.

My Saddam river hol
By Philip Cardy, The Sun, September 22, 2003

Business consultant Robert, of Notting Hill, West London, said: “I’d done a spot of waterskiing but only off Dorset. We went for lunch by the Tigris and realised it was beautiful for waterskiing. The boat guy had a pair of ancient waterskis nobody had used for years.”

Ryan, a US Army contractor said: “I know it was crazy but I thought, what the hell.”

Iraqi onlooker Majid Kadom, 41, said: “In Saddam’s day nobody ever waterskied along the Tigris. His guards would have shot at you. I was still worried somebody would start shooting.”
Related posts here at the Missing Man:
Waterskiing on the Tigris
Waterskiing on the Tigris Pt 2
Two Weeks in Baghdad by Robert Sinclair
Majid Kadom, briefly quoted in the article above, worked for Ryan Manelick. On the day he was killed, Kadom was reportedly at the hospital seeing to an injured relative. Because of his absence that day, Kadom would later figure in theories about what happened to both Ryan Manelick and Kirk von Ackermann.
Death of a Contractor
By Daniel Halpern, Rolling Stone, February 22, 2007

Dawkins proposed a series of theories. Maybe Charles Phillips and Ryan had invented the bribery allegations as part of the scheme to seize Ultra Services for themselves. Phillips "made bold threats to me stating that it is easy to frame someone and that Ryan had been trying to frame me for bribery and that his aim was to land me in jail," Dawkins wrote to Greg Manelick. Or maybe Ryan was skimming money from the company along with his Iraqi bodyguard, Majid Kadom, and Majid had killed Ryan to get the whole score for himself. Maybe Kirk von Ackermann had discovered Ryan's skimming and had been silenced by Ryan or Majid.
Colin Freeman interviewed Kadom for a piece published in the Scotsman in November of 2003, just 6 weeks before Ryan Manelick was killed.
Six months on, Iraq is a nation in a state of flux
By Colin Freeman, The Scotsman, November 1, 2003

For the first two months after the war, [Majid Kadom] lived off his wits, buying and selling whatever he could to keep money coming in for his wife and four children. Then he realised that with the influx of foreigners into the country, the fluent English he had learned during military training 20 years ago was probably his best asset.

After a brief spell working as a translator, he got a job as a $140 (£82.56)-a-week local manager for a US civilian contractor to the army, supplying gadgets such as shower units and caravans to army bases around Tikrit.

Mr Kadom now finds himself as the main breadwinner in his family, with his eight grown-up brothers now dependent on his new job to find them work as drivers, labourers and office assistants.
From the interview, it's a stretch to believe Kadom was involved. It just sounds like he had too much to lose

Friday, August 10, 2007

Contractor Casualties - 1,001

LancasterOnline has a blog by Gil Smart, Smart Remarks. Smart is associate editor and columnist for the Sunday News in Lancaster, PA. The blog post links to Daniel Halpern's in-depth article in the Rolling Stone, Death of a Contractor.

Who killed Ryan Manelick?
by Gil Smart, Smart Remarks, LancasterOnline, August 9th, 2007

Ryan Manelick died at age 31 in 2003, a victim - or so it has seemed - of the then-nascent Iraqi insurgency. The Conestoga Valley graduate, an Air Force vet, was in Iraq as a contractor; and more than 400 contractors have died at the hands of insurgents since the war began.
The Department of Labor just released new contractor casualty figures based on claims filed under the Defense Base Act.
Labor Dept: 1,001 contractors have died in Iraq
by David Ivanovich, Houston Chronicle, August 8, 2007

In response to a request from Rep. Jan Schakowsky, D-Ill., the Labor Department revealed that 1,001 civilian contractors had died in Iraq as of June 30, including 84 during the second quarter of the year.

So far in 2007, at least 231 contractors working for U.S. firms have died in Iraq.

Those contractor fatalities are in addition to the 3,668 military personnel the Defense Department had confirmed dead in Iraq from the start of the war in March 2003 until today.
On a related note, several of us at ePluribus Media have started a new project using their Timelines database: a list of contractors who have died while working in Afghanistan and Iraq. It's currently in beta format as we continue to adjust data fields to meet the needs of this new Timeline. Ryan Manelick and Kirk von Ackermann are both included.

e Pluribus Media Contractor Casualty Timeline

Friday, May 25, 2007

Manelick in South Africa

It's always interesting to see the spread of news on the internet and who will pick up a story. But, I have to admit, this one caught me by surprise.

Keep in mind Ryan Manelick was killed 3 and 1/2 years ago.

The image I am including is a screen capture from the Security Affairs section of the website of the United States Diplomatic Mission to South Africa. Under the heading Military Civilian Relations is a summary and link to Daniel Halpern's article in Rolling Stone magazine, Death of a Contractor. At the bottom of the page: "This site is maintained by the Public Affairs Section of the Department of State in South Africa."

I'm glad to see the story get publicity. I'm just a little puzzled as to why the US Embassy in South Africa picked it up.

Wednesday, April 18, 2007

We Get Mail

In response to letters, a follow up to the previous post, The ID Badge, is in progress.

Background: Von Ackermann's badge was found among John Dawkin's belongings by a former colleague, Egeman Çakmak. It is my understanding that the circumstances surrounding the ID badge and Egemen Çakmak are much more complicated than publicly disclosed to date.

To avoid further confusion, included is a scan of the photo of Kirk von Ackermann's id badge which accompanied the print version of the article in Rolling Stone magazine, Death of A Contractor.

Saturday, April 14, 2007

The ID Badge

Dan Halpern wrote a wonderful piece for the Rolling Stone. His writing style appealed to the avid reader in me, capturing a bravado and adventurism I've always imagined must be present in Iraq.

On a more serious note though, Halpern's reporting of circumstances surrounding von Ackermann's ID badge raises some questions.

Death of a Contractor
By Dan Halpern, Rolling Stone, March 8, 2007, Issue 1021

Then, while [Egeman] Cakmak was traveling with [John] Dawkins in Afghanistan that fall, trying to drum up new contracts, he stumbled across something that stopped him in his tracks. There, among Dawkins' possessions, was the Ultra Services badge that had belonged to Kirk von Ackermann, the official Defense Department identification that allowed him to be in Iraq. For Cakmak, it was a stunning discovery: Dawkins had previously said that the badge had never been recovered.

Cakmak confronted Dawkins. "Nobody found his passport or his badge?" Cakmak asked. Dawkins said no -- they hadn't ever found Kirk's passport, badge or gun.

Cakmak turned to [Bora] Tuncay. "He's lying," he said in Turkish. "Because I have the badge." Then, turning to Dawkins: "I found Kirk's Ultra Services badge in the office, while we were moving."

"Ah, the badge!" Dawkins said. "It wasn't missing. It came with the stuff CID gave me."

Cakmak didn't believe him. Dawkins had told him that CID had not returned von Ackermann's possessions until months after his disappearance. But Cakmak had discovered a scan of Kirk's badge on a laptop computer belonging to Dawkins. The scan was dated October 10th, 2003 -- the day after Kirk had disappeared.

"How does he have the badge that was around Kirk's neck to scan onto his computer the day after Kirk disappeared?" Cakmak says. "He has it because the men he hired to kill Kirk brought it to him as proof."
Let's address the "badge" first. Colin Freeman reported a "photo ID" in November 2003.
Bay Area civilian vanishes in Iraq
By Colin Freeman, San Francisco Chronicle, November 11, 2003

At a U.S. Army checkpoint a few miles along the road from where von Ackermann disappeared, soldiers were issued with a photocopy of his photo ID several weeks ago. But during troop rotations, no information was passed on about the case, leaving the incoming troops unaware of who he was or why they even had his photo.
We know from Freeman's second article that Ryan Manelick was a significant source for the above first on Kirk von Ackermann's disappearance. It's possible Manelick knew about the photocopies of the photo ID and told/showed Freeman. It shouldn't be too hard to find out.

Çakmak's insinuations also raise questions about what appears to be a deliberate and on-going effort to pin the disappearance of von Ackermann on Dawkins even though CID has supposedly determined it was a botched kidnapping attempt by Iraqis (ref). Any way...

Back to that short sentence about the laptop:
But Cakmak had discovered a scan of Kirk's badge on a laptop computer belonging to Dawkins.
That one sentence contains a very small but intriguing detail. What was Egeman Çakmak doing with John Dawkins' laptop?

In June 2004, the domain name server listed on the registration for Dawkin's company mesopotamiagroup.com was changed. The domain name server was switched to a co-located server in Turkey. A year later, in the summer of 2005, mesopotamiagroup.com was "hijacked." In order to accomplish this, access was needed to send an email from one very particular address: john@ultra-services.com

It's been a while since I've thought about who hijacked mesopotamiagroup.com?

Wednesday, April 11, 2007

Jeffrey Ake

An American contractor, Jeffrey Ake of LaPorte, Indiana, disappeared in Iraq two years ago today. The side bar to an AP article about Jeffrey Ake today mentions Kirk von Ackermann as still missing.

A Hoosier's fate remains uncertain
By Will Higgins, The Indianapolis Star, April 11, 2007

Recent news reports have highlighted that the Ake family have had a hard time financially. With the large number of contractors now working in Iraq for United States agencies, is it really too much to ask that each and every contractor at least be covered by a minimum of insurance? Families shouldn't have financial stress added on top of the pain and worry of a missing family member.

See The Defense Base Act for more on the topic of insurance.

Friday, April 06, 2007

The Defense Base Act

In early 2005, I became aware that Kirk von Ackermann, a civilian contractor working in Iraq, was not covered by "insurance" when he disappeared on October 9, 2003. I sought to find out a) what was this "insurance" and b) why was it missing? The result of the ensuing two years of research -- in to what I would quickly learn was the Defense Base Act -- is a three-part series for ePluribus Media of which the first part is now available.

Part I traces how the lack of adequate insurance coverage impacts families. In particular, it goes into some detail on how lack of Defense Base Act coverage impacted the von Ackermann family.

Part II concentrates on how the appropriate Defense Base Act contract clauses that could have made a difference went "missing in action."

Part III focuses on the lack of information and access to low cost coverage for contractors based overseas.

Iraq, Contingency Contracting and the Defense Base Act
by Susie Dow, ePluribus Media, March 28, 2007

Established in 1941, the Defense Base Act (DBA) provides the equivalent of workers' compensation for civilian contractors working on contingency operations in overseas countries such as Iraq and Afghanistan. DBA provides benefits in the event contractors are injured, killed, or kidnapped in the course of their work for US government agencies such as the various branches of the Department of Defense, USAID, or the State Department. But this insurance is not automatic, employers must purchase it. And before they can do that, they must know about it.

More...
Parts II & III will be posted over the next several weeks. I'll update this post with links once available.

Sunday, March 04, 2007

Iraq, Contingency Contracting and the Defense Base Act

This is a reprint of my article,
Iraq, Contingency Contracting and the Defense Base Act
By Susie Dow, ePluribus Media, March 4, 2007

Introduction

Iraq contractor. Those two words evoke different reactions from different people. For the families of the contractors who have been injured, kidnapped or killed as a result of simply doing their jobs,there's a much more pressing concern than public opinion: insurance.

In early 2005, Susie Dow became aware that a civilian contractor, Kirk von Ackermann, was not covered by "insurance" when he disappeared in Iraq on October 9, 2003. She sought to find out why. The story that follows is based on research, interviews, correspondence, documents, emails, and phone calls over a two year time span.

The first part of this series traces how the lack of adequate insurance coverage impacted families already suffering the deaths or uncertainty surrounding the status of their family members serving in Iraq or Afghanistan as civilian contractors. Part II concentrates on why the appropriate Defense Base Act clauses that could have made a difference went "missing in action." Part III focuses on the lack of information, training and access to low cost coverage for contractors based overseas.

Susie Dow has followed the Missing Man story since February 27, 2005. Her first ePluribus Media story One Missing, One Dead; An Iraq Contractor in the Fog of War, follows the tale of two American civilian contractors.

Part I - Insurance

Kirk von Ackermann is missing.

So is his fellow worker, Ryan Manelick.

Although both men, contractors in the Iraq theater, have been declared dead, they are both missing from the official statistics of the injured or deceased maintained by the Department of Labor.

But let's back up a minute:

On March 18, 2003, one day before the start of the war in Iraq, Defense acquisition personnel were given a presentation that outlined recurring problems with insurance for contractors: contracts from the Department of Defense (DOD) were too often excluding Defense Base Act clauses, the very clauses that provided a modicum of insurance protection for civilian contractors. While both the State Department and the US Agency for International Development (USAID) secured low cost insurance for their overseas workers, the Pentagon consistently did not implement efforts for department-wide coverage. The rationale? To many, it seemed that for the DOD, saving money [1] was considered more important than broad access to coverage [2], coverage that would ensure surviving family members of kidnapped or killed contractors received compensation [3].

History of the Defense Base Act

Established in 1941, the Defense Base Act (DBA) [4] provides the equivalent of workers' compensation for civilian contractors working on contingency operations in overseas countries such as Iraq and Afghanistan. DBA provides benefits in the event contractors are injured, killed, or kidnapped in the course of their work for US government agencies such as the various branches of the Department of Defense, USAID, or the State Department. But this insurance is not automatic, employers must purchase it. And before they can do that, they must know about it.

According to a January 23, 2007 USA Today and AP wire services story, the Department of Labor who administers DBA benefits, reports that at least 770 contractors have died [5] and 7,761 contractors have been injured in Iraq between March 2003 to December 31, 2006.

At least two American contractors should be listed: Ryan Manelick and Kirk von Ackermann. They are not, however, included in DBA casualty figures.

[Editor's note: in October 2008, author Susie Dow learned that the Department of Labor did not release casualty information on companies with fewer than 7 incidents out of concern for privacy. However, the policy is not a legal requirement and as a result, its merit is questioned.]

The Slow Pace of Bureaucracy

Deirdre A. Lee, former Director of Defense Procurement and Acquisition, attended that March 18th, 2003 briefing [6] of the Defense Acquisition Excellence Council, highlighting that contracts with the Department of Defense did not always include the required DBA contract clauses.

Seven months after that briefing, on October 9, 2003, civilian contractor Kirk von Ackermann working for Ultra Services of Istanbul, Turkey, which fulfilled logistics contracts for the US Army, disappeared in Iraq.

Nine months after that same briefing, on December 8, 2003, Director Lee belatedly issued a policy memo to [7] Defense agencies indicating that DBA was a required contract clause that should be included in overseas contracts where appropriate. Within one week, von Ackermann's colleague, Ryan Manelick, was gunned down after leaving a meeting at a base in Iraq.

Eighteen months after that briefing, the two Ultra Services principals would learn for the first time of the necessity of DBA insurance, too late to cover either of the two men. With no coverage, both men are omitted from the statistics the Department of Labor compiles on Iraq contractors.

The Family Left Behind

When Kirk von Ackermann disappeared on that October day in 2003, he left behind a wife and three children.

Within a month of first learning about the Defense Base Act in March 2004, Megan von Ackermann filed a claim for compensation. To contact her husband's employer Ultra Services, which by that time had ceased operations, a claims examiner faxed a letter of inquiry dated August 5, 2004 ultimately reaching Ultra Services' principals John Dawkins and Geoff Nordloh. The inquiry requested information on von Ackermann's disappearance as well as the name and address of Ultra Services' Defense Base Act insurance carrier.

But, Ultra Services didn't have DBA insurance. In fact, the company principals had never even heard of DBA during the time of their work in Iraq despite the fact that Ultra Services had processed over $12 million in contracts.

And even though Nordloh and Dawkins had also fulfilled millions of dollars in contracts for the US Army in Afghanistan, they only had just first learned of the Defense Base Act requirement from another contractor, construction giant Perini, through a draft of a proposed subcontract for work with the US Army in Afghanistan in the summer of 2004. In none of Dawkins' or Nordloh's previous prime contracts had the US Army ever mentioned the need for DBA.

Meanwhile, Megan von Ackermann had another problem -- her husband was considered "missing," not dead. The Department of Labor initially indicated that they needed the US Army's Criminal Investigation Division's (CID) findings into her husband's disappearance before they could decide her claim's status.

On August 9, 2006 -- two years after the initial letter was faxed -- the CID informed Megan von Ackermann that they had determined that her husband, a former Air Force Captain, had been killed on October 9, 2003 during a botched kidnapping [8]. While CID's determination allows Megan to move forward with processing a claim, it doesn't resolve the issue that Ultra Services didn't have DBA insurance at the time of her husband's disappearance. To this date, his remains still have not been found.

The von Ackermann family is unlikely to ever collect DBA benefits. Worse, since Kirk von Ackermann was considered a missing person for almost three years, and as a result, his family was not eligible for Social Security survivors' benefits [9], until the determination by CID. For the von Ackermann family, meeting day-to-day expenses is an ongoing problem:
I worry about money constantly - and I hate it. I don't want to reduce our situation to finances, and in a way I'm afraid the stress over money is masking the pain of our loss. The two things are so huge... and that hurts too; it hurts that being poor is nearly as difficult as losing Kirk. -- Megan von Ackermann [10]
Unfortunately, the von Ackermann family's experience is not unique. An Associated Press article reported Lillian Ake, wife of missing Iraq contractor Jeffrey Ake, is also unable to collect benefits. While she and her four children have received financial support through her church, Lillian Ake has placed their family home on the market in addition to beginning bankruptcy proceedings for her husband's business. [11] Jeffrey Ake was last seen being held at gunpoint in an April 13, 2005 video.

Contingency Contracting

Like Jeffrey Ake, Kirk von Ackerman and Ryan Manelick were civilian contractors working in a "contingency operation." As designated by the Secretary of Defense, Operation Enduring Freedom (OEF) in Afghanistan [12] and Operation Iraqi Freedom (OIF) in Iraq [13] are both contingency operations. [14] As such, the procurement of goods and services in support of these operations is known as Contingency Contracting and is performed by Contingency Contracting Officers (CCOs). [15]

Contingency contracting, by its very nature of working in close proximity to the battlefield, brings high risks. Civilian contractors deliver much needed supplies and services and, in doing so, often find themselves situated closer and closer to hostilities as competitive outsourcing through the US government's A-76 [16] program increasingly determines the most cost-effective way to fulfill government operations is through the private sector.

Contractors

Based on a survey for CENTCOM [17], and as reported in a December 5th, 2006 Washington Post article, more than 100,000 American and Third Country National civilian contractors [18] are estimated to currently be working in Iraq. Notably, this number does not include their sub-contractors. Requiring DBA insurance coverage depends in part on the "type" of support a civilian contractor provides.

Three types of civilian contractors are on or near the battlefield supporting contingency operations:
Systems support contractors maintain specialized equipment, generally sophisticated weapons. [19]

Theater support contractors are contracted by contingency contracting officers to provide immediate goods and services, generally by local vendors.

External support contractors, perform logistical support such as base construction and maintenance.
Ultra Services, the company Von Ackerman and Manelick worked for, was an external support contractor, similar to the more well-known, although much larger, Halliburton subsidiary Kellogg, Brown and Root (KBR). In fact, as external support contractors, ------------. KBR administers the Logistics Civil Augmentation Program (LOGCAP) III contract for the US Army.

According to one former US Military contracting officer, as a result of LOGCAP, KBR has its own contracting officers who procure goods and services for the Department of Defense's contingency operations. KBR employees are required to be covered by DBA insurance and, per the terms of the LOGCAP contract, KBR also requires that their subcontractors be adequately covered by DBA insurance as well. [20]

Had everything gone according to the Pentagon's plans, Halliburton's KBR unit would have handled most of the contracts for logistics in Iraq. [21] Companies such as Ultra Services would have served as subcontractors to KBR so that, by default, their employees would have been covered by DBA insurance coverage. Unfortunately for the von Ackermann family, the Pentagon's assumptions met a different reality.

Who Cares?

The Department of Defense was obligated to have all of its contractors who are legally required to carry DBA insurance to do so. Unfortunately, the Department of Defense's implementation was less aggressive than other US governmental agencies.

Whereas the State Department and USAID had for many years secured reasonable rates from insurance carriers for DBA, rates that added less than 5% to contract costs, the Department of the Defense did not. For other agencies, rates remained low as underwriters spread risks, charging the same rates in safer countries. But for years, the Department of Defense resisted efforts to secure broad coverage for its contractors. By the time the Department of Defense solicited competitive bids, its efforts met failure:
"On August 8, 2003 after the invasion, the Defense Department asked insurance agencies to submit proposals for selling discounted death and injury coverage to military contractors in Iraq, Afghanistan and Kuwait.

Not a single insurance company bid on the solicitation, which expired September 2, 2003 because the risks were too high to make it profitable." [22]
At the same time that the Department of Defense was failing to secure DBA insurance for its contractors at a reasonable cost, Operation Enduring Freedom was nearing the end of its second year in Afghanistan; Operation Iraqi Freedom, was nearing the end of its first six months. Meanwhile, DBA insurance rates for Department of Defense contractors – not surprisingly -- had skyrocketed well above those of USAID and State Department contractors, in some cases almost doubling overall contract costs. [23]

Eventually, the Department of Defense would later learn it was paying out as much as 10 times more in premiums than the other two government agencies [24]. The US taxpayer, of course, picked up the tab. [25]

Part II: DBA Clauses Missing In Action

The first part of this series traced how the lack of adequate insurance coverage impacted families already suffering the deaths or uncertainty surrounding the status of their family members serving in Iraq or Afghanistan as civilian contractors. Part II concentrates on how the appropriate Defense Base Act contract clauses that could have made a difference went "missing in action."Missing in Action

For those writing and administering contracts, whether or not to include the appropriate Defense Base Act (DBA) clauses requiring insurance protection for civilian contractors is left to individual contracting officers. At best when the appropriate clauses are missing, the contract was mistakenly assumed to be exempt. At worst, the clause was overlooked or never considered.

Gray Zone

Department of Defense contracts are generally divided into three types: services, supplies, and construction.

Both "services" and "construction" contracts require DBA clauses. But civilian contractors who provide "supplies" on or near the battlefield are generally exempt from carrying DBA insurance. However, in some instances, contractors who provide supplies where the contract requires work on site -- known as "service incidental to supply" -- are not exempt. 1

Current language within Federal Acquisition Regulation (FAR) 2 is ambiguous and may appear to waive the requirement of DBA coverage by creating grey zones for service incidental to supply. These grey zones leave each contingency contracting officer to interpret FAR to the best of his or her ability and to determine when and where they should include DBA clauses.
The Defense Base Act clause is a mandatory clause that must be included in appropriately designated contracts awarded by any federal agency for overseas performance. It should be included in the "check list " provided to government contracting officers with responsibility for soliciting and awarding contingency (and any other) type of contracts for overseas performance. -- Alan Chvotkin of the Professional Services Council 3
One can argue that the work of Ultra Services and its employees, Kirk von Ackermann and Ryan Manelick, may have fallen outside of "service incidental to supply." That is, the contracts they worked under were exempt from DBA because they supplied US forces with prefabricated Containerized Housing Units (CHUs) and their work was not sufficient to warrant DBA coverage.

Although purchases of trailers such as Containerized Housing Units (CHUs) are handled by supply contracts and are usually exempt from DBA, CHUs require some supervision from the contracted vendor -- in this case, Ultra Services -- on the work site itself such as offloading from shipping trucks, placement on concrete pads, and hook-up of utility lines.

Given such activity at the worksite, should the supply contracts for the purchase of CHUs include DBA clauses? Contingency contracting officers were left to figure it out on their own. Complicating the matter, while deployed in a war zone, contingency contracting officers also had other priorities.

In 2003, during the time von Ackerman and Manelick were in Iraq, contingency contracting officers (CCOs) were expected to respond rapidly to the priorities set by their commanders for fulfilling the immediate needs of 173,000 troops. They were also expected to verify that, where needed, subcontractors also had DBA in place.

With upwards of 200 requisitions and 400 contracts on the CCOs' desks, each CCO had to decide between 1) carefully including all relevant contract clauses and verifying each contractor's insurance paperwork -- which could add delays or 2) quickly expediting the contracts to secure the needed supplies and services for troops.

A 21st-century military force "burns up" a tremendous volume of expendable supplies and continuously needs repairs to equipment as well as medical treatment. Without a plentiful and dependable source of fuel, food, and ammunition, a military force falters. First it stops moving, then it begins to starve, and eventually it becomes unable to resist the enemy.4 -- Patrick Lang, Christian Science Monitor.

Under such a pressure, it should come as no surprise that some supply contracts were little more than a statement of understanding, with an actual contract following months later. The Department of Defense placed its contingency contracting officers in an untenable position. Either the troops on the ground suffered shortages or the civilian contractors and their families faced the risk of being uninsured in a dangerous environment. Even today, unless more detailed language is added to the Federal Acquisition Regulation (FAR), contingency contracting officers are likely to be unaware of decisions that clarify policy5 -- most especially while deployed in war zones -- as they prioritize fulfilling troops' needs over paperwork.

Bandaid or Surgery?

The sheer volume of work, compounded by a lack of clear guidance from the Department of Defense promoted confusion. Confusion, the Department of Defense should have both expected and been prepared for.

And indeed, the Special Inspector General of Iraq Reconstruction (SIGIR) issued a report, Iraq Reconstruction: Lessons Learned in Contracting and Procurement which analyzed contracting problems and made several recommendations. One recommendation was to establish a new Contingency FAR specifically for contingency operations. Another prompted the Deputy Secretary of the Army for Policy and Procurement to prepare two new guidebooks: The Army Guidebook for OCONUS Contingency Contracting and CONUS Guide for Supporting Emergencies within the United States and Supporting Overseas Contingencies from CONUS Locations.

Drafts of the guidebooks reportedly rely on Special Operations Command (SOCOM) contracting documents as well as on the Air Force Guidebook on Contingency Contracting6 a source that a review showed7contained no reference to DBA insurance.

In September 2003, the US Army issued a new guidebook, Army Contractors Accompanying the Force (CAF) 8 which included two pages on the necessity of Defense Base Act coverage. Acquisition personnel knew contractors may not be aware of the DBA, as pointed out within the guidebook:
Pursuing benefits and remedies under these laws is the responsibility of the contractor employee and/or contractor. Since they may be unaware of this assistance, however, contracting personnel should inform the contractor of these laws if the situation arises. 9
The contractor is ultimately responsible.

Insurance in some circumstances is available under the Defense Base Act and Longshoreman's and Harbor Workers Compensation Act administered by the Department of Labor, and the War Hazards Act. It is the contractor's or employee's responsibility to pursue possible benefits under those Acts. 10

Yet, for the families of civilian contractors, it is imperative that both new guidebooks include clear guidance on the implementation of the Defense Base Act for the tens of thousands of civilian contractors working overseas.

Ducking Responsibility

The SIGIR report, Lessons Learned, confirmed that by Spring 2003 the Department of Defense had fully expected the Logistics Civil Augmentation Program (LOGCAP III), as administered by Halliburton's KBR, to reliably fulfill ALL logistics needs in Iraq. 11 Had KBR done as the Pentagon expected, companies such as Ultra Services would have clearly understood they were required to carry DBA insurance for their employees. Had Ultra Services secured coverage, Kirk von Ackermann's family would have received benefits during the entire duration he was considered missing, sparing his family the added burden of financial hardship.

But unfortunately, due to the urgency and sheer volume of needs required by deploying 173,00012 troops to the Iraq region, many of the responsibilities expected to be coordinated by KBR actually fell to Department of Defense contracting officers. Simply put: the Department of Defense had grossly underestimated and severely misjudged the abilities of LOGCAP III to handle Iraq contracts and by extension, insurance protection for its contractors. The Pentagon was unprepared to handle logistics on the battlefield.

As succinctly pointed out by Dov S. Zakheim, the Pentagon's comptroller from 2001 until 2004, "You're really asking too much of one firm to be able to manage all of this."13 As further proof of this basic fact -- that no one company could provide 100,000 contractors -- the Department of Defense announced in July 2006 that the next contract for logistics support, LOGCAP IV, would be split and awarded to three separate external support contractors. 14 And a fourth contractor will "monitor the performance" of the other three.

Finding Insurance On The Battlefield

While the Department of Defense in Washington DC expected external support contractor KBR to fulfill LOGCAP III, life in theater didn't cooperate. Contingency contracting officers were confronted with the necessity of working with local contractors to get urgently needed requisitions filled. Waiting for KBR to deploy sufficient staff and personnel to implement LOGCAP III throughout Iraq was not a viable option. Additionally, the expectation that contractors already operating in Iraq would have secured some form of local workers' compensation coverage was unrealistic.

Even if they'd known of the need for DBA insurance, local companies such as Ultra Services had few options. Iraq didn't have much in the way of a robust private insurance industry. Many Iraqis had relied on government insurance programs. Reporting on an early briefing held by Bechtel for local Iraqi companies in Baghdad, July 2003, Kelly Hayes-Raitt wrote:
Before this last war, there were six insurance companies in Iraq, the largest of which were run by Saddam Hussein's government. They offered basic auto and casualty insurance, workers compensation and liability insurance with maximum policies of either 200 million or 150 million dinars (about $100,000 or $60,000, respectively). As of July [2003], only one insurance company was operating. The others had been shut down or looted. 15
As one example of these difficulties, when local Iraqi companies first sought work as Bechtel subcontractors, they were told to get insurance. 16 But there was no mechanism in place to procure the three types of insurance Bechtel required -- indemnification, bid security, and performance, so eventually, Bechtel told their potential subcontractors that American companies would provide it. Finally, even unable to make that solution work, Bechtel waived their insurance requirements for Iraqi sub-contractors altogether17. Under LOGCAP III, today, KBR does not normally require liability insurance18 from its Iraq sub-contractors, but instead requires DBA coverage which is easier to obtain through a referral to its own insurance carrier, AIG. 19

Civilian Contractors Assuming Military RisksWhy is the insurance situation for civilian contractors important?

Since 2000, the number of contract obligations and contract actions by the Department of Defense has nearly doubled. 20 As more services within the military are privatized or outsourced, 21 reliance on civilian contractors supporting overseas contingency operations increases -- civilian contractors assume risks once handled entirely by military personnel.

The administration's own numbers illustrate how dramatically the warrior is becoming privatized.

With their increased presence, more civilian contractors, such as Ultra Services' von Ackermann and Manelick, face the possibility of injury, kidnapping and death. Accordingly, the Department of Defense and the Department of Labor have a responsibility to ensure broad implementation and uniform dissemination of DBA contract clauses.

Part III: Information, Training & Access

Part I of this series traces how the lack of adequate insurance coverage impacted families already suffering the deaths or uncertainty surrounding the status of their family members serving in Iraq or Afghanistan as civilian contractors.

Part II concentrates on why the appropriate Defense Base Act (DBA) clauses that could have made a difference went "missing in action."

Part III focuses on the Defense Department's (unlike its counterparts in the State Department and United States Agency for International Development (USAID)) inability to provide information, training and access to low cost coverage.

What Went Wrong?

Inadequate planning, staffing and implementation seem to be the main culprits in the Department of Defense's inability to implement Defense Base Act procedures, especially in light of the other government agencies' ongoing success in doing so.

Stepping back five years to see what happened to the Department of Defense's efforts, we start in March of 2002, when two former councils1 combined to create the Defense Acquisition Excellence Council (DAEC). The DAEC was established to:
...address acquisition, technology and logistics issues that cut across organizational and functional boundaries [and] to collectively work issues as well as take actions to accelerate implementation of the Under Secretary of Defense for Acquisition, Technology & Logistics (AT&T) initiatives to achieve acquisition excellence. 2
One of the earliest meetings of the new DAEC, 3 March 18, 2003 mentioned in Part I of this series was the same briefing that Deirdre A. Lee, then Director of Defense Procurement and Acquisition, attended but failed to act upon for over 9 months.

The presenter that day who outlined the difficulties with DBA was Alan Chvotkin of the Professional Services Council (PSC). PSC is "the leading national trade association representing the professional and technical services industry doing business with the Federal government"4 In his briefing, Chvotkin showed the slide on the left.


Alan Chvotkin's slide was clear. His action list provided immediate steps to solve the DBA problem. And those immediate steps weren't merely hypothetical -- Chvotkin based his presentation in part on an informal telephone survey he conducted with PSC member companies that had contracts from the Department of Defense.5 A number of those member companies' contracts had not included DBA clauses even though they should have been required to.
Like so many other government contracting matters, overseas contracting requires specialized training and experience. [...] We found that, during the initial phases of the Iraq conflict, the responsibility for contracting was more highly diffused among DoD contracting officers, some of whom did not traditionally award overseas contracts. That lack of familiarity, coupled with the urgency of some awards and the ambiguity of the scope of coverage of the DBA clause, probably contributed to the failures to include this specific provision in all contracts.6 -- Alan Chvotkin
Although it took 9 months to be issued, Director Deirdre A. Lee's memo clearly recognized the severity of the problem that Chvotkin had so succinctly outlined.
Subject: Inclusion of Defense Base Act Clause in DOD Overseas Contracts

It has come to my attention that there may be some inconsistency within the Department regarding the inclusion of the Workers' Compensation Insurance (Defense Base Act) clause at FAR 52.228-3 in our contracts to be performed outside of the United States. [...]

I want to emphasize that the Workers' Compensation Insurance (Defense Base Act) clause FAR 52.228-3 should be included in all DoD service contracts to be performed (either entirely or in part) outside of the United States, as well as in all supply contracts that also require the performance of employee services overseas. [sic]
Despite the strong wording of Director Lee's memo, there were (and continue to be) few opportunities for contingency contracting officers to learn how to determine where, how, and for whom to include the appropriate DBA clauses.

As just one example, as recently as November 2006, a contractor had to point out to its military contracting officer that DBA was required and should be included as a cost in a service contract proposal for the US Army. In response, the contracting officer replied -- in writing -- that having spoken with "legal," DBA was "not required." Yet, the contract was for trucking, a service that is known, even to the general public, as carrying a high risk of injury in its region of operations. [7]

Training for DBA requirements: A Well-Kept Secret

Prior to December 2003, contractors and subcontractors hoping to learn about DBA and its application to Department of Defense contracts would find little information. In 2001, two years prior to Director Lee's attendance of the meeting, the Department of Labor (DOL), which administers Defense Base Act claims, had growing concerns of employers not carrying DBA. [8] To rectify the situation, the DOL's Office of Workers' Compensation Programs (OWCP)'s initiated seminars domestically [9] "to inform employers about the obligation to insure their workers and about the severe costs for not doing so." Since this was before the Iraq and Afghanistan conflicts, at that time, there was no mention of seminars for overseas contractors. The OWCP was most concerned about employers, predominately in Florida, with maritime workers as their employees.

Web pages from the Department of Labor were light on DBA information.10 On the Defense Base Act (DBA) Information page, [11] there was one link to the DLHWC (Longshore) homepage for more detail on "periodic seminars and workshops for industry groups."

Defense Base Act Seminars and Workshops

The OWCP National Office and district offices hold periodic seminars and workshops for industry groups as the need arises, or upon request. For information on upcoming events, check the official Longshore website.

Indeed, the first known DBA workshop would not be announced until November 14, 2003 [12] and scheduled for December 15, 2003, the day after Ultra Services civilian contractor Ryan Manelick was killed in Iraq. The announcement read:
Due to overwhelming demand, the Department of Labor, Office of Workers' Compensation Programs, will conduct a one day workshop on the Defense Base Act and the War Hazards Compensation Act. The date of the workshop is Monday, December 15, 2003. [13]
Unfortunately, there appeared to be no such seminars or workshops scheduled for contractors in Afghanistan and Iraq. Unless they were in the United States, overseas contractors who didn't know to secure DBA insurance or its equivalent, they wouldn't learn about it through Department of Labor seminars and workshops.

And, if the civilian contractors working in Iraq looked to the Coalition Provisional Authority (CPA) for information and training on DBA, they certainly wouldn't find much help. Of four documents available online through the CPA, two were dated June 11, 2004 -- 17 days before the CPA handed over sovereignty to the Iraqi people. Of the remaining two, the most extensive, from insurance company Rutherfoord, had a creation date of November 20, 2003 -- eight months after Coalition forces had moved into the region. [14] The last and earliest of the four, from American International Group Inc (AIG), with a May 16, 2003 creation date, contained only the following on DBA:
Defense Base Act (DBA) - AIG's member companies have been in the business of writing coverage in response to the DBA for many years. The Act was passed during World War II to provide compensation for disability or death to personnel employed at American military, air and naval bases outside the United States. The Act has evolved to cover contracts and subcontracts approved and financed by any independent establishment or agency of the United States ... Upon adequate lifting of sanctions, we plan to have employees on the ground in Iraq. [15]
Obviously, overseas contractors weren't going to learn about DBA from the CPA.

In September 2003, the US Army issued a new guidebook, Army Contractors Accompanying the Force (CAF). [16] which included two pages on the necessity of Defense Base Act coverage. Acquisition personnel knew contractors may not be aware of the DBA, as pointed out within the guidebook:
Pursuing benefits and remedies under these laws is the responsibility of the contractor employee and/or contractor. Since they may be unaware of this assistance, however, contracting personnel should inform the contractor of these laws if the situation arises. [17]
The contractor is ultimately responsible.

Insurance in some circumstances is available under the Defense Base Act and Longshoreman's and Harbor Workers Compensation Act administered by the Department of Labor, and the War Hazards Act. It is the contractor's or employee's responsibility to pursue possible benefits under those Acts. [18]

Eventually, in 2005, two years after the start of the Iraq war, the Defense Contract Management Agency at dcma.mil, which provides Contingency Contract Administration Services,19 published an article by Michael Dudley, Contractors on the Battlefield: Part III20 that summarized Chvotkin's 2003 PowerPoint presentation.

Congress Jumps In

Throughout the Iraq war, there continues to be problems with DBA implementation. Over 100 members of Congress requested reviews related to Iraq and DBA, and finally, in April 2005, the Government Accountability Office (GAO) reported that a review of costs and implementation was needed:
Defense Base Act Insurance: Review Needed of Cost and Implementation Issues [21]

This report explains DBA requirements; discusses DBA insurance rates, which are higher for DOD than for other agencies; identifies challenges and concerns that federal agencies face when implementing DBA; and suggests that Congress consider requiring that the Director of the Office of Management and Budget (OMB) determine, in coordination with DOD, the Departments of Labor and State, and the U.S. Agency for International Development, what actions should be taken to address issues that came to light during our review.
In response, the Department of Defense (DOD) provided details of a new 1-year pilot program for DBA insurance for the US Army Corps of Engineers, a decision based soley on the escalating costs rather than on protection for contractors who are working in the war theatre, even as the Department of Defense continued to replace its military personnel with private sector civilians.

DOD completed a congressionally directed study in 1996 on the feasibility and desirability of initiating a single-insurer program. While DOD concluded at that time that such a program would not lead to cost savings, the DBA insurance rates defense contractors are now paying have led to concerns among DOD officials over the cost of DBA insurance. To address these concerns, DOD, through the U.S. Army Corps of Engineers, issued a solicitation on March 7, 2005, for a 1-year pilot contract to a single insurer for DBA insurance for all Army Corps of Engineers contractors performing work overseas. [22]

On December 1, 2005, the Department of Defense's U.S. Army Corps of Engineers (USACE) finally awarded CNA Financial Group the contract for the new Defense Base Act (DBA) pilot program. [23] As of December 2006, almost 4 years of war in the mid-east and, although during the same time period the USAID and State Department had had effective DBA coverage for its contractors, the Department of Defense has only just finished its pilot program.

If successful, the program could revolutionize consistent DBA implementation throughout the Armed Services for civilian contractors working overseas. For the eligible, but uninsured contractors who were kidnapped, injured or killed, the revolution comes much too late.

Contractors at Risk

Four years. Two wars. Two countries. Two contingency operations. Hundreds of billions of dollars in contracts. Tens of thousands of civilian contractors. Thousands of injuries. Hundreds of deaths.

Why was the Department of Defense so inept implementing the Defense Base Act --placing contractors, and their families, at risk? The Government Accountability Office's June 2006 report Contract Management: DOD Vulnerabilities to Contracting Fraud, Waste, and Abuse, [24] may reveal the answer:
DOD's tone at the top allows a certain level of vulnerability to enter into the acquisition process. Senior acquisition officials ultimately shape the environment that midlevel and frontline acquisition personnel operate within, and it is that tone that clearly identifies and emphasizes the values deemed acceptable within the acquisition function. [...] DOD officials told us that, in recent years, the tone set in DOD was one of streamlining acquisitions to get results as fast as possible. While this is a desired outcome of the acquisition process, the acquisitions should still be carried out within prescribed policies and practices.
As the Deputy Secretary of the Army for Policy and Procurement prepares two new guidebooks for contingency contracting: The Army Guidebook for OCONUS Contingency Contracting and CONUS Guide for Supporting Emergencies within the United States and Supporting Overseas Contingencies from CONUS Locations, it is imperative that both include clear guidance on the implementation of the Defense Base Act.

For the families of contractors such as Kirk von Ackermann and Ryan Manelick the Manuals come much too late.

ePluribus Media Contributors: rba, newton snookers, cho, intranets, steven reich, wanderindiana, standingup, roxy

Side Bars Part I & II

Defense Base Act
The Defense Base Act provides disability compensation, medical treatment, and vocational rehabilitation to workers injured at work and death benefits to survivors when the worker is killed on the job. You need not be a U.S. citizen or a U.S. resident to obtain these benefits. [SB1] Source: Department of Labor
Contingency Operations
A military operation that is designated by the Secretary of Defense as an operation in which members of the armed forces are or may become involved in military actions, operations, or hostilities against an enemy of the United States or against an opposing militaryforce; or results in the call or order to, or retention on, active duty of members of the uniformed services [...] or any other provision of law during a war or during a national emergency declared by the President or Congress. [SB2] Source: US Code
Contingency Contracting
Contingency contracting is direct contracting support to tactical and operational forces engaged in the full spectrum of armed conflict and military operations (both domestic and overseas), including war, other military operations, and disaster or emergency relief. [SB3] Source: US Army Standard Procurement System
Federal Aquisition Regulation
FAR 28.305 [SB4] Overseas workers' compensation and war-hazard insurance.

FAR 28.310 [SB5] Contract clause for work on a Government installation.
For more information on FARS, please see the endnote section.

References

Please email me if you need assistance locating original source material cited in the references.

Endnotes - Part I

1 http://www.gao.gov/htext/d05280r.html -- see notes on 1996 review, “DOD concluded at that time that such a program would not lead to cost savings

2 http://www.gao.gov/htext/d05280r.html; The title of one section is “Large Numbers of Contractors in Iraq Have Led to Concerns over the Cost of DBA Insurance”

3 Ibid. http://www.gao.gov/htext/d05280r.html

4 FAR 52.228-3 Workers Compensation Insurance (Defense Base Act)

5 Americans die in security contractor copter crash, USA Today, USA Today Staff and Wire Reports, AP, January 23, 2007
According to a Guardian article, http://www.guardian.co.uk/worldlatest/story/0,,-6436602,00.html, The AP had to file a Freedom of Information Act request to obtain figures on pre-2006 civilian deaths and injuries from the Labor Department.
ePluribus Media writer Ilona Meagher also reports on the secrecy of the Department of Labor at http://scoop.epluribusmedia.org/story/2007/2/24/123023/888

6 From this page on meeting notes: http://www.acq.osd.mil/dpap_archive/daec/index.htm
List of attendees: http://www.acq.osd.mil/dpap_archive/Docs/DAEC/DAECnotesFrom031803.doc

7 Inclusion of Defense Base Act Clause in DoD Overseas Contracts, 08 Dec 2003

8 Blog post from Missing in Iraq by Megan von Ackermann (aka “For Kirk”), August 18, 2006

9 Email correspondence with Megan von Ackermann

10 Email from Megan von Ackermann to Susie Dow Auguest 22, 2006 5:55 AM

11 Fund to help wife of Iraq kidnap victim by AP, January 12, 2007

12 Authorization to Utilize Contingency Operations Contracting Procedures, THE UNDER SECRETARY OF DEFENSE, E.C. Aldridge, Jr., October 9, 2001

13 MEMORANDUM FOR ALMAJCOM/FOA/DRU (CONTRACTING), Emergency Acquisitions in Direct Support of U.S. or Allied Forces Deployed in Military Contingency Operations during Operation Iraqi Freedom, CHARLIE E. WILLIAMS, JR., March 21, 2003

14 FAR 2.101 Definitions: "Contingency operation" (10 U.S.C. 101(a)(13)) means a military operation that: (1) Is designated by the Secretary of Defense as an operation in which members of the armed forces are or may become involved in military actions, operations, or hostilities against an enemy of the United States or against an opposing military force; or (2) Results in the call or order to, or retention on, active duty of members of the uniformed services under section 688, 12301(a), 12302, 12304, 12305, or 12406 of 10 U.S.C., Chapter 15 of 10 U.S.C, or any other provision of law during a war or during a national emergency declared by the President or Congress.

15 For the purposes of this article, contingency operations and contingency contracting refer to support of overseas US government agency missions on or near the battlefield as managed by the Pentagon.

16 Circular No. A-76 Performance of Commercial Activities, August 4, 1983, Revised 1999 & the Government shall not start or carry on any activity to provide a commercial product or service if the product or service can be procured more economically from a commercial source.

17 White House Office of Budget and Management, Robert A. Burton, Memorandum:Request Contracting Information on Contractors Operating in Iraq, May 16, 2006

18 Renae Merle, Census Counts 100,000 Contractors in Iraq Civilian Number, Duties Are Issues, Washington Post, Tuesday, December 5, 2006; Page D01

19 Is Force Protection For Contractor Personnel on the Battlefield Adequate? by Mr. Michael J. Dudley, DCMA, Spring Summer 2004 (I have reason to believe this article was intended to be published earlier – note footnote dates: May 2003)

20 Interview and follow up emails with Former US military contracting officer.

21 Iraq Reconstruction: Lessons Learned in Contracting and Procurement, Special Inspector General of Iraq Reconstruction, July 2006, p 14

22 Bechtel Benefits as Iraq Contractors Struggle to Get Insurance Bloomberg News, November 21, 2003

Iraq contractors' sky-high insurance costs hobble efforts (reprint of same article, slight variation) by Vernon Silver, Bloomberg News, November 27, 2003

23 IRAQ: Army and Insurer at Odds, by T. Christian Miller, The Los Angeles Times, June 13th, 2005

24 US: Defense Discovers Insurance Companies Charge Huge Fees for Contractors Overseas, by Elliot Blair Smith, USA Today, June 14th, 2005

25 Iraq contracts burden taxpayers, By Joseph Neff, McClatchy Newspapers, December 25, 2006

Sidebar I

SB1 U.S. Department of Labor, Working for U.S. Government Contractors Overseas, WHAT YOU SHOULD KNOW BEFORE YOU ARE INJURED

SB2 10 U.S. Code 101(a)(13)

SB3 Standard Procurement System, SPS & Contingency Contracting

Endnotes - Part II

1 The Department of Labor Benefits Review Board had previously determined in 1988 in Alan-Howard v. Todd Logistics, Inc., 21 BRBS 70, that "individuals who work on-site to facilitate the utilization of such goods "constituted a service and as a result employees of such supply contractors were covered by DBA.
See: The Defense Base Act -- A Growth Industry? by Kerry J. Anzalone, Counsel for Longshore, Office of Administrative Law Judges, U.S. Department of Labor, 2004

2Federal Acquisition Regulation(FAR)

3 email from Alan Chvotkin to Susie Dow Friday, July 07, 2006 5:11 PM

4 The vulnerable line of supply to US troops in Iraq By Patrick Lang, Christian Science Monitor, July 21, 2006
5 ARMY CONTRACTORS ACCOMPANYING THE FORCE(CAF), Guidebook, September 8, 2003 page 17 & 18 include information on DBA

6 Iraq Reconstruction: Lessons Learned in Contracting and Procurement, Special Inspector General of Iraq Reconstruction, July 2006, pp 112-113 Also see...

7 Army Federal Acquisition Regulation (AFARS) Manual No. 2 for Contingency Contracting released November 1997
Air Force Federal Acquisition Regulation Supplement (AFFARS)
APPENDIX CC Contingency Operational Contracting Support Program (COCSP), revised June 15, 2006,
Navy Contingency Contracting Handbook
Marine Corps Purchasing Procedures Manual Appendix B

8 ARMY CONTRACTORS ACCOMPANYING THE FORCE(CAF), Guidebook, September 8, 2003 page 18

9 ARMY CONTRACTORS ACCOMPANYING THE FORCE(CAF), Guidebook, September 8, 2003 page 17 & 18 include information on DBA

10 ARMY CONTRACTORS ACCOMPANYING THE FORCE(CAF), Guidebook, September 8, 2003 page 17 & 18 include information on DBA

11 Iraq Reconstruction: Lessons Learned in Contracting and Procurement, Special Inspector General of Iraq Reconstruction, July 2006, p 14

12 Total US and Coalition Troops in May 2003, The Iraq Index (PDF), May 30, 2006

13 Army to End Expansive, Exclusive Halliburton Deal, By Griff Witte, Washington Post, July 12, 2006

14 Army to End Expansive, Exclusive Halliburton Deal, By Griff Witte, Washington Post, July 12, 2006

15 Evidence Of Waste Of US Taxpayers' Dollars In Iraq Contracts Letter from Rep. Henry Waxman to Joshua Bolten, September 26, 2003

16 America's rebuilding of Iraq shuts out Iraqis by Kelly Hayes-Raitt, Santa Monica Daily Press, August 19, 2003

17 Bechtel's Outreach to Iraqi Subcontractors

18In a few instances, contractors from surrounding nations are able to obtain liability insurance. But more often, KBR requires DBA coverage.

19 Former US military contracting officer

20 Contract Management: DOD Vulnerabilities to Contracting Fraud, Waste, and Abuse, GAO-06-838R, p 8, Government Accountability Office, July 7, 2006

21Contract Management: DOD Vulnerabilities to Contracting Fraud, Waste, and Abuse, GAO-06-838R, Government Accountability Office, July 7, 2006, http://www.gao.gov/new.items/d06838r.pdf

Sidebar II

SB4 FAR 28.305

SB5 FAR 28.310 (2) (a)

Endnotes - Part III

1 Single Process Initiative (SPI) Executive Council and the Defense Systems Affordability Council

2 DAEC charter letter, March 14, 2002

3 Contractors on the Battlefield: Part III by Mr. Michael J. Dudley, U.S. Army Defense Leadership and Management Program Participant Fall 2004/Winter 2005 - page 3

4 A-76 Revisions, Testimony to US House of Representatives, Committee on Government Reform, by Stan Soloway, June 26, 2003, page 2 See menu: Policy Leadership > Outsourcing/A-76 > Testimony > A-76 Revisions -- 6/2003 (actual link to pdf not available)

5 email from Alan Chvotkin to Susie Dow Friday, July 07, 2006 5:11 PM

6 email from Alan Chvotkin to Susie Dow Friday, July 07, 2006 5:11 PM

7 email to Susie Dow -- source prefers to remain anonymous

8 as documented in the DOL's Office of Workers' Compensation Programs (OWCP)'s annual report.

9Office of Workers' Compensation Programs (OWCP), Annual Report to Congress FY 2001, page 28

10Internet Archive

11 Ibid Link shown to workshops and seminars

12 Ibid Announcement

13 Division of Longshore and Harbor Workers' Compensation

14 Rutherfoord The Assurance Company

15AIG Solutions for Iraq Reconstruction

16 ARMY CONTRACTORS ACCOMPANYING THE FORCE (CAF), Guidebook, September 8, 2003 page 18 -- ARMY CONTRACTORS

17 ACCOMPANYING THE FORCE (CAF), Guidebook, September 8, 2003 page 17 & 18 include information on DBA

18 ARMY CONTRACTORS ACCOMPANYING THE FORCE (CAF), Guidebook, September 8, 2003 page 17 & 18 include information on DBA

19 Contingency Contract Administration Services

20 Contractors on the Battlefield:Part III by Mr. Michael J. Dudley, DCMA Communicator, Fall 2004/Winter 2005

21United States Government Accountability Office Defense Base Act Insurance: Review Needed of Cost and Implementation Issues April 29, 2005

22 http://www.gao.gov/htext/d05280r.html

23 US Army Corps of Engineers Contracts with CNA for Defense Base Act Program, Global Risk Alert, AON, December 13, 2005

24 Contract Management: DOD Vulnerabilities to Contracting Fraud, Waste, and Abuse, GAO-06-838R, pp 6-7 Government Accountability Office, July 7, 2006

Friday, February 23, 2007

Death of a Contractor

Keep an eye out for the current issue of Rolling Stone magazine which features a new article by Daniel Halpern about Ultra Services. I understand the article centers around Ryan Manelick. Below is a photo of the online cover for February 21, 2007 but I haven't yet located the dead tree version on local news stands.

Rolling Stone

Update: The article is available online. Try to pick up the print version as it includes photos.
Death of a Contractor: Greed and Murder in Iraq's Lawless Desert (link expired) by Dan Halpern


Use this link:
Death of a Contractor - alternate link

Tuesday, January 16, 2007

Obituary for Kirk von Ackermann

Obituary
The Albuquerque Journal
January 14, 2007

VON ACKERMANN -- Kirk von Ackermann was killed October 9, 2003 while acting as a contractor in Iraq. Kirk served his country with distinction, first as a Russian linguist in the army, then as an intelligence officer in the air force. He earned numerous awards including Army, Air Force, and joint service commendation medals. Kirk was passionate about his family and devoted to them and to his many friends. He pursued many activities, and taught his children his personal philosophy: live life, don't watch it.

More...