Loquasto v. Fluor Corporation Inc

CourtDistrict Court, N.D. Texas
DecidedJanuary 8, 2021
Docket3:19-cv-01455
StatusUnknown

This text of Loquasto v. Fluor Corporation Inc (Loquasto v. Fluor Corporation Inc) is published on Counsel Stack Legal Research, covering District Court, N.D. Texas primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Loquasto v. Fluor Corporation Inc, (N.D. Tex. 2021).

Opinion

UNITED STATES DISTRICT COURT NORTHERN DISTRICT OF TEXAS DALLAS DIVISION CHARLOTTE LOQUASTO, et al., § § Plaintiffs, § § v. § CIVIL ACTION NO. 3:19-CV-1455-B § (Consolidated with 3:19-CV-1624-B) FLUOR CORPORATION, INC., et al., § § Defendants. § MEMORANDUM OPINION AND ORDER Before the Court is a Motion to Dismiss for Lack of Jurisdiction and Motion for Summary Judgment in the Alternative (Doc. 45) filed by Defendants Fluor Corporation, Inc., Fluor Enterprises, Inc., Fluor Intercontinental, Inc., and Fluor Government Group International, Inc. (collectively, “Fluor” or the “Fluor Defendants”) and Alliance Project Services, Inc. (“Alliance”). For the reasons that follow, the Court GRANTS the motion insofar as it seeks dismissal for lack of subject-matter jurisdiction. I. BACKGROUND A. Factual Background This is a personal-injury case arising out of a suicide bombing that occurred on Veterans’ Day 2016 at a United States Military base in Afghanistan. See Doc. 1-3, Pls.’ Pet., 2.1 Plaintiffs include 1 In July 2019, the Court consolidated this action with Civil Action No. 3:19-cv-1624-B (the “Branch Action”). The Branch Action is a similar personal-injury action brought by Marvin T. Branch, a soldier injured in the same 2016 bombing. Pet. at 4, Branch v. Fluor Corp., Inc., No. 3:19-cv-1624-B, (N.D. Tex. July 5, 2019), ECF No. 1-3. Because the allegations in the Branch petition are essentially identical to the -1- injured civilians and soldiers, as well as family members of those injured and killed in the bombing. Doc. 1-3, Pls.’ Pet., 5–19. The Fluor Defendants are military contractors, and Alliance is a subcontractor. Id. at 22.

“Fluor provides base operations support” to the United States military at Bagram Airfield (“Bagram”), a military base in Afghanistan. Doc. 45-1, Defs.’ App., 2–3. The support Fluor provides includes “facilities management, hazardous material and hazardous waste management, . . . power generation and distribution, water supply, sewage, sanitation, . . . waste management, maintenance operations, and motor pool[.]” Id. at 3. Fluor provides such services at Bagram pursuant to a task order under the “Logistics Civil Augmentation Program (‘LOGCAP’) IV contract,” the contract that governs its relationship to the military and its conduct at Bagram. Id. at 2.

The military personnel at Bagram are engaged in the Afghan First Program, a counterinsurgency (“COIN”) strategy. Id. at 136; 45-3, Defs.’ App., 556. The Afghan First Program aims to “increase opportunities for Afghan socio-economic development and expansion” and requires bases in Afghanistan to “use available Afghan services and products” and “provid[e] Afghans with training which will add marketable skills to [their] population.” Doc. 45-1, Defs.’ App., 136. COIN efforts like the Afghan First Program aim to “get the people to accept” their legitimate government’s

authority over the authority of insurgents, “tak[e] charge of their own affairs,” and “consent[] to the government’s rule.” Doc. 45-3, Defs.’ App., 558. In that vein, an important aspect of COIN is affording local nationals (“LNs”) economic footing and, in turn, power to reject insurgents. See id. Part and parcel of the Afghan First Program, Fluor’s task order required it to “hire [LNs] to the

allegations in Plaintiffs’ petition, the Court refers only to Plaintiffs’ petition in this Order. -2- maximum extent possible in performance of [the] contract[.]” Doc. 45-1, Defs.’ App., 40. Fluor subcontracted with Alliance to hire LNs to work at Bagram. Id. at 16. Importantly, Alliance “typically recruit[ed] and hire[d] individuals who were initially part of the military labor pool who

were vetted through local village police departments, tribal elders, and the military.” Id. at 17 (citations omitted); see also Doc. 45-4, Defs.’ App., 844. Qari Naeb Hafezi, also known as Nayeb, was one such LN hired to work at Bagram pursuant to the Afghan First Program. Doc. 45-1, Defs.’ App., 12 & n.10. Former Taliban ties ordinarily disqualify an LN from participation in the Afghan First Program. See id. at 18. Even so, Nayeb, who was known to be a former Taliban member,2 was sponsored by the military for training and, in December 2011, began to work at Bagram. Id. at 18, 22, 138. Approximately five years later, on

November 12, 2016, he detonated a bomb strapped to his chest killing himself and at least five other people and injuring many more. Id. at 29; Doc. 1-3, Pls.’ Pet., 6–11. Nayeb worked at Bagram in the HAZMAT area of the non-tactical vehicle yard. Doc. 45-1, Defs.’s App., 22. “He worked with benign substances and did not have access to explosives[.]” Id. at 23. But a military investigation report states that “Nayeb likely smuggled small quantities of homemade explosive[s] onto Bagram Airfield over approximately four months” and assembled the

“suicide vest” at his workstation using materials readily available to him. Doc. 45-4, Defs.’ App., 855. Then, instead of leaving the premises after his November 11, 2016, night shift, he remained on the

2 Fluor posits that the military did not apprise it or Alliance of Nayeb’s Taliban ties. Id. at 18. Plaintiffs do not dispute this. See generally Doc. 57, Pls.’ Resp. -3- base and detonated the bomb “a little over a mile” away from his workstation. Doc. 57-1, Pls.’ Ex. A, 32–33. Pursuant to its task order, Fluor was “responsible for ensuring all personnel supporting [the

task order] compl[ied] with the standards of conduct, and all terms/conditions set forth in [the performance work statement] and the Basic Contract.” Doc. 45-1, Defs.’ App., 40. Fluor was also responsible for “provid[ing] the necessary supervision for personnel required to perform” the contract. Id. This means that Fluor supervised Nayeb’s “day-to-day work[.]” Doc. 57-1, Pls.’ Ex. A, 18.3 Fluor was also responsible for transporting and escorting Nayeb around the base as needed for his job. See Doc. 45-1, Defs.’ App., 45. Importantly, Fluor was required to ensure Nayeb was escorted in compliance with the military’s base-access policy if he left his work area, and the military

determined that Fluor failed to do so on the morning of the bombing, given that Nayeb was able to leave his work area and detonate the bomb elsewhere on the base. See Doc. 57-1, Pls.’ Ex. A(2), 2. The United States military, on the other hand, was responsible for force protection at Bagram. Doc. 45-1, Defs.’ App., 6, 40. “The [m]ilitary’s [f]orce [p]rotection obligation included issuing security badges to [LNs like Nayeb,] . . . who worked at [Bagram].” Id. at 6. Thus, the military determined “who may enter and remain on” Bagram. Id. Prior to issuing security badges to LNs, the

military screened them by checking their identifications, scanning their irises “for biometric check against a watchlist,” collecting their fingerprints and DNA, and interviewing them. Id. at 7–8. Once an LN received a security badge, it was the military’s “responsibility to determine whether [he] may continue to access” Bagram. Id. This means the military continuously vetted LNs even after they 3 Though Alliance participated in the hiring of Afghan nationals for work at Bagram, Alliance took no part in supervising those individuals once they were hired. Doc. 57-2, Pls.’ Ex. B, 25. -4- were hired. Id. Fluor took no part in screening LNs for base access, and it was not privy to the information the military maintained on Bagram’s Afghan workforce. Id. at 9. “The [m]ilitary also completely and exclusively control[led] what materials enter[ed] [Bagram] through physical searches

of all vehicles and personnel entering [Bagram].” Id. at 9. “No LNs subcontracted to Fluor through [Alliance] stay[ed] at [Bagram] full-time, so all [those] entering . . . [had to] traverse the [m]ilitary- run security control points every day.” Id. at 10.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Lane v. Halliburton
529 F.3d 548 (Fifth Circuit, 2008)
Aktepe v. United States
105 F.3d 1400 (Eleventh Circuit, 1997)
Marbury v. Madison
5 U.S. 137 (Supreme Court, 1803)
Baker v. Carr
369 U.S. 186 (Supreme Court, 1962)
Gilligan v. Morgan
413 U.S. 1 (Supreme Court, 1973)
Taylor v. Kellogg Brown & Root Services, Inc.
658 F.3d 402 (Fourth Circuit, 2011)
Galbraith Engineering Consultants, Inc. v. Pochucha
290 S.W.3d 863 (Texas Supreme Court, 2009)
Cheryl Harris v. Kellogg Brown & Root Services
724 F.3d 458 (Third Circuit, 2013)
Lear Siegler, Inc. v. Perez
819 S.W.2d 470 (Texas Supreme Court, 1991)
Santerre v. Agip Petroleum Co., Inc.
45 F. Supp. 2d 558 (S.D. Texas, 1999)
Alan Metzgar v. KBR, Incorporated
744 F.3d 326 (Fourth Circuit, 2014)
In re Dawson
550 S.W.3d 625 (Texas Supreme Court, 2018)
Withers v. Schneider National Carriers, Inc.
13 F. Supp. 3d 686 (E.D. Texas, 2014)
In re KBR, Inc.
893 F.3d 241 (Fourth Circuit, 2018)

Cite This Page — Counsel Stack

Bluebook (online)
Loquasto v. Fluor Corporation Inc, Counsel Stack Legal Research, https://law.counselstack.com/opinion/loquasto-v-fluor-corporation-inc-txnd-2021.