Showing posts with label policies and procedures. Show all posts
Showing posts with label policies and procedures. Show all posts

Friday, July 06, 2012

7FAM1820 Revised

It appears that there is a new revision to the Foreign Affairs Manual. The circular on Hostage Taking and Kidnappings shows a revision date of June 29, 2012.

7 FAM 1820 HOSTAGE TAKING AND KIDNAPPINGS (PDF) 17 pages
U.S. Department of State
Foreign Affairs Manual
Volume 7 - Consular Affairs

I feel so cynical. The guidance was a complete failure when Kirk von Ackermann disappeared.

The Office of Casualty Assistance is the primary point of contact in the Department for assistance to families and victims in these cases.
They never even assigned a case officer.


Saturday, March 31, 2012

Defense Base Act

The Department of Labor Office of Workers' Compensation Programs now has sortable tables of their summaries of Defense Base Act claims, including one by Employer:

Defense Base Act Case Summary by Employer

The data below reflects the number of claims cases created under the DBA for the time period specified, sorted by Employer. [...] The columns show the different Case Types: NLT ( no lost time), LTO (lost time 3 days or less), LT4 (lost time 4 days or more), DEA (death), COP (salary continuation), OTH (other or unknown).
Employers with fewer than 7 claims are not listed. Therefor, Kirk von Ackermann and Ryan Manelick's employer, Ultra Services is not listed.

When I first started researching the Defense Base Act, there was a significant lack of information available - including basics like what the acronyms stood for. So it's nice to see the Department of Labor website is now much more easy to navigate and chock full of information.

One frustration - how many contractors and their families did not file timely Defense Base Act claims simply because they didn't know the law existed? Not just a hypothetical, it's definitely happened.

Defense Base Act Case Summary Reports
US Department of Labor
Office of Workers' Compensation Programs (OWCP)
Division of Longshore and Harbor Workers' Compensation (DLHWC)

Tuesday, February 22, 2011

Reading Room

What follows is a list of publicly available manuals, instructions, regulations, laws and policies applicable to overseas Americans who go missing while working under contract for US government agencies. If links go bad, use a search engine like google to find updated information about the publication you seek.

Legal Reference Material

The laws that govern missing persons, hostage affairs, etc.

National Security Act of 1947 
Establishes intelligence community support for missing persons. See Section 117 POW/MIA Analytic Capability. Also see 50 USC § 404L: United States Code, Title 50 - War and National Defense, Chapter 15 - National Security, Subchapter I - Coordination for National Security, 404L - POW Analytic Capability. The National Security Act of 1947 was last amended in 2007 by Public Law 110-53.

U.S. Code Title 10 § 1513
Legal definition of a missing person. United States Code, Title 10 - Armed Forces, Subtitle A - General Military Law, Part II - Personnel, Chapter 76 - Missing Persons.

Missing Persons Act
10 USC § 1501 - 1513 (A) policy, control, and oversight within the Department of Defense of the entire process for investigation and recovery related to missing persons (including matters related to search, rescue, escape, and evasion); and (B) coordination for the Department of Defense with other departments and agencies of the United States on all matters concerning missing persons.

Presumed Death under the Missing Persons Act
States laws govern how presumption of death is determined for a missing person. This is a critical phase in getting benefits in a prompt manner to surviving family members. Sample law for Rhode Island.

Defense Prisoner of War Missing Personnel (DPMO)
Provides policy oversight for the mission to recover captured, missing, or isolated personnel, usually military.

Workers Compensation for Overseas Workers

Information on the survivors benefits, including eligibility, etc. Benefits are administered by the Department of Labor.

Longshore and Harbor Workers Compensation Act (LHWCA)
LHWCA forms the basis for workers compensation for overseas workers.

Defense Base Act (DBA) also known as 42 USC § 1651
Defense Base Act extends LHWCA protections to overseas workers employed under contract to US government agencies. Benefits are payable if a casualty is not the result of hostile force(s). 

Workers Compensation Clauses for Overseas Performance (PDF)
Article on the application of FAR 52.228-3 and FAR 52.228-4 contract clauses.

War Hazards Compensation Act (WHCA) also known as 42 USC § 1701
Coverage under WHCA is automatically extended to anyone who has DBA. Benefits are payable if a casualty is the result of hostile force(s).

Regulations under WHCA - Employees Benefits
Title 20 Part 61- Claims for Compensation under the War Hazards Compensation Act, as Amended

Federal Employee Compensation Act (FECA)
WHCA benefits are paid directly from the FECA fund

Regulations under FECA
Title 20 Part 10 - Claims for Compensation under the Federal Employees' Compensation Act, as Amended

Dept of Labor DBA LHWCA page

Dept of Labor Compliance Page - FECA WHCA

Reports, Policies, and Manuals


General information and resources.

From the US Department of State:

Foreign Affairs Manual (FAM)

3 FAM 4100 Foreign Affairs Manual
US State Department Employee Responsibility and Conduct
Including 'Guidelines for Personnel Taken Hostage'

7 FAM 000 Foreign Affairs Manual
Consular Protection of US Nationals Abroad

From the US Department of Defense:

Defense Contingency Contracting Handbook

DA PAM 715–16
Contractor Deployment Guide. Procedures for contractor operations within the Department of the Army. Chapters 10 & 11 cover a variety of issues for hostages, including identification, aid, rights, etc. Department of the Army, February 27, 1998

AR 715-9
Contractors Accompanying the Force, November 29, 1999

Field Manual FM 3-100.21 (formerly FM 100-10-2)
Contractors on the Battlefield, Department of the Army, January 3, 2003. General overview of responsibilities includes brief passages and references on Personnel Recovery, Next of Kin Notification, etc.

