Norfolk Southern Corporation 1200 Peachtree Street, N.E. Atlanta, Georgia, 30309 January 27, 2016 Robert C. Lauby, P.E. Associa

Norfolk Southern Corporation 1200 Peachtree Street, N.E. Atlanta, Georgia, 30309 January 27, 2016

Robert C. Lauby, P.E. Associate Administrator for Railroad Safety and Chief Safety Officer Federal Railroad Administration 1200 New Jersey Avenue, S.E., Mailstop 25 Washington, D.C. 20590

RE: Norfolk Southern Railway Revised Positive Train Control Implementation Plan (Docket FRA –2010- 0060)

Dear Associate Administrator Lauby,

Pursuant to the Positive Train Control Enforcement and Implementation Act of 2015 (“Act”), Norfolk Southern Railway Company (“NSR”) hereby submits the enclosed revised Positive Train Control Implementation Plan (“PTCIP”). For ease of review, the PTCIP is organized to sequentially follow the requirements of the Act as codified at 49 U.S.C. § 20157(a)(2).

The filing contains security sensitive transportation information and is marked SSI with the appropriate designations. NSR has made three filings in this submittal, one designated SSI for FRA review, one designated SSI with highlights of redacted material for FRA review, and one redacted for presentation to the public on the NS PTC docket.

Please contact me if you have any questions or require additional information.

Kindest Regards,

Lisa Wilson Lisa Wilson Manager Advanced Train Control Regulatory Compliance and Training NORFOLK SOUTHERN RAILWAY COMPANY Revised Positive Train Control Implementation Plan Version R1.0

PTC Docket: FRA-2010-0060

This document and its appendices, including an alternative schedule and sequence for implementing a positive train control system, constitute the revised PTC Implementation Plan for the Norfolk Southern Railway Company. It is submitted to the Federal Railroad Administration as required by the Positive Train Control Enforcement and Implementation Act of 2015, Public Law 114-73.

This document and its appendices, including an alternative schedule and sequence for implementing a positive train control system, constitute the revised PTC Implementation Plan for the Norfolk Southern Railway Company. It is submitted to the Federal Railroad Administration for approval pursuant to Title 49 CFR Part 236, Subpart I, § 236.1009, as mandated by the Rail Safety Improvement Act of 2008 § 104, Public Law 110-432 and the Surface Transportation Extension Act of 2015, Public Law 114-73.

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SENorfolkNSRITIVE SECURITY Southern INFORMATION Railway (SSI) Company Confidentiality Notice

This document contains information pertaining to Norfolk Southern’s risk-based deployment of a positive train control system, disclosure of which could be detrimental to transportation safety. In preparing this filing, Norfolk Southern has determined that certain sections of the submission, as identified below, must be redacted on the grounds that they contain sensitive security information within the meaning of 49 C.F.R. Parts 15 and 1520.

This document also contains confidential commercial information within the meaning of 5 U.S.C. §552 (b)(4) pertaining to Norfolk Southern and its freight rail tenants, which is subject to non-disclosure requirements under 49 U.S.C. §11904. The disclosure of such information could result in competitive harm to or impair NSR’s competitive position by disclosing NSR’s business practices.

Disclosure is prohibited without the express written permission of the Norfolk Southern Railway Company (“NSR”).

Norfolk Southern hereby makes a request to the agency pursuant to 49 C.F.R. Section 209.11 that the redacted material be given confidential treatment on the foregoing grounds. The sections of the document redacted under the foregoing cited provisions and appropriately marked are:

. 4.3.2.2 Class II and III Tenant Railroads Required to Equip for PTC to Operate on NSR PTC Required Track . 4.3.2.3 Class II and III Tenant Railroads Not Required to Equip Must Operate under § 236.1029 on NSR PTC Required Track . 4.3.2.4 Class II and III Tenant Railroads Not Required to Equip to Operate in PTC Required Territory Where Passenger Service Operates . 4.3.3.2 Obstacles to Tenant Interoperability . Appendix C NSR PTC Track Segment Characteristics . Appendix D NSR PTC Tenant Interoperability Agreements . Appendix E Exclusions and Removals from PTC Baseline

As described in § 236.1009(e)(3), this filing is being made in three separate parts:

. Unredacted SSI for FRA review . Highlighted SSI for FRA review . Public Redacted

p. ii

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SE NSRITIVE SECURITY INFORMATION (SSI)

REVISION HISTORY

Date Version Description Author 16 April 2010 1.0 Initial NSR PTCIP Submittal to FRA NSR- L. Wilson 27 May 2010 1.2 Clarification of items following FRA review NSR- L. Wilson 09 July 2010 1.3 Clarification of items for FRA approval NSR- L. Wilson NSR Revised PTC Implementation Plan, including alternative sequence and schedule per Positive Train Control Enforcement and 27 January 2016 R1.0 Implementation Act of 2015 NSR- L. Wilson

p. iii

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SETABLENSRITIVE SECURITY OF CONTENTS INFORMATION (SSI)

1 Introduction ...... 1 1.1 Executive Summary ...... 1 1.1.1 Summary of Implementation ...... 1 1.2 Confidential Treatment of PTCIP Content ...... 4 1.3 Acronyms and Definitions ...... 4 1.4 Reference Documents ...... 6

2 How the NSR PTC System Will Provide for Interoperability ...... 8 2.1 Methods to Achieve Interoperability ...... 8 2.1.1 Common Technology ...... 8 2.1.2 Standard Implementation...... 10 2.1.3 Product Testing ...... 11 2.1.4 Industry Partnership ...... 12

3 How the NSR PTC System Will Be Implemented in a Manner That Addresses Areas of Greater Risk before Areas of Lesser Risk ...... 14 3.1 Track Segment Characteristics ...... 14

4 Requirements of 49 C.F.R. §236.1011 ...... 17 4.1 Functional Requirements ...... 17 4.2 Notice of Product Intent, PTC Development Plan, PTC Safety Plan ...... 19 4.3 Interoperability...... 19 4.3.1 How the PTC System Will Provide for Interoperability ...... 20 4.3.2 Railroad Agreement Provisions Relevant to Interoperability ...... 20 4.3.3 Interoperability Next Steps and Obstacles ...... 24 4.3.4 NSR as Tenant to a Foreign Line Host ...... 26 4.4 Relative Risk ...... 26 4.5 Sequence and Schedule of Implementation ...... 26 4.5.1 Exclusion or Removal of PTC Track Segments from PTC Baseline ...... 27 4.5.2 Additions of Track Segments ...... 29 4.6 Locomotives (Rolling Stock) ...... 29 4.6.1 Locomotives to Be Equipped ...... 30 4.6.2 PTC Locomotive Installation Schedule & Progressive Implementation ...... 31 4.6.3 Reporting ...... 32 4.7 Wayside Devices ...... 33 4.7.1 Wayside Hardware to Be Installed ...... 33

p. iv

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SENSRITIVE4.7.2 SECURITYWayside INFORMATIONInstallation Schedule (SSI) ...... 33 4.8 Mainline or Non-Mainline Track Identification ...... 34 4.9 Basis for Determination that Risk-Based Prioritization Is Not Practical ...... 34 4.9.1 Resources ...... 35 4.9.2 Location Specifics ...... 36 4.10 Additional Requirements for Class I Railroads ...... 38

5 Other Requirements of the Positive Train Control Enforcement and Implementation Act of 2015 ...... 39 5.1 Spectrum Acquisition Schedule ...... 39 5.2 Hardware Amounts by Category and Schedule for Installation ...... 39 5.3 Number of and Schedule for Employee Training ...... 40 5.4 Summary of Remaining Technical, Programmatic, Operational or Other Challenges ...... 42 5.4.1 Challenges to Locomotive Implementation ...... 42 5.4.2 Challenges to Wayside Implementation ...... 43 5.4.3 Challenges to Interoperability ...... 45 5.4.4 Challenges to Testing, Demonstration, Certification and Progressive Implementation...... 45 5.5 Schedule and Sequence for Implementing PTC by the Positive Train Control Enforcement and Implementation Act of 2015 Deadline ...... 47

Table of Tables

Table 1 - Summary of NSR PTC Implementation Requirements ...... 3 Table 2- PTCIP Acronyms and Meaning ...... 4 Table 3 - PTCIP Frequently Used Terms and Meaning ...... 5 Table 4 - I-ETMS PTC Functions ...... 18 Table 5- Rolling Stock to Be Equipped ...... 30 Table 6 - Locomotive Equipping and Percentage of NSR Trains as PTC Trains ...... 32 Table 7 - Wayside Installation Schedule ...... 34 Table 8 - NSR PTC Spectrum Acquisition Schedule ...... 39 Table 9 - PTC Required Hardware Totals and Implementation Schedule ...... 40 Table 10- Employee PTC Training and Schedule ...... 41

Table of Appendices Appendix A NSR Implementation Summary Metrics Appendix B NSR PTC Implementation Schedule Sequence Hardware Totals Appendix C NSR PTC Track Segment Characteristics Appendix D NSR PTC Tenant Interoperability Agreements p. v

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SEAppendixNSRITIVE SECURITYE Exclusions INFORMATION and Removals (SSI) from PTC Baseline

p. vi

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SE1NSR ITIVEIntroduction SECURITY INFORMATION (SSI)

1.1 Executive Summary On October 29, 2015, the Positive Train Control Enforcement and Implementation Act of 2015 (the “Act”), which amends 49 U.S.C. § 20157, was enacted. The Act requires each covered railroad to submit to the Federal Railroad Administration (the “FRA”) a revised PTCIP (as hereinafter defined) or “Plan” no later than 90 days after the Act’s enactment.

This document is the revised PTC Implementation Plan v.R1.0 of Norfolk Southern Railway Company (“NSR” or “Norfolk Southern”) as required by the Act. This revised Plan includes an alternative schedule and sequence as permitted by 49 U.S.C. § 20157(a)(2)(B).

This Plan also reflects certain exclusions or removals from NSR’s PTC baseline as permitted by 49 C.F.R. § 236.1005(b)(4). All of the exclusions or removals reflected in this Plan are categorical exclusions (i.e., exclusions that are permitted provided certain objective criteria are met). NSR has not submitted a separate Request for Amendment to exclude these segments pursuant to Section 11315 of P.L. 114-94.

Norfolk Southern has worked in good faith to ensure the accuracy and completeness of the analysis and Plan for its PTC implementation. All metrics, dates and goals to deploy PTC to the rail network are based on NSR’s estimates at the time of this filing. As the PTCIP is a living document, NSR will submit to the FRA any appropriate revisions in conformance with the applicable regulatory process.

NSR certifies that it will be in full compliance with the requirements of 49 U.S.C. § 20157 on or before December 31, 2020.

1.1.1 Summary of Implementation NSR is deploying a PTC system on 8,028 miles of its network that meet the requirements of 49 U.S.C. § 20157 and 49 C.F.R. 236, Subpart I. This revised PTCIP, as required by the Act

. Describes how the positive train control system will provide for interoperability of the system with the movements of trains of other railroad carriers over its lines; . Describes how, to the extent practical, the positive train control system will be implemented in a manner that addresses areas of greater risk before areas of lesser risk; p. 1

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SENSRITIVE SECURITY. Complies INFORMATION with the (SSI) positive train control system implementation plan content requirements under section 236.1011 of title 49, Code of Federal Regulations; and . Provides the calendar year(s) in which spectrum will be acquired and available for use in each area as needed for PTC implementation, if such spectrum is not already acquired and available for use; . Provides the total amount of positive train control system hardware that will be installed for implementation, with totals separated by each major hardware category; . Provides the total amount of positive train control system hardware that will be installed by the end of each calendar year until the positive train control system is implemented, with totals separated by each hardware category; . Provides the total number of employees required to receive training under the applicable positive train control system regulations; . Provides the total number of employees that will receive the training, as required under the applicable positive train control system regulations, by the end of each calendar year until the positive train control system is implemented; . Provides a summary of any remaining technical, programmatic, operational, or other challenges to the implementation of a positive train control system, including challenges with— . availability of public funding; . interoperability; . spectrum; . software; . permitting; and . testing, demonstration, and certification; and . Provides an alternative schedule and sequence for implementing a positive train control system subject to Secretarial Review under the Act.

Table 1 - Summary of NSR PTC Implementation Requirements provides a summary of the NSR PTC implementation metrics over the 132 PTC districts. The final number may differ slightly as employment and design factors change. This table is reproduced as Appendix A to this Plan.

p. 2

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SENSRITIVE SECURITY INFORMATIONTable 1 - Summary (SSI) of NSR PTC Implementation Requirements Thru EOY EOY EOY EOY EOY 2015 2016 2017 2018 2019 2020 Total Route Miles 8,028 Line Segments 0 9 27-31 66-70 104-106 132 132 PTC Trains as a Percentage 0% 3 - 8% 10 -25% 30 - 45% 45 - 60% 60 -75% 60-75% of Total NSR Trains Employees Trained 4,627 7,370 10,778 15,048 18,041 21,446 21,446 Wayside Signal WIUs 1,932 2,459 3,371 4,007 4,007 Wayside Switch Monitor 34 56 150 150 150 WIUs Wayside Radios 1,908 2,269 2,847 3,259 3,259 Wayside Towers/Poles 1,439 1,742 2,408 3,259 3,259 Base Station Towers/Poles 311 351 381 409 409 Base Station Radios 311 351 381 411 411 Locomotive TMCs 1,959 2,079 2,310 2,900 2,900 Locomotive Radios 730 1,175 2,038 2,900 2,900 Office Hardware Done

Spectrum Location Year Acquired Year Available for Use Nationwide 2008 2008 Chicago, IL 2013 2013 Philadelphia, PA 2016 2016 New Jersey Regulatory Review 2016 Expect 2016

NSR is fully committed to the implementation of PTC. The senior management of the company has been involved in monthly meetings with the PTC project team, which has reviewed technical and resourcing issues, coordinated issues with the other roads and addressed issues dealing with regulatory agencies as they have presented themselves. The PTC system required by Congress requires NSR to assemble a system of systems, all of which have to function with close to six-sigma reliability for the entire system to operate at the current railroads’ levels. Not only is this system highly complex, it must operate in one of the most hostile industrial environments—a moving diesel-electric locomotive and track wayside. While we are working feverishly to build reliability into every segment of the system and rigorously test PTC, the possibility of disruptions as PTC is implemented is a very real one. The NSR PTC schedule and sequence provides for implementation of a PTC system as soon as practicable, but no later than December 31, 2020, in conformance with the Act.

p. 3

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SE1.2NSR ITIVEConfidential SECURITY INFORMATION Treatment (SSI) of PTCIP Content NSR has determined that certain sections of the PTCIP must be redacted on the grounds that it could cause competitive harm to Norfolk Southern within the meaning of 5 U.S.C. § 552 (b)(4) and/or 18 U.S.C. Section 1905 and that it contains certain security sensitive information within the meaning of 49 C.F.R. parts 15 and 1520. See also SSI Order 2005-09-FRA-01 and SSI Order 2011-06-FRA-01.

The majority of the information redacted from public view is security sensitive information that is the result of the railroad carrier’s route analysis of security sensitive commodity data, by route, district or series of districts as aggregated by NSR. This data identifies the total number of shipments designated by certain UN identification numbers as defined in the Pipeline and Hazardous Materials Safety Administration (PHMSA) regulations and 49 CFR §§ 236.1003, 171.8, 173.115, and 173.132. Other redacted material describes commercial arrangements between NSR and its tenant railroads.

NSR requests from FRA in its PTCIP filing, pursuant to 49 C.F.R. Section 209.11, that the redacted material be given confidential treatment on the foregoing grounds. Disclosure is prohibited without the express written permission of Norfolk Southern Railway Company.

1.3 Acronyms and Definitions This section includes a list of acronyms and terms and their meaning that may be used to interpret the PTCIP. Table 2- PTCIP Acronyms and Meaning contains a list of acronyms frequently used in this document. Table 3 - PTCIP Frequently Used Terms and Meaning contains a list of terms frequently used in both this document and Subpart I.

Table 2- PTCIP Acronyms and Meaning

Acronym Meaning AAR Association of American Railroads AREMA American Railway Engineering and Maintenance-of- Way Association ASLRRA American Short Line and Regional Railroad Association AVP Assistant Vice President BNSF BNSF Railway CFR Code of Federal Regulation CHMM Crash Hardened Memory Module CSXT CSX Transportation EC2 Electro Code 2 signaling product p. 4

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SENSRITIVE SECURITYAcronym INFORMATION Meaning (SSI) FR Federal Register FRA Federal Railroad Administration GIS Geographical Information System ITC Interoperable Train Control MTEA Main Line Track Exclusion Addendum NPI Notice of Product Intent PIH Poison by Inhalation Hazard PTC Positive Train Control PTCDP Positive Train Control Development Plan PTCIP Positive Train Control Implementation Plan PTCSP Positive Train Control Safety Plan RFA Request For Amendment RSD Revenue Service Demonstration SSI Sensitive Security Information UPRR Union Pacific Railroad U.S.C. United States Code V&V Verification & Validation

Table 3 - PTCIP Frequently Used Terms and Meaning

Term Meaning Class I railroad See definition in 49 C.F.R. § 236.1003 District A portion of an operating division designated by timetable Host railroad A railroad that has effective operating control over a segment of track Interoperability See definition in 49 C.F.R. § 236.1003 ITCA The Interoperable Train Control Agreement, executed in October 2008 by BNSF, CSXT, NSR and UPRR to develop a set of standards which would allow the participants to adopt an interoperable train control system, and or its working or technical committees Line segment Same as a district Main line See definition in 49 C.F.R. § 236.1003 Main line track See definition in 49 C.F.R. § 236.1003 exclusion addendum NPI See definition in 49 C.F.R. § 236.1003 PTC See definition in 49 C.F.R. § 236.1003 PTCDP See definition in 49 C.F.R. §236.1003 PTCIP See definition in 49 C.F.R. §236.1003 PTC railroad See definition in 49 C.F.R. § 236.1003 PTCSP See definition in 49 C.F.R. § 236.1003

p. 5

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SENSRITIVETerm SECURITY INFORMATIONMeaning (SSI) PTC System See definition in 49 C.F.R. § 236.1003 Certification Request For See definition in 49 C.F.R. § 236.1003 Amendment Segment of track See definition in 49 C.F.R. § 236.1003 Subdivision or Any portion of a railroad district designated as PTC territory. A subdivision SUBDIV file (subdiv) is a binary file that represents all of the geographic and railroad information about a segment of railroad track. The data in a subdiv file includes but is not limited to the geographic location of the track centerline, switches, signals, speed limits, mileposts, signs Tenant railroad See definition in 49 C.F.R. § 236.1003 Track segment See definition in 49 C.F.R. § 236.1003

1.4 Reference Documents The documents listed here either are referenced within this PTCIP or are listed as general resources to provide information regarding a particular subject relevant to this PTCIP. These referenced documents are not considered a part of this PTCIP. Documents that form an integral part of this PTCIP are contained in the appendices.

Documentation on this list may be obtained from the applicable standards body where appropriate, or from the publisher of the document. For undated references, the most current version applies.

[1] Congress of the United States. Rail Safety Improvement Act of 2008. Public Law 110–432, 16 October 2008. [2] Congress of the United States. Positive Train Control Enforcement and Implementation Act of 2015. Public Law 114-73, 29 October 2015. [3] Congress of the United States. Fixing America’s Surface Transportation (FAST) Act. Public Law 114-94, 4 December 2015. [4] Federal Railroad Administration, US Department of Transportation. 49 CFR Part 236 Subpart H, Standards for Development and Use of Processor-Based Signal and Train Control Systems; Final Rule, Docket Number FRA-2001- 10160, 7 March 2005. [5] Federal Railroad Administration, US Department of Transportation. 49 CFR Parts 229, 234, 235 236 Subpart I, “Positive Train Control Systems; Final Rule,” Docket No. FRA-2008-0132, Notice No. 3; Docket No. FRA–2011– 0028, Notice No. 3; and Docket No. FRA–2011–0061, Notice No. 3.

p. 6

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SENSRITIVE[6 SECURITY] Federal INFORMATION Railroad Admin (SSI)istration, US Department of Transportation. “Risk Prioritization Methodology for PTC System Implementation,” 7 January 2010. [7] Association of American Railroads. AAR Manual of Standards and Recommended Practices, Section K, Parts I- VI. [8] Association of American Railroads. PTC Implementation: The Railroad Industry Cannot Install PTC on the Entire Nationwide Network by the 2015 Deadline. [9] CSX Transportation, Norfolk Southern Railway Company, Union Pacific Railroad. Interoperable Electronic Train Management System (I-ETMS®) Positive Train Control Development Plan (PTCDP), Version 3.1, 8 July 2015.

[10] Norfolk Southern Railway Company. PTC Implementation Plan v1.3, 9 July 2010.

p. 7

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SE2NSR ITIVEHow SECURITY the NSR INFORMATION PTC System (SSI) Will Provide for Interoperability

As required by the Act, this section describes how the PTC system deployed by NSR will provide for interoperability between the host and all tenant railroads on the NSR districts required to be equipped with a PTC system. Further discussion of interoperability can be found in Section 4.3.

49 C.F.R. § 236.1006(a) generally requires each train operating on any track segment equipped with a PTC system to be controlled by a locomotive equipped with an onboard PTC apparatus that is fully operative and functioning in accordance with the NSR PTCSP governing that territory, with certain exceptions described in § 236.1006(b). NSR is implementing a PTC system designed to be interoperable with any PTC system that gains FRA Type Approval and is built to common interface standards to achieve interoperability. Any tenant railroad required to equip for operation on NSR must also successfully and safely interoperate with the NSR PTC system.

2.1 Methods to Achieve Interoperability Interoperability is achieved through four interrelated means: Product testing, industry and community partnership, common technology, and standard implementation. Technical interoperability is achieved using common interface control documents and standards. Semantic interoperability is achieved through the common use of documented system behavioral specifications. Organizational interoperability is achieved primarily through industry partnerships and forums, such as committees chartered by ITC, AREMA, AAR and ASLRRA, and through positive business relationships between host and tenant railroads. Each of these methods to achieve interoperability is addressed in the NSR interoperability terms and conditions required for each tenant road’s operation in NSR PTC territory.

2.1.1 Common Technology Without common product engineering, PTC systems will be unable to intercommunicate or otherwise interact as necessary to comply with the law. To that end, NSR is deploying the Wabtec I-ETMS PTC system, which is designed to support interoperability. By design, I-ETMS provides for full functionality for any equipped locomotive, regardless of ownership, with any office or wayside correspondingly equipped. Interoperability is achieved through native operation of I-ETMS without the need for data, function or human-machine interface (HMI) translation. Interoperable communications are achieved through adoption of the common communications and message protocols and application behavior specifications. I-ETMS is designed to work with the methods of operation of both NSR and its interoperability partners and accommodates any differences in the data provided by back office systems. I-ETMS and its p. 8

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SEoperationsNSRITIVE SECURITY are fully INFORMATION described in (SSI) the latest FRA Type Approved Interoperable Electronic Train Management System (I-ETMS®) Positive Train Control Development Plan. If any system other than I-ETMS is to be deployed by an NSR tenant railroad for operation on NSR, it must first gain FRA Type Approval to ensure it meets all legal requirements for interoperability and provides FRA the confidence that the system will exhibit syntactic interoperability so that it may successfully communicate and exchange data with I-ETMS.

From a railroad operating perspective, “interoperability” can be construed to mean any scenario in which the locomotive, railroad control system and/or train crew are not “employed” by the same entity. Permutations of interoperability scenarios may thus exist in three dimensions, as illustrated in the Figure 1 - Dimensions of Interoperability. I-ETMS supports each permutation of interoperability.

Figure 1 - Dimensions of Interoperability

The AAR modified and adopted standards developed by the ITCA signatories and committees that address a list of interoperability requirements:

. Definition and adoption of uniform interface standards; . Definition, adoption, and implementation of AAR-standard communications protocols; . Definition, adoption, and implementation of common office-locomotive communications protocols and message formats; . Definition, adoption, and implementation of a common Human Machine Interface, allowing the train crew from any of the participant’s roads to utilize the system on any participant’s locomotives on territory for which the train crew is qualified;

p. 9

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SENSRITIVE SECURITY. Adoption INFORMATION of a coordinated (SSI) plan for configuration management of the interoperable PTC onboard executable software; . Agreement on use of railroad-owned radio spectrum in the 220MHz band for communications between the locomotive and wayside and the locomotive and back office; . Agreement to acquire, develop and deploy all of the technical capabilities required to permit the use of shared communications infrastructure; and . Definition and adoption of standards allowing each participant’s train crew, at the start of a trip, to initialize the interoperable onboard system with the back offices of any participant’s PTC system, which may be traversed during the trip to support all interoperability scenarios that will be encountered on the line-of-road with respective locomotive fleets and run-through operations.

Standard application-level specifications define the behavior of the interoperable system. Use of and compliance with these common behavioral specifications ensure each interoperable system segment properly interprets and acts upon exchanged data messages.

2.1.2 Standard Implementation I-ETMS complies with the AAR PTC standards and best practices found in the AAR Manual of Standards and Recommended Practices, Section K, Parts I- VI. The I-ETMS PTCDP describes the I-ETMS PTC system components and operation. NSR requires that its tenant railroads required to equip in PTC territory install and implement a PTC system (or its components, as necessary) that conforms to the AAR Manual of Standards and Recommended Practices – Section K documents related to the implementation of positive train control.

