The Massachusetts Port Authority (Massport), which operates Logan airport, will not let the appellant, a charter airline operator called The Interface Group, Inc. (Interface), use Logan’s Terminal C. Interface, believing that Massport’s refusal violates the federal antitrust laws, 15 U.S.C. §§ 1, 2 (1982), and several federal aviation statutes, 49 U.S.C.App. §§ 1349(a), 1513, 2210 (1982), sued Massport in federal district court. Interface also asked the court to assume pendent jurisdiction over two state claims that parallel its antitrust claims. Mass.Gen.L. ch. 93, §§ 4, 5; ch. 93A, § 2 (1985). The district court dismissed the entire complaint for failure to state a federal claim. Fed.R.Civ.P. 12(b)(6),
I.
Interface’s antitrust claims amount to an imaginative, but unsuccessful, effort to dress its facts in the wrong suit of legal clothes. The facts that it asserts, in essence, are the following: (1) Interface bought two L1011 aircraft from TWA to use for charter service during the winter; (2) it leased them back to TWA for TWA’s use during the peak summer season; (3) TWA promised Interface that during the winter Interface could use TWA ground services; (4) Massport allows TWA to service itself at Terminal C; (5) Massport permits two other private companies (called “fixed base operators” or “FBOs”) to sell ground services at Terminal E; and (6) Massport requires all nontenant charter carriers, such as Interface, to use Terminal E; they cannot use Terminal C.
Interface asserts that Massport’s policy, at least as applied in this instance, is unreasonable. Interface’s basic legal problem is that it is not seeking judicial review of an unreasonable regulation under the state Administrative Procedure Act (as counsel at oral argument agreed it might have done).
See
Mass.Gen.L. ch. 30A, § 7 (1985). Rather, it has brought an antitrust claim. And “unreasonableness” in antitrust law has a rather special meaning. It means that the anticompetitive consequences of a particular action or arrangement outweigh its legitimate business purposes.
See
7 P. Areeda,
Antitrust Law
111500, at 362-63 (1986). “Anticompetitive” also has a special meaning: it refers not to actions that merely injure individual competitors, but rather to actions that harm the competitive process,
Brown Shoe Co. v. United States,
Interface says that Massport’s requirement that it use Terminal E and the ground services provided there amounts to an unreasonable “exclusive dealing” arrangement between Massport and the FBOs, unlawful under Sherman Act § 1. But “[n]ot all exclusive dealing contracts even by a monopolist are illegal.”
Smith v. Northern Michigan Hospitals, Inc.,
Exclusive dealing arrangements may
sometimes
be found unreasonable under the antitrust laws because they may place enough outlets, or sources of supply, in the hands of a single firm (or small group of firms) to make it difficult for new, potentially competing firms to penetrate the market.
See
3 P. Areeda & D. Turner,
Antitrust Law
11732, at 253 (1978). To put the matter more technically, the arrangements may “foreclose” outlets or supplies to potential entrants, thereby raising entry barriers.
Cf. Tampa Elec. Co. v. Nashville Coal Co.,
The complaint before us, however, seems inadequate to raise an antitrust controversy. Certainly the kind of antitrust harm typically present in an unlawful exclusive dealing arrangement is missing here. Interface does not claim that the arrangement, by foreclosing entry into the FBO market, makes it easier for Massport to abuse its market power or more difficult for new firms to build competing airports. Nor does it allege any more exotic theory of antitrust harm. Even if we were to concoct on Interface’s behalf an analogy between FBOs and dealers to which an important manufacturer assigns exclusive territories, we would not cure the deficiency, because a manufacturer is ordinarily free to decide just how many dealers it will place in any given geographic area.
See Packard Motor Car Co. v. Webster Motor Car Co.,
When there is no plausible connection between exclusive dealing and antitrust harm, courts have not hesitated to hold that dealing lawful. Thus, courts have explicitly permitted even private firms with effective monopoly control of a transportation facility to maintain exclusive dealing arrangements with even a single supplier.
See, e.g., Donovan v. Pennsylvania Co.,
The fact that Massport is a public rather than a private body makes any risk to competition yet more remote. Unlike a
private
owner, Massport does not directly profit from its ownership of Logan.
See Opinion of the Justices,
Interface’s alternative antitrust theory suffers from similar problems. Interface says that Massport’s failure to make Terminal C ground facilities available to it violates Sherman Act § 2’s prohibition of monopolization. It argues that because Massport has a monopoly of the airport business, it must make “essential facilities” available to anyone who wishes to use them. This view of the essential facilities doctrine, however, considerably overstates its scope. The doctrine aims to prevent a firm with monopoly power from extending that power “from one stage of production to another, and from one market into another.”
MCI Communications Corp. v. American Tel. & Tel. Co.,
Interface fails to state a claim under Sherman Act § 1 or § 2 for an alternative reason: in our view, Massport is immune from antitrust liability under the state action doctrine of
Parker v. Brown,
We realize that since our decision in
Wiggins,
the Supreme Court has tightened the immunity rules for certain kinds of state instrumentalities, namely municipalities,
see Lafayette v. Louisiana Power & Light Co.,
Moreover, Massport satisfies
Lafayette’s
rule that a municipality is immune only when it acts pursuant to a “clearly articulated and affirmatively expressed” state policy.
Lafayette,
Of course, one might argue to the contrary that technically Massachusetts did not delegate to Massport the authority to make unreasonable rules, and Interface has alleged that Massport’s rules are “unreasonable” (in the ordinary, not the special antitrust, sense of the word). But this argument does not persuade us that Mass-port loses its antitrust immunity. If Mass-port’s lawful activity in this area falls outside the Sherman Act, the fact that the activity may be (not obviously) unlawful under state law (for reasons having nothing to do with antitrust) cannot make a legal difference for the purposes of antitrust immunity. To hold otherwise would impose the antitrust laws’ treble damage liability upon agencies that may have done no more than to misjudge difficult questions of state law or make administrative errors having nothing to do with antitrust policy. It would force antitrust courts to review state administrative law disputes.
We should not lightly assume that Lafayette’s authorization requirement dictates transformation of state administrative review into a federal antitrust job. Yet that would be the consequence of making antitrust liability depend on an undiscriminating and mechanical demand for “authority” in the full administrative law sense.
P. Areeda & H. Hovenkamp,
supra,
H 212.-3, at 104. A Congress that intended to permit states to authorize potentially anti-competitive activity would not have left outside that area of autonomy conduct involving “ ‘ordinary’ errors or abuses in the administration of powers conferred by the state.”
Llewellyn v. Crothers,
In sum, Wiggins remains good law. And even were Massport not immune, the complaint would fail to state an antitrust claim. The district court therefore properly dismissed Interface’s antitrust claims.
II.
Interface also claims that Massport violated three federal aviation statutes, 49 U.S.C.App. §§ 1349(a), 1513, and 2210. The district court dismissed these claims on the ground that the government alone has the right to enforce these statutes; the statutes do not provide private parties such as Interface with a “private right of action.” In two instances we agree with the district court; in one instance (49 U.S.C. App. § 1513) we do not.
A.
In
Cort v. Ash,
First, is the plaintiff “one of the class for whose especial benefit the statute was enacted” ... — that is, does the statute create a federal right in favor of the plaintiff? Second, is there any indication of legislative intent, explicit or implicit, either to create such a remedy or to deny one? ... Third, is it consistent with the underlying purposes of the legislative scheme to imply such a remedy for the plaintiff? ... And finally, is the cause of action one traditionally relegated to state law, in an area basically the concern of the States, so that it would be inappropriate to infer a cause of action based solely on federal law?
Id.
at 78,
No federal funds ... shall be expended ... for the acquisition, establishment, construction, alteration, repair, maintenance, or operation of any landing area, or for the acquisition, establishment, construction, maintenance, or operation of air navigation facilities thereon, except upon written recommendation and certification by the Secretary of Transportation that such landing area or facility is reasonably necessary for use in air commerce or in the interests of national defense.
... There shall be no exclusive right for the use of any landing area or air navigation facility upon which Federal funds have been expended.
The statutory language weighs slightly against appellants with respect to Cort’s “especial benefit” test. We concede that the language about “exclusive rights,” taken alone, supports the view that the statute (or at least the last sentence) aims at the “especial benefit” of those who operate planes as contrasted with those who fly as passengers in them. But the statutory provision taken as a whole suggests that Congress sought to benefit the public at large, not carriers in particular.
See Montauk-Caribbean Airways, Inc. v. Hope,
The evidence weighs more strongly against appellant with respect to Cort’s second, “legislative intent,” inquiry. There is nothing in the legislative history that suggests any intent to create a private right of action. At the same time, the statute as a whole provides an administrative and judicial enforcement scheme that suggests at least some Congressional wish for an element of administrative expertise at the enforcement stage, an expertise that *15 tends to be lost when private parties can enforce the statute directly in federal court. This latter view is reinforced by the reference to the Secretary of Transportation in the first quoted sentence and by the fact that Congress created an express private right of right of action elsewhere in related provisions of the statute, but not here. See 49 U.S.C.App. § 1487 (1982) (creating a private right of action for violations of § 1371(a) of the same Act). Thus, if anything, the statute manifests legislative intent to deny, not to grant, a private right of action.
Although the third and fourth
Cort
factors better serve Interface’s claim, these are minor factors that, here, cannot make a legal difference. Indeed, the Supreme court has said that a private right of action should not be implied on the basis of these factors alone.
See Transamerica Mortgage Advisors, Inc. v. Lewis,
B.
Interface claims that Massport has violated 49 U.S.C.App. § 2210. That provision reads as follows:
As a condition precedent to approval of an airport development project ... the Secretary shall receive assurances ... that—
(1) ... (A) each air carrier using such airport ... shall be subject to such nondiscriminatory and substantially comparabie rates, fees, rentals, and other charges and such nondiscriminatory and substantially comparable rules, regulations, and conditions as are applicable to all such air carriers which make similar use of such airport facilities, subject to reasonable classifications such as tenants or nontenants ..., and (C) each air carrier using such airport shall have the right to service itself or to use any fixed-base operator that is authorized to serve any such air carrier at such airport____
We see two relevant differences between this statute and 49 U.S.C.App. § 1349(a). First, the statute’s language suggests more strongly that it was “enacted” for the “especial benefit” of air carriers such as Interface. Second (and conversely), the statute’s language also suggests more strongly that Congress had in mind an alternative enforcement scheme inconsistent with a private right of action. That language does not impose on airport developers a duty that arguably could run in favor of private plaintiffs. Rather, it imposes only the duty to give “assurances” to “the Secretary.” The view that Congress intended to enact an exclusively administrative enforcement scheme is reinforced by legislative history that refers only to the right of air carriers “to consult” with the Secretary.
See
H.R.Rep. No. 594, 94th Cong., 2d Sess.,
reprinted in
1976 U.S. Code Cong. & Admin.News 1600, 1614; H.R.Conf.Rep. No. 1292, 94th Cong., 2d Sess.,
reprinted in
1976 U.S.Code Cong.
&
Admin.News 1638, 1648. For this reason, we believe that Congress did not intend to create a private right of action under § 2210.
See Arrow Airways, Inc. v. Dade County,
C.
Interface also says that Massport assesses, on flights departing through terminal E, a charge that amounts to nearly $10 per passenger flown. Interface claims that this charge violates the Anti-Head-Tax *16 Act, 49 U.S.C.App. § 1513. The statute says
(a) No state (or political subdivision thereof ...) shall levy or collect a tax, fee, head charge, or other charge, directly or indirectly, on persons traveling in air commerce or on the carriage of persons traveling in air commerce or on the sale of air transportation or on the gross receipts derived therefrom____
(b) ... nothing in this section shall prohibit a State (or political subdivision thereof ...) owning or operating an airport from levying or collecting reasonable rental charges, landing fees, and other service charges from aircraft operators for the use of airport facilities.
In this case, we find that the statute impliedly confers on Interface a private right of action.
The primary beneficiaries of this statute are obviously air travelers, not air carriers. Still, by prohibiting the levying of taxes on the
carriage of persons,
the statute at least in some instances gives air carriers a “benefit” that is “especial,” at least when compared with the benefit conferred on the general public. The ban on head taxes means that air carriers will neither have to face diminished demand for costlier services nor have to absorb all or part of the charge by reducing ticket prices.
Cf. Indianapolis Airport Authority v. American Airlines, Inc.,
Moreover, the second, third, and fourth
Cort
factors also support implication of a private right of action. With respect to the “legislative intent” to permit private enforcement actions, the absence of the word “Secretary” from the statute suggests that Congress did not consider it especially important to employ administrative expertise in the statute’s enforcement. This suggestion is reinforced by the fact that Congress did not provide the extensive administrative and judicial enforcement scheme for § 1513 that it created for §§ 1349(a) and 2210. Moreover, the legislative history of § 1513 suggests that Congress viewed air carriers as a kind of surrogate for air passengers. Congress realized, for example, that in banning taxes on the carriage of persons, and thereby directly benefiting air carriers, it simultaneously protected air travelers from paying a tax “passed through” to their tickets.
See
S.Rep. No. 12, 93d Cong., 1st Sess.,
reprinted in
1973 U.S. Code Cong. & Admin.News 1434, 1451. Because the amount of tax imposed on each passenger is ordinarily small, individual travelers may prove unwilling to take the time and trouble to determine whether the tax is unlawful. A carrier, on the other hand, will often have a significant financial incentive, and the expertise needed, to enforce the statute. Thus, private enforcement would further the purposes of § 1513. Finally, the area is one especially suited for federal action, in that the statute itself seeks to prohibit certain activity by the States. Because all four
Cort
factors argue to some degree in favor of the existence of a private right of action, we conclude that in this instance the Congress intended to grant a private right of action.
See Indianapolis Airport Authority,
III.
On appeal, Interface also asserted several new claims. It alleged that Massport’s actions violate the Supremacy and Commerce Clauses of the United States Constitution. Because these constitutional claims were not raised below, we will not consider them here.
See United States v. State Tax Commission,
*17 IV.
In sum, with the exception of the claim under 49 U.S.C. § 1513, we affirm the district court’s dismissal of Interface’s claims. The judgment of the district court with respect to § 1513 is vacated, and the case is remanded for proceedings not inconsistent with this opinion.
So ordered.