Army Publishing Directorate
Everything you ever wanted to read in PDF format from the US Army but can't get access to without a password and login. Great way to double check titles and numbers. Also see:
Department of the Army Official Publishing sites
Lists other websites to find publications - alas, some with secure logins

Army Knowledge Online (AKO)
All Departmental Publications and Forms, including distribution-restricted Items

Army Home Page (AHP)
All Unrestricted Departmental Publications and Forms

U.S. Army Publishing Directorate (APD)
Administrative Departmental Publications and Forms (ARs, CIRs, PAMs, OFs, SFs, DD and DA Forms)

U.S. Army Materiel Command (AMC) Logistics Support Activity
Technical and Equipment Publications(TMs, TBs and SCs)

U.S. Army Training and Doctrine Command
Training and Doctrinal Publications (FMs, PBs, TCs and STPs)

U.S. Army Corps of Engineers
Training & Doctrinal, Technical & Equipment Publications with Engineering & Design Criteria (TMs and FMs)

The Surgeon General/Medical Command
Training & Doctrinal, Technical & Equipment Publications with Medical Content (TMs, FMs, and SB 8-75 Series Publications)

Department of Defense Forms
Just what it sounds like. Standard forms galore. See DD Form 1833 Isolated Personnel Report (ISOPREP)
Standard Forms and Casualty Reporting

Everything starts with a standardized form for information.

SIGACT
Significant Activity reports are typically the very first incident report generated in the field.

SPOT
Synchronized Predeployment and Operational Tracker (SPOT). Registration for contractors working overseas.

DCIPS
Defense Casualty Information Processing System. Electronic reporting system used to report and track casualties.

AF CARES
Armed Forces Casualty Assistance Readiness Enhancement System, March 2007. Electronic system for tracking the progress of a casualty through the system. General order of flow: Initial Contact - Initial Visit - Interment - Disposition of Benefits - Disposition of Personal Effects - Disposition of Investigative Reports - Case After Action Report

Form DS-2060
Report of the Death of an American Citizen Abroad

Casualty Matters

AI Part 52.2 01  (DOC)
Basic form to provide to the Contracting Officer for reporting a hostage. See Part 52, page 31, Hostage Reporting instruction, Joint Contracting Command,  May 2007

AR 15-6 (PDF)
Commanders responsibilities in initiating an investigation of a casualty. Procedures for Investigating Officers and Boards of Officers, Department of the Army, October 2, 2006

AR 600-8-1 Army Casualty Program
Chapter 13 - Procedures for Casualties Involving Missing Persons (Non-Hostile and Hostile)

FM-27-1
Legal Guide for Commanders including authority for an AR-15 investigation

DODI 1300.18 Casualty Matters, Policies
Personnel Casualty Matters, Policies, and Procedures

DODD 1300.22
Mortuary Affairs, November 21, 2003 Disposition of remains, personal effects, etc.

DODD 2310.2
General policy for Personnel Recovery, Department of Defense, December 22, 2000

DODI 2310.4
Repatriation of Prisoners of War, Hostages, Peacetime Government Detainees and Other Missing or Isolated Personnel

DODI 2310.05 Missing Persons
Accounting for Missing Persons – Boards of Inquiry, Department of Defense, March 14, 2008

DODI 3001.03
Responsibility for disposition of human remains. Accounting for Personnel Lost in Past Conflicts – The Armed Forces Identification Review Board (AFIRB), March 14, 2008

Annual Reports of Missing Persons

Military Casualty and Loss

DOS Country Reports on Terrorism
Annual reports on terrorism incidents (includes kidnappings) of American citizens, listed by year since 2000. Country Reports on Terrorism, US Department of State

NCTC Reports on Terrorism
Annual reports of incidents. National Counterterrorism Center

WITS
Searchable database of worlwide terrorism incidents. Search kidnapping. Worldwide Incidents Tracking System, National Counterterrorism Center

Abbreviations

AI Acquisition Instruction 
AR Army Regulation
DODI Department of Defense Instruction
DODD Department of Defense Directive
FAM Foreign Affairs Manual (State Department)
FM Field Manual

Friday, August 13, 2010

Joint Personnel Recovery Agency

The Defense Business Board has advised Secretary Gates that the Department of Defense eliminate Joint Forces Command.


I'm wondering what happens to the Joint Personnel Recovery Agency which is a subordinate of the Joint Forces Command at Fort Belvoir. The idea that it might go over to Special Operations Command doesn't inspire confidence. (See: Lynch, Jessica)

References

By Andrew Tilghman, Army Times, August 11, 2010

By Marc Ambinder, The Atlantic, August 9, 2010


Friday, March 05, 2010

Foreign Affairs Manual - hostage and missing

The US Department of State Foreign Affairs Manual (FAM) includes sections on hostages and missing persons that I thought were worth including here.

U.S. Department of State

Foreign Affairs Manual

I'm of the opinion that the US government should have a dedicated office for hostage affairs/missing persons of US citizens abroad. It would have a core of permanent staff in addition to representatives from US government agencies such as the FBI, Department of State, Department of Defense (POW-MIA, Casualty Affairs, Criminal Investigation Division, etc). One of the things the office should be responsible for is coordinating regulations and reporting requirements by publishing an annual manual.

Just a thought.

Thursday, March 26, 2009

Contractor Deployment Guide

I was looking for more background information on general identification requirements for contractors working overseas when I stumbled upon this Pamphlet. Fascinating reading. As far as I can tell, this is the most recent version. It really is a must read for anyone going to work overseas.

Ed. note for June 14, 2010: please use this new link DA PAM 715-16

Contractor Deployment Guide
Pamphlet 715–16
Department of the Army
27 February 1998

