Hoover v. Cyber Litigation Inc.

CourtUnited States Bankruptcy Court, D. Delaware
DecidedAugust 19, 2022
Docket20-50966
StatusUnknown

This text of Hoover v. Cyber Litigation Inc. (Hoover v. Cyber Litigation Inc.) is published on Counsel Stack Legal Research, covering United States Bankruptcy Court, D. Delaware primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Hoover v. Cyber Litigation Inc., (Del. 2022).

Opinion

UNITED STATES BANKRUPTCY COURT DISTRICT OF DELAWARE CRAIG T. GOLDBLATT pp, 824 N. MARKET STREET JUDGE 4 WILMINGTON, DELAWARE CA fy. (302) 252-3832 oe Ale, & ae August 19, 2022 VIA CM/ECF Re: Hoover v. Drivetrain LLC, Adv. Pro. No. 20-509661 Dear Counsel: In bankruptcy cases that are preceded by mass layoffs or plant shutdowns, it is commonplace for former employees who assert claims arising under the WARN Act, 29 U.S.C. § 2101, et seq., to file adversary proceedings and to seek the certification, under Rule 23 of the Federal Rules of Civil Procedure, of a class of affected employees. Indeed, in many cases, the propriety of treating the affected employees as part of a class is noncontroversial, and class certification is often accomplished by stipulation of the parties. This case, however, is different. While many of the debtor’s employees worked at its principal location in Las Vegas, Nevada, it also had a substantial number of employees who worked remotely. The application of the WARN Act to remote employees is an issue of increasing importance as remote work becomes more prevalent and raises reasonably complex issues. Particularly in a case (like this one) that involves some employees who worked at the debtor’s facility and others who were remote employees, the proper use of the class action raises questions over which there is substantial room for fair disagreement. In this case, the named plaintiffs (who themselves worked at the debtor’s Las Vegas facility) originally moved to certify a class in August 2021.2 That motion was 1 Drivetrain LLC, as the plan trustee, is the successor to Cyber Litigation, Inc. (“Cyber”), which was the debtor in the main bankruptcy case, In re Cyber Litigation Inc., No. 20-12702, and is the defendant in this adversary proceeding. 2 The initial proposed class was to be made up of “Plaintiffs and all persons G) who worked at, reported to, or received assignments from Defendant’s Las Vegas Facility, Gi) who were terminated without cause beginning on or about September 11, 2020, and within 30 days of that date, or were terminated without cause as the reasonably foreseeable consequence of the mass layoff and/or plant closing ordered by Defendant on or about are ‘affected employees’ within the meaning of

Page 2 of 17

fully briefed in December 2021 and set for argument in January 2022. Following that argument, the Court concluded that while the record before it would warrant the certification of a class of employees who worked at the debtor’s Las Vegas facility, the record was insufficient to permit the Court to determine whether debtor’s remote employees could be included in the class. The parties thus engaged in additional discovery and submitted supplemental briefs addressing the results of that discovery. The Court heard the parties renewed arguments on August 11, 2022. At that argument, the Court expressed its tentative conclusion that the evidentiary record did support the certification of classes that included remote employees. The Court, however, raised the question, in view of the distinct legal questions regarding the application of the WARN Act to remote employees, whether the remote employees ought to be included in a separate subclass. As further described below, however, the Court has concluded that the named plaintiffs can properly and adequately represent a class that includes remote employees, and that common issues predominate over individual issues despite the presence of a few factual or legal wrinkles that may apply to some but not all of the class. The Court is persuaded that those specific issues may properly be addressed by an appropriate case management order issued under Rule 23(d)(1). The Court did, however, express the concern that in view of the record as it developed, the question of which employees “received assignments from Defendant’s Las Vegas Facility” was itself a disputed issue such that a class was defined by reference to the location from which an employee received assignments would not be sufficiently “ascertainable” to satisfy the requirement of Rule 23.3 In light of the record before the Court and for the reasons more fully set forth 2Fbelow, the Court believes that the more appropriate definition of the class would replace the existing clause (i) so that the description of the class would begin: “Plaintiffs and all persons (i) who worked at Defendant’s Las Vegas Facility and/or who worked in Defendant’s sales or engineering departments, (ii) who were terminated….” For the reasons described more fully below, the Court is satisfied that the record before it supports the certification of such a class. The Court will enter an appropriate order certifying such a class. Factual and Procedural Background The debtor was a cyber-fraud prevention company. Its business collapsed in September 2020 when its founder, Adam Rogas, was indicted on fraud charges. It is

