William Aramony v. United Way Of AmericaWilliam Aramony v. United Way Of America
Reversed.[Copyrighted Material Omitted]
Dennis Houdek, Curan Callahan Gale & Houdek, LLP, New York, NY, for Plaintiff-Appellee.
Paul J. Ondrasik, Jr. (Sara E. Hauptfuehrer, on the brief), Steptoe & Johnson LLP, Washington, D.C., for Defendant-Appellant.
LEVAL, Circuit Judge:
William Aramony, the former Chief Executive Officer of United Way of America, brought this action against his former employer, after his dismissal by reason of fraud, to recover pension benefits allegedly due him. After a bench trial, the United States District Court for the Southern District of New York (Shira Scheindlin, J.) ruled in favor of Aramony, in part, and in favor of United Way, in part. See Aramony v. United Way of America, 28 F. Supp. 2d 147 (S.D.N.Y. 1998) (“Aramony I”). The parties appealed. We affirmed the judgment except insofar as it held that United Way was estopped from denying that Aramony was entitled to certain pension benefits under a Replacement Benefit Plan to replace benefits lost because of the 1986 enactment of
I. BACKGROUND
The background of this case is described in detail in the decisions of the district court, and in our September 1999 decision in the appeal from the district court‘s initial judgment. We restate it here only insofar as it is relevant to the issue presented in this appeal.
A. Aramony‘s Employment with United Way and United Way‘s Pension Plans
Aramony served from 1970 to 1992 as president and CEO of United Way of America, one of the nation‘s leading charitable organizations. In 1992, United Way terminated Aramony‘s employment amidst allegations that he had engaged in fraud and financial improprieties with respect to United Way funds. Aramony was convicted in 1995 in the United States District Court for the Eastern District of Virginia of numerous felony counts of fraud, and sentenced to seven years in prison.
During Aramony‘s tenure as President and CEO of United Way, United Way provided its employees with a qualified defined benefit plan under which pension benefits were calculated as a function of an employee‘s average salary over a five-year period. Under a 1982 amendment to the Internal Revenue Code,
The general practice at United Way was for the Executive Committee to adopt the concept of a pension plan, but not to involve itself in the details of the plan. Details were worked out by Stephen Paulachak, a Senior Vice President of United Way, and Mutual of America Life Insurance Company (“Mutual“). Mutual was the entity with which United Way had signed a group annuity contract. Mutual also drafted United Way‘s pension plan documents and administered United Way‘s pension plans.
At the February 1984 meeting, Paulachak described the purposes of the RBP as: (1) to restore benefits lost because of the restrictions imposed by
As ultimately executed, the RBP is made up of nine articles, two of which are relevant here. Article I sets out the “Purpose of the Plan.” It states in relevant part that
[t]his plan is being installed to provide a mechanism for securing the pension benefit promises made to [United Way‘s] management and highly compensated key employees who may receive relatively smaller retirement benefits under the existing pension arrangement than rank and file employees will receive as a result of limitations imposed by the Internal Revenue Code and rulings thereunder on the amount of pensions payable to the highly compensated.
Article V sets out the operative terms of the RBP. The relevant aspects of Article V are Sections 5.01 through 5.05. Sections 5.02, 5.03, and 5.04, which are set out in full in the margin,1 each specify a particular formula for calculating contributions to the RBP. Section 5.02 provides a formula for calculating contributions to the RBP to replace benefits lost because of
The benefit to be provided under this Plan on behalf of each eligible Participant shall be the sum of (a) plus (b) below:
(a) the yearly contributions required pursuant to Section 5.02, 5.03, or 5.04, whichever is applicable, and
(b) any additional contributions or benefit amount that the Employer has agreed to pay to the Participant pursuant to either a contractual commitment or a resolution of the Board of Trustees of the Employer.
Approximately a year later, in 1986, as part of the Tax Reform Act of 1986, Congress enacted
In October 1988 and January 1989, Mutual sent Aramony estimates of his United Way pension benefits under both the qualified defined benefit plan and the RBP. Notwithstanding that the RBP does not mention the replacement of benefits lost because of
B. Prior Proceedings & Proceedings Below
As a consequence of Aramony‘s misconduct, United Way determined to deny Aramony pension benefits under both the RBP and a Supplemental Benefits Agreement (“SBA“) into which United Way and Aramony had entered in 1984. Aramony brought this action pursuant to
On the issue whether the RBP included replacement benefits for pension benefit losses incurred because of
Both parties appealed. We affirmed the district court‘s judgment with respect to all questions except the issue of the
As part of its estoppel analysis, the district court decided, however, that the RBP was ambiguous on this point. We remand, therefore, so that the district court may consider whether United Way is contractually bound by the RBP itself to provide the benefit to Aramony.
On remand, the district court again ruled in Aramony‘s favor. The court explained that there is a “‘conflict between the plan‘s stated purpose‘” in Article I of the RBP, on the one hand, “‘and the effect of § 401(a)(17),‘” on the other. Aramony III, 86 F. Supp. 2d at 203 (quoting Aramony I, 28 F. Supp. 2d at 170). In particular, the court reasoned that “it is not clear from the language of the RBP that the general statement of purpose in Article I [of the RBP] does not include the limitation on pension benefits contained in § 401(a)(17),” and that such “ambiguity is reinforced by the fact that § 401(a)(17) takes away some of the § 415 make-up benefit explicitly mentioned in § 5.02 [of the RBP].” Id. at 204. Moreover, the district court explained that the “‘absence of any mention of 401(a)(17) from the [RBP]‘” is not determinative of the RBP‘s scope because the RBP was executed before the enactment of
II. DISCUSSION
On appeal, United Way argues (1) that the district court erred in interpreting the RBP as ambiguous, and (2) that the RBP can be read reasonably only as not providing
A. The Law of the Case Doctrine Does Not Bar Our Consideration of Whether the RBP Is Ambiguous
As a threshold matter, we reject Aramony‘s contention that the law of the case bars us from ruling that the RBP is not ambiguous. The doctrine of the law of the case “‘posits that if a court decides a rule of law, that decision should continue to govern in subsequent stages of the same case.‘” In re Crysen/Montenay Energy Co., 226 F.3d 160, 165 n.5 (2d Cir. 2000), cert. denied, 121 S. Ct. 1356 (2001) (quoting Sagendorf-Teal v. County of Rensselaer, 100 F.3d 270, 277 (2d Cir. 1996)). Courts apply the law of the case doctrine when their prior decisions in an ongoing case either expressly resolved an issue or necessarily resolved it by implication. See 18 Charles Alan Wright & Arthur R. Miller, Federal Practice and Procedure § 4478, at 789 (1981). “Application of the law of the case doctrine is discretionary and does not limit a court‘s power to reconsider its own decisions prior to final judgment.” In re Crysen/Montenay, 226 F.3d at 165 n.5 (quoting Sagendorf-Teal, 100 F.3d at 277) (internal quotation marks omitted).
Aramony argues that in our decision in Aramony II, 191 F.3d at 150-53, we necessarily held that the RBP is ambiguous. First, he argues that we so held when we affirmed the district court‘s decision in Aramony I to resort to extrinsic evidence to resolve an ambiguity in the RBP unrelated to the question now at issue in this case.4 A contract that is ambiguous in one respect, however, need not be ambiguous in another, and nothing we said in Aramony II about an unrelated ambiguity in the RBP has any bearing on the question now before us.
Aramony argues that in these passages we both expressly and necessarily held the plan to be ambiguous as to whether it replaced benefits lost because of
As to the express text, we read the opinion of our predecessor panel differently. Repeatedly it stated that the district court had found the provisions ambiguous. Because such ambiguity as the district court found, together with the misleading benefit estimates, did not justify the district court‘s conclusion of promissory estoppel, we remanded for consideration of the rights as provided by the contract. Our discussion of ambiguity referred to the ambiguity as found by the district court - not to any conclusion of our own that the plan was ambiguous as a matter of law.
As to the argument that a finding of ambiguity was necessarily implicit in our remand, Aramony is correct that, having rejected the district court‘s estoppel analysis, we could have resolved the meaning of the contract ourselves without remand, had we found it unambiguous. We could have, but we were under no obligation to do so. Because the district court had initially relied on estoppel, it had never made a determination of contract rights. The fact that we remanded to the district court for an initial determination of the meaning of this complex contract in no way implies that we found it ambiguous as a matter of law. A court of appeals‘s understanding of a complex matter is immensely benefitted by the district court‘s prior consideration. No inference of a finding of ambiguity can be drawn from the fact of the remand.
In any event, as noted above, application of the doctrine of law of the case is discretionary and does not limit a court‘s power to reconsider its decisions. See In re Crysen/Montenay, 226 F.3d at 165 n.5. For these numerous reasons, we reject Aramony‘s contention that this court is bound to consider the RBP ambiguous.
B. The Terms of the RBP Are Unambiguous
Interpretation of the terms of an ERISA pension plan is governed by the “federal common law of rights and obligations under ERISA-regulated plans.” Firestone Tire & Rubber Co. v. Bruch, 489 U.S. 101, 110 (1989) (internal quotation marks omitted); see also Schonholz, 87 F.3d at 79 (“ERISA is a federal law regime for regulating employee benefits designed to eliminate the threat of conflicting state and local regulation of benefit plans.“); Kemmerer v. ICI Americas Inc., 70 F.3d 281, 287 (3d Cir. 1995). In applying these principles, we interpret and enforce “unambiguous language in an ERISA plan” according to its “plain meaning.” Aramony II, 191 F.3d at 149. “‘Language is ambiguous when it is capable of more than one meaning when viewed objectively by a reasonably intelligent person who has examined the context of the entire integrated agreement.‘” Id. (quoting O‘Neil v. Retirement Plan for Salaried Employees of RKO Gen., Inc., 37 F.3d 55, 59 (2d Cir. 1994)). In making a determination of ambiguity, “reference may not be had to matters external to the entire integrated agreement.” Id. We review determinations as to the ambiguity of an ERISA plan provision de novo. See id.
The district court believed ambiguity resulted from the general provision set forth in Article I under the caption “Purpose of the Plan.” As noted above, the purpose described is “to provide a mechanism for securing the pension benefit promises made to... highly compensated key employees who may receive relatively smaller retirement benefits under the existing pension arrangement than rank and file employees will receive as a result of limitations imposed by the Internal Revenue Code and rulings thereunder on the amount of pensions payable to the highly compensated.”
Of course, it is true that the words “receive... smaller... benefits... as a result of limitations imposed by the Internal Revenue Code,” if read in isolation, could refer to future limitations imposed by the Code, as well as to limitations already imposed by the Code. But when this vague provision is read in conjunction with the highly detailed provisions in Article V, specifying with precision how replacement benefits are to be calculated - in each case in relation to limitations already imposed - the finding of ambiguity becomes improbable and unreasonable. This was clearly a contract written in detailed and precise terms that intended to make its meanings unmistakably clear. Nothing in the contract supports the notion that the phrase “imposed by the Internal Revenue Code” intended to refer to continuing changes that might in the future be “imposed by the Internal Revenue Code.” To the contrary, all of the plan‘s details reinforce the understanding that the word “imposed” carries its most natural meaning: as a reference to limitations that have been “imposed” before the execution of the plan.
Thus, if the plan‘s instructions had spoken in terms as vague as the language of the Purpose of the Plan provision and instructed that the employer‘s contributions to the replacement benefit plan would be determined by subtracting contributions actually made to the qualified defined benefit plan from the contributions that would have been made but for “limitations imposed by the Internal Revenue Code,” we would agree that such a promise might be ambiguous as to whether it intended to encompass limitations to be imposed in the future. But because the plan specifies with such clarity which tax provisions are to be taken into account, we find it unreasonable to treat the imprecision of the general purpose clause as overriding the specificity of the detailed computation clauses. Contracts would offer very little protection to their signatories if ambiguities of the sort found in the purpose clause could take precedence over carefully spelled out terms.
Second, it is a fundamental rule of contract construction that “specific terms and exact terms are given greater weight than general language.” Restatement (Second) of Contracts § 203(c) (1981); see also Jamie Sec. Co. v. The Limited, Inc., 880 F.2d 1572, 1576-77 (2d Cir. 1989); Arthur Linton Corbin, Corbin on Contracts §§ 545-54, at 521 (1952) (“[W]ords of general description should generally yield to words that are more specific.“).5 Even where there is no “true conflict” between two provisions, “specific words will limit the meaning of general words if it appears from the whole agreement that the parties’ purpose was directed solely toward the matter to which the specific words or clause relate.” 11 Richard A. Lord, Williston on Contracts § 32:10, at 449 (4th ed. 1999); see also Kayfield Constr. Corp. v. United States, 278 F.2d 217, 219 (2d Cir. 1960) (interpreting a contract by its more specific terms rather than by “the general language of... other paragraphs“); Friedrich v. Local No. 780, 515 F.2d 225, 227-28 (5th Cir. 1975) (general language of one paragraph limited by specific language in subsequent paragraphs); G.T. Schjeldahl Co. v. Local Lodge 1680, 393 F.2d 502, 504 (1st Cir. 1968) (same). Thus, even if the general language of Article I, considered in isolation, is broad enough to manifest a generalized intent to replace benefit reductions caused by future limitations imposed by the Internal Revenue Code, Article I‘s broad language is limited by the specific operative language of Article V, which provides only for the replacement of benefit reductions caused by specific existing tax provisions.
The district court also reasoned that “the failure to offset the limitation contained in § 401(a)(17) would frustrate [the RBP‘s] purpose [of providing a full make-up benefit for § 415].” Aramony III, 86 F. Supp. 2d at 204; see also id. at 203 (“401(a)(17) deprives Aramony of the pension benefit promises made by [United Way].“); id. at 204 (“[T]he ambiguity is reinforced by the fact that § 401(a)(17) takes away some of the § 415 make-up benefit explicitly mentioned in § 5.02.“). It is certainly true that Aramony‘s aggregate pension benefits became smaller after Congress passed
CONCLUSION
The judgment in plaintiff‘s favor is vacated and the matter remanded for entry of judgment in favor of the defendants.
Notes
Section 5.02 (Excess over Section 415 Limit). The contribution to be made to this Plan, in each Plan Year, on behalf of each eligible Participant, shall be equal to the difference between:
(a) the contribution that would have been made on behalf of such Participant under the Pension Plan sponsored by the Employer without the limitation on the annual addition imposed by Section 415 of the Internal Revenue Code, and
(b) the amount that has actually been contributed on such Participant‘s behalf and allocated to his individual account under that Plan.
Section 5.03. (Deferred Compensation). The contribution to be made to this Plan, in each Plan Year, on behalf of each eligible Participant, shall be equal to the difference between:
(a) the contribution that would have been made on behalf of such Participant under the Pension Plan sponsored by the Employer, if such contribution had been based on compensation inclusive of amounts deferred pursuant to an agreement between the Employer and the Participant, and
(b) the amount that has actually been contributed on such Participant‘s behalf and allocated to his individual account under that Plan.
Section 5.04. (Section 415 plus deferred compensation). The contribution to be made to this Plan, in each Plan Year, on behalf of each eligible Participant, shall be equal to the difference between:
(a) the contribution that would have been made on behalf of such Participant under the Pension Plan sponsored by the Employer if the amount of such contribution:
(i) had been based on compensation inclusive of amounts deferred pursuant to an agreement between the Employer and the Participant, and
(ii) was not limited by the annual addition permitted to be made pursuant to Section 415 of the Internal Revenue Code, and
(b) the amount that has actually been contributed on such Participant‘s behalf and allocated to his individual account under that Plan.