DA PAM 715–16
Contractor Deployment Guide

This new Department of the Army pamphlet provides procedures for contractor operations within the Department of the Army.
The Pamphlet includes a short section on Hostages (see page 6), which contains some information that I don't recall reading before.
Chapter 11

11–1. Hostage aid

a. Hostages

When and where the Secretary of State, in consultation with the Secretary of Labor, declares that U.S. citizens or resident aliens of the United States rendering service overseas have been placed in a “captive” status as a result of a “hostile action” against the U.S. government, a wide range of benefits accrue to that person and that
person’s dependents. For example, captives can continue to receive their full pay. Captives can claim some, but not all, of the benefits of the Soldiers’ and Sailors’ Civil Relief Act. A person designated as a captive or his/her family members are eligible for physical and mental health care benefits at U.S. government expense. A spouse
or unmarried dependent of a designated captive is eligible for certain education benefits. If a designated captive ultimately dies from hostile action caused by his/her relationship to the U.S. government, the Secretary of State may provide death benefits to the captive’s survivors.

b. Any person possibly affected (e.g., family members and dependents) may petition the Secretary of State to make the declaration of coverage. Pursuing benefits and remedies under these laws is up to the contractor employee and/or the employee’s family members, dependents or employer.
As far as identification...no surprises. Seems basic. But what exists on paper and what's done in reality are two different things. So, the question that really needs answering is: what identification were Ultra Services personnel expected to carry back in Iraq in 2003?

Identification mentioned in the Contractor Deployment Guide:
Passport
Visas - as needed
Invitational Travel Orders
Uniformed Services Identifications and Privilege Card (DD Form 1173)
Geneva Conventions Identity Card (DD Form 489)
Personal Identification ('dog tags')
Local In-theater Identification (Baghdad International Airport, etc)
Authorization to carry a weapon (from Theater Commander or State Department)
Record of Emergency Data Card (DD Form 93)
Company Id
Drivers license
Record of Immunizations
Medical information ('medical tags')
Not mentioned:
Common Access Card (DD Form 1172-2)
Looking over the list above, what exactly was the green id card issued to Kirk von Ackermann featured in the Rolling Stone article? Was it still valid? And what happened to all of the other identification he should have been carrying?

Always questions.

Related

Base Access
March 20, 2009

Friday, February 06, 2009

POW/MIA - National Security Act of 1947


I'm spending my free time at the local law library trying - more or less hopelessly - to do research for the NSA appeal. I stumbled on a bit related to POW/MIA in one of the books I was reading today on National Security Intelligence.

Makes me wonder, if information is unintentionally acquired prior to the disappearance of someone, but it's later determined that the information might be useful in determining what happened, under whose authority does the information then fall? It's unclear, especially since it wasn't originally collected for investigative purposes.


But that's a separate side issue and unrelated to the appeal at hand. At least, not at this point.

National Security Act of 1947 as amended. Unclassified.
POW/MIA ANALYTIC CAPABILITY

SEC. 117. (a) REQUIREMENT - (1)The Director of Central Intelligence shall, in consultation with the Secretary of Defense, establish and maintain in the intelligence community an analytic capability with responsibility for intelligence in support of the activities of the United States relating to individuals who, after December 31, 1990, are unaccounted for United States personnel.

(2) The analytic capability maintained under paragraph (1) shall be known as the 'POW/MIA analytic capabiltity of the intelligence community'.

(b) UNACCOUNTED FOR UNITED STATES PERSONNEL - In this section, the term 'unaccounted for United States personnel' means the following:

(1) Any missing person (as that term is defined in section 1513(1) of title 10, United States Code).

(2) Any United States national who was killed while engaged in activities on behalf of the United states and whose remains have not been repatriated to the United States.
What exactly is a 'missing person'? To find out, it's necessary to visit the United States Code, Title 10 - Armed Forces, Subtitle A - General Military Law, Part II - Personnel, Chapter 76 - Missing Persons. I've covered this before, but it never hurts to take a look at the information again.
U.S. Code Title 10 § 1513

In this chapter:
(1) The term “missing person” means—
(A) a member of the armed forces on active duty who is in a missing status; or
(B) a civilian employee of the Department of Defense or an employee of a contractor of the Department of Defense who serves in direct support of, or accompanies, the armed forces in the field under orders and who is in a missing status.
Such term includes an unaccounted for person described in section 1509 (b) of this title who is required by section 1509 (a)(1) of this title to be considered a missing person.
(2) The term “missing status” means the status of a missing person who is determined to be absent in a category of any of the following:
(A) Missing.
(B) Missing in action.
(C) Interned in a foreign country.
(D) Captured.
(E) Beleaguered.
(F) Besieged.
(G) Detained in a foreign country against that person’s will.

(3) The term “accounted for”, with respect to a person in a missing status, means that—
(A) the person is returned to United States control alive;
(B) the remains of the person are recovered and, if not identifiable through visual means as those of the missing person, are identified as those of the missing person by a practitioner of an appropriate forensic science; or
(C) credible evidence exists to support another determination of the person’s status.
Additional Reading - just for fun:

National Security Investigations and Prosecutions
By David Kris, J. Douglas Wilson, West Thomson, 2007

Tuesday, December 23, 2008

Defense Base Act vs War Hazards Compensation Act





This post looks at the significance of a non-hostile event vs a hostile event in determining how a casualty will be handled under the Defense Base Act. Any errors are strictly my own and, as always, corrections are very much welcome.

Casualty

Under United States policies and laws, a casualty is composed of a) TYPE, b) STATUS, and c) CATEGORY.

a) TYPE:
(1) non-hostile or
(2) hostile

