text
stringlengths 0
1.03k
|
---|
crossing. However, any crossing closure, change in crossing surface (e.g., |
timber to rubber) or change in the type of warning device (e.g., crossbuck to |
flashing lights and gates) must be reported within three months. In addition, FRA |
encourages updates as other crossing information changes. |
Q 33. Would electronic submission allow a railroad or State to update fields for |
which it is not responsible? |
The Railroad only has the ability to update the data fields for which it is |
responsible. Similarly, the State only has the ability to update the data fields for |
which the State is responsible, regardless of the method used to provide the |
update. The submitting entity should only submit updated data for processing for |
which it is responsible. Exceptions to this policy are, however, permitted when |
both entities have provided prior written notification to FRA. |
Q 34. When a crossing is being changed from Private to Public, what data must |
be provided by the submitting agency? |
For a change from a private highway-rail grade crossing to a public highway-rail |
grade crossing, railroads must complete the entire Inventory Form (with the |
exception of I.20 and III.2.K) with updated information. |
For a change from a private pathway grade crossing to a public pathway grade |
crossing, railroads must update the Header, Parts I, II, and III.2.K of the |
Inventory Form and the Submission Information section. |
Q 35. If a private company, port or dock area, or a rail yard has multiple |
crossings, is it possible to have more than one Inventory number assigned |
to the facility? |
A. Although one Inventory Number may be assigned for all of the crossings in |
the facility, there are two reasons why a private company may have more |
than one Inventory Number: |
1. A railroad may assign Inventory Numbers to specific crossings while |
assigning one Inventory Number to the remaining crossings. |
2. If more than one operating railroad provides service to the private |
company from its own track (e.g., one track off of railroad X’s track and |
one track off of railroad Y’s track), each operating railroad must assign a |
Appendix E-10 |
unique Inventory number for the private company. If a crossing accident |
occurs, the railroad that is involved in the collision must use the Inventory |
number that it assigned to the private company. |
Q36. How do I report a change in crossing characteristics (such as a change in |
the crossing surface or a change in the crossing warning devices) that is |
required by 49 CFR 234.411(c) at a public highway-rail grade crossing to |
the Crossing Inventory? |
Complete all of the data fields in the Header of the Inventory Form, checking the |
“Change in Data” box in Item C. |
The primary operating railroad must update all data fields in Parts II and III on the |
Inventory Form. |
Finally, if a hardcopy Inventory Form update will be submitted to the Crossing |
Inventory, the primary operating railroad must complete the Submission |
Information section of the Inventory Form as well. |
Appendix F-1 |
APPENDIX F – High-Speed Rail ID Corridor Designations and Codes |
Key: “#” Use for Rail-Section Identifier (numeric 1 - 9) or use “X” if numeric not used. |
For High Speed Rail Corridor Codes for any new corridors that are not listed above, |
contact the FRA Crossing Inventory Program Manager. |
High-Speed Rail Corridor Designations and Codes |
Code Corridor Route |
PNW# |
Pacific |
Northwest Vancouver - Seattle - Portland - Eugene |
CAV# California San Diego - Los Angeles - Stockton - Sacramento/Bay Area |
CAC# Los Angeles - Bay Area - Sacramento |
CLL# Los Angeles - Las Vegas |
CMM# Chicago Hub Chicago - Milwaukee - Minneapolis |
CSK# Chicago - Springfield - St. Louis - Kansas City |
CIC# Chicago - Indianapolis - Cincinnati |
CKD# Chicago - Kalamazoo - Detroit |
CTC# Chicago - Toledo - Cleveland |
CIL# Indiana Extension: Indianapolis - Louisville |
CCC# Ohio 3 C’s Cleveland - Columbus - Cincinnati |
KEY# Keystone Philadelphia - Harrisburg - Pittsburgh |
EMP# Empire New York - Albany - Buffalo |
NEP# |
Northern |
New England Boston - Portland |
NEM# |
Northern |
New England Boston - Montreal |
NEW# New England Boston - Albany |
NHS# |
Southern |
New England New Haven - Hartford - Springfield |
NEC# |
Northeast |
Corridor |
Washington - Baltimore - Philadelphia - New York - New Haven - |
Boston |
Appendix F-2 |
High-Speed Rail Corridor Designations and Codes |
Code Corridor Route |
SER# Southeast Washington - Richmond - Raleigh |
SES# Raleigh - Columbia - Savannah - Jesup - Jacksonville |
SEC# |
Raleigh - Durham - Greensboro - Charlotte - zGreenville - Atlanta - |
Macon |
SEV# Virginia Extension: Richmond - Hampton Roads |
SEG# Georgia Connection: Macon - Jesup |
FLX# Florida Miami - Orlando - Tampa |
GCA# Gulf Coast Atlanta - Birmingham - Meridian - New Orleans |
GCM# Mobile - Biloxi - New Orleans - Houston |
SCA# |
South |
Central Dallas/Ft Worth - Austin - San Antonia |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.