Norfolk Southern Railway Co. v. Public Utility Commission
77 A.3d 619
Pa.2013Background
- Colebrook Road Bridge in Lancaster County carried a road over Amtrak-owned tracks; Norfolk Southern (Norfolk) operated freight on the line by written easement/operating agreement but did not own the track or facilities there.
- The PUC ordered removal of the deteriorated bridge; after the Township advanced initial costs, the PUC held a final cost-allocation proceeding under 66 Pa.C.S. § 2704(a).
- The PUC (and an ALJ) allocated 15% of disputed allocable costs to Norfolk, finding Norfolk benefited from and was affected by the bridge removal despite lacking ownership.
- Norfolk argued the PUC lacked authority to assess costs against a non-owner operator, relying on City of Chester which suggested ownership (not mere usage) determines who may be assessed.
- The Commonwealth Court reversed, adopting an ownership-only rule for transportation utilities and holding the PUC could not allocate costs to non-owner railroads; the Supreme Court granted review.
- The Pennsylvania Supreme Court considered statutory text, common-law background, and policy, and held a transportation utility need not own facilities to be a "concerned" party when it regularly operates at the crossing and can enforce an easement-based right-of-way.
Issues
| Issue | Plaintiff's Argument | Defendant's Argument | Held |
|---|---|---|---|
| Whether PUC may designate who is a "public utility ... concerned" under §2704(a) (threshold question) | Norfolk: "concerned" requires ownership of facilities at the crossing; usage alone insufficient | PUC/Intervenors: PUC may determine concerned parties by weighing factors; ownership not dispositive | The determination of who is a "concerned" party is a question of statutory construction (plenary review); PUC has some deference on scope but not unlimited discretion |
| Whether ownership is a prerequisite to assess costs against a transportation utility | Norfolk: statutory text and precedents require ownership/facilities at the crossing | PUC/Intervenors: ownership is a strong factor but not required; regular operation and benefit justify inclusion | Court rejected categorical ownership litmus; non-owner railroad can be a concerned party if it regularly operates at the crossing and has an enforceable easement/right-of-way |
| Proper scope of PUC discretion in allocating cost proportions under §2704(a) | Norfolk: PUC discretion applies only to proportions after concerned parties are identified | PUC: identification of concerned parties and allocation are both within its discretion | Court: PUC discretion applies to determining proportions; identification of concerned parties is statutory and subject to plenary review, but PUC’s reasonable interpretations get deference |
| Reliance on common-law history (railroad liability) to limit PUC authority | Norfolk: common law and cases (e.g., Pittsburgh Railways, Lehigh Valley) support ownership focus | PUC: common-law portrait relied on by Norfolk/Commw. Ct. is truncated and not controlling; §2704(a) meant to address all parties with substantial interests | Court: common-law history was incomplete and not a basis to impose a categorical ownership rule; statutory purpose favors including parties with substantial operational interests |
Key Cases Cited
- City of Chester v. PUC, 798 A.2d 288 (Pa. Cmwlth. 2002) (held usage alone insufficient; emphasized ownership in prior context)
- Nat'l R.R. Passenger Corp. v. PUC, 848 F.2d 436 (3d Cir. 1988) (federal precedents limit state assessments against Amtrak)
- Pittsburgh Railways Co. v. PUC, 237 A.2d 602 (Pa. 1967) (discussed concerned parties as those with facilities at the crossing)
- Lehigh Valley R.R. Co. v. Pub. Serv. Comm'n, 161 A. 422 (Pa. Super. 1932) (common-law view: presence/ownership of track imposes liability)
- AT & T v. PUC, 737 A.2d 201 (Pa. 1999) (PUC has broad discretion in allocating costs once parties are properly before it)
- Greene Twp. Bd. of Supervisors v. PUC, 668 A.2d 615 (Pa. Cmwlth. 1995) (nonexclusive factors PUC may consider in cost allocation)