b) STATUS:
(1) deceased or
(2) duty status – whereabouts unknown (DUSTWUN) for military, or excused absence – whereabouts unknown (EAWUN) for civilians or
(3) missing or
(4) very seriously ill or injured (VSI) or
(5) seriously ill or injured (SI) or
(6) not seriously ill or injured (NSI) or
(7) Returned to Military Control (RMC) or
(8) Pending - for preliminary reports only

At the DoD Component’s discretion, an additional casualty Status may be used - generally used for illnesses that require hospitalization:

(9) Special Patient (SPECPAT) or
(10) Special Category (SPECAT)
c) CATEGORY:
There are a wide variety of casualty categories depending on the status. For example, categories used for 'Status - Missing' are - Beleaguered, Besieged, Captured, Detained, Interned, Missing, Missing in Action (MIA), and again, Pending is for preliminary reports only.
POW is not a casualty status for reporting purposes, rather Status and Category are "Missing-Captured."

The key to understanding the difference between the Defense Base Act and the War Hazards Compensation Act lies in the TYPE of casualty: non-hostile vs. hostile

Laws

The Defense Base Act is an extension of the Longshore and Harbor Workers' Compensation Act - the equivalent of worker's compensation for Americans working overseas for US government agencies.

The Defense Base Act is, in effect, a group of laws: Defense Base Act (1941), War Hazards Compensation Act (1942), Mutual Security Act (1958), and in part the Dayton Peace Accords (1995). In addition, the Federal Employees Compensation Act (1916) applies should an incident qualify under the War Hazards Compensation Act.

Because coverage under the Defense Base Act is a legal requirement, premiums paid by a contractor are a reimbursable expense under the terms of the contract. Contracts should carry the relevant contract clauses (see: PDF - Memorandum: Inclusion of Defense Base Act Clause in DoD Overseas Contracts 08 Dec 2003).

Defense Base Act vs War Hazards Compensation Act

Incidents are divided into two types: NON-HOSTILE and HOSTILE. Casualties the result of a Non-Hostile event are covered under the Defense Base Act. Casualties the result of a Hostile event, however, are covered under the War Hazards Compensation Act.

The following graphic is an attempt to help clarify the difference between the Defense Base Act and the War Hazards Compensation Act.

right click to open in a new window

Claims arising from incidents that are the result of non-hostile action generally are reported under the Defense Base Act and as such are 15-40% reimbursable. [see note below] Claims arising from incidents that are the result of hostile action are paid under the War Hazards Compensation Act and subsequently the Federal Employees Compensation Act and consequently are 100% reimbursable.

Example:

John Brown sprains his ankle getting out of his truck in Iraq. Even though he's working in a war zone, the type of incident is non-hostile. Claims will be covered under the Defense Base Act. The claims will be reimbursed at 15-40%.

Bob Jones sprains his ankle getting out of his truck in Iraq as he attempts to retreat from mortar fire. Even though the injury is physically and medically identical to that of his co-worker, John Brown, the incident is the result of hostile action. Claims will be covered under the War Hazards Compensation Act and subsequently the Federal Employees Compensation Act. The claims will be reimbursed at 100%.

Previous related posts

Casualty Status of Missing

Iraq Contractors and The Missing Persons Act


Note (added July 19, 2009)

Figures were provided by Department of Labor personnel during several presentations at the Defense Base Act conference in Washington DC in the fall of 2008. The vast majority of claims filed under the Defense Base Act are for injuries. Expense to be reimbursed is usually for Loss Time - that is, the amount of time that an employee is unable to work due to the injury - but only if more than 4 days. The first 4 days are expected to be paid as sick days by an employer, and are not reimbursed.

As a result, the bulk of the claims - which again are for injuries - generally end up being reimbursed at 15-40%. In more concrete terms, the vast majority of injuries result in a time loss of 5 to 7 days of which 1 to 3 days, roughly 15-40%, will be reimbursed.

The Department of Labor breaks down Loss Time as follows:
NLT - No Loss Time - No lost time and no medical expense
NL0 - No Loss Zero - No lost time and no medical expense * but may result in a later claim, Questionable No Lost Time Injury**
NL4 - No Loss Four - No lost time, medical expense incurred or expected *
DEA - Death
COP - Continuation of regular pay*
OTH - Other
* found on a DOL form for Federal Employee's Notice of Traumatic Injury and Claim for Continuation of Pay/Compensation
** CHAPTER 1-300 - INDEX AND CONTROL at the Department of Labor website

Saturday, July 26, 2008

Casualty Status of Missing

This post expands on the topic of casualty status as relates to missing personnel. Right about now, you probably want me to stop quoting Department of Defense Publications. I kinda think this one is important and suggest reading through to the end.

Each casualty is composed of a) Type, b) Status, and c) Category.

DoD Instruction 1300.18 - "Personnel Casualty Matters, Policies, and Procedures"
From the Under Secretary of Defense for Personnel and Readiness, January 8, 2008
- replacing DoD Instruction 1300.18, “Military Personnel Casualty Matters, Policies, and Procedures,” December 18, 2000 (hereby canceled)

4 CASUALTY INFORMATION (page 38)

Use the chart below when completing blocks 4a (TYPE), 4b (STATUS), and 4c (CATEGORY). Only these combinations are authorized. Definitions are contained in Enclosure 2. The word Pending can only be used on Initial or Interim reports.
Taken from the Section E.2 Definitions (page 26):

