The DOT National Crossing Inventory File

Transcription

1 The DOT National Crossing Inventory File Eastern Region Highway-Rail Crossing Safety Conference Albany, New York October 2-4, 2007 Thomas P. Woll Federal Railroad Administration Office of Safety

2 DOT National Highway-Rail Crossing Inventory Background, Purpose and Goals How it Works & Requirements Numbering and Filing for New Crossings Responsibilities for Updating Updating for States and Railroads, and for Public Authorities (QZ) New Importance for Homeland Security How to get Data PCAPS, WBAPS, GX, etc. Outreach Effort to add Data Fields & Changes

3 Background Original Inventory Started January 1, 1975 Contains both Current and Historical Records Currently, 2.2 Million Records in the File 1975 had 365,000 at-grade Crossings 2007 has 233,000 at-grade Crossings Process 80K to 100K Updates per Year Submittals Received from 50 States and 650 Railroads

4 Establishing a National Database The AAR, ASLRA, States, FHWA, NHTSA & FRA developed: the DOT/AAR Crossing Inventory Numbering System, the Operating Procedures and Database FRA is the Custodian for the States and Railroads for their National Inventory Data File This is YOUR (States & Railroads) Inventory. FRA only updates it with YOUR data.

5 Purpose & Goals 1973 Federal-Aid Highway Act (Section 203) requires each State to maintain a State Inventory of all crossings And maintain the National Inventory States may maintain just National File Act also requires a Priority List of Improvements Purpose is to Provide Information to Governments and Railroads for Safety Improvement Merge Data with Accident Files to plan Safety improvements Accident Prediction Model Support Homeland Security and the Inventory is critical for supporting ENS (1-800) Program

6 Delivering Results: Collisions, Fatalities and Exposure Rail (million train miles) X Hwy Volume (trillion hwy miles) Collisions X 10 (= quadrillion) = Exposure Fatalities Exposure

7 How it works Currently, it is a Voluntary Program (but not for long) Every Crossing shall have a DOT Crossing Number Six (6) digits followed by an alphabetical character Number is like a street-name sign Coincides with Inventory Data in the File Information on Location, Classification, Physical Characteristics, Traffic Control Devices, Railroad data, Highway data. Posted on both sides of the Crossing Responsibility for posting is the Railroad Aluminum motorcycle license-plate size Alternative posting on ENS Sign

8 Inventory Form

9 Requirements (for it to work) Every Railroad & State Agency needs to maintain an Inventory of all Crossings Each Crossing must be assigned a DOT Inventory Number which is posted at the Crossing Private Company Rail Yards, Docks, etc. Railroad Yards can have just one (1) Number DOT Number is Required on Accident Reports So, inventory ALL of your crossings now, and there will not be a problem later.

10 Initial Numbering and Filing Responsibility of the Operating Railroad Public at-grade: Complete Parts I IV and forward to the State to complete Part V Private: Complete Part I and send to FRA Send copy to State FRA only accepts Inventory Updates from the State Inventory Contacts or the Railroad Inventory Contacts

11 Responsibility for Updating Responsibility is both State and Railroad - Whenever any characteristics change - As a minimum, review and update data at least every three years to keep File current Responsibility for QZ is the Public Authority For a Pre-Rule Quiet Zone To create a New Quiet Zone Must provide updated crossing inventory data prior to use of the QZ Calculator

12 How to Update for Public Authorities aa 3 Step Process (1) Use Crossing Inventory Form F Or Current Inventory Record printout - Reference FRA s Website for a copy of the Form, Instructions and Contact List (State and Railroad), and other information. (2) Perform a Site Survey obtain updated data - Contact the Railroad and State for correct current information (3) Forward Updated Form/Record to the State Inventory Contact to verify and send to FRA

13 Send Hardcopy by Hardcopy Updates can be sent via Use pdf Format Send to:

14 Inaccurate Data Mismatches A Big Problem Example of Accident Data for Accident Reports that have NO Inventory Record 290 have different Warning Devices (active/passive) 40 were Closed at time of Accident 19 were Grade Separated 11 were in different States 143 were in different Counties Railroad Accident Reporting Officers Need of Verify the Accident Reports with the National Inventory File BEFORE Filing, and make any necessary corrections.

15 New Importance of Inventory since September 11 th HOMELAND SECURITY HOMELAND SECURITY Private Crossings must be included for 911 Centers. Data Files are downloaded from National File Need Accurate Data Correct Crossing Location and Ownership Correct Emergency Railroad Contact How can a Railroad be contacted about a Security Breech? Where am I? - Crossing Number identifies Location What Railroad? - Which Railroad owns this Crossing? Who do I contact? - What is the telephone number to report a Problem?

16 Sign for State of Texas Posted on Signal Mast

17 Installed SEDA-COG ENS Signs Public Crossing Private Crossing

18 Sign Posted where there is no Post

19 Availability of Crossing Inventory Data How to get Crossing Inventory Data from FRA?

20 Current Availability of Data Website (.dbf file) Current and Historical Records GX32 (.mdb Access file) obtain directly from our Contractor CITI WBAPS (Web Based Accident Prediction System) PCAPS (Personal Computer Accident Prediction System)

21 Website Inventory Data FRA Home Page -

22 Website Inventory Data Safety Data Home Page

23 Website Inventory Data

24 Website Inventory Data

25 Website Inventory Data

26 Website Inventory Data

27 Website Inventory Data Download Data

28 Current Availability of Data Website (.dbf file) (.mdb Access file) GX32 obtain directly from our Contractor CITI WBAPS PCAPS (Web Based Accident Prediction System) (Personal Computer Accident Prediction System)

