|
(ignore crappy writing; I'm doing this for speed today.) 1. We didn't study immunities, but if the government is immune from lawsuits, you sue the contractor only (unless the contractor is also immune; then you're SO:L).
2. Is neutralizing VX considered an unusually dangerous activity? If so, the government and the contractor can be held strictly liable (you don't have to prove negligence).
3. If you have to prove negligence, you would have to prove that each defendant had a duty, and breached a duty to the nearby citizens. You will also have to prove legal cause (but-for, substantial factor) and proximate cause -- that the negligence was the cause of the harm. I'm going to assume a general duty -- that the federal government and the contractor have duties to exercise reasonable care to avoid harm that is foreseeable. As it is foreseeable that dispersed VX could kill people in the immediate vicinity, I'll declare duty to have been met.
An issue I would need to resolve before I could more accurately predict who would be responsible for what would be the respective roles of the government and the contractor: • Were the terrorists at all directly responsible for hitting the munitions, or do we know that the government planes hit it? • How responsible was the contractor for the operation of the base?
For this...I will assume the contractor has the sole responsibility for the base. (Otherwise, you could also sue the government for joint responsibility for the base and analysis will be similar, but will also involve contractor screening and oversight issues.)
I will also assume that it is UNCLEAR who hit the munitions -- it could be the terrorists alone, the government and the terrorists both, or the government alone.
So, first, the contractor's liabilities:
Injured people v. Contractor: Duty: The contractor had a duty to take reasonable care to protect the citizens from harm. Breach: What did the contractor do wrong? Did they violate a law or their own internal processes for handling VX? Did they violate industry custom? If they violated a law, and the law was designed to protect the public from harm from VX, we have negligence per se and have an automatic breach of duty. If they violate industry custom, that's either dispositive or persuasive, depending on the jurisdiction and whether we consider the contractors under a professional standard or a general standard.
If the contractor was doing everything reasonably (they don't need to go to heroic measures), no breach. No liability. If, however, the contractor was negligent (i.e. they moved the VX negligently, or they had inadequate security), we can move to:
Cause-in-fact: Can we say either... But-for cause: If not for the contractor's negligence, the people wouldn't have died. (In any case, the contractor is not the sole but-for cause of the deaths, as the air strike/terrorism/at least one were also responsible.) Substantial factor: The contractor's negligence was a substantial factor in the people's deaths.
However...if the damage would have happened regardless (i.e. the air strike or terrorist attack hit the building with such force that the munitions would have blown no matter how the contractor handled them), no cause, so liability.
Proximate cause: Was the terrorist attack an intervening superseding cause? Was the air strike? IF so, we can say the causal chain was interrupted and the contractor's negligence was not the proximate cause of the injuries. To determine whether an intervening (happened after the initial negligence) cause is superseding, we look to foreseeability. The contractor would say "we never could have anticipated a terrorist attack, or that our own government would blow us up." The victims, of course, would say "of COURSE you could anticipate an attack, and an appropriate response, on a military base."
Harm: Not an issue, because we know who was harmed and how.
Ok, hurt people vs. government, plus apportionment, in another post.
|