From Casetext: Smarter Legal Research

BAE SYSTEMS N. AMERICA INC. v. LOCKHEED MARTIN CORP.

Court of Chancery of Delaware, New Castle County
Aug 3, 2004
C.A. No. 20456 (Del. Ch. Aug. 3, 2004)

Summary

finding no duty to disclose to correct past predictive statements regarding the likelihood of success in litigation.

Summary of this case from Osram Sylvania Inc. v. Townsend Ventures, LLC

Opinion

C.A. No. 20456.

Submitted: June 7, 2004.

Decided: August 3, 2004.

Richard L. Horwitz, Esquire and Erica L. Niezgoda, Esquire of Potter Anderson Corroon LLP, Wilmington, Delaware and Daniel Slifkin, Esquire and Antony L. Ryan, Esquire of Cravath, Swaine Moore LLP, New York, New York, Attorneys for Plaintiffs.

Samuel A. Nolen, Esquire, Jeffrey L. Moyer, Esquire, and Anne Shea Gaza, Esquire of Richards, Layton Finger, P.A., Wilmington, Delaware, Attorneys for Defendant.


MEMORANDUM OPINION


Plaintiffs BAE Systems North America Inc. ("BAE") and BAE Systems Information and Electronic Systems Integration Inc. and Defendant Lockheed Martin Corporation ("Lockheed") are defense and aerospace contractors. In 2000, BAE purchased the assets of Lockheed's Sanders division. At the time of the transaction, Lockheed, through its unincorporated Sanders division and its wholly-owned subsidiary, Lockheed Martin Federal Systems, Inc. ("Federal"), was a defendant in an action pending in California. In accordance with the agreement by which BAE bought the Sanders division, BAE undertook the defense of the action. That agreement was intended to allocate any liability that might result from the California action. For BAE and Lockheed, that action turned out rather badly, and BAE filed suit in this Court to sort out where that liability, as between BAE and Lockheed, falls. In response to BAE's complaint, Lockheed filed a counterclaim relying upon theories of breach of contract, breach of fiduciary duty, equitable fraud, and reformation. Before the Court are the parties' cross-motions for partial judgment on the pleadings and the Plaintiffs' motion to dismiss Lockheed's counterclaims.

I. BACKGROUND

A. The Transaction

In July 2000, Lockheed agreed to sell its Aerospace and Electronic Systems business (the "AES Business") to BAE for $1.67 billion. The central component of the AES Business was the unincorporated business unit of Lockheed known as "Sanders." This agreement was formalized in the Transaction Agreement, dated July 13, 2000. The transaction was structured as a sale of assets. In order to effect the sale of assets, Lockheed and its affiliates and BAE executed the Bill of Sale, Assignment and Assumption Agreement at closing on November 27, 2000.

Sanders, as a result of the acquisition and subsequent events, is essentially now BAE Systems Information and Electronic Systems Integration, Inc. In fact, that company was formerly known as BAE Systems Sanders, Inc. Compl. ¶ 3.

B. The CCT Litigation

At the heart of the dispute arising out of the Transaction Agreement is litigation (the "CCT Litigation") initiated by Cable and Computer Technology, Inc. ("CCT") in June 1997 against Lockheed, Federal, and Sanders. CCT's complaint, alleging breach of contract, promissory estoppel, fraud, intentional interference with prospective economic advantage, unfair business practices, and violation of California's Cartwright Act, sought both compensatory and punitive damages. Following its acquisition of the AES Business, BAE undertook the defense of the CCT Litigation.

The CCT Litigation was based on the following facts. CCT and Federal were competing for a contract with Boeing Corporation involving a computer system upgrade for the B1-B bomber. Sanders had joined in a teaming arrangement with CCT under which CCT would be the bidder and Sanders would provide subcontract work to CCT. Sanders withdrew from the arrangement shortly before the deadline to submit bids, and Federal subsequently won the contract.

CCT alleged that Lockheed, Federal, and Sanders acted in concert to deprive CCT of an opportunity to win the contract. Specifically, CCT alleged that Lockheed and Federal induced Sanders to withdraw from the teaming agreement. On April 13, 1998, the United States District Court for the Central District of California granted summary judgment on all counts to the defendants. In a May 31, 2000 decision, the United States Court of Appeals for the Ninth Circuit reversed the District Court, reinstated all but the unfair business practices and Cartwright Act counts, and remanded the case for trial.

Cable Computer Tech., Inc. v. Lockheed Sanders, Inc., 214 F.3d 1030 (9th Cir. 2000).

The Transaction Agreement, under which the AES Business (including the Sanders business) was transferred to BAE, was entered into less than two months thereafter. After closing in November 2000, BAE took control of the defense of the CCT Litigation. Trial began in February 2001, and on March 28, 2001, a jury verdict was entered for CCT against all three defendants as to liability. During the damages phase of the trial, the defendants proposed a special verdict form that allowed the jury to allocate liability to Sanders and Federal separately. On April 5, 2001, the jury awarded CCT compensatory damages of $11,270,902 (with the defendants jointly and severally liable) and punitive damages totaling $53,276,000 — half of which was assessed against Sanders/Lockheed and half against Federal. The trial judge, upon the defendants' motion, reduced these amounts to $5,762,902 in compensatory damages (jointly and severally) and $12,867,500 in punitive damages against Sanders/Lockheed and the same against Federal (the "CCT Liability").