2.1.2.1 AAR Manual of Standards and Recommended Practices – Section K Section K-I, “Railway Electronics Systems Architecture and Concepts of Operations,” documents the system architecture for an interoperable train control (ITC) compliant PTC system. It describes how the ITC-compliant PTC system, which is a locomotive-centric train control system, is designed to be overlaid on existing methods of operation and to provide a high level of railroad safety through enforcement of a train’s:

. authorized operating limits . protection against train-to-train collisions . derailments due to over speed operations

p. 10

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SENSRITIVE. SECURITYunauthorized INFORMATION incursion (SSI) into work zones . operation through main track switches improperly lined. Section K-II, “Locomotive Electronics and Train Consist System Architecture,” defines the logical system architecture for locomotive electronics and specifies the associated physical architecture requirements. This section provides general discussion of functionality and architecture and presents the standard for train information systems, additional train handling and safety information in locomotive cabs.

Section K-III, “Wayside Electronics and Mobile Worker Communications Architecture,” specifies requirements for the wayside interface unit and hardware for the wayside messaging server.

Section K-IV, “Office Architecture and Railroad Electronics Messaging,” documentation specifies the messaging protocols and requirements. This section’s documentation also specifies critical interface requirements between the wayside and the locomotive and the office and locomotive, among others.

Section K-V, “Electronics Environmental Requirements and Systems Management,” documentation specifies the range of environmental conditions for the storage and operation of railway electronics equipment. Documentation also describes the requirements established for the Interoperable PTC Systems Management System (ITCSM) and the PTC I-ETMS Master Test Strategy (MTS).

2.1.3 Product Testing The NSR PTC system has been and will continue to be tested through a rigorous verification and validation (V&V) program instituted by suppliers of system components and software and by Norfolk Southern, as the system owner and integrator. The testing program will be detailed in the NSR PTC Safety Plan. NSR has instituted a master test strategy specific to NSR processes and based upon the AAR Recommended Practice RP-9457, “Positive Train Control Interoperable Electronic Train Management System (I-ETMS) Master Test Strategy (MTS),” which NSR co- authored.

The NSR PTC testing strategy includes, but is not limited to, testing of all four segments of the system, their individual components and the integration of all components as a system of systems. NSR testing addresses all PTC system functionality by demonstrating that I-ETMS is in conformance with its safety-functional requirements in laboratory and field environments. Testing also validates I-ETMS semantic interoperability; in other words, proving the system can

p. 11

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SEautomatically,NSRITIVE SECURITY accurately INFORMATION and meaningfully (SSI) interpret the information exchanged between each communicating PTC system.

Because of the I-ETMS architecture, design, and operation, functions that support interoperability are fully exercised during functionality testing. Few tests are required solely to cover many of the permutations of interoperability. NSR will conduct some interoperability tests at property boundaries with tenant roads to validate tenant readiness for operations on the NSR network.

2.1.4 Industry Partnership NSR has been and will continue to be actively engaged as a leader in rail industry forums, teams, organizations, user groups and conferences to identify, discuss and resolve interoperability topics and issues.

An Interoperable Train Control collaboration agreement (ITCA) was executed by and among BNSF Railway Company (BNSF), CSX Transportation, Inc. (CSXT), Norfolk Southern Railway Company (NSR) and Union Pacific Railroad (UPRR) in 2008 for developing an interoperable PTC system that would enable locomotives of one railroad to transition at track speed to the control of another railroad. Since that time, NSR PTC resources have participated in:

. ASLRRA annual conventions . NSR Shortline Marketing’s annual Shortline Caucus meetings . NSR Shortline Marketing meetings . AAR/ASLRRA/APTA PTC Conferences . ITC meetings and committees . AREMA annual conventions and PTC committees . Northeast Corridor Communications Team NSR fully supports industry education and teamwork to facilitate interoperability. The AAR, through the PTC Interoperability Committee (PTCIC) created a PTC Interoperability Interchange agreement that binds signing railroads to an agreed upon process for identifying, coordinating, and scheduling software and hardware revisions to maintain interoperability. This industry group facilitates coordination between the Industry Committees, vendors, interchange foreign railroads and tenant railroads, tying together each railroad’s configuration management plan with industry- and vendor-driven configuration management processes. NSR has signed the AAR/ASLRRA/APTA Positive Train Control Interchange Agreement to facilitate governance of

p. 12

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SEPTCNSR ITIVE systems SECURITY and interoperability.INFORMATION (SSI) NSR requires each of its tenant railroads operating in PTC territory to sign and commit to comply with this industry agreement.

p. 13

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SE3NSR ITIVEHow SECURITY the NSR INFORMATION PTC System (SSI) Will Be Implemented in a Manner That Addresses Areas of Greater Risk before Areas of Lesser Risk

NSR applied a methodology utilizing track segment characteristics to determine the relevant quantifiable risk of each mainline segment of its railroad. Mainline segments, as defined by 49 C.F.R. Subpart I, are:

Except as provided in 49 C.F.R. § 236.1019 or where all trains are limited to restricted speed within a yard or terminal area or on auxiliary or industry tracks, a segment or route of railroad tracks:

Of a Class I railroad, as documented in current timetables filed by the Class I railroad with the FRA under § 217.7 of this title, over which 5,000,000 or more gross tons of railroad traffic is transported annually; or

Used for regularly scheduled intercity or commuter rail passenger service, as defined in 49 U.S.C. 24102, or both. Tourist, scenic, historic, or excursion operations as defined in part 238 of this chapter are not considered intercity or commuter passenger service.

Through this methodology, NSR determined the relevant quantifiable risk and the risk-based priority of each mainline district. NSR set the baseline for sequencing implementation by ranking relevant quantifiable risk into three groups or tiers. The resulting risk prioritization calculations are included in Appendix C NSR PTC Track Segment Characteristics.

3.1 Track Segment Characteristics NSR considered the track segment characteristics identified in § 236.1011(a)(5) and others described in the January 2010 FRA Technical Report, “Risk Prioritization Methodology for PTC System Implementation.” Ultimately, eight factors were identified as significant for inclusion in the NS methodology included in our FRA-approved PTCIP v1.3 Appendix C-1 PTCIP Risk Prioritization Model:

1. Freight train volume: annual million gross ton (MGT) levels NSR assessed this risk factor to have a “Very High” effect on the probability component of risk and a “High” effect on the consequence component of risk. The total risk weight assigned to this risk factor was 20%. p. 14

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SENSRITIVE2. SECURITY Presence INFORMATION and volume (SSI)of passenger traffic NSR assessed this risk factor to have a “High” effect on the probability component of risk and a “Very High” effect on the consequence component of risk. The total risk weight assigned to this risk factor was 20%. Although there is a risk weight of 20% with respect to all factors, if a district has passenger service, it is equipped for PTC. 3. Presence and volume of PIH material (loads and residue) transported NSR assessed this risk factor to have a “High” effect on the probability component of risk and a “Very High” effect on the consequence component of risk. As a result, the total risk weight assigned to this risk factor was 20%. 4. Number of tracks NSR assessed this risk factor to have a “High” effect on the probability component of risk and a “Medium” effect on the consequence component of risk. As a result, the total risk weight assigned to this risk factor was 10%. 5. Method of operation NSR assessed this risk factor to have a “High” effect on the probability component of risk and a “Medium” effect on the consequence component of risk. As a result, the total risk weight assigned to this risk factor was 10%. 6. Maximum allowable train speeds NSR assessed this risk factor to have a “Medium” effect on the probability component of risk and a “High” effect on the consequence component of risk. As a result, the total risk weight assigned to this risk factor was 10%. 7. Track grade NSR assessed this risk factor to have a “Medium” effect on the probability component of risk and a “Very Low” effect on the consequence component of risk. As a result, the total risk weight assigned to this risk factor was 5%. 8. Track curvature NSR assessed this risk factor to have a “Medium” effect on the probability component of risk and a “Very Low” effect on the consequence component of risk. As a result, the total risk weight assigned to this risk factor was 5%.

Each mainline district has a range of values based on its operational characteristics for each risk factor. NSR, along with other Class I road experts, assigned and applied a weight to each risk factor to assess each district or subdivision’s overall risk mathematically. Since not all districts are equal, a weighted scoring was then applied using a distance-weighted average to ensure that risk is proportional to distance, where “0” represents the lowest risk and “5” represents p. 15

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SEtheNSR ITIVE highest SECURITY risk. The INFORMATION result is an (SSI) overall risk ranking for each mainline NSR district. Similarly ranked districts were grouped into deployment tiers, so that in general, the NSR deployment is sequenced by highest risk districts based on the presence of certain operational characteristics (risk factors), followed by medium risk; and finally, low risk districts. Exceptions to this quantifiable risk methodology are discussed in Section 4.9. These additional non-quantifiable factors were considered to contribute to the overall risk of the district to determine its sequence for implementation.

p. 16

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SE4NSR ITIVERequirements SECURITY INFORMATION of 49 (SSI) C.F.R. §236.1011

4.1 Functional Requirements As required by 49 CFR § 236.1011(a)(1) the functional requirements that the PTC system must meet can be summarized by the requirements listed in § 236.1005. A complete description of the I-ETMS® functionality is provided in the latest Type Approved Interoperable Electronic Train Management System (I-ETMS®) Positive Train Control Development Plan, available on the NSR PTC FRA Docket FRA-2010-0060. The referenced PTCDP provides a concept of operations in Section 5 of the PTCDP, which contains a common description of I-ETMS functionality. The PTCDP’s Section 5 Concept of Operations provides detail for how the I-ETMS system was built to provide for the following functional positive train control system requirements: (1) Reliably and functionally prevent: (i) Train-to-train collisions—including collisions between trains operating over rail-to-rail at-grade crossings. (ii) Overspeed derailments, including derailments related to railroad civil engineering speed restrictions, slow orders, and excessive speeds over switches and through turnouts; (iii) Incursions into established work zone limits without first receiving appropriate authority and verification from the dispatcher or roadway worker in charge, as applicable and in accordance with 49 CFR Part 214 (iv) The movement of a train through a main line switch in the improper position as further described in § 236.1005(e). (2) Include safety-critical integration of all authorities and indications of a wayside or cab signal system, or other similar appliance, method, device, or system of equivalent safety, in a manner by which the PTC system shall provide associated warning and enforcement to the extent, and except as, described and justified in the FRA approved PTCDP or PTCSP, as applicable; (3) As applicable, perform the additional functions specified in this subpart; (4) Provide an appropriate warning or enforcement when: (i) A derail or switch protecting access to the main line required by § 236.1007, or otherwise provided for in the applicable PTCSP, is not in its derailing or protecting position, respectively; {NSR has no high speed passenger lines}

p. 17

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SENSRITIVE SECURITY(ii) A mandatory INFORMATION directive (SSI) is issued associated with a highway-rail grade crossing warning system malfunction as required by §§ 234.105, 234.106, or 234.107; (iii) An after-arrival mandatory directive has been issued and the train or trains to be waited on has not yet passed the location of the receiving train; (iv) Any movable bridge within the route ahead is not in a position to allow permissive indication for a train movement pursuant to § 236.312; and (v) A hazard detector integrated into the PTC system that is required by paragraph (c) of this section, or otherwise provided for in the applicable PTCSP, detects an unsafe condition or transmits an alarm; and (5) Limit the speed of passenger and freight trains to 59 miles per hour and 49 miles per hour, respectively, in areas without broken rail detection or equivalent safeguards.

The PTCDP describes the functional requirements in Table 4 - I-ETMS PTC Functions. Other system requirement documents providing detailed descriptions of system functions and their implementation design will be provided in the PTC Safety Plan.

Table 4 - I-ETMS PTC Functions

Power Up and Diagnostics Initialization Train Consist File Download Departure Test I-ETMS System Synchronization Location Determination & Navigation Warning and Braking Calculation Territory Entrance Protection Protection of Movement Authority provided by Mandatory Directive in ABS or Non-ABS Territory Temporary Speed Restriction Protection Work Zone Protection Advisory or Cautionary Notices Protection Protection of Notice of Highway Crossing Warning System Malfunction Permanent & Equipment Speed Switch Protection Enforcement Cab Signal Indication Enforcement Reverse Movement Enforcement Restricted State Enforcement Notification of Authority Violation by Another Train Crew Authority Requests Cut-Out State Territory Exit Horn Activation Parking Brake Train Handling and Energy Management Assistance Logging File Upload Train Operation Exception Reporting Switch Position Awareness Crew Logoff

p. 18

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SE4.2NSR ITIVENotice SECURITY of Product INFORMATION Intent, (SSI) PTC Development Plan, PTC Safety Plan A Notice of Product Intent required under § 236. 1009(c) was not applicable to nor filed by NSR. NSR submitted its first PTCIP in April 2010 and its amended PTC Implementation Plan v1.3, 9 July 2010 to address feedback from the FRA. FRA approved the NSR PTCIP v1.3 on 24 August 2010.

As required by §§ 236.1009(b) and 236.1013, NSR, CSXT and UPRR together submitted the Interoperable Electronic Train Management System (I-ETMS®) Positive Train Control Development Plan (PTCDP), Version 3.1, 8 July 2015 for which Type Approval FRA-TA-2011-02-C was finalized on December 21, 2015.

As required by § 236.1009(d) and § 236.1011(a)(10), Norfolk Southern filed a preliminary draft PTC Safety Plan with FRA 19 December 2014 and plans to file a final PTC Safety Plan which meets the requirements of § 236.1015 in first quarter of 2016, or as soon as field test results are available, to seek system certification of its implementation of I-ETMS.

4.3 Interoperability This section addresses interoperability between NSR and its tenant roads and

. Includes relevant provisions of agreements, executed by all applicable railroads, in place to achieve interoperability; . Identifies any railroads with respect to which interoperability agreements have not been achieved as of the time the plan is filed, the practical obstacles that were encountered that prevented resolution and the further steps planned to overcome those obstacles. NSR has made a formal written request to each tenant railroad requesting identification of each item of rolling stock to be PTC-system equipped and the date each will be equipped; and has included each tenant railroad's response to the NSR written request made in accordance with 49 C.F.R. § 236.1011(a)(6)(iv).

p. 19

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SE4.3.1NSRITIVE How SECURITY the PTC INFORMATION System Will (SSI) Provide for Interoperability A full description of how the NSR PTC system will provide for interoperability and the methods to achieve interoperability are provided in Section 2.

4.3.2 Railroad Agreement Provisions Relevant to Interoperability Since 2010, NSR has maintained contact with shortline, commuter/passenger and Class I tenants through several industry related forums. NSR has also held individual discussions with several tenants, focused on tenant implementation education, implementation status and progress, and resolution of issues regarding interoperability. Prior to revising the PTCIP, NSR conducted a renewed survey of tenant operations on its railroad to identify tenant railroad operating rights and operations on PTC-required districts. For those tenants operating in PTC- required territory, NSR reviewed those operations and relevant risk characteristics of the locations.

In December 2015 as required by 49 C.F.R. § 236.1011(a)(6)(iv)(A), NSR made a formal written request to each Class II or III tenant railroad operating on PTC-required track

. To notify the railroad of its requirement to equip for PTC . To provide the NSR terms and conditions for interoperability . To request the tenant identify rolling stock to be PTC-system equipped . To request the date their rolling stock will be equipped with a PTC system . To provide NSR contacts for commercial, technical and regulatory compliance related matters and to request the same from each tenant. A copy of the letter sent to each railroad with the provisions of those agreements as required by § 236.1011(a)(3)(i), and each tenant’s response to the NSR interoperability terms and conditions, as required by § 236.1006(a)(6)(iv)(B), is included in Appendix D NSR PTC Tenant Interoperability Agreements. NSR reached agreement on interoperability conditions with its Class I tenants through execution of the ITCA. By virtue of their implementing I-ETMS, these roads are interoperable with NSR. Information regarding their equipped rolling stock is supplied in their PTCIP.

The agreement provisions for interoperability with NSR include the following conditions to achieve technical and semantic interoperability. The tenant railroad is required to:

1. Subscribe to the AAR/ASLRRA/APTA Positive Train Control Interchange Agreement binding the tenant railroad to industry interoperability p. 20

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SENSRITIVE SECURITYstandards. INFORMATION The Regional, (SSI) Shortline and Terminal Working Group includes all participants of the Agreement who are not Class I railroads or passenger railroads. 2. Install and implement a PTC system (or its components, as necessary) which conforms to the AAR Manual of Standards and Recommended Practices – Section K documents related to the implementation of positive train control. These documents are available from the AAR. Relevant standards and recommended practices are located in the following sections of the Manual: . Section K-I – Railway Electronics Systems Architecture and Concepts of Operations . Section K-II – Locomotive Electronics and Train Consist System Architecture . Section K-IV – Office Architecture and Railroad Electronics Messaging . Section K-V – Electronics Environmental Requirements and Systems Management . Section K-VI – Railway Data Management and Communications 3. Federate an ITC-compliant message system (ITCM) for interoperable messaging and communications. Federated connection of ITC-compliant back offices will have the effect of joining the underlying communications systems that support the ITCM by allowing the free-flow of all ITC- compliant messages between back offices. Specifically, federation enables any ITC back office to pass traffic from any 220 MHz base station, locomotive or wayside as well as other railroad-specific communications networks, e.g. cellular, IEEE 802.11, etc. NSR and tenant railroad will establish bi or multi-lateral testing protocols, security standards, and related service-level requirements. The primary I-ETMS traffic that will be exchanged between railroads via federated links will be locomotive-BOS traffic and wayside-locomotive traffic. 4. Institute processes to ensure tenant railroad data security of employee credentials for PTC system initialization functionality and secure tenant railroad locomotive identification and messaging. 5. Maintain at a designated office on its railroad all records required by 49 C.F.R. § 236.1037 which demonstrate tenant railroad has:

p. 21

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SENSRITIVE SECURITY .INFORMATION Conducted (SSI)tenant railroad lab testing to validate and verify the tenant railroad PTC system installation, operation and functionality are interoperable with I-ETMS prior to field interoperability tests with NSR. Records of such tests shall be made available by tenant railroad to FRA upon request. . Participated in field interoperability testing according to a field test plan to validate and verify tenant railroad PTC system is functionally operable and interoperable for PTC service on the NS rail network. NSR shall provide records of interoperability testing to FRA, as required. . Properly installed all PTC equipment in accordance with the procedures required by 49 C.F.R. § 236.1039, “Operations and Maintenance Manual (OMM).” Records of locomotive installation checkout procedures and the OMM shall be made available by tenant railroad to FRA upon request. . Delivered the training for train crews required by 49 C.F.R. § 236.1041, “Training and qualification program, general,” § 236.1043, “Task analysis and basic requirements,” and § 236.1047, “Training specific to locomotive engineers and other operating personnel.” Records of training, exams and training plans shall be made available by tenant railroad to FRA upon request. . Each contractor providing services relating to the testing, maintenance, or operation of tenant railroad PTC system shall maintain at a designated office training records required under § 236.1039(b). Records of training, exams and training plans shall be made available by tenant railroad to FRA upon request. 6. In the event of errors or malfunctions of the system in operation on NSR, the tenant railroad shall operate under the requirements of 49 CFR § 236.1029.

4.3.2.1 Class I and Commuter/Passenger Tenant Railroads Required to Equip for PTC to Operate on NSR PTC Required Track The following Class I and commuter or passenger tenant roads are required to equip for operation on an NSR PTC required line segments:

p. 22

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SENSRITIVE SECURITY. Amtrak INFORMATION (ATK) (SSI) . BNSF Railway (BNSF) . Canadian National Railway (CN) . Canadian Pacific Railway (CP) . CSX Transportation (CSX) . Kansas City Southern Railway (KCS) . Northeast IL Regional Commuter Rail Corp. (Metra- NIRC) . Union Pacific Railroad Co. (UP) . Virginia Railway Express (VRE)

4.3.2.2 Class II and III Tenant Railroads Required to Equip for PTC to Operate on NSR PTC Required Track The following Class II and III tenant roads are required to equip for operation on an NSR PTC required line segments:

p. 23

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SENSRITIVE SECUR. N (SSI)

4.3.2.3 Class II and III Tenant Railroads Not Required to Equip Must Operate under § 236.1029 on NSR PTC Required Track The following roads have acknowledged their narrow operational limits on a PTC mainline must be performed under § 236.1029 requirements.