Type
E2.32. Hostile Casualty. A person who is the victim of a terrorist activity or who becomes a casualty "in action." "In action" characterizes the casualty as having been the direct result of hostile action, sustained in combat or relating thereto, or sustained going to or returning from a combat mission provided that the occurrence was directly related to hostile action. Included are persons killed or wounded mistakenly or accidentally by friendly fire directed at a hostile force or what is thought to be a hostile force. However, not to be considered as sustained in action and not to be interpreted as hostile casualties are injuries or death due to the elements, self-inflicted wounds, combat fatigue, and except in unusual cases, wounds or death inflicted by a friendly force while the individual is in an AWOL, deserter, or dropped-from-rolls status or is voluntarily absent without authority from a place of duty.

E2.38. Non-hostile Casualty. A person who becomes a casualty due to circumstances not directly attributable to hostile action or terrorist activity. Casualties due to the elements, self-inflicted wounds, and combat fatigue are non-hostile casualties.

[Again, "Pending" can only be used on Initial or Interim reports and from what I can glean, it pretty much means deceased...]
Status
E2.11 (page 27)

There are six casualty statuses: (1) deceased; (2) duty status – whereabouts unknown (DUSTWUN) for military, or excused absence – whereabouts unknown (EAWUN) for civilians; (3) missing; (4) very seriously ill or injured (VSI); (5) seriously ill or injured (SI); and (6) not seriously ill or injured (NSI). At the DoD Component’s discretion, an additional casualty status of Special Patient (SPECPAT) or Special Category (SPECAT) may be used [both are injury or illness related].

E2.20. Deceased. A casualty status applicable to a person who is either known to have died, determined to have died on the basis of conclusive evidence, or declared to be dead on the basis of a presumptive finding of death. The recovery of remains is not a prerequisite to determining or declaring a person deceased.

E2.26. Duty Status - Whereabouts Unknown (DUSTWUN). A transitory casualty status, applicable only to military personnel, that is used when the responsible commander suspects the member may be a casualty, whose absence is involuntary, but does not feel sufficient evidence currently exists to make a determination of missing or deceased.

E2.28. Excused Absence – Whereabouts Unknown (EAWUN). An administrative status, applicable only to civilian personnel, that is used when the responsible commander suspects the employee may be a casualty, whose absence is involuntary, but does not feel sufficient evidence currently exists to make a determination of missing or deceased.

E2.37. Missing. A casualty status for which the United States Code provides statutory guidance concerning missing members of the Military Services. Excluded are personnel who are in an AWOL, deserter, or dropped-from-rolls status. [see categories below]

E2.54. Very Seriously Ill or Injured (VSI). The casualty status of a person whose illness or injury is such that medical authority declares it more likely than not that death will occur within 72 hours.

E2.50. Seriously Ill or Injured (SI). The casualty status of a person whose illness or injury requires medical attention, and medical authority declares that death is possible, but not likely within 72 hours, and/or the severity is such that it is permanent and life-altering.

E2.39. Not Seriously Ill or Injured (NSI). The casualty status of a person whose illness or injury requires medical attention, may or may not require hospitalization, and medical authority classifies as less severe than SI.

E2.49. Returned to Military Control (RMC). The status of a person whose casualty status of DUSTWUN or missing has been changed due to the person's return or recovery by U.S. military authority.

[Again, "Pending" can only be used on Initial or Interim reports.]

Note

E2.46. Prisoner of War (POW). POW is not a casualty status for reporting purposes. For reporting purposes, the casualty status and category would be missing-captured.
Category

A person declared missing is categorized as follows:
E2.37.1. Beleaguered. The casualty is a member of an organized element that has been surrounded by a hostile force to prevent escape of its members.

E2.37.2. Besieged. The casualty is a member of an organized element that has been surrounded by a hostile force, compelling it to surrender.

E2.37.3. Captured. The casualty has been seized as the result of action of an unfriendly military or paramilitary force in a foreign country. See also Prisoner of War (POW).

E2.37.4. Detained. The casualty is prevented from proceeding or is restrained in custody for alleged violation of international law or other reason claimed by the government or group under which the person is being held.

E2.37.5. Interned. The casualty is definitely known to have been taken into custody of a nonbelligerent foreign power as the result of and for reasons arising out of any armed conflict in which the Armed Forces of the United States are engaged.

E2.37.6. Missing. The casualty is not present at his or her duty location due to apparent involuntary reasons and whose location is unknown.

E2.37.7. Missing in Action (MIA). The casualty is a hostile casualty, other than the victim of a terrorist activity, who is not present at his or her duty location due to apparent involuntary reasons and whose location is unknown.

[Again, "Pending" can only be used on Initial or Interim reports.]
Missing Missing is Missing

If you managed to work your way through the various definitions and read the above carefully, many small details probably started to jump out at you. Keep in mind, the whole point of DoDI 1300.18 is it "provides uniform official casualty terms and definitions."

Mission so not accomplished.

One

There is no written definition for one line shown in the Casualty Information Chart a) Type: Hostile b) Status: Missing and c) Category: Terrorist. In theory, this combination should have been included as a category under definition E2.37.8. But, it's not there. Further along, there is a definition for "Terrorism"...but I'm specifically interested in "Terrorist" as used to categorize Missing Status.
E2.52. Terrorism. The calculated use of unlawful violence or threat of unlawful violence to inculcate fear; intended to coerce or to intimidate governments or societies in the pursuit of goals that are generally political, religious, or ideological.
Two

There is no line in the Casualty Information Chart for a) Type: Hostile b) Status: Missing and c) Category: Missing although this combination is included in the definition E2.37.6.

Missing-Missing (E2.37.6) is quite literally missing from the Casualty Information Chart. Instructions are very clear - "Only these combinations are authorized." With a little help from Photoshop, the corrected chart with the line inserted is shown below:

Three

