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
Slope Flattening | Safe Design

Slope Flattening

DEFINITION AND DESCRIPTION

Slope flattening reduces the steepness of the roadside and median slopes so that errant motorists are more likely to keep their vehicles stable, regain control, and avoid obstacles. Slopes of 4H:1V or flatter are recoverable (i.e., motorists can retain control of a vehicle by slowing or stopping). Slopes between 3H:1V and 4H:1V are generally considered traversable, but non-recoverable (i.e., the errant vehicle will continue to the bottom of the slope).

Foreslopes, or fill slopes, are parallel to the flow of traffic and are negative slopes extending from the roadway shoulder down to the ditch or toe. The backslope is a positive slope that extends upward from the base of the foreslope or toe of the ditch. Transverse slopes are not parallel to the roadway and are usually created by median crossovers, berms, driveways, or intersecting roadways.

Implementation Categories

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

CONSIDERATIONS

  • Slope flattening can improve fill slope stability and safety.
  • Right-of-way or space constraints may restrict usage.
  • When restrictions prevent slope flattening, roadside barriers are an option to shield steep embankments.
  • See AASHTO’s Roadside Design Guide (RDG) for more information on recoverable slopes and clear zone distances.
  • Can be done on new construction or reconstruction projects or at high-risk sites (e.g., outside of curves, near fixed objects) to improve safety.
  • On large earthwork projects with excess material, a false ditch / false cuts in steep embankment areas to simulate the effect of a cut slope and provides a wider recovery area.
  • Coordinate with drainage design—flatter slopes may change ditch capacity and runoff.

APPLICATION

  • When feasible, design or correct side slopes with recoverable or traversable foreslope and back slope gradients the width of the clear zone. Slopes of 4H:1V or flatter are preferred for foreslopes.
  • Transverse slopes of 6H:1V or flatter are recommended, particularly for sections immediately adjacent to traffic. On high-speed roadways transverse slopes are often 10H:1V or flatter.
  • In clear zones, include traversable headwalls unless the headwall is protected by a barrier. See KYTC’s Drainage Manual (DR-606.5) and the Sloped and Mitered Concrete Headwall detail sheets for additional information on safety headwalls and their applications
  • Coordinate slope design with drainage and maintenance needs.

example

complementary SSA Strategies

REFERENCES AND RESOURCES

AASHTO. Roadside Design Guide. 4th ed. American Association of State Highway and Transportation Officials, Washington, DC., 2011.

FHWA. Roadside Design Improvements at Curves. https://highways.dot.gov/safety/proven-safety-countermeasures/roadside-design-improvements-curves

Highway Knowledge Portal. Clear Zone Concepts. https://kp.uky.edu/directory/knowledge-books/clear-zone-concepts-knowledge-book/

[wpforms id="3461"]

CONTACT:

Jill Asher

Research Engineer 

jill.asher@uky.edu