Skip to content
FHWA Safety: First graphic from left courtesy of (http://www.pedbikeimages.org/Dan Burden)

Indiana 2006 Five Percent Report

This report is in response to the Federal requirement that each state describe at least 5 percent of its locations currently exhibiting the most severe highway safety needs, in accordance with Sections 148(c)(1)(D) and 148(g)(3)(A), of Title 23, United States Code.  Each state’s report is to include potential remedies to the hazardous locations identified; estimated costs of the remedies; and impediments to implementation of the remedies other than costs.  The reports included on this Web site represent a variety of methods utilized and various degrees of road coverage.  Therefore, this report cannot be compared with the other reports included on this Web site.

Protection from Discovery and Admission into Evidence—Under 23 U.S.C. 148(g)(4) information collected or compiled for any purpose directly relating to this report shall not be subject to discovery or admitted into evidence in a Federal or State court proceeding or considered for other purposes in any action for damages arising from any occurrence at a location identified or addressed in the reports.

Additional information, including the specific legislative requirements, can be found in the guidance provided by the Federal Highway Administration,
http://safety.fhwa.dot.gov/safetealu/fiveguidance.htm.


HIGHWAY SAFETY IMPROVEMENT PROGRAM
INDIANA “5 PERCENT REPORT”

This report is to meet the requirement for Indiana to submit an annual report describing not less than 5 percent of their highway locations exhibiting the most severe safety needs. The intent of the report is to raise the public awareness of the highway safety needs and the challenges that exist.

Extent of Coverage

The crashes used for this report are for the calendar years of 2003, 2004 and 2005 obtained from the Indiana State Police. The extent of coverage is for Interstate, US and State Roads, those administered by INDOT. The only intersections included are those at intersections of INDOT to INDOT administered roads. The report does not include local roads.

The crash records were assigned first to some 1085 intersections if the crash fell within 250 feet of the intersection. The remaining crashes were assigned to segments of which there were 19,262.

Fatal and injury crashes were combined and assigned. All injury crashes were used since at this time serious injury crashes are difficult to distinguish.

Explanation and an Estimated Schedule of when Full Coverage will be Reported

The present report is based on the approximate 11,700 miles of INDOT administered network and does not include local roads. There was not time to develop a complete road network. An investigation will be made to determine what road networks are available. The state wide transportation model does contain a road network of approximately 30,000 miles which will be considered. It is also a possibility that the state and local road inventory network could be used which would give 100% coverage. At any rate next years report will be expanded considerably.

Approximately 80% of the crashes had sufficient information that they could be matched to an intersection or road segment. Processes being developed will improve on the number of crashes that can be assigned.

Methodology Used to Determine 5% most Hazardous Locations

For each intersection and road segment five measures of safety and evaluation criteria were calculated. These are the fatal-injury Annual Crash Frequency, fatal-injury Annual Crash Density, fatal-injury Crash Rate, fatal-injury Index of Crash Frequency and the fatal-injury Index of Crash Cost.

Appendix B contains a Working Report that explains these measures in detail and the procedures used to produce them.

Because the index of crash costs represents a measure of the impact that crashes have on society it was chosen as the factor to determine Indiana's segments and intersections that exhibit the most severe safety needs. Those intersections and segments that had 4.0 standard deviations more crash cost than could be expected were chosen. The number of fatal and injury crashes for these selected intersections and road segments were then summed. It was found that they represent approximately 7.2 percent of the fatal-injury crashes for 2003 through 2005. Therefore these intersections and roadway segments represent more then the minimum requested.

There were 93 roadway segments selected out of the 19,262 roadway segments analyzed and 11 intersections out of 1,085. This shows that 0.51% of the segments and intersections analyzed accounted for 7.2% of the fatal-injury crashes.

A listing of the intersections and road segments can be found in appendix A.

Assessment of Potential Remedies, their Estimated Costs, and Impediments to their Implementation

Detailed improvement remedies and costs are currently not available for each segment or intersection. Each road segment and intersection was compared to projects either planned or under construction. Under the potential remedy column an “A” indicates that the road segment or intersection needs to be reviewed, an “X” means that a project presently exists that will mitigate the safety need. There were several locations where projects are scheduled but since the project does not necessarily mitigate the safety need an “A” was assigned and the safety need will be reviewed. Included in the table are Project Designation numbers (DES#), improvement type and the estimated cost. Projects that are already planned will be reviewed to see if the proposed project can incorporate mitigation of the safety need.

Approximately 30 of the severe safety need locations have projects planned that will mitigate the safety need. Another 74 locations did not and will be evaluated and programmed for future project if practical.

The above mentioned listing will be shared with the districts for consideration in the next call for projects and as projects develop, the costs and remedies will be included in the annual “5 percent report”.

5% Locations for Indiana
RouteSeg/ IntRef Post FromRef Post ToDescriptionCountyDistrictPotential Remedy Projects - Scheduled or Recently Let
DES #Estimated Yr of CnProject TypeCost $(millions)
U-012SEG0+000+06From Illinois St line to the SW ramp B to I-90LAKELaPorteA06000032010HMA.804
S-045SEG38+1338+28From the N Jct with SR 37 East 0.15 miMONROESeymourANONE   
S-144SEG7+007+20From the Morgan Co Ln to SR 37JOHNSONSeymourX9611710&05003972006Int Imp1.172
I-065SEG7+368+26From SR 60 to.0.84 mi S of SR 311CLARKSeymourX92419652006ATR10.114
U-040SEG67+5768+09From 0.30 mi W of then to the Marion Co LnHENDRICKSCrawfordsvilleA85620702006ATR9.818
S-933SEG0+000+26From the Elkhart Co Ln W to the Osceola Corp LnST JOSEPHLaPorteANONE   
S-048SEG35+8735+93From SR 37 W 0.60 MiMONROESeymourANONE   
U-031SEG101+31102+50From Hilltop Dr W to the Marion Co LnJOHNSONSeymourA01013752006Partial 3R.333
U-030SEG6+857+11From 0.03 mi W of Pine Isl St to Scherriville/ Merrillville City Limits LAKELaPorteANONE2007HMA 
U-006SEG27+7027+84From 0.32 mi E of SR 46 to "Old Hwy SR 49"PORTERLaPorteANONE   
S-026SEG38+5638+65From 0.9 Mi W of Creasy Ln to Creasy Ln in LafayetteTIPPECANOECrawfordsvilleANONE   
S-019SEG114+92114+96From 0.12 mi S to 0.08 S of Franklin St in ElkhartELKHARTFort WayneX980113020093R/4R17.859
S-002SEG13+6913+82From SR 35 to SR 4 in LaPorteLA PORTELaPorteA03004972004HMA.955
U-031SEG160+78160+87From .09 mi S of Lincoln Rd to Lincoln Rd in KokomoHOWARDGreenfieldA0300866&02000942006Partial 3/R4.359
U-031INT162+41 US 31 at US 35HOWARDGreenfieldANONE   
I-065SEG0+891+19From 0.43 mi to 0.13 mi S of Stanisfer Ave in Jeffersonville/ClarksvilleCLARKSeymourA9966920   
U-030SEG4+995+06From 0.01 mi W of to 0.06 mi E of Cline Ave in SherervilleLAKELaPorteANONE2007HMA 
U-031SEG129+50129+69From 0.11 mi N to 0.30 mi N of 146th St in WestfieldHAMILTONGreenfieldANUMEROUS   
U-040SEG102+67103+53From CR 600 E to 0.03 mi E of CR 700 EHANCOCKGreenfieldA0400522   
S-111SEG35+6035+34From 0.34 mi S of SR 60 to SR 60CLARKSeymourX990254020083R/4R22.143
S-037SEG171+33171+44From 0.01 mi S of 141st St to 0.10 mi N of 141st StHAMILTONGreenfieldX04003612015ATR59.760
S-252SEG0+000+15From SR 37 E 0.15 mi.MORGANSeymourA0600272   
S-025SEG72+9273+00From 0.08 mi S of SR 17 to SR 17CASSLaPorteX030077320093R/4R5.000
U-031SEG69+5069+73From Beam Road to SR 46 (25th St) in ColumbusBARTHOLOMEWSeymourX97002302008ATR25.667
I-074SEG34+0539+36From the Bridge over CSX RR (0.13 mi East of US231) to SR 32 NE of CrawfordsvilleMONTGOMERYCrawfordsvilleA05012412008HMA8.000
S-018SEG103+24103+49From Western Ave to D St. in MarionGRANTFort WayneANONE   
U-030SEG11+0411+10From 0.06 mi W of then to Mississippi St in MerrillvilleLAKELaPorteANONE2007HMA 
U-024SEG68+6671+96From 1.36 mi E of to 2.16 mi W of CR 700 E East of LogansportCASSLaPorteANONE   
U-231SEG203+76203+85From 0.13 mi S of River Rd (0.45 mi N of Wabash River) to 0.04 mi S of River RoadTIPPECANOECrawfordsvilleANONE   
S-311INT6+00 SR 311 at SR 60CLARKSeymourX96117202004INT IMP3.313
U-030INT10+10 S 30 at SR 53LAKELaPorteANONE   
U-421INT231+90 US 421 at US 20LA PORTELaPorteX97034002006INT IMP2.703
S-046SEG83+0583+13From 0.67 mi E to 0.75 mi E of the Brown Co LnBARTHOLOMEWSeymourA02013492006Partial 3/R4.388
S-045SEG46+4247+96From Earl Young Rd to Tunnel Rd Northeast of BloomingtonMONROESeymourANONE   
S-311SEG4+585+04From 0.46 Mi S of then to the Floyd Co LnFLOYDSeymourX96117202005INT IMP3.313
U-030SEG9+569+77From 0.54 to 0.33 mi W of SR 53LAKELaPorteX05011012007SAFETY2.500
U-030SEG11+9212+12From 1.22 mi to 1.42 mi E of I-65LAKELaPorteANONE2007HMA 
S-037SEG143+93144+23From 0.32 S to 0.02 mi S of Epler Ave in IndianapolisMARIONGreenfieldX0201319&04006782006ATR11.029
I-064SEG123+32123+61From the bridge over Spring St to the Kentucky St lnFLOYDSeymourX05003072014ATR17.734
U-041SEG277+59277+85From 121st st to 119th St in HammondLAKELaPorteX02010802004SIG INT.065
S-135SEG132+36132+52From Faith St to Main St in GreenwoodJOHNSONSeymourANONE   
U-052SEG48+7648+56From 0.1 mi N of Kossuth St to Kossuth St in LafayetteTIPPECANOECrawfordsvilleANONE   
S-032SEG78+4578+51From Elm St to US 31 in WestfieldHAMILTONGreenfieldANONE   
U-052SEG42+0742+15From 0.08 mi W of then to Moorhouse RoadTIPPECANOECrawfordsvilleANONE   
S-120SEG0+000+48From Middleton Road (Elkhart Corp Ln) then E 0.48 miELKHARTFort WayneANONE   
S-039INT20+46 SR 39 at SR 67 (North Junction)MORGANSeymourX0600273&05008442009ATR3.45
S-007SEG17+7518+48From 0.04 mi S to 0.69 mi N of CR 330 S Southeast of Mt VernonJENNINGSSeymourANONE   
U-031SEG124+18124+24From 106th St N 0.06 mi in CarmelHAMILTONGreenfieldX06001062006SIGNALS0.076
U-036SEG20+6620+72From 0.06 mi W of then to Raceway Road (Marion / Hendricks Co Ln)HENDRICKSCrawfordsvilleX01011152011ATR1.000
S-010SEG73+4573+89From Linden Rd to US 31 East of ArgosMARSHALLLaPorteA03004962003HMA1.787
S-055INT104+21 SR 55 at US 30LAKELaPorteANONE   
U-020SEG44+0644+92From Meer Rd (CR 600 W) to I-94 Southeast of Michigan CityLA PORTELaPorteANONE   
U-421SEG222+74222+92From CR 400 S to CR 375 S North of WestvilleLA PORTELaPorteX02013022010ATR7.351
I-080SEG0+000+33From Illinois State Line E 0.33miLAKELaPorteANumerous   
S-037SEG140+53140+72From Johnson Co Line N 0.19 miMARIONGreenfieldX03002132006SIG MOD0.032
U-031SEG69+7369+80From SR 46 (25th St) N to Haw Creek BlvdBARTHOLOMEWSeymourA9700230   
U-012SEG7+617+63From 0.02 mi E of then to Cline AveLAKELaPorteANONE   
U-031SEG68+2268+25From 0.74 mi N of Base Road to CR 50N SE of ColumbusBARTHOLOMEWSeymourX0014820&030026820083R/4R27.662
S-933SEG108+50108+63From 0.03 mi W of Baker St East to .01 mi E of Taylor St in MishawakaST JOSEPHLaPorteANONE   
S-009SEG46+3346+50From US 40 (Main St) to Grant St in GreenfieldHANCOCKGreenfieldA04005212007HMA1.261
U-020SEG95+0095+25From 0.60 mi W to 0.35 mi W of CR 17 Bridge over US 20ELKHARTFort WayneANONE   
S-120SEG4+845+71From CR 17 E 0.87 miELKHARTFort WayneANONE   
S-135SEG133+92134+00From 0.08 mi S then to the Marion Co LnJOHNSONSeymourANONE   
S-053SEG1+251+34From 0.09 mi S of then to North St (109th St) in Crown PointLAKELaPorteANONE   
S-055SEG101+19101+43From Summit St (105th St) to Birch St in Crown PointLAKELaPorteANONE   
U-041SEG11+6611+78From 0.58 mi S to 0.46 mi S of I-70 (Johnson Ave) in Terre HauteVIGOCrawfordsvilleANONE   
I-065SEG2+082+17From the Eastern Blvd Bridge over I-65 then N 0.11 mi in JeffersonvilleCLARKSeymourA9018850   
U-052INT49+91 US 52 at SR 25TIPPECANOECrawfordsvilleANONE   
I-065SEG0+000+32From the Ky St Ln to Br over Court/Fourth/MarketCLARKSeymourA99669202006ATR 
S-135SEG131+82132+01From 0.20 mi S then N to Smith Valley RoadJOHNSONSeymourANONE   
U-031INT81+39 US 31 at SR 252JOHNSONSeymourA03000502003Partial 3R1.089
U-231SEG272+10273+09From 8th St to 8th Ave in De MotteJASPERLaPorteANONE   
U-020SEG29+6429+94From Oak Hill to Waverly Rd in ChestertonPORTERLaPorteANONE   
U-024INT115+13 US 24 at SR 9 (W Jct)HUNTINGTONFort WayneANONE   
S-267SEG18+2918+39From 0.27 mi S to 0.17 mi S of I-74HENDRICKSCrawfordsvilleX96089302007MED CN4.674
S-038SEG72+6172+82From US 36/SR 67 E 0.21 miMADISONGreenfieldX9703270&05000422007INT IMP1.092
U-040SEG7+327+53From 9th St to 11th St of EB one way pair in Terre HauteVIGOCrawfordsvilleANONE   
S-057SEG49+4849+53From Southside Ave/ Troy Rd to Old US 50 in WashingtonDAVIESSVincennesANONE   
I-065SEG0+390+61From 0.22 mi S of then to the bridge over 7th St in JeffersonvilleCLARKSeymourA90188502006ATR 
U-024SEG38+2939+63From CR 300 E to CR 400 E W of MonticelloWHITELaPorteX0500525&05000582009INT IMP1.340
U-136SEG65+6566+01From 0.39 mi E of then to Hamstra Rd/ CR 600 E in BrownsburgHENDRICKSCrawfordsvilleANONE   
S-003SEG195+91196+35From SR 8 then N 0.44 miNOBLEFort WayneX0401187&03009232011INT IMP0.800
S-056SEG117+67117+90From Beechwood Ave to Park Ave is ScottsburgSCOTTSeymourANONE   
U-035SEG173+44174+02From CR 25 N to SR 8 North of KnoxSTARKELaPorteANONE   
U-041SEG270+82271+07From 175th St to 173rd St in HammondLAKELaPorteA86658702006Mj PVMT9.321
U-041SEG266+39266+53From 45th St to 0.14 mi N in HighlandLAKELaPorteX91336252003ATR18.088
U-006SEG19+5319+54From 0.01 mi W of then to Swanson Rd in PortagePORTERLaPorteX92999352007ATR21.742
S-009SEG47+2247+31From Michigan St to McKenzie Rd in GreenfieldHANCOCKGreenfieldX971005A2004INT IMP0.107
U-041INT263+18 US 41 at US 30LAKELaPorteANONE   
I-065SEG229+82231+57From 1.68 mi S of then to the Newton Co LnJASPERLaPorteANONE   
S-257SEG31+2631+29From Grove St to Old US 50 in WashingtonDAVIESSVincennesANONE   
U-030INT33+74 US 30 at US 421LA PORTELaPorteX050070520053R/4R2.700
I-265SEG0+000+32From I-64 then 0.32 mi EFLOYDSeymourX041133&05011792004INT MOD0.775
U-041SEG3+463+55From 0.15 mi S of Lincoln Ave to Walnut St in EvansvilleVANDERBURGHVincennesA0501073&99032402006FLASHER0.009
S-124SEG47+7248+10From 0.41 mi W to 0.03 mi W of the Wabash RiverWELLSFort WayneANONE   
U-031SEG97+2497+57From Tracy Rd (CR 600 W) to 0.13 mi N in New WhitelandJOHNSONSeymourANONE   
U-031SEG158+99159+01From 0.07 mi S of Arrow St to Center Rd in Indian HeightsHOWARDGreenfieldA0300866&02000942004Partial 3/R4.359
S-025SEG44+9545+03From 0.07 mi W to 0.01 mi E of Earl Ave (22nd St) in LafayetteTIPPECANOECrawfordsvilleA01006992009PVMT9.900
U-040SEG100+65101+66From CR 400 E to CR 500E E of GreenfieldHANCOCKGreenfieldA04005222006HMA3.077
U-050SEG103+20103+56From 0.01 mi E of Hancock St to Jackson Park Dr in SeymourJACKSONSeymourA89236452000ATR6.745
S-009SEG48+2948+33From 0.19 mi N of Muskegon Dr to CR 200N in GreenfieldHANCOCKGreenfieldA04005212006HMA1.261
S-110SEG12+5813+24From 0.07 mi E of US 31 to Michigan RdMARSHALLLaPorteANONE   
I-865SEG904+34904+72From 0.38 mi W of then to I-465BOONECrawfordsvilleX04008822018INT MOD57.5
S-026SEG45+3146+35From 0.03 mi E of CR 990E to Clinton County LineTIPPECANOECrawfordsvilleANONE   
ATRAdded Travel Lanes
INT IMPIntersection Improvement
HMAHot Mix Asphalt Resurface
INT MODInterchange Modification
FLASHERInstall Flashing Light
3R/4RResurface and Bring Roadside up to appropriate 3R/4R Standards
Partial 3/RResurface Minimal Roadside Imprvements
PVMTPavement Replacement
MED CNConstruct Median
SIG INTSignal Interconnect
SIGNALSSignal Installation
SIG MODSignal Modification

REVISED as of Oct 30, 2006

Working Report to Assist INDOT
In Preparation of the 5-percent Report for 2006

REVISED September 8, 2006

Andrew Tarko
August 13, 2006

INTRODUCTION

This working report summarizes the data and measures of safety used to develop lists of segments and intersections in Indiana included in the attached Excel file. This report is meant to help the Indiana Department of Transportation write the 5% report requested by FHWA.

DATA

The data used to develop the lists include: crash data, segment data, and intersection data. The crash data has been extracted from the Indiana State Police Crash Database. The source files are in the text format and include records of all crashes reported on public roads in Indiana in the period of 2003-2005.

The segment data were in the format of a dbf table. It is a part of he Indiana Travel Demand Model and it includes all the segments administered by the Indiana Department of Transportation. These segment data were extracted by INDOT from the Indiana Roadway Inventory Database, supplemented with geographic coordinates and other data, and converted to the dbf format required by the TransCAD. The recent Annual Average Daily Traffic values were included in the segment table.

The intersection data also takes the form of a dbf table and it has been generated with the tool called INSIP (INput to Safety In Planning tool) developed by the Purdue University research team. The segment data were used to identify all the network nodes where at least three state road segments meet. The table of state network nodes includes location, traffic, and geometry data extracted from the road segment table and converted as needed.

The data currently available allow analyzing road segments and intersections administered by INDOT. Inclusion of local roads will be considered for the next year 5% report.

METHOD

The procedure of ranking road locations by level of hazard requires crashes assigned to these locations and proper measures of the safety level.

Assigning crashes to the road network

The crashes reported during the three-year period 2003-2005 obtained from the Indiana State Police were assigned to the Indiana network using the INSIP tool. The original text files were reformatted to fit the TransCAD requirements. A total of 16 tables were created from which the tables consisted of type 10 records were further used. This record type includes all the information needed for the analysis: GIS coordinates of most crashes (app. 80%), names of the streets, time, date, and severity of crashes. In the first step, the INSIP assigned crashes to network nodes based on the geographical proximity. The 250 feet criterion was used according to which any crash that occurred on a road within 250 feet from the center of an intersection is assigned to that intersection. In the next step, the remaining crashes are assigned to the nearest road segments. The outcome of this procedure is the crashes assigned to segments and intersections counted by year and severity. The obtained counts have been attached to the original interaction and segment tables.

The crash assignment procedure also generates a set of tables that link the crash records, with segment and intersection records. They allow checking the detail information about the crashes assigned to specific segments and intersections. These tables were used to verify the correctness of the crash assignment results by displaying on a TransCAD map the crashes assigned to several selected segments and intersections. The check has confirmed good quality of the assignment.

Measures of Safety and Evaluation Criteria

Locations can be ranked (sorted) from two general points of view:

(1) System wide perspective, and
(2) Individual user perspective.

The systems perspective aims to reduce as many crashes as practical in the studied area and to promote the most cost-effective mitigation of hazard. The user perspective aims to reduce the excessive risk faced by individual users, which promotes fairness of the highway system by reducing the difference between risks faced by users at different locations. These two perspectives yield different rank lists.

Annual crash frequency is a system perspective criterion used for intersections. It is a basic measure of crash experience and easy to use as it requires only crash data. The crash frequency is estimated by dividing the number of crashes by the number of years. Selecting locations with a high crash frequency does not consider exposure to risk, i.e. does not take into account volume or vehicle miles traveled (VMT).

Annual crash density is a system perspective criterion used for segments. It provides the normalized annual crash frequency on segments and it is expressed in number of crashes per mile per year.

Crash rate is a user perspective criterion. It is the number of crashes divided by the amount of exposure to risk at the location. For an intersection, a crash rate is calculated as the annual number of crashes per million vehicles entering the intersection. For a roadway segment, a crash rate is calculated as the annual number of crashes per million vehicle-miles traveled (VMT).

Neither a crash frequency nor a crash rate considers uncertainty caused by random variability in the annual number of crashes. Consequently, a high value of crash frequency or crash rate may be caused by randomness and not by high hazard. To incorporate consideration of random crash variability, an index of crash frequency and the index of crash cost are calculated.

Index of crash frequency (ICF) measures the difference between expected and reported number of crashes divided by the standard deviation of the difference estimate. It combines the system and user perspectives with a stronger emphasis on the system perspective. For example, ICF = 2 indicates that the number of crashes at the location exceeds the expected number of crashes for that location by two standard deviations. A set of predictive equations is presented Table 1. These equations have been developed for this analysis by fitting the 2003-2005 total crash counts to the segment and intersection data (segment lengths and traffic volumes). Index of crash frequency was calculated using Equation 1.

Equation 1 Equation 1

where :

A=number of crashes during Y years (three years here),
a=typical crash frequency calculated using Table 1,
Y=number of years in analyzed period, in years, and
D=over-dispersion parameter taken from Table 1. The smaller factor, the better crash frequency estimate a.

The index of crash frequency can be used in two different ways. In the first method, locations can be ranked using the index of crash frequency. The sorted locations form a priority list for safety reviews, starting with the location for which the evidence of a high crash location is strongest. In the second method, locations can be sorted by other criteria and then the only ones from the top of the list and statistically significant (let say, ICF >2) are selected.

Index of crash cost (ICC) measures the difference between expected and estimated crash cost at the location divided by the standard deviation of the difference. It incorporates the crash severity and combines the system and user perspectives with a stronger emphasis on the system perspective. For example, ICC =2 implies that the crash cost at the location exceeds the expected crash cost for that location by two standard deviations. A set of predictive equations developed for this study by fitting the counts of injury/fatal and PDO crashes to the segment and intersection data are presented in Table 2. Index of crash cost is calculated using Equation 2.

Equation 2 Equation 2

where:

CPD=average cost of PDO crash, here $6,500,
CIF=average cost of I/F crash, here $65,000,
PD=number of PDO crashes during Y years,
IF=number of I/F crashes during Y years,
aPD=typical PDO crash frequency, in PDO crashes per year,
aIF= I/F crash frequency, in, I/F crashes per year,
Y=number of years in analyzed period, in years,
DPD=over-dispersion parameter for PDO crashes, and
DIF=over-dispersion parameter for I/F crashes.

RESULTS

The Excel file provided with this report includes an Intersection spreadsheet with 1085 intersections and a Segments spreadsheet with 19,262 inventory segments. The color-coded columns have names that are self-explaining or explained in the above part of this report. The blue color indicates location and ID information needed to display the results on an electronic GIS map or to find the segment or intersection on a map. The yellow color indicates all the input values used to calculate the results. The orange color indicates the results. The remaining white columns contain wealth of additional information about segments and intersections. The variable (column) names for segments are explained in the manual for the Travel Demand Model. The variable (column) names for intersections are in the draft final report for the JTRP project on safety-conscious planning. These descriptions can be provided upon request if needed.

The tables can be sorted by any of the columns containing measures of safety as introduced in the previous section of the report. Other can serve as secondary measures. If using measures other than Index of Crash Frequency and Index of Crash Cost, then the segment and intersection lists have to be kept apart and sorted individually. The value of the Indices of Crash Frequency and Cost give an indication of the statistical significance that a location experiences excessive hazard.

Another alternative is to combine the segment and intersection lists and sort the combined list by Index of Crash Cost. Other measures such as crash rate can be used to make a final selection.

In any case, the segments that are too short may be removed.

Table 1 Safety performance functions
FacilitySafety Performance FunctionsOver-dispersion parameter (D)
Intersectionsa = 3.17.Q10.403Q20.416 0.460
Rural non-interstate segmentsa = 2.291LQ0.8090.430
Rural interstate segmentsa = 0.557LQ0.9780.086
Urban non-interstate segmentsa = 4.747LQ0.8600.893
Urban interstate segmentsa = 0.230LQ1.3500.225
a=typical crash frequency in Indiana , in crashes per year,
Q=AADT entering the intersection or along the road segment, in thousand vehicles per day,
D=over-dispersion parameter, and
L=road segment length, in miles.
Table 2 Safety performance functions including severity
FacilitySafety Performance FunctionsOver-dispersion parameter
IntersectionsaIF= 0.913.Q10.271.Q20.4560.257
aPDO= 0.238.Q10.415.Q20.4210.434
Rural non-interstate segmentsaIF= 0.462LQ0.8250.120
aPDO= 1.747LQ0.7930.370
Rural interstate segmentsaIF= 0.065LQ1.0960.005
aPDO= 0.506LQ0.9500.082
Urban non-interstate segmentsaIF= 0.959LQ0.8860.565
aPDO= 3.394LQ0.8700.863
Urban interstate segmentsaIF= 0.913LQ0.4560.257
aPDO= 0.181LQ1.3580.218
aPD=typical PDO crash frequency, in PDO crashes per year,
aIF=typical I/F crash frequency, in I/F crashes per year,
Q=AADT entering an intersection or along the road segment, in thousand veh/day,
L=road segment length, in miles, and
D=over-dispersion parameter.

CLOSURE

The present report does not include local roads due to the lack of sufficiently complete representation of Indiana road network. A progress is being made to include local roads. An effort is planned to incorporate local roads in the next year report. Another issue that needs to be addressed is the frequent lack of data for local roads. It may require modification of the method used this year.

 

Office of Operations FHWA Safety Home