If "RET MIL CONTROL" or Returned to Military Control is shown under "4b) Status" on the Casualty Information Chart, why isn't it included in the list at E.11 on page 27 which specifically states that there are "six casualty statuses?" Dare I mention, the acronym for Returned to Military Control is RMC not RET MIL CONTROL under "Definition."

Does the chart over rule the definition? Does the definition overrule the chart? Which instruction is correct? And what kind of impact does all of this have on casualty reporting?

More...

There's also an issue with the Casualty Feeder Card (DA Form 1156) used by Commanders that I referenced in another post just the other day, Iraq, Contractors and The Missing Persons Act. The options for "Status" on DA Form 1156 do not match those in the definitions or in the Casualty Information Chart of DoDI 1300.18. Statuses shown on the DA Form 1156 are: (1) deceased; (2) DUSTWUN (3) VSI (4) SI (5) NSI and (6) Pending. No "Missing." And as there is no "Missing," I'm also wondering why DUSTWUN isn't at least listed as DUST/EA-WUN since the form applies to both military and civilian personnel.

I'd love to drop an email to the Office of the Under Secretary for Personnel and Readiness to point out the conflicts between chart and definitions. But, they don't have any contact information on their website. So, I'm off to fill out the generic contact form at DefenseLink.

Maybe I should just type up a new Excel Table for the DoD.

Thursday, July 24, 2008

Iraq Contractors and The Missing Persons Act

Editor's note: the following is based on information available at the time of writing in 2008 and may not accurately reflect procedures and policies in place in the fall of 2003.

As an American civilian contractor working in support of US Army operations in Iraq, Kirk von Ackermann should have been covered under legislation commonly known as the Missing Persons Act. His family should have received notification that counsel was appointed to represent his interests within 45 days of his disappearance. By Day 100, an unclassified summary report should have been provided to von Ackermann's family. At the one year anniversary, Day 365, they should have received notification of the meeting of a Board of Inquiry. If that board reached no definitive conclusion as to his whereabouts, additional inquiries should have been held which the family would have had the right to attend. The von Ackermann family could have passed concerns to the counsel as well as provide information and/or objections to any recommendations by the Board of Inquiry.

But, that's not what happened....something went awry after the Battalion Commander in Tikrit first reported von Ackermann missing.

This post and the following chart are an attempt to recreate the flow of reports and information in 2003 and 2004.


The Missing Persons Act

The Missing Persons Act was first established in 1942, the same year as the Defense Base Act. At the time, the primary purpose of the legislation was to alleviate financial hardship suffered by the dependents of servicemen reported as missing [ref]. Over the years, The Missing Persons Act has been amended.

§ 1501. System for accounting for missing persons

(1) The Secretary of Defense shall establish within the Office of the Secretary of Defense an office to have responsibility for Department of Defense policy relating to missing persons. Subject to the authority, direction, and control of the Secretary of Defense, the responsibilities of the office shall include­­
(A) policy, control, and oversight within the Department of Defense of the entire process for investigation and recovery related to missing persons (including matters related to search, rescue, escape, and evasion); and

(B) coordination for the Department of Defense with other departments and agencies of the United States on all matters concerning missing persons.
In 1996, a new provision was added allowing the Department of Defense to designate a missing person as deceased without proof. In addition, the new changes allow government agencies to withhold information on missing persons without penalty. [ref] The 1996 amendments were controversial with some veterans groups who, unsuccessfully, attempted to have them removed.

Reporting

The status of 'missing,' both hostile and non-hostile, is considered a casualty. The Army Casualty Program publication Army Regulation (AR) 600-8-1 outlines the general steps and time frame for reporting procedures for missing persons.
AR 600-8-1
Chapter 13
Procedures for Casualties Involving Missing Persons (Non-Hostile and Hostile)
May 15, 2007
Casualty Assistance

Casualty Assistance Centers (CACs) noted in the above chart "... accomplish the administrative functions of the casualty operations, mortuary affairs, and line of duty programs, the key subcomponents of the Army Casualty Program. They account for, report, and document all casualties. The Casualty and Memorial Affairs Operations Center (CMAOC), U.S. Army Human Resources Command (AHRC-PEZ), has technical supervision over CACs worldwide. "

A general overview of procedural responsibility of CAC's can be found at the DoD Instruction 1300.18 - "Personnel Casualty Matters, Policies, and Procedures" - which describes the responsibilities of the Casualty Assistance Officer.

6.1.4. Casualty Assistance

6.1.4.1. DUSTWUN, EAWUN, Missing, or Deceased Cases. In all cases involving DUSTWUN, EAWUN, missing, or deceased casualties, the DoD Component concerned shall appoint a casualty assistance officer who will initiate contact with the [primary next of kin] PNOK within 24 hours following initial notification. Within the guidelines established by each DoD Component, the casualty assistance officer may be the notification officer. The casualty assistance officer, to the extent the PNOK desires, shall provide guidance and assistance for such matters as pay, allowances and benefits, veteran benefits, social security benefits, and income tax refunds or exclusions whenever section 692 of title 26, U.S.C. (Reference (r)) applies to the particular case. Assistance to civilian personnel will be coordinated through the designated civilian personnel office or civilian benefits center. The casualty assistance officer shall provide points of contact or information regarding autopsy reports, all known reports of inquiry or investigations, as applicable, and other governmental or non-DoD agencies that may be involved in a particular case. The casualty assistance officer shall maintain contact with the PNOK to keep them informed until all matters relating to the case have been answered and all entitlements and benefits are received.
I admit to being confused here. The commander, who in theory first reported von Ackermann as missing, was in the US Army. The DoD Component within which Iraq falls, Central Command (CENTCOM), reports civilian casualties to a Designated Military Service, in this case, the US Air Force, at HQ Air Force Personnel Center (AFPC/DPFCS) at Randolph AFB in Texas.
E6.2.1.1. Casualty reports will be submitted without delay to the appropriate Military Service Headquarters Casualty Office within 24 hours of a Component learning of the casualty.
The following sample report, "DoD Component Civilian Casualty Report," referred to as "Enclosure 6," is used to input data into the Defense Casualty Information Processing System (DCIPS) which, in theory, maintains data on all casualties including civilian contractors.

