Flinders v. Datasec Corp.

742 F. Supp. 929, 1990 U.S. Dist. LEXIS 8913, 1990 WL 99459
CourtDistrict Court, E.D. Virginia
DecidedJuly 16, 1990
DocketCiv. A. 89-1763-A
StatusPublished
Cited by13 cases

This text of 742 F. Supp. 929 (Flinders v. Datasec Corp.) is published on Counsel Stack Legal Research, covering District Court, E.D. Virginia primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Flinders v. Datasec Corp., 742 F. Supp. 929, 1990 U.S. Dist. LEXIS 8913, 1990 WL 99459 (E.D. Va. 1990).

Opinion

MEMORANDUM OPINION

ELLIS, District Judge.

Introduction

Not yet decided in this Circuit is whether an employee terminated for threatening to expose, or refusing to participate in, his employer’s allegedly unlawful racketeering practices has standing to sue his employer under RICO 1 to recover for the termination. Defendants’ threshold dismissal motions in this case present this question. And while the answer to this question is the same for both the substantive RICO offense alleged in Count I and the RICO conspiracy offense alleged in Count II, the analytical path to the answer is different for each count. With respect to the substantive RICO offense alleged in Count I,, settled authority from other circuits persuades the Court that plaintiff’s termination is not an “injury” that occurred “by reason of” the alleged racketeering acts. See 18 U.S.C. § 1964(c). In the case of the RICO conspiracy alleged in Count II, authority is sparse and in conflict. But the same answer applies because plaintiff’s termination was not caused by a predicate offense or a wrongful overt act. Accordingly, for the reasons stated here, the RICO counts (Counts I and II) must be dismissed for failure to state a claim upon which relief may be granted. See Rule 12(b)(6), Fed.R.Civ.P. The Court reserves its ruling with respect to the state claims asserted in Counts III and IV. Counsel for Datasec has withdrawn. Upon notification that new counsel has been acquired, the Court may order new briefs with respect to these Counts.

Background 2

Defendant, Datasec Corporation, is a New Hampshire company with its principal place of business in New Hampshire and an office in Virginia. It is engaged chiefly in the sale of “Tempest” computer products and technology. 3 Plaintiff, a Virginia citizen, was hired by Datasec in July 1988 to serve as Vice President of Sales. Individu *931 al defendants, Callaway and Williams, are New Hampshire citizens and respectively, Datasec’s president and vice-president for business development.

At the times relevant to the complaint, Datasec sold the “Paradyne” computer line. Acquired by AT & T in 1989, Paradyne followed a practice of handling only those equipment orders that exceeded $25,-000. Smaller orders were handled by certain dealers, including Datasec, specifically authorized by Paradyne to do so. Wary of the potential for kickbacks in return for steering orders, Paradyne had a strict policy in force prohibiting its employees from soliciting or accepting gratuities from dealers. Despite this, plaintiff alleges that Da-tasec paid gratuities to Paradyne’s customer referral personnel to induce them to steer business to Datasec. According to the complaint, this kickback scheme used interstate telephone communications and the U.S. mails, in violation of the mail and wire fraud statutes. See 18 U.S.C. §§ 1341, 1343.

By early 1989, plaintiff had become aware of this scheme. In April 1989, plaintiff informed defendants that he would not participate in the scheme. In response, defendant Callaway (i) demoted plaintiff to vice president of Eastern Regional Sales, (ii) named himself to replace plaintiff as “acting Vice President of Sales” and (iii) attempted unilaterally to change plaintiff’s compensation-commission agreement. Thereafter, on April 24, 1989, defendants terminated plaintiff. The complaint alleges this occurred because plaintiff persisted in his refusal either to countenance, or to participate in, the kickback scheme. The complaint also alleges that plaintiff, at all times, fully and satisfactorily performed his corporate duties.

On these facts, plaintiff asserts four claims against defendants. In Count I, plaintiff seeks treble damages and attorneys’ fees under RICO, claiming an injury to his business or property by reason of defendants’ conduct of an enterprise’s affairs through a pattern of racketeering activity. See 18 U.S.C. §§ 1962(c), 1964(c). Count II alleges a conspiracy to violate RICO and seeks the same damages. See 18 U.S.C. §§ 1962(d), 1964(c). Treble damages are also sought in Count III, which alleges that defendants conspired to injure plaintiff in his trade, business or profession in violation of Virginia Code §§ 18.2-499 and 18.2-500. Finally, Count IV asserts a breach of contract claim against Datasec for failure to pay plaintiff $8,690 in commissions due and owing, and refusing to sell plaintiff 2,000 shares of Datasec stock pursuant to a stock option. Defendants, in response, filed a motion to dismiss all claims pursuant to Rules 12(b)(1) and 12(b)(6).

Analysis

A. Count I: RICO

Under § 1964(c), standing to sue under RICO requires that a plaintiff’s injuries occur “by reason of” the predicate racketeering acts. As the Supreme Court in Sedima put it:

‘[a] defendant who violates section 1962 is not liable for treble damages to everyone he might have injured by other conduct. ...’
... [T]he compensable injury necessarily is the harm caused by predicate acts sufficiently related to constitute a pat-tern_ Any recoverable damages occurring by reason of a violation of § 1962(c) will flow from the commission of the predicate acts.

Sedima, S.P.R.L. v. Imrex Co., 473 U.S. 479, 496-97, 105 S.Ct. 3275, 3285, 87 L.Ed.2d 346 (1985) (quoting Haroco, Inc. v. American Nat’l Bank & Trust Co., 747 F.2d 384, 398 (7th Cir.1984), aff'd per curiam, 473 U.S. 606, 105 S.Ct. 3291, 87 L.Ed.2d 437 (1985)). Put simply, the “by reason of” language in § 1964(c) imports a proximate causation requirement into civil RICO. See O’Malley v. O’Neill, 887 F.2d 1557, 1561 (11th Cir.1989); Brandenburg v. Seidel, 859 F.2d 1179, 1189 (4th Cir.1988); Cullom v. Hibernia Nat’l Bank, 859 F.2d 1211, 1214 (5th Cir.1988); Sperber v. Boesky, 849 F.2d 60, 63 (2d Cir.1988); Haroco, 747 F.2d at 398.

The question presented here, therefore, is whether plaintiff’s firing was proximate *932

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

Related

Marshall v. Goguen
D. Montana, 2022
Storey v. Patient First Corp.
207 F. Supp. 2d 431 (E.D. Virginia, 2002)
Sadighi v. Daghighfekr
36 F. Supp. 2d 267 (D. South Carolina, 1999)
Virginia Heartland Bank v. Roberts
46 Va. Cir. 71 (Spotsylvania County Circuit Court, 1998)
Baglio v. Baska
940 F. Supp. 819 (W.D. Pennsylvania, 1996)
Williams v. Prince Georges County Hospital Center
932 F. Supp. 687 (D. Maryland, 1996)
Childress v. City of Richmond, Va.
907 F. Supp. 934 (E.D. Virginia, 1995)
National Organization for Women, Inc. v. Scheidler
897 F. Supp. 1047 (N.D. Illinois, 1995)
Cherokee Corp. v. Chicago Title Ins.
35 Va. Cir. 19 (Warren County Circuit Court, 1994)
Casper v. Paine Webber Group, Inc.
787 F. Supp. 1480 (D. New Jersey, 1992)

Cite This Page — Counsel Stack

Bluebook (online)
742 F. Supp. 929, 1990 U.S. Dist. LEXIS 8913, 1990 WL 99459, Counsel Stack Legal Research, https://law.counselstack.com/opinion/flinders-v-datasec-corp-vaed-1990.