29 GX32 Software Package

30 GX32 Software Package

31 Current Availability of Data Website GX32 WBAPS PCAPS (.dbf file) (.mdb Access file) (Web Based Accident Prediction System) (Personal Computer Accident Prediction System)

32 WBAPS Web Based Accident Prediction System Basically the same as PCAPS Provides a Ranking of Crossings by the highest Risk of Predicted Accidents Based on fixed Inventory Characteristics and 5 Years of Accident Data 2 Versions of Accident Data (1) Fixed 5 Years of Annual Data (2) Floating 60 Months of Cyclic Data

33 WBAPS Accident Prediction Model

34 WBAPS (continued)

35 WBAPS (continued)

36 WBAPS Ranked List

37 Current Availability of Data Website GX32 WBAPS PCAPS (.dbf file) (.mdb Access file) (Web Based Accident Prediction System) (Personal Computer Accident Prediction System)

38 PCAPS Personal Computer Accident Prediction System Basically Allows the same as WBAPS for Corridor Analysis to play what if games - built in calculator Allows

39 What is coming? New Inventory Form Additional Data Elements Revised File Structure New Instructions Legislation making the Inventory Mandatory

40 Four OUTREACH MEETINGS A Dialogue to Identify and Explore New Ideas and Ways for Future Improvement Dallas, TX, November 8, 2001 Washington, DC, March 5, 2002 Chicago, IL May 7, 2002 Los Angeles, CA June 25, 2002

41 History of Outreach Effort Nov 2001 to June Four Outreach Meetings Sept 1, 2006 Contractor Analyzes Suggested Changes Dec 15, 2006 Prepared Report Categorizing Changes into Three Groups: (1) Accepted, (2) Rejected, (3) Open for Additional Discussion Dec 20, 2006 Report ed to States and Railroads Requesting Review and Comment Jan 2007 Resent Report to States and Railroads February 2007 Contractor telephoned all States and Railroads again Requesting Review and Comment March 15, 2007 Final Comments and Responses were Received April 15, 2007 Comments Compiled for Final Review by FRA to Determine Planned Changes

42 Responses Received Received 30 Responses from 23 States and 6 Railroads Railroads States Some Responding: BNSF, CN, CSX, LIRR, NS, UP Responding: AL, AZ, CA, DE, GA (2), IL, IO, KS, LA, MD, MA, MN, MS, NJ, NY, OR, PA, SC, SD, TN, VA, WV, WI responses provided many good suggestions that are being considered and incorporated.

43 Next Steps Complete Determination of Accepted and Rejected Changes Prepare List of Changes and Proposed copy of New Inventory Form Disseminate to State and Railroad Inventory Contacts, and put on FRA s Website for final Comment Review and Consider any final Comments Prepare final New Form Prepare New Instructions and Field Specifications Publish and set Effective Date for Implementation

44 Probable Accepted Revisions What do we need at the National Level? Initiating Agency: Add Transit Crossing Number: Move to Right-hand Corner Reason for Update: Add Abandoned Out of Service/Inactive Transfer (to New Operating Railroad Company) Administrative Correction (fix errors) Re-Open Date Change Only Multiple Oper. RR s: (will probably not Accept) 2nd Operating Railroad Company Div, Sub-Div, Branch, Milepost, RRID,Train Counts Will Move Field Does another RR Operate over Track Railroad Milepost: Add space for Prefix & Suffix

45 Probable Accepted Revisions (continued) Increase many Field Lengths e.g., Street Name, RRID, Change Type of Passenger Service to Type of Train Service : Add & Check all that apply : Freight (default); Amtrak, Commuter, Transit, Light Rail Shared, Tourist/Other Move ENS Sign Installed to Highway Signs Section Quiet Zone: FRA only will populate this field Crossing User: Highway Vehicle OR Pedestrian/Other Crossing Type: Public OR Private Position (same): At-grade OR RR Over OR RR Under

46 Probable Accepted Revisions (continued) Average Passenger Train Count: Add Check box for: Less than One Train per Day Add Update Year to: Train Counts & Highway Counts Combine Private Crossing Category and Type of Development and Change Farm to Farm/Open Space Add: Institutional (e.g., Military and Educational Facilities, etc.) Delete: County Reference Map (use Item 29.D. State Use ) Is Commercial Power Available (of little use) Add: USNG Number FRA will calculate this from the Latitude/Longitude Values

47 Probable Accepted Revisions (continued) Emergency Contact, Railroad Contact, State Contact FRA will populate these fields with known telephone numbers if data is not provided. Highway Traffic Control Devices: Add Yield Sign Pre-Signal Advanced Warning Signs; W10-2, -3, -4, -5 Boxes to check Surface Provide for multiple surfaces Plus lots of Clarifications in the Instructions Crossing

48 What is Still Needed? Legislation to make the Inventory Mandatory Is in process Define Required Fields (see Responsibility Table ) Important for Updating if Inventory is Mandatory Primary Responsibility for the Updating of each Data Field is defined in the Responsibility Table When Railroads change Warning Devices It is the Railroad s Responsibility to Notify the State and FRA of the change.

49 How to Start Updating for Data Reconciliation Agree on Crossing Numbers for all Open Crossings Agree on Operating Railroads (or States) Agree on State and County Location Agree on Type: Public or Private and Position: At-grade or Grade Separated Assign New Numbers Close Others When Resolved and Data File Agreement is Reached Then Update the Balance of Data Items

50 Have Questions or Need More Information? Contact: Tom Woll or

51