From this Casualty Report, DCIPS will generate DD Form 1300, "Report of Casualty."

Commander's Report - DD Form 2812

In order to complete the above steps, an initial report of a missing person, DD Form 2812, is prepared within the first 10 days by the appropriate commander. The commander also completes a short casualty checklist known as a "casualty feeder card" (DA Form 1156).



§ 1502. Missing persons: initial report

(a) Preliminary assessment and recommendation by commander.-- After receiving information that the whereabouts and status of a person described in section 1501(c) of this title is uncertain and that the absence of the person may be involuntary, the commander of the unit, facility, or area to or in which the person is assigned shall make a preliminary assessment of the circumstances. If, as a result of that assessment, the commander concludes that the person is missing, the commander shall­­
(1) recommend that the person be placed in a missing status; and

(2) not later than 10 days after receiving such information, transmit a report containing that recommendation to the Secretary concerned in accordance with procedures prescribed under section 1501(b) of this title.
(b) Transmission of advisory copy to theater component commander.-- When transmitting a report under subsection (a)(2) recommending that a person be placed in a missing status, the commander transmitting that report shall transmit an advisory copy of the report to the theater component commander with jurisdiction over the missing person.

(c) Safeguarding and forwarding of records.-- A commander making a preliminary assessment under subsection (a) with respect to a missing person shall (in accordance with procedures prescribed under section 1501 of this title) safeguard and forward for official use any information relating to the whereabouts and status of the missing person that results from the preliminary assessment or from actions taken to locate the person.

When Safa Shukir called John Dawkins to tell him he had found Kirk von Ackermann's vehicle abandoned on an isolated road, Shukir had reached Dawkins in the contracting office at a US Army base in Tikrit. The battalion commander at the time was LTC Steven Russell who would have relied on Department of Defense Instruction (DODI) 2310.5 for guidance.

DODI 2310.5 is applicable to both military and civilian personnel and details steps for filing DD Form 2812, "Commander's Preliminary Assessment and Recommendation Regarding Missing Person" sometimes referred to as a Commander's Report.

To create the report, the commander is likely to initiate an informal investigation known as an AR 15-6 investigation. The commander assigns an investigating officer who compiles a preliminary report, DA Form 1574, "Report of Proceedings by Investigating Officer." DA Form 1574 includes a chronology, witness statements, exhibits with an index indicating what evidence there is and where it is stored.
DODI 2310.05 [2310.5]

Accounting for Missing Persons (PDF) - Boards of Inquiry
COMMANDER'S PRELIMINARY ASSESSMENT AND RECOMMENDATION
Department of Defense, Army Publishing Directorate
January 31, 2000 with administrative changes March 1, 2008
Page 15 - 23

E3.1. PRELIMINARY ASSESSMENT AND RECOMMENDATION BY COMMANDER

E3.1.1. A flow chart diagramming the elements of the commander's preliminary assessment and recommendation, together with the elements of an initial board of inquiry that would follow that assessment, is found at attachment E3.A1. of this enclosure.



E3.1.2. Information may be received showing that the whereabouts and status of a covered person are uncertain and that the absence of the person may be involuntary. If so, the commander of the unit, facility, or area to or in which the person is assigned shall make a preliminary assessment of the circumstances. When the circumstances of the involuntary absence are questionable, i.e., whether the absence resulted from hostile action, the commander of the unit, facility, or area to or in which the person is assigned shall submit a preliminary assessment and recommendation. Attachment E3.A2. of this enclosure contains a checklist of those items, as applicable, that the commander may wish to consider when preparing the assessment. If, as a result of that assessment, the commander concludes that the person is missing, the commander shall:

E3.1.2.1. Recommend that the person be placed in a missing status; and

E3.1.2.2. Transmit a report containing the recommendation to the Secretary concerned in accordance with procedures prescribed by that Secretary not later than 10 days after receiving such information.

E3.1.3. DD Form 2812, "Commander's Preliminary Assessment and Recommendation Regarding Missing Person," is found at attachment E3.A3. of this enclosure.


E3.1.4. Transmission of a DD Form 2812 is not always required. For instance,
evidence regarding a covered person may be received through news coverage or
discovered through diplomatic channels. That evidence may be sufficient to enable the commander to make a preliminary assessment regarding the covered person's whereabouts and status and whether the absence of the person is involuntary. In all cases, however, the evidence upon which this determination is made shall be recorded and preserved. Receipt of additional evidence could require the commander to submit a preliminary assessment and recommendation. Such evidence could include cessation of hostilities without the return of the covered person or a complete lack of further evidence that, without additional information, could create a doubt concerning the whereabouts and status of the covered person. A preliminary assessment and recommendation is required whenever evidence is received or discovered that may cause the whereabouts and status of the covered person to be uncertain and indicates that the absence of the person may be involuntary.

E3.1.5. Persons who are "covered persons" (defined herein at paragraph E2.1.7.) are limited to those whose involuntary absence arises as a result of a hostile action or under circumstances suggesting that the involuntary absence is a result of a hostile action and whose status is undetermined or who is unaccounted for. A case resolution file will be created and maintained on a covered person and an initial board of inquiry will be convened to inquire into the whereabouts and status of the person. The Under Secretary of Defense for Policy shall determine, with regard to a pending or ongoing military operation, the specific employees, or groups of employees, of contractors of the Department of Defense to be considered to be covered persons. In appropriate circumstances, the USD(P) may expand coverage to non-U.S. citizen civilian officers and employees of the Department of Defense.

