Florida Public Telecommunications Association, Inc. v. Federal Communications Commission and United States of America, at & T Corporation, Intervenors

54 F.3d 857, 312 U.S. App. D.C. 24, 1995 U.S. App. LEXIS 12199
CourtCourt of Appeals for the D.C. Circuit
DecidedMay 23, 1995
Docket91-1486, 92-1356
StatusPublished
Cited by17 cases

This text of 54 F.3d 857 (Florida Public Telecommunications Association, Inc. v. Federal Communications Commission and United States of America, at & T Corporation, Intervenors) is published on Counsel Stack Legal Research, covering Court of Appeals for the D.C. Circuit primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Florida Public Telecommunications Association, Inc. v. Federal Communications Commission and United States of America, at & T Corporation, Intervenors, 54 F.3d 857, 312 U.S. App. D.C. 24, 1995 U.S. App. LEXIS 12199 (D.C. Cir. 1995).

Opinion

Opinion for the Court filed by Circuit Judge STEPHEN F. WILLIAMS.

STEPHEN F. WILLIAMS, Circuit Judge:

This case turns on the meaning of one phrase in a subsection of the Telephone Operator Consumer Services Improvement Act of 1990 (“TOCSIA”). Section 226(e)(2) directs the Federal Communications Commis *859 sion to

consider the need to prescribe compensation (other than advance payment by consumers) for owners of competitive public pay telephones for calls routed to providers of operator services that are other than the presubscribed provider of operator services for such telephones.

47 U.S.C. § 226(e)(2) (Supp.1993) (emphasis added). In the two orders under review here, the FCC ruled that this provision gives it authority to prescribe compensation only for access-code calls (including ones using the number 800), that is, phone calls directed initially to a carrier’s “platform” (by dialing, for example, 10-ATT or 1-800-COLLECT), and then redirected under the caller’s instructions to the party the caller wishes to reach. By contrast, the FCC ruled that subscriber-800 calls, that is, calls to an 800 number assigned to a particular subscriber (for example, 1-800-FLOWERS or 1-800-USA-RAIL), go “through” a carrier preselected by the subscriber but not “to” a carrier, and thus do not fall within § 226(e)(2). See Policies and Rules Concerning Operator Service Access and Pay Telephone Compensation, 6 F.C.C.R. 4736, 4746 ¶36 (1991) (report, order and further notice of proposed rulemaking) (“First Order”); Policies and Rules Concerning Operator Service Access and Pay Telephone Compensation, 7 F.C.C.R. 4355, 4367 ¶50 (1992) (order on reconsideration) (“Second .Order*’). Several pay telephone owners, here represented by Florida Public Telecommunications Association, Inc. (formerly Florida Pay Telephone Association) and American Public Communications Council, Inc. contest this exclusion, arguing that the FCC’s interpretation is contrary to the statute’s plain language. We agree with the petitioners and therefore grant the petition, remanding to the Commission to “consider the need to prescribe compensation” for subscriber-800 calls.

Because the FCC is charged with administering TOCSIA, our review is governed by Chevron, Inc. v. NRDC, 467 U.S. 837, 104 S.Ct. 2778, 81 L.Ed.2d 694 (1984), under which we make the familiar inquiry into “whether Congress has directly spoken to the precise question at issue”, id. at 842, 104 S.Ct. at 2781, and, if not, into whether the agency’s construction is “reasonable”, id. at 840, 844-45, 866, 104 S.Ct. at 2780, 2782-83, 2793.

Section 226(e)(2) directs the Commission to consider requiring compensation “for calls routed to providers of operator services that are other than the presubscribed provider of operator services”. Petitioners tell us, without contradiction by the Commission, that subscriber-800 calls, like access-code calls, are most often if not always .carried by a “provider of operator services”. Thus, if we read the words “routed to” as essentially the equivalent of “carried by”, such subscriber-800 calls fall undeniably — plainly and unambiguously — within the statutory language.

The Commission, however, finds deeper meaning in the words “routed to”. According to it, one may properly describe subscriber-800 calls as carried “by” or even routed “through” a provider of operator services; one cannot, however, say that such calls are routed “to” a provider of operator services because they do not — as access-code calls do — temporarily stop at the provider’s platform for the caller to enter numbers indicating the final destination of the call, but rather are routed seamlessly through the provider to the subscriber. From the caller’s perspective, the FCC claims, only access-code calls make a stop at the provider of operator services and thus only those calls are routed “to” a provider.

We find the FCC’s parsing of the word “to” completely unconvincing. Whether we adopt the caller’s or a technical point of view, we see no reasoned way to distinguish between the routing of access-code calls and of subscriber-800 calls. Technically, both access-code calls and subscriber-800 calls are routed “to” a provider, in the sense that both types of calls at some point in their journey switch from a local carrier “to” an interex-change operator services provider (“OSP”), which in both cases redirects the call “to” its final destination, the called party. Commission orders repeatedly use the phrase “routed to” to describe the portion of the path of a subscriber-800 call between the local exchange carrier and the interexehange carrier, despite the fact that the caller does not interact with the interexchange carrier at the *860 time of the switch. See, e.g., Data Base Access Tariffs and the 800 Service Mgmt. Sys. Tariff, 8 F.C.C.R. 5132, 5132 (1993) (“SCPs are data bases which contain routing instructions for 800 numbers, including identification of the IXC [inter-exchange carrier] to whom the call should be routed.... Upon receipt of the routing instructions, the SSP routes the call to the appropriate IXC.”) (emphasis added); Bell Atlantic Tel. Cos., 7 F.C.C.R. 2955, 2955 (1992) (“[L]ocal exchange carriers (LECs) identify the inter exchange earner (IXC) to which 800 calls should be routed by reading the three digits that immediately follow the 800 prefix of the dialed number-”) (emphasis added); Provision of Access for 800 Service, 6 F.C.C.R. 5421, 5421 (1991) (“LECs must handle originating 800 access differently from originating access for ordinary interexchange calls because the LECs must route 800 calls to the carrier selected by the 800 service subscriber (the called party), rather than the carrier presubscribed to the originating line or chosen by the calling party.”) (emphasis added). The fact that the caller is aware of the route of access-code calls and unaware of the route of subscriber-800 calls does not itself change the call’s technical route.

Further, from the caller’s perspective, neither type of call is a call “to” the provider of operator services. In both situations — as the FCC itself has stated in a different context— the caller perceives (and intends) the call as a single call, the ultimate destination of which is not the provider but a third party. See Teleconnect Co. v. Bell Tel. Co., Nos. E-88-83 to E-88-103, 1995 WL 59773 ¶ 14 & n. 4 (8 F.C.C. Feb. 14, 1995) (noting that to the caller 800 access-code calls “appear to be a single call”, “regardless of whether [the] caller must dial a second number at some point before the call is completed”.); id. at ¶ 14 (“[F]rom the caller’s point of view, any intermediate switching during the call is ... ‘transparent’. [The caller] intends to make a single call terminating not at the ... intermediate switch, ... but at the telephone line of the called party.”).

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

Related

Cite This Page — Counsel Stack

Bluebook (online)
54 F.3d 857, 312 U.S. App. D.C. 24, 1995 U.S. App. LEXIS 12199, Counsel Stack Legal Research, https://law.counselstack.com/opinion/florida-public-telecommunications-association-inc-v-federal-cadc-1995.