Details
Type: Bulletin
Topic or Program: Access Management
Final Number: AM13-06(B)
Effective Date: 05/01/2013
Updated Date: 08/24/2017
Signature on File: Larry McKinley, Access Management Program Manager
Purpose
The purpose of this Technical Services Bulletin is to provide guidance to ODOT staff when evaluating sight distance in association with approach applications and deviation requests from sight distance standards for approach applications. This Bulletin also applies to sight distance evaluation as part of the “moving in the direction of” criteria for change of use applications and to “optimizing” access locations for properties with no alternate access.
Guidance
This bulletin describes the criteria to use in measuring sight distance as used in the standard approval criteria of OAR 734-051-4020(2)(c). If the standard is not met, guidance is provided when determining if a deviation from the sight distance standards can be approved and suggests an order in which mitigation measures be considered.
Definitions
-
OAR
- Oregon Administrative Rule.
- ORS
- Oregon Revised Statute.
Background/Reference
In 2011, the Oregon legislative assembly passed SB 264. The bill established specific approval criteria for approach applications, one of which is sight distance. ORS 374.311(6) authorizes ODOT to adopt administrative rules for sight distance standards and ORS 374.312(7) authorizes ODOT to approve deviations from the standards. OAR 734-051-4020(2)(c) and 3050(8)-(10), effective June 29, 2012, establish sight distance standards and the procedures and criteria to approve deviations from the standards.
Explanation
Attachment A, “Sight Distance Standards and Deviations,” provides information and guidance on applying sight distance standards and evaluating deviations for different types of approach applications, including “moving in the direction of” and “optimization” evaluations under OAR 734-051-4020(5). It includes a discussion of using design speeds other than those assumed in Table 2 of OAR 734-051-4020(2)(c). Attachment B, entitled “Sight Distance Measurement Procedure for Intersections with Stop Control at the Approach,” describes the procedure for measuring sight distances.
Responsibilities
Department staff in the following positions are responsible for carrying out the guidance in this Bulletin as it relates to their assigned duties and authority:
- Region Managers.
- District Managers.
- Region Access Management Engineers.
- Development Review Coordinators.
- Access Management Coordinators.
- Permit Specialists.
More specific responsibilities include the following:
- Region Roadway Manager
- Responsible for approving the use of a design speed that varies from the assumed design speed that appears in Table 2 of OAR 734-051-4020 if the private development involves any construction on the highway other than the access itself.
- Region Access Management Engineer (RAME)
- Responsible for approving the use of a design speed that varies from the assumed design speed that appears in Table 2 of OAR 734-051-4020 if the private development doesn’t involve any construction on the highway other than the access itself; approving or denying a deviation to the sight distance standards for an approach application; consulting with the Region Manager on deviations that can only be approved by the Region Manager under OAR 734-051-3050(9)-(10); consulting with the Region and/or District Manager on evaluation of “move in the direction of” and “optimized location” proposals that don’t meet the sight distance standards; and specifying mitigation to address inadequate sight distance.
- Permit Specialists, Access Management Coordinators and others
- Responsible for accurate sight distance measurements in the field and collection of other relevant information needed to evaluate sight distance.
- Region Manager
- Responsible for deviations that can only be approved by the Region Manager under OAR 734-051-3050(9)-(10).
Action Required
Implement this Bulletin upon the effective date.
Special Instructions
If problems or concerns develop in implementing this Bulletin, or if further clarification is
needed, contact the Access Management Program Manager.
Attachments