29 U.S.C. § 2101(a)(5), and (iv) who have not filed a timely request to opt-out of the class.” D.I. 26 at 1. 3 See Marcus v. BMW of N. Am., LLC, 687 F.3d 583, 592-593 (3d Cir. 2012) (Rule 23(b)(3) class must be ascertainable based on objective criteria). Page 3 of 17

alleged that Rogas falsified the debtor’s financial records in order to raise more than $100 million from investors. Soon after Rogas’ arrest, the debtors terminated the majority of its approximately 200 employees and soon thereafter filed for bankruptcy.4 3F Plaintiffs filed this WARN Act adversary proceeding in October 20205 and moved to certify it as a class action in August 2021.6 Declarations submitt4Fed in support of the class certification motion established that5F the debtor’s principal facility was located in Las Vegas, Nevada, but that the debtor also had a number of employees who worked remotely.7 As described above, after the January 2022 ruling denying class certification witho6F ut prejudice,8 the parties engaged in additional discovery, much of which has been presented 7Fto the Court in connection with the renewed motion to certify. In broad strokes, that discovery revealed that in addition to its Las Vegas employees, the debtor employed approximately 128 remote employees working in one of four departments: engineering, general and administration, marketing, and sales. D.I. 35-1. The two largest departments, the sales and engineering departments, collectively made up the vast majority of those employees. Additional factual material is set forth below, in the analysis section of this letter ruling, as appropriate. Jurisdiction Because the plaintiffs seek, in this adversary, allowed claims in the bankruptcy case, the district court has subject-matter jurisdiction under 28 U.S.C. § 1334(b), as a dispute “arising under” § 502 of the Bankruptcy Code. The case has been referred to this Court under 28 U.S.C. § 157(a) and the district court’s standing order of February 29, 2012.

4 See generally the first-day declaration of Daniel P. Wikel, filed in the main bankruptcy case, In re Cyber Litigation, No. 20-12702 (Bankr. D. Del. Oct. 27, 2020), D.I. 9. 5 D.I. 1. 6 D.I. 26. 7 D.I. 26-2. 8 D.I. 58. Page 4 of 17

Overview of Applicable Law A.

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

Related

Eisen v. Carlisle & Jacquelin
417 U.S. 156 (Supreme Court, 1974)
Amchem Products, Inc. v. Windsor
521 U.S. 591 (Supreme Court, 1997)
In Re Pet Food Products Liability Litigation
629 F.3d 333 (Third Circuit, 2010)
Waste Management Holdings, Inc. v. Mowbray
208 F.3d 288 (First Circuit, 2000)
Wal-Mart Stores, Inc. v. Dukes
131 S. Ct. 2541 (Supreme Court, 2011)
Baby Neal v. Casey
43 F.3d 48 (Third Circuit, 1994)
Robert Stewart v. Lynne Abraham
275 F.3d 220 (Third Circuit, 2001)
Dewey v. Volkswagen Aktiengesellschaft
681 F.3d 170 (Third Circuit, 2012)
Marcus v. BMW of North America, LLC
687 F.3d 583 (Third Circuit, 2012)
Comcast Corp. v. Behrend
133 S. Ct. 1426 (Supreme Court, 2013)
In Re Hydrogen Peroxide Antitrust Litigation
552 F.3d 305 (Third Circuit, 2009)
In Re Insurance Brokerage Antitrust Litigation
579 F.3d 241 (Third Circuit, 2009)
In Re United Companies Financial Corp.
276 B.R. 368 (D. Delaware, 2002)
Beck v. Maximus, Inc.
457 F.3d 291 (Third Circuit, 2006)
Landsman & Funk PC v. Skinder-Strauss Associates
640 F.3d 72 (Third Circuit, 2011)
Casale v. Kelly
257 F.R.D. 396 (S.D. New York, 2009)
Gavron v. Blinder Robinson & Co.
115 F.R.D. 318 (E.D. Pennsylvania, 1987)

Cite This Page — Counsel Stack

Bluebook (online)
Hoover v. Cyber Litigation Inc., Counsel Stack Legal Research, https://law.counselstack.com/opinion/hoover-v-cyber-litigation-inc-deb-2022.