Deprecated: WPDataTables\Vendor\DI\create(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\scope-vendor\php-di\php-di\src\functions.php on line 35

Deprecated: WPDataTables\Vendor\DI\autowire(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\scope-vendor\php-di\php-di\src\functions.php on line 48

Deprecated: WPDataTables\Vendor\DI\ContainerBuilder::writeProxiesToFile(): Implicitly marking parameter $proxyDirectory as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\scope-vendor\php-di\php-di\src\ContainerBuilder.php on line 283

Deprecated: WPDataTables\Vendor\DI\Definition\Source\ReflectionBasedAutowiring::autowire(): Implicitly marking parameter $definition as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\scope-vendor\php-di\php-di\src\Definition\Source\ReflectionBasedAutowiring.php on line 19

Deprecated: WPDataTables\Vendor\DI\Definition\Source\Autowiring::autowire(): Implicitly marking parameter $definition as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\scope-vendor\php-di\php-di\src\Definition\Source\Autowiring.php on line 23

Deprecated: WPDataTables\Vendor\DI\Definition\Source\DefinitionFile::__construct(): Implicitly marking parameter $autowiring as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\scope-vendor\php-di\php-di\src\Definition\Source\DefinitionFile.php on line 28

Deprecated: WPDataTables\Vendor\DI\Definition\Source\DefinitionArray::__construct(): Implicitly marking parameter $autowiring as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\scope-vendor\php-di\php-di\src\Definition\Source\DefinitionArray.php on line 39

Deprecated: WPDataTables\Vendor\DI\Definition\Source\DefinitionNormalizer::normalizeRootDefinition(): Implicitly marking parameter $wildcardsReplacements as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\scope-vendor\php-di\php-di\src\Definition\Source\DefinitionNormalizer.php on line 46

Deprecated: WPDataTables\Vendor\DI\Proxy\ProxyFactory::__construct(): Implicitly marking parameter $proxyDirectory as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\scope-vendor\php-di\php-di\src\Proxy\ProxyFactory.php on line 43

Deprecated: WPDataTables\Vendor\DI\Container::__construct(): Implicitly marking parameter $definitionSource as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\scope-vendor\php-di\php-di\src\Container.php on line 87

Deprecated: WPDataTables\Vendor\DI\Container::__construct(): Implicitly marking parameter $proxyFactory as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\scope-vendor\php-di\php-di\src\Container.php on line 87

Deprecated: WPDataTables\Vendor\DI\Container::__construct(): Implicitly marking parameter $wrapperContainer as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\scope-vendor\php-di\php-di\src\Container.php on line 87

Deprecated: WPDataTables\Vendor\DI\Definition\ObjectDefinition::__construct(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\scope-vendor\php-di\php-di\src\Definition\ObjectDefinition.php on line 72

Deprecated: WPDataTables\Vendor\DI\Definition\ObjectDefinition::setClassName(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\scope-vendor\php-di\php-di\src\Definition\ObjectDefinition.php on line 88

Deprecated: WPDataTables\Vendor\DI\Definition\ObjectDefinition::setLazy(): Implicitly marking parameter $lazy as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\scope-vendor\php-di\php-di\src\Definition\ObjectDefinition.php on line 186

Deprecated: WPDataTables\Vendor\DI\Definition\Resolver\ObjectCreator::setPrivatePropertyValue(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\scope-vendor\php-di\php-di\src\Definition\Resolver\ObjectCreator.php on line 212

Deprecated: WPDataTables\Vendor\DI\Definition\Resolver\ParameterResolver::resolveParameters(): Implicitly marking parameter $definition as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\scope-vendor\php-di\php-di\src\Definition\Resolver\ParameterResolver.php on line 38

Deprecated: WPDataTables\Vendor\DI\Definition\Resolver\ParameterResolver::resolveParameters(): Implicitly marking parameter $method as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\scope-vendor\php-di\php-di\src\Definition\Resolver\ParameterResolver.php on line 38

Deprecated: WDTIntegration\Webhooks\WebhookManagerService::__construct(): Implicitly marking parameter $repository as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\tiers\pro\webhooks\Services\WebhookManagerService.php on line 24

Deprecated: WDTIntegration\Webhooks\WebhookDispatcherService::__construct(): Implicitly marking parameter $repository as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\tiers\pro\webhooks\Services\WebhookDispatcherService.php on line 30

Deprecated: WDTIntegration\Webhooks\WebhookDispatcherService::__construct(): Implicitly marking parameter $payloadBuilder as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\tiers\pro\webhooks\Services\WebhookDispatcherService.php on line 30

Deprecated: WDTIntegration\Webhooks\WebhooksAjaxController::__construct(): Implicitly marking parameter $manager as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\tiers\pro\webhooks\Controllers\WebhooksAjaxController.php on line 18

Deprecated: WDTIntegration\Webhooks\WebhooksAjaxController::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\tiers\pro\webhooks\Controllers\WebhooksAjaxController.php on line 18

Deprecated: WDTIntegration\Webhooks\WebhookDispatchHooks::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead in C:\inetpub\sites\SafeDesign\wp-content\plugins\wpdatatables\backend\tiers\pro\webhooks\Hooks\WebhookDispatchHooks.php on line 15
Increase Use of Roadside Barriers and End Terminals | Safe Design

Increase Use of Roadside Barriers and End Terminals

DEFINITION AND DESCRIPTION

When it is not feasible to remove or relocate a roadside obstacle, it may be shielded by a longitudinal traffic barrier or crash cushion. A roadside barrier redirects or contains errant vehicles, improving safety by preventing more severe outcomes. Barrier examples include guardrail, cable rail, and concrete barriers. 

Barrier end treatments (e.g., anchorages, terminals, crash cushions) are essential components that safely absorb or redirect vehicle impacts at the ends of barriers. Proper end treatment selection and installation are critical, as untreated barrier ends can pose severe hazards.

The Crash Modification Factor (CMF) Clearinghouse contains several CMFs for adding new guardrail along embankments. Guardrail installations can reduce run-off-road injury crashes by up to 47% and fatal crashes up to 44%.

Implementation Categories

Area(s) Design & Geometrics, HSIP, Operations & Maintenance
Safety Category 1

CONSIDERATIONS

  • The Roadside Design Guide uses length-of-need calculations to determine how much barrier is required to shield an obstacle. KYTC applies a fixed 15-degree departure angle, producing shorter barrier lengths than AASHTO’s method. See the Highway Knowledge Portal article Length of Need for more information. For higher-risk sites, KYTC may instead use AASHTO’s calculation or a smaller departure angle to provide added shielding.
  • The Manual for Assessing Safety Hardware (MASH) provides current crash-testing criteria for roadside safety features used on the National Highway System (NHS).
  • Barriers and end treatments may require additional clear width for working width and deflection.
  • Consider review and evaluation of barriers and end treatments on low-volume facilities off the NHS.
  • KYTC’s Guardrail Rating Program prioritizes guardrail installation locations.

APPLICATION

  • Prioritize candidate locations based on crash data, traffic volumes, and roadway characteristics (e.g., curvature, lane width, roadside slopes, fixed-objects).
  • Incorporate barrier installation as part of resurfacing, reconstruction, or safety improvement projects to minimize additional cost.

example

complementary Countermeasures

REFERENCES AND RESOURCES

AASHTO. Roadside Design Guide (RSG) 4th Edition. American Association of State Highway Transportation Officials, Washington DC, 2011.

KTC. Guardrail. Highway Knowledge Portal. 2023. https://kp.uky.edu/knowledge-portal/articles/guardrail/

Howell, Brian K.; Staats, William Nicholas; and Albright, Nancy, “Evaluation of Guardrail Needs and Update of Guardrail Rating Program” (2019). Kentucky Transportation Center Research Report. 1634.
https://uknowledge.uky.edu/ktc_researchreports/1634

Do you have more questions? Get in touch!

[wpforms id="3461"]

CONTACT:

Jill Asher

Research Engineer 

jill.asher@uky.edu