(PS) Gianelli v. Schoenfeld
This text of (PS) Gianelli v. Schoenfeld ((PS) Gianelli v. Schoenfeld) is published on Counsel Stack Legal Research, covering District Court, E.D. California primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.
Opinion
1 2 3 4 5 6 7 8 UNITED STATES DISTRICT COURT 9 FOR THE EASTERN DISTRICT OF CALIFORNIA 10 11 SHEILA GIANELLI, No. 2:21–cv–0477–JAM–KJN PS 12 Plaintiff, ORDER & FINDINGS AND RECOMMENDATIONS 13 v. (ECF No. 17) 14 RONALD STEVEN SCHOENFELD, et al., 15 Defendants. 16
17 18 Presently before the court is plaintiff’s motion to remand this case to state court.1 (ECF 19 No. 17.) All four of the active defendants in this case filed a joint opposition, to which plaintiff 20 replied.2 (ECF Nos. 23, 26.) The court took the motion under submission pursuant to Local 21 Rule 230(g). (ECF No. 25.) For the following reasons, the undersigned recommends denying the 22 motion to remand. 23 1 Because plaintiff is representing herself, this action is referred to the undersigned for all pretrial 24 proceedings, pursuant to 28 U.S.C. § 636, Federal Rule of Civil Procedure 72, and Local Rule 302(c)(21). 25
26 2 The court accepts plaintiff’s reply brief although it was filed six days late, on May 19, 2021. See Local Rule 230(d) (reply due 7 days preceding hearing date, making the deadline May 13, 27 2021 in this case). The court will not consider untimely filings in the future, however. The court also notes that the five-page reply brief plaintiff submitted contains two page 3s, one before 28 page 4 and one after, and does not contain a page 5 with a final signature line. (See ECF No. 26.) 1 BACKGROUND 2 On January 29, 2021, plaintiff Sheila Gianelli filed this suit in California state court, 3 naming five defendants. (ECF No. 1.1 (Complaint in Gianelli v. Schoenfeld, et al., Cal. Sup. Ct., 4 San Joaquin Cty., No. STK-CV-UMR-2021-0000849).) The complaint asserts six state 5 employment law causes of action and two federal causes of action for violations of the Racketeer 6 Influenced and Corrupt Organizations Act (“RICO”). (Id. at 15-26.) The complaint generally 7 stems from alleged retaliation plaintiff experienced at work after reporting a co-worker’s 8 conspiracy to defraud their mutual employer, Pacific Gas and Electric Company (“PG&E”).3 9 Over the next several weeks, plaintiff filed in the state court proofs of service of the 10 summons and complaint on each of the five defendants. (ECF No. 18 (Gianelli RJN) at 4-20, 11 Exs. A-E).4 As reflected in the proofs of service, process servers personally served the four 12 individual defendants as follows: defendant Nick Dujmovich was served in Texas on January 30, 13 2021 (ECF No. 18 at 4, Ex. A); defendant Ronald Schoenfeld was served in Arizona on 14 February 6, 2021 (id. at 7, Ex. B); defendant Debra Silver was served in California on 15 February 15, 2021 (id. at 16, Ex. D); and defendant Lance Schultz was served in California on 16 February 19, 2021 (id. at 19, Ex. E). As for the corporate defendant, PG&E, the proof of service 17 shows that the company was served by substituted service on February 17, 2021. (Id. at 11, 18 Ex. C.) 19 The case proceeded in state court for a short while. As relevant to this motion, on 20 March 11, 2021, counsel for PG&E, Mr. Bren Thomas—who also represents defendants Schultz 21 and Dujmovich—filed in the state court a Notification of Effective Date of Chapter 11 Plan and 22 Imposition of Plan Injunction (“Notification of Plan Effective Date”). (ECF No. 23.2; see ECF 23
24 3 The court reserves recitation of the full factual allegations for resolution of the co-pending motions to dismiss this case. (ECF Nos. 6, 19.) 25
26 4 The court, on its own motion, takes judicial notice of the state court docket, which is a matter of public record, and all state court filings provided in support of the parties’ briefs. See Porter v. 27 Ollison, 620 F.3d 952, 955 n.1 (9th Cir. 2010) (taking judicial notice of docket in state court proceedings); United States v. Howard, 381 F.3d 873, 876 n.1 (9th Cir. 2004) (courts may take 28 judicial notice of public records, including court records from another case). 1 No. 23.1 (Thomas Decl.) ¶ 3.) The three-page Notification of Plan Effective Date advised the 2 state court and plaintiff of several key details of PG&E’s ongoing bankruptcy proceeding and its 3 effect on plaintiff’s claims against PG&E. The Notification of Plan Effective Date stated that on 4 January 29, 2019, PG&E Corporation and PG&E each filed in the Northern District of California 5 petitions for bankruptcy under Chapter 11; that the bankruptcy court confirmed PG&E’s 6 Chapter 11 Plan of Reorganization on June 20, 2020; that the effective date of the Plan occurred 7 on July 1, 2020, and as a result the Plan had been “substantially consummated,” and PG&E had 8 been “revested with [its] property, and discharged from [its] debts” as provided in the Plan; that 9 prior to the July 1, 2020 Plan effective date, an automatic stay was in place under 11 U.S.C. 10 § 362(a); and that as of the confirmation of the Plan, a permanent injunction applied to enjoin 11 plaintiff’s claims against PG&E. (ECF No. 23.2 at 2-4.) Beneath counsel’s signature on the 12 Notification of Plan Effective Date, an italicized statement reads: “No general appearance 13 intended; appearance for limited purpose of notifying court that action is enjoined as to PG&E.” 14 (Id. at 4.) 15 A few other state court filings, all regarding defendant Dujmovich, deserve note. On 16 March 15, 2021, with no answer or appearance by Dujmovich, plaintiff requested entry of default 17 against him, which the state court entered the same day (without granting default judgment). 18 (ECF No. 17 at 8; ECF No. 23.1 (Thomas Decl.) ¶ 4.) On March 22, 2021, Dujmovich objected 19 to entry of default on the ground that there was no personal jurisdiction over him, as he is 20 domiciled in Texas and does not have sufficient minimum contacts with California. (ECF 21 No. 17.1 (Gianelli Decl.) at 10-13, Ex. B.) And on March 30, 2021, Dujmovich moved the state 22 court to quash the summons served on him—so as to set aside the default—for lack of personal 23 jurisdiction. (ECF No. 18 (Gianelli RJN) at 22-30, Ex. F; ECF No. 23.3 (Thomas Decl.) ¶ 6.) 24 Meanwhile, on March 16, 2021, defendant Silver—represented by her own separate 25 counsel, Mr. Peter Rausch—filed a notice of removal removing the case to this court (“Notice of 26 Removal”). (ECF No. 1.) The Notice of Removal confirmed that defendant Silver first received 27 a copy of the complaint when she was served on February 15, 2021, and it invoked this court’s 28 subject-matter jurisdiction based on the federal questions raised by the RICO claims. (Id. at 2.) 1 Regarding the other defendants’ consent, the Notice of Removal stated: “All other defendant(s) 2 who have been served with Summons and complaint [sic] have joined in this Notice of Removal, 3 as evidenced by the Joinders of defendants Ronald Steven Schoenfeld and Lance Schultz, filed 4 concurrently herewith.”5 (Id.) It made no express mention of the other two defendants, 5 Dujmovich and PG&E. 6 On April 8, 2021, Dujmovich made his first appearance in this court by filing a joinder to 7 the Notice of Removal. (ECF No. 13.) The joinder specified that “By this joinder, Mr. 8 Dujmovich does not waive any objections as to service, jurisdiction, or venue, or any other 9 defenses or objections to this action. Mr. Dujmovich intends no admission or fact, law or liability 10 by this joinder, and expressly reserves all defenses, motions, and/or pleas.” (Id.
Free access — add to your briefcase to read the full text and ask questions with AI
1 2 3 4 5 6 7 8 UNITED STATES DISTRICT COURT 9 FOR THE EASTERN DISTRICT OF CALIFORNIA 10 11 SHEILA GIANELLI, No. 2:21–cv–0477–JAM–KJN PS 12 Plaintiff, ORDER & FINDINGS AND RECOMMENDATIONS 13 v. (ECF No. 17) 14 RONALD STEVEN SCHOENFELD, et al., 15 Defendants. 16
17 18 Presently before the court is plaintiff’s motion to remand this case to state court.1 (ECF 19 No. 17.) All four of the active defendants in this case filed a joint opposition, to which plaintiff 20 replied.2 (ECF Nos. 23, 26.) The court took the motion under submission pursuant to Local 21 Rule 230(g). (ECF No. 25.) For the following reasons, the undersigned recommends denying the 22 motion to remand. 23 1 Because plaintiff is representing herself, this action is referred to the undersigned for all pretrial 24 proceedings, pursuant to 28 U.S.C. § 636, Federal Rule of Civil Procedure 72, and Local Rule 302(c)(21). 25
26 2 The court accepts plaintiff’s reply brief although it was filed six days late, on May 19, 2021. See Local Rule 230(d) (reply due 7 days preceding hearing date, making the deadline May 13, 27 2021 in this case). The court will not consider untimely filings in the future, however. The court also notes that the five-page reply brief plaintiff submitted contains two page 3s, one before 28 page 4 and one after, and does not contain a page 5 with a final signature line. (See ECF No. 26.) 1 BACKGROUND 2 On January 29, 2021, plaintiff Sheila Gianelli filed this suit in California state court, 3 naming five defendants. (ECF No. 1.1 (Complaint in Gianelli v. Schoenfeld, et al., Cal. Sup. Ct., 4 San Joaquin Cty., No. STK-CV-UMR-2021-0000849).) The complaint asserts six state 5 employment law causes of action and two federal causes of action for violations of the Racketeer 6 Influenced and Corrupt Organizations Act (“RICO”). (Id. at 15-26.) The complaint generally 7 stems from alleged retaliation plaintiff experienced at work after reporting a co-worker’s 8 conspiracy to defraud their mutual employer, Pacific Gas and Electric Company (“PG&E”).3 9 Over the next several weeks, plaintiff filed in the state court proofs of service of the 10 summons and complaint on each of the five defendants. (ECF No. 18 (Gianelli RJN) at 4-20, 11 Exs. A-E).4 As reflected in the proofs of service, process servers personally served the four 12 individual defendants as follows: defendant Nick Dujmovich was served in Texas on January 30, 13 2021 (ECF No. 18 at 4, Ex. A); defendant Ronald Schoenfeld was served in Arizona on 14 February 6, 2021 (id. at 7, Ex. B); defendant Debra Silver was served in California on 15 February 15, 2021 (id. at 16, Ex. D); and defendant Lance Schultz was served in California on 16 February 19, 2021 (id. at 19, Ex. E). As for the corporate defendant, PG&E, the proof of service 17 shows that the company was served by substituted service on February 17, 2021. (Id. at 11, 18 Ex. C.) 19 The case proceeded in state court for a short while. As relevant to this motion, on 20 March 11, 2021, counsel for PG&E, Mr. Bren Thomas—who also represents defendants Schultz 21 and Dujmovich—filed in the state court a Notification of Effective Date of Chapter 11 Plan and 22 Imposition of Plan Injunction (“Notification of Plan Effective Date”). (ECF No. 23.2; see ECF 23
24 3 The court reserves recitation of the full factual allegations for resolution of the co-pending motions to dismiss this case. (ECF Nos. 6, 19.) 25
26 4 The court, on its own motion, takes judicial notice of the state court docket, which is a matter of public record, and all state court filings provided in support of the parties’ briefs. See Porter v. 27 Ollison, 620 F.3d 952, 955 n.1 (9th Cir. 2010) (taking judicial notice of docket in state court proceedings); United States v. Howard, 381 F.3d 873, 876 n.1 (9th Cir. 2004) (courts may take 28 judicial notice of public records, including court records from another case). 1 No. 23.1 (Thomas Decl.) ¶ 3.) The three-page Notification of Plan Effective Date advised the 2 state court and plaintiff of several key details of PG&E’s ongoing bankruptcy proceeding and its 3 effect on plaintiff’s claims against PG&E. The Notification of Plan Effective Date stated that on 4 January 29, 2019, PG&E Corporation and PG&E each filed in the Northern District of California 5 petitions for bankruptcy under Chapter 11; that the bankruptcy court confirmed PG&E’s 6 Chapter 11 Plan of Reorganization on June 20, 2020; that the effective date of the Plan occurred 7 on July 1, 2020, and as a result the Plan had been “substantially consummated,” and PG&E had 8 been “revested with [its] property, and discharged from [its] debts” as provided in the Plan; that 9 prior to the July 1, 2020 Plan effective date, an automatic stay was in place under 11 U.S.C. 10 § 362(a); and that as of the confirmation of the Plan, a permanent injunction applied to enjoin 11 plaintiff’s claims against PG&E. (ECF No. 23.2 at 2-4.) Beneath counsel’s signature on the 12 Notification of Plan Effective Date, an italicized statement reads: “No general appearance 13 intended; appearance for limited purpose of notifying court that action is enjoined as to PG&E.” 14 (Id. at 4.) 15 A few other state court filings, all regarding defendant Dujmovich, deserve note. On 16 March 15, 2021, with no answer or appearance by Dujmovich, plaintiff requested entry of default 17 against him, which the state court entered the same day (without granting default judgment). 18 (ECF No. 17 at 8; ECF No. 23.1 (Thomas Decl.) ¶ 4.) On March 22, 2021, Dujmovich objected 19 to entry of default on the ground that there was no personal jurisdiction over him, as he is 20 domiciled in Texas and does not have sufficient minimum contacts with California. (ECF 21 No. 17.1 (Gianelli Decl.) at 10-13, Ex. B.) And on March 30, 2021, Dujmovich moved the state 22 court to quash the summons served on him—so as to set aside the default—for lack of personal 23 jurisdiction. (ECF No. 18 (Gianelli RJN) at 22-30, Ex. F; ECF No. 23.3 (Thomas Decl.) ¶ 6.) 24 Meanwhile, on March 16, 2021, defendant Silver—represented by her own separate 25 counsel, Mr. Peter Rausch—filed a notice of removal removing the case to this court (“Notice of 26 Removal”). (ECF No. 1.) The Notice of Removal confirmed that defendant Silver first received 27 a copy of the complaint when she was served on February 15, 2021, and it invoked this court’s 28 subject-matter jurisdiction based on the federal questions raised by the RICO claims. (Id. at 2.) 1 Regarding the other defendants’ consent, the Notice of Removal stated: “All other defendant(s) 2 who have been served with Summons and complaint [sic] have joined in this Notice of Removal, 3 as evidenced by the Joinders of defendants Ronald Steven Schoenfeld and Lance Schultz, filed 4 concurrently herewith.”5 (Id.) It made no express mention of the other two defendants, 5 Dujmovich and PG&E. 6 On April 8, 2021, Dujmovich made his first appearance in this court by filing a joinder to 7 the Notice of Removal. (ECF No. 13.) The joinder specified that “By this joinder, Mr. 8 Dujmovich does not waive any objections as to service, jurisdiction, or venue, or any other 9 defenses or objections to this action. Mr. Dujmovich intends no admission or fact, law or liability 10 by this joinder, and expressly reserves all defenses, motions, and/or pleas.” (Id. at 2.) PG&E has 11 not entered any appearance in the action in this court—and did not participate in the state court 12 proceeding after filing the Notification of Plan Effective Date. 13 On April 15, 2021, exactly 30 days after the Notice of Removal, plaintiff timely filed the 14 instant motion to remand, asserting procedural defects in the removal. (ECF No. 17.) See 15 28 U.S.C. § 1447(c) (providing 30 days to move to remand “on the basis of any defect other than 16 lack of subject matter jurisdiction”).6 17 LEGAL STANDARD 18 A defendant generally may remove any civil action from state court to federal district 19 court if the district court has original jurisdiction over the matter. 28 U.S.C. § 1441(a). “The 20 mechanics and requirements for removal are governed by 28 U.S.C. § 1446.” Kuxhausen v. 21 BMW Fin. Servs. NA LLC, 707 F.3d 1136, 1139 (9th Cir. 2013). To remove an action, the 22
23 5 No separate joinders were “concurrently” filed, but defendant Schoenfeld filed his joinder to the notice of removal the next day, March 17, 2021 (ECF No. 5), and defendant Schultz filed his 24 joinder on April 1, 2021 (ECF No. 11). Mr. Rausch attests that he attempted to e-file joinders on behalf of Schultz and Schoenfeld as authorized by their respective attorneys, but the court’s 25 clerk’s office rejected them because they had to be filed by each party’s own attorney. (ECF 26 No. 23.3 (Rausch Decl.) ¶ 7.) Plaintiff does not challenge the timing or effect of these joinders.
27 6 Two motions to dismiss—one by defendant Silver, and a joint motion by defendants Schultz and Dujmovich—are also pending and will be addressed in a subsequent order after their briefing is 28 complete. (See ECF Nos. 6, 19.) 1 removing defendant(s) “shall file [in the appropriate district court] a notice of removal signed 2 pursuant to Rule 11 of the Federal Rules of Civil Procedure and containing a short and plain 3 statement of the grounds for removal, together with a copy of all process, pleadings, and orders 4 served upon such defendant or defendants in such action.” 28 U.S.C. § 1446(a). Each defendant 5 has 30 days after receiving the initial pleading or summons evidencing the case’s removability to 6 file a notice of removal. 28 U.S.C. § 1446(b)(1), (b)(2)(B); see Destfino v. Reiswig, 630 F.3d 7 952, 955-56 (9th Cir. 2011). 8 When there is more than one defendant in the action, “all defendants who have been 9 properly joined and served must join in or consent to the removal of the action.” 28 U.S.C. 10 § 1446(b)(2)(A); see Destfino, 630 F.3d at 956; Emrich v. Touche Ross & Co., 846 F.2d 1190, 11 1193 n.1 (9th Cir. 1988). This is commonly referred to as the unanimity requirement, or rule of 12 unanimity. Lewis v. City of Fresno, 627 F. Supp. 2d 1179, 1182 (E.D. Cal. 2008). The Ninth 13 Circuit does not require each defendant to submit written notice of consent, so long as at least one 14 defendant’s attorney certifies in the notice of removal that all defendants consent to removal. 15 Proctor v. Vishay Intertechnology Inc., 584 F.3d 1208, 1224-25 (9th Cir. 2009) (“One 16 defendant’s timely removal notice containing an averment of the other defendants’ consent and 17 signed by an attorney of record is sufficient.”). And, as implied in the rule itself, there are 18 exceptions to the unanimity requirement. Most relevant to this case is the exception for 19 defendants who were not properly served before notice of removal. See Destfino, 630 F.3d at 957 20 (“Because none of the non-joining defendants was properly served, their absence from the 21 removal notice did not render the removal defective.”); Salveson v. W. States Bankcard Ass’n, 22 731 F.2d 1423, 1429 (9th Cir. 1984) (“Our circuit rule is that a party not served need not be 23 joined [in the petition for removal.]”), superseded by statute on other grounds. Absent an 24 applicable exception, however, failure to comply with the unanimity requirement renders the 25 removal procedurally defective. See Emrich, 846 F.2d at 1193 n.1. 26 “A correlate rule to the unanimity requirement and its exceptions logically follows . . . .” 27 Mitchell v. Paws Up Ranch, LLC, 597 F. Supp. 2d 1132, 1135 (D. Mont. 2009). “Where fewer 28 than all the defendants have joined in a removal action, the removing party has the burden under 1 section 1446(a) to explain affirmatively the absence of any co-defendants in the notice for 2 removal.” Prize Frize, Inc. v. Matrix (U.S.) Inc., 167 F.3d 1261, 1266 (9th Cir. 1999), superseded 3 by statute on other grounds as stated in Abrego Abrego v. Dow Chem. Co., 443 F.3d 676, 681 4 (9th Cir. 2006). “If, for example, named co-defendants believe an exception to the unanimity rule 5 applies to them and therefore they are not required to join in the notice of removal, the removing 6 defendants should explain this in their notice.” Paws Up Ranch, 597 F. Supp. 2d at 1135-36. 7 Failure to explain the absence of consent from any co-defendant is also a procedural defect. Prize 8 Frize, 167 F.3d at 1266 (holding that a notice of removal was “facially deficient” for not 9 explaining why all non-joining defendants had not consented). 10 “[T]he defendant always has the burden of establishing that removal is proper.” Moore- 11 Thomas v. Alaska Airlines, Inc., 553 F.3d 1241, 1244 (9th Cir. 2009). “If the removal suffers 12 from procedural defects, the plaintiff is responsible for bringing those defects to the attention of 13 the district court in a timely motion to remand.” Polo v. Innoventions Int’l, LLC, 833 F.3d 1193, 14 1196 (9th Cir. 2016).7 “Once the plaintiff raises a procedural defect in the removal, it is the 15 removing defendant’s burden to show compliance with the pertinent procedural requirement.” 16 Smith v. Furniture Deals, Inc., No. 1:19-CV-1557-AWI-EPG, 2020 WL 429130, at *3 (E.D. Cal. 17 Jan. 28, 2020). 18 DISCUSSION 19 Plaintiff argues that remand is warranted because (1) the Notice of Removal failed to 20 affirmatively explain the absence of consent by Dujmovich and PG&E, (2) not all defendants 21 consent to removal, based on PG&E’s silence and Dujmovich’s purportedly “ambiguous” and 22 arguably untimely subsequent joinder to the notice of removal, and (3) this case is better 23 adjudicated in state court. (ECF No. 17 at 5-10.) Because Dujmovich and PG&E’s different 24 circumstances dictate different analyses, the court addresses these arguments separately for each 25 defendant, beginning with PG&E. 26
27 7 District courts cannot “remand a case sua sponte for a non-jurisdictional defect in procedure.” Kelton Arms Condo. Owners Ass’n, Inc. v. Homestead Ins. Co., 346 F.3d 1190, 1191 (9th Cir. 28 2003). 1 A. There Was No Need to Obtain PG&E’s Consent to Removal, or to Explain the 2 Absence of PG&E’s Consent to Removal 3 Plaintiff is correct that (1) PG&E never filed anything indicating it joins in or consents to 4 removal, and (2) defendant Silver’s Notice of Removal did not explain the absence of PG&E’s 5 consent. (ECF No. 17 at 5.) However, neither ground presents a basis for remand because of 6 PG&E’s bankruptcy discharge. 7 1. Lack of Consent from PG&E 8 The court concludes that the “non-served defendant exception” to the rule of unanimity 9 applies to excuse PG&E’s failure to join in removal here—but for a slightly different reason than 10 that asserted by defendants. Defendants argue that any purported service on PG&E was 11 ineffective because “PG&E had filed a petition for bankruptcy in 2020, such that an automatic 12 stay pursuant to 11 U.S.C. § 362(a) was in effect as to Plaintiff’s claims against PG&E,” and a 13 bankruptcy debtor cannot be served with process while an automatic stay is in effect. (ECF 14 No. 23 at 6.) This may be true as a matter of law, but defendants get the facts wrong. 15 First, PG&E filed its voluntary petition for Chapter 11 bankruptcy in 2019, not 2020. See 16 In re: PG&E Corp. and Pacific Gas and Electric Co., No. 19-30088 (Bankr. N.D. Cal., filed 17 Jan. 29, 2019), ECF No. 1.8 Moreover, based on the limited information provided to this court 18 regarding that bankruptcy case, it appears that PG&E was actually discharged from its debts 19 many months before plaintiff filed her case on January 29, 2021, and served PG&E on 20 February 17, 2021—so the automatic stay was no longer in effect by then. 21 In response to the motion to remand, defendants request judicial notice of the Order 22 Confirming Debtors’ and Shareholder Proponents’ Joint Chapter 11 Plan of Reorganization Dated 23 June 19, 2020 (“Confirmation Order”)—and its attached Plan of Reorganization—entered in the 24 bankruptcy case, In re: PG&E Corp., No. 19-30088 (Bankr. N.D. Cal.), at ECF No. 8053. 25
26 8 The jointly administered bankruptcy cases were filed out of concerns over the utility companies’ potential liability for causing wildfires that ravaged California in 2017 and 2018. Under the terms 27 of the since-confirmed Chapter 11 Plan of Reorganization, PG&E and PG&E Corporation agreed, among other things, to contribute billions of dollars to certain newly established fire trusts and 28 funds. (ECF No. 24.1 at 25, 27.) 1 (Defendants’ RJN, ECF Nos. 24-24.1.) That request is granted. According to both the 2 Confirmation Order and the identically worded relevant provisions of the Chapter 11 Plan itself, 3 subject to certain inapplicable exceptions, “[u]pon the Effective Date and in consideration of the 4 distributions to be made under the Plan, except as otherwise expressly provided in the Plan or in 5 this Confirmation Order, the Debtors shall be discharged to the fullest extent permitted by 6 section 1141 of the Bankruptcy Code . . . .” (ECF No. 24.1 at 48, ¶ 49 (“Discharge of the 7 Debtors”); id. at 151, § 10.3.) 8 Section 1141 of the Bankruptcy Code governs the effect of an order of confirmation of a 9 plan of reorganization under Chapter 11. Unless otherwise provided in a confirmation order or in 10 a reorganization plan, “the confirmation of a plan . . . discharges the debtor from any debt that 11 arose before the date of such confirmation.” 11 U.S.C. § 1141(d)(1). The Confirmation Order in 12 this case specified that discharge would take effect upon the Effective Date, which ultimately 13 occurred on July 1, 2020. See In re: PG&E Corp., No. 19-30088 (Bankr. N.D. Cal.), ECF 14 No. 8252 (Notice Regarding Entry of Confirmation Order and Occurrence of Effective Date, filed 15 July 2, 2020). Thus, the automatic stay appears to have terminated as of July 1, 2020, more than 16 six months before plaintiff served PG&E with her state court summons and complaint. See 17 11 U.S.C. § 362(c)(2) (automatic stay “continues until the earliest of--(A) the time the case is 18 closed; (B) the time the case is dismissed; or (C) if the case is . . . a case under chapter 9, 11, 12, 19 or 13 of this title, the time a discharge is granted or denied”) (emphasis added); In re Howes, 20 246 B.R. 280, 290 (Bankr. W.D. Ky. 2000) (“It is clear that under § 362(c) the automatic stay is 21 not unlimited in its duration, but terminates upon the earliest of three events: (1) the closing of the 22 case; (2) the dismissal of the case; or (3) the entry or denial of a discharge.”). 23 Defendants’ single paragraph of argument on this point provides no explanation for their 24 position that the automatic stay was still in effect at the time of plaintiff’s substituted service on 25 PG&E. (ECF No. 23 at 6.) Nevertheless, even assuming the automatic stay terminated on July 1, 26 2020, it was immediately replaced with the customary discharge injunction, which for the 27 following reasons also prevented plaintiff’s later service on PG&E from having legal effect. 28 /// 1 Section 524 of the Bankruptcy Code provides in relevant part that a “discharge” 2 (1) voids any judgment at any time obtained, to the extent that such judgment is a determination of the personal liability of the debtor 3 with respect to any debt discharged under section . . . 1141 . . . of this title, whether or not discharge of such debt is waived; [and] 4 (2) operates as an injunction against the commencement or 5 continuation of an action, the employment of process, or an act, to collect, recover or offset any such debt as a personal liability of the 6 debtor, whether or not discharge of such debt is waived . . . . 7 11 U.S.C. § 524(a). “Once a discharge is entered, the permanent injunction of § 524 replaces the 8 automatic stay of § 362 and prevents creditors from ever collecting a discharged debt.” In re 9 Howes, 246 B.R. at 290 (emphasis and internal quotation marks omitted); In re Jones, 348 B.R. 10 715, 718 (Bankr. E.D. Va. 2006) (explaining that when discharge is granted or denied, “the 11 automatic stay is replaced by the discharge injunction” (citing § 524(a)). 12 “In this context, a debt is defined as liability on a claim,” In re Jackson, 2017 WL 13 2371111, at *4 (Bankr. D. Conn. May 30, 2017), and the term “claim” means “right to payment, 14 whether or not such right is reduced to judgment, liquidated, unliquidated, fixed, contingent, 15 matured, unmatured, disputed, undisputed, legal, equitable, secured, or unsecured.” 11 U.S.C. 16 § 101(5)(A). “For purposes of the discharge in bankruptcy, a claim arises at the time of the 17 events giving rise to the claim, not at the time plaintiff is first able to file suit on the claim.” In re 18 Lombard Flats, LLC, No. BK 09-32219 DM, 2014 WL 3963009, at *7 (N.D. Cal. Aug. 13, 2014) 19 (citing In re Heilman, 430 B.R. 213, 219-20 (9th Cir. B.A.P. 2010)). 20 Here, although plaintiff did not sue PG&E until January 2021, she is asserting a legal right 21 to payment based on events that concluded in August 2017. (See ECF No. 1.1 ¶¶ 35-36 (alleging 22 that retaliation ended and her career “flourished” after she was approved for a new role on 23 August 7, 2017).) Thus, any claim plaintiff held against PG&E for its part in those events 24 asserted in the instant lawsuit arose well before PG&E filed its Chapter 11 bankruptcy petition in 25 January 2019. And PG&E’s liability on that claim—i.e., its “debt” to plaintiff—was apparently 26 discharged (at the latest) on the Chapter 11 Plan effective date of July 1, 2020. 27 By statute, this discharge automatically enjoined “the commencement or continuation of 28 an action, the employment of process, or an act, to collect, recover or offset” that pre-petition 1 debt. 11 U.S.C. § 524(a)(2). In addition, the bankruptcy court issued its own discharge 2 injunction, as permitted by 11 U.S.C. § 524(g)(1)(A) (“After notice and hearing, a court that 3 enters an order confirming a plan of reorganization under chapter 11 may issue, in connection 4 with such order, an injunction in accordance with this subsection to supplement the injunctive 5 effect of a discharge under this section.”). As stated in the Confirmation Order and the identically 6 worded relevant provisions of the Chapter 11 Plan, “[u]pon the Effective Date, all holders of 7 Claims against or Interests in the Debtors shall be forever precluded and enjoined, pursuant to 8 section 524 of the Bankruptcy Code, from prosecuting or asserting any such discharged Claim 9 against or Interest in the Debtors.” (ECF No. 24.1 at 48, ¶ 49 (“Discharge of the Debtors”); id. at 10 151, § 10.3.) The Confirmation Order and the Chapter 11 Plan further specify that (again subject 11 to inapplicable exceptions) as of the entry of the Confirmation Order and “subject to the 12 occurrence of the Effective Date”: 13 [A]ll Entities who have held, hold, or may hold Claims[9] or Interests are, with respect to any such Claim or Interest, permanently 14 enjoined after the entry of the Confirmation Order from: (i) commencing, conducting, or continuing in any manner, directly 15 or indirectly, any suit, action, or other proceeding of any kind (including, any proceeding in a judicial, arbitral, administrative, or 16 other forum) against or affecting, directly or indirectly, a Debtor, . . . ; and (v) commencing or continuing, in any manner or in 17 any place, any action that does not comply with or is inconsistent with the provisions of the Plan . . . . 18 (ECF No. 24.1 at 49-50, ¶ 52(a) (emphasis added); id. at 152, § 10.6(a).) 19 These provisions of the Plan and Confirmation Order were highlighted in PG&E’s 20 March 11, 2021 Notification of Plan Effective Date, filed in the state court in this action. (ECF 21 No. 23.2 at 3.) The Notification of Plan Effective Date stated that none of the specific limited 22 exceptions in the Plan “apply to the claim or claims asserted against PG&E in this action,” and 23 accordingly “the Plan injunction applies to and enjoins the continued prosecution of this action 24 except pursuant to the plan and the Chapter 11 claims reconciliation process.” (Id. at 4 (emphasis 25 26 9 The Plan defines “Entities” and “Claims” the same way the Bankruptcy Code does. (ECF 27 No. 24.1 at 82, ¶ 1.25 and 85, ¶ 1.61.) See 11 U.S.C. §§ 101(5) (definition quoted above), 101(15) (“The term ‘entity’ includes person, estate, trust, governmental unit, and United States 28 trustee.”). 1 omitted).) Therefore, even though defendants are likely wrong about the duration of the 2 automatic stay, the discharge injunction similarly blocked plaintiff from prosecuting her claims 3 against PG&E.10 (ECF No. 24.1 at 49-50, ¶ 52(a) (permanently enjoining the “commencing, 4 conducting, or continuing in any manner . . . any suit . . . against . . . a Debtor”).) See 11 U.S.C. 5 § 524(a)(2) (discharge “operates as an injunction against the commencement or continuation of an 6 action, the employment of process, or an act, to collect, recover or offset” a discharged debt 7 (emphasis added)). 8 The key question is whether plaintiff’s service of process in a lawsuit seeking recovery for 9 a pre-bankruptcy-petition claim against a debtor (PG&E) can be effective in the face of a pre- 10 existing discharge injunction. If so, PG&E would be a properly served defendant whose consent 11 is required for removal; if not, PG&E’s lack of consent is irrelevant under the non-served 12 defendant exception to the rule of unanimity. 13 For the following reasons, the court concludes that the 2020 discharge injunction means 14 that plaintiff’s service on PG&E in 2021 was void from the moment it occurred. Because that 15 service was without legal effect, PG&E is not a “properly . . . served” defendant whose consent is 16 required for removal. See 28 U.S.C. § 1446(b)(2)(A); Destfino, 630 F.3d at 956. 17 The court’s independent research reveals no federal cases determining the validity of 18 service of process in a lawsuit for claims covered by a discharge injunction.11 An extensive 2005 19 opinion by the Bankruptcy Appellate Panel (“BAP”) of the Ninth Circuit, however, strongly 20 supports viewing such service of process as void. See In re Gurrola, 328 B.R. 158 (9th Cir. 21 B.A.P. 2005).12 In Gurrola, the BAP chronicled the legislative history of § 524(a)(1) to its
22 10 Defendants’ present position that the automatic stay was still in effect at the commencement of 23 plaintiff’s suit also runs counter to PG&E’s own statements in the March 11th Notification of Plan Effective Date. That notice indicates the automatic stay terminated upon the effective date, 24 and advised that plaintiff’s present claims were enjoined, not that they were stayed. (ECF No. 23.2 at 3 (“[P]rior to the Effective Date, this action was stayed by the automatic stay under 25 Section 362(a) . . . .” (emphasis added)); id. at 4 (“Plan injunction applies to and enjoins the 26 continued prosecution of this action”).)
27 11 Defendants only briefed the impact of the allegedly existing automatic stay.
28 12 Although decisions by the BAP are not binding on district courts or the court of appeals, “BAP 1 present formulation that a bankruptcy discharge “voids any judgment at any time obtained, to the 2 extent that such judgment is a determination of the personal liability of the debtor with respect to 3 any debt discharged under section . . . 1141 . . . of this title, whether or not discharge of such debt 4 is waived.” 11 U.S.C. § 524(a)(1); see 328 B.R. at 164-70. The BAP concluded that as of the 5 date of the debtor’s discharge in his prior bankruptcy case, “any judgment that [the creditor] at 6 any time obtained on the discharged debt would automatically be rendered ‘void’ by § 524(a)(1).” 7 In re Gurrola, 328 B.R. at 171. Thus, the default judgment the creditor obtained in a subsequent 8 bankruptcy case “was ‘void’ the instant it was entered.” Id. Further, the creditor’s “activities in 9 prosecuting its effort to obtain a default judgment and thereafter to collect upon it violated the 10 discharge injunction.” Id. (citing 11 U.S.C. § 524(a)(2)) (footnote omitted). 11 Crucially for present purposes, the BAP held that “judgments and acts in violation of the 12 injunction are automatically void ab initio, hence self-executing, for the same reasons as the 13 [§ 362] automatic stay.” Id. at 175 (citations omitted). Primarily at issue in Gurrola was whether 14 the debtor could waived the defense of “discharge in bankruptcy” by not raising it when 15 challenging the default. The BAP held that—based on Ninth Circuit precedent that actions 16 violating a § 362 automatic stay are void, not voidable—the discharge defense is likewise 17 absolute and nonwaivable. Id. at 170, 175. But the BAP also concluded that not only was the 18 creditor’s later obtained judgment void, but also the creditor’s “actions in obtaining the judgment 19 are void as having violated the discharge injunction.” Id. at 176. 20 Applying the persuasive authority of Gurrola to the present case, any actions by plaintiff 21 in seeking to obtain judgment against PG&E for a discharged debt—its liability for the present 22 claims that arose pre-bankruptcy—violate the 2020 discharge injunction for the reasons explained 23 above and are thus void ab initio (meaning “from the very start”). Plaintiff’s efforts to serve 24 PG&E with process were taken for the purpose of bringing PG&E into the present suit in order to 25 obtain judgment against PG&E. The February 17, 2021 service on PG&E was therefore void, 26 opinions may be ‘persuasive and aid [courts in their] reading of the Bankruptcy Code.” Shapiro 27 v. Henson, 739 F.3d 1198, 1201 n.3 (9th Cir. 2014) (quoting In re Healthcentral.com, 504 F.3d 775, 784 n.3 (9th Cir. 2007)). 28 1 that is, without legal effect.13 2 This conclusion is bolstered by the fact that the Ninth Circuit’s interpretations of § 362 3 make it easy to equate the effect of a § 362 automatic stay with that of a § 524(a) injunction. The 4 Ninth Circuit, sitting en banc, held in In re Gruntz that automatic stays are “self-executing, 5 effective upon the filing of the bankruptcy petition,” and that “actions taken in violation of the 6 automatic stay are void.” 202 F.3d 1074, 1081, 1082 (9th Cir. 2000) (citing 11 U.S.C. § 362(a)). 7 Although § 362(a) speaks in terms of “stay[ing]” all manner of collection efforts upon the filing 8 of a bankruptcy petition, in effect “[t]he automatic stay is an injunction issuing from the authority 9 of the bankruptcy court.” In re Gruntz, 202 F.3d 1082 (emphasis added); see id. at 1081 (“The 10 automatic stay sweeps broadly, enjoining the commencement or continuation of [collection 11 efforts against the debtor].” (emphasis added)). 12 With this gloss, § 362(a)(1) and (a)(6) in combination almost perfectly mirror the text of 13 § 524(a)(2). Compare 11 U.S.C. § 362(a) (providing that a bankruptcy petition “operates as a 14 stay . . . of (1) the commencement or continuation, including the issuance or employment of 15 process, of a judicial, administrative, or other action or proceeding against the debtor [that was or 16 could have been brought before the bankruptcy petition]; . . . [and] (6) any act to collect, assess, 17 or recover a claim against the debtor [that arose pre-petition]), with 11 U.S.C. § 524(a)(2) 18 (providing that a bankruptcy discharge “operates as an injunction against the commencement or 19 continuation of an action, the employment of process, or an act, to collect, recover or offset any 20 [discharged] debt as a personal liability of the debtor”). In a slightly separate context, the Ninth 21 Circuit also stated that a “discharge injunction prevents [creditors, i.e., plaintiff in this case,] from 22 even commencing [a] second suit” “to try to enforce the debt” post-discharge. Espinosa v. United 23 Student Aid Funds, Inc., 553 F.3d 1193, 1200 (9th Cir. 2008), aff’d, 559 U.S. 260, (2010). The 24 undersigned is thus persuaded that the Ninth Circuit would hold a party’s actions taken in
25 13 Plaintiff’s service of process and continued prosecution of this case against PG&E were and are 26 done at peril of contempt proceedings in the bankruptcy court. See In re Gurrola, 328 B.R. at 175-76. Discharge injunctions are enforced by the bankruptcy court that issued the confirmation 27 order. Barrientos v. Wells Fargo Bank, N.A., 633 F.3d 1186, 1189, 1191 (9th Cir. 2011) (“an order of contempt under [11 U.S.C.] § 105 to enforce an existing injunction must be sought via 28 motion in the bankruptcy action”). 1 violation of a discharge injunction to be just as void as a party’s actions taken in violation of an 2 automatic stay.14 3 Because plaintiff’s service of process on PG&E in this case was void, it is as though 4 PG&E was never served. See Black’s Law Dictionary (11th ed. 2019) (defining “void” as “[o]f 5 no legal effect”). Treating PG&E as never having been served, as we must, the “non-served 6 defendant” exception to the rule of unanimity applies. See Salveson, 731 F.2d at 1429 (noting 7 circuit rule that “a party not served need not be joined” for purposes of removal). Accordingly, 8 PG&E’s lack of consent to removal is not a procedural defect.15 9 2. Failure to Explain the Absence of PG&E’s Consent 10 Plaintiff also presents a corollary argument that the Notice of Removal is facially 11 defective because it fails to explain the absence of PG&E’s consent. (ECF No. 17 at 5-6.) 12 Defendants do not acknowledge this argument as it relates to PG&E, focusing instead solely on 13 why their failure to explain the absence of consent from Dujmovich was cured by his later joinder 14 (an argument addressed in the next section). And plaintiff is completely correct that the removing 15 defendants should have explained in the Notice of Removal why PG&E was not joining in or 16 consenting to removal. See Paws Up Ranch, 597 F. Supp. 2d at 1135-36 (if removing defendants 17 believe an exception to the unanimity rule applies such that they are not required to join in the 18 notice of removal, they “should explain this in their notice”). 19 Although defendant Silver’s Notice of Removal makes some acknowledgement of this 20 14 Because plaintiff’s service of process is “void” not “voidable,” it is irrelevant that PG&E has 21 not directly challenged the effectiveness of service in this case. Cf. In re Gurrola 328 B.R. at 167 (“[T]here is no requirement that the fact of bankruptcy protection be raised in the state court.” 22 (discussing the Supreme Court’s interpretation of the impact of automatic stays in Kalb v. 23 Feuerstein, 308 U.S. 433, 444 (1940)).
24 15 Without the benefit of briefing by the parties, the court does not rule on PG&E’s status as a defendant in this case, beyond holding that the February 2021 service was a nullity for purposes 25 of removal procedure. One district court relied on Gurrola to conclude that a bankruptcy 26 discharge effectively acts as a “jurisdictional bar” to the continuation of claims against a covered debtor. See Stewart v. Stoller, No. 2:07-CV-552, 2014 WL 585442, at *2-3 (D. Utah Feb. 14, 27 2014) (dismissing debtor as defendant, based on information in case status report). The undersigned is unwilling to go so far as to recommend dismissing PG&E from this action on the 28 present thin record. 1 requirement, the Notice of Removal plainly does not “affirmatively explain” the absence of 2 consent by PG&E (or Dujmovich, addressed below). The Notice of Removal simply states: “All 3 other defendant(s) who have been served with Summons and complaint have joined in this Notice 4 of Removal, as evidenced by the Joinders of defendants Ronald Steven Schoenfeld and Lance 5 Schultz, filed concurrently herewith.” (ECF No. 1 at 2.) This statement implies that the reason 6 PG&E and Dujmovich were not joining is that they had not been served. It certainly does not 7 “affirmatively explain” their absence, however, and even the implied explanation is refuted by the 8 proofs of service on those two defendants, which plaintiff filed in the state court. Defendants 9 likely could have avoided this entire motion if they had simply stated that PG&E was not joining 10 in the removal because plaintiff’s service upon it was without effect, pursuant to the discharge 11 injunction. 12 The law is clear that they should have done so. The Ninth Circuit case establishing this 13 affirmative explanation requirement frames the requirement in all-or-nothing terms: “Where 14 fewer than all the defendants have joined in a removal action, the removing party has the burden 15 under section 1446(a) to explain affirmatively the absence of any co-defendants in the notice for 16 removal.” Prize Frize, 167 F.3d at 1266 (emphasis added). Defendants’ opposition to the remand 17 motion does not even cite this case, which many courts have used to remand cases that fail to 18 affirmatively explain a co-defendant’s silence, sometimes even when the absent co-defendant was 19 not properly served.16 Nevertheless, after much reflection, the undersigned concludes that the 20 16 See Riggs v. Plaid Pantries, Inc., 233 F. Supp. 2d 1260, 1267-68 (D. Or. 2001) (defendant had 21 affirmative duty to explain absence of co-defendants from notice of removal, even if co- defendants were not properly served and defendant was removing a claim separate and 22 independent from those brought against co-defendants) (collecting cases); Sotelo v. Browning- 23 Ferris Indus. of California, Inc., No. 2:20-CV-06927-SB-PVC, 2020 WL 7042816, at *3 (C.D. Cal. Nov. 30, 2020) (Prize Frize “requires an explanation for the absence of co-defendants who 24 have not been served”; remanding because notice of removal lacked such explanation, and later joinders were untimely); Vargas v. Riley, No. 18-CV-00567-JST, 2018 WL 2267731, at *3 (N.D. 25 Cal. May 17, 2018) (remanding for failure to explain absence of co-defendants in notice of 26 removal, which was uncured within 30-day statutory period); Boyett Constr., Inc. v. Allianz Glob. Risks U.S. Ins. Co., No. 2:14-CV-00607-GEB-AC, 2014 WL 2093569, at *1 (E.D. Cal. May 19, 27 2014) (notice of removal was procedurally deficient because removing defendant “has not satisfied its burden of affirmatively explaining why it failed to obtain [co-defendant’s] joinder in 28 or consent to the removal”); Canterbury Lots 68 LLC v. Esposito, No. CV 5:11-01880 SVW 1 failure to affirmatively explain PG&E’s absence in the Notice of Removal does not warrant 2 remand in this case. 3 The court finds most instructive Mitchell v. Paws Up Ranch, LLC, 597 F. Supp. 2d 1132 4 (D. Mont. 2009), a case not cited by either side. In Paws Up, the plaintiff challenging removal 5 argued for a formal application of the Prize Frize affirmative explanation requirement, contending 6 that a notice of removal must explain the absence of all co-defendants, regardless of the 7 surrounding circumstances. See 597 F. Supp. 2d at 1136-37 (explaining plaintiff’s reliance on 8 Riggs v. Plaid Pantries, Inc., 233 F. Supp. 2d 1260, 1268 (D. Or. 2001), which held that Prize 9 Frize’s explanation requirement “applies to all co-defendants, even those who are exempted from 10 joinder because they were not served or were fraudulently joined”). The court rejected plaintiff’s 11 argument and held that because plaintiff “was fully aware that he had not accomplished service 12 on [the unexplained non-consenting defendant] at the time of removal,” there was no need to 13 “explain affirmatively what the plaintiff already knows.” Paws Up, 597 F. Supp. 2d at 1136, 14 1139, 1141. The court distinguished the scenarios in Prize Frize and Riggs that engendered their 15 bright-line formulations of the explanation requirement, and it discerned a policy reason for the 16 rule as stated in those cases: “The requirement that a removing defendant explain affirmatively 17 the absence of non-joining defendants serves the purpose of giving the plaintiff notice regarding 18 his obligations pertaining to service of process.” Id. at 1137 (discussing how in Prize Frize, 167 19 F.3d at 1266, the Ninth Circuit dealt with a notice of removal that “merely indicated that some of 20 the absent defendants might challenge service of process” and found that “explanation was 21 insufficient to put the plaintiff on notice of who was challenging what in terms of service of 22 process”). The court in Paws Up refused to require the removing defendants to “provide an 23 (SSx), 2011 WL 6100967, at *2 (C.D. Cal. Dec. 5, 2011) (remanding because defendant offered 24 no explanation for absence of co-defendants); Valley Forge Ins. Co. v. APL Co. Pte., No. CV 09- 09323 MMM (VBKx), 2010 WL 960341, at *3-5 (C.D. Cal. Mar. 16, 2010); Parking Concepts, 25 Inc. v. RSUI Group, Inc., No. CV 09-5143 PSG (AJWx), 2009 WL 2973118, at *3 (E.D. Cal. 26 Sept. 11, 2009); Anderson v. Kaz, Inc., No. 08-CV-253-BR, 2008 WL 2477559, at *3 (D. Or. June 12, 2008). See also 16 Moore’s Federal Practice - Civil § 107.42 (2021) (citing cases 27 “remanded to state courts at least in part because a removal petition filed by less than all of the named defendants did not include an explanation for a co-defendant’s absence”). Defendants’ 28 opposition likewise does not acknowledge any of these cases. 1 explanation for the absence of other named defendants who have no obligation to even make an 2 appearance because they are not yet parties to the action.” Id. at 1139. It reasoned that, given the 3 reason for the affirmative explanation rule—“to provide the plaintiff notice of issues regarding 4 effectiveness of service of process”—requiring an explanation for a plaintiff who already knows 5 he has not served the absent defendant “would impose on the removing defendants a merely 6 perfunctory obligation.” Id. Accordingly, the court denied the motion to remand. 7 Paws Up also relied in part on an unpublished decision of the Ninth Circuit in Fisher v. 8 Alfa Chemicals Italiana, 258 F. App’x 150 (9th Cir. 2007). See 597 F. Supp. 2d at 1136. In 9 Fisher, the Court of Appeals rejected the plaintiff’s challenge to removal based on failure to 10 explain why other named defendants did not join the notice of removal. 258 F. App’x at 151. 11 The Ninth Circuit non-precedentially held that because “it was clear to [the plaintiff] and to the 12 district court that none of the other defendants had been served, . . . there was no reason for [the 13 removing defendant] to have provided such an explanation in this case.” Id. (citing Emrich, 846 14 F.2d at 1193 n.1 for “the general rule that all defendants must join a removal petition ‘applies, 15 however, only to defendants properly joined and served in the action’”). 16 The undersigned finds the reasoning of these cases persuasive and applicable to this case, 17 even if not perfectly on point. The main difference with this case, of course, is that plaintiff here 18 did arrange for substituted service on PG&E, which occurred on February 17, 2021. (ECF No. 18 19 at 11.) Plaintiff therefore may have believed that PG&E was a properly served defendant at the 20 time of removal. However, the Notification of Plan Effective Date filed in state court five days 21 before defendant Silver filed her Notice of Removal should have dispelled plaintiff of that belief. 22 The March 11th Notification of Plan Effective Date clearly stated in bold, all-caps font that “the 23 Plan injunction applies to and enjoins the continued prosecution of this action” against PG&E. 24 (ECF No. 23.2 at 4.) Although the court does not expect plaintiff, who is self-represented, 25 thereby became aware of all the bankruptcy law discussed in the previous section, the plain text 26 of the March 11th Notification put her on notice that there was an obstacle to bringing PG&E into 27 28 1 this case as a defendant.17 Requiring defendants to repeat the existence of the discharge 2 injunction against plaintiff’s claims in the Notice of Removal would, as in Paws Up, be a “merely 3 perfunctory obligation.” See 597 F. Supp. 2d at 1139. Providing such an explanation would not 4 enable plaintiff to “cure” the obstacle to PG&E’s prosecution in this case; there was nothing 5 plaintiff could do to change the fact of the bankruptcy discharge injunction.18 6 Under the statutory and court-ordered discharge injunction, plaintiff’s service on PG&E 7 was ineffective, as explained above. Accordingly, the undersigned sees no utility in requiring the 8 removing defendants to explain the absence of PG&E, who—as an unserved defendant—had “no 9 obligation to even make an appearance because [it is] not yet part[y] to the action.” See id. 10 at 1139. As in Fisher, it was clear to plaintiff and to the court that PG&E could not be made party 11 to this case, given the discharge injunction, “so there was no reason for [the removing defendants] 12 to have provided such an explanation in this case.” 258 F. App’x at 151. While it would have 13 undoubtedly been the better practice to explain PG&E’s failure to join in the notice of removal, 14 the lack of such explanation is not grounds for remand here. 15 B. Dujmovich’s Subsequent Joinder Cured the Procedural Defects Existing at the 16 Time of Removal 17 Plaintiff directs most of her motion to challenging the removal in relation to defendant 18 Dujmovich, as opposed to PG&E, but the court finds the issues with respect to Dujmovich 19 simpler to resolve because of his subsequent joinder in the removal. Plaintiff applies the same 20 two general arguments discussed above for both PG&E and Dujmovich. As to Dujmovich, 21 plaintiff argues for remand because (1) the Notice of Removal did not explain his absence, and 22 (2) Dujmovich still has not consented to removal because his later filed joinder was not timely 23 and was “ambiguous.” (ECF No. 17 at 5-7.) The court disagrees with plaintiff on the second 24 17 The Notification of Plan Effective Date also quoted the relevant portions of the injunction 25 provisions of the Confirmation Order and the Plan. (ECF No. 23.2 at 3.) 26 18 “The only manner in which a debtor’s personal liability on a pre-petition debt can survive a 27 discharge is through an enforceable reaffirmation agreement between the debtor and creditor pursuant to 11 U.S.C. § 524(c).” Stewart v. Stoller, No. 2:07-CV-552, 2014 WL 585442, at *3 28 (D. Utah Feb. 14, 2014) (cleaned up). 1 point and therefore need not reach the first. 2 To recap, Dujmovich was the first defendant served in this action. He was served in 3 Texas on January 30, 2021. (ECF No. 18 at 4, Ex. A.) The other four defendants were served 4 over the following weeks,19 with defendant Schultz served last, on February 19, 2021. (Id. at 19, 5 Ex. E). Defendant Silver filed her Notice of Removal on March 16, 2021, without expressly 6 mentioning whether Dujmovich consented to removal. (ECF No. 1.) About three weeks later, on 7 April 8, 2021, defendant Dujmovich filed his joinder to the Notice of Removal. (ECF No. 13.) 8 The following week, plaintiff moved to remand. (ECF No. 17.) And the next day, defendants 9 Dujmovich and Schultz—both represented by Mr. Thomas—filed a joint motion to dismiss. 10 (ECF No. 19.) 11 Defendants’ opposition to the remand motion sheds more light on the timing of 12 Dujmovich’s consent to removal. In a supporting declaration, Mr. Thomas avers that, “[b]ased on 13 a misunderstanding of Mr. Dujmovich’s description of the events, [he] mistakenly believed that 14 Plaintiff had not properly served Mr. Dujmovich” on January 30th. (ECF No. 23.1 (Thomas 15 Decl.) ¶ 2.) Therefore, when defendant Silver’s counsel, Mr. Rausch, removed the action to this 16 court on March 16, 2021, Mr. Thomas informed him that “Lance Schultz would join in the 17 removal to federal court but that Mr. Dujmovich would not join because Plaintiff had not properly 18 served him.” (Id. ¶ 5.) However, on April 5, 2021, Mr. Thomas “learned that Plaintiff’s 19 January 30, 2021 service on Mr. Dujmovich was proper,” leading him to file Dujmovich’s joinder 20 to the removal on April 8, 2021. (Id. ¶ 7.) 21 Plaintiff only obliquely argues that Dujmovich’s April 8th joinder was untimely, because 22 each consent had to be received “within 30 days of service of the complaint and summons.” 23 (ECF No. 17 at 6-7.) To the extent plaintiff believes Dujmovich could only consent to removal 24 within 30 days of when he, himself, was served, she is incorrect. The Ninth Circuit adopted the 25 “later-served defendant” rule back in 2011, and that rule was codified in the removal statute 26 shortly after. See Destfino v. Reiswig, 630 F.3d 952, 955-56 (9th Cir. 2011); see also 28 U.S.C. 27
28 19 Notwithstanding the prior discussion of how the substituted service on PG&E is without effect. 1 § 1446(b)(2)(C) (“If defendants are served at different times, and a later-served defendant files a 2 notice of removal, any earlier-served defendant may consent to the removal even though that 3 earlier-served defendant did not previously initiate or consent to removal.”). Thus, an earlier- 4 served defendant (like Dujmovich in this case) gets a new opportunity to consent to removal upon 5 the filing of a notice of removal by a later-served defendant (like defendant Silver in this case). 6 The question remains, by when must an earlier-served defendant like Dujmovich consent 7 to a removal initiated by a later-served defendant like Silver? This is an open question in this 8 circuit, as in many others, because the statute oddly does not specify a deadline. See 9 § 1446(b)(2)(C). Defendants, however, never acknowledge the widely divergent ways the courts 10 have answered this question.20 Defendants simply argue in a single paragraph, citing a single 11 district court case, that Dujmovich’s April 8th joinder was timely because it was filed within 30 12 days of Silver’s March 16th Notice of Removal. (ECF No. 23 at 7 (quoting Pattison v. Nevada ex 13 rel. Nevada Dep’t of Corr., No. 3:14-CV-00020-MMD, 2014 WL 2506467, at *7-9 (D. Nev. 14 June 3, 2014).) Defendants’ omission is particularly glaring because Pattison itself makes plain 15 the unsettled nature of the question. See Pattison, 2014 WL 2506467, at *1 (“[T]he question of 16 when a defendant’s separate joinder or consent [to removal] must be filed to be timely does not 17 appear to be definitively established in the Ninth Circuit . . . .”). 18 Some courts, like Pattison, land on a deadline of 30 days after the notice of removal. See 19 Wilburn v. Bratcher, No. 2:15-CV-0699-TLN-GGH, 2015 WL 9490242, at *4 (E.D. Cal. Dec. 30, 20 20 See, e.g., Majewski v. Dick’s Sporting Goods, Inc., No. 20-CV-6906, 2021 WL 76819, at *2 21 n.1 (N.D. Ill. Jan. 8, 2021) (comparing different approaches of courts across the country); Alston v. Wells Fargo Bank, N.A., 2017 WL 2839629, at *2 (D. Md. 2017) (“This temporal language [in 22 § 1446(b)(2)(A)] suggests that all defendants must consent to removal, if not within their own 30- 23 day window under § 1446(b)(2)(B), then when the case is actually removed, not at some undetermined point afterwards.”); Palmeira v. CIT Bank, N.A., No. CV 17-00275 ACK-RLP, 24 2017 WL 4797515, at *4-5 (D. Haw. Oct. 24, 2017) (comparing different approaches and ultimately concluding that “consent must be filed within the 30-day period for removal . . . , not 25 within 30 days of when the notice of removal was filed”); Gibbs v. Ocwen Loan Servicing, LLC, 26 No. 3:14-CV-1153-M-BN, 2014 WL 2767206, at *2 (N.D. Tex. June 18, 2014) (consent to removal under § 1446(b)(2)(C) must be filed within the later-served defendant’s 30-day removal 27 period); Moore v. Svehlak, No. ELH-12-2727, 2013 WL 3683838, at *14 (D. Md. July 11, 2013) (consent to removal must be filed either within the earlier-served defendant’s own 30-day 28 removal window or concurrently with the later-served defendant’s notice of removal). 1 2015) (citing Hafiz v. Greenpoint Mortgage Funding, Inc., 652 F. Supp. 2d 1050, 1052 (N.D. Cal. 2 2009)). But others criticize that deadline as disadvantaging plaintiffs who might then have to 3 wait until that 30th day to file a motion to remand for lack of consent—while facing their own 4 concurrent 30-day deadline to so move. See, e.g., Palmeira v. CIT Bank, N.A., No. CV 17-00275 5 ACK-RLP, 2017 WL 4797515, at *5-6 (D. Haw. Oct. 24, 2017) (disagreeing with Pattison and 6 holding that earlier-served defendants must consent within the 30-day period for later-served 7 defendant to initiate removal, not within 30 days of the notice of removal). If the court were to 8 follow Palmeira, and the multiple other courts adopting its 30-day-removal-period deadline,21 9 defendant Dujmovich’s consent here would be too late, falling more than 30 days after service on 10 the last-served defendant.22 See 28 U.S.C. § 1446(b)(2)(B), (C). 11 Luckily for defendants, however, it turns out that the court need not decide what deadline 12 applies because the Ninth Circuit consistently approves of district courts allowing procedural 13 defects in removal to be cured at any point prior to entry of judgment. If the unanimity 14 requirement is not met when a notice of removal is filed, “the district court may allow the 15 removing defendants to cure the defect by obtaining joinder of all defendants prior to the entry of 16 judgment.” Destfino, 630 F.3d at 956-57; Soliman v. Philip Morris Inc., 311 F.3d 966, 970 (9th 17 Cir. 2002) (“[A] procedural defect existing at the time of removal but cured prior to entry of 18 judgment does not warrant reversal and remand of the matter to state court.” (alteration in original 19 21 See, e.g., A. N. v. Target Corp., No. CV 20-11380 PA (RAOx), 2021 WL 53169, at *2 (C.D. 20 Cal. Jan. 5, 2021) (earlier-served defendant’s consent to removal did not timely cure lack of unanimity because it was “filed well outside the 30-day removal period that began running when 21 the last defendant was served with the Summons and Complaint”); Sotelo v. Browning-Ferris Indus. of Cal., Inc., No. 2:20-CV-06927-SB-PVC, 2020 WL 7042816, at *4 (C.D. Cal. Nov. 30, 22 2020) (“numerous courts have affirmed that defendants must consent to removal within the 30- 23 day removal period of the last-served defendant”) (citations and internal quotation marks omitted); Lopez v. Michael Weinig, Inc., No. CV 20-6012 PA (JEMx), 2020 WL 4192260, at *2 24 (C.D. Cal. July 17, 2020) (same, collecting cases); Lewis v. HSBC Bank USA, N.A., 2017 WL 3671279, at *7-8 (D. Haw. Aug. 25, 2017) (same, noting that § 1446(b)(2)(C) “does not provide 25 an open-ended opportunity to consent to removal at any time during the course of a case”); 26 Zambrano v. New Mexico Corr. Dep’t, 256 F. Supp. 3d 1179, 1186 (D.N.M. June 1, 2017) (same). 27 22 Dujmovich consented on April 8, 2021, which is 48 days after the last-served defendant 28 (Schultz) was served on February 19, 2021. 1 and internal quotation marks omitted)).23 2 Courts in this district, including the undersigned, routinely recognize later joinders to 3 removal as curing prior procedural unanimity defects. See, e.g., Smith v. Furniture Deals, Inc., 4 No. 1:19-CV-1557 AWI EPG, 2020 WL 429130, at *5 (E.D. Cal. Jan. 28, 2020) (“a violation of 5 the defendant unanimity rule may be corrected prior to entry of judgment” (citing Destfino, 630 6 F.3d at 957); Wimberly v. Beard, No. 2:16-CV-0279-KJM-KJN-P, 2016 WL 5791228, at *3 7 (E.D. Cal. Aug. 26, 2016) (remand was unwarranted despite “untimely consent” because later 8 joinder cured procedural defect and no judgment had been entered); see also Conroy v. Ridge 9 Tool Co., No. 4:20-CV-05882-YGR, 2020 WL 8641963, at *4 (N.D. Cal. Nov. 18, 2020) 10 (“Destfino instructs that the timeline for joinder is not strict . . . .”). The undersigned therefore 11 concludes that defendant Dujmovich’s joinder to removal, filed 23 days after the Notice of 12 Removal, cured the prior unanimity defect—without opining on what the deadline is for earlier- 13 served defendants to join a later-served defendant’s notice of removal (if any). 14 Given that there is now unanimous consent to removal by all properly served defendants, 15 the court need not address plaintiff’s corollary argument that the Notice of Removal failed to 16 affirmatively explain the absence of Dujmovich’s consent. Violation of the affirmative 17 explanation rule only supports remand where the unmentioned co-defendant never subsequently 18 joins in or consents to removal. See Conroy, 2020 WL 8641963, at *5-6 (failure to explain 19 absence of co-defendants was “not fatal to removal because any resulting defect was cured when 20 [those defendants] joined the notice of removal,” in that case more than 30 days after the last- 21 served defendant); see id. at *6 & n.4 (noting that Prize Frize, 167 F.3d at 1266, held removal was 22 improper because “because the removal notice was facially defective and the deficiencies [were] 23 uncured within the thirty-day statutory period” and that the Ninth Circuit was primarily concerned 24 23 But see Sotelo, 2020 WL 7042816, at *4 (critiquing application of Destfino’s rule to cases in 25 their early stages at the trial level). While true that this rule originated in appellate courts to avoid 26 having to remand cases that came to the Court of Appeals after judgment was already rendered, Destfino explicitly approved of a court in this very district permitting co-defendants to join in 27 removal several months after the notice of removal but quite early in the litigation. See Destfino v. Kennedy, No. CV-F-08-1269LJODLB, 2008 WL 4901195, at *2-5 (E.D. Cal. Nov. 12, 2008), 28 aff’d sub nom. Destfino v. Reiswig, 630 F.3d 952 (9th Cir. 2011). 1 there with the lack of unanimity, “which was never cured”). 2 Despite this conclusion, the court must emphatically reject defendants’ assertion that the 3 failure to mention PG&E or Dujmovich in the Notice of Removal was a “de minimis defect.” 4 (See ECF No. 23 at 5-6.) The cases defendants cite in support of this argument all deal with 5 failures to attach the requisite papers to a notice of removal—and unsurprisingly hold these 6 administrative defects “both de minimis and curable.” Gray v. Extended Stay Am., Inc., 7 No. 2:19-CV-01269-MCE-EFB, 2020 WL 1274265, at *5 (E.D. Cal. Mar. 17, 2020) (failure to 8 attach “Civil Case Cover Sheet, Case Management Statement, ADR Packet, Notice and 9 Acknowledgment of Receipt, and a state court order”); see Kuxhausen v. BMW Fin. Servs. NA 10 LLC, 707 F.3d 1136, 1142 (9th Cir. 2013) (failure to attach original complaint); Countryman v. 11 Farmers Ins. Exchange, 639 F.3d 1270, 1272-73 (10th Cir. 2011) (failure to attach summons). 12 These sorts of technical omissions rarely prejudice the plaintiff or impede the court’s ability to 13 proceed with the case. See Countryman, 639 F.3d at 1273. By contrast, failing to explain the 14 absence of consent from all named defendants leaves the court and the plaintiff totally in the dark 15 as to whether the case can proceed in federal court. 16 Defendants now try to excuse the lack of affirmative explanation as occurring “due to a 17 misunderstanding regarding service of Dujmovich.” (ECF No. 23 at 6.) But that entirely misses 18 the point. The problem is not that defendants initially mistook Dujmovich for an improperly 19 served defendant. The problem is that they did not explain in the Notice of Removal that this 20 was the reason Dujmovich was not joining in or consenting to removal. The unanimity rule is 21 core to ensuring that removal is fair and proper. The affirmative explanation requirement is 22 essential to enforcing that rule. Although, as discussed above, a lack of affirmative explanation 23 can be cured, that does not mean it is a “de minimis” defect. Defendants cite no case supporting 24 that proposition, nor is the court aware of any. 25 1. Plaintiff’s Remaining Arguments 26 Plaintiff’s remaining arguments for remand with respect to Dujmovich can be easily 27 rejected. Plaintiff argues that Dujmovich “filed an ambiguous Joinder reserving his right to 28 object to the joinder at a later date, and continues to litigate this case in state court” by virtue of 1 his objection to the entry of default and his motion to quash. (ECF No. 17 at 6-7.) First, 2 Dujmovich’s statement in his joinder that he was not thereby “waiv[ing] any objections as to 3 service, jurisdiction, or venue, or any other defenses or objections to this action” does not render 4 his joinder “ambiguous” by any means. (ECF No. 13 at 2.) This statement does not say that 5 Dujmovich is “reserving his right to object to the joinder,” contrary to plaintiff’s belief. (ECF 6 No. 17 at 6 (emphasis added).) It merely makes explicit what was already true as a matter of law: 7 that Dujmovich’s joinder was simply that—joining in the removal of the case to federal court— 8 and not a waiver of any of the other procedural options available to defendants in the normal 9 course of litigation. 10 Second, the court does not share plaintiff’s critical view of Dujmovich’s conduct in the 11 state court after defendant Silver filed the Notice of Removal to this court. Based on the 12 declaration of his counsel, Mr. Thomas (ECF No. 23.1), Dujmovich’s state court filings appear 13 perfectly reasonable. His March 22 objection to entry of default and March 30 motion to quash 14 both preceded Mr. Thomas’s April 5 realization that Dujmovich had, in fact, been properly 15 served. Dujmovich then joined the Notice of Removal within a few days on April 8, and his 16 counsel represents to the court that “no actions were taken on behalf of Dujmovich in state court” 17 thereafter. (ECF No. 23 at 8.) Soon after, on April 16, 2021, Dujmovich filed a joint motion to 18 dismiss (with defendant Schultz) in this court, primarily asserting that plaintiff fails to state a 19 claim—confirming his intent that this action be litigated in federal court. (See ECF No. 19.1 at 20 12-19.) Dujmovich unequivocally consented to removal in his April 8th joinder, and none of his 21 surrounding litigation conduct raises any doubt about that express consent. 22 Plaintiff also goes on to speculate about why Dujmovich did not initially consent to 23 removal and might wish to keep the case in state court; and she even goes so far as to impute a 24 conflict of interest between Mr. Thomas’s various clients in this action. (ECF No. 17 at 7-9.) 25 These arguments are neither relevant nor based on anything more than conjecture. 26 Finally, plaintiff’s conclusory argument that the state law causes of action are better 27 adjudicated in state court does not support remand. This case is properly removable based on the 28 federal causes of action, and the court exercises its discretion to retain supplemental jurisdiction 1 over the state law claims which arise from a common set of facts. 2 CONCLUSION 3 Despite defendants’ many missteps in removing this case—and in defending the 4 removal—the undersigned concludes that the removal is not defective. PG&E’s consent was not 5 required to remove this case; the Notice of Removal did not need to explain the absence of 6 PG&E’s consent, although it would have been better to do so; and because Dujmovich’s later 7 unequivocal joinder in the removal cured the prior lack of unanimity, there is no basis to remand 8 for failure to explain his absence. Accordingly, the undersigned recommends denying plaintiff’s 9 motion to remand. 10 ORDER 11 In light of these findings and recommendations, the undersigned resets a schedule to 12 complete the briefing of the pending motion to dismiss by defendants Schultz and Dujmovich 13 (ECF No. 19): 14 1. Plaintiff shall file any opposition in response to the motion to dismiss no later than 15 June 10, 2021; 16 2. Defendants Schultz and Dujmovich shall file any optional reply no later than June 24, 17 2021. 18 The motion remains under submission (ECF No. 21 at 2), so no hearing is set. The court 19 intends to resolve this motion to dismiss along with the already briefed co-pending motion to 20 dismiss by defendant Silver (ECF No. 6). If the court subsequently determines that a hearing is 21 needed on either motion to dismiss, it will be scheduled at a later date with notice to the parties. 22 RECOMMENDATIONS 23 It is HEREBY RECOMMENDED that: 24 1. Plaintiff’s motion to remand this action to state court (ECF No. 17) be DENIED; and 25 2. This case be referred again to the undersigned for further proceedings. 26 These findings and recommendations are submitted to the United States District Judge 27 assigned to the case, pursuant to the provisions of 28 U.S.C. § 636(b)(l). Within fourteen (14) 28 days after being served with these findings and recommendations, any party may file written 1 | objections with the court and serve a copy on all parties. Such a document should be captioned 2 || “Objections to Magistrate Judge’s Findings and Recommendations.” Any reply to the objections 3 || shall be served on all parties and filed with the court within fourteen (14) days after service of the 4 || objections. The parties are advised that failure to file objections within the specified time may 5 || waive the right to appeal the District Court’s order. Turner v. Duncan, 158 F.3d 449, 455 (9th 6 || Cir. 1998); Martinez v. YIst, 951 F.2d 1153, 1156-57 (9th Cir. 1991). 7 || Dated: May 25, 2021 Foci) Aharon 9 KENDALL J. NE UNITED STATES MAGISTRATE JUDGE 10 1] AW, gian.0477 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 26
Related
Cite This Page — Counsel Stack
(PS) Gianelli v. Schoenfeld, Counsel Stack Legal Research, https://law.counselstack.com/opinion/ps-gianelli-v-schoenfeld-caed-2021.