Fluence Energy, LLC v. M/V/BBC Finland

1 2 3 4 5 6 7 8 UNITED STATES DISTRICT COURT 9 SOUTHERN DISTRICT OF CALIFORNIA 10 11 FLUENCE ENERGY, LLC, a Delaware ) Case No.: 3:21-cv-01239-BEN-JLB limited liability company, ) Related Case: 3:21-cv-02014-BEN-JLB 12 ) Plaintiff, 13 ) ORDER: v. ) 14 ) (1) DENYING MOTION TO VACATE M/V BBC FINLAND, bearing 15 International Maritime Organization No. ) VESSEL ARREST; and ) 16 9593684 (the “Vessel”), its cargo, ) (2) DENYING MOTION TO DISMISS apparel, tackle, and appurtenances, etc. in 17 rem, ) ) 18 Defendant. ) 19 ) [ECF No. 40] ) 20 ) 21 ) ) 22 23 I. INTRODUCTION 24 Plaintiff FLUENCE ENERGY, LLC, a Delaware limited liability company 25 (“Fluence”) brings its Verified Complaint, in rem, against Defendant M/V BBC 26 FINLAND, bearing International Maritime Organization No. 9593684 (the “Vessel”), its 27 cargo, apparel, tackle, etc., in rem, for breach of a maritime contract and negligence, 28 seeking arrest and money damages. See Complaint, ECF No. 1 (“Compl.”). 1 Before the Court is Claimant Briese Schiffahrts GmbH & Co. KG MS Filsum’s 2 (“Owner”) Motion to Vacate the Arrest of the Vessel and Dismiss the Case (the “Motion”). 3 Owner brings the Motion pursuant to Rule E(4)(f) of the Supplemental Rules for Admiralty 4 or Maritime Claims of the Federal Rules of Civil Procedure (“Rule E(4)(f)”). After 5 considering the papers submitted, supporting documentation, the parties’ oral arguments, 6 and applicable law, the Court DENIES (1) Owner’s Motion to Vacate the Arrest of the 7 Vessel, ECF No. 40-1; and (2) Owner’s Motion to Dismiss the Case, ECF No. 40-1. 8 II. BACKGROUND 9 Fluence alleges breach of maritime contract and negligence resulting from damage 10 to marine cargo aboard the Vessel, occurring while in route from Hai Phong, Vietnam to 11 San Diego, California. Compl. at 31, ¶ 10; 8, ¶ 42; 9, ¶ 49. 12 A. Statement of Relevant Facts 13 1. Fluence’s Verified Complaint2 14 Fluence “provides grid-scale, industrial-strength energy storage by lithium batteries, 15 referred to as Gen6 Cubes (“Cubes”).” Compl. at 2 ¶ 5. The Cubes are manufactured in 16 Vietnam, packed into containers, and shipped to the United States. Id. at 2–3, ¶ 5. 17 “On February 25, 2021, Fluence . . . contracted with DB Schenker (“DBS”) to serve 18 as a Non-Vessel-Operating Common Carrier [(“NVOCC”)] in booking the loading, 19 stowage, and carriage of the cargo[3] . . . and preparing the necessary shipping contracts 20 with the Vessel interests.” Id. at 4, ¶ 14. Pursuant to “the contract of carriage, DBS agreed 21 to ship the cargo . . . from the” Hai Phong port to locations in California. Id. at 5, ¶ 17. 22 23 1 Unless otherwise indicated, all page number references are to the ECF-generated page number contained in the header of each ECF-filed document. 24 2 The majority of the facts set forth herein are taken from Plaintiff’s Verified 25 Complaint, and for purposes of ruling on the instant Motion, the Court assumes the truth of the allegations pled and liberally construes all allegations in favor of the non-moving 26 party. Manzarek v. St. Paul Fire & Marine Ins. Co., 519 F.3d 1025, 1031 (9th Cir. 2008). 27 3 Fluence’s cargo will be referred to as the “Cargo” and consists of 333 containers holding 954 Cubes, 13 containers holding accessories, and 2 containers holding CRTs. 28 1 “Between February and April 2021 . . . the Cargo [was transported] by truck in 333 2 containers from the[] Vietnam factory to the [port in] Hai Phong . . . .” Id. at 4, ¶ 15. On 3 April 15, 2021, the Cubes were properly loaded in apparent good order and condition at 4 the Hai Phong port for carriage to San Diego, California. Id. at 3, ¶ 10; 7, ¶ 39. Fluence 5 alleges the total value of the cargo aboard the Vessel was $109,677,308.50. Id. at 5, ¶ 22. 6 Also on April 15, 2021, “DBS entered into four written maritime contracts titled 7 ‘SCHENKERocean Non-Negotiable SEA WAYBILL for Combined Transport . . . .’” (the 8 “Sea Waybills”), wherein DBS agreed to accept and safely load and carry Fluence’s Cargo 9 aboard the Vessel. Id. at 5, ¶19. DBS agreed to “discharge the Cargo at San Diego, 10 California . . . .” Id. Fluence’s Cargo was the only cargo carried aboard the Vessel for that 11 voyage. Id. at 5, ¶ 20. The Vessel “had the non-delegable duty to safely load, stow, carry, 12 and deliver the Cargo in good order and condition to San Diego in accordance with the 13 terms and conditions of the Sea Waybills.” Id. Fluence signed the Non-Negotiable Sea 14 Waybill, which redacts the Shipper/Exporter for reasons not explained to the Court but 15 shows the Vessel as the BBC Finland; the port of loading as Hai Phong, Vietnam; and the 16 port of discharge as San Diego, California. Exhibit 1 to Compl.,4 ECF No. 1-2 at 2. 17 On April 28, 2021, “rolling, pitching, and pounding with persistent heavy sea spray 18 over the deck” of the Vessel was reported, causing the Vessel to make course and speed 19 changes. Compl. at 6, ¶ 23. “Because of a subsequent report of smoke in the cargo holds, 20 the Vessel . . . .” diverted to Aomori, Japan to assess for damage. Id. at 6, ¶ 24. 21 The Vessel arrived in Japan on May 8, 2021. Id. at 6, ¶ 25. “Upon arrival at the 22 pier, the Vessel’s interests and surveyors . . . investigate[d] the scope of damage to the 23 Cargo.” Id. “All containers were discharged . . . for inspection . . . to assess any damage 24 to the containers and the potential need for salvage, repacking, and continued 25 transshipment.” Id. at 6, ¶ 27. Fluence alleges “the attending surveyors indicated that a 26 27 4 Plaintiff alleges that Exhibit 1 is “an exemplar Sea Waybill for one of the damaged containers,” and “[a]ll of the waybills related to this incident are in the same form.” Compl. 28 1 cause of the collapsed and damaged containers in the Vessel’s holds was due to improper 2 usage of twist locks and insufficient lashing to the containers . . . .” Id. at 6, ¶ 28. An 3 estimated 179 of 333 containers holding the Cargo suffered some damage, with an 4 estimated 87 containers deemed damaged to the extent they could not safely be reloaded. 5 Id. at 6, ¶ 29. Consequently, 87 containers remain in Japan. Id. at 7, ¶ 30. 6 On June 18, 2021, the Vessel left Aomori, Japan for San Diego, California but the 7 Vessel was only partially loaded and therefore, “short the number of containers contracted 8 for in the Sea Waybills.” Id. at 7, ¶ 33. On or about July 8, 2021, the Vessel arrived in 9 San Diego, California. ECF No. 7 at 7. Fluence estimates $30 million in damages to the 10 Cargo caused by the Vessel, depending on the results of inspection. Compl. at 7, ¶ 35. 11 2. Additional Facts in Fluence and Owner’s Motion Briefing 12 On February 25, 2021, Fluence and DB Schenker5 entered into a contract of 13 affreightment,6 in which DB Schenker agreed to move Fluence’s Cargo from Hai Phong, 14 Vietnam to San Diego, California. Declaration of Mattias Becker, ECF No. 50 (“Becker 15 Decl.”) at 2, ¶ 4; see also ECF No. 51 (“Oppo.”) at 9; Compl. at 4. ¶ 14. 16 On March 1, 2021, DB Schenker entered into a charter party or contract of 17 affreightment, the “Booking Note,” with BBC Chartering Carrier GmbH & Co. KG 18 (“BBC”).7 Declaration of Thomas Bock, ECF No. 40-3 (“Bock Decl.”) at 2–3, ¶ 6; Exhibit 19 20 5 DB Schenker is “the trade name of both Schenker Deutschland AG and Schenker Inc.” ECF No. 51 at 9, ¶ 2. Accordingly, Schenker Deutschland AG and Schenker Inc. 21 will be referred to as DB Schenker. 22 6 Fluence cites to the Declaration of Mattias Becker, ECF No. 50, but no Exhibits are 23 attached evidencing the specific contract of affreightment. No Exhibits, in either parties’ briefing, contains a contract or other agreement dated February 25, 2021. The Declaration 24 of Matthew P. Vafidis, ECF No. 48, attaches the BIMCO Uniform Time Charter as Exhibit 25 H, which is dated February 26, 2021. However, Fluence did not sign the BIMCO Uniform Time Charter, nor does Fluence mention it by name. Therefore, the contract of 26 affreightment entered into by Fluence and DB Schenker dated February 25, 2021, does not 27 appear in the briefing. 7 The Booking Note was signed by BBC Chartering Singapore Pte Ltd. on behalf of 28 1 A to Bock Decl.; Declaration of Matthew P. Vafidis, ECF No. 48 (“Vafidis Decl.”) at 3, ¶ 2 10; Exhibit D to Vafidis Decl.; see also Motion at 6; Oppo. at 9. The Booking Note 3 arranged for the Vessel to carry an unspecified amount (but no less than 250 Cubes) of 4 Fluence’s Cargo. Exhibit A to Bock Decl. at 5; Exhibit D to Vafidis Decl. at 59.; see also 5 Motion at 6. On April 1, 2021, DB Schenker and BBC executed an Addendum to the 6 Booking Note, which provided specifics on the Cargo being shipped. Exhibit E to Vafidis 7 Decl. at 65; see also Oppo at 9. Special Clause B(i) of the Booking Note reads: 8 In case the Contract evidenced by this Bill of Lading covers a shipment to or 9 from a port in the United States, including any US territory, the U.S. Carriage of Goods by Sea Act of the United States of America 1936 (U.S. COGSA) 10 shall apply . . . . In the event that U.S. COGSA applies, then the carrier may, 11 at the Carrier’s election commence suit in a court of proper jurisdiction in the United States in which case this court shall have exclusive jurisdiction. 12 13 Exhibit A to Bock Decl. at 7; Exhibit D to Vafidis Decl. at 61. 14 On April 13 and 14, 2021, Fluence’s Cargo was loaded on the Vessel in Haiphong, 15 Vietnam. Becker Decl. at 3, ¶ 7; Exhibit A to Becker Decl. at 5; see also Oppo. at 9. Also 16 on April 14, 2021, BBC issued four bills of lading (the “Bills of Lading”), which named 17 Fluence as the shipper, BBC as the carrier, and Schenker, Inc. as the consignee (or freight 18 forwarder). Bock Decl. at 3, ¶ 7; Exhibit B to Bock Decl. at 11, 16, 22, 25; Vafidis Decl. 19 at 3, ¶ 9; Exhibit C to Vafidis Decl. at 41, 46, 52, 55; see also Motion at 6. Special Clause 20 B(iv) of the Bills of Lading included the following terms: 21 Whenever the U.S. COGSA applies, whether by virtue of carriage of cargo to 22 or from the US or otherwise, any dispute arising out of or in connection with 23 the Contract of carriage evidenced by this Bill of Lading shall be exclusively determined by the United States District Court for the Southern District of 24 Texas, and in accordance with the laws of the United States. Merchant further 25 agrees to submit to the jurisdiction of the Southern District of Texas and to waive any and all objections to venue. 26 27 Exhibit B to Bock Decl. at 12, 17, 23, 26; Exhibit C to Vafidis Decl. at 42, 47, 53, 56. 28 On April 15, 2021, DB Schenker (through Schenker Deutschland AG) issued four 1 Sea Waybills on behalf of NVOCC and affiliate entity, SchenkerOcean. Becker Decl. at 2 3, ¶ 8; Exhibit B to Becker Decl.; see also Oppo. at 10. 3 B. Procedural History 4 1. The Instant, California Litigation 5 On July 8, 2021, Fluence filed suit alleging (1) breach of maritime contract of 6 carriage and (2) negligence. Compl. at 7–9. On the same day, Fluence filed two Ex Parte 7 Applications requesting the Court arrest the Vessel, appoint a substitute custodian, and 8 permit normal operations of the Vessel while under arrest. ECF Nos. 5, 6. On July 9, 9 2021, this Court granted in part Fluence’s Ex Parte Applications, authorizing the arrest of 10 the Vessel and allowing for normal operations while under arrest, but denying appointment 11 of a substitute custodian. ECF No. 7. 12 On July 16, 2021, Fluence and Owner filed a Joint Motion to Appoint a Substitute 13 Custodian and a Joint Motion to Release the Vessel From Arrest. ECF Nos. 16, 19. The 14 Court granted both Motions. ECF Nos. 18, 21. 15 On August 13, 2021, the Vessel answered Fluence’s Complaint, listing forum non 16 conveniens and improper venue as affirmative defenses. ECF No. 26 at 7–8, ¶¶ 17, 18. 17 The Vessel based these assertions on the terms of the Bills of Lading. Id. at 7, ¶ 17. 18 On October 15, 2021, Owner filed the instant Motion to Vacate the Vessel Arrest 19 and Dismiss the case. Motion. On November 22, 2021, Fluence filed its Response in 20 Opposition to Owner’s Motion, along with supporting declarations of Mattias Becker, Julia 21 M. Haines, and Matthew P. Vafidis. Oppo.; Becker Decl.; Vafidis Decl.; ECF No. 49. On 22 December 6, 2021, Owner filed its Reply. ECF No. 53 (“Reply”). 23 On December 8, 2021, Fluence and Owner filed a Joint Request for Oral Argument 24 as to Defendant’s Motion to Vacate Arrest and Dismiss Action, which the Court granted 25 on December 17, 2021. ECF Nos. 54, 55. On February 7, 2022, the Court heard Oral 26 Argument. ECF No. 62. 27 28 1 2. The Texas Litigation 2 On July 9, 2021, BBC filed a complaint against Fluence8 for declaratory judgment 3 in the Southern District of Texas. Declaration of Frank C. Brucculeri, ECF No. 40-2 4 (“Brucculeri Decl.”) at 2, ¶ 5; Declaration of Julia M. Haines, ECF No. 49 (“Haines Decl.”) 5 at 2, ¶ 3. 6 On September 23, 2021, Fluence filed a motion to transfer to the Southern District 7 of California. Supplemental Declaration of Frank C. Brucculeri, ECF No. 53-1 (“Supp. 8 Brucculeri Decl.”) at 2, ¶ 5–6; Exhibit A to Supp. Brucculeri Decl. at 10; Haines Decl. at 9 2, ¶ 8; Exhibit D to Haines Decl. at 53–72. Fluence based its argument for transfer on the 10 “first to file rule,” which allows a court to refuse to hear a case when the issues in related 11 and previously filed litigation, pending before another federal court, substantially overlap. 12 Exhibit A to Supp. Brucculeri Decl. at 11–13; Exhibit D to Haines Decl. at 62–63. 13 Fluence’s California action was filed one day before BBC filed its Texas action. Exhibit 14 A to Supp. Brucculeri Decl. at 8–9. BBC argued the forum-selection clause in the Bills 15 of Lading, specifying the Southern District of Texas as the proper forum, precluded 16 transfer. Id. at 14. 17 On December 1, 2021, the Texas Court ruled in favor of Fluence and transferred the 18 case to the Southern District of California. Id. at 16. The Texas Court cited several cases 19 granting transfers pursuant to the “first to file rule” despite forum-selection clauses 20 specifying the Southern District of Texas as the appropriate forum. Id. at 14–15. 21 III. LEGAL STANDARD 22 The Constitution extends the jurisdiction of federal courts “to all Cases of admiralty 23 and maritime Jurisdiction.” U.S. CONST. art. III, § 2. “Congress, in turn, embodied that 24 [judicial] power in a statute” vesting federal courts with exclusive jurisdiction over 25 admiralty and maritime claims. Ventura Packers, Inc. v. F/V Jeanine Kathleen, 305 F.3d 26 913, 918 (9th Cir. 2002) (citing 28 U.S.C. § 1333(1)). 27 8 Schenker Inc. and Schenker Deutschland AG (i.e., DB Schenker) were also named 28 1 IV. DISCUSSION 2 Owner makes two overarching arguments in its Motion. First, if reading the 3 Complaint broadly, Owner argues Fluence accepted the terms of the Bills of Lading, 4 including the forum-selection clause therein, by making references to other contracts and 5 agreements in its Complaint. Motion at 13–16. Owner explains, given the language, those 6 referenced contracts/agreements implicitly included the Bills of Lading. Id. Second, if 7 reading the Complaint narrowly, Owner argues Fluence failed to make a prima facie case 8 for arrest of the Vessel because Fluence based its breach of contract claim on the non- 9 binding Sea Waybill attached as Exhibit 1 to the Complaint. Motion at 9. Owner also 10 argues Fluence’s negligence claim is nominal because it is swept up in Fluence’s 11 contractual allegations. Reply at 7–8. 12 Fluence counters Owner should have brought a motion to transfer venue, pursuant 13 to 28 U.S.C. § 1404(a), instead of a Rule E(4)(f) motion to vacate the arrest and dismiss 14 the action. Oppo. at 23–24. Fluence argues the forum-selection clause in the Booking 15 Note, and not that in the Bills of Lading, govern the issue of an appropriate forum. Id. at 16 26–29. Fluence further contends in rem liability exists regardless of which contract 17 governs the dispute, because Fluence’s cargo was damaged while aboard the Vessel. Id. 18 at 15–18. Finally, Fluence argues it made a valid prima facia case for an in rem arrest of 19 the Vessel pursuant to Rule E and Rule C of the Supplemental Rules for Admiralty or 20 Maritime Claims of the Federal Rules of Civil Procedure (“Rule C”), and that Owner’s 21 argument the Sea Waybills are not binding creates factual disputes. Oppo. at 13–18. 22 A. Procedural Mechanism to Enforce Forum-Selection Clause 23 In Atlantic Marine Const. Co. v. U.S. Dist. Ct. for W. Dist. of Texas, the Supreme 24 Court held that “[t]he appropriate way to enforce a forum-selection clause pointing to a 25 state or foreign forum is through the doctrine of forum non conveniens.” 571 U.S. 49, 55 26 (2013). In the federal court system, “Congress has replaced the traditional remedy of 27 outright dismissal with transfer” pursuant to 28 U.S.C. § 1404(a). Id. However, Atlantic 28 Marine also held “the same standards should apply to motions to dismiss for forum non 1 conveniens in cases involving valid forum-selection clauses,” because “dismissal would 2 work no injustice on the plaintiff.” 571 U.S. at 66 n.8. See also Yei A. Sun v. Advanced 3 China Healthcare, Inc., 901 F.3d 1081, 1091 (9th Cir. 2018) (quoting Atlantic Marine, 571 4 at 66 n.8) (“A court must dismiss a suit filed ‘in a forum other than the one specified in a 5 valid forum-selection clause,’ even if it ‘makes it possible for [plaintiffs] to lose out 6 completely, through the running of the statute of limitations in the forum finally deemed 7 appropriate.’”). 8 “When reviewing a [§ 1404(a)] motion to transfer venue ... a court may consider 9 evidence outside of the pleadings but must draw all reasonable inferences and resolve 10 factual conflicts in favor of the non-moving party.” Universal Stabilization Techs., Inc. v. 11 Advanced Bionutrition Corp., No. 17-cv-87-GPC-MDD, 2017 WL 1838955, at *9 (S.D. 12 Cal. May 8, 2017) (quoting Sleepy Lagoon, Ltd. v. Tower Grp., Inc., 809 F. Supp. 2d 1300, 13 1306 (N.D. Okla. Aug. 19, 2011)). 14 The party “defying the forum-selection clause . . . bears the burden of establishing 15 that transfer to the forum for which the parties bargained is unwarranted.” Atlantic Marine, 16 571 U.S. at 63. Generally, in deciding a motion to transfer, courts consider both private 17 and public interest factors but when deciding a transfer based on a forum-selection clause, 18 the court should consider only public interest factors, because the clause acts as a waiver 19 of the plaintiff’s private interests. Id. at 64. 20 Fluence argues Owner did not follow the “proper procedural path” in seeking to 21 enforce the forum-selection clause at issue, because it filed a Rule E(4)(f) Motion instead 22 of a motion to transfer pursuant to 28 U.S.C. § 1404(a). Oppo. at 23–24. Fluence claims 23 Owner is attempting to avoid the burden of weighing private and public interest factors 24 favoring transfer. Id. at 23–24. Owner does not address whether its Rule E Motion is 25 appropriate and replies that it did not file a motion to transfer because dismissal is the 26 proper remedy. Reply at 3. 27 Although the proper mechanism to enforce a forum-selection clause is a § 1404(a) 28 motion to transfer venue, Atlantic Marine also held that the result of enforcing a forum- 1 selection clause pursuant to §1404(a) would be dismissal. 571 U.S. at 56, 66 n.8. 2 Furthermore, in the event of a valid forum-selection clause, the burden would be on 3 Fluence to establish public interest factors, and private interest factors would be 4 disregarded. However, based on the evidence presented, the Court finds Fluence is not 5 bound by the terms of the forum-selection clause in the Bills of Lading and therefore, the 6 clause is unenforceable. See infra Part IV.B. 7 B. Rule E(4)(f) Challenge of Forum-Selection Clause in Bills of Lading 8 Forum selection clauses are “prima facie valid and should be enforced unless 9 enforcement is shown by the resisting party to be ‘unreasonable’ under the circumstances.” 10 Fireman’s Fund Ins. Co. v. M.V. DSR Atl., 131 F.3d 1336, 1338 (9th Cir. 1997), as 11 amended (Mar. 10, 1998) (quoting M/S Bremen v. Zapata Off–Shore Co., 407 U.S. 1, 10, 12 (1972)). Federal courts, including the Ninth Circuit, have a long history of upholding 13 forum-selection clauses in bills of lading. Kawasaki Kisen Kaisha Ltd. v. Regal-Beloit 14 Corp., 561 U.S. 89, 108–11 (2010) (enforcing a forum selection clause in a bill of lading); 15 Fireman’s Fund Ins., 131 F3.d at 1339–40 (same); Kukje Hwajae Ins. Co. v. M/V 16 HYUNDAI LIBERTY, 408 F.3d 1250, 1255 (9th Cir. 2005) (same); Mazda Motors of Am., 17 Inc. v. M/V COUGAR ACE, 565 F.3d 573, 580 (9th Cir. 2009) (same); see also Vimar 18 Seguros y Reaseguros, S.A. v. M/V Sky Reefer, 515 U.S. 528, 541 (1995) (upholding a 19 foreign arbitration clause in the bills of lading). 20 “Enforcement is ‘unreasonable’ where it would ‘contravene a strong public policy 21 of the forum in which suit is brought.’” Fireman’s Fund, 131 F.3d at 1338 (quoting M/S 22 Bremen, 407 U.S. at 15). In discussing forum-selection clauses, the Supreme Court has 23 held “[a] clause of this kind is enforced unless it imposes a venue ‘so gravely difficult and 24 inconvenient that [the plaintiff] will for all practical purposes be deprived of his day in 25 court.’” Kawasaki, 561 U.S. at 109–10 (2010) (quoting M/S Bremen, 407 U.S. at 18). 26 The issue here is whether Fluence accepted the terms of the forum-selection clause 27 in the Bills of Lading. Reading the Complaint broadly, Owner argues Fluence accepted 28 the Bills of Lading terms when it based its suit on the various contracts involved in this 1 action. Motion at 13–15. Although Fluence did not refer specifically to the Bills of Lading 2 in its Complaint, Owner contends Fluence made several vague references to them when 3 discussing “agreements constituting the contract of carriage,” “the applicable contracts,” 4 and the “necessary shipping contracts with the Vessel interests.” Id. at 13–14 (citing 5 Compl. at 4, ¶14; 8, ¶¶ 41, 45). For example, Owner explains that Fluence based its suit, 6 at least in part, on the agreement between DB Schenker and Fluence, wherein DB Schenker 7 “contracted to serve as [NVOCC] . . . and “agreed not only to book the loading, stowage, 8 and carriage of the Cargo aboard the Vessel but also to ‘prepar[e] the necessary shipping 9 contracts with the Vessel interests.’” Motion at 13–14 (citing Compl. at 4, ¶¶ 19–22). 10 Owner argues this assertion refers to the Bills of Lading, because they are “‘necessary’ to 11 the overall contract of carriage” and “those necessary ‘shipping contracts’ would be 12 contracts with Vessel interests . . . .” Motion at 14. 13 Owner further contends there is mandatory language in the Bills of Lading forum- 14 selection clause, and that such clauses are presumptively valid when litigating commercial 15 maritime contracts. Motion at 17; Exhibit B to Bock Decl. at 12, 17, 23, 26 (“[A]ny dispute 16 arising out of or in connection with the Contract of carriage evidenced by this Bill of Lading 17 shall be exclusively determined by the United States District Court for the Southern District 18 of Texas . . . .”). Owner asserts the clause should be enforced unless Fluence shows 19 “enforcement would be unreasonable and unjust or that it was invalid from its inception 20 due to formation issues such as fraud, mutual mistake, or impossibility.” Motion at 16. 21 Fluence contends it was unaware of and had not seen the Bills of Lading prior to 22 filing suit. Oppo. at 11, 22; Becker Decl. at 3, ¶ 10. Fluence also argues that because this 23 was a contract of private carriage, the terms of the Booking Note, “including its forum- 24 selection clause [broadly allowing for litigation in a court of proper jurisdiction], control.” 25 Oppo. at 25; Exhibit D to Vafidis Decl. at 61. Fluence explains the Booking Note and 26 Addendum entered into by DB Schenker and BBC, “constituted a contract of private 27 carriage, a voyage charter.” Oppo. at 25. Fluence argues in these cases, the charter party 28 agreement acts as the contract of carriage, and the Bills of Lading act as receipts. Id. 1 Fluence maintains the Bills of Lading cannot unilaterally alter the terms of the Booking 2 Note. Id. at 26. 3 Owner is correct that contracts and/or agreements other than the Sea Waybills are 4 mentioned in Fluence’s Complaint. However, Fluence did not specifically reference the 5 Bills of Lading and claims it was unaware of them prior to filing suit. Id. at 11; Becker 6 Decl. at 3, ¶ 10; Compl. One principle behind enforcing forum-selection clauses in bills 7 of lading is that the choice of forum was bargained for. See M/S Bremen, 407 U.S. at 12 8 (“The choice of that forum was made in an arm’s-length negotiation by experienced and 9 sophisticated businessmen, and absent some compelling and countervailing reason it 10 should be honored by the parties and enforced by the courts”). To the extent Fluence was 11 unaware of the Bills of Lading, and the forum-selection clause contained therein, it would 12 be unreasonable to enforce the clause and disregard Fluence’s choice of forum. See also 13 All Pac. Trading, Inc. v. Vessel M/V Hanjin Yosu, 7 F.3d 1427, 1431 (9th Cir. 1993) 14 (quoting C-ART, Ltd. v. Hong Kong Islands Line Am., S.A., 940 F.2d 530, 532 (9th Cir. 15 1991)) (“Bills of lading are contracts of adhesion, usually drafted by the carrier, and are 16 therefore ‘strictly construed against the carrier.’”). 17 Owner relies on Hyundai Liberty, where the Ninth Circuit “held that a cargo owner 18 ‘accepts’ a bill of lading to which it is not a signatory by bringing suit on it.” 408 F.3d 19 1250, 1254 (9th Cir. 2005) (citing All Pac. Trading, 7 F.3d at 1432). However, in Hyundai 20 Liberty, the “[p]laintiff filed suit on all ‘applicable bills of lading’” and made several other 21 references to the “bills of lading” in its complaint. 408 F.3d at 1254. Here, the Complaint 22 does not specifically mention the Bills of Lading. See generally Compl. 23 This is one of those instances when enforcement of a forum-selection clause would 24 be unreasonable or unjust. See Gemini Techs., Inc. v. Smith & Wesson Corp., 931 F.3d 25 911, 914–17 (9th Cir. 2019) (citing M/S Bremen, 407 U.S. at 15) (holding the district court 26 erred in enforcing a forum-selection clause). Accordingly, the Court DENIES Owner’s 27 Motion to enforce the forum-selection clause in the Bills of Lading. 28 1 C. Rule E(4)(f) Challenge to Fluence’s Causes of Action 2 1. Breach of Contract Claim 3 A complaint for an in rem action maritime claim must: (1) be verified; (2) describe 4 the property that is the subject of the action with reasonable particularity; and (3) “state 5 that the property is within the district or will be within the district while the action is 6 pending.” Fed. R. Civ. P. Supp. Adm. & Mar. Cl. R. C(2); see also Barnes v. Sea Hawaii 7 Rafting, LLC, 889 F.3d 517, 529 (9th Cir. 2018) (“To commence an action in rem against 8 a vessel, the plaintiff must file a verified complaint that describes the vessel ‘with 9 reasonable particularity’ and states that the vessel ‘is within the district’ or will be so ‘while 10 the action is pending.’”). If the plaintiff meets the conditions for an in rem action, “the 11 court must issue an order directing the clerk to issue a warrant for the arrest of the vessel . 12 . . .” Fed. R. Civ. P. Supp. Adm. & Mar. Cl. R. C(3)(a)(i). “Once the district court issue[s] 13 warrants for the arrest of the . . . vessels pursuant to Rule C, and the warrants [are] 14 successfully served, jurisdiction [i]s complete.” Barnes, 889 F.3d at 529 (quoting Ventura 15 Packers, Inc. v. F/V Jeanine Kathleen, 424 F.3d 852, 858 (9th Cir. 2005)). “After the 16 vessel is arrested, the owner is entitled to ‘a prompt post-seizure hearing at which he can 17 attack the verified complaint, the arrest, the security demanded, or any other alleged 18 deficiency in the proceedings up to that point.’” Barnes, 889 F.3d at 532 (citing, inter alia, 19 Fed. R. Civ. P. Supp. Adm. & Mar. Cl. R. E(4)(f)). The plaintiff must then “show why the 20 arrest or attachment should not be vacated or other relief granted consistent with these 21 rules.” Fed. R. Civ. P. Supp. Adm. & Mar. Cl. R. E(4)(f)). 22 Rule E(2)(a) sets forth additional requirements, instructing the plaintiff’s complaint 23 “state the circumstances from which the claim arises with such particularity that the 24 defendant or claimant will be able, without moving for a more definite statement, to 25 commence an investigation of the facts and to frame a responsive pleading.” Fed. R. Civ. 26 P. Supp. Adm. & Mar. Cl. R. E(2); Russell v. U.S. Dist. Ct. For Cent. Dist. of California, 27 182 F.3d 927 (9th Cir. 1999). The Ninth Circuit has not analyzed the standard articulated 28 in Rule E(2), but some courts have held the language rises to the level of a heightened 1 pleading requirement. See Vitol, S.A. v. Primerose Shipping Co., 708 F.3d 527, 542 (4th 2 Cir. 2013) (quoting United States v. Mondragon, 313 F.3d 862, 865 (4th Cir. 2002)) (“Rule 3 E(2)(a)’s requirement for pleading specific circumstances is one part of the process which 4 guards against the improper use of admiralty seizure proceedings. Thus, Rule E(2)’s 5 heightened particularity in pleading requirement is always subject to the general standard 6 that the complaint sufficiently notify the defendant of the incident in dispute and afford a 7 reasonable belief that the claim has merit.”); Beluga Chartering GMBH v. Korea Logistics 8 Sys. Inc., 589 F. Supp. 2d 325, 327 (S.D.N.Y. Dec. 8, 2008) (“[T]he plaintiff need not 9 present evidence to support his claim, but the complaint must contain factual allegations to 10 meet the heightened pleading standard of Supplemental Rule E(2)(a) . . . .”). However, 11 “the precise boundaries of such a heightened pleading requirement are not clearly defined.” 12 Vitol, 708 F.3d at 542. 13 Cases in this and other districts have held that, at the Rule E(4)(f) hearing, the 14 plaintiff bears the burden of proving there were reasonable grounds and probable cause to 15 arrest the defendant’s property. See Sea Prestigio, LLC v. M/Y Triton, No. 10-cv-2412- 16 BTM-AJB, 2010 WL 5376255, at *2 (S.D. Cal. Dec. 22, 2010) (quoting Del Mar Seafoods 17 Inc. v. Cohen, No. C 07-02952-WHA, 2007 WL 2385114, at *3 (N.D. Cal. Aug. 17, 2007)) 18 (“The purpose of a Rule E(4)(f) hearing, however, is not to resolve these factual disputes, 19 but rather to assess whether plaintiff’s showing rises to the level of probable cause.”). 20 Owner argues in rem jurisdiction is improper, because Fluence based its Complaint 21 on the NVOCC-issued Sea Waybill, and the Vessel provides contrary “evidence that the . 22 . . Bills [of Lading], including their forum-selection clause, govern the subject shipment.” 23 Motion at 9–10. Owner further contends that if Fluence’s in rem action is based solely on 24 the Sea Waybill, the action should be dismissed, because “the Vessel had never even seen, 25 much less authorized, the Sea Waybill issued by SchenkerOcean to . . . . Fluence.” Id. at 26 11–13. Owner contends neither it nor the Vessel were parties to the Sea Waybill, and that 27 the relationship of the NVOCC, SchenkerOcean, to the Vessel is insufficient to ratify it 28 based on the carriage of goods alone. Id. at 7, 12–13 (citing Ins. Co. of N. Am. v. S/S Am. 1 Argosy, 732 F.2d 299, 304 (2d Cir. 1984)). 2 Fluence argues it “has sufficiently met the standard for an in rem vessel arrest,” 3 citing the Rule C(2)’s requirement that the Complaint be verified, the property described 4 with reasonable particularity, and that the property be within the district at the time of filing 5 suit. Oppo. at 15; Vafidis Decl. at 2, ¶ 5; Exhibit A to Vafidis Decl. at 7. Fluence claims 6 it could not have arrested the Vessel in Texas, because the Vessel never intended to go to 7 Texas—the Vessel’s voyage was from Hai Phong, Vietnam to San Diego, California. 8 Oppo. at 15. The only place where an in rem arrest of the Vessel could take place was San 9 Diego. Id. Fluence claims Owner is attempting “to draw the Court into a premature mini 10 trial” and that it is “not ‘required to prove its case just to defeat the motion to vacate.’” Id. 11 at 13 (quoting SMS Yacht Maint. V. One Nautique 210 Pleasure Vessel, No. 23-cv-2038- 12 IEG-NLS, 2012 WL 6737197, at *1 (S.D. Cal. Dec. 28, 2012) (quoting Equatorial Marine 13 Fuel Mgmt. Servs. Pte Ltd. v. MISC Berhad, 591 F.3d 1208, 1211(9th Cir. 2010)). Instead, 14 Fluence maintains it is only required to establish probable cause for the arrest, which it has 15 already done. Oppo. at 13–15. Finally, Fluence contends the issue of which contract 16 governs the action is often considered immaterial, and that “[t]he Vessel is liable in rem 17 for breach of contract under the mutual lien theory, due to improper stowage of Fluence’s 18 Cargo.” Id. at 18. Fluence explains that under this theory, once the Vessel sailed with 19 Fluence’s Cargo on board, the Vessel and Fluence were entitled to “reciprocal liens for 20 non-performance of the contract of affreightment.” Id. at 17 (citing Krauss Brothers 21 Lumber Co. v. Dimon S.S. Corp., 290 U.S. 117, 121–22 (1933)). 22 Owner replies again that it is not bound by the NVOCC issued Sea Waybills because 23 they were issued “without the knowledge or authority of the Vessel or the charterer . . . .” 24 Reply at 5. Owner further argues that Fluence is now asserting new legal theories—its 25 mutual lien theory, and that the Booking Note governs and not the Sea Waybills—but these 26 claims fails because the allegations did not form “the actual basis for the Vessel’s arrest . . 27 . .” Id. at 4–5. Owner also claims Fluence incorrectly characterizes the Booking Note as 28 a charter party and the contract of affreightment. Id. at 9–10. Finally, Owner asserts the 1 terms of the Bills of Lading supersede the Booking Note. Id. at 10. 2 In arguing it is not liable under the Sea Waybills, Owner relies on Argosy. Motion 3 at 12–13 (citing Argosy, 732 F.2d at 301–304). There, the question was “whether a ship 4 may be held liable on a bill of lading issued by an NVOCC without the authorization of 5 the ship’s owner or charterer.” Argosy, 732 F.2d at 302. The Second Circuit held that the 6 owner in that case “cannot be said to have ratified the bill of lading; one cannot ratify an 7 unauthorized agreement of which one is wholly unaware.” Id. (citations omitted). The 8 Court explained “the relationship of the NVOCC to the vessel is too insubstantial to permit 9 adoption or application of a ratification doctrine based solely on the carriage of goods.” Id. 10 at 304. Fluence argues its case is distinguishable because in Argosy, there were several 11 NVOCCs and the case focused on “one shipment among several hundred shipments and 12 two separate ships.” Oppo. at 19 (citing Argosy, 732 F.2d at 301). The owner could not 13 have been “aware of bills of lading issued by ‘hundreds of shippers and middlemen who 14 book freight on each voyage.’” Oppo. at 20 (citing Argosy, 732 F.2d at 303–304). Here, 15 the case involves a contract of private carriage, where “Fluence was the sole shipper 16 pursuant to . . . [the] contract of affreightment with DB Schenker” and Owner “should be 17 deemed to have ratified the contract.” Oppo. at 21. 18 In Argosy, the Court decided whether the owner ratified and was therefore, liable 19 under NVOCC-issued bills of lading. 732 F.2d at 302. Fluence also argues Owner’s 20 liability under the Sea Waybills pursuant to the mutual lien theory. Oppo. at 17–18. For 21 purposes of the instant Motion, the Court will not decide whether Owner is liable under the 22 Sea Waybills at issue. The Court will only decide whether Fluence satisfied its pleading 23 requirements and burden pursuant to Owner’s Rule E(4)(f) challenge. 24 Fluence brought suit based on the Sea Waybills, evidenced by its Complaint and its 25 own statements. See e.g., Compl. at 3, ¶ 8; Exhibit B to Brucculeri Decl. at 32 (Fluence 26 stating it “sued under the Sea Waybills” in its motion to transfer the Texas action to the 27 Southern District of California); Oppo. at 16 (“Fluence has adequately alleged contract- 28 based in rem liability based on the . . . Sea Waybills”). However, the references to other 1 contracts/agreements in Fluence’s Complaint, establish that Fluence does not rely solely 2 on the Sea Waybills. For example, Fluence alleges damages based on “the material 3 breaches of the Sea Waybills and the maritime contract of carriage . . . .” Compl. at 8, ¶ 4 45. This allegation distinguishes the Sea Waybills from the contract of carriage and 5 establishes Fluence is basing suit on more than one agreement. Even Owner recognizes 6 Fluence’s references to several contracts/agreements in making its argument that Fluence 7 accepted the Bills of Lading. See supra Part IV.B. 8 In this Court’s July 9, 2021 Order Arresting the Vessel, Fluence met the 9 requirements for arrest by filing its Verified Complaint, describing the Vessel with 10 reasonable particularity, and alleging the Vessel was within the district at the time of filing 11 suit. ECF No. 7 at 10–11. The parties do not dispute these facts, or the allegation that 12 Fluence’s Cargo was damaged while aboard the Vessel during shipment to San Diego, as 13 set forth in Fluence’s Complaint. However, a Rule E(4)(f) hearing imposes additional 14 requirements on Fluence to prove arrest of the Vessel was proper, and Rule E(2)(a) sets 15 forth heightened pleading requirements. 16 As to whether Fluence met its Rule E(4)(f) burden of proving probable cause, there 17 is no requirement that a party alleging breach of contract and seeking arrest of a vessel 18 must attach all applicable agreements to its verified complaint. However, Fluence must 19 establish a prima facie claim for breach of contract. Equatorial Marine, 591 F.3d at 1210 20 (“[T]he district court properly vacated the attachment because Equatorial failed to show it 21 had a valid prima facie breach of contract . . . claim against MISC.”). A claim for relief 22 for breach of contract under California law must show: (1) a legally enforceable contract 23 between the parties; (2) the defendant’s breach of that contract; and (3) damage to the 24 plaintiff caused by the defendant’s breach. Hickcox-Huffman v. US Airways, Inc., 855 F.3d 25 1057, 1062 (9th Cir. 2017); McKell v. Wash. Mut., Inc., 142 Cal. App. 4th 1457, 1489 26 (2006). 27 Fluence argues the issue of which contract governs the action is often immaterial. 28 Oppo. at 18 (citing Cactus Pipe & Supply Co. v. M/V Montmartre, 756 F.2d 1103, 1113 1 (5th Cir. 1985)). This may be true in certain Circuit Courts, but Fluence must still plead a 2 legally enforceable contract between the parties. The Sea Waybills attached to Fluence’s 3 Complaint and the Becker Decl. were issued by DB Schenker, names M/V BBC Finland 4 as the Vessel, and Fluence alleges DB Schenker agreed to accept and safely load and carry 5 the Cargo aboard the Vessel in Hai Phong, Vietnam and to deliver the Cargo to San Diego, 6 California. Compl. at 5, ¶ 19. Fluence alleges “[p]ursuant to its obligations as carrier,” the 7 Vessel “had the non-delegable duty to safely load, stow, carry, and deliver the Cargo in 8 good order and condition to San Diego in accordance with the terms and conditions of the 9 Sea Waybills.” Id. at 5, ¶ 20. Fluence further alleges the “Vessel is liable in rem to perform 10 its obligations under the Sea Waybills . . . .” Id. at 8, ¶ 41. 11 Although Fluence alleges the Vessel is liable under the Sea Waybills, pursuant to 12 maritime law, Owner alleges it was unaware of the Sea Waybills and makes legal 13 arguments as to why it is not bound by them. Whether Owner is liable under the Sea 14 Waybills is a factual dispute inappropriate for determination on Owner’s Rule E(4)(f) 15 Motion. See Greger Leasing Corp. v. Barge PT. Potrero, No. C-05-5117 SC, 2006 WL 16 889537, at *3 (N.D. Cal. Apr. 5, 2006) (“Despite the repeated efforts of the parties to turn 17 a limited adversary hearing into a full-blown trial on the merits, the Court’s inquiry at this 18 point remains focused on the narrow issue of whether [the] [p]laintiff has demonstrated 19 probable cause to believe a lien exists.”). 20 Regarding the contract of carriage, Fluence alleges the Vessel “agreed, under a 21 maritime contract of carriage, to carry, handle, and act as the bailees of the Cargo, and to 22 discharge the Cargo at San Diego, California in good order and condition,” which the 23 Vessel failed to do. Compl. at 8, ¶ 40, 42. Reading the Complaint in the light most 24 favorable to Fluence, it alleges a legally enforceable contract of carriage to which the 25 Vessel was bound. Accordingly, the Court DENIES Owner’s Motion seeking a Rule 26 E(4)(f) dismissal of Fluence’s breach of contract claim. 27 2. Negligence Claim 28 Regarding Fluence’s negligence claim, Owner argues it is “styled as one for 1 negligence under a bailment theory, [but] is caught up in the broad sweep of the contract 2 cause of action.” Motion at 15. Fluence argues its negligence “claim provides an 3 independent basis” for the Vessel’s in rem liability, and that Owner failed to address the 4 negligence claim in its Motion. Oppo. at 15. Owner replies that because Fluence 5 incorporates its contractual allegations into its allegations for negligence, the negligence 6 claim is “nominal” and cannot be extricated from its contract claim. Reply at 7–8. 7 Owner is correct in that Fluence incorporates its contract allegations into its claim 8 for negligence. See Compl. at 9, ¶ 47. However, Fluence makes additional allegations. 9 Fluence alleges the Vessel owed it “a duty of care to preserve, not damage and not lose the 10 Cargo,” and that “[u]nder the circumstances [as described in the factual and breach of 11 contract allegations], the Defendant V[essel] negligently breached its duty as carrier, 12 handler, or bailee with respect to the cargo.” Id. at 9, ¶¶ 48–49. Fluence further pleads 13 “the negligence, failures and omissions of Defendant Vessel, as aforesaid and as specified 14 herein, give rise to an admiralty claim in rem . . . against the Vessel.” Id. at 9, ¶ 51. 15 The Vessel received Fluence’s Cargo in good condition, and the Cargo was damaged 16 while aboard the Vessel. Id. at 3–4, ¶¶ 10. Fluence states these facts as material to all 17 causes of action and incorporates them into its negligence claim—not just its claim for 18 breach of contract. Id. Fluence further alleges the Vessel’s conduct was the proximate 19 cause of the damages. Id. at 9, ¶ 52. Thus, Fluence does not rely solely on its breach of 20 contract allegations in pleading its negligence cause of action. See id. at 9, ¶¶ 48–53. It 21 would be incorrect to dismiss Fluence’s negligence claim because the facts underlying it 22 overlap with those alleged in Fluence’s breach of contract claim. Albany Ins. Co. v. M.V. 23 Istrian Exp., 61 F.3d 709, 710 (9th Cir. 1995) (citations omitted) (“[The Ninth] Circuit 24 recognizes a maritime tort lien irrespective of contractual obligations.”); All Alaskan 25 Seafoods, Inc. v. M/V Sea Producer, 882 F.2d 425, 430 (9th Cir. 1989) (“If [the vessel’s 26 operator] breached its duty of care with respect to [the shipper] then that breach of duty 27 can give rise to tort liability irrespective of contract obligations between the parties.”). 28 Accordingly, the Court DENIES Owner’s Motion seeking a Rule E(4)(f) dismissal of 1 || Fluence’s negligence claim. 2||V. CONCLUSION 3 For the foregoing reasons, and after considering oral argument and all briefing and 4 || Exhibits filed in connection to the instant Motion to Vacate the Vessel Arrest and Dismiss 5 Action, the Court ORDERS as follows: 6 lL. Owner’s Motion to Vacate the Vessel Arrest and Dismiss as to Fluence’s 7 || Breach of Contract Claim is DENIED. 8 2. Owner’s Motion to Vacate the Vessel Arrest and Dismiss as to Fluence’s 9 || Negligence Claim is DENIED. 10 3. Owner’s Motion to Vacate the Vessel Arrest and Dismiss based on the forum- 11 |} selection clause is DENIED. 12 13 IT IS SO ORDERED. 14|| DATED: February 8, 2022 gute, 15 HON. ROGER T. BENITEZ 6 United States District Judge 17 18 19 20 21 22 23 24 25 26 27 28 -20-