Tribal Transportation |
| < Prev | Top | Next > | |
Executive SummaryIntroduction In 2000, the national average mortality rate from motor vehicle crashes (MVCs) for Native Americans was 32.3 deaths per 100,000 population - more than twice the national average for all races. [16] There are many causes for these high MVC death (and injury) rates, including unsafe roads, driving errors, neglecting the use of passenger restraints, and disregarding the rules of the road. While each of these causes can be addressed in a comprehensive Tribal Highway Safety Improvement Program (THSIP), this document places primary emphasis on the issues and process for improving the safety of roads on reservations. The purpose of this project is to develop a model process and guidelines to improve Tribes' abilities 1) to identify hazardous highway locations, sections, and elements; and 2) to develop and prioritize projects. The goal for implementing the model process and guidelines is to place Tribes in a position to effectively compete for Hazard Elimination Program (HES) and other available highway safety funding. The model process provides Tribes a step-by-step approach to develop a highway safety improvement program (HSIP). The process will help assure a Tribe fully considers the benefits and the costs of implementing a THSIP or safety project. It provides decision-making points, so that a Tribe can make resource commitments in increments or stop the process at logical points. This process draws from highway safety funding source information and the technical and policy guidelines prepared for this project. The process described consists of four major tasks.
The first two tasks of this process focus on the broader issues of creating a THSIP or safety project with no particular emphasis on any funding source. The third task focuses on planning needs for a THSIP or a stand-alone safety project. The last task centers on the implementation of a tribal HES roadway reconstruction project. Highway Safety Funding SourcesThe plan for implementing a THSIP or safety project will depend immensely on which funding sources the Tribe pursues, since each source has different program eligibility requirements. A few important traffic safety funding sources are identified. Some funding sources are exclusively dedicated to highway safety improvements, while other sources can be used for highway safety, as well as other activities. Sources listed include federal and state transportation programs, and programs from non-transportation agencies that can be used for transportation purposes. A Tribe may find it necessary to combine multiple funding sources to address highway safety needs. Policy and Technical Components Nine component guidelines are presented to serve as the principal information sources for this model process. These components are also intended to provide Tribes guidance on the considerations necessary for developing a THSIP. However, the guidelines are not intended to be a "how to" manual for carrying out the various activities associated with the THSIP or a safety project, such as how to collect data, count traffic, fill in a funding application, design a project or administer a reconstruction project. The first three components are policy oriented. The components provide guidance on a decision-making process to operate a THSIP on tribal lands, e.g. data sharing, relationship with a state, tribal roles and organization in the activities and projects, and tribal preparation in the HES projects.
The second six components are technically oriented. The components provide Tribes technical guidance for meeting the HES federal and state requirements.
IntroductionImpact of Motor Vehicle Crashes The term motor vehicle crash (MVC) refers to a crash involving a motor vehicle and another motor vehicle, pedestrian, non-motorized vehicle (e.g. cycle), animal, or fixed object. MVC also includes non-collision crashes, such as loss of control rollover crashes. Tribal members and tribal governments are severely impacted by the high number of MVCs. In 2000, the national average mortality rate from MVCs for Native Americans was 32.3 deaths per 100,000 population - more than twice the national average for all races. [16] Many regions with significant Native American population and tribal lands will most likely have annual average MVC mortality rates worse than the national average. In Arizona, a state with Indian reservations accounting for approximately 27 percent of the land, the mortality rate for MVCs for Native Americans is almost four times the rate for the next closest ethnic group. From 1990 to 2000 this rate was 74.3 deaths per 100,000 population. MVCs are the leading cause of death for ages 1 to 44.[1] This trend continued in Arizona for the year 2002, when the MVC rate for Native Americans was 68.6 deaths per 100,000 population, compared to an average of 20.4 deaths per 100,000 population statewide. [12] There are many causes or combination of causes for these high MVC death (and injury) rates, including unsafe roads, driving errors, not using or the misuse of passenger restraints, and neglecting to follow the rules of the highway. While each of these causes requires attention, this document places primary emphasis on the issues and process for improving the safety of highways on reservations. Highway Safery Improvement Program (HISP)
Highway Safery Improvement Program (HISP) Guidelines The Federal Highway Administration (FHWA) has established requirements for states to follow in the development of HSIPs. [14] The National Highway Traffic Safety Administration (NHTSA) has also developed Highway Safety Program Guidelines, called "Roadside Safety", for a comprehensive HSIP. [19] These guidelines are more in depth than the federal HSIP requirements associated with the Hazard Elimination Program (HES).For a HSIP to be effective, it must include a process that identifies highway safety problems, generates measures to address the problems, implements the measures, and evaluates the results. Each step of the process depends on the availability of roadway data, safety data and traffic records. If these data and records are not substantive, reliable, accessible, accurate, and up-to-date, the program will not likely achieve its goals. Tribal Highway Safery Improvement Program (THISP) Tribal Considerations:
Although a THSIP promotes preparedness thru organization and collaboration, some Tribes may discover thru data analysis that only one highway safety problem exists. In this case, a complete THSIP may not be needed. The Safety Management System Administered by the Bureau of Indian affairs (BIA) and the Tribal Highway Safery Improvement Program (THISP) are coordinated. A THSIP may need to be coordinated with the federally mandated and Bureau of Indian Affairs (BIA) administered safety management system (SMS) requirements, if state or federal funds are used. The SMS requirements will apply to federally and tribally owned roads on the Indian Reservation Roads (IRR) System. FHWA and BIA are implementing the SMS under 23 Code of Federal Regulations (CFR) Part 973, Federal Lands Highway Program; Management Systems Pertaining to the Bureau of Indian Affairs and the Indian Reservation Roads Program. [25] For further information, refer to the guide entitled, "Safety Management Systems: Good Practices for Development and Implementation". [29] The SMS requirements include:
Sections 152 and 130 of 23 United States Code (USC) established the federal HES and Highway-Rail Grade Crossings Programs for public highways. [14, 24] These programs require all states to identify hazardous roadway locations and to prioritize projects developed to eliminate the hazards. About $550 million annually was allocated under the Transportation Equity Act for the 21st Century (TEA-21) for hazard elimination. [26] This amount could substantially increase when the reauthorization process for the fiscal years (FY) 2004-2009 federal surface transportation program is completed. HES funds may be accessed through the states. Following are the general requirements for HES funding as described in 23 CFR, Chapter I, Part 924. [24]
|
|
| < Prev | Top | Next > |
To provide Feedback, Suggestions or Comments for this page contact Kenneth Petty at kenneth.petty@dot.gov.