The alternative would have been to have combined all of the Lockheed liability, including both Sanders and Federal, together.

Cable Computer Tech, Inc. v. Lockheed Sanders, Inc., No. CV 97-5315 CM (C.D. Cal. Oct. 15, 2001) (revised judgment).

On January 27, 2003, following an unsuccessful appeal BAE paid $33,809,512.44, for satisfaction of the CCT judgment against all defendants. Whether Lockheed must reimburse BAE for some or all of that payment is the question posed in this proceeding.

Cable Computer Tech, Inc. v. Lockheed Sanders, Inc., 2002 WL 31689043 (9th Cir. Nov. 27, 2002).

C. The Transaction Agreement

As a general matter, with its acquisition of Sanders' assets, BAE, in accordance with the Transaction Agreement, also acquired Sanders' liabilities. BAE took responsibility for those obligations defined by the Transaction Agreement as "Assumed Liabilities," but responsibility for the obligations defined as "Excluded Liabilities" remained with Lockheed. The parties dispute whether the CCT Liability is among "Assumed Liabilities" or "Excluded Liabilities."

The Transaction Agreement provides in part:

"Assumed Liabilities" means all liabilities and obligations of Seller Companies of any kind, character or description, . . . to the extent relating to or arising out of the operation, affairs or conduct of the AES Business or the Transferred Assets, including but not limited to the following (other than Excluded Liabilities):
(i) all liabilities and obligations, . . . at or prior to the Closing, that . . . (b) are disclosed in any of the Disclosure Schedules delivered hereunder . . .
(ii) all liabilities and obligations arising under Contracts . . ., including, without limitation, liabilities and obligations arising from or relating to the performance or nonperformance of the Contracts by the AES Business, a Buyer Company or any other Person, whether arising prior to, on or after the Closing Date;
(xi) all liabilities and obligations arising from or relating to governmental, judicial or adversarial proceedings (public or private), [or] litigation . . . arising from or directly or indirectly relating to the AES Business or any Transferred Assets, . . .

Transaction Agreement at A-2-3, Transmittal Aff. of Anne Shea Gaza Ex. A.

The term "Seller Companies" is defined as Lockheed and its subsidiaries. The AES Business includes Sanders, but not Federal. The CCT Litigation is listed on Disclosure Schedule B.09.

The Excluded Liabilities that the definition of Assumed Liabilities references are defined to include:

(v) all liabilities or obligations, whether presently in existence or arising after the date of this Agreement, relating to or arising primarily out of Excluded Assets or any business of Seller Companies other than the AES Business;

Id. at A-8.

Excluded Assets include Federal assets.

D. The Current Litigation

BAE's complaint seeks reimbursement from Lockheed for the amount it paid in satisfaction of the CCT Liability, in addition to attorneys' fees and expenses incurred in the CCT Litigation. Its complaint is based on breach of contract and unjust enrichment. The breach of contract claim relies on the indemnification provision in the Transaction Agreement requiring Lockheed to indemnify BAE for any damages incurred by BAE relating to the contractually defined Excluded Liabilities. BAE argues that the CCT Liability is among those Excluded Liabilities because, inter alia, it "relat[es] to Federal."

The indemnification provision is set forth at section 11.02(b) of the Transaction Agreement. It states, "[e]ffective as of the Closing . . . Seller hereby indemnifies Buyer . . . from, any and all Damages incurred or suffered by any of them arising out of, resulting from or related in any way to . . ., (ii) any Excluded Liabilities. . . ."

Lockheed's answer asserts five counterclaims. The first of the counterclaims seeks a declaratory judgment that the CCT Liability is contractually defined as one of the Assumed, as opposed to Excluded, Liabilities and, thus, is for BAE's account. Counterclaim Count V seeks reformation of the Transaction Agreement if its language is found to exclude the CCT Liability from the definition of Assumed Liabilities. Counterclaim Counts II-IV, based on breach of contract, equitable fraud, and breach of fiduciary duty respectively, are rooted in the decision to seek a special verdict form in the damages phase of the CCT Litigation. Both sides have moved for partial judgment on the pleadings. The Plaintiffs also seek dismissal of Lockheed's counterclaims. The Plaintiffs' claim for unjust enrichment is not contested at this stage.

BAE has moved for partial judgment on the pleadings with respect to its contract claim as set forth in Count I of its Complaint. Lockheed has moved for partial judgment on the pleadings with respect to its Counterclaim Count I in which it seeks a declaratory judgment regarding the proper interpretation of the contract between the parties, a claim which mirrors Count I of BAE's Complaint.

II. STANDARDS

In considering a motion to dismiss under Court of Chancery Rule 12(b)(6), the Court is required to accept as true all of the nonmoving party's well-pleaded factual allegations and to draw all reasonable inferences in the light most favorable to the nonmoving party. The motion may not be granted unless it appears with reasonable certainty that the nonmoving party would not be entitled to relief under any set of facts that it could prove at trial.

Anglo Am. Sec. Fund, L.P. v. S.R. Global Int'. Fund, L.P., 829 A.2d 143, 149 (Del.Ch. 2003); Orman v. Cullman, 794 A.2d 5, 15-16 (Del.Ch. 2002).

