Phoenix Renovation Corp. v. Gulf Coast Software, Inc.

197 F.R.D. 580, 2000 U.S. Dist. LEXIS 19650, 2000 WL 1752239
CourtDistrict Court, E.D. Virginia
DecidedNovember 22, 2000
DocketNo. Civ.A. 00-121-A
StatusPublished
Cited by9 cases

This text of 197 F.R.D. 580 (Phoenix Renovation Corp. v. Gulf Coast Software, Inc.) 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
Phoenix Renovation Corp. v. Gulf Coast Software, Inc., 197 F.R.D. 580, 2000 U.S. Dist. LEXIS 19650, 2000 WL 1752239 (E.D. Va. 2000).

Opinion

MEMORANDUM OPINION

BRINKEMA, District Judge.

On September 15, 2000, a magistrate judge issued a Report and Recommendation (“Report”), in which he recommended that a default judgment in the total amount of $158,218.00 plus costs be entered in favor of plaintiff, Phoenix Renovation Corp., t/a Phoenix Construction, Inc. against the defaulting defendant, Computer Dimensions Associates (“CDA”). The parties were advised that failure to object timely to the Report waived appellate review of any judgment entered on the basis of the Report. On September 28, 2000, the non-defaulting defendant, Gulf Coast Software, Inc., t/a Vertical Market Software (“VMS”) filed an objection to many of the Report’s factual findings about its software products. VMS also complained that plaintiff is trying to circumvent its obligation to arbitrate disputes over VMS’ software by “proving its case” in these default proceedings. The defaulting defendant, [581]*581CDA, filed no objections and therefore has waived appellate review of any judgment based on the Report.

Having fully reviewed the case file, the Report and VMS’ objections, we accept the Report and the magistrate’s recommendations with the limitations and restrictions set forth herein.

I. Procedural Background

On January 24, 2000, plaintiff, a Virginia corporation with its principal place of business in Virginia, filed this three count diversity action against VMS, a Florida corporation with its principal place of business in Florida, and CDA, a Delaware corporation with its principal place of business in Pennsylvania. The gravamen of Phoenix’s complaint is that software manufacturer VMS and software distributor CDA together convinced Phoenix to purchase VMS-manufactured accounting software products from CDA through deliberate misrepresentations of the software’s capabilities and that these products failed to satisfy either Phoenix’s specifications or the defendants’ representations. The complaint charges both defendants with Breach of Contract-Gross Negligence-Willful Misconduct (Count 1), Breach of Express and Implied Warranties (Count 2), and Fraud in the Inducement (Count 3).

On February 16, 2000, a process server attempted to serve CDA. When he arrived at defendant’s address, the woman who answered the door and acknowledged the address was for CDA, refused to accept process. See Process Return, file entry 2. Service was again attempted on July 30, 2000. This time a copy of the complaint and summons were served on Vance Anderberry, the defendant’s CEO. Since that time, CDA has not filed an answer or made any appearance in this case.

Before the plaintiffs second effort to serve CDA, VMS moved for a stay of litigation pending the conclusion of arbitration proceedings prescribed by VMS’s contract with Phoenix.1 On April 7, 2000, VMS’s motion was granted, this litigation was stayed with respect to both defendants, and plaintiff and VMS were “directed to proceed to arbitration.” See Phoenix Renovation Corp. v. Gulf Coast Software et al., No. 00-121-A (E.D.Va. April 7, 2000).

Phoenix subsequently successfully moved for leave to pursue a default judgment against CDA which, unlike VMS, had never appeared in any capacity or responded to the complaint at all. Plaintiff pointed to the admonition in Fed.R.Civ.P. 55(a) that default judgment “shall” be entered against defendants failing to “plead or otherwise defend” against claims for affirmative relief. Plaintiffs Motion for Leave to File Motion for Entry of Default Judgment and Motion to Show Cause Why Default Judgment Should Not Be Entered at 2. On May 5, 2000, a magistrate judge lifted the stay of litigation “to the extent that default judgment may be sought against [CDA].” Phoenix Renovation Corp. v. Gulf Coast Software et al., CA-00-121-A (E.D.V.A. May 5, 2000) On August 9, 2000, Phoenix moved for the entry of default against CDA and for the subsequent entry of a default judgment in the amount of $158,218.2

II. The Magistrate’s Report and Recommendation

Based solely on the uncontested facts alleged in the complaint, the Report concludes that CDA breached its contract with Phoenix, breached several implied and express warranties made to Phoenix, and fraudulently misrepresented and failed to disclose VMS’s alleged misrepresentations of the software’s capabilities. Report at 2-4. Because [582]*582CDA has not contested any of these facts, they are deemed admitted as against CDA only. The magistrate judge found Phoenix’s claims for reimbursement of the $42,400.00 purchase price plus $115, 818 in incidental damages to be appropriately supported by declarations. Report at 4.

Although CDA did not object to the Report, CDA’s non-defaulting co-defendant, VMS, opposes entry of a default judgment against CDS until the resolution of its dispute with Phoenix. VMS contends that the April 7, 2000 order instructing VMS to arbitrate its dispute with Phoenix restrained VMS from challenging the evidence on which Phoenix’s default judgment relies. VMS argues that entry of default judgment against CDS would “penalize” VMS for awaiting arbitration, contravening federal policy favoring arbitration proceedings. See O’Neil v. Hilton Head Hospital, 115 F.3d 272, 273 (4th Cir.1997).

VMS implies that it would be “penalized” through the preclusive effects of a default judgment in subsequent arbitration or litigation. Although the contours of collateral estoppel vary between jurisdictions, it is highly unlikely that VMS would be charged with the preclusive effects of a default judgment against CDA in the absence of privity between them. See Horton v. Morrison, 248 Va. 304, 448 S.E.2d 629, (1994) (default judgment in action by third party lacks preclusive effect in action by different plaintiff). In any event, we need not resolve the preclusion issue because considerations of judicial economy and consistency independently compel us to postpone entry of default judgment against CDA until the conclusion of Phoenix’s action against VMS.

III. Discussion

Fed.R.Civ.P. 54(b)3 authorizes entry of a final judgment as to one of multiple defendants in a civil action following an express finding that “there is no just reason for delay.” The avoidance of logically inconsistent judgments in the same action and factually meritless default judgments provide “just reason.”

When more than one claim for relief is presented in an action, whether as a claim, counterclaim, cross-claim, or third-party claim, or when multiple parties are involved, the court may direct the entry of a final judgment as to one or more but fewer than all of the claims or parties only upon an express determination that there is no just reason for delay and upon an express direction for the entry of judgment. In

The United States Supreme Court first confronted this issue in Frow v. De La Vega, 15 Wall. 552, 82 U.S. 552, 21 L.Ed. 60 (1872). Frow

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

Related

Johnson v. Singh
D. Maryland, 2019
Vick v. Wong
263 F.R.D. 325 (E.D. Virginia, 2009)
Jones v. Luthi
586 F. Supp. 2d 595 (D. South Carolina, 2008)
Jefferson v. Briner, Inc.
461 F. Supp. 2d 430 (E.D. Virginia, 2006)
Shanghai Automation Instrument Co., Ltd. v. Kuei
194 F. Supp. 2d 995 (N.D. California, 2001)

Cite This Page — Counsel Stack

Bluebook (online)
197 F.R.D. 580, 2000 U.S. Dist. LEXIS 19650, 2000 WL 1752239, Counsel Stack Legal Research, https://law.counselstack.com/opinion/phoenix-renovation-corp-v-gulf-coast-software-inc-vaed-2000.