E3.1.6. The scope of persons for whom the United States will undertake Personnel Recovery is not limited to situations involving hostile action or circumstances suggestive of hostile action. Personnel Recovery measures may be initiated for personnel (U.S., allied, or coalition) who become unaccounted for as a result of training exercises, operations other than war wherein hostile action is not involved and operational environments not involving hostile action. The specific persons for whom Personnel Recovery may be initiated will vary based upon the circumstances unique to each situation. Located at attachment E3.A4. of this enclosure is a graph depicting the relationship of "covered persons" for whom case resolution files and boards of inquiry apply and those to whom Personnel Recovery applies. For further information on Personnel Recovery, refer to DoD Directive 2310.2, "Personnel Recovery" (reference (d)).

E3.2. TRANSMISSION OF ADVISORY COPY TO THEATER COMPONENT COMMANDER

The Commander of the unit, facility, or area to or in which the person is assigned shall, when recommending that a person be placed in a missing status, transmit an advisory copy of the preliminary assessment and recommendation to the theater Component Commander having jurisdiction over the missing person.

E3.2. TRANSMISSION OF ADVISORY COPY TO THEATER COMPONENT COMMANDER

The Commander of the unit, facility, or area to or in which the person is assigned shall, when recommending that a person be placed in a missing status, transmit an advisory copy of the preliminary assessment and recommendation to the theater Component Commander having jurisdiction over the missing person.

E3.3. SAFEGUARDING AND FORWARDING OF RECORDS

In accordance with procedures prescribed by the Secretary concerned, a Commander
making a preliminary assessment and recommendation with respect to a missing person shall:

E3.3.1. Safeguard and forward, to the Secretary concerned for official use, any
information relating to the whereabouts and status of the missing person that results from the preliminary assessment and recommendation or from actions taken to locate the person.

E3.3.2. Attachment E3.A2. of this enclosure contains a checklist of those items, as
applicable, that the commander may wish to safeguard and forward.
For the most part, E3.A2 relates to recordings, vehicles, weapons and ordinance (think plane crash as a result of missile fire). It does not list personal effects.

Once the Commander's Assessment and Recommendation is filed with The Adjutant General and Theater Component Commander, usually within 10 days of the initial incident, and as authority passes to a Board of Inquiry, jurisdiction over any future investigation becomes unclear. Which may explain why an aggressive and formal investigation into the disappearance of Kirk von Ackermann, once properly accounted for as a missing person, was seemingly forgotten. That is, until his colleague Ryan Manelick was murdered shortly after alleging fraud at Ultra Services.

So, what happened?

Was there a Board of Inquiry? Is Kirk von Ackermann listed in the DCIPS? Was a Casualty Assistance Officer assigned to his case? Did the Missing Persons Act fail to protect the legal rights of Kirk von Ackermann as a missing person and if so, what steps need to be taken to prevent that from ever happening again? At what point did the system break down?

Changes Since 2003

In the summer of 2004, the US Department of State Hostage Working Group was organized by the US Embassy in Baghdad to monitor hostages in Iraq. The Group is sometimes referred to as the Office of Hostage Affairs. According to news reports, the group meets weekly bringing together officials from the FBI, the Defense Department, the State Department and the Iraqi government.

Between January 2006 and January 2007, a Hostage Reporting contract clause was added to Joint Contracting Command (JCC) Acquisition Instructions. The clause is intended for construction and service contracts, and does not address the gray area of service incidental to supply of supply contracts. Contracting officers are now responsible for gathering the very first details of an incident and submitting the information to JCC.
See: Acquisition Instruction (AI), Part 52.2, 01 May 2007

Additional Reading

Army Publishing Directorate - regulations and so much more including a complete list of Department of Defense Issuances (DODI)

DoD Instruction 1300.18 - Personnel Casualty Matters, Policies, and Procedures from the Under Secretary of Defense for Personnel and Readiness from January 8, 2008

DoD Directive 1300.22 - from the Joint Mortuary Affairs Office, Under Secretary of Defense for Personnel and Readiness, on Personal Effects from February 3, 2000 current as of November 21, 2003

Defense Prisoner of War/Missing Personnel Office (DPMO) responsibility for Personnel Recovery after the conclusion of hostilities
Try this link: http://www.dtic.mil/dpmo/faq/

Military Assistance Program includes information from Mortuary and Casualty Affairs

General Information

Casualty: There are six casualty statuses: (1) deceased; (2) duty status – whereabouts unknown (DUSTWUN) for military, or excused absence – whereabouts unknown (EAWUN) for civilians; (3) missing; (4) very seriously ill or injured (VSI); (5) seriously ill or injured (SI); and (6) not seriously ill or injured (NSI). At the DoD Component’s discretion, an additional casualty status of Special Patient (SPECPAT) or Special Category (SPECAT) may be used. POW is not a casualty status for reporting purposes, rather status and category are "missing-captured."

Civilian: A person who is not a member of the armed forces, including a member of the general public, U.S. and non-U.S., a defense contractor, a DoD civilian employee, non-DoD Federal employees, or military dependents.

Contractor: An individual or employee of a private business who contracts to furnish supplies [supply] or perform work [construction or service] at a certain price or rate.

Defense Casualty Information Processing System (DCIPS): The system of record for the "Report of Casualty" DD Form 1300 and other documents and reports. The DCIPS Configuration Control Board (CCB) governs changes within this system. DCIPS is an electronic system used in the collection and management of casualty data and produces the DD Form 1300 and other documents and reports.

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