Judgment on the pleadings under Court of Chancery Rule 12(c) "may be granted only when no material issue of fact exists and the movant is entitled to judgment as a matter of law." In deciding cross-motions for judgment on the pleadings, the Court will take the well-pleaded facts contained in the complaint and the counterclaim and "view the facts pleaded and the inferences to be drawn from such facts, in a light most favorable to the non-moving party."

Court of Chancery Rule 12(c) states in part: "After the pleadings are closed but within such time as not to delay the trial, any party may move for judgment on the pleadings."

Desert Equities, Inc. v. Morgan Stanley Leveraged Equity Fund II, L.P., 624 A.2d 1199, 1205 (Del. 1993).

Id. "[C]ourts generally apply the same standard of review to motions for judgment on the pleadings and summary judgment." Id. at 1205, n. 9 (citing WRIGHT MILLER, FEDERAL PRACTICE PROCEDURE, CIVIL 2d § 1369 at 534-35). But see Acierno v. Goldstein, 2004 WL 1488673, at *2 (Del.Ch. June 25, 2004) ("The Rule 12(c) standard has been described as `almost identical' to the 12(b)(6) standard and favors the claimant.") (quoting Cantor Fitzgerald, L.P. v. Cantor, 2001 WL 1456494, at *4 (Del.Ch. Nov. 5, 2001). Although apparently at odds with each other, these different formulations of the standard governing Rule 12(c) are contextual. When the question is whether to dismiss a claim in the context of a motion for judgment on the pleadings, the inquiry follows the procedures established by Rule 12(b)(6) jurisprudence. If affirmative relief is sought, the analysis is substantially the same, although subject to the constraint of a more limited record, as that for summary judgment motions.

III. ANALYSIS

A. Contract Interpretation — BAE's Contract Claim and Lockheed's Declaratory Judgment Application

Because the transaction was structured as a sale of assets, the parties agree that, under the present circumstances, the liabilities associated with those assets are transferred only by operation of the Transaction Agreement. Thus, it is necessary to apply the Transaction Agreement to the alleged facts.

In passing on a contract dispute, the Court first looks to the express terms of the contract to see "whether the parties' intent can be discerned" from those terms. If the terms of the contract are clear on their face, the Court will give those terms the meaning that "would be ascribed to [them] by a reasonable third party." If, however, a contract's provisions are "reasonably susceptible to two or more meanings," the Court will deem that contract ambiguous and will consider extrinsic evidence to discern the "reasonable shared expectations of the parties at the time of contracting." In making this determination, the Court "must interpret contractual provisions in a way that gives effect to every term of the instrument, and that, if possible, reconciles all of the provisions of the instrument when read as a whole."

Comrie v. Enterasys Networks, Inc., 837 A.2d 1, 13 (Del.Ch. 2003).

True North Communications, Inc. v. Publicis, S.A., 711 A.2d 34, 38 (Del.Ch. 1997), aff'd, 705 A.2d 244 (Del. 1997).

Amtower v. Hercules, Inc., 1999 WL 167740, at *11 (Del.Super. Feb. 26, 1999).

Comrie, 837 A.2d at 13.

Council of Dorset Condo. Apartments v. Gordon, 801 A.2d 1, 7 (Del. 2002).

Under the terms of the Transaction Agreement, BAE took on the "Assumed Liabilities." Assumed Liabilities, for purposes of the current litigation, are "all liabilities and obligations of [Lockheed] . . . to the extent relating to or arising out of the operation, affairs or conduct of [Sanders]." There is a carve out to this definition, however. The parenthetical in the definition of Assumed Liabilities, "(other than Excluded Liabilities)," means that a liability that may initially be categorized as an Assumed Liability, may be removed from that category if it falls within "Excluded Liabilities." Excluded Liabilities, again for purposes of this litigation, include "all liabilities . . . relating to or arising primarily out of [Federal]."

This exclusion applies with equal force to those liabilities categorized as Assumed Liabilities because they appear on the list of specifically enumerated liabilities following the general definition of Assumed Liabilities as it does to those liabilities categorized as Assumed Liabilities solely through the general definition of Assumed Liabilities.

Thus, to the extent a liability is "relating to or arising out of" Sanders, it is an Assumed Liability unless it is "relating to or arising primarily out of" Federal, in which case it is an Excluded Liability. BAE argues that although the CCT Liability relates to Sanders, it also relates to Federal and, therefore, is an Excluded Liability. Lockheed argues the CCT Liability is not excluded because, while it may relate to Federal, it does not "arise primarily out of" Federal.

If the CCT Liability is an "Excluded Liability," not only did BAE not acquire that burden under the Transaction Agreement, but also BAE would be entitled to indemnification by Lockheed for that obligation.

Accordingly, both parties agree that at least some of the CCT Liability "relates to" and "arises out of" Sanders. Both parties also agree that at least some of the CCT Liability "relates to" and "arises out of" Federal. But the critical definition of Excluded Assets is not "relating to or arising out of"; instead, it is "relating to or arising primarily out of." While both parties agree the CCT Liability "relates to" Federal, it is unclear whether the CCT Liability "arises primarily out of" Federal.

The improper severing of the CCT teaming agreement, the immediate wrong leading to the CCT Litigation, was accomplished by those Lockheed employees managing the Sanders assets. The impetus for severing the relationship appears to have come from the Federal business segment and, perhaps significantly, the benefits from the severing accrued not to the Sanders business segment but to Federal, which was then able to secure the contact. In short, as of now, the onus is with Sanders ( i.e., BAE) and the bonus is with Federal.

This, then, requires the Court to interpret the phrase "relating to or arising primarily out of." Clearly, anything "arising primarily out of" Federal would also be "relating to" Federal. But something "relating to" Federal may not always be "arising primarily out of" Federal. Thus, to the extent "relating to" has independent meaning, it nullifies the independent narrowing effect of "primarily" in "arising primarily out of." To the extent "arising primarily out of" has independent meaning, however, it precludes "relating to" from having independent significance.

Motorola, Inc. v. Amkor Technology, Inc., teaches Delaware courts the proper approach for resolving such issues. In that case, a "patent license agreement" provided Amkor (the licensee) with an undivided one-half interest in two of Motorola's patents. The agreement precluded Amkor from licensing its rights under that agreement to any third party who was also a licensee of Motorola (the licensor). The agreement, however, allowed Amkor to assign its rights under the agreement to "a successor in ownership of all or substantially all of the assets of" Amkor. Amkor proceeded to "assign" its rights under the agreement, including its undivided one-half interest in the Motorola patents, to Citizen. At that time, Citizen was a licensee of Motorola.

849 A.2d 931 (Del. 2004).

Id. at 931.

In disputing whether such an "assignment" was valid under that agreement, Amkor argued that "because the terms `license' and `assignment' have distinct meanings," the agreement permitted an assignment. Motorola argued that in the context of the agreement, the term "`license' [was] subsumed within an `assignment.'" While the Superior Court on cross-motions for summary judgment concluded that the clear meaning of the agreement permitted the assignment, the Supreme Court, despite the fact both parties before the Superior Court had taken the position that there were no material facts in dispute, held that since both interpretations of the agreement "may be reasonable," summary judgment should have been denied.

Id. at 934-35.

Id. at 937.

Id. Although the Supreme Court was applying Illinois law, the standards set forth in Motorola for contract interpretation under Illinois law do not differ materially from those guiding Delaware courts. Specifically, in applying Illinois law, the Supreme Court wrote, "[w]here more than one plausible construction of a contract exists or the contract is ambiguous because two or more key provisions conflict, an issue of material fact arises and summary judgment must be denied." Id.

Based on this reasoning, the cross-motions for partial judgment on the pleadings with respect to the meaning to be given to the contractual language are denied. The parties have set forth "more than one plausible construction of" the meaning of Excluded Liabilities. BAE's reading would give no independent significance to "arising primarily out of." Lockheed's reading would give no independent significance to the general phrase of "relating to." The parties, by utilizing the phrase "arising out of' in their definition of Assumed Liabilities, but defining Excluded Liabilities to contain the phrase "arising primarily out of," seem to have demonstrated an intent to afford the word "primarily" an independent meaning. The significance of "primarily," a term of the contract to which some effect should be ascribed, if possible, however, is unclear at this stage.

This is not to say that this case will necessarily proceed beyond any possible summary judgment motions. Although "[c]ross-motions for summary judgment are not the procedural equivalent of a stipulation of decision on a paper record," id. at 935-36, the Court may be presented with sufficient uncontroverted evidence at the summary judgment stage to decide this issue. Indeed, at the summary judgment stage, the Court may consider events that the sides have addressed here, but which the Court could not, at the pleadings stage, take into account in resolving any ambiguity in the Transaction Agreement ( e.g., history of negotiations and the parties' conduct before and after closing of the Transaction Agreement) because the record has not been, and, as a practical matter, could not have been, sufficiently developed.

Id. at 937.

Council of Dorset Condo. Apartments, 801 A.2d at 7.

Another aspect of the mechanism for allocating liabilities between BAE and Lockheed also merits mention. The drafters' use of the phrase "to the extent" in the definition of Assumed Liabilities prompts the following possible reading of the agreement. Even if the CCT Liability is an Assumed Liability, but not an Excluded Liability, BAE would be responsible only "to the extent" that the CCT Liability "relat[es] to or aris[es] out of" the Sanders operations. If that is a proper reading, it would suggest that a fact-intensive analysis may be required. This type of complication was anticipated by the drafters of the Transaction Agreement who defined the term "Shared Assumed Liabilities" and created a formula for sharing some liabilities, but excluded certain disclosed liabilities, such as the CCT Litigation, from its scope.

For the above reasons, and following Motorola, the cross-motions for partial judgment on the pleadings as to the interpretation of the Transaction Agreement are denied.

B. Mistake — Lockheed's Claim for Reformation

Lockheed pleads that if "the Agreement were found to provide that liability for the CCT Litigation did not pass to BAE, the Agreement fails to express the parties' mutual understanding and agreement on this issue and Lockheed . . . is entitled to reformation of the Agreement to reflect the parties' mutual understanding at the time the Agreement was executed." Lockheed, then, would seek reformation of the Transaction Agreement based on the theory of mistake.

Countercl. ¶ 61.

In Interactive Corp. v. Vivendi Universal, S.A., this Court noted the limited nature of mistake claims: "Though mistake is a necessary legal tool to reform contracts that do not reflect the parties' intent because of problems such as scriveners' errors, it must be applied narrowly so as to ensure to contracting parties that in only limited circumstances will the court look beyond the four corners of a negotiated contract." Thus, Court of Chancery Rule 9(b), working in conjunction with the substantive requirements of both the mutual and unilateral theories of mistake, requires a pleading of mistake, to survive a pleadings stage motion, to allege with particularity some form of specific prior agreement. Lockheed's shallow pleading that invites the Court to read the Transaction Agreement as not in conformity with a prior "mutual understanding and agreement," without more, takes the form of "conclusory factual allegations [that] do not suffice for a claim of mistake to survive a motion [to dismiss.]"

Interactive Corp. v. Vivendi Universal, S.A., 2004 WL 1572932, at *15 (Del.Ch. June 30, 2004).

Court of Chancery Rule 9(b) provides: "In all averments of fraud or mistake, the circumstances constituting fraud or mistake shall be stated with particularity."

Mutual mistake requires both parties to be mistaken as to a material portion of a written agreement. Unilateral mistake requires that one party be mistaken and that the other party know of the mistake but remain silent. Cerberus Int'l Ltd. v. Apollo Mgmt., L.P., 794 A.2d 1141, 1151-52 (Del. 2002). Both theories of mistake, however, require a showing that "the parties came to a specific prior understanding that differed materially from the written agreement." Id.

See Interactive Corp, 2004 WL 1572932, at *15-*16. In addition, a party pursuing a mistake claim will be required to satisfy the "clear and convincing evidence" standard. Cerberus Int'l Ltd., 794 A.2d at 1149.

Interactive Corp, 2004 WL 1572932, at *16.

While none alone is dispositive of the current motion, there is a distinct shortfall in the allegations as to which individuals came to the specific prior agreement, the terms of the specific prior agreement, at what point the mistake was introduced, or any negotiating history. Moreover, pleading that Lockheed disclosed the CCT Litigation on draft disclosure schedules or that BAE conducted due diligence investigations prior to closing does not make up for the lack of pleading of a specific prior agreement. Finally, the pleading of actions taken after closing is not substitutable for an express pleading that the parties came to a specific prior agreement. Simply put, a claim for reformation based on mistake must be based on something more than a conclusory allegation of a mutual understanding and agreement on the issue. Lockheed's Counterclaim V, therefore, is dismissed.

Cf. id. at *17 ("While the nature of mistake claims allows parol evidence to be used as proof of a mistake at the summary judgment or trial stage, it is unclear whether such evidence, when properly before the court at the pleadings stage, may be used to discern an allegation of a specific prior agreement in the absence of an explicit allegation. . . . This is not the type of inquiry a motion on the pleadings typically invites.").

C. BAE's Conduct in Defending the CCT Litigation — Lockheed's Claims of Breach of Contract and Breach of Fiduciary Duty

Lockheed's breach of contract and breach of fiduciary duty counterclaims are both based on allegations that defense counsel in the then-BAE-controlled CCT Litigation structured the damages verdict form in a way so as to enhance BAE's position in the current litigation. Whether or not BAE did so is a question of fact that may not be decided in a motion to dismiss. What must be decided here is whether, viewing Lockheed's allegations as true and drawing all reasonable conclusions flowing from them in Lockheed's favor, Lockheed presents a viable claim under one of the two legal theories.

Lockheed's breach of contract counterclaim is premised on an alleged breach of section 11.03(b)(i) of the Transaction Agreement. That section provides that since BAE was controlling the CCT Litigation, it had the duty to "at all times act as if all Damages relating to the [litigation] were for its own account and [to] act in good faith and with reasonable prudence to minimize Damages therefrom." If BAE acted as, and with the intent that, Lockheed claims, it may have breached this provision of the Transaction Agreement. This is a question of fact. Lockheed's breach of contract counterclaim, therefore, survives BAE's motion to dismiss.

Transaction Agreement § 11.03(b)(i).

BAE argues that if Lockheed's interpretation of the Transaction Agreement is correct, there would be no harm because everything flowing from the CCT Litigation would be an Assumed Liability. In substance, Lockheed's claim is the mirror image of BAE's direct claims. Thus, this dispute is fairly joined.
Second, BAE argues that because the jury had already decided liability on a verdict form identifying the various defendant entities, proposing a similar verdict form for damages could not cause harm. The possibility that a separate verdict form for damages may have caused jurors to award a higher amount of punitive damages or allocated them in a particular direction cannot be discounted in considering a motion to dismiss.
Finally, BAE argues that the punitive damages award could not be assessed against the CCT defendants collectively because courts could not then conduct a meaningful review of the constitutionally of the award under the rubric set out in BMW of N. Am., Inc. v. Gore, 517 U.S. 559 (1996). That rubric requires an analysis of a party's "degree of reprehensibility." Id. at 575. What is before this Court is whether BAE, in instructing defense counsel to push for the separate damages verdict, breached its duty under the Transaction Agreement.

Lockheed's breach of fiduciary duty counterclaim, however, will be dismissed. That counterclaim is based on the same operative facts as its breach of contract counterclaim. As this Court has previously held, claims sounding in fiduciary duty that cannot be brought independently of claims based on breach of contract will not survive a motion to dismiss. Here, BAE's duties in conducting the CCT Litigation are set forth in Section 11.03 of the Transaction Agreement.

See Madison Realty Partners 7, LLC v. AG ISA, LLC, 2001 WL 406268, at *6 (Del.Ch. Apr. 17, 2001) (dismissing a breach of fiduciary duty claim because "the contract and fiduciary claims overlap" and "are based on the same underlying conduct"); Gale v. Bershad, 1998 WL 118022, at *5 (Del.Ch. Mar. 4, 1998) ("To allow a fiduciary duty claim to coexist in parallel with [a contractual] claim, would undermine the primacy of contract law over fiduciary law in matters involving . . . contractual rights and obligations."), quoted in Madison Realty Partners 7, LLC, 2001 WL 406268, at *6.

Lockheed argues that its "fiduciary duty claim is based on more than just BAE's contractual duty to defend" since "BAE's fiduciary duty arose out of the totality of the relationship between the parties — not only out of BAE's contractual obligations as set forth in Section 11.03." But, in the same breath, Lockheed admits that "both claims are rooted in Section 11.03 of the Transaction Agreement." The language of the pleadings shows that the actions underlying Lockheed's breach of contract counterclaim are the same as the actions underlying Lockheed's breach of fiduciary duty counterclaim. Therefore, the Court will address the actions under "contract principles," and Lockheed's Counterclaim Count IV is dismissed.

Lockheed Martin's Opening Br. in Supp. of Def.'s Mot. for Partial J. on the Pleadings and Answering Br. in Opp'n to BAE's Mot. for Partial J. on the Pleadings and Mot. to Dismiss Countercls., at 45.

Id.

Compare Countercl. ¶ 37 ("Under the Agreement, once BAE assumed control and defense of the CCT Litigation, it had an obligation to at all times act as if all Damages relating to [CCT's] claim were for its own account and [to] act in good faith and with reasonable prudence to minimize damages therefrom.") (citations and internal quotations omitted), with Countercl. ¶ 54 ("Pursuant to the Agreement, BAE assumed responsibility to control and defend the CCT Litigation."), and Countercl. ¶ 55 ("Lockheed Martin was lulled into believing that its interests would be fully defended by virtue of the special relationship formed with BAE by the Agreement and as evidenced by BAE's conduct after closing the sale of the AES Business.") (emphasis added). Compare also Countercl. ¶ 42 ("Having so manipulated the jury special verdict form, BAE asserts that that [sic] Lockheed Martin retained liability for the CCT Litigation. This contention would not have been available had the jury special verdict form not artificially separated out particular business units (Lockheed Martin Sanders and Lockheed Martin Federal Systems) of a single entity (Lockheed Martin Corporation)."), with Countercl. ¶ 57 ("By surreptitiously changing the jury special verdict form, BAE breached its fiduciary obligation to Lockheed Martin. In doing so, BAE failed to defend the case for the full benefit of Lockheed Martin pursuant to Section 11.03.").

See Moore Bus. Forms, Inc. v. Cordant Holdings Corp., 1995 WL 662685, at *6 (Del.Ch. Nov. 2, 1995) ("[D]isputes that relate to obligations expressly treated and rights [that are] created by contract will be governed by contract principles.") (citations and internal quotations omitted). There is no suggestion that any special relationship had developed before the Transaction Agreement was negotiated; indeed, BAE and Lockheed were competitors. They freely agreed to the terms of their relationship; nothing in Lockheed's counterclaim affords a basis for imposing duties on BAE, as sought by Lockheed, beyond those which were negotiated.

D. Lockheed's Claim of Equitable Fraud

Lockheed's third counterclaim is labeled "equitable fraud." "To state a prima facie case for equitable fraud, [a] plaintiff must . . . satisfy all the elements of common-law fraud with the exception that [the] plaintiff need not demonstrate that the misstatement or omission was made knowingly or recklessly." Thus the elements of equitable fraud are the same as those for common-law fraud, except that no showing of scienter need be made.

Zirn v. VLI Corp., 681 A.2d 1050, 1061 (Del. 1996).

There are three types of common law fraud: 1) representing false statements as true; 2) actively concealing facts which prevents the plaintiff from discovering them; or 3) remaining silent in the face of a duty to speak. Expressing opinions or predictions about the future, however, "cannot give rise to actionable common law fraud."

