I am writing in response to your request for the addition of protected-permissive left turn traffic signals at Dixie Trail and Wade Avenue. The City of Raleigh Transportation Department conducted a left turn study for this location. This study included examining current traffic volumes, crash history, and performing field investigations.

There are two main reasons for installing left turn signals at an intersection; (1) to correct a crash problem and (2) to reduce delay. This intersection did not meet the guidelines from the Federal Highway Administration “Signalized Intersection: Information Guide” (FHWA-SA-13-027). NCDOT has also fully adopted these guidelines as standards. These guidelines contain criteria for the consideration of the installation of Left-Turn Phasing (protected-permissive, permissive-protected or protected only) traffic signals. Some of this criteria used include traffic volumes and turning movement counts for peak times of a typical day. In addition, recent crash history is also analyzed for particular crashes that may be considered correctable by the installation of protected-permissive left-turn phasing and the minimal sight distance for the turning phases are satisfied.

Crash history shows that for the last 5year study period from 2/28/2015 thru 2/29/2020 there have been 3 reported left turn crashes from the same approach at Dixie Trail and Wade Avenue, which might be considered correctable by the installation of protected-permissive left turn signals. This location does not meet the crash warrant criteria for consideration of a traffic signal, which are 5 or more crashes in a recent 12 month study period.

Traffic volumes were studied checked and found that the intersection of Dixie Trail and Wade Avenue did not meet the cross product threshold lower limit for the installation of protected left turn signals. Based on the traffic signal study the Transportation Department can not recommend left turn signals be installed for this location at this time.

This issue has been closed. If the problem persists, please re-open this issue and give us more detailed information on how to identify the location of the problem - then we will get right on it. Thanks a lot for reporting!