4.3.2.4 Class II and III Tenant Railroads Not Required to Equip to Operate in PTC Required Territory Where Passenger Service Operates In accordance with 236.1006(b)(4(i)(B), the following short lines are permitted to operate unequipped for PTC only when the following conditions exist, else equipping is required:

4.3.3 Interoperability Next Steps and Obstacles This section identifies any railroads with respect to which interoperability agreements have not been achieved as of the time the plan was filed, the practical obstacles that were encountered that prevented resolution, and the further steps planned to overcome those obstacles as required by 236.1011(a)(3)(iii).

p. 24

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SE4.3.3.1NSRITIVE InteroperabilitySECURITY INFORMATION Next Steps (SSI) Following the filing of this PTCIP, NSR will hold direct discussions with each railroad required to equip for operation in NSR PTC territory to align our tenant railroad plans for equipping with the NSR sequence and schedule. NSR was unable to accomplish these discussions prior to the filing of the PTCIP, given the timing of the PTC Extension Act. NSR will provide insight into the requirements for PTC operation, including providing guidance and assistance with PTC training for crews, and work to gain assurances that tenants’ implementations are successful. NSR has provided each tenant road with technical, commercial and regulatory compliance contacts to facilitate interoperability discussions.

4.3.3.2 Obstacles to Tenant Interoperability NSR has evaluated the tenants’ operations within their respective operating agreement rights, taken the applicable FRA regulations and Norfolk Southern’s own safety criteria into account, and concluded that it will be necessary for certain roads to equip their locomotives.

The following roads have either disputed NSR’s ability to require their locomotives to be equipped as a condition of operating on NSR PTC territory, disputed a condition of their operation or of interoperability or not responded to the letter of December 2015 by the filing of this revised PTCIP:

Although the

p. 25

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

4.3.4 NSR as Tenant to a Foreign Line Host In cases where NSR is a tenant railroad to a foreign line PTC railroad host, discussions of how interoperability is achieved are found in the host railroad’s PTCIP as required by § 236.1011(a)(3). NSR will operate its locomotives utilizing I-ETMS on each of these railroads. NSR operates as a tenant road on the following PTC host railroads:

. Amtrak (ATK) . Belt Railway Company of Chicago (BRC) . BNSF Railway (BNSF) . Canadian National Railway (CN) . Canadian Pacific Railway (CP) . Conrail Shared Assets Corporation (CRSH) . CSX Transportation (CSX) . Kansas City Southern Railway (KCS) . Kansas City Terminal Railway (KCT) . Metro North Commuter RR Co (MNCW) . New Jersey Transit Rail Operations (NJTR) . Southeastern Pennsylvania Transportation Authority (SEPA) . Terminal Railroad Association of St. Louis (TRRA) . Union Pacific Railroad Co. (UPRR)

4.4 Relative Risk The requirements of § 236.1011(a)(4) are discussed in Section 3, above.

4.5 Sequence and Schedule of Implementation NSR categorizes its implementation into phases (“sequence”). The basis for this decision includes the prioritization of districts based on relative quantifiable risk, as discussed in Section 3, and other factors affecting the operation of a Class I railroad, as described in Section 4.9. The deployment has been sequenced into 10 phases, each phase consisting of one-half of a calendar year. This allows NSR to maintain some flexibility to adjust to changing conditions in operations and some of the many challenges listed in the Summary of Remaining Technical, Programmatic, Operational or Other Challenges.

p. 26

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SEANSR completeITIVE SECURITY list of INFORMATION districts, their (SSI) sequence and schedule for implementation on or before December 31, 2020 and the hardware required for implementation is provided in Appendix B NSR PTC Implementation Schedule, Sequence and Hardware Totals. Occasionally, NSR will have a need to make changes in the implementation; any such changes will be made in accordance with applicable law.

The NSR PTC schedule is managed and monitored by the Director Advanced Train Control, with input from resources from Engineering, Mechanical, Transportation, Network & Service Management and Information Technology departments.

4.5.1 Exclusion or Removal of PTC Track Segments from PTC Baseline 4.5.1.1 Routing Changes In accordance with 49 C.F.R. § 236.1005(b)(4)(i), NSR has excluded or removed from its implementation plan certain track segments where a PTC system is otherwise required but has not yet been installed based upon changes in rail traffic, such as reductions in total traffic volume to a level below 5 million gross tons annually or the cessation of PIH materials traffic. Appendix E Exclusions or Removals from NSR PTC Baseline lists the segments that have been excluded from the Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0 and provides information regarding those track segment’s operational characteristics.

NSR attests that each of these excluded segments meets the requirements for categorical exclusion:

1 Either NSR 2014 traffic met the requirements of annual MGT less than 5 or cessation of PIH materials traffic or application controls were instituted by the end of first quarter 2016 to ensure the rerouting would be in place for all future moves.

p. 27

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SENSRITIVE SECURITYo No PIHINFORMATION traffic will be(SSI) present on the involved track segments or the gross tonnage on the involved track segments will decline to below 5 million gross tons annually as computed over a 2-year period.

4.5.1.2 Freight Lines with de Minimis Risk Not Used for Regularly Provided Passenger Service In accordance with 49 C.F.R. § 236.1005(b)(4)(iii), NSR has excluded or removed from its implementation plan certain track segments where a PTC system is otherwise required but has not yet been installed based upon the presence of a minimal quantity of PIH materials traffic. Appendix E Exclusions or Removals from NSR PTC Baseline lists the segments that have been excluded from the Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0 and provides information regarding those track segment’s operational characteristics.

NSR attests that each of these excluded segments meets the requirements for categorical exclusion:

. An operational analysis was conducted by the Network & Service Management and Marketing Industrial Products teams to validate five- year projections for traffic would meet regulatory requirements for traffic density and/or PIH materials for removal from the baseline. This analysis establishes that each such segment2: o Carries less than 15 million gross tons annually; o Does not have a heavy grade as “heavy grade” is defined in 49 C.F.R. § 232.407 for any train operating over the track segment; o Will have in effect an operating rule requiring the crew of any train approaching working limits established under 49 C.F.R. Part 214 to notify the roadway worker in charge of the train's approach at least 2 miles in advance of the working limits or, if the train crew does not have advance knowledge of the working limits, as soon as practical;

2 Either NSR 2014 traffic met the requirements listed above or application controls were instituted by the end of first quarter 2016 to ensure the rerouting would be in place for all future moves.

p. 28

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SENSRITIVE SECURITY oINFORMATION Carries fewer (SSI) than 100 cars containing PIH materials per year, excluding those cars containing only a residue, as defined in 49 C.F.R. § 171.8, of PIH materials; o Carries 2 or fewer trains per day carrying any quantity of PIH materials; o Where trains carrying any quantity of PIH materials will operate at speeds not to exceed 40 miles per hour; and o Where any train transporting a car containing any quantity of PIH materials is operated with a vacant block ahead of and behind the train.

4.5.1.3 Line Sales Since the 2008 baseline was established for the 2010 PTCIP, NSR has sold or leased two line segments. Appendix E Exclusions or Removals from NSR PTC Baseline lists the districts or portions thereof that have been excluded from the Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0 due to sale or lease of the property. Where PTC was required, NSR has ensured its agreement has maintained a provision for operations under PTC.

4.5.2 Additions of Track Segments Per 49 C.F.R. § 236.1005(b)(3) “Addition of Track Segments,” the following factors account for limited additions to the NS PTCIP:

. Regularly scheduled passenger or commuter traffic was added in Virginia, increasing the required limits of PTC of a district already designated for PTC . Changes in limits previously designated as non-mainline track limited to restricted speed within a yard or terminal area or on auxiliary or industry tracks . Changes in limits to correct data anomalies or to accommodate specific location design factors

4.6 Locomotives (Rolling Stock)

This section contains information to meet the requirements of 49 C.F.R. § 236.1011(a)(6)(i) through (iii) related to the NSR locomotive units that will be equipped with PTC technology, the schedule to equip those units and specific goals for progressive implementation of PTC.

p. 29

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SE4.6.1NSRITIVE Locomotives SECURITY INFORMATION to Be Equipped (SSI) Norfolk Southern’s vice president Mechanical has the responsibility for equipping units for PTC. A team reporting to the vice president Network & Service Management is responsible for locomotive power assignment to the shops and then after installation, to the NS network, including PTC-required districts. The locomotive equipping plan was developed through a thorough analysis of the locomotive fleet assignments, fleet age and operating service plan to ensure a sufficient pool of locomotives for PTC operation.

NSR will equip units in each of its eight brake interface type categories, encompassing close to 20 different locomotive model types:

Table 5- Rolling Stock to Be Equipped

Units Brake Interface Units Brake Interface 236 Wabtec EPIC3102D2 1,848 NYAB CCB-2 107 Wabtec EPIC II 24 Wabtec EPIC II (Revision 24658) (Revision 24384) 53 Wabtec EPIC II 130 Wabtec FASTBRAKE (Revision 24603) 120 NYAB CCB-26 382 26L

NSR will equip the majority of the locomotive fleet for PTC, including both road locomotives and locomotives used primarily for local freight service. All new road locomotives will be PTC- equipped. As locomotive manufacturers become capable of supplying new units that are PTC- equipped and enabled from the factory, NSR will pursue this option to help achieve locomotive implementation goals. As locomotives are retired from the NSR fleet, they will be removed from implementation pool and other locomotives added to maintain the targeted number of PTC-equipped locomotives and the strategy for progressive implementation. The Mechanical Department is utilizing its locomotive shops at the following locations for installations:

. Birmingham Locomotive Shop . Shaffer’s Crossing (Roanoke) Locomotive Shop . Roanoke Locomotive Shop . Chattanooga Locomotive Shop . Conway Locomotive Shop . Enola Locomotive Shop

p. 30

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SENSR.ITIVE Bellevue SECURITY Locomotive INFORMATION Shop (SSI) . Elkhart Locomotive Shop . Juniata (Altoona) Locomotive Shop

Other smaller NSR facilities may be utilized as practical. Technical assistance and guidance will be provided by service personnel from the PTC equipment suppliers or other industry technical resources as required.

4.6.2 PTC Locomotive Installation Schedule & Progressive Implementation Locomotive equipping began in 2010 for NSR. Until 2015, units were partially equipped with PTC components. Beginning in 2015, fully equipped units rolled off the production line for use in field qualification testing, Revenue Service Demonstration and to prepare for deployment of PTC. NSR has developed a schedule that focuses heavily on progressive implementation by model types to focus unit modification on models most frequently utilized in road service.

As required by 49 C.F.R. § 236.1006(b)(1), NSR has developed specific goals for progressive implementation of onboard systems and deployment of PTC equipped locomotives such that the safety benefits of PTC are achieved through incremental growth in the percentage of controlling locomotives operating on PTC lines that are equipped with operative PTC onboard equipment. These goals are expressed as a percentage of trains equipped with I-ETMS operating on PTC lines, found in Table 6 - Locomotive Equipping and Percentage of NSR Trains as PTC Trains. This percentage represents the number of I-ETMS trains operated in revenue service on a PTC district divided by the total number of trains operated in revenue service across the entire NSR network. After December 31, 2020, not all NSR trains will be PTC trains, as PTC is not required on the entre NS network. These progressive implementation goals are based on a number of factors that include but are not limited to:

1. Number of districts in RSD or implemented in Revenue Service 2. Annual number of locomotive units to be equipped 3. Locomotive reliability, including units out of service for inspection or overhaul 4. Availability and/or assignment of locomotives to PTC districts and shared power agreements with other roads 5. Total number of train starts across the NSR system 6. Business traffic volumes and service demands

p. 31

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SENSRITIVE SECURITYTable INFORMATION 6 - Locomotive (SSI) Equipping and Percentage of NSR Trains as PTC Trains Locomotive Equipping & PTC Through EOY EOY EOY EOY EOY Trains 20151 2016 2017 2018 2019 2020 TMC Installs 1,959 2,079 2,310 2,900 Locomotive Radio Installs 730 1,175 2,038 2,900 Total Equipped Locomotives 375 1,175 2,038 2,900 PTC Trains as Percentage of 0% 3 - 8% 10 - 30 - 45 - 60 - Total NSR Trains 25% 45% 60% 75%

1 At the end of 2015, NSR had a large partially equipped fleet, which included TMCs on 1,959 units and locomotive radios on 730 units. Throughout 2015, as partially equipped units became fully equipped units, NSR reported fewer partially equipped units.

4.6.3 Reporting In accordance with the Positive Train Control Enforcement and Implementation Act of 2015, NSR shall, no later than March 31, 2016, and annually thereafter until NSR has completed implementation of the PTC system, submit to the Secretary a report on the progress toward implementing PTC, including—

A. The information on spectrum acquisition provided pursuant to 49 U.S.C. § 20157(a)(2)(A)(iii)(I); B. The totals provided pursuant to subclauses (III) and (V) of 49 U.S.C. § 20157(a)(2)(A)(iii), by territory, if applicable; C. The extent to which NSR is complying with the implementation schedule under 49 U.S.C. § 20157(a)(2)(A)(iii)(VII) or 49 U.S.C. § 20157(a)(2)(B); D. Any update to the information provided under 49 U.S.C. § 20157(a)(2)(A)(iii)(VI); E. The total number of route miles on which a PTC system has been initiated for revenue service demonstration or implemented, as compared to the total number of route miles required to have a PTC under subsection (a); and F. Any other information requested by the Secretary.

NSR’s Manager Advanced Train Control Regulatory Compliance & Training is responsible for compiling and submitting the required information to the FRA.

p. 32

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SE4.7NSR ITIVEWayside SECURITY Devices INFORMATION (SSI)

This section provides the information required by 49 C.F.R. § 236.1011(a)(7) for the number of wayside devices required for each track segment and the installation schedule to complete wayside equipment installation.

The wayside installation plan presents the greatest challenge to the implementation of PTC due to the sheer volume of work involved. Not only is the workload immense, but it is also dispersed across every mile of track required to be implemented, involving the work of various labor organizations, outside contractors and multiple suppliers. This work is affected by variable risks such as weather and equipment availability. To meet this enormous challenge, organizational structure has changed, detailed plans have been developed and reporting and control processes established.

4.7.1 Wayside Hardware to Be Installed

Norfolk Southern’s vice president Engineering has ownership of the wayside installation plan and corresponding metrics. The key wayside hardware includes WIUs, the Wayside Interface Unit, which interface to traditional signaling equipment and switch position monitors, which are technically WIUs, but installed on switch machines in unsignaled territory. The wayside also requires base station radios and towers or poles and wayside radios and towers or poles.

The wayside devices NSR must deploy are detailed in Appendix B NSR PTC Implementation Schedule, Sequence and Hardware Totals. This appendix provides the number per district of the wayside hardware required to implement PTC. Actual numbers may vary slightly based upon the unique characteristics and specific designs of locations. The NSR wireless engineering team has determined that the proposed placement of certain PTC wayside locations using the 220 MHz radios could potentially interfere with the reception of a base station if they are within .5 miles or less of the base site. It is very likely that many of these sites will be provisioned without a 220 radio due this potential interference problem, but the precise number will be determined by an engineered solution for every location. This issue will account for wayside radio and towers numbers installed having a variance of +/- 10 at 173 locations.

4.7.2 Wayside Installation Schedule The AVP Communication & Signal is responsible for setting the schedule for the wayside deployment. C&S Construction coordinates with the Signal and Engineering design team and

p. 33

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SEtheNSR ITIVEAdvanced SECURITY Train INFORMATION Control teams (SSI) for wayside and communications who plan, test and validate software for field deployment.

The wayside installation schedule is provided in Table 7 - Wayside Installation Schedule.

Table 7 - Wayside Installation Schedule

Wayside Installation Through EOY EOY EOY 20151 2016 2017 2018 Signaling WIU Installs 1,932 2,459 3,371 4,007 Switch Position Monitor WIU 34 56 150 150 Installs Wayside Radio Installs 1,908 2,269 2,847 3,259 Wayside Tower/Pole Installs 1,439 1,742 2,408 3,259 Base Station Radio Installs 311 351 381 411 Base Station Tower/Pole Installs 311 351 381 409

4.8 Mainline or Non-Mainline Track Identification NSR’s rail network is comprised of mainline and non-main line tracks. Main line is defined in 49 C.F.R. § 236.1003:

Main line means, except as provided in § 236.1019 regarding Mainline Track Exceptions or where all trains are limited to restricted speed within a yard or terminal area or on auxiliary or industry tracks, a segment or route of railroad tracks: (1) Of a Class I railroad, as documented in current timetables filed by the Class I railroad with the FRA under 49 C.F.R. § 217.7, over which 5,000,000 or more gross tons of railroad traffic is transported annually; or (2) Used for regularly scheduled intercity or commuter rail passenger service, as defined in 49 U.S.C. 24102, or both.

As required by § 236.1011(a)(8), NSR provides a list of track segment designation in Appendix C NSR PTC Track Segment Characteristics.

4.9 Basis for Determination that Risk-Based Prioritization Is Not Practical Because PTC is being implemented on an active railroad network with a myriad of factors affecting daily operation, NSR has determined that PTC implementation strictly based solely

p. 34

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SEuponNSRITIVE a quantifiable SECURITY INFORMATION risk methodology (SSI) is sometimes not practical. Consideration of factors in addition to quantifiable risk is required to maintain a plan that best utilizes NSR resources to maximize the benefit of PTC operations and ensure the earliest possible completion of PTC implementation. The basis for NSR’s determination includes but is not limited to the major categories or risk described in the following sections.

4.9.1 Resources Certain labor agreement provisions limit the types and locations of work to be performed by employees and contractors on NSR property. To minimize the schedule impact of those agreement restrictions, NSR entered into a special contract (“PTC Labor Agreement”) with a labor organization to allow work by contracted labor to proceed for PTC installation of wayside infrastructure. These agreements and limitations required work to be performed in certain locations and under a timeframe specified in the PTC Labor Agreement that did not always follow the sequencing based on the highest risk district first.

Additionally, due to the limitations of wayside design resources and wayside product readiness, certain methods of operation or territories were deferred until knowledgeable design resources or quality products became available.

Federal Communications Commission (FCC) resources, in conjunction with the Advisory Council on Historic Preservation, suspended the submittal and approval of PTC wayside towers in its Tower Construction Notification Service for approximately 12 months as the agency worked with industry stakeholders to develop a process that could support the massive influx of PTC wayside towers. At the conclusion of those discussions, the FCC published a Program Comment document requiring NSR to consult with SHPOs and THPOs (State and Tribal Historic Preservation Officers, respectively), prior to construction of the wayside tower sites. This process currently takes six to nine months to reach approval for wayside radio tower construction or the co-location of a new transmitter that involves use of an FCC licensed frequency. The GPS coordinates for PTC towers also must be established for the wayside. Because of the complexity of some locations and their connectivity with other railroads, or because of the lengthy hiatus on tower construction imposed by the FCC, completed mileage in a district may not have been contiguous or have adhered to the risk-based prioritization. NSR deployed its resources where it was able to keep the process moving once the FCC’s application process moratorium was lifted.

p. 35

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SE4.9.2NSRITIVE Location SECURITY Specifics INFORMATION (SSI) NSR also took into account factors regarding a location including, but not limited to, whether the location was part of a pilot test territory for field qualification testing, interoperability complexity, the state of existing infrastructure, key route/corridor continuity and impacts of natural disasters and harsh weather.

All methods of operation must be tested prior to implementation. Districts in each method of operation were selected for test, which may have changed their implementation sequence to account for this.

While some locations have high relative quantifiable risk, they are also interoperably complex locations, which require tremendous planning and coordination within NSR and with other roads. Interoperability complexity manifests itself in many ways including:

. Multiple-railroad complexity: NSR may interact with as few as one or as many as 12 railroads around a complex area; . Physical plant complexity, such as multiple terminals and adjoining terminals, possibly serving multiple railroads in a 35-mile radius that complicate PTC wayside and communications installation and coordinated train operations; . Traffic density complexity, found in the number of operating trains on a subdivision. Some locations have as many as 30 freight trains starts a day, many with upwards of 500 train starts a day, and Chicago has over 1,000 train starts a day. . Multiple crews operating trains for multiple hosts over NSR and other host/tenant roads.

Figure 2 - Interoperably Complex Major Terminal (City) Locations illustrates an industry view of interoperably complex terminal locations, the majority of which are included in the NSR implementation.

p. 36

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SENSRITIVE SECURITY INFORMATION (SSI)

Figure 2 - Interoperably Complex Major Terminal (City) Locations

The PTC installation effort on any district is also affected by the state of the existing wayside infrastructure. In particular, the presence of color light, color position, searchlight signals, EC2 and older relay-based signal systems on a district increase the scope of the installation effort. These older systems cannot sufficiently be upgraded to “speak PTC,” so a total replacement is required. This effort, combined with the previously mentioned labor and tower installation constraints, also affected the sequencing of wayside implementation, at times contrary to the highest risk districts first methodology.

Norfolk Southern invests in corridor initiatives to provide superior service to its customers. Increasing freight capacity and aligning key routes improves transit times and helps keep the national economy competitive. Multiple districts make up these key routes and corridors. Implementation of PTC along these routes may be grouped together to completely implement a key route or corridor. When feasible, NSR will deploy PTC to districts with higher risk levels first along those routes and proceed to districts of lesser risk.

Finally, when all planning is complete, implementation sequencing may be altered due to fires, floods, hurricanes, earthquakes or similar calamity. When harsh winter weather like that which was experienced in the winter of 2014 occurs, NSR is forced to alter its plan to work where it is practicable. Summer floods, tornadoes and hurricanes have the same effect. Lake effect snows p. 37

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SEofNSR twoITIVE to SECURITY six feet, INFORMATION snow and ice (SSI) across the southeast with downed power lines and closed roads, flooding in the south that washed out roads, bridges, overpasses and track structure all take a toll on NSR resources working to keep the infrastructure of the railroad safe and operational and the PTC installation schedule. A prime example occurred in the summer of 2015, when NSR field qualification testing and training on the South Carolina pilot territories was impeded by a catastrophic flooding event.

4.10 Additional Requirements for Class I Railroads NSR has not changed its view on this subject since the 2010 PTCIP. NSR is implementing PTC as required by the Act. The NSR strategy for identifying additional line segments not already specified in this Plan for PTC deployment is to monitor and evaluate rail traffic using the methodology described herein for safety risk to railroad employees and the public that PTC will eliminate. NS will evaluate segment characteristics annually to identify any additional PTC deployment scope and will make amendments to this Plan in conformance with the applicable regulatory process. For a more in-depth discussion, refer to the NSR PTCIP v 1.3 Section 12.

p. 38

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SE5NSR ITIVEOther SECURITY Requirements INFORMATION (SSI) of the Positive Train Control Enforcement and Implementation Act of 2015

5.1 Spectrum Acquisition Schedule NSR is a member of PTC-220, owned equally by each of the seven Class I railroads including NSR. PTC-220 holds nationwide and regionally licensed FCC spectrum for PTC implementation in the 220-222 MHz spectrum band. Access to this spectrum for NSR and each of the PTC-220 owner-members, and for non-members, is provided by a spectrum lease. NSR will utilize spectrum planning tools provided by PTC-220 that will enable NSR to coordinate its spectrum usage with other railroads to ensure adequate availability and interference mitigation in areas of overlapping operation.

PTC-220 and its member-owners, including NSR, believe that the licenses that PTC-220 currently holds provide spectrum sufficient for nationwide PTC implementation. To further assure interoperability and spectral separation to mitigate potential interference in certain regions of the country, PTC-220 is also acquiring additional [217 and/or 218 MHz] licenses that it expects to finalize and transfer to the commuter agencies upon FCC authorization to operate in 2016.

Table 8 - NSR PTC Spectrum Acquisition Schedule

Spectrum Location Year Acquired Year Available for Use Nationwide 2008 2008 Chicago, IL 2013 2013 Philadelphia, PA 2016 2016 New Jersey Regulatory Review 2016 Expect 2016

5.2 Hardware Amounts by Category and Schedule for Installation Table 9 - PTC Required Hardware Totals and Implementation Schedule summarizes the total amount of PTC system hardware that will be installed by the end of each calendar year until the PTC system is implemented, with totals separated by each hardware category.

The PTC-required hardware includes the locomotive apparatus (locomotive train management computer, “TMC”), a wayside interface unit (including any associated legacy signal system replacements), a switch position monitor (also WIU), physical back office system equipment, a base station radio, a wayside radio, a locomotive radio, or a communication tower or pole. p. 39

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SENSRITIVE SECURITY TableINFORMATION 9 - PTC Required (SSI) Hardware Totals and Implementation Schedule Through EOY EOY EOY PTC Required Hardware 2015 2016 2017 2018 Locomotive Train Management Computer (TMC) 1,959 2,079 2,310 2,900 Installs Locomotive Radio Installs 730 1,175 2,038 2,900 Wayside Signaling WIU Installs 1,932 2,459 3,371 4,007 Wayside Switch Position Monitoring WIU Installs 34 56 150 150 Wayside Radio Installs 1,908 2,269 2,847 3,259 Wayside Tower/Pole Installs 1,439 1,742 2,408 3,259 Base Station Radio Installs 311 351 381 411 Base Station Tower/Pole Installs 311 351 381 409 Back Office Hardware: NSR Back Office Servers, Completed Dispatching Servers and PTC Message Router Servers

5.3 Number of and Schedule for Employee Training NSR will provide PTC training to locomotive engineers and conductors, train dispatchers, back office support personnel, field maintenance personnel, and front line supervisors, as required. This effort involves over 60% of the company’s active employees. Employee training and qualification to perform assigned duties properly and safely are crucial to maintaining safe railroad equipment and a safe workplace.

PTC system related training will be conducted in accordance with 49 C.F.R. §§ 236.1041 through 236.1049. Training for PTC will be fully described in the NSR PTCSP. I-ETMS training is required for the following active and designated trainee employee groups as per § 236.1041:

Persons who operate trains or serve as a train or engine crew member, subject to instruction and testing, on a train operating in territory where I-ETMS is in use; Persons who work as “office control personnel” who dispatch train operations (issue or communicate any mandatory directive that is executed or enforced, or is intended to be executed or enforced, by I-ETMS); Persons whose duties include installing, maintaining, repairing, modifying, inspecting, and testing safety critical components of the PTC system:

p. 40

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SENSRITIVERoadway SECURITY workers INFORMATION whose (SSI) duties require them to know and understand how a train control system affects their safety and how to avoid interfering with its proper functioning; and The direct supervisors of persons listed above, as applicable based upon their duties and responsibilities.

Training is being conducted by each of the departments involved in PTC implementation: Transportation, Dispatch, Mechanical, Engineering, and Information Technology. Each has developed a training program and plan that encompasses the required elements to ensure NSR employees have the training they need to perform assigned duties properly and safely. A summary of the total number of employees to be trained by end of year each year is provided in Table 10- Employee PTC Training and Schedule.

The number of employees required to be trained for PTC will fluctuate over time as attrition, organizational changes, employee movement and promotion and other factors affect each department’s population.

Table 10- Employee PTC Training and Schedule

Employee Through EOY EOY EOY EOY EOY Total To Be Training Category 2015 2016 2017 2018 20191 20201 Trained

Cumulative Total 4,627 7,370 10,778 15,048 18,041 21,446 21,446

Annual Total 4,627 2,743 3,408 4,270 2,993 3,405 21,446

Transportation 53 642 2,431 3,322 2,727 3,276 12,451

Train Dispatching 20 80 80 110 80 - 370

Engineering & Roadway Worker 3,872 886 442 540 - - 5,740

Mechanical 485 435 270 - - - 1,190 Information Technology 20 - - - - - 20

Supervisors 177 700 185 298 186 129 1,675

p. 41

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SE5.4NSR ITIVESummary SECURITY ofINFORMATION Remaining (SSI) Technical, Programmatic, Operational or Other Challenges This section provides a summary of the major challenges or risks NSR foresees to maintaining its planned PTC implementation schedule.

5.4.1 Challenges to Locomotive Implementation 5.4.1.1 Harsh Weather Extreme weather conditions (e.g., prolonged subfreezing temperatures, high heat events) can slow planned installations as more units are taken out of service for repair. The resulting increase in locomotive failures consumes resources otherwise allocated to PTC installation.

5.4.1.2 Variance in Locomotive Model Design Configurations Locomotives vary in design not only between make and model, but also between delivery years and even batches within the same year. The result is variation in both software and hardware. For each locomotive variant, specialized designs and software integration must be specified to account for differences in wiring, terminal board arrangements, circuit breaker configurations, and subsystem interfaces. This makes PTC installation standardization challenging. Each difference has to be acknowledged and a determination made how to handle for design and installation. I-ETMS readiness requires updates to electronic airbrake systems and validation with legacy cab signal systems, like Ultra-Cab II and Ultra-Cab I. Each of these integrations is tedious, requiring rigorous testing to ensure proper system operation prior to writing the detailed modification instructions to insure proper installation. The magnitude of the variation in design or any resultant issues can cause delay in the implementation schedule.

5.4.1.3 New Hardware Required for PTC and Product Immaturity New required hardware or hardware to enhance reliability of PTC must be developed and integrated with PTC systems and qualified for service on the many different models of locomotives. The immaturity of these products and their interfaces to the different locomotive models has and continues to create delays in installations of stable products for fully equipped units. PTC serviceability and reliability is dependent on healthy sub-parts such as the TMC, PTC radio, Locomotive Interface Gateway and CHMM, which are new systems built specifically for PTC. Defects and malfunctions require recall or replacement programs. These recall and replacement cycles are time consuming in the detection of issues and cause delay and rework for installations.

p. 42

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SE5.4.1.4NSRITIVE RadioSECURITY Hardware INFORMATION Failures (SSI) Railroad technical staff have recently identified several incidents of premature failure with some of the PTC radios. The issue appears to be related to one manufacturer of the Meteorcomm design and affects both the base station and locomotive radios. The impact of the failure causes the radio to stop transmitting. The cause is not yet known, but could be due to deficiencies in the manufacturing process, component failure or a combination of the two. While the root cause and scope of the issue is expected be determined in early 2016, the effect on the schedule and requirement to replace locomotive radios is not yet known.

5.4.1.5 Vendor Product Releases Each new PTC subsystem (Train Management Computer (TMC), PTC Radio, Crash-hardened Memory Module (CHMM), etc.) release requires special configuration tools, instructions and training.

5.4.1.6 Additional Regulatory Requirements for Locomotive Hardware In the event the FRA enacts any regulation requiring additional locomotive hardware be installed prior to December 31, 2018, it would conflict with goals to complete PTC installations and severely constrain NSR Mechanical resources.

5.4.2 Challenges to Wayside Implementation 5.4.2.1 Wayside Software and Hardware Immaturity The software and hardware required for reliable WIU operation has not reached the same maturity level that is typical of other wayside logic controllers. This manifests itself in vendors or railroads identifying occasional defects or issues that then require new versions. After Verification & Validation of new versions of wayside software or hardware, the product must be deployed to all locations that have already been PTC equipped. This is exceptionally problematic later in deployment since more locations must be visited. Additionally, it is possible in some cases that a change in software could result in a need to repeat validation of the wayside location and the track database SUBDIV file.

5.4.2.2 Labor Resources Labor resources available to perform PTC work are constrained in some areas due to large ongoing public projects such as the Indiana Gateway Project and the Piedmont Improvement Projects, which, when completed, will enhance passenger operations in these areas. There are also several active Virginia projects to expand Amtrak service to Roanoke, Va. The industry is also challenged with the largest C&S attrition rate in history. Training a new generation of signalman and supervisors adds to the challenges of the project. p. 43

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SE5.4.2.3NSRITIVE InteroperabilitySECURITY INFORMATION Coordination (SSI) for Communications Completion of a significant number of locations is dependent upon a foreign railroad’s cooperation. Diamond locations and jointly operated interlockings where the different railroads use different signal aspects present challenges. The differences require agreement as to how to equip the location and coordination of engineering. In many cases, jointly planned cutovers of new equipment require field forces from both railroads to be present when the location is placed in service for PTC.

5.4.2.4 Interoperability Complexity Many of the remaining NS lines that require PTC have high volume traffic levels and require much coordination with not only the cut ins, but the construction work as well. Minimal track time is available for cut-ins on an operating railroad. Updates, green fielding, to the older signal systems to modern technology requires more resources and time to install and test. While these factors are considered in the scheduling of a segment or location, estimates and actual duration may vary based on issues or complexity not accounted for.

5.4.2.5 Radio Hardware Failures Railroad technical staff have recently identified several incidents of premature failure with some of the PTC radios. The issue appears to be related to one manufacturer of the Meteorcomm design and affects the base station radios. To date, the problem has not been observed in the wayside radios. The impact of the failure causes the radio to stop transmitting. The cause is not yet know but could be due to deficiencies in the manufacturing process, component failure or a combination of the two. While the root cause and scope of the issue is expected be determined in early 2016, the effect on the schedule and requirement to replace base station radios is not yet known.

5.4.2.6 Cooperation with FCC on Tower Approval Process Timely approval of PTC tower approvals are an important part of staying on schedule and progressing PTC as planned. Delays associated with getting only partial tower approvals affect our ability to construct towers on entire line segments end to end. The delays from lagging approvals which force revisiting locations to install towers creates schedule delay and affects other work in the Plan.

5.4.2.7 Harsh Weather Weather will be a key factor in progressing work on the Northern Territories over the next three years. There is a significant amount of work to complete PTC in this region and severe

p. 44

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SEwinterNSRITIVE weather SECURITY would INFORMATION impede the (SSI) progress of PTC. Flooding, tornadoes and hurricanes also negatively affect PTC Construction.

5.4.3 Challenges to Interoperability 5.4.3.1 Tenant Locomotive Equipping NSR requires certain tenants operating in PTC required territory to equip for PTC operation. Several tenants refuse to equip their locomotives, claiming NSR cannot require them to equip where the short line exception set forth in 49 CFR § 236.1006(b)((4) applies. These issues are referenced in 4.3.3.2. One road is planning to install a system other than I-ETMS, which has not yet received FRA Type Approval. NS has concerns this could present a major challenge for the shortline tenant to meet NSR’s interoperability terms and conditions for operation on a PTC mainline.

5.4.3.2 Software Enhancement Governance Although there is an industry committee aligned to provide structure and processes around governance and configuration management of PTC software versioning, the implementation of that plan will be challenging, particularly when other suppliers enter the market with additional Type Approved systems.

5.4.3.3 Interoperability Coordination for Communications See the Wayside challenges for a full description.

5.4.3.4 NS as Tenant on Northeast Corridor Technical challenges persist in achieving interoperability on the Northeast Corridor. Although NSR expects to overcome these challenges with cooperation with Amtrak, the scope of potential challenges and duration of delays is as of yet unknown.

5.4.4 Challenges to Testing, Demonstration, Certification and Progressive Implementation 5.4.4.1 PTC Software Immaturity – PTC Does Not Perform as Intended Each implementing railroad has certain nuances about its operation that the PTC software requirements may not have taken into account. These potential deficits in requirements or design would require design, programming, testing and re-versioning of software for deployment. This development and verification and validation effort could severely affect NSR’s ability to maintain its implementation schedule, depending on the scope of the programmatic changes required of the onboard, back office or dispatch suppliers.

p. 45

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SE5.4.4.2NSRITIVE DefectsSECURITY Are INFORMATION Found During (SSI) Revenue Service Demonstration, or RSD If severity 1 and severity 2 issues continue to be detected by NSR or any other I-ETMS implementing railroad, the schedule will be negatively impacted by the required programming changes, as described above. As a condition of FRA’s approval to run in RSD, if a severity 1 or severity 2 defect is detected, the phase of RSD must be re-started and re-run until the software is found to be defect free. For busy districts with many trains, this could impose a severe cost to the NSR schedule.

5.4.4.3 Final Defect Free Product NSR believes that until a defect-free PTC System product is achieved, delays in implementation will be realized through required software changes, testing efforts, re-training, hardware replacement and software re-deployment. Depending upon the scope of the issues, the scope of the changes required and resultant delay cannot be estimated.

5.4.4.4 Scalability of the PTC System Due to the impracticality and risk of testing in a production environment, NSR performs testing in a scaled-down environment. It is unlikely that testing will identify performance and reliability concerns beyond the capacity of this environment. As implementation progresses, the production environment may reveal issues related to system design and hardware adequacy that would require design, programming, testing and re-versioning of software and hardware for deployment. This potential development and deployment effort would negatively affect NSR’s ability to maintain its implementation schedule.

5.4.4.5 Potential Increase in Scope of Functionality NSR has concerns that any increase in the scope of PTC functionality beyond the defined system described by the PTCDP v3.1 Type Approval FRA-TA-2011-2C, would severely impede NSR’s ability to meet the planned implementation completion date before December 31, 2020. Scope changes require resources, programming and verification, re-training and deployment of software changes, etc.

5.4.4.6 FRA Certification Requirements NSR has concerns that the extent of the effort required for conditions of PTC system certification may cause schedule delay, depending upon the scope of those FRA conditions.

p. 46

Docket FRA - 2010-0060 Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0

SE5.5NSR ITIVESchedule SECURITY and INFORMATION Sequence (SSI) for Implementing PTC by the Positive Train Control Enforcement and Implementation Act of 2015 Deadline The sequence and schedule for NS to complete its PTC implementation as soon as possible and prior to December 31, 2020 is provided in Appendix B NSR PTC Implementation Schedule, Sequence and Hardware Totals. Until the system is certified by FRA for revenue service operation across NSR’s network, implementation dates represent either the date NSR enters Revenue Service Demonstration or Extended Revenue Service Demonstration. Following FRA certification of the PTC system for operation on NSR, the implementation date represents when the district will be fully implemented.

p. 47

NORFOLK SOUTHERN RAILWAY COMPANY Revised Positive Train Control Implementation Plan Version R1.0 Appendix A: NSR PTC Implementation Summary Metrics Public

PTC Docket: FRA-2010-0060

This document is an appendix to the revised PTC Implementation Plan for the Norfolk Southern Railway Company. It is submitted to the Federal Railroad Administration as required by the Positive Train Control Enforcement and Implementation Act of 2015, Public Law 114-73.

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix A: NSR PTC Implementation Summary Metrics

REVISION HISTORY

Date Version Description Author Appendix provides a summary of the key NSR PTC implementation metrics required by the Positive Train Control Enforcement 27 January 2016 R1.0 and Implementation Act of 2015. NSR- L. Wilson

p. ii

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix A: NSR PTC Implementation Summary Metrics

TABLE OF CONTENTS

Appendix A NSR PTC Implementation Summary Metrics ...... 1

p. iii

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix A: NSR PTC Implementation Summary Metrics

Appendix A NSR PTC Implementation Summary Metrics

This document provides a summary of the key metrics required by the Positive Train Control Enforcement and Implementation Act of 2015 as discussed in the PTCIP. The table provides the following cumulative totals by year:

. Number of line segments implemented . PTC trains as a percentage of total NSR trains . Employees trained . Number of Wayside Interface Units installed for legacy signal systems . Number of Wayside Interface Units installed for switch position monitoring . Number of wayside radios installed . Number of wayside towers or poles installed . Number of base station towers or poles installed . Number of base station radios installed . Number of Locomotive TMCs installed . Number of Locomotive radios installed . Office hardware installed . Spectrum acquisition by location and availability for use

Actual final numbers may vary slightly due to specific design, employment or organizational changes or interoperability factors affecting implementation.

p. 1

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix A: NSR PTC Implementation Summary Metrics

Table 1 - Summary of NSR PTC Implementation Requirements

Thru EOY EOY EOY EOY EOY 2015 2016 2017 2018 2019 2020 Total Route Miles 8,028 Line Segments 0 9 27-31 66-70 104-106 132 132 PTC Trains as a Percentage 0% 3 - 8% 10 -25% 30 - 45% 45 - 60% 60 -75% 60-75% of Total NSR Trains Employees Trained 4,627 7,370 10,778 15,048 18,041 21,446 21,446 Wayside Signal WIUs 1,932 2,459 3,371 4,007 4,007 Wayside Switch Monitor 34 56 150 150 150 WIUs Wayside Radios 1,908 2,269 2,847 3,259 3,259 Wayside Towers/Poles 1,439 1,742 2,408 3,259 3,259 Base Station Towers/Poles 311 351 381 409 409 Base Station Radios 311 351 381 411 411 Locomotive TMCs 1,959 2,079 2,310 2,900 2,900 Locomotive Radios 730 1,175 2,038 2,900 2,900 Office Hardware Done

Spectrum Location Year Acquired Year Available for Use Nationwide 2008 2008 Chicago, IL 2013 2013 Philadelphia, PA 2016 2016 New Jersey Regulatory Review 2016 Expect 2016

p. 2

NORFOLK SOUTHERN RAILWAY COMPANY Revised Positive Train Control Implementation Plan Version R1.0 Appendix B: NSR PTC Implementation Schedule, Sequence and Hardware Totals Public

PTC Docket: FRA-2010-0060

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix B: NSR PTC Implementation Schedule, Sequence & Hardware

Totals

REVISION HISTORY

Date Version Description Author Appendix provides the NSR PTC alternative schedule, sequence and hardware showing completion of a majority of PTC territories by 12/31/2018 and total implementation 27 January 2016 R1.0 completed by 12/31/2020. NSR- L. Wilson

p. ii

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix B: NSR PTC Implementation Schedule, Sequence & Hardware Totals

TABLE OF CONTENTS

Appendix B NSR PTC Schedule, Sequence and Hardware ...... 1

p. iii

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix B: NSR PTC Implementation Schedule, Sequence & Hardware Totals

Appendix B NSR PTC Schedule, Sequence and Hardware

This document provides the data related to the NSR PTC implementation alternative schedule, sequence and hardware totals as discussed in Sections 4.5, 4.72 and 5.2 of the PTCIP. The table provides the following:

. Year PTC implementation will be achieved . Implementation phase, by half year designation . Sequence of implementation . Line ID . District name . From-to station names for the district . Start (from) milepost and end (to) milepost . Number of miles . WIU Installation schedule, by year . Number of Wayside Interface Units for legacy signal systems . Number of Wayside Interface Units for switch position monitoring . Number of wayside towers or poles . Number of wayside radios . Number of base station towers or poles . Number of base station radios

Actual final numbers may vary slightly due to specific design or interoperability factors affecting implementation.

p. 1

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix B: NSR PTC Implementation Schedule, Sequence and Hardware

SENSRITIVE SECURITY INFORMATION (SSI) Table 1- NSR PTC Implementation Schedule, Sequence & Hardware Totals Base Switch Wayside Station Base Implementation From To Signal Monitor Towers Wayside Towers or Station YEAR Complete Date Sequence Line ID District From-To MP MP Miles WIUs WIUs or Poles Radios Poles Radios 2016 1H 2016 1 03 R COLUMBIA CHARLOTTE JCT. - AUGUSTA (Charlotte-Columbia) 0.0 110.4 110.4 47 44 44 4 4 2016 1H 2016 1 03SC CHARLESTON CHARLESTON - COLUMBIA 9.5 128.0 118.5 0 34 34 34 7 7 2016 2H 2016 2 07 A Knoxville BRISTOL-KNOXVILLE 0.0 125.0 125.0 56 51 51 5 5 2016 2H 2016 2 07 A Knoxville KNOXVILLE-OOLTEWAH 125.0 226.6 101.6 55 52 52 6 6 2016 2H 2016 2 08 AGS CHATTANOOGA - MERIDIAN 0.0 295.4 295.4 139 126 126 16 16 2016 2H 2016 2 08 A MEMPHIS STEVENSON - NORALA 279.8 401.1 121.3 53 51 51 7 7 2016 2H 2016 2 08 A MEMPHIS TUSCUMBIA - MEMPHIS 402.3 545.0 142.7 58 59 59 6 6 2016 2H 2016 2 08 MF MEMPHIS TUSCUMBIA - SHEFFIELD 0.3 3.6 3.3 3 2 2 2016 2H 2016 2 08NA WEST END SHEFFIELD - PARRISH 1.7 3.7 2.0 11 4 4 2017 1H 2017 3 03 WASH/DANV/CHAR/GRVL (Greenville) A. F. TOWER - FOREMOST (Greenville-Inman) 485.0 630.9 145.9 78 61 61 7 7 2017 1H 2017 3 04 NORCROSS FOREMOST - HOWELL 630.9 635.2 4.3 3 3 3 2017 1H 2017 3 04 A ATLANTA NORTH OOLTEWAH - JERSEY 226.7 235.1 8.4 5 4 4 2017 1H 2017 3 04 H ATLANTA NORTH OOLTEWAH - ATLANTA 15.1 149.7 134.6 65 57 57 7 7 2017 1H 2017 3 08 EAST END AUSTELL - BIRMINGHAM 650.0 798.4 148.4 65 60 60 7 7 2017 1H 2017 3 08 A NEW ORLEANS SHREWSBURY - EAST CITY SWITCH 0.0 3.5 3.5 2 2 2 2017 1H 2017 3 08 NT NEW ORLEANS BASIN STREET - PT. CHALMETTE 2.5 8.1 5.6 5 5 5 2017 1H 2017 3 08NO NO&NE MERIDIAN - NEW ORLEANS 0.4 195.9 195.6 89 82 82 10 10 2017 2H 2017 4 03 WASH/DANV/CHAR/GRVL (Charlotte) A. F. TOWER - FOREMOST (Salisbury-Greenville) 334.0 485.0 151.0 92 76 76 8 8 2017 2H 2017 4 03 WASH/DANV/CHAR/GRVL (Danville) A. F. TOWER - FOREMOST (Montview-Salisbury) 175.0 334.0 159.0 96 64 64 9 9 2017 2H 2017 4 03 H DANVILLE/ECBU GREENSBORO - GOLDSBORO 0.0 110.5 110.5 59 5 51 51 8 8 2017 2H 2017 4 03 S ASHEVILLE SALISBURY - MURPHY JCT. (Columbia-Beaumont) 0.0 25.6 25.6 66 12 12 2 2 2017 2H 2017 4 03AC DANVILLE HURT CONNECTION 197.0 198.8 1.8 0 2017 2H 2017 4 04 H ATLANTA SOUTH ATLANTA - NORTH MACON 149.7 239.2 89.5 47 41 41 4 4 2017 2H 2017 4 04 H BRUNSWICK NORTH MACON - BRUNSWICK 239.2 242.1 2.9 1 2017 2H 2017 4 04 S GRIFFIN MACON - ATLANTA 288.2 294.5 6.3 4 4 4 2017 2H 2017 4 07 W LOUISVILLE LOUISVILLE-DANVILLE 268.3 268.9 0.6 2 2 2 2017 2H 2017 4 07 W LOUISVILLE LOUISVILLE-DANVILLE 274.9 357.7 82.8 43 38 38 3 3 2017 2H 2017 4 08 WEST END BIRMINGHAM - BERRY 798.4 798.8 0.4 3 3 3 2017 2H 2017 4 55 V ALTAVISTA ABILENE - ROANOKE 200.3 243.1 42.8 18 18 18 2017 2H 2017 4 92 B CLEVELAND BAY VILLAGE - BELLEVUE 222.6 248.1 25.5 16 16 16 0 0 2017 2H 2017 4 92 B FOSTORIA BELLEVUE - FORT WAYNE 248.1 367.8 119.7 59 55 55 4 4 2018 1H 2018 6 03 KM WASHINGTON MONTVIEW - KINNEY CONN. 0.0 1.2 1.2 2 1 1 p. 2

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix B: NSR PTC Implementation Schedule, Sequence and Hardware

SENSRITIVE SECURITY INFORMATION (SSI) Base Switch Wayside Station Base Implementation From To Signal Monitor Towers Wayside Towers or Station YEAR Complete Date Sequence Line ID District From-To MP MP Miles WIUs WIUs or Poles Radios Poles Radios 2018 1H 2018 6 04 D AUGUSTA MILLEN - AUGUSTA 78.7 120.5 41.8 7 6 6 2 2 2018 1H 2018 6 04 D AUGUSTA NIXON - AUGUSTA 125.0 129.0 4.0 5 5 5 2018 1H 2018 6 04 S SAVANNAH ARDMORE - MACON 78.5 134.0 55.5 9 7 7 5 5 2018 1H 2018 6 04 S SAVANNAH ARDMORE - MACON 137.0 190.4 53.4 9 10 18 18 2018 1H 2018 6 04GH ALBANY CGA JCT. - RUTLAND JCT. 0.0 0.6 0.6 2018 1H 2018 5 55HW HAGERSTOWN SEC. (Lurgan) HAGERSTOWN (CP TOWN) 73.7 74.8 1.1 2018 1H 2018 5 62 N KENOVA KENOVA - PORTSMOUTH 567.9 608.5 40.6 22 17 17 1 1 2018 1H 2018 5 62 N KENOVA WILLIAMSON - NAUGATUCK 470.0 484.3 14.3 7 5 5 2018 1H 2018 5 72HW HAGERSTOWN SEC. SHIPPENSBURG-CP TOWN 40.0 73.7 33.7 16 15 15 3 3 2018 1H 2018 5 72LG LURGAN BR. CAPITAL-LURGAN 0.0 40.0 40.0 19 17 17 2018 1H 2018 5 92 S SANDUSKY COLUMBUS - SANDUSKY 1.0 111.4 110.4 50 38 38 4 4 2018 1H 2018 6 92MP MARION GOSHEN - ANDERSON 0.0 58.5 58.5 32 7 23 23 1 1 2018 1H 2018 6 94 W SOUTHERN EAST PRINCETON - LOUISVILLE 162.8 268.3 105.5 44 43 43 5 5 WASH/DANV/CHAR/GRVL 2018 2H 2018 6 03 (Washington) A. F. TOWER - FOREMOST (Alexandria-Montview) 8.0 175.0 167.0 95 68 68 10 10 2018 2H 2018 6 03 B WASHINGTON MANASSAS - EDINBURG 0.0 50.9 50.9 18 18 18 2 2 2018 2H 2018 6 04 G MACON/VALDOSTA VALDOSTA-JACKSONVILLE 152.0 254.5 102.5 44 41 41 2018 2H 2018 6 07 CNO&TP (CNO&TP-Third) OAKDALE-CHATTANOOGA 254.0 334.0 80.0 45 41 41 7 7 2018 2H 2018 6 07CJ CINCINNATI LINE SHARONVILLE-IVORYDALE JCT. 245.4 255.1 9.7 7 4 4 2018 2H 2018 6 55 N CHRISTIANSBURG ROANOKE - WALTON 257.4 297.6 40.2 30 20 20 2 2 2018 2H 2018 6 55 N CHRISTIANSBURG WALTON - EAST BLUEFIELD 301.9 360.3 58.5 32 25 25 2 2 2018 2H 2018 6 62 N POCAHONTAS DISTRICT BLUEFIELD - WILLIAMSON 360.3 470.0 109.7 76 68 68 6 6 2018 2H 2018 6 62NA KENOVA NAUGATUCK -KENOVA 0.0 59.1 59.1 39 26 26 4 4 2018 2H 2018 6 72AF READING/HARRISBURG LINE CP BELT-CP TITUS 5.4 13.0 7.6 7 5 5 2018 2H 2018 6 72EN READING LINE BETHLEHAM-CP BURN 88.6 93.0 4.4 1 2018 2H 2018 6 72FR POTTSVILLE BR. READING-CP BELT 58.6 61.2 2.6 1 1 1 2018 2H 2018 6 72RV READING LINE CP BLANDON-ALLENTOWN 7.5 36.3 28.8 18 15 15 2 2 2018 2H 2018 6 72TK READING LINE CP BLANDON-CP BELT 0.0 5.4 5.4 3 3 3 2018 2H 2018 6 72TW READING LINE CP TULP-WYOMISSING JCT 8.1 9.4 1.3 1 1 1 2018 2H 2018 6 74 B LAKE ERIE DISTRICT BUFFALO-EUCLID 6.5 172.0 165.5 71 72 72 6 6 2018 2H 2018 6 76 D DETROIT DETROIT - MONTPELIER 4.5 116.0 111.5 47 44 44 4 4 2018 2H 2018 6 92 D HUNTINGTON MONTPELIER - PERU 116.0 204.5 88.5 41 39 39 4 4 2018 2H 2018 6 92 N COLUMBUS VERA - COLUMBUS 608.5 704.6 96.1 62 40 40 4 4

p. 3

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix B: NSR PTC Implementation Schedule, Sequence and Hardware

SENSRITIVE SECURITY INFORMATION (SSI) Base Switch Wayside Station Base Implementation From To Signal Monitor Towers Wayside Towers or Station YEAR Complete Date Sequence Line ID District From-To MP MP Miles WIUs WIUs or Poles Radios Poles Radios 2018 2H 2018 6 92AM WESTERN BRANCH SCIOTO - BANNON 132.1 137.6 5.5 2 1 1 0 0 2018 2H 2018 6 92CJ DAYTON WEBER - SHARONVILLE 134.4 245.4 111.0 57 45 45 4 4 2018 2H 2018 6 94 W SOUTHERN WEST ST. LOUIS - PRINCETON 4.7 162.8 158.1 72 64 64 9 9 2018 2H 2018 6 94 D BROOKLYN MOSSER - E. ST. LOUIS 376.5 480.4 103.9 40 36 36 5 5 2018 2H 2018 6 94 D LAFAYETTE PERU - MOSSER 204.5 376.5 172.0 78 66 66 7 7 2018 2H 2018 6 94DH SPRINGFIELD MOSSER - HANNIBAL 376.5 466.0 89.5 61 48 48 3 3 2019 1H 2019 7 03 R COLUMBIA CHARLOTTE JCT. - AUGUSTA (Columbia-Augusta) 112.0 190.5 78.5 40 31 31 4 4 2019 1H 2019 7 03 W COLUMBIA SPARTANBURG - COLUMBIA 67.7 75.5 7.8 0 11 3 3 4 4 2019 1H 2019 7 04 G MACON/VALDOSTA MACON-VALDOSTA 0.0 152.0 152.0 75 65 65 13 13 2019 1H 2019 7 04 H ALBANY RUTLAND JCT. - SMITHVILLE 197.0 219.6 22.6 10 11 11 1 1 2019 1H 2019 7 08 MB 3B SOUTH MARION JCT - MOBILE 0 143.2 143.2 48 38 38 8 8 2019 1H 2019 7 08 MB 3B SOUTH MARION JCT - MOBILE 145.5 148 2.5 2019 1H 2019 7 08 N 3B NORTH WILTON - SOUTH SELMA 139.3 192.4 53.1 10 8 8 3 3 2019 1H 2019 7 08 N 3B SOUTH SOUTH SELMA - MARION JCT. 192.4 206.6 14.2 2 2 2 2019 1H 2019 7 08 R 3B NORTH WILTON - BURSTALL 0.0 35.0 35.0 10 9 9 1 1 2019 1H 2019 7 92 T TOLEDO IRONVILLE-YEOMANS 24.6 53.1 28.6 2 14 14 1 1 2019 2H 2019 8 55 B BLUE RIDGE BURKEVILLE - PAMPLIN 0.0 36.9 36.9 13 13 13 2 2 2019 2H 2019 8 55 H HAGERSTOWN HAGERSTOWN - SHENANDOAH 0.6 59.1 58.4 45 25 25 5 5 2019 2H 2019 8 55 N BLUE RIDGE CREWE - BURKEVILLE 128.9 133.4 4.5 5 4 4 2019 2H 2019 8 55 N BLUE RIDGE FOREST - ROANOKE 214.5 257.4 42.9 21 18 18 2 2 2019 2H 2019 8 55 N BLUE RIDGE PAMPLIN - CONCORD 169.1 189.9 20.8 7 6 6 1 1 2019 2H 2019 8 55 N NORFOLK BRIDGE 5 - POE 1.2 77.8 76.6 53 33 33 4 4 2019 2H 2019 8 55 N NORFOLK JACK - CREWE 88.3 128.9 40.6 11 11 11 2 2 2019 2H 2019 8 55 P NORFOLK POE - JACK 0.0 4.2 4.2 6 5 5 2019 2H 2019 8 55BC WINSTON-SALEM JUNCTION - DUKE POWER 0.0 4.1 4.1 2019 2H 2019 8 55LP NORFOLK LAMBERTS POINT - BRIDGE 5 0.0 5.1 5.1 4 4 4 2019 2H 2019 8 55NB PULASKI WALTON - BRISTOL 297.6 408.4 110.8 47 46 46 6 6 2019 2H 2019 8 55PH BLUE RIDGE CONCORD - FOREST 0.0 22.4 22.4 11 11 11 2019 2H 2019 8 55VC BLUE RIDGE VINTON - DEMUTH 0.0 1.5 1.5 2019 2H 2019 8 72 B LAKE ERIE DISTRICT BUFFALO-BLASDELL 2.0 6.5 4.5 4 4 4 2019 2H 2019 8 72FK DELMARVA SEC. DAVIS-PORTER 0.4 6.3 5.9 4 4 4 1 1 2019 2H 2019 8 72GV HARRISBURG LINE CP CUMRU-BIRDSBORO 11.7 18.9 7.2 2 2 2 2019 2H 2019 8 72HN NORRISTOWN CONN. KALB-CP NORRIS 17.2 18.0 0.9 1 1 1

p. 4

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix B: NSR PTC Implementation Schedule, Sequence and Hardware

SENSRITIVE SECURITY INFORMATION (SSI) Base Switch Wayside Station Base Implementation From To Signal Monitor Towers Wayside Towers or Station YEAR Complete Date Sequence Line ID District From-To MP MP Miles WIUs WIUs or Poles Radios Poles Radios 2019 2H 2019 8 72HP HARRISBURG LINE FALLS-HARRISBURG 5.2 112.9 107.7 71 41 41 7 7 2019 2H 2019 8 72LB LEHIGH LINE (L&S) BETHLEHEM-LEHIGHTON 84.3 114.7 30.4 14 13 13 3 3 2019 2H 2019 8 72LE LEHIGH LINE MANVILLE-BETHLEHEM 35.8 88.9 53.1 27 25 25 4 4 2019 2H 2019 8 72RY ROYALTON BR. SHOCKS-HARRIS 0.0 11.4 11.4 1 1 1 2019 2H 2019 8 72SR SOUTHERN TIER LINE BINGHAMTON-CP DRAW 368.3 424.2 55.9 90 21 21 4 4 2019 2H 2019 8 74YG YOUNGSTOWN LINE ASHTABULA-CP ROCHESTER 0.0 97.2 97.2 45 39 39 5 5 2019 2H 2019 8 76DR DETROIT LINE BLAHA-SWAN CREEK 20.0 57.7 37.7 17 17 17 1 1 2019 2H 2019 8 76GZ CLOGGSVILLE LINE CLOGGSVILLE-CP MAX 485.5 493.4 7.9 5 5 5 0 0 2019 2H 2019 8 92 B CHICAGO FORT WAYNE - E. HOBART 367.8 486.5 118.7 54 50 50 3 3 2020 1H 2020 9 07 CNO&TP (CNO&TP-First) CINCINNATI-DANVILLE 2.5 116.0 113.6 52 46 46 4 4 2020 1H 2020 9 07 CNO&TP (CNO&TP-Second) DANVILLE-OAKDALE 116.0 252.0 136.0 81 63 63 8 8 2020 1H 2020 9 72BR BUFFALO LINE NORTH DRIFTWOOD-ROCKVILLE 194.0 306.4 112.4 55 49 49 7 7 2020 1H 2020 9 72MK MORRISVILLE CONN. TRACK NORRISTOWN 0.0 2.0 2.0 1 1 1 2020 1H 2020 9 72MV MORRISVILLE LINE CP MA-GLEN 30.3 46.0 15.8 4 4 4 1 1 2020 1H 2020 9 74LC CONEMAUGH LINE CP CONPIT-CP PENN 0.0 77.9 77.9 19 14 14 8 8 2020 1H 2020 9 74RD CLEVELAND LINE CP ROCHESTER-RAVENNA 67.0 85.9 18.9 2 2020 1H 2020 9 76 B CHICAGO DISTRICT HOBART-FOREST HILL 486.5 518.7 32.2 23 19 19 1 1 2020 1H 2020 9 76 B LAKE ERIE DISTRICT EUCLID-BAY VILLAGE 172.0 185.6 13.6 8 6 6 2020 1H 2020 9 92CF NEW CASTLE MILL - WEST WAYNE 16.5 185.8 169.3 68 65 65 6 6 2020 2H 2020 10 07 A CHATTANOOGA TERMINAL JERSEY-CITICO JCT. 235.1 238.1 3.0 4 4 4 2020 2H 2020 10 72EP PORT ROAD BR. PORT-BANKS 33.7 76.1 42.4 5 4 4 2 2 2020 2H 2020 10 72OO PORT ROAD BR. CONN. CP HIP-CP MARY 72.8 73.7 0.9 2020 2H 2020 10 72PD PORT ROAD BR. PERRYVILLE-PORT 0.3 39.7 39.4 22 20 20 4 4 2020 2H 2020 10 72PT PITTSBURGH LINE HARRIS-CP CANNON 104.9 119.2 14.3 10 7 7 2020 2H 2020 10 72YI REYBOLD I.T. PORTER-REYBOLD 0.0 3.5 3.5 1 1 1 2020 2H 2020 10 74JP PORT PERRY BR. E PITTSBURGH-THOMSON 0.0 2.9 2.9 1 1 1 2020 2H 2020 10 74ML MON LINE CP BELL-WAYNESBURG 0.0 40.2 40.2 13 3 3 2 2 2020 2H 2020 10 74PC FORT WAYNE LINE PITTSBURGH-CRESTLINE 0.0 110.2 110.2 99 31 31 11 11 2020 2H 2020 10 74PT PITTSBURGH LINE CP CANNON-PITTSBURGH 119.2 353.4 234.2 168 79 79 27 29 2020 2H 2020 10 74SG SANG HOLLOW EXTENSION SG-CP CONPIT 277.3 290.6 13.3 1 1 1 1 1 2020 2H 2020 10 74TJ ISLAND CONN. CP PENN-CP ISLE 0.0 1.4 1.4 2020 2H 2020 10 76CD CHICAGO LINE CLEVELAND-CHICAGO 181.2 523.3 342.1 243 158 158 16 16 2020 2H 2020 10 76RD CLEVELAND LINE RAVENNA-DRAWBRIDGE 85.9 123.2 37.3 9 8 8 1 1

p. 5

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix B: NSR PTC Implementation Schedule, Sequence and Hardware

SENSRITIVE SECURITY INFORMATION (SSI) Base Switch Wayside Station Base Implementation From To Signal Monitor Towers Wayside Towers or Station YEAR Complete Date Sequence Line ID District From-To MP MP Miles WIUs WIUs or Poles Radios Poles Radios 2020 2H 2020 10 76UW C.R. & I. I.T. CP518-WOOD 0.0 5.3 5.3 6 5 5 1 1 2020 2H 2020 10 94 S KANSAS CITY MOBERLY -KANSAS CITY 213.0 274.8 61.8 30 27 27 2 2

p. 6

NORFOLK SOUTHERN RAILWAY COMPANY Revised Positive Train Control Implementation Plan Version R1.0 Appendix C: NSR PTC Track Segment Characteristics Public - Redacted

PTC Docket: FRA-2010-0060

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix C: NSR Track Segment Characteristics

Norfolk Southern Railway Company Confidentiality Notice

Disclosure is prohibited without the express written permission of Norfolk Southern.

. Table 1- NSR Track Segment Characteristics

p. ii

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix C: NSR Track Segment Characteristics

REVISION HISTORY

Date Version Description Author Appendix provides the NSR rail network track segment characteristics, mainline and non-mainline designations and associated 27 January 2016 R1.0 PTC risk analysis data NSR- L. Wilson

p. iii

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix C: NSR Track Segment Characteristics

TABLE OF CONTENTS

Norfolk Southern Railway Company Confidentiality Notice ...... ii

Appendix C NSR Track Segment Characteristics...... 1

p. iv

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix C: NSR Track Segment Characteristics

Appendix C NSR Track Segment Characteristics

Table 1- NSR Track Segment Characteristics provides the data related to the track segment characteristics discussed in Sections 3 and 4.8 of the PTCIP. The table provides the following:

. The line segment ID . District name . From-to station names for the district . PTC implementation status o Baseline – non-mainline o Baseline- 0 TIH o Baseline- planned o DeMinimis- categorical o DeMinimis categorical planned o Foreign railroad- leased o Line sale, mainline- not-PTC o Non-mainline o Non-mainline- auxiliary track o Non-mainline- Rule 93 yard limits, restricted speed o PTC . Start (from) milepost and end (to) milepost . Number of miles . Mainline or non-mainline status . Segment characteristics distance weighted average risk rank . Distance weighted average PIH shipments . Overall quantifiable risk rank for the segment

Due to the sensitive security nature of this information, much of the data is redacted.

p. 1

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix C: NSR Track Segment Characteristics

SENSRITIVE SECURITY INFORMATION (SSI) Table 1- NSR Track Segment Characteristics

PTC From To ML MGT PSGR TIH TRACK MOO SPEED GRADE CURVE DWA TOTAL Risk Line ID District From-To MP MP Miles NML Status Rank Rank Rank Rank Rank Rank Rank Rank PIH Rank Tier 03 CHARLOTTE SALISBURY-GREENVILLE 334.0 485.0 151.0 ML 03 DANVILLE MONTVIEW-SALISBURY 175.0 334.0 159.0 ML 03 GREENVILLE GREENVILLE-INMAN 485.0 630.9 145.9 ML 03 WASHINGTON ALEXANDRIA-MONTVIEW 9.2 175.0 165.8 ML 03 DW DANVILLE STOKESLAND JCT. - LEAKSVILLE JCT. 5.4 21.0 15.6 NML 03 KM WASHINGTON MONTVIEW - KINNEY CONN. 0.0 1.2 1.2 ML 03 L DANVILLE LEAKSVILLE JCT. - SPRAY 19.7 26.3 6.5 NML 03 RE CHARLESTON READS BRANCH 0.0 2.6 2.6 NML 03 B WASHINGTON MANASSAS - EDINBURG 0.0 50.9 50.9 ML 03 B WASHINGTON MANASSAS - EDINBURG 60.9 78.9 18.0 NML 03 C COLUMBIA CAYCE - EDMUND 110.1 124.0 13.9 NML 03 D DANVILLE OXFORD - EAST DURHAM 53.2 86.4 33.3 NML 03 F DANVILLE DUNDEE-KENT 0.0 3.3 3.3 NML 03 H DANVILLE/ECBU GREENSBORO - GOLDSBORO 0.0 110.5 110.5 ML 03 H DANVILLE/ECBU GREENSBORO - GOLDSBORO 110.5 130.0 19.5 NML 03 J DANVILLE GLENN - CARRBORO 0.0 10.2 10.2 NML 03 K DANVILLE POMONA - RURAL HALL 0.0 37.0 37.0 NML 03 L DANVILLE WINSTON JCT. - NORTH MOORESVILLE 0.0 53.5 53.5 NML 03 M DANVILLE HIGH POINT - RANDLEMAN JCT. 0.0 17.5 17.5 NML 03 M DANVILLE RANDLEMAN - ASHEBORO 20.6 30.8 10.2 NML 03 N CHARLOTTE SALISBURY - ALBERMARLE 0.8 27.5 26.7 NML 03 O DANVILLE ATANDO JCT. - SOUTH MOORESVILLE 3.0 29.1 26.1 NML 03 R COLUMBIA CHARLOTTE JCT. - AUGUSTA 0.0 110.4 110.4 ML 03 R COLUMBIA CHARLOTTE JCT. - AUGUSTA 110.4 112.0 1.6 NML 03 R COLUMBIA CHARLOTTE JCT. - AUGUSTA 112.0 190.5 78.5 ML 03 S ASHEVILLE SALISBURY - MURPHY JCT. 0.0 25.6 25.6 ML

03 S ASHEVILLE SALISBURY - MURPHY JCT. 25.6 38.4 12.8 ML

03 S ASHEVILLE SALISBURY - MURPHY JCT. 38.4 138.0 99.6 ML 03 S ASHEVILLE SALISBURY - MURPHY JCT. 138.0 139.1 1.1 NML p. 2

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix C: NSR Track Segment Characteristics

03 S ASHEVILLE SALISBURY - MURPHY JCT. 139.1 142.4 3.3 ML 03 V COLUMBIA NEWBERRY - CONRAD 47.1 58.0 10.9 NML 03 V COLUMBIA PROSPERITY - BOYD 36.0 42.1 6.1 NML 03 V GREENVILLE PIEDMONT - GREENVILLE 131.9 143.5 11.6 NML 03 W ASHEVILLE/CHARLOTTE ASHEVILLE - SPARTANBURG (HAYNE) 24.1 65.8 41.7 NML 03 W COLUMBIA SPARTANBURG - COLUMBIA 67.7 75.5 7.8 ML

03 W COLUMBIA SPARTANBURG - COLUMBIA 75.5 79.1 3.6 ML 03 W COLUMBIA SPARTANBURG - COLUMBIA 79.1 161.4 82.3 ML 03 Z GREENVILLE ANDERSON - WALHALLA 10.2 42.6 32.4 NML 03AC DANVILLE HURT CONNECTION 197.0 198.8 1.8 ML 03CF DANVILLE GREENSBORO - COMNOCK 69.4 123.7 54.3 NML 03CW WASHINGTON CALVERTON - CASANOVA 0.0 3.8 3.8 NML 03EC ECBU GOLDSBORO - MOREHEAD CITY 0.0 94.3 94.3 NML 03HG ASHEVILLE S. NEWTON - NEWTON 77.0 80.2 3.2 NML 03HG CHARLOTTE CROWDER - GASTONIA 37.5 45.0 7.5 NML 03NB ECBU CHOCOWINITY - NEW BERN 0.0 30.9 30.9 NML 03NE GREENVILLE LULA - CENTER 0.0 32.0 32.0 NML 03NS ECBU PHOSPHATE JCT. - CHOCOWINITY S. 127.4 132.0 4.6 NML 03NS ECBU RALEIGH N. - CUMNOCK 228.0 279.9 51.9 NML 03OM DANVILLE LYNCHBURG - DURMID 171.0 175.1 4.1 NML 03PM ASHEVILLE CATAWBA - TERRELL 0.0 10.2 10.2 NML 03SB CHARLESTON CATAWBA - ROCK HILL 90.0 102.0 12.0 NML 03SB CHARLESTON KINGVILLE - WATEREE 0.0 5.0 5.0 NML 03SC CHARLESTON CHARLESTON - COLUMBIA 0.3 9.5 9.2 NML 03SC CHARLESTON CHARLESTON - COLUMBIA 9.5 128.0 118.5 ML 03SC CHARLESTON CHARLESTON - COLUMBIA 128.0 128.9 0.9 NML 03VF ECBU VARINA - FAYETTEVILLE 0.0 43.1 43.1 NML 03WL ECBU PHOSPHATE JCT. - LEE CREEK 0.0 25.9 25.9 NML 04 NORCROSS FOREMOST - HOWELL 630.9 635.2 4.3 ML 04 A ATLANTA NORTH OOLTEWAH - JERSEY 226.7 235.1 8.4 ML

p. 3

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix C: NSR Track Segment Characteristics

SENSRITIVE SECURITY INFORMATION (SSI) PTC From To ML MGT PSGR TIH TRACK MOO SPEED GRADE CURVE DWA TOTAL Risk Line ID District From-To MP MP Miles NML Status Rank Rank Rank Rank Rank Rank Rank Rank PIH Rank Tier 04 B NAVAIR VALDOSTA - NAVAIR 151.0 216.2 65.2 NML 04 G MACON/VALDOSTA MACON - JACKSONVILLE 0.0 152.0 152.0 ML 04 G MACON/VALDOSTA MACON - JACKSONVILLE 152.0 254.5 102.5 ML 04 G MACON/VALDOSTA MACON - JACKSONVILLE 254.5 260.6 6.1 NML 04 GB MACON ADEL 0.0 1.0 1.0 NML 04 H ATLANTA NORTH OOLTEWAH - ATLANTA 15.1 149.7 134.6 ML 04 H ATLANTA SOUTH ATLANTA - NORTH MACON 149.7 239.2 89.5 ML 04 H BRUNSWICK NORTH MACON - BRUNSWICK 239.2 242.1 2.9 ML 04 H BRUNSWICK NORTH MACON - BRUNSWICK 242.1 243.6 1.6 NML

04 H BRUNSWICK NORTH MACON - BRUNSWICK 243.6 385.8 142.2 ML 04 H BRUNSWICK NORTH MACON - BRUNSWICK 385.8 425.2 39.4 NML 04 I COHUTTA CLEVELAND - COHUTTA 0.0 14.5 14.5 NML 04 K KRANNERT FOX - KRANNERT 0.0 12.8 12.8 NML 04 WT DUBLIN TENNILE - DUBLIN 0.0 36.3 36.3 NML 04 A EATONTON GORDON - EATONTON 170.3 210.3 40.0 NML 04 B THOMASTON BARNESVILLE - THOMASTON 233.0 251.4 18.4 NML 04 C CEDARTOWN SENOIA - GREEN 270.1 361.4 91.3 NML 04 C FAIRBANKS FAIRBANKS JCT. - KRANNERT JCT. 373.0 381.7 8.8 NML 04 D AUGUSTA AUGUSTA - AUGUSTA 129.0 131.8 2.8 NML 04 D AUGUSTA MILLEN - AUGUSTA 78.7 120.5 41.8 ML 04 D AUGUSTA NIXON - AUGUSTA 125.0 129.0 4.0 ML 04 D AUGUSTA NIXON - NIXON 120.5 125.0 4.5 NML 04 F MADISON MOGUL - MACHEN 4.5 11.1 6.6 ML 04 F MADISON MOGUL - MACHEN 11.1 53.8 42.7 NML 04 H ALBANY RUTLAND JCT. - SMITHVILLE 197.0 219.6 22.6 ML 04 H ALBANY RUTLAND JCT. - SMITHVILLE 219.6 220.0 0.4 NML

04 H ALBANY RUTLAND JCT. - SMITHVILLE 220.0 274.0 54.0 ML 04 H GRIFFIN EDGEWOOD - RUTLAND JCT. 191.9 197.0 5.1 ML

04 J ALBANY SMITHVILLE - ALBANY WEST 274.0 295.8 21.8 ML

p. 4

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix C: NSR Track Segment Characteristics

04 M COLUMBUS FT. VALLEY - MUSCOGEE JCT. 220.0 287.0 67.0 ML 04 S GRIFFIN MACON - ATLANTA 192.1 288.2 96.1 NML 04 S GRIFFIN MACON - ATLANTA 288.2 294.5 6.3 ML

04 S SAVANNAH ARDMORE - MACON 39.9 78.5 38.6 ML 04 S SAVANNAH ARDMORE - MACON 78.5 134.0 55.5 ML 04 S SAVANNAH ARDMORE - MACON 134.0 137.0 3.0 NML 04 S SAVANNAH ARDMORE - MACON 137.0 190.4 53.4 ML

04 S SAVANNAH SAVANNAH - CENTRAL JCT. 0.0 3.5 3.5 ML 04FL SAVANNAH FOUNDATION LEAD 1.6 5.5 3.9 NML 04GF MOORES MOORES - AUGUSTA 235.1 249.1 14.0 NML 04GH ALBANY CGA JCT. - RUTLAND JCT. 0.0 0.6 0.6 ML 04GY MACON SOUTH LEG CONNECTION 0.0 0.8 0.8 ML 04PC SAVANNAH PORT WENTWORTH LEAD CONNECTOR 0.0 0.6 0.6 NML 04PW SAVANNAH PORT WENTWORTH LEAD 0.0 3.0 3.0 NML 04SA CAMAK WAYNESBORO - WARRENTON 94.3 142.3 48.0 NML 04SA SAVANNAH CENTRAL JCT. - ARDMORE 3.5 7.3 3.9 NML

04SA SAVANNAH CENTRAL JCT. - ARDMORE 7.3 36.3 29.0 ML 04WA CEDARTOWN WANSLEY JCT - WANSLEY 0.0 7.0 7.0 NML 07 CNO&TP-First CINCINNATI-DANVILLE JCT. 2.5 116.0 113.6 ML 07 CNO&TP-Second DANVILLE JCT.-COLEMAN 116.0 252.0 136.0 ML 07 CNOTP-Third COLEMAN-CHATTANOOGA 252.0 338.2 86.2 ML 07 A CHATTANOOGA TERMINAL JERSEY-CITICO JCT. 235.1 238.1 3.0 ML 07 A KNOXVILLE BRISTOL-KNOXVILLE 0.0 125.0 125.0 ML 07 A KNOXVILLE KNOXVILLE-OOLTEWAH 125.0 226.7 101.7 ML 07 BL KNOXVILLE BULLS GAP-LEADVALE 0.0 16.9 16.9 ML 07 C KNOXVILLE HYDE-FONDE 74.0 80.0 6.0 NML 07 C KNOXVILLE KNOXVILLE-LOT 0.0 2.3 2.3 NML

p. 5

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix C: NSR Track Segment Characteristics

07 C KNOXVILLE KNOXVILLE-LOT 2.3 20.9 18.6 ML 07 C KNOXVILLE KNOXVILLE-LOT 20.9 67.6 46.7 NML 07 CG KNOXVILLE BEVERLY-CUMBLERLAND GAP 5.8 65.0 59.2 NML

07 CO KNOXVILLE WEST SEVIER-COSTER 0.0 7.9 7.9 ML

07 D KNOXVILLE CLINTON-HARRIMAN JCT. 20.9 36.1 15.2 ML

07 D KNOXVILLE CLINTON-HARRIMAN JCT. 36.1 50.0 13.9 ML

07 D KNOXVILLE CLINTON-HARRIMAN JCT. 50.0 51.3 1.3 ML 07 H CNO&TP ROCKWOOD-HARRIMAN 158.0 166.0 8.0 NML 07 KA KNOXVILLE KNOXVILLE-MARYVILLE 0.0 15.4 15.4 NML 07 T APPALACHIA ANDOVER-MOCCASIN GAP 0.0 3.4 3.4 NML 07 T APPALACHIA ANDOVER-MOCCASIN GAP 3.4 40.0 36.6 ML

07 TC APPALACHIA MOCCASIN GAP-BULLS GAP 40.0 87.2 47.2 ML 07 W LOUISVILLE LOUISVILLE-DANVILLE 268.3 268.9 0.6 ML 07 W LOUISVILLE LOUISVILLE-DANVILLE 268.9 274.9 6.0 NML 07 W LOUISVILLE LOUISVILLE-DANVILLE 274.9 357.7 82.8 ML 07 C CHATTANOOGA TERMINAL ALTON-CHATTANOOGA 445.4 448.0 2.6 NML

07 S KNOXVILLE MURPHY JCT.-MORRISTOWN 142.4 216.5 74.1 ML

07 S KNOXVILLE MURPHY JCT.-MORRISTOWN 216.5 227.9 11.4 ML 07CJ CINCINNATI LINE SHARONVILLE-IVORYDALE JCT. 245.4 255.1 9.7 ML 07CT CINCINNATI CINCINNATI-VERA 0.9 73.5 72.7 NML 07CV CINCINNATI CLARE-VALLEY / RENDCOMB 110.0 112.3 2.3 NML 07CV KNOXVILLE MIDDLESBORO-CUMBERLAND GAP 215.2 219.6 4.4 NML 07HX CINCINNATI TERMINAL ECKLER-WINSTON PLACE 4.0 6.8 2.7 ML 07MR KNOXVILLE QUEENSBURY-APPOLLO 216.0 221.0 5.0 NML

p. 6

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix C: NSR Track Segment Characteristics

SENSRITIVE SECURITY INFORMATION (SSI) PTC From To ML MGT PSGR TIH TRACK MOO SPEED GRADE CURVE DWA TOTAL Risk Line ID District From-To MP MP Miles NML Status Rank Rank Rank Rank Rank Rank Rank Rank PIH Rank Tier 07MS KNOXVILLE STONEY FORK JCT.-BELL COUNTY 219.0 221.8 2.8 NML 07OB CINCINNATI OAKLEY JCT.-NORWOOD 10.1 11.3 1.2 NML 07VA VAUGHN YARD LEAD 0.0 0.7 0.7 NML 08 AGS CHATTANOOGA - MERIDIAN 0.0 295.4 295.4 ML 08 EAST END AUSTELL - BIRMINGHAM 650.0 798.4 148.4 ML 08 WEST END BIRMINGHAM - BERRY 798.4 798.8 0.4 ML

08 WEST END BIRMINGHAM - BERRY 800.0 839.5 39.5 ML 08 WEST END BIRMINGHAM - BERRY 839.5 862.8 23.3 NML 08 A MEMPHIS STEVENSON - NORALA 279.8 401.1 121.3 ML 08 A MEMPHIS STEVENSON - NORALA 401.1 402.3 1.2 NML 08 A MEMPHIS TUSCUMBIA - MEMPHIS 402.3 545.0 142.7 ML 08 A MEMPHIS TUSCUMBIA - MEMPHIS 545.0 551.7 6.7 NML 08 A NEW ORLEANS SHREWSBURY - EAST CITY SWITCH 0.0 3.5 3.5 ML 08 AG AGS NORTH ATTALLA - GADSDEN 0.0 5.5 5.5 NML 08 ES WEST END PARRISH - SEGCO 0.0 1.6 1.6 NML 08 LS NEW ORLEANS ROSIN JCT - PORT NICKEL 3.1 16.4 13.3 NML 08 MB 3B SOUTH MARION JCT - MOBILE 0 143.2 143.2 ML 08 MB 3B SOUTH MARION JCT - MOBILE 143.2 145.5 2.3 NML 08 MB 3B SOUTH MARION JCT - MOBILE 145.5 148 2.5 ML 08 ME MEMPHIS LISTERHILL - EMCO 0.0 6.0 6.0 NML 08 MF MEMPHIS TUSCUMBIA - SHEFFIELD 0.3 3.6 3.3 ML 08 N 3B NORTH WILTON - SOUTH SELMA 138.0 139.3 1.3 NML 08 N 3B NORTH WILTON - SOUTH SELMA 139.3 192.4 53.1 ML 08 N 3B SOUTH SOUTH SELMA - MARION JCT. 192.4 206.6 14.2 ML 08 N ANNISTON ANNISTON - WILTON 61.1 138.0 76.9 NML 08 N DEMOPOLIS MARION JCT. - DEMOPOLIS 206.6 244.4 37.9 NML 08 NT NEW ORLEANS BASIN STREET - PT. CHALMETTE 2.5 8.1 5.6 ML 08 NT NEW ORLEANS BASIN STREET - PT. CHALMETTE 8.1 13.9 5.8 NML 08 NT NEW ORLEANS BASIN STREET - PT. CHALMETTE 13.9 14.4 0.5 NML 08 R 3B NORTH WILTON - BURSTALL 0.0 35.0 35.0 ML 08 SA AGS SOUTH WOODLAWN JCT - ENSLEY JCT 0.0 10.8 10.8 NML

p. 7

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix C: NSR Track Segment Characteristics

SENSRITIVE SECURITY INFORMATION (SSI) PTC From To ML MGT PSGR TIH TRACK MOO SPEED GRADE CURVE DWA TOTAL Risk Line ID District From-To MP MP Miles NML Status Rank Rank Rank Rank Rank Rank Rank Rank PIH Rank Tier 08 M CGA MUSCOGEE JCT - COLUMBUS 287.0 290.9 3.9 NML 08 O CGA MUSCOGEE JCT - OCHILLEE 2.6 12.0 9.4 NML 08 P CGA COLUMBUS - CENTRAL 290.9 292.0 1.1 NML

08 P CGA COLUMBUS - CENTRAL 292.0 425.8 133.8 ML 08 R GREENVILLE COLUMBUS - NORTH COLUMBUS 1.2 12.0 10.8 NML 08 S CGA COLUMBUS - GIRARD 291.0 292.8 1.8 NML 08GU DEMOPOLIS GULF STATES LEAD 0.0 7.0 7.0 NML 08IC MEMPHIS RUSLOR JCT - CORINTH 525.0 529.5 4.5 NML 08NA WEST END SHEFFIELD - PARRISH 1.7 3.7 2.0 ML

08NA WEST END SHEFFIELD - PARRISH 3.7 95.6 91.9 ML 08NO NO&NE MERIDIAN - NEW ORLEANS 0.4 195.9 195.6 ML 55 A NORFOLK TERMINAL TIDEWATER JCT- WEST JCT. 0.0 6.8 6.8 ML 55 A NORFOLK TERMINAL TIDEWATER JCT- WEST JCT. 6.8 7.2 0.4 NML 55 B BLUE RIDGE BURKEVILLE - PAMPLIN 0.0 36.9 36.9 ML 55 C ROANOKE CLOVERDALE - LONE STAR 0.0 8.9 8.9 NML 55 F DURHAM SOUTH BOSTON - CLOVER 31.0 47.4 16.4 NML 55 F RICHMOND BURKEVILLE - WEST POINT 84.8 179.0 94.2 NML 55 H HAGERSTOWN HAGERSTOWN - SHENANDOAH 0.6 59.1 58.4 ML

55 H HAGERSTOWN HAGERSTOWN - SHENANDOAH 59.1 106.7 47.6 ML

55 H ROANOKE SHENANDOAH - ROANOKE 106.7 239.3 132.6 ML 55 L DURHAM KINNEY YARD - PICKS 0.0 33.5 33.5 NML 55 L DURHAM KINNEY YARD - PICKS 33.5 73.1 39.6 ML 55 L DURHAM KINNEY YARD - PICKS 73.1 85.9 12.8 NML 55 M DURHAM MAYO JCT. - MAYO CREEK 0.0 4.0 4.0 NML 55 N BLUE RIDGE CREWE - BURKEVILLE 128.9 133.4 4.5 ML 55 N BLUE RIDGE FOREST - ROANOKE 214.5 257.4 42.9 ML 55 N BLUE RIDGE HALSEY - FOREST 207.7 214.5 6.9 NML

p. 8

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix C: NSR Track Segment Characteristics

SENSRITIVE SECURITY INFORMATION (SSI) PTC From To ML MGT PSGR TIH TRACK MOO SPEED GRADE CURVE DWA TOTAL Risk Line ID District From-To MP MP Miles NML Status Rank Rank Rank Rank Rank Rank Rank Rank PIH Rank Tier 55 N BLUE RIDGE PAMPLIN - CONCORD 169.1 189.9 20.8 ML 55 N CHRISTIANSBURG ROANOKE - WALTON 257.4 297.6 40.2 ML 55 N CHRISTIANSBURG WALTON - EAST BLUEFIELD 301.9 360.3 58.5 ML 55 N NORFOLK BRIDGE 5 - POE 1.2 77.8 76.6 ML 55 N NORFOLK JACK - CREWE 88.3 128.9 40.6 ML 55 N NORFOLK POE - PETERSBURG - JACK 77.8 88.3 10.5 NML 55 P NORFOLK POE - JACK 0.0 4.2 4.2 ML 55 P NORFOLK POE - JACK 4.2 8.9 4.6 ML

55 R WINSTON-SALEM W. ROANOKE - WINSTON SALEM 3.36 105.45 102.1 ML 55 R WINSTON-SALEM W. ROANOKE - WINSTON SALEM 105.45 124.38 18.9 ML 55 V ALTAVISTA ABILENE - ROANOKE 141.4 200.3 58.9 ML 55 V ALTAVISTA ABILENE - ROANOKE 200.3 243.1 42.8 ML 55 V NORFOLK TERMINAL TIDEWATER JCT- ALGREN 2.3 5.1 2.8 ML 55 V NORFOLK TERMINAL TIDEWATER JCT- ALGREN 5.1 15.4 10.3 NML 55 V WHITETHORNE ROANOKE - NARROWS 243.1 316.9 73.8 ML 55 W WINSTON-SALEM ROANOKE - BELT LINE JCT. 0.0 2.3 2.3 ML 55BC WINSTON-SALEM JUNCTION - DUKE POWER 0.0 4.1 4.1 ML 55BS WHITETHORNE IRONTO - BRADSHAW 0.0 4.9 4.9 NML 55CP NORFOLK PETERSBURG - HOPEWELL 0.4 9.9 9.5 NML 55CW CHESAPEAKE & WESTERN BOWMAN - HARRISONBURG 84.0 111.9 27.9 NML 55EB CHESAPEAKE & WESTERN ELKTON - DAYTON 0.0 23.0 23.0 NML 55FD FRANKLIN SUFFOLK - EDGERTON 16.5 29.6 13.1 NML 55GX WHITETHORNE GLENVAR CROSSOVER 0.0 0.3 0.3 NML 55HS CHESAPEAKE & WESTERN HARRISONBURG - PLEASANT VALLEY 0.0 5.0 5.0 NML 55HW HAGERSTOWN SEC. HAGERSTOWN (CP TOWN) 73.7 74.8 1.1 ML 55HW WILLIAMSPORT I. T. HAGERSTOWN - WILLIAMSPORT 74.8 80.3 5.5 NML 55HY DURHAM HYCO JCT. - HYCO 0.0 7.6 7.6 ML 55LP NORFOLK LAMBERTS POINT - BRIDGE 5 0.0 5.1 5.1 ML 55NB PULASKI WALTON - BRISTOL 297.6 408.4 110.8 ML 55NS ALBERMARLE NORFOLK - CHESAPEAKE 0.0 4.0 4.0 NML 55PH BLUE RIDGE CONCORD - FOREST 0.0 22.4 22.4 ML 55PV WHITETHORNE POTTS VALLEY - KERNS 0.0 4.7 4.7 NML

p. 9

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix C: NSR Track Segment Characteristics

SENSRITIVE SECURITY INFORMATION (SSI) PTC From To ML MGT PSGR TIH TRACK MOO SPEED GRADE CURVE DWA TOTAL Risk Line ID District From-To MP MP Miles NML Status Rank Rank Rank Rank Rank Rank Rank Rank PIH Rank Tier 55RB PULASKI RADFORD - FOREST AVENUE 0.0 1.8 1.8 NML 55SX WHITETHORNE SALEM CONNECTION 0.0 1.8 1.8 NML 55VC BLUE RIDGE VINTON - DEMUTH 0.0 1.5 1.5 ML 62 C CLINCH VALLEY DUMPS CREEK BRANCH 0.0 7.3 7.3 NML 62 D POCAHONTAS BUCHANAN BRANCH 0.0 50.8 50.8 ML 62 G CLINCH VALLEY EXT. GLAMORGAN BRANCH 0.0 5.8 5.8 NML 62 H BUCHANAN BRANCH LEVISA BRANCH 0.0 11.5 11.5 NML 62 I POCAHONTAS DRY FORK BRANCH 0.0 44.9 44.9 ML 62 L KENOVA LENORE BRANCH 0.0 17.9 17.9 NML 62 N KENOVA KENOVA - PORTSMOUTH 567.9 608.5 40.6 ML 62 N KENOVA LENORE BRANCH (OML) 484.3 485.6 1.3 ML 62 N KENOVA LENORE BRANCH (OML) 485.6 488.7 3.1 NML 62 N KENOVA WAYNE BRANCH (OML) 543.2 566.7 23.5 NML 62 N KENOVA WAYNE BRANCH (OML) 566.7 567.9 1.2 ML 62 N KENOVA WILLIAMSON - NAUGATUCK 470.0 484.3 14.3 ML 62 N POCAHONTAS DISTRICT BLUEFIELD - WILLIAMSON 360.3 470.0 109.7 ML 62 P CLINCH VALLEY EXT. PARDEE BRANCH 0.0 7.8 7.8 NML 62 R CLINCH VALLEY BIG CREEK BRANCH 0.0 15.1 15.1 NML 62 T POCAHONTAS TUG FORK BRANCH 0.0 12.3 12.3 NML PRINCETON - DEEPWATER 62 V DIST. ELMORE - DEEPWATER 374.5 376.7 2.2 ML PRINCETON - DEEPWATER 62 V DIST. ELMORE - DEEPWATER 376.7 434.9 58.2 NML PRINCETON - DEEPWATER 62 V DIST. KELLYSVILLE - ELMORE 327.0 374.5 47.5 ML 62 W POCAHONTAS GILBERT BRANCH 0.0 13.0 13.0 NML 62AL POCAHONTAS ALMA BRANCH 0.0 3.6 3.6 NML 62BC LEVISA BRANCH BIG CREEK SPUR 0.0 2.3 2.3 NML 62BM POCAHONTAS BRIAR MOUNTAIN BRANCH 0.0 4.0 4.0 NML 62BP BUCHANAN BRANCH BIG PRATER CREEK SPUR 0.0 4.4 4.4 NML 62BS GILBERT BRANCH BEN CREEK SPUR 0.0 2.8 2.8 NML 62BT CLINCH VALLEY BIG TOMS CREEK BRANCH 0.0 2.3 2.3 NML 62CM GUYANDOT RIVER BRANCH CUB CREEK BRANCH 0.0 9.4 9.4 NML 62CS KENOVA COLMONT SPUR 0.0 3.6 3.6 NML p. 10

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix C: NSR Track Segment Characteristics

SENSRITIVE SECURITY INFORMATION (SSI) PTC From To ML MGT PSGR TIH TRACK MOO SPEED GRADE CURVE DWA TOTAL Risk Line ID District From-To MP MP Miles NML Status Rank Rank Rank Rank Rank Rank Rank Rank PIH Rank Tier 62CV CLINCH VALLEY DISTRICT BLUEFIELD - NORTON 366.3 465.8 99.6 ML 62CV CLINCH VALLEY DISTRICT BLUEFIELD - NORTON 465.8 466.5 0.7 NML 62CX CLINCH VALLEY EXT. CALVIN SPUR 0.0 1.3 1.3 NML 62DB POCAHONTAS DELORME BRANCH 0.0 9.6 9.6 NML 62DC BUCHANAN BRANCH DISMAL CREEK BRANCH 0.0 16.6 16.6 NML 62GC BUCHANAN BRANCH RIGHT FORK GARDEN CREEK SPUR 0.0 1.9 1.9 NML 62GD GLAMORGAN BRANCH DIXIANA BRANCH 0.0 7.4 7.4 NML 62GE KENOVA BUCK CREEK BRANCH 0.0 1.6 1.6 NML 62GR PRINCETON - DEEPWATER GUYANDOT RIVER BRANCH 0.0 11.9 11.9 ML 62GR PRINCETON - DEEPWATER GUYANDOT RIVER BRANCH 11.9 45.0 33.2 NML 62IN CLINCH VALLEY EXT. MUDLICK JCT. - TACOMA JCT. 0.0 4.5 4.5 NML 62IN CLINCH VALLEY EXT. MUDLICK JCT. - TACOMA JCT. 4.5 17.2 12.7 ML 62IN CLINCH VALLEY EXT. MUDLICK JCT. - TACOMA JCT. 17.2 22.8 5.6 NML 62JB DELORME BRANCH JAMBOREE SPUR 0.0 6.8 6.8 NML 62JF DRY FORK BRANCH JACOBS FORK BRANCH 0.0 10.4 10.4 NML 62KB KENOVA KENOVA BELT LINE 0.0 4.8 4.8 NML 62LF NOLAN SPUR LONG FORK SPUR 0.0 6.5 6.5 NML 62MC POCAHONTAS MATE CREEK BRANCH 0.0 6.3 6.3 NML 62MS LENORE BRANCH MARROWBONE BRANCH 0.0 2.5 2.5 NML 62NA KENOVA NAUGATUCK -KENOVA 0.0 59.1 59.1 ML 62NH KENOVA NOLAN SPUR 0.0 4.7 4.7 NML 62PC GUYANDOT RIVER BRANCH PINNACLE CREEK SPUR 0.0 5.2 5.2 NML 62RB CLINCH VALLEY EXT. RODA BRANCH 0.0 3.3 3.3 NML 62RG CLINCH VALLEY COAL CREEK BRANCH 0.0 2.9 2.9 NML WEST VIRGINIA 62RR SECONDARY BRICE - HOBSON JCT. 7.0 116.5 109.5 ML 62SF TUG FORK BRANCH SOUTH FORK TUG FORK SPUR 0.0 5.6 5.6 NML 62SK GUYANDOT RIVER BRANCH MORRI BRANCH 0.0 19.4 19.4 NML 62SL TUG FORK BRANCH SAND LICK BRANCH 6.5 10.8 4.3 NML 62SS LONG FORK SPUR SIDNEY SPUR 0.0 7.5 7.5 NML 62ST WINDING GULF BRANCH STONE COAL BRANCH 0.0 4.5 4.5 NML 62TB CLINCH VALLEY EXT. ST. CHARLES BRANCH 0.0 25.5 25.5 NML 62TE POCAHONTAS LICK FORK SPUR 0.0 1.5 1.5 NML

p. 11

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix C: NSR Track Segment Characteristics

SENSRITIVE SECURITY INFORMATION (SSI) PTC From To ML MGT PSGR TIH TRACK MOO SPEED GRADE CURVE DWA TOTAL Risk Line ID District From-To MP MP Miles NML Status Rank Rank Rank Rank Rank Rank Rank Rank PIH Rank Tier 62UE BUCHANAN BRANCH UPPER ELK CREEK SPUR 0.0 2.2 2.2 NML 62WB KENOVA WAYNE BRANCH 0.0 7.7 7.7 NML 62WC KENOVA WOLF CREEK BRANCH 0.0 23.2 23.2 NML 62WG PRINCETON - DEEPWATER WINDING GULF BRANCH 0.0 29.3 29.3 NML 62WP POCAHONTAS POND CREEK BRANCH 0.0 2.2 2.2 NML WEST VIRGINIA 62WV SECONDARY KANAUGA - CORNELIA 125.6 197.1 71.5 ML WEST VIRGINIA 62WV SECONDARY KANAUGA - CORNELIA 197.1 253.4 56.3 NML 72 OJ ORANGE I.T. FOREST HILL-GREAT NOTCH 8.5 10.5 2.0 NML 72 TG OLD ROAD I.T. WASHINGTON-END 66.5 67.6 1.1 NML 72 B LAKE ERIE DISTRICT BUFFALO-BLASDELL 1.4 2.0 0.6 ML 72 B LAKE ERIE DISTRICT BUFFALO-BLASDELL 2.0 6.5 4.5 ML READING/HARRISBURG 72AF LINE CP BELT-CP TITUS 5.4 13.0 7.6 ML 72BR BUFFALO LINE CP DRAW-CP GRAVITY 0.4 8.8 8.4 NML 72BR BUFFALO LINE NORTH DRIFTWOOD-ROCKVILLE 134.0 194.0 60.0 NML 72BR BUFFALO LINE NORTH DRIFTWOOD-ROCKVILLE 194.0 306.4 112.4 ML 72BV BEAR CREEK R.T. JCT MD-DUNDALK 1.3 5.0 3.7 NML 72DM DELMARVA SEC. PORTER-POCOMOKE 14.4 64.0 49.6 ML 72DM DELMARVA SEC. PORTER-POCOMOKE 64.0 128.2 64.2 NML 72EI EVANSVILLE I.T. LAUREL-EVANSVILLE 8.4 14.3 5.9 NML 72EN READING LINE BETHLEHAM-CP BURN 88.6 93.0 4.4 ML 72EP PORT ROAD BR. PORT-BANKS 33.7 76.1 42.4 ML 72FJ C&F SEC. SEIPLE-ALBURTIS 2.5 14.1 11.6 NML 72FK DELMARVA SEC. DAVIS-PORTER 0.4 6.3 5.9 ML 72FR POTTSVILLE BR. READING-CP BELT 58.6 61.2 2.6 ML 72GK SPARROWS POINT I.T. BAY VIEW YD-SPARROWS PT 0.0 5.6 5.6 NML 72GL CORNING SEC. LYONS-CORNING 11.5 70.9 59.4 NML 72GV HARRISBURG LINE CP CUMRU-BIRDSBORO 11.7 18.9 7.2 ML

72HA D&H 2015 Acquisition BINGHAMTON - DUPONT JUNCTION 616.0 679.4 63.4 ML 72HA D&H 2015 Acquisition DUPONT JUNCTION - SUNBURY 679.4 752.0 72.6 ML

p. 12

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix C: NSR Track Segment Characteristics

72HA D&H 2015 Acquisition SCHENECTADY - BINGHAMTON 484.9 616.0 131.2 ML 72HE SHELLPOT SEC. BELLEVUE-RAGAN 0.0 3.8 3.8 NML

72HE SHELLPOT SEC. BELLEVUE-RAGAN 3.8 6.4 2.6 ML 72HJ STEELTON I.T. HARRISBURG-STEELTON 0.0 2.4 2.4 NML 72HN NORRISTOWN CONN. KALB-CP NORRIS 17.2 18.0 0.9 ML 72HP HARRISBURG LINE FALLS-HARRISBURG 5.2 112.9 107.7 ML 72HW HAGERSTOWN SEC. SHIPPENSBURG-CP TOWN 40.0 73.7 33.7 ML 72HZ NEW HOLLAND SEC. EAST EARL-GREENFIELD 26.6 39.6 13.0 NML 72IP PRESIDENT ST. TK. BALTIMORE 0.0 1.1 1.1 NML 72IR INDIAN RIVER SEC. HARRINGTON-FRANKFORD 0.0 39.0 39.0 NML 72IS ITHACA SEC. ATHENS-MILLIKEN 269.5 321.0 51.5 NML 72JV BELVIDERE I.T. BELVIDERE-BRAINARDS 71.0 78.6 7.6 NML 72JW HAZELTON R.T. ASHMORE-ONEIDA JCT 141.3 147.4 6.1 NML 72KA SHEPPTON I.T. ONEIDA JCT-HARWOOD JCT 148.0 150.0 2.0 NML 72LB LEHIGH LINE (L&S) BETHLEHEM-LEHIGHTON 84.3 114.7 30.4 ML 72LE LEHIGH LINE MANVILLE-BETHLEHEM 35.8 88.9 53.1 ML 72LG LURGAN BR. CAPITAL-LURGAN 0.0 40.0 40.0 ML 72LG LURGAN BR. CAPITAL-LURGAN 40.0 42.4 2.4 ML 72LH LEHIGH LINE LEHIGHTON- M&H JCT 119.3 130.5 11.2 NML 72MK MORRISVILLE CONN. TRACK NORRISTOWN 0.0 2.0 2.0 ML 72MV MORRISVILLE LINE CP MA-GLEN 4.8 30.3 25.6 ML 72MV MORRISVILLE LINE CP MA-GLEN 30.3 46.0 15.8 ML 72ND NAVE-CROXTON R.T. CP CROXTON-HX 1.8 4.3 2.5 NML 72NK NEWARK I.T. WOODSIDE-PATERSON JCT 8.3 17.3 9.0 NML 72OO PORT ROAD BR. CONN. CP HIP-CP MARY 72.8 73.7 0.9 ML 72PD PORT ROAD BR. PERRYVILLE-PORT 0.3 39.7 39.4 ML 72PO PORTLAND SEC. EASTON-PORTLAND 0.0 22.0 22.0 NML 72PT PITTSBURGH LINE HARRIS-CP CANNON 104.9 119.2 14.3 ML 72QH ASHMORE SEC. M&H JCT-ASHMORE 0.0 10.8 10.8 NML 72QR LEHIGH SEC. CROFT-CP WAVERLY 271.6 273.2 1.6 NML

p. 13

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix C: NSR Track Segment Characteristics

SENSRITIVE SECURITY INFORMATION (SSI) PTC From To ML MGT PSGR TIH TRACK MOO SPEED GRADE CURVE DWA TOTAL Risk Line ID District From-To MP MP Miles NML Status Rank Rank Rank Rank Rank Rank Rank Rank PIH Rank Tier 72RV READING LINE CP BLANDON-ALLENTOWN 7.5 36.3 28.8 ML 72RY ROYALTON BR. SHOCKS-HARRIS 0.0 11.4 11.4 ML 72RY ROYALTON BR. SHOCKS-HARRIS 11.4 21.5 10.1 ML 72SE CEMENT SEC. BETHLEHEM-UHLERS 0.0 22.6 22.6 NML 72SI SHIPPENSBURG SEC. LEMOYNE-CARLISLE 0.5 21.0 20.5 NML

72SR SOUTHERN TIER LINE BINGHAMTON-CP DRAW 213.0 368.3 155.3 ML 72SR SOUTHERN TIER LINE BINGHAMTON-CP DRAW 368.3 424.2 55.9 ML 72SV SELINSGROVE I.T. SELINSGROVE JCT-KREAMER 0.0 7.4 7.4 NML 72TH TOMHICKEN R.T HAZLETON JCT-HARLEIGH JCT 145.8 149.6 3.8 NML NML- 72TJ WALDEN SEC. CAMPBELL HALL-MONTGOMERY 5.0 10.5 5.5 LEASED 72TK READING LINE CP BLANDON-CP BELT 0.0 5.4 5.4 ML 72TW READING LINE CP TULP-WYOMISSING JCT 8.1 9.4 1.3 ML 72VI HAVRE DE GRACE I.T. OAK-JUNIATA STREET 0.0 2.3 2.3 NML 72VM CENTRAL I.T. LUDLOW-LEHIGH CONN 60.1 66.6 6.5 NML 72VT VESTAL I.T. BINGHAMTON-WILLOW PT 192.8 195.4 2.6 NML 72WD WASHINGTON SEC. HACKETTSTOWN-PHILLIPSBURG 58.0 80.3 22.3 NML 72WH WATSONTOWN SEC. WATSONTOWN-DERRY 0.0 14.2 14.2 ML 72WO NEW CASTLE SEC. RIVER-PORTER 0.0 14.0 14.0 NML 72YI REYBOLD I.T. PORTER-REYBOLD 0.0 3.5 3.5 ML 72YX YORK SEC. WAGO-YORK 2.4 12.5 10.1 NML 72ZL COLUMBIA SEC. LANCASTER-COLUMBIA 69.1 80.3 11.2 NML 72ZU HARRIMAN I.T. NEWBURG JCT-HARRIMAN 45.0 45.9 0.9 NML 74 B LAKE ERIE DISTRICT BUFFALO-EUCLID 6.5 172.0 165.5 ML 74DL WELLS I.T. WEIRTON JCT-WELLSBURG 0.0 7.2 7.2 NML 74EL ELLSWORTH SEC. MONONGAHELA-MARIANNA 0.0 11.9 11.9 NML 74EQ BENS CREEK I.T. PORTAGE-SONMAN 0.0 2.5 2.5 NML 74JK COVE SEC. / RAE I.T. ALTOONA-HOLLIDAYSBURG 0.0 8.0 8.0 NML 74JM BLAIRSVILLE SEC. CP ALUM-DIAS 0.0 6.5 6.5 NML 74JO GEM I.T. SOAPTOWN-GOODMAN 0.0 2.2 2.2 NML 74JP PORT PERRY BR. E PITTSBURGH-THOMSON 0.0 2.9 2.9 ML 74KB KEYSTONE BRANCH SALTSBURG-SHELOCTA 0.0 16.4 16.4 NML

p. 14

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix C: NSR Track Segment Characteristics

SENSRITIVE SECURITY INFORMATION (SSI) PTC From To ML MGT PSGR TIH TRACK MOO SPEED GRADE CURVE DWA TOTAL Risk Line ID District From-To MP MP Miles NML Status Rank Rank Rank Rank Rank Rank Rank Rank PIH Rank Tier 74KF SHELOCTA R.T. CREEKSIDE-SHELOCTA 27.0 33.0 6.0 NML 74KR KOPPEL SEC. CEMENT-CP WOOD 81.1 87.5 6.4 NML 74LC CONEMAUGH LINE CP CONPIT-CP PENN 0.0 77.9 77.9 ML 74LQ HARDING I.T. MANS-ONTARIO 268.8 274.8 6.0 NML

74LR LOVERIDGE SEC. BROWNSVILLE-LOVE 0.0 0.5 0.5 ML 74LR LOVERIDGE SEC. BROWNSVILLE-LOVE 0.5 45.3 44.8 ML 74LR LOVERIDGE SEC. BROWNSVILLE-LOVE 45.3 78.1 32.8 ML 74LR LOVERIDGE SEC. BROWNSVILLE-LOVE 78.1 79.6 1.5 NML 74MI MEADVILLE LINE FRENCH-COALBURG 105.5 150.8 45.3 NML 74MJ WHEATLAND I.T. WHEATLAND-SHARPVILLE 66.0 73.0 7.0 NML 74ML MON LINE CP BELL-WAYNESBURG 0.0 40.2 40.2 ML 74ML MON LINE CP BELL-WAYNESBURG 40.2 57.9 17.7 ML

74ML MON LINE CP BELL-WAYNESBURG 57.9 58.2 0.3 ML 74ML MON LINE CP BELL-WAYNESBURG 58.2 85.8 27.6 ML 74NJ DETOUR R.T. NILES-PINE 11.7 15.5 3.8 NML 74NJ NILES SEC. CP EAST WAR-LATIMER 20.0 30.8 10.8 NML 74NW NEWELL I.T. WEIRTON-NEWELL 3.0 19.2 16.2 NML

74OC O TRACK MON LINE-LOVERIDGE 58.0 58.4 0.4 ML 74OP CAPTINA SEC. POWHATAN-ALLEDONIA 0.0 15.7 15.7 ML 74OT ECONOMY I.T. EXT. ECONOMY YARD-BADEN 1.0 3.0 2.0 NML 74OY YOUNGSTOWN LINE ASHTABULA-HARBOR YARD 0.0 1.0 1.0 ML 74OY YOUNGSTOWN LINE ASHTABULA-HARBOR YARD 1.0 3.3 2.3 NML 74PA FAIRPORT BRANCH PERRY-END (CPI) 0.0 8.6 8.6 NML 74PC FORT WAYNE LINE PITTSBURGH-CRESTLINE 0.0 110.2 110.2 ML

74PC FORT WAYNE LINE PITTSBURGH-CRESTLINE 110.2 188.7 78.6 ML 74PT PITTSBURGH LINE CP CANNON-PITTSBURGH 119.2 353.4 234.2 ML 74RD CLEVELAND LINE CP ROCHESTER-RAVENNA 0.0 25.4 25.4 ML 74RD CLEVELAND LINE CP ROCHESTER-RAVENNA 25.4 67.0 41.6 NML 74RD CLEVELAND LINE CP ROCHESTER-RAVENNA 67.0 85.9 18.9 ML

p. 15

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix C: NSR Track Segment Characteristics

SENSRITIVE SECURITY INFORMATION (SSI) PTC From To ML MGT PSGR TIH TRACK MOO SPEED GRADE CURVE DWA TOTAL Risk Line ID District From-To MP MP Miles NML Status Rank Rank Rank Rank Rank Rank Rank Rank PIH Rank Tier 74RN RAE I.T. HOLLIDAYSBURG YARD 28.0 32.0 4.0 NML 74RO RIVER LINE YELLOW CREEK-POWHATAN 0.0 20.0 20.0 ML 74RO RIVER LINE YELLOW CREEK-POWHATAN 20.0 20.6 0.6 ML 74RO RIVER LINE YELLOW CREEK-POWHATAN 20.6 58.4 37.8 NML 74RO RIVER LINE YELLOW CREEK-POWHATAN 58.4 59.5 1.1 ML 74RO RIVER LINE YELLOW CREEK-POWHATAN 59.5 60.5 1.0 NML

74RZ LORDSTOWN SEC. YOUNGSTOWN-N JACKSON 0.0 1.7 1.7 ML 74RZ LORDSTOWN SEC. YOUNGSTOWN-N JACKSON 1.7 20.2 18.5 NML 74SG SANG HOLLOW EXTENSION SG-CP CONPIT 277.3 290.6 13.3 ML 74SY SOUTH FORK SEC. SOUTH FORK-GAHAGAN 0.0 1.5 1.5 ML 74SY SOUTH FORK SEC. SOUTH FORK-GAHAGAN 1.5 34.6 33.1 NML 74TJ ISLAND CONN. CP PENN-CP ISLE 0.0 1.4 1.4 ML 74VD VAN WYE I.T. LORDSTOWN SEC-NILES SEC 0.0 0.5 0.5 NML 74WR WEIRTON SEC. STEEL-MINGO YARD 39.3 49.5 10.2 NML 74WX WANA SPUR WANA-BLACKSVILLE MINE #2 0.0 1.5 1.5 ML 74WY WAYNESBURG BRANCH WAYNESBURG-LACK 1.1 22.3 21.2 ML 74WY WAYNESBURG BRANCH WAYNESBURG-LACK 22.3 24.5 2.2 NML 74XC COKEBURG I.T. COKEBURG JCT-84 MINE 0.0 2.6 2.6 NML 74YG YOUNGSTOWN LINE ASHTABULA-CP ROCHESTER 0.0 97.2 97.2 ML 74YN MIRACLE RUN BR. CLIFF-FEDERAL MINE #2 0.0 4.5 4.5 ML 74YP YELLOW CREEK R.T. CP RIVER-CP BRANCH 0.0 1.0 1.0 NML 76 B CHICAGO DISTRICT HOBART-FOREST HILL 486.5 518.7 32.2 ML 76 B LAKE ERIE DISTRICT EUCLID-BAY VILLAGE 172.0 185.6 13.6 ML

76 B LAKE ERIE DISTRICT EUCLID-BAY VILLAGE 185.6 197.3 11.7 ML 76 D DETROIT DETROIT - MONTPELIER 1.4 4.5 3.1 NML 76 D DETROIT DETROIT - MONTPELIER 4.5 116.0 111.5 ML

76 T TOLEDO DISTRICT TOLEDO 5.4 8.0 2.6 ML 76BK WESTERN AVENUE I.T. 47TH STREET-CHICAGO 305.8 307.5 1.7 NML

p. 16

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix C: NSR Track Segment Characteristics

76BK WESTERN AVENUE I.T. 47TH STREET-CHICAGO 307.5 308.3 0.8 ML 76BK WESTERN AVENUE I.T. 47TH STREET-CHICAGO 308.3 309 0.7 NML 76CB CLEVELAND BELT MAHONING RD-KNOB 0 2.2 2.2 NML 76CB CLEVELAND BELT MAHONING RD-KNOB 2.2 6.7 4.5 ML 76CD CHICAGO LINE CLEVELAND-CHICAGO 181.2 523.3 342.1 ML 76CS CHERRY STREET BR. CHERRY STREET-IRONVILLE 2.5 3.7 1.2 NML 76DR DETROIT LINE BLAHA-SWAN CREEK 20.0 57.7 37.7 ML 76DY MIAMI CUT BR. MAUMEE-STANLEY 1.2 4.0 2.8 NML 76GZ CLOGGSVILLE LINE CLOGGSVILLE-CP MAX 485.5 493.4 7.9 ML 76HK DETROIT LINE GIBRALTER - LASALLE 20.0 40.0 20.0 ML 76IW MAUMEE BRANCH TOLEDO-WATERVILLE 105.9 118.2 12.3 NML 76KN KENWOOD LINE (CR&I) ASHLAND-CORNWITH 0.0 2.9 2.9 NML 76KS KANKAKEE BR. NIPSCO-HENNEPIN 55.9 58.1 2.2 NML 76KS KANKAKEE BR. NIPSCO-HENNEPIN 58.1 59.6 1.5 ML

76KS KANKAKEE BR. NIPSCO-HENNEPIN 59.6 152.4 92.8 ML 76KS KANKAKEE BR. NIPSCO-HENNEPIN 152.4 186 33.6 NML

76LK KANKAKEE LINE IHB-SCHNEIDER 6.3 33.4 27.1 ML ML- 76MH MICHIGAN LINE Townline-Kalamazoo 7.6 143.3 135.7 SOLD 76OJ HUGO I.T. HUGO-BRADY LAKE 25.5 27.4 1.9 NML 76PN HARVARD CONN. CP 9-WHITE 0.0 1.8 1.8 NML 76QP BERNICE R.T. DOLTON-CALUMET RIVER 293.4 294.3 0.9 NML 76RD CLEVELAND LINE RAVENNA-DRAWBRIDGE 85.9 123.2 37.3 ML 76RU CALUMET RIVER I.T. RIVER BRANCH JCT-HEGEWISCH 0.0 1.8 1.8 ML 76RU CALUMET RIVER I.T. RIVER BRANCH JCT-HEGEWISCH 1.8 4.4 2.6 NML 76TB TOLEDO BELT FASSETT-IRONVILLE 1.2 5.4 4.1 NML 76TC GARY BRANCH AETNA-CLARKE JCT 240.3 246.6 6.3 NML TOLEDO/MAUMEE BACK 76TM SIDE VULCAN-GOULD 11.0 12.7 1.7 NML 76UW C.R. & I. I.T. CP518-WOOD 0.0 5.3 5.3 ML

p. 17

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix C: NSR Track Segment Characteristics

SENSRITIVE SECURITY INFORMATION (SSI) PTC From To ML MGT PSGR TIH TRACK MOO SPEED GRADE CURVE DWA TOTAL Risk Line ID District From-To MP MP Miles NML Status Rank Rank Rank Rank Rank Rank Rank Rank PIH Rank Tier 76VO OLIVERS I.T. SOUTH BEND-OLIVERS 0.5 2.7 2.2 NML 76XA OAKDALE CONN. CP 286-CP OAK 286.9 287.8 0.9 NML 76XK CLINTON I.T. VULCAN-MICHIGAN ELEVATOR 299.3 308.8 9.5 NML 92 B CHICAGO FORT WAYNE - E. HOBART 367.8 486.5 118.7 ML

92 B CLEVELAND BAY VILLAGE - BELLEVUE 197.3 202.3 5.0 ML

92 B CLEVELAND BAY VILLAGE - BELLEVUE 202.3 204.7 2.4 ML

92 B CLEVELAND BAY VILLAGE - BELLEVUE 204.7 222.6 17.9 ML 92 B CLEVELAND BAY VILLAGE - BELLEVUE 222.6 248.1 25.5 ML 92 B FOSTORIA BELLEVUE - FORT WAYNE 248.1 367.8 119.7 ML 92 D HUNTINGTON MONTPELIER - PERU 116.0 204.5 88.5 ML 92 H CLEVELAND HURON BRANCH 10.7 12.5 1.8 NML 92 N COLUMBUS VERA - COLUMBUS 608.5 704.6 96.1 ML 92 S SANDUSKY COLUMBUS - SANDUSKY 1.0 111.4 110.4 ML

92 T TOLEDO IRONVILLE-YEOMANS 8.0 24.6 16.6 ML 92 T TOLEDO IRONVILLE-YEOMANS 24.6 53.1 28.6 ML 92 T TOLEDO IRONVILLE-YEOMANS 53.1 54.7 1.6 NML 92AM WESTERN BRANCH SCIOTO - BANNON 132.1 137.6 5.5 ML 92CF NEW CASTLE MILL - WEST WAYNE 16.5 185.8 169.3 ML 92CJ DAYTON WEBER - SHARONVILLE 134.4 245.4 111.0 ML 92EW TOLEDO FREMONT SWITCHING LEAD - N&W 20.4 25.5 5.1 NML 92FY CLEVELAND SOUTH LORAIN I.T. 0.0 6.8 6.8 NML 92KM BUCKEYE BRANCH HOCKING - BUCKEYE 0.0 9.5 9.5 NML 92MP MARION GOSHEN - ANDERSON 0.0 58.5 58.5 ML

92MP MARION GOSHEN - ANDERSON 58.5 99.8 41.3 ML 92MP MARION GOSHEN - ANDERSON 99.8 111.1 11.3 NML 92QD DAYTON FRANKLIN I.T. 0.0 1.0 1.0 NML 92QZ DAYTON BUCKEYE YARD BRANCH 0.0 3.3 3.3 NML 92RK RED KEY SEC. GAS CITY-GOODMAN 154.5 162.0 7.5 NML

p. 18

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix C: NSR Track Segment Characteristics

SENSRITIVE SECURITY INFORMATION (SSI) PTC From To ML MGT PSGR TIH TRACK MOO SPEED GRADE CURVE DWA TOTAL Risk Line ID District From-To MP MP Miles NML Status Rank Rank Rank Rank Rank Rank Rank Rank PIH Rank Tier NML- 92RK RED KEY SEC. RED KEY - CONVERSE 124.9 130.0 5.1 LEASED 92RR WEST VIRGINIA SEC. BANNON - REFUGEE 0.0 7.0 7.0 ML 92SC CLEVELAND HURON BRANCH / SHINROCK CONN 0.0 2.6 2.6 NML 92SL CLEVELAND SOUTH LORAIN BRANCH 0.0 3.1 3.1 NML 92SP FRANKFORT HALES - FRANKFORT 136.4 172.5 36.1 NML

92SP FRANKFORT HALES - FRANKFORT 172.5 173.9 1.4 ML

92SP FRANKFORT HALES - FRANKFORT 173.9 234.0 60.1 ML 92SP FRANKFORT HALES - FRANKFORT 234.0 234.7 0.7 NML 92SP LIMA ARCADIA - LIMA 48.4 88.8 40.4 NML 92TN FOSTORIA WOODBURN BRANCH 79.0 87.2 8.2 NML 92TS COLUMBUS TEAYS SPUR 0.0 3.3 3.3 NML 94 BY SOUTHERN EAST YANKEETOWN - LYNNVILLE MINE 0.0 21.0 21.0 ML 94 BY SOUTHERN EAST YANKEETOWN - LYNNVILLE MINE 21.0 21.6 0.6 NML 94 CB SOUTHERN WEST MT. CARMEL - KEENSBURG 126.2 132.0 5.8 NML 94 CJ SOUTHERN EAST OAKLAND CITY JCT - ALGERS 0.0 12.0 12.0 NML 94 EB SOUTHERN EAST EVANSVILLE - HUNTINGBURG 0.0 32.2 32.2 NML 94 EB SOUTHERN EAST EVANSVILLE - HUNTINGBURG 32.2 46.9 14.7 ML 94 EJ SOUTHERN EAST OAKLAND CITY JCT - ENOSVILLE 0.0 4.7 4.7 NML 94 RB SOUTHERN EAST AEP - ROCKPORT JCT. 3.2 16.2 13.0 ML 94 W SOUTHERN EAST PRINCETON - LOUISVILLE 162.8 268.3 105.5 ML 94 W SOUTHERN WEST ST. LOUIS - PRINCETON 4.4 4.7 0.3 NML 94 W SOUTHERN WEST ST. LOUIS - PRINCETON 4.7 162.8 158.1 ML 94 A ALTON ALTON - END 0.0 1.7 1.7 NML 94 A ALTON ALTON - END 1.7 4.9 3.2 ML 94 A ALTON ALTON - END 4.9 9.1 4.2 NML 94 C BLOOMINGTON GIBSON CITY - BEMENT 113.3 153.1 39.8 ML 94 D BROOKLYN MOSSER - E. ST. LOUIS 376.5 480.4 103.9 ML 94 D BROOKLYN MOSSER - E. ST. LOUIS 480.4 485.0 4.6 NML 94 D LAFAYETTE PERU - MOSSER 204.5 376.5 172.0 ML

p. 19

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix C: NSR Track Segment Characteristics

94 H HANNIBAL HANNIBAL - MOBERLY 0.0 69.9 69.9 ML 94 M SPRINGFIELD BLUFFS - MEREDOSIA 465.7 471.6 5.9 NML

94 S KANSAS CITY MOBERLY -KANSAS CITY 148.4 213.0 64.6 ML 94 S KANSAS CITY MOBERLY -KANSAS CITY 213.0 274.8 61.8 ML 94 S ST. LOUIS ST. LOUIS - MOBERLY 3.0 5.0 2.0 NML

94 S ST. LOUIS ST. LOUIS - MOBERLY 5.0 46.7 41.7 ML

94 S ST. LOUIS ST. LOUIS - MOBERLY 46.7 148.4 101.7 ML 94AE ALTON BRIDGE JCT - GRANITE CITY 3.9 9.3 5.4 NML 94AE ALTON GRANITE CITY - WOOD RIVER 9.9 21.9 12.0 NML 94CC KANSAS CITY BIRMINGHAM - FORD PLANT 0.0 3.1 3.1 NML 94DE BROOKLYN REMINGTON - MONTEREY JCT. 0.0 14.3 14.3 NML 94DH SPRINGFIELD MOSSER - HANNIBAL 376.5 466.0 89.5 ML

94DH SPRINGFIELD MOSSER - HANNIBAL 466.0 515.5 49.5 ML 94ME BROOKLYN MONTEREY JCT - EXXON 0.0 4.4 4.4 NML 94SP BLOOMINGTON GIBSON CITY - FARMDALE 340.0 340.5 0.5 ML 94SP BLOOMINGTON GIBSON CITY - FARMDALE 340.5 410.8 70.3 NML

94SP FRANKFORT FRANKFORT - LAYFAYETTE 234.7 250.9 16.2 ML

94SP FRANKFORT FRANKFORT - LAYFAYETTE 250.9 257.7 6.8 ML 94SP FRANKFORT FRANKFORT - LAYFAYETTE 257.7 259.0 1.3 NML 94TS MADISON COFFEEN - SORENTO 394.3 395.8 1.4 NML 94TS MADISON COFFEEN - SORENTO 395.8 406.6 10.9 ML 94UM BLOOMINGTON URBANA - MANSFIELD 28.5 47.9 19.4 NML 94VC BROOKLYN DYKE JCT.-BROOKLYN 0.0 5.6 5.6 NML

p. 20

NORFOLK SOUTHERN RAILWAY COMPANY Revised Positive Train Control Implementation Plan Version R1.0 Appendix D: NSR PTC Tenant Interoperability Agreements Public - Redacted

PTC Docket: FRA-2010-0060

Docket FRA - 2010-0060 NSR PTCIP v.R1.0- Appendix D NSR PTC Tenant Interoperability Agreements

SENSRNorfolkITIVE SECURITY Southern INFORMATION Railway (SSI) Company Confidentiality Notice

Contains Confidential Information. This document contains confidential commercial information within the meaning of 5 U.S.C. §552 (b)(4). Disclosure is prohibited without the express written permission of the Norfolk Southern Railway Company (“NSR”).

This document contains commercial information pertaining to Norfolk Southern and its freight rail tenants, which is subject to non-disclosure requirements under 49 U.S.C. §11904. The disclosure of such information could result in competitive harm to Norfolk Southern Railway Company or its freight rail tenants or customers. Release of this information could impair NS’s competitive position by disclosing NSR’s business practices to its competitors.

p. i

Docket FRA - 2010-0060 NSR PTCIP v.R1.0- Appendix D NSR PTC Tenant Interoperability Agreements

SENSR ITIVE SECURITY INFORMATION (SSI)

REVISION HISTORY

Date Version Description Author Appendix provides the three NSR letters to tenants containing NSR interoperability terms and conditions and the responses 27 January 2016 R1.0 received from tenants as of 1/25/16. NSR- L. Wilson

p. ii

Norfolk Southern Corporation Roberto H. Robinson Short Line Marketing & Commercial Development AVP Short Line Marketing & 3 Commercial Place Commercial Development Norfolk, VA 23510 757-668-1587

December 22, 2015

Tenant Railroad Name Addressee Address City, State Zip

Subject: Equipping of Locomotives on Norfolk Southern Railway Company PTC Territory and PTC Implementation Plan Required Information Collection (File- RTE)

Dear Addressee,

In accordance with Section 104 of the Rail Safety Improvement Act of 2008 (RSIA) (codified at 49 U.S.C. § 20157) and its implementing regulations found in Title 49 of the Code of Federal Regulations, Part 236, Subpart I, Norfolk Southern Railway Company (NSR) will be deploying Positive Train Control (PTC) on many of its track segments. Norfolk Southern’s PTC Implementation Plan (PTCIP) must describe how the PTC system will provide for interoperability of the system between the host and all tenant railroads on the track segments required to be equipped with PTC systems, see 49 C.F.R. § 236.1011(a)(3). The purpose of this letter is to inform you that Tenant Railroad Name will be required to equip its locomotives with a fully operative onboard PTC apparatus when operating on the NSR track segments listed below, to provide you with NSR conditions for its tenant railroads to achieve PTC interoperability and to collect information required for the revised NSR PTCIP due to the FRA on January 27, 2016.

Generally, trains operating over track segments equipped with PTC must be controlled by a locomotive equipped with an onboard PTC apparatus, see 49 C.F.R. § 236.1006(a). Trains operated by Class II or Class III railroads not so equipped are permitted by regulation to operate on a PTC-operated track segment provided certain criteria are met (49 C.F.R. § 236.1006(b)(4)), but Class I railroads are permitted to impose requirements beyond the regulatory minimums established by the Federal Railroad Administration (see, 49 C.F.R. § 236.1001(b), 75 Federal Register 2598, 2635). NS will adopt new Operating Rules to cover PTC operations. Norfolk Southern has evaluated your railroad’s operations at the locations listed below and determined Tenant Railroad Name will be required to equip its locomotives with PTC to conduct its operations at those locations.

NSR is planning to deploy the Wabtec Interoperable Electronic Train Management System (I- ETMS®) PTC system, which is designed to support interoperability. This system complies with the AAR PTC standards and best practices found in the AAR Manual of Standards and

Recommended Practices, Section K, Parts I-VI. The FRA Type-Approved I-ETMS PTC Development Plan (PTCDP) describes I-ETMS system components and operation. This PTCDP can be found on the NSR FRA PTC docket FRA-2010-0060 or a copy may be obtained from NSR upon request. Although the BNSF implementation of the system received FRA conditional certification in 2015, I-ETMS will continue to be under test and Revenue Service Demonstration phases in 2016.

The use of I-ETMS or any other FRA-approved PTC system by another railroad on Norfolk Southern property requires prior written verification by Norfolk Southern to FRA that the tenant road is fully interoperable with NSR. This includes documentation and verification that the PTC equipment has been properly installed in accordance with the procedures required by 49 CFR § 236.1039, data has been properly secured under 49 CFR § 236.1033, and train crews have been properly trained as required by 49 CFR §§ 236.1041, 236.1043, and 236.1047. NSR will refuse any non-equipped trains or trains found not to be interoperable with I-ETMS which are required to be equipped for operation on NSR.

Norfolk Southern requests your response no later than January 6, 2016 to meet our regulatory obligations for the PTC implementation Plan. Please complete the PTC Interoperability Terms & Conditions and acknowledge Tenant Railroad Name receipt, understanding and required compliance with these conditions. Return this form to [email protected]

NSR Identified Tenant Railroad Name PTC District Operations

PTC District Milepost Start Milepost End

December 22, 2015 2

We plan to conduct meetings in 2016 to work together to discuss details for interoperable PTC operations. If you have any questions, please do not hesitate to contact one of the following Norfolk Southern resources to assist your team.

NS Commercial contact Rob Robinson Assistant Vice President Short Line Marketing & Commercial Development [email protected] 757-668-1587

NS PTC technical contact Eric Hullemeyer Director Advanced Train Control [email protected] 404-527-2880

NS PTC regulatory compliance contact Lisa Wilson Manager ATC Regulatory Compliance & Training [email protected] 404-962-5931

Sincerely,

Rob Robinson

December 22, 2015 3

NSR Positive Train Control Interoperability Terms & Conditions RTE

This document (1) lists the information the FRA requires Norfolk Southern Railway receive from its tenant railroads under § 236.1011(a)(6)((iv) and (2) describes conditions for interoperability which must be satisfied prior to the use of a PTC system by another railroad on NS property. Please complete this form and acknowledge receipt, your understanding of these conditions, and your commitment to comply with these conditions. Return to [email protected]

Tenant Railroad Name

LOCOMOTIVE EQUIPPING

Total Number of Locomotives to Be Equipped with a PTC System

Identify each item of rolling stock to be PTC system equipped and the date each will be equipped.

Locomotive Model Number to be Equipped Date for Equipping*

* If not known, Tenant Railroad Name shall notify NSR of its schedule to equip its locomotives no later than 30 days (on or before February 29, 2016) after the NSR PTCIP is submitted to FRA. Norfolk Southern Railway and its tenant shall define a schedule for PTC operations with equipped locomotives consistent with the NSR PTC Implementation Plan schedule.

PTC SYSTEM

Tenant Railroad Name shall install and implement the I-ETMS system described in FRA Type Approval FRA-TA-2011-02-C ☐Yes ☐No

If Tenant Railroad Name plans to install and implement a PTC system other than I-ETMS identify: System Name

System Manufacturer PTCDP FRA Type Approval ID

December 22, 2015

NSR Positive Train Control Interoperability Terms & Conditions RTE

Tenant Railroad Name OPERATIONS Please identify Tenant Railroad Name operations on NSR by the district found in the in the NSR timetables and the milepost where operations start and the farthest point of travel where they end on NSR mainline track to verify the NSR understanding of your operation. [Example: District: Buffalo Line, MP Start: BR158.08, MP End: BR165.60]

District Milepost Start Milepost End

NSR reserves the right to require Tenant Railroad Name to equip its locomotives with PTC in the future for operations on any other NSR track segments to comply with any applicable regulatory, safety, or operational requirements.

December 22, 2015

NSR Positive Train Control Interoperability Terms & Conditions RTE

Technical interoperability is achieved through the common use of documented interface definitions. Semantic interoperability is achieved through the common use of documented system behavioral specifications. To achieve technical and semantic PTC interoperability for operation on NSR, the Tenant Railroad Name is required to:

1. Subscribe to the AAR/ASLRRA/APTA Positive Train Control Interchange Agreement binding the Tenant Railroad Name to industry interoperability standards. The Regional, Shortline and Terminal Working Group includes all participants of the Agreement who are not Class I railroads or passenger railroads. 2. Install and implement a PTC system (or its components, as necessary) which conforms to the AAR Manual of Standards and Recommended Practices – Section K documents related to the implementation of positive train control. These documents are available from the AAR. Relevant standards and recommended practices are located in the following sections of the Manual: . Section K-I – Railway Electronics Systems Architecture and Concepts of Operations . Section K-II – Locomotive Electronics and Train Consist System Architecture . Section K-IV – Office Architecture and Railroad Electronics Messaging . Section K-V – Electronics Environmental Requirements and Systems Management . Section K-VI – Railway Data Management and Communications 3. Federate an ITC-compliant message system (ITCM) for interoperable messaging and communications. Federated connection of ITC-compliant back offices will have the effect of joining the underlying communications systems that support the ITCM by allowing the free-flow of all ITC- compliant messages between back offices. Specifically, federation enables any ITC back office to pass traffic from any 220 MHz base station, locomotive or wayside as well as other railroad-specific communications networks, e.g. cellular, IEEE 802.11, etc. NSR and Tenant Railroad will establish bi or multi-lateral testing protocols, security standards, and related service-level requirements. The primary I-ETMS traffic that will be exchanged between railroads via federated links will be locomotive-BOS traffic and wayside-locomotive traffic.

December 22, 2015

NSR Positive Train Control Interoperability Terms & Conditions RTE

4. Institute processes to ensure Tenant Railroad Name data security of employee credentials for PTC system initialization functionality and secure Tenant Railroad Name locomotive identification and messaging. 5. Maintain at a designated office on its railroad all records required by 49 C.F.R. § 236.1037 which demonstrate Tenant Railroad Name has: . Conducted Tenant Railroad Name lab testing to validate and verify the Tenant Railroad Name PTC system installation, operation and functionality are interoperable with I-ETMS prior to field interoperability tests with NSR. Records of such tests shall be made available by Tenant Railroad Name to FRA upon request. . Participated in field interoperability testing according to a field test plan to validate and verify Tenant Railroad Name PTC system is functionally operable and interoperable for PTC service on the NS rail network. NSR shall provide records of interoperability testing to FRA, as required. . Properly installed all PTC equipment in accordance with the procedures required by 49 C.F.R. § 236.1039, “Operations and Maintenance Manual (OMM).” Records of locomotive installation checkout procedures and the OMM shall be made available by Tenant Railroad Name to FRA upon request. . Delivered the training for train crews required by 49 C.F.R. § 236.1041, “Training and qualification program, general,” § 236.1043, “Task analysis and basic requirements,” and § 236.1047, “Training specific to locomotive engineers and other operating personnel.” Records of training, exams and training plans shall be made available by Tenant Railroad Name to FRA upon request. . Each contractor providing services relating to the testing, maintenance, or operation of Tenant Railroad Name PTC system shall maintain at a designated office training records required under § 236.1039(b). Records of training, exams and training plans shall be made available by Tenant Railroad Name to FRA upon request. 6. In the event of errors or malfunctions of the system in operation on NSR, the Tenant Railroad Name shall operate under the requirements of 49 CFR § 236.1029.

December 22, 2015

NSR Positive Train Control Interoperability Terms & Conditions RTE

Organizational interoperability is achieved primarily through industry-wide forums, such as committees chartered by ITC, AAR and ASLRRA, and through positive business relationships between host and tenant railroads. To facilitate organizational interoperability, please provide name, email and phone number contact information for your key PTC contacts.

Tenant Railroad Name

PTC Technical Resource

Name Click here to enter text.

Email Click here to enter text.

Phone Number Click here to enter text.

Commercial Resource

Name Click here to enter text.

Email Click here to enter text.

Phone Number Click here to enter text.

PTC Operations Resource

Name Click here to enter text.

Email Click here to enter text.

Phone Number Click here to enter text.

Tenant Railroad Name acknowledges receipt and understanding of and shall comply with NSR PTC Interoperability terms and conditions.

Signature ______Date ______

(Print) Name ______

(Print) Title ______

December 22, 2015

F. Lonegro, CSX T. Schnautz, NS Chairman Vice Chairman

R. Kollmar, AAR Committee Liaison

ASSOCIATION OF AMERICAN RAILROADS POSITIVE TRAIN CONTROL INTEROPERABILITY COMMITTEE PTC INTERCHANGE AGREEMENT OVERVIEW

The Association of American Railroads (AAR) has established an Interoperable Operations Working Committee (IOWC) reporting to Safety and Operations Management Committee (SOMC) and a Positive Train Control Interoperability Committee (PTCIC), which is responsible for adopting PTC interchange standards for all U.S. railroads. The PTCIC develops standards and processes for: . hardware and software . configuration management . maintenance requirements . minimum service levels . schedules for phasing in new software and standards . phasing out obsolete software and standards. The AAR has established a PTC Interchange Agreement for all PTC users to acknowledge their commitment to work with all other carriers through an established agreement, forum and industry standards; thus, a commitment to nationwide PTC interoperability. The AAR strongly encourages all railroads (PTC user) which must install and operate PTC in any manner to participate as a member of the PTCIC although all PTC user railroads are not required to be a member of AAR to enjoy PTCIC membership. Nationwide interoperability requires diversity of thought and experience of railroads of all sizes and types; AAR encourages PTC users to join this agreement to be able to express their views and to reach solutions to PTC interoperable issues when they arise. In sum, the PTC Interchange Agreement covers basic needs for interoperability between and among through ITC, ASLRRA, or APTA railroads and is simple in form and content. No one railroad will have authority to make unilateral changes and all PTC railroads, both hosts and tenants, must have a forum for communication and cooperation to work together to ensure PTC interoperability. As railroads submit their updated PTC Implementation Plans to the FRA, they must clearly describe how interoperability will be achieved; execution of this agreement is a positive step forward. The AAR fully supports the execution of the PTC Interchange Agreement by all PTC railroads and welcomes your participation. For more information or to receive a copy of the PTCIC for your signature, please contact Robert Kollmar, Executive Director Engineering, Communications and Train Control, Phone: (202) 639-2142, E-Mail: [email protected].

December 22, 2015

Norfolk Southern Corporation Roberto H. Robinson Short Line Marketing & Commercial Development AVP Short Line Marketing & 3 Commercial Place Commercial Development Norfolk, VA 23510 757-668-1587

December 22, 2015

Tenant Railroad Name Contact Name Address City, State Zip

Subject: Equipping of Locomotives on Norfolk Southern Railway Company PTC Territory (File-DNE-AO)

Dear Tenant Railroad Name,

In accordance with Section 104 of the Rail Safety Improvement Act of 2008 (RSIA) (codified at 49 U.S.C. § 20157) and its implementing regulations found in Title 49 of the Code of Federal Regulations, Part 236, Subpart I, Norfolk Southern Railway Company (NSR) will be deploying Positive Train Control (PTC) on many of its track segments. Norfolk Southern’s PTC Implementation Plan (PTCIP) must describe how the PTC system will provide for interoperability between the host and all tenant railroads on the track segments required to be equipped with PTC systems, see 49 C.F.R. § 236.1011(a)(3). The purpose of this letter is to inform you that based on our understanding of your current operation on NSR, Tenant Railroad Name will not be required to equip its locomotives with a fully operative onboard PTC apparatus when operating on the NSR track segments listed below provided the operation can be modified to address certain safety and/or regulatory issues.

Generally, trains operating over track segments equipped with PTC must be controlled by a locomotive equipped with an onboard PTC apparatus, see 49 C.F.R. § 236.1006(a). Trains operated by Class II or Class III railroads not so equipped are permitted by regulation to operate on a PTC-operated track segment provided certain criteria are met (49 C.F.R. § 236.1006(b)(4)), but Class I railroads are permitted to impose requirements beyond the regulatory minimums established by the Federal Railroad Administration (see, 49 C.F.R. § 236.1001(b), 75 Federal Register 2598, 2635). Norfolk Southern has evaluated your railroad’s operations at the locations listed below and determined that while the present operation would require Tenant Railroad Name to equip its locomotives with PTC, there may be an opportunity to modify the operation to avoid this requirement.

Accordingly, we would like to discuss with you our proposal for modifying the operation. Please contact me by January 6, 2016 to begin this discussion. If I do not hear from you, I will assume you are not interested in modifying the operation and you will receive additional instructions and requests for information to ensure compliance with the interoperability requirements of the PTC regulations.

As information, NSR is planning to deploy the Wabtec Interoperable Electronic Train Management System (I-ETMS®) PTC system, which is designed to support interoperability. This system complies with the AAR PTC standards and best practices found in the AAR Manual of Standards and Recommended Practices, Section K, Parts I- VI. The FRA Type-Approved I-ETMS PTC Development Plan (PTCDP) describes the I-ETMS PTC system components and operation. This PTCDP can be found on the NSR FRA PTC docket FRA-2010-0060 or a copy may be obtained from NSR upon request. Although the BNSF implementation of the system received FRA conditional certification in 2015, I-ETMS will be under test and Revenue Service Demonstration phases in 2016.

The use of I-ETMS or any other FRA approved positive train control system by another railroad on Norfolk Southern property requires prior written verification by Norfolk Southern to FRA that the tenant road is fully interoperable with NSR. This includes documentation and verification that the Positive Train Control equipment has been properly installed in accordance with the procedures required by 49 CFR § 236.1039, data has been properly secured under 49 CFR § 236.1033, and train crews have been properly trained as required by 49 CFR §§ 236.1041, 236.1043, and 236.1047. NSR will refuse any non-equipped trains required to be equipped for operation on NSR.

NSR Identified Tenant Railroad Name PTC District Operations

PTC District Milepost Start Milepost End

December 22, 2015 2

If you have any questions or wish to discuss other issues please do not hesitate to contact one of the following NSR resources to assist your team.

NS Commercial contact Rob Robinson Assistant Vice President Shortline Marketing & Commercial Development [email protected] 757-668-1587

NS PTC technical contact Eric Hullemeyer Director Advanced Train Control [email protected] 404-527-2880

NS PTC regulatory compliance contact Lisa Wilson Manager ATC Regulatory Compliance & Training [email protected] 404-962-5931

Sincerely,

Rob Robinson

December 22, 2015 3

Norfolk Southern Corporation Roberto H. Robinson Short Line Marketing & Commercial Development AVP Short Line Marketing & 3 Commercial Place Commercial Development Norfolk, VA 23510 757-668-1587

December 22, 2015

Tenant Railroad Name Contact Name Address City, State Zip

Subject: Equipping of Locomotives on Norfolk Southern Railway Company PTC Territory (File-DNE-1029)

Dear Tenant Railroad Name,

In accordance with Section 104 of the Rail Safety Improvement Act of 2008 (RSIA) (codified at 49 U.S.C. § 20157) and its implementing regulations found in Title 49 of the Code of Federal Regulations, Part 236, Subpart I, Norfolk Southern Railway Company (NSR) will be deploying Positive Train Control (PTC) on many of its track segments. Norfolk Southern’s PTC Implementation Plan (PTCIP) must describe how the PTC system will provide for interoperability between the host and all tenant railroads on the track segments required to be equipped with PTC systems, see 49 C.F.R. § 236.1011(a)(3). The purpose of this letter is to 1) inform you that based on our understanding of your current operation on NSR, Tenant Railroad Name will not be required to equip its locomotives with a fully operative onboard PTC apparatus when operating on the NSR track segments listed below and 2) to collect information required for the revised NSR PTCIP due to the FRA on January 27, 2016.

Generally, trains operating over track segments equipped with PTC must be controlled by a locomotive equipped with an onboard PTC apparatus, see 49 C.F.R. § 236.1006(a). Trains operated by Class II or Class III railroads not so equipped are permitted by regulation to operate on a PTC-operated track segment provided certain criteria are met (49 C.F.R. § 236.1006(b)(4)), but Class I railroads are permitted to impose requirements beyond the regulatory minimums established by the Federal Railroad Administration (see, 49 C.F.R. § 236.1001(b), 75 Federal Register 2598, 2635). Norfolk Southern has evaluated your railroad’s operations at the locations listed below and determined (1) that it meets the criteria set forth in 49 C.F.R. § 236.1006(b)(4); and (2) that it will not be necessary at this time to impose additional requirements beyond the FRA’s regulatory minimums.

Accordingly, Tenant Railroad Name will not be required to equip its locomotives with PTC to conduct the operations summarized below. However, operations on those segments must be conducted in accordance with applicable regulations, including 49 C.F.R. § 236.1029.

Please acknowledge this letter by verifying your railroad’s operations and acknowledging NSR interoperability conditions in the required tenant information page. Norfolk Southern requests your response no later than January 6, 2016 to meet our regulatory obligations for the PTC Implementation Plan. If you anticipate your railroad’s operations at any of the below locations will change in any way in the future, it will be necessary for you to immediately contact Norfolk Southern’s PTC regulatory compliance contact so we can re-evaluate this determination.

NSR Identified Tenant Railroad PTC District Operations

PTC District Milepost Start Milepost End

If you have any questions please do not hesitate to contact one of the following NSR resources to assist your team.

NS Commercial contact Rob Robinson Assistant Vice President Short Line Marketing & Commercial Development [email protected] 757-668-1587

NS PTC technical contact Eric Hullemeyer Director Advanced Train Control [email protected] 404-527-2880

NS PTC regulatory compliance contact Lisa Wilson Manager ATC Regulatory Compliance & Training [email protected] 404-962-5931

Sincerely,

Rob Robinson

NSR PTC Implementation Plan Required Tenant Information DNE-1029

This document lists the information Norfolk Southern Railway requires it receive from its tenant railroads to ensure it meets the requirements of Subpart I. Please complete this form and acknowledge receipt, your understanding of these interoperability conditions, and your commitment to comply with these conditions. Return to [email protected]

Tenant Railroad Name Click here to enter text.

TENANT RAILROAD OPERATIONS Please identify Tenant Railroad Name operations on NSR by the district found in the in the NSR timetables and the milepost where operations start and the farthest point of travel where they end on NSR mainline track to verify the NSR understanding of your operation. Operations on a PTC mainline must be conducted in accordance with applicable regulations, including 49 C.F.R. § 236.1029. [Example: District: Buffalo Line, MP Start: BR158.08, MP End: BR165.60]

District Milepost Start Milepost End

The undersigned acknowledges that any changes in Tenant Railroad Name operations or NSR’s understanding of those operations may necessitate a change in this determination. Additionally, if your railroad’s operations change in any way, it will be necessary for you to immediately notify Norfolk Southern’s PTC regulatory compliance contact so we can re-evaluate this determination. NSR reserves the right to require Tenant Railroad Name to equip its locomotives with PTC in the future for operations on these or any other NSR track segments to comply with any applicable regulatory, safety, or operational requirements.

Tenant Railroad Name acknowledges receipt and understanding of and shall comply with NSR PTC interoperability conditions.

Signature ______Date ______

(Print) Name ______

(Print) Title ______

NORFOLK SOUTHERN RAILWAY COMPANY Revised Positive Train Control Implementation Plan Version R1.0 Appendix E: Exclusions or Removals from NSR PTC Baseline Public- Redacted

PTC Docket: FRA-2010-0060

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix E: Exclusions or Removals from NSR PTC Baseline

Norfolk Southern Railway Company Confidentiality Notice

Disclosure is prohibited without the express written permission of the Norfolk Southern Railway Company (“NSR”).

Norfolk Southern hereby makes a request to the agency pursuant to 49 C.F.R. § 209.11 that the redacted material be given confidential treatment on the foregoing grounds. The sections of the document redacted under the foregoing cited provisions and which have been appropriately marked are:

. Table 1- Exclusions or Removals Due to Routing Changes . Table 2- Freight Lines with de Minimis Risk Not Used for Regularly Provided Passenger Service

p. ii

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix E: Exclusions or Removals from NSR PTC Baseline

REVISION HISTORY

Date Version Description Author Appendix E provides the data and information to support removal or exclusion of certain track segments as provided for in 49 C.F.R. Subpart I § 236.1005(b)(4) from the NSR PTC implementation baseline 27 January 2016 R1.0 established in 2008 by Subpart I. NSR- L. Wilson

p. iii

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix E: Exclusions or Removals from NSR PTC Baseline

TABLE OF CONTENTS

Norfolk Southern Railway Company Confidentiality Notice ...... ii

Appendix E Exclusions or Removals from NSR PTC Baseline ...... 1

1 Routing Changes § 236.1005(b)(4)(i) ...... 2

2 Freight Lines with de Minimis Risk Not Used for Regularly Provided Passenger Service ...... 5

3 Line Sales or Leases ...... 8

Table of Tables

Table 1- Exclusions or Removals Due to Routing Changes ...... 3

Table 2- Freight Lines with de Minimis Risk Not Used for Regularly Provided Passenger Service ...... 7

Table 3- Exclusion of Districts Sold or Leased from NSR PTC Implementation ...... 8

p. iv

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix E: Exclusions or Removals from NSR PTC Baseline Totals

Appendix E Exclusions or Removals from NSR PTC Baseline

NSR has excluded or removed certain track where PTC installation has not yet occurred but was otherwise required as provided for in 49 C.F.R. § 236.1005(b)(4). These exclusions or removals are the result of changes in rail traffic or a minimal quantity of PIH materials traffic:

. Reductions in total traffic volume is designated as “Baseline – NML” (non- mainline) where the segment already meets the below 5 million gross tons annually as computed over a 2-year period requirement and now qualifies as non-mainline as per § 236.1003. . The cessation of PIH materials traffic is designated as “Baseline - 0 TIH” where the segment already meets the cessation of PIH requirement. . The cessation of PIH materials traffic is designated as “Baseline – Planned,” where cessation of PIH materials traffic will be instituted through application controls by the end of first quarter 2016 to ensure the rerouting will be in place for all future moves. . Reductions in PIH traffic is designated as “ML- NOT PTC” for segments where the line qualifies as a mainline per § 236.1003 but has zero TIH; thus no requirement for PTC. . The presence of a minimal quantity of PIH materials traffic is designated as “DeMinimis – Categorical” where the segment already meets the traffic requirements of § 236.1005(b)(4)(iii). . The presence of a minimal quantity of PIH materials traffic is designated as “DeMinimis - Categorical Planned” where reduction in PIH materials traffic will be instituted through application controls by the end of first quarter 2016 to ensure the rerouting will be in place for all future moves to meet the traffic requirements of § 236.1005(b)(4)(iii). . The sale or lease of properties is designated as “Line Sale” and “FGN RR- NS Leased,” where NS has leased the property to a short line road.

p. 1

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix E: Exclusions or Removals from NSR PTC Baseline Totals

1 Routing Changes § 236.1005(b)(4)(i)

As per 49 C.F.R. § 236.1005(b)(4)(i), NSR has excluded or removed certain track where a PTC system is otherwise required, but has not yet been installed, based upon changes in rail traffic such as reductions in total traffic volume to a level below 5 million gross tons annually or the cessation of PIH materials traffic. As per 49 C.F.R. § 236.1005(b)(4)(ii), NSR attests that these routing changes exclusions each meet the following requirements:

. An operational analysis was conducted by the Network & Service Management and Marketing Industrial Products teams to validate five-year projections for traffic would meet regulatory requirements for traffic density, passenger and/or PIH materials for removal from the baseline. This analysis establishes that, as of the end of the first quarter of 20161: o No passenger service will be present on the involved track segments, and o No PIH traffic will be present on the involved track segments or the gross tonnage on the involved track segments will decline to below 5 million gross tons annually as computed over a 2-year period.

Table 1- Exclusions or Removals Due to Routing Changes provides the track segment characteristics data for these line segments accounting for 1,882 miles to support the removal from the NSR implementation.

p. 2

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix E: Exclusions or Removals from NSR PTC Baseline

SENSRITIVE SECURITY INFORMATION (SSI) Table 1- Exclusions or Removals Due to Routing Changes PTC From ML MGT PSGR TIH TRACK MOO SPEED GRADE CURVE DWA TOTAL Risk Line ID District From-To Status MP To MP Miles NML Rank Rank Rank Rank Rank Rank Rank Rank TIH Rank Tier

p. 3

Docket FRA - 2010-0060 NSR PTCIP v. R1.0 Appendix E: Exclusions or Removals from NSR PTC Baseline

SENSRITIVE SECURITY INFORMATION (SSI) PTC From ML MGT PSGR TIH TRACK MOO SPEED GRADE CURVE DWA TOTAL Risk Line ID District From-To Status MP To MP Miles NML Rank Rank Rank Rank Rank Rank Rank Rank TIH Rank Tier

p. 4

2 Freight Lines with de Minimis Risk Not Used for Regularly Provided Passenger Service

In accordance with 49 C.F.R. § 236.1005(b)(4)(iii), NSR has excluded or removed from its implementation plan certain track segments where a PTC system is otherwise required but has not yet been installed based upon the presence of a minimal quantity of PIH materials traffic. Table 2- Freight Lines with de Minimis Risk Not Used for Regularly Provided Passenger Service lists the segments accounting for 1,060 miles that have been excluded from the Norfolk Southern Railway Revised PTC Implementation Plan v.R1.0 and provides information regarding those track segment’s operational characteristics.

NSR attests that each of these excluded segments meets the requirements for categorical exclusion:

2 Either NSR 2014 traffic met the requirements listed above or application controls were instituted by the end of first quarter 2016 to ensure the rerouting would be in place for all future moves.

p. 5

train crew does not have advance knowledge of the working limits, as soon as practical; o Carries fewer than 100 cars containing PIH materials per year, excluding those cars containing only a residue, as defined in 49 C.F.R. § 171.8, of PIH materials; o Carries 2 or fewer trains per day carrying any quantity of PIH materials; o Where trains carrying any quantity of PIH materials will operate at speeds not to exceed 40 miles per hour; and o Where any train transporting a car containing any quantity of PIH materials is operated with a vacant block ahead of and behind the train.

p. 6

Table 2- Freight Lines with de Minimis Risk Not Used for Regularly Provided Passenger Service

PTC From ML MGT PSGR TIH TRACK MOO SPEED GRADE CURVE DWA TOTAL Risk Line ID District From-To Status MP To MP Miles NML Rank Rank Rank Rank Rank Rank Rank Rank TIH Rank Tier

p. 7

3 Line Sales or Leases

Since the 2008 baseline, NSR has sold or leased two line segments included in the 2010 PTCIP. These changes account for a reduction of 141.2 miles from the NSR PTC implementation.

The Michigan Line was sold to Michigan DOT, accounting for 135.7 miles of the deployment. The MDOT operates regularly scheduled passenger service on this line segment, making PTC implementation required. NSR made provisions in its agreement with Michigan DOT to retain trackage rights and to ensure the Michigan Line is equipped with a PTC system that is fully interoperable with I-ETMS. NSR understands that Michigan DOT has an agreement with GE to install such a system and with Amtrak to maintain and operate the PTC system.

In 2010, The Walden Secondary from Campbell Hall to Montgomery was leased in its entirety (DJ-5 to DJ-10.5) to the Middletown & New Jersey Railroad (MNJ). Prior to the lease, the 5.5 mile non-mainline line carried only .10 MGT annually and had a maximum authorized speed of 10 MPH.

Table 3- Exclusion of Districts Sold or Leased from NSR PTC Implementation

Line From ID District From-To Status MP To MP Miles FGN RR- NS 72DJ WALDEN SEC. CAMPBELL HALL-MONTGOMERY Leased 5.0 10.5 5.5 MICHIGAN LINE SALE to 76MH LINE TOWNLINE- KALAMAZOO MDOT 7.6 143.3 135.7

p. 8