In order to make out a claim for equitable fraud based on a false representation, one must show, in addition to a false representation: 1) an intent to induce the plaintiff to act or refrain from acting; 2) that the plaintiff's action (or inaction) was taken in justifiable reliance upon the representation; and 3) damage to the plaintiff from her reliance on the representation. Gaffin v. Teledyne, Inc., 611 A.2d 467, 472 (Del. 1992).

See Metro Communication Corp. BVI v. Advanced Mobilecomm Techs. Inc., 2004 WL 1043728, at *15 (Del.Ch. Apr. 30, 2004) ("In order to state a claim of fraud by active concealment, [a plaintiff] must show that a `defendant took some action affirmative in nature designed or intended to prevent, and which does prevent, the discovery of facts giving rise to the fraud claim, some artifice to prevent knowledge of the facts or some representation intended to exclude suspicion and prevent inquiry.'") (quoting Lock v. Shreppler, 426 A.2d 856, 860 (Del.Super. 1981), superseded by statute on other grounds).

Id. at *11.

Great Lakes Chem. Corp. v. Pharmacia Corp., 788 A.2d 544, 554 (Del. 2001). This is not to say that providing a false representation of one's opinion cannot constitute actionable fraud. "A statement of belief may be open to objection . . . solely as a misstatement of the psychological fact of the speaker's belief in what he says." Virginia Bankshares, Inc. v. Sandberg, 501 U.S. 1083, 1095 (1991).

Lockheed essentially makes two arguments under the "equitable fraud" heading. The first is fundamentally a rehash of Lockheed's breach of contract argument. Lockheed argues that "BAE was in complete control of the litigation and did not express any belief or contention to Lockheed Martin that any potential liability in the CCT case had not been fully assumed by BAE under the Agreement," and that by crafting the special jury verdict the way it did, BAE "positioned itself to try to shift all or part of the liability to Lockheed Martin." Lockheed best summarizes this line of argument, alleging that "[b]ecause of BAE's failure to disclose the material fact that it was no longer willing fully and faithfully to defend Lockheed Martin's interests, Lockheed Martin now faces a potential liability for which it is not and should not be held responsible under both law and at equity."

Countercl. ¶ 49.

Id. ¶ 50.

Id. ¶ 51.

In essence, Lockheed argues that BAE committed fraud by not disclosing its intent not to perform its obligations (to defend as if all damages were for its account) under (Lockheed's interpretation of) the Transaction Agreement. This Court has expressly rejected that type of argument. "One cannot `bootstrap' a claim of breach of contract into a claim of fraud merely by alleging that a contracting party never intended to perform its obligations." Couching an alleged failure to comply with the Transaction Agreement as a failure to disclose an intention to take certain actions arguably inconsistent with that agreement is exactly the type of bootstrapping this Court will not entertain. Thus, a fraud claim based on this alleged nondisclosure, in light of the express terms of the Transaction Agreement, does not survive a motion to dismiss.

IOTEX Communications, Inc. v. Defries, 1998 WL 914265, at *4 (Del.Ch. Dec. 21, 1998) (applying New York law); see Tristate Courier Carriage, Inc. v. Berryman, 2004 WL 835886, at *11 (Del.Ch. Apr. 15, 2004).

Lockheed's second argument is based on alleged statements (and omissions) made by BAE outside of the promises contained in the Transaction Agreement itself. Specifically, Lockheed alleges:

• At various times prior to the entry of the CCT Judgment, representatives of Lockheed Martin, and in particular Maryanne Lavan, communicated with BAE regarding the status of the CCT trial. On these occasions, representatives of BAE confirmed that the trial was going well and that there was a high likelihood of success.
• Near the end of trial, Ms. Lavan was informed by Kevin Perkins, counsel for BAE, that due to the strength of BAE's case no settlement offer would be made. During this conversation, BAE did not disclose that it intended to object to CCT's proposed jury special verdict form because it did not provide space for the assessment of damages against each of the defendants individually. Nor did it disclose its intent to propose a different jury special verdict form which artificially separated out Lockheed Martin Sanders and Lockheed Martin Federal Systems. Instead, BAE concealed this fact from Lockheed Martin.

Countercl. ¶ 47.

Id. ¶ 48.

Lockheed does not make an allegation that BAE actively concealed information. Nor does it argue that BAE made any statements that are by themselves false. Rather, it bases its argument on silence in the face of a duty to speak.

While Lockheed, in paragraph 48 of its Counterclaim, alleges that "BAE concealed this fact from Lockheed Martin," Lockheed does not allege active concealment. To state a claim of fraud by active concealment, the plaintiff must allege an affirmative action. Supra note 45.

A statement that the trial is going well and that there is a high likelihood of success is a statement of opinion and prediction that, by itself, cannot constitute equitable fraud. Lockheed does not allege that the BAE representatives falsely stated their opinions.

In Matthews Office Designs, Inc. v. Taub Investments, the Supreme Court cited the Restatement (Second) of Torts for a list of circumstances that would create a duty to speak. Under the Restatement, such a duty to speak arises when necessary to make a previous statement not misleading or when, because of a "fiduciary or other similar relation of trust and confidence," such information should be disclosed.

1994 WL 267479, at *2 (Del. 1994).

RESTATEMENT (SECOND) OF TORTS § 551(2). The Restatement also requires disclosure when a previous representation was made and information subsequently acquired would make that statement untrue or misleading; when a false statement is made that the speaker did not anticipate would be relied upon, but subsequently learns another party is relying on it, and when "facts basic to [a] transaction, if [the speaker] knows that the other is about to enter into it under a mistake as to them, and that the other, because of the relationship between them, the customs of the trade or other objective circumstances, would reasonably expect a disclosure of those facts." Id. § 551(2)(e). None of these issues is present in the current case.

Lockheed alleges that BAE stated that the case was going well, that there was a high likelihood of success, and that "due to the strength of BAE's case no settlement offer would be made." The first two statements are statements of opinion and prediction. The third statement is a factual statement that due to BAE's opinions and predictions on the outcome of the CCT Litigation, BAE would not make a settlement offer. In effect, Lockheed argues that it was reasonable for it to infer from BAE's statement that BAE would not take any action to protect its own interests in the event that the jury returned an unfavorable verdict. This is an unreasonable inference to take from that statement. BAE's alleged statement went to its perception of the likelihood of success in an adversarial proceeding. Nothing in that statement supports any inference about what BAE would do if its prediction turned out to be incorrect. BAE said it would not make a settlement offer and it did not. That statement was neither false nor misleading, and Lockheed's equitable fraud counterclaim must be dismissed.

This reading, the only reading of Counterclaim Count III that could attempt to state a claim for equitable fraud, overlaps Lockheed's breach of contract counterclaim. This is noted to highlight that the conduct about which Lockheed complains will continue to be a focus of this litigation. This memorandum opinion merely determines under which legal theory this set of facts could plausibly state a claim.

The Restatement also requires disclosure of matters that the plaintiff is "entitled to know because of a fiduciary or other similar relation of trust and confidence" in order to avoid a claim for fraud. How this purported "duty to disclose" fits within our already complex jurisprudence on fraud, equitable fraud, and in some contexts, a corporate director's duty to disclose is unclear. Moreover, it is unclear what constitutes a "special relationship of trust and confidence."
Clearly, the Transaction Agreement, itself a product of negotiation between two extremely sophisticated parties, did not create a fiduciary relationship. Such a relationship would require "confidence reposed by one side and domination and influence exercised by the other." Gross v. Univ. of Chi., 302 N.E.2d 444, 453-54 (Ill.App.Ct. 1973). Lehner v. Crane Co., 448 F. Supp. 1127, 1131 (E.D. Pa. 1978), one of the few cases to deal expressly with this provision of the Restatement as it pertains to fraud outside of the securities context, implies that a "special relationship of trust and confidence" would also have to meet the standard for a fiduciary relationship spelled out in Gross. Regardless, even if such a relationship existed here, it would not require BAE to disclose each and every decision of litigation strategy. To hold otherwise would lead to perverse results. Essentially, the opposite result would allow the elements of the tort of equitable fraud to be used to write additional terms into a contract between two highly sophisticated business entities.
Moreover, the Restatement only requires reasonable care to disclose information. "Under the rule stated in this Subsection the person under a duty of disclosure is not subject to liability merely because he has failed to bring the required information home to the person entitled to it. His duty is to exercise reasonable care to do so. If reasonable care is exercised, the fact that the information does not reach the person entitled to it does not subject him to liability." RESTATEMENT (SECOND) OF TORTS § 551 cmt. (d). I note this in light of the fact that the alleged "nondisclosure" occurred during a public trial.

IV. CONCLUSION

For the reasons set forth above, the Plaintiffs' motion to dismiss Counts III, IV, and V of Lockheed's Counterclaim is granted, but it is denied in all other respects. The motions for partial judgment on the pleadings are denied.

IT IS SO ORDERED.


Summaries of

BAE SYSTEMS N. AMERICA INC. v. LOCKHEED MARTIN CORP.

Court of Chancery of Delaware, New Castle County
Aug 3, 2004
C.A. No. 20456 (Del. Ch. Aug. 3, 2004)

finding no duty to disclose to correct past predictive statements regarding the likelihood of success in litigation.

Summary of this case from Osram Sylvania Inc. v. Townsend Ventures, LLC

finding that the counterclaim plaintiffs fiduciary duty claims could not be brought independently of its breach of contract claims as they were "rooted in" the contract

Summary of this case from PT China LLC v. PT Korea LLC

denying a motion for judgment on the pleadings because "[t]he parties have set forth `more than one plausible construction of the meaning of" a key term in the contract

Summary of this case from United Rentals, Inc. v. RAM Hldgs., Inc.

asserting that for a pleading of mistake to survive, the party must "allege with particularity some form of specific prior agreement"

Summary of this case from AECOM v. SCCI Nat'l Holdings, Inc.

summarizing that "a claim for reformation based on mistake must be based on something more than a conclusory allegation of a mutual understanding and agreement on the issue"

Summary of this case from JJS, Ltd. v. Steelpoint CP Holdings

dismissing claim for fraud because plaintiff's claim was based on the defendant's failure to disclose its intent not to perform its obligations under the parties contract

Summary of this case from Khushaim v. Tullow Inc.

stating that representing false statements as true can give rise to a common law fraud claim

Summary of this case from Alltrista Plastics, LLC v. Rockline Indus., Inc.

discussing Amkor holding "Illinois law does not differ materially from those guiding Delaware courts."

Summary of this case from Lillis v. AT&T Corp.
Case details for

BAE SYSTEMS N. AMERICA INC. v. LOCKHEED MARTIN CORP.

Case Details

Full title:BAE SYSTEMS NORTH AMERICA INC. and BAE SYSTEMS INFORMATION AND ELECTRONIC…

Court:Court of Chancery of Delaware, New Castle County

Date published: Aug 3, 2004

Citations

C.A. No. 20456 (Del. Ch. Aug. 3, 2004)

Citing Cases

Narrowstep v. Onstream Media Corporation

Id. (internal citations and quotation marks omitted).See BAE Sys. N. Am. Inc. v. Lockheed Martin Corp., 2004…

Zutrau v. Jansing

See also Grunstein v. Silva, 2009 WL 4698541, at *6 (Del. Ch. Dec. 8, 2009); BAE Sys. N. Am. Inc. v. Lockheed…