Natalie LaFave and Nicolas LaFave v. LMH Military Property Management LP, et al.
- Proceeding
- district
- Area
- civil
- Panel
- Cynthia Ann Bashant (author)
Analysis
The court considered Plaintiffs' motion to remand a wrongful death action to state court, where Defendants had removed the case based on federal officer jurisdiction. The court granted the motion, finding that Defendants did not meet the 'acting under' requirement of 28 U.S.C. § 1442(a)(1) because their relationship with the U.S. Navy was an arm's-length business arrangement rather than a federal agency relationship.
| What the court decided | The model |
|---|---|
Plaintiffs' Motion to Remand (ECF No. 7) is granted.“For the reasons above, the Court GRANTS Plaintiffs’ Motion to Remand. (ECF No. 7.)” | agree with court The court correctly applied the strict construction of removal statutes and the burden on the removing party. The factual findings that the defendants had 'exclusive management and control' and that the Navy's consent powers were limited to major structural decisions, not routine maintenance, support the conclusion that the defendants were not 'acting under' a federal officer under Ninth Circuit precedent (specifically Lake v. Ohana Mil. Cmtys., LLC). The distinction between compliance with regulations and acting under a federal officer is well-established. |
The case is remanded to the Superior Court of California, County of San Diego.“The Court thus REMANDS this case to the Superior Court of California, County of San Diego.” | agree with court Remand is the proper remedy when removal jurisdiction is lacking. |
The Clerk of Court is directed to close the present action.“The Clerk of Court is DIRECTED TO CLOSE the present action.” | agree with court Standard administrative procedure following remand. |
The order itself: sound — The order is sound. It correctly identifies the legal standard for federal officer removal, addresses the Defendants' argument regarding the recent Supreme Court decision in Plaquemines, and applies binding Ninth Circuit precedent (Lake, San Mateo, Fidelitad) to the specific facts of the case. The court carefully analyzes the contracts to determine the level of control the Navy had, finding it insufficient to establish an 'acting under' relationship. The reasoning is thorough and directly answers the motion.
Opinion
1 2 3 4 5 6 7 8 UNITED STATES DISTRICT COURT 9 SOUTHERN DISTRICT OF CALIFORNIA 10 11 NATALIE LAFAVE and NICOLAS Case No. 26-cv-03519-BAS-JLB LAFAVE, 12 Plaintiffs, ORDER GRANTING PLAINTIFFS’ 13 MOTION TO REMAND (ECF No. 7) v. 14 15 LMH MILITARY PROPERTY MANAGEMENT LP, et al., 16 Defendants. 17 18 Before the Court is Plaintiffs Natalie LaFave and Nicolas LaFave’s motion to 19 remand the current action to state court (“Motion to Remand”). (ECF No. 7.) For the 20 reasons below, the Court GRANTS Plaintiffs’ Motion to Remand. (Id.) The Court thus 21 REMANDS this case to the Superior Court of California, County of San Diego. The Clerk 22 of Court is DIRECTED TO CLOSE the present action. 23 I. BACKGROUND 24 Plaintiffs filed this action against Defendants LMH Military Property Management 25 LP (“LMPM”) and San Diego Family Housing, LLC (“SDFH”) in the San Diego Superior 26 Court, asserting that Defendants’ residential premises at the Howard Gilmore military 27 housing community (“Howard Gilmore”) were unsafe, and the unsafe conditions (i.e., 28 1 failed window fall prevention device) led to the death of Plaintiffs’ 30-month-year-old son, 2 Kent Adam LaFave. (ECF No. 1-2 ¶¶ 1–31.) 3 More specifically, Plaintiffs allege their window in their second floor living room 4 had a window fall prevention device installed, but it “ceased to consistently function” in 5 preventing the window from being opened beyond four inches without manual 6 disengagement. (Id. ¶¶ 23–24.) Plaintiff Nicolas LaFave opened the subject window and 7 did not manually disengage the device. (Id. ¶¶ 29–31.) Kent LaFave fell through the 8 subject window shortly afterwards and incurred life-threatening injuries, later leading to 9 his death. (Id. ¶¶ 29–31.) 10 In their complaint, Plaintiffs bring a single cause of action for wrongful death— 11 alleging Defendants breached their duties to Plaintiffs to keep Howard Gilmore in a safe 12 condition (i.e., by repairing broken window fall prevention devices), to conduct reasonable 13 inspections, and to warn Plaintiffs of the dangers of broken window fall prevention devices. 14 (Id. ¶¶ 32–44.) 15 Defendants removed the action from state court to this Court and filed an answer to 16 Plaintiffs’ Complaint. (ECF Nos. 1, 2.) Plaintiffs filed a motion to remand this action to 17 state court. (ECF No. 7.) Defendants opposed. (ECF No. 10.) Plaintiffs replied. (ECF 18 No. 18.) 19 II. LEGAL STANDARD 20 A defendant may remove a civil action from state court to federal court. 28 U.S.C. 21 § 1441(a). “The removal statute is strictly construed against removal jurisdiction, and the 22 burden of establishing federal jurisdiction falls to the party invoking the statute.” Acad. of 23 Country Music v. Cont’l Cas. Co., 991 F.3d 1059, 1061 (9th Cir. 2021) (citation omitted). 24 “[A]ny doubt about the right of removal requires resolution in favor of remand.” Moore- 25 Thomas v. Alaska Airlines, Inc., 553 F.3d 1241, 1244 (9th Cir. 2009). Removal is proper 26 when the federal courts have original jurisdiction over the state court action. 28 U.S.C. 27 § 1441(a). District courts have original jurisdiction over “all civil actions arising under the 28 Constitution, laws, or treaties of the United States.” 28 U.S.C. § 1331; see also Republican 1 Party of Guam v. Gutierrez, 277 F.3d 1086, 1088–89 (9th Cir. 2002) (“A case ‘arises 2 under’ federal law either where federal law creates the cause of action or where the 3 vindication of a right under state law necessarily turn[s] on some construction of federal 4 law”). “A motion to remand is the proper procedure for challenging removal.” Moore- 5 Thomas, 553 F.3d at 1244. 6 On a motion to remand, this Court must resolve all disputed questions of fact and 7 any ambiguities of law in favor of the non-removing party. Rader v. Sun Life Assur. Co. 8 of Canada, 941 F. Supp. 2d 1191, 1194 (N.D. Cal. 2013) (citing Good v. Prudential Ins. 9 Co. of Am., 5 F. Supp. 2d 804, 807 (N.D. Cal. 1998)). 10 Defendants removed this case to federal court based on federal officer jurisdiction, 11 28 U.S.C. 1442(a)(1). (ECF No. 1.) “To protect the Federal Government from state-court 12 ‘interference with its operations,’ Congress has given federal courts jurisdiction over some 13 suits against federal officers or those acting under them.” Chevron USA Inc. v. 14 Plaquemines Par., Louisiana, 608 U.S. 1, 5 (2026) (citing Watson v. Philip Morris Cos., 15 551 U.S. 142, 150 (2007)). 16 III. ANALYSIS 17 Under the federal officer removal statute, a removing defendant must satisfy three 18 requirements. Plaquemines Par., Louisiana, 608 U.S at 5. First, the removing defendant 19 must be the United States, a federal agency, a federal officer, or a person “acting under” a 20 federal officer, such as certain private parties hired to assist federal officers. Id. (citing 21 Watson, 551 U.S. at 148–53). Second, the suit must be “for or relating to any act under 22 color of such office.” 28 U.S.C. § 1442(a)(1). Third, the removing defendant must assert 23 “a colorable federal defense.” Mesa v. California, 489 U.S. 121, 129 (1989); see id. at 24 136–37 (grounding this requirement in Article III of the Constitution). 25 “For a private entity to be acting under a federal officer, the private entity must be 26 involved in an effort to assist, or to help carry out, the duties or tasks of the federal 27 superior.” Fidelitad, Inc. v. Insitu, Inc., 904 F.3d 1095, 1099 (9th Cir. 2018). “Acting 28 under” a federal officer includes when the private person: (1) “act[s] on behalf of the officer 1 in a manner akin to an agency relationship”; (2) “is subject to the officer’s close direction, 2 such as acting under the subjection, guidance, or control of the officer, or in a relationship 3 which is an unusually close one involving detailed regulation, monitoring, or supervision”; 4 or (3) “assist[s] the federal officer in fulfilling basic governmental tasks that the 5 Government itself would have had to perform if it had not contracted with a private firm.” 6 Cnty. of San Mateo v. Chevron Corp., 32 F.4th 733, 756 (9th Cir. 2022) (internal quotation 7 marks and citations omitted). 8 Plaquemines Does Not Overrule Ninth Circuit Precedent 9 As a threshold matter, Defendants argue that a recent United States Supreme Court 10 case, Plaquemines Par., Louisiana, clearly establishes three prongs for removal and that 11 Ninth Circuit cases applying the “causal nexus” standard—which purportedly conflates the 12 first and second prongs for federal officer removal—are now overruled to the extent they 13 pre-date Plaquemines Par., Louisiana. (See ECF No. 10 at 4:3–5:3 (citing Lake v. Ohana 14 Mil. Cmtys., LLC, 14 F.4th 993, 1004–05 (9th Cir. 2021)).) 15 However, the Court disagrees for two reasons. First, Ninth Circuit precedent 16 applying the “causal nexus” standard separately analyzes whether the defendant is “acting 17 under” a federal officer and whether the act is pursuant to “any act under color of such 18 office”—meaning the “causal nexus” standard does not directly contradict the three- 19 pronged approach set forth in Plaquemines Par., Louisiana. See Cnty. of San Mateo, 32 20 F.4th at 755–60 (holding “[t]o demonstrate a causal nexus, the private person must show: 21 (1) that the person was ‘acting under’ a federal officer in performing some ‘act under color 22 of federal office,’ and (2) that such action is causally connected with the plaintiff’s claims 23 against it” and finding against federal officer removal when defendant failed to meet its 24 burden to prove it was “acting under” a federal officer) (citing Goncalves ex rel. Goncalves 25 v. Rady Child.’s Hosp. San Diego, 865 F.3d 1237, 1244–50 (9th Cir. 2017)). 26 Second, the Court agrees with Plaintiffs that Plaquemines Par., Louisiana only 27 decided upon the second prong for federal officer removal (“for or relating to any act under 28 color of . . . office”) and expressly assumed without deciding that the defendant had met 1 the first prong (“acting under”) (ECF No. 18 at 2:15–4:12). See Plaquemines Par., 2 Louisiana, 608 U.S. 1, 10 n.2 (“No party disputes that Chevron acted under a federal officer 3 in that capacity. We assume, without deciding, that it did.”). 4 Since the U.S. Supreme Court did not address the first prong of federal officer 5 removal, this Court disagrees with Defendants that Plaquemines Par., Louisiana directly 6 overrules any Ninth Circuit precedent assessing that prong. 7 Whether Defendants “Act Under” the U.S. Navy 8 1. Contracts Do Not Provide Defendants “Act Under” the U.S. Navy 9 As private parties, Defendants must demonstrate that they were “involved in an 10 effort to assist, or to help carry out, the duties or tasks of the federal superior” to satisfy the 11 “acting under” requirement of § 1442(a)(1). Fidelitad, 904 F.3d at 1099; Riggs v. Airbus 12 Helicopters, Inc., 939 F.3d 981, 985 (9th Cir. 2019). One key consideration is whether the 13 private person is assisting the federal officer in fulfilling “basic governmental tasks” that 14 “the Government itself would have had to perform” if it had not contracted with a private 15 firm. Cnty. of San Mateo, 32 F.4th at 756–57 (quoting Watson, 551 U.S. at 153–54); 16 Goncalves, 865 F.3d at 1246–47 (holding that private person fulfilled a basic governmental 17 task by pursuing subrogation claims on behalf of a government agency). 18 Here, Defendants claim that through their contracts with the U.S. Navy “with the 19 express purpose of operating and managing Navy military housing” (ECF No. 10 at 9:13– 20 18), Defendants “act under” the U.S. Navy and fulfill a “basic governmental task” the U.S. 21 Navy would otherwise have to do itself. Watson, 551 U.S. at 153–54. 22 Because Defendants have exclusive management and control over the day-to-day 23 operations of Howard Gilmore, the Court finds that Defendants do not “act under” the U.S. 24 Navy. “A person is not ‘acting under’ a federal officer when the person enters into an 25 arm’s-length business arrangement with the federal government or supplies it with widely 26 available commercial products or services.” Cnty. of San Mateo, 32 F.4th at 757–58 27 (holding defendant was not “acting under” a federal officer by supplying gasoline and 28 diesel fuel to the U.S. Navy pursuant to fuel supply contracts because fuel is a “generally 1 available commercial product[],” despite contractual provisions requiring compliance with 2 certain industry fuel standards and giving the U.S. Navy the “right to inspect delivery, site, 3 and operations.”). 4 By contrast, a defendant is “acting under” a federal agency where the defendant is 5 directly controlled by the federal agency or acting pursuant to the federal agency’s 6 instructions. See Goncalves, 865 F.3d at 1248 (finding defendants were “acting under” the 7 federal Office of Personnel Management (“OPM”) where the OPM contracted with the 8 defendants to administer a health insurance plan for federal employees under the Federal 9 Employee Health Benefit Act and, crucially, making a “reasonable effort” to pursue 10 subrogation claims against plaintiff was part of defendants’ contractual duties); Cabalce v. 11 Thomas E. Blanchard & Assocs., Inc., 797 F.3d 720, 727–30 (9th Cir. 2015) (holding that 12 where contractor defendant’s plan to destroy seized fireworks went awry, defendant was 13 not acting under a federal officer because the Government did not dictate or control the 14 contractor’s plan for destroying the fireworks); see also State v. Monsanto Co., 274 F. 15 Supp. 3d 1125, 1131 (W.D. Wash. 2017), aff’d, 738 F. App’x 554 (9th Cir. 2018) (“[E]ven 16 if the government contracted for Monsanto’s PCBs, the Court cannot say that Monsanto 17 was ‘acting under’ a federal agency where the government did not direct Monsanto to 18 produce and promote PCBs in a particular way.”). 19 The present case is analogous to Lake—wherein the Ninth Circuit found housing 20 defendants did not “act under” a federal officer when the U.S. Navy formed a public-private 21 venture to build housing on a military base because the venture’s operating agreement gave 22 “sole and exclusive management and control” to the private partner. 14 F.4th at 999, 1004– 23 05. According to Defendants’ own briefing (ECF No. 10 at 14:13–22), though the U.S. 24 Navy previously managed Howard Gilmore directly, the U.S. Navy transferred daily 25 management duties of U.S. military housing to private housing authority SDFH following 26 the Military Housing Privatization Initiative, 10 U.S.C. §§ 2871–85, in 2001. The new 27 public-private venture is governed by three agreements (collectively, “Agreements”): 28 1 (1) The “Operating Agreement”: A joint venture agreement between the U.S. 2 Navy and LMPM establishing that LMPM operates the housing and that LMPM 3 needs to seek written consent from the U.S. Navy for major decisions (e.g., 4 corporate governance or filing for bankruptcy) (Ex. A, ECF No. 12-1); 5 (2) The “Leasing Agreement”: A leasing agreement between the U.S. Navy and 6 LMPM in which the U.S. Navy—as land-owner—leases the underlying land to 7 LMPM for no cash rent, in exchange for LMPM’s agreement to build, renovate, 8 operate, and maintain housing at no expense to the U.S. Government, and 9 providing that LMPM bears maintenance liability (Ex. B, ECF No. 12-2); 10 (3) The “Property Management Agreement”: An agreement between LMPM and 11 SDFH providing SDFH a fixed percentage of gross collections in exchange for 12 SDFH managing the day-to-day operations of Howard Gilmore (e.g., renting 13 units to military and non-military tenants, staffing, annual operating and 14 renovation budgets, leasing, hiring and paying employees and contractors, and 15 maintenance and repair) (Ex. C, ECF No. 12-3). 16 Following Lake, the Court finds that the U.S. Navy’s property interests in the 17 underlying land and power to withhold consent over structural aspects of a private housing 18 arrangement do not amount to directing Defendants how to run the day-to-day operations 19 of Howard Gilmore such that Defendants “act under” the U.S. Navy. 14 F.4th at 1004–05. 20 Indeed, the Agreements expressly provide that Defendants do not need direct 21 permission from the U.S. Navy for routine property maintenance, such as conducting 22 window fall prevention device repairs (see Ex. A §§ 5.01(b), 5.12, Article 10; Ex. C 23 §§ 2.1.6(a)–(b)). See United States v. King Features Ent., Inc., 843 F.2d 394, 398 (9th Cir. 24 1988) (“Interpretation of a contract is a matter of law.”). More specifically, Section 5.01(b) 25 of the Operating Agreement explicitly grants LMPM “exclusive management and control 26 of the business” beyond that which is explicitly in the domain of the U.S. Navy consent 27 power (see Ex. A § 5.12) and bankruptcy-remoteness provisions (see Ex. A, Article 10). 28 The list of actions in the U.S. Navy’s domain in Section 5.12 of the Operating Agreement 1 does not include anything relating to managing routine repairs or installations. In addition, 2 the Property Management Agreement provides that SDFH is responsible for keeping 3 Howard Gilmore “in good, safe and clean condition and repair.” (Ex. C § 2.1.6(a).) 4 Furthermore, SDFH is explicitly granted discretion to spend thousands of dollars per 5 instance of routine repair, funded by LMPM, without seeking consent. (Id.) If a broken 6 device presents “immediate danger to persons,” SDFH can even spend outside the budget 7 upon attempting to consult LMPM beforehand and notifying LMPM afterward. (Ex. C 8 § 2.1.6(b).) No routine or individual repairs explicitly require permission from the U.S. 9 Navy. (See Ex. A § 5.12.) 10 Relatedly, though Defendants argue they serve a governmental function through the 11 act of providing military housing (which was previously provided by the U.S. Government) 12 (see ECF No. 10 at 9:13–18, 14:13–22), Lake held that “[m]erely leasing housing to a 13 servicemember cannot itself be a governmental function.” 14 F.4th at 1005. In addition, 14 Congressional acts to privatize military housing—“allowing private companies to own and 15 manage housing on military installations”—do not render those private companies’ 16 housing management a governmental function. Id. 17 Lake provided the caveat that “there may be situations where leasing housing on a 18 military installation might perform a governmental function,” but Defendants would need 19 to show they “perform[] a governmental function in this specific factual context.” 14 F.4th 20 at 1006. Here, the Court agrees with Plaintiffs that Defendants have not shown that they 21 are performing a “governmental function”—as opposed to exercising discretion over 22 routine repair as part of their standard landlord duties—when they allegedly did not repair 23 Plaintiffs’ broken window fall prevention device. (ECF No. 7-1 at 8:19–9:12.) 24 Moreover, the present case is distinct from contrary Ninth Circuit precedent because 25 here, providing military housing does not involve a “strong and distinctly federal 26 interest[],” and Defendants’ contracts with the U.S. Navy do not instruct Defendants to act 27 as an agent on behalf of the U.S. Navy. See Goncalves, 865 F.3d at 1246–48 (finding 28 private insurer was “acting under” OPM where binding precedent has treated pursuing 1 subrogation claims as a distinctly federal interest, and where the contracts with OPM 2 advised the private insurer on strategies for pursuing subrogation claims). 3 Thus, the Court finds the Agreements provided by Defendants amount to an “arm’s- 4 length business arrangement” with the U.S. Navy, rather than Defendants “acting under” 5 the U.S. Navy. Cnty. of San Mateo, 32 F.4th at 757–58. 6 2. Compliance with the U.S. Navy’s Window Fall Prevention Device 7 Program 8 Defendants also argue they “act under” the U.S. Navy by installing window fall 9 prevention devices pursuant to the U.S. Navy’s Window Fall Prevention Device Program 10 (ECF No. 10 at 2:9–3:1) and contractual terms purportedly requiring Defendants to comply 11 with Navy regulations (id. at 8:23–10:5). The main issue here is whether Defendants’ 12 actions taken pursuant to the U.S. Navy’s Window Fall Prevention Device Program 13 constitute directives from the U.S. Navy such that Defendants “act under” the U.S. Navy. 14 Contrary to Defendants’ theory, courts have generally held that merely acting in 15 compliance with federal regulations or agency directives does not entail performing a 16 “basic governmental task”—and thus, does not constitute “acting under” a federal officer. 17 See Fidelitad, 904 F.3d at 1099 (holding a drone manufacturer—which sold drones to both 18 military and civilian consumers—was not “acting under” a federal officer when delaying 19 shipment of a civilian drone order to verify federal export licensing compliance, in the 20 absence of direct orders from a federal officer or agency); cf. Riggs, 939 F.3d at 990 21 (finding “an aircraft manufacturer does not act under a federal officer when it exercises 22 designated authority to certify compliance with governing federal regulations,” despite the 23 manufacturer’s need to obtain the consent of a federal agency prior to making structural or 24 design changes to its aircraft). 25 Although Defendants claim they communicated with the U.S. Navy regarding 26 compliance with the U.S. Navy’s Window Fall Prevention Device Program (ECF No. 10- 27 1 ¶¶ 12–13) and a U.S. Navy representative inspected the windows at Howard Gilmore to 28 comply with the Program (id. ¶ 15), the Ninth Circuit has found that “highly detailed” 1 regulation and “highly supervised and monitored” activities are alone insufficient to 2 demonstrate defendants “act[ed] under” a federal agency. Fidelitad, 904 F.3d at 1099– 3 1100. 4 Rather, Defendants must demonstrate that the U.S. Navy has enlisted Defendants to 5 perform a key governmental duty. See Watson, 551 U.S. at 156 (finding the absence of a 6 “formal delegation” of authority dispositive, including “any contract, any payment, any 7 employer/employee relationship, or any principal/agent arrangement”); Riggs, 939 F.3d at 8 988 (adopting the Seventh Circuit’s interpretation of Watson that a “power to issue 9 conclusive certification of compliance” is a delegation of “rule making” authority, whereas 10 the power to self-certify non-binding compliance is not). 11 Defendants’ exhibits demonstrate that their communications with the U.S. Navy 12 largely constitute guidance for installing compliant window fall prevention devices. For 13 example, the U.S. Navy sent letters to all private housing partners: informing them of 14 modifications to regulatory requirements for window fall prevention devices (ECF No. 10- 15 3), encouraging window safety (ECF No. 10-4), and describing requirements to comply 16 with the Window Fall Prevention Device Program (ECF Nos. 10-5, 10-6). The U.S. Navy 17 also emailed its private housing partners recommending three program-compliant devices 18 and encouraging them to develop their own plans to complete device installation. (ECF 19 No. 10-7.) 20 Although the U.S. Navy’s communications contain detailed instructions, 21 conspicuously missing from these documents is any explicit delegation of the U.S. Navy’s 22 authority for Defendants to determine compliance or to act on behalf of the U.S. Navy 23 when installing or repairing the relevant devices. See Herring v. Californian-Magnolia 24 Convalescent Hosp., Inc., No. EDCV 22-44 JGB (KKx), 2022 WL 743515, at *4 (C.D. 25 Cal. Mar. 11, 2022) (“A facility’s compliance with federal directives, memoranda, and 26 additional regulations and recommendations is insufficient to show that it was conscripted 27 to assist a federal officer or agency in performance of a government duty.”) (citing Saldana 28 v. Glenhaven Healthcare LLC, 27 F.4th 679, 684–85 (9th Cir. 2022)). 1 Moreover, Defendants’ alleged responsibilities to warn, inspect, repair, and maintain 2 window safety devices at issue in this case (see ECF No. 1-2) seemingly derive from their 3 landlord relationship with Plaintiffs—rather than any communications from the U.S. Navy 4 regarding window safety. See Lake, 14 F.4th at 1005 (“Requiring federal agency consent 5 on collateral points falls within the simple compliance with the law circumstance that does 6 not meet the acting under standard.”) (citation modified). For example, though 7 Defendants’ cited communications with the U.S. Navy specify the device category, the 8 qualifying-window thresholds, funding, deadlines, and reporting, they do not contain 9 instruction on installation methodology. (See ECF Nos. 10-3, 10-4, 10-5, 10-6, 10-7, 10- 10 10.) Furthermore, the U.S. Navy’s resident-communication materials postdate Plaintiffs’ 11 tenancy: the “Lock in Safety” strategy is dated July 15, 2025, after Plaintiffs moved in, and 12 the CNIC letter is dated November 2025. (See ECF Nos. 10-8, 10-10.) The warnings 13 Plaintiffs received were Defendants’ own forms—and even explicitly represent non- 14 compliance with the U.S. Navy’s sill height standards. Compare ECF No. 10-2 at 79 15 (Defendants’ materials communicated to residents that only windows with sill heights of 16 25 inches or lower have devices) with ECF No. 10-3 at 2 (U.S. Navy instructed its private 17 housing partners that windows with sill heights 42 inches or less off the floor should have 18 devices installed to be compliant). 19 Thus, the Court finds that Defendants’ communications with the U.S. Navy 20 constitute “mere compliance” with the Window Fall Prevention Device Program and do 21 not transform Defendants’ relationship with the U.S. Navy from an “arm’s-length 22 transaction” to provide military housing to one where Defendants “act under” the U.S. 23 Navy. 24 * * * 25 For the reasons above, the Court finds that Defendants do not demonstrate they were 26 “acting under” the U.S. Navy when failing to repair the window fall prevention device in 27 Plaintiffs’ apartment. Thus, Defendants fail to meet the first requirement of federal officer 28 removal jurisdiction. Plaquemines Par., Louisiana, 608 U.S at 5. Since the removing 1 ||defendant must satisfy all three requirements of federal officer removal, id., the Court 2 || GRANTS Plaintiffs’ Motion to Remand. (ECF No. 7.) 3 CONCLUSION 4 For the reasons above, the Court GRANTS Plaintiffs’ Motion to Remand. (ECF 5 7.) The Court thus REMANDS this case to the Superior Court of California, County 6 |}of San Diego. The Clerk of Court is DIRECTED TO CLOSE the present action. 7 IT IS SO ORDERED. 8 ~ 9 || DATED: September 21, 2026 (yatta Bahar □□ 10 H n. Cynthia Bashant, Chief Judge United States District Court 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28