Enjoy (?) this collection of near misses and collisions collected over the past year and a half. The City of Everett has declared the existing traffic controls at this intersection to be “appropriate” and they refuse to make any changes to the design.
And of course these are just the ones that happened while we were home and checked the camera after hearing the commotion.
Update: One of my neighbors contacted the city yet again to request some sort of improvement at this intersection and the similar one a block north. Here is the city’s reply, in part:
It appears that no crashes have been reported to the Everett Police at the intersection of 36th Street and Wetmore Ave in recent years. The intersection of 35th Street and Wetmore Ave does have an average of 1.5 reported crashes per year, but only about 1 crash every 2 years results in any injuries. While ideally there would be no vehicle crashes in Everett, the low incidence of injuries in this area is considered acceptable to the City.
Still more dangerous driving persists right in front of my house. The city of Everett traffic engineering department refuses to make any modifications to the flawed designs at this intersection that are obviously conducive to such dangerous behavior.
Here are the latest examples:
[Update November 28 – Here’s another.]
Note that these are just the ones that we happened to see first-hand. This kind of dangerous driving happens daily, I just don’t happen to be looking and save the video.
Here’s my latest email to the city of Everett traffic engineering department:
From: Timothy Ellis Sent: Wednesday, October 05, 2016 11:36 AM To: Michael Brick; Ryan Sass; Engineering / Public Services Subject: Re: FW: dangerous intersections on Wetmore Ave
I would like to reiterate my request for four-way stops on Wetmore Ave. at 36th, 35th, and 34th streets. We continue to see people driving at unsafe speeds (35-40mph) north on Wetmore and other drivers running the stop signs on the cross streets. We’ve already seen one fatality and without adjustments I am certain we will see more.
Please consider adding four-way stops at 36th, 35th, and 34th where the steep hills lead down to Wetmore. By adding the four-way stops it would 1) discourage through traffic from using Wetmore Ave, moving them instead to the much better suited Colby Ave and 2) slow all traffic through those three intersections, dramatically reducing the risk of a fatality collision.
And here’s their non-response reply:
From: Michael Brick <email@example.com> Date: Wed, Oct 12, 2016 at 9:11 AM Subject: RE: FW: dangerous intersections on Wetmore Ave
To: Timothy Ellis
Cc: Ryan Sass <firstname.lastname@example.org>, Tim Miller <email@example.com>, Kevin Allen <firstname.lastname@example.org>
After further review of this location Traffic Engineering still finds that the existing east-west stops at these intersections are appropriate. I have contacted Sgt Allen with the Everett Police Department and made him aware of your concerns. He agrees that this is an issue of compliance with the existing stop signs and that police enforcement is the appropriate next step. He will be contacting you shortly to discuss what option the Police have to address your concerns.
Michael Brick, P.E.
Associate Traffic Engineer
City of Everett Public Works
It’s only a matter of time before there’s another serious injury or fatality collision at one of these intersections. It’s a shame that the city refuses to take the appropriate measures to prevent it.
The main problem is that people (often on bicycles but also in cars) frequently ignore the stop signs on 35th and 36th and blow right across Wetmore Avenue, especially when heading east, since both of these streets have a steep hill leading down to the stop sign at Wetmore. This has led to many close calls already. Here are just two recent near-misses that I happened to catch on camera at 36th & Wetmore:
Here’s an excerpt from my April 5th email:
I have seen people coming down the steep hill eastbound on 35th blow through the stop across Wetmore, and when you’re coming southbound down Wetmore, you have zero visibility of oncoming vehicles from the west thanks to that row of hedges. I typically avoid driving that portion of the road at all since I am afraid I will run over someone on a bicycle or skateboard without any chance to even see them coming.
This is what it looks like as you approach 35th heading southbound down Wetmore. Note that this street view was taken in 2012. The hedges on the right are even bigger than that now. [2021 Update: The streetview below shows how large the hedges were when this post was written. Thankfully in August 2020, the hedges were finally dramatically trimmed, mostly eliminating the zero-visibility hazard.]
Last Friday, April 22, the city traffic engineer responded to email. Unfortunately, the only action the city plans to take for these two intersections is to improve stop sign visibility and measure traffic to possibly recommend “emphasis patrols” by the Everett Police for speeding on Wetmore. Neither of these solutions really does anything to address the structural problems that make these two intersections so dangerous.
Sadly on Monday afternoon 35th and Wetmore was host to the exact kind of collision I warned the city about:
EVERETT — A bicyclist suffered critical injuries Monday after colliding with a school bus in north Everett. The man, 52, was knocked unconscious but was breathing, according to police.
The man was taken to Providence Regional Medical Center Everett. No students were injured.
The crash happened about 2:15 p.m. at the intersection of Wetmore Avenue and 35th Street. The southbound bus was carrying the Everett High School track team to Memorial Stadium, according to the school district.
Police believe the eastbound bicyclist ran the stop sign and collided with the school bus, which did not have a stop sign.
I initially requested that the city install “traffic calming circles” at these two intersections. These exist at quite a few other intersections in our neighborhood, and would serve to slow traffic in both directions. The traffic engineer rejected that suggestion, saying that “they restrict the ability of emergency responders (particularly fire department vehicles) while they have proven to provide little to no reduction in crashes or excessive speeding at locations where they have been installed.”
Therefore, my latest suggestion is that the intersections on Wetmore at 35th and 36th streets should be made into four-way stops. There is already a four-lane north-south road with a flatter grade and a higher speed limit that is designed for through traffic just one block to the west on Colby. If vehicles on Wetmore were made to stop at 35th and 36th streets, collisions like the one that happened yesterday would be far less likely.
Here is my email exchange with the city on this matter:
From: Timothy Ellis Sent: Tuesday, April 05, 2016 1:33 PM To: Ryan Sass; Engineering / Public Services Subject: dangerous intersections on Wetmore Ave
I have lived on the corner of 36th Street and Wetmore Avenue since 2011, and I am very concerned about the safety of this intersection. In the time we have lived here, we have seen many people driving much too fast down Wetmore (usually northbound down the hill), and also many people–usually on bicycles or skateboards, but sometimes in cars as well–blowing through the stop signs on 36th Street.
Frankly I am amazed that nobody has been killed yet, and I fear that it is inevitable if changes are not made.
We also witness people driving far faster than 25mph up Wetmore on a daily basis (usually northbound as that is the downhill direction), occasionally even fast enough to catch a little air off the slight bump in the road just north of the intersection. It is ridiculous.
I would like to request that the intersection be modified in some way. I’m obviously not a transportation engineer, but it seems like the traffic calming circles solution in place at the intersections of 35th and Lombard and 35th and Oakes would sufficiently slow traffic in both directions to avoid any tragic events.
Also, I’m not personally there to witness it as often, but 35th and Wetmore has the same problems. I have seen people coming down the steep hill eastbound on 35th blow through the stop across Wetmore, and when you’re coming southbound down Wetmore, you have zero visibility of oncoming vehicles from the west thanks to that row of hedges. I typically avoid driving that portion of the road at all since I am afraid I will run over someone on a bicycle or skateboard without any chance to even see them coming.
From: Michael Brick Sent: Friday, April 22, 2016 11:53 AM To: Timothy Ellis Subject: RE: dangerous intersections on Wetmore Ave
Thank you for taking the time to make the City of Everett aware of your safety concerns. We have evaluated the line of sight for the intersections of Wetmore Ave with 35th Street and 36th Street, checked that the stop signs at these intersections are clearly visible, and checked crash records along Wetmore Ave.
Traffic Engineering has evaluated the line of sight at the intersections of Wetmore Ave with 35th Street and 36th Street and found them acceptable. For local street intersections such as these this line of sight check consists of measuring how far away vehicles approaching along Wetmore can be seen from the side-streets when stopped 10 feet back from the edge of the travel lanes. When stopped 10 feet from the travel lanes approaching vehicles should be visible from at least 155 feet away. The City of Everett does not check that drivers along the main road can clearly see drivers stopped on the side-streets, only that drivers stopping on the side-streets can clearly see approaching drivers on the main road. We assume that side-street drivers will respond appropriately and yield to any vehicles approaching along the main road. The large hedge on the northwest corner of 35th Street and Wetmore Ave does extend partially across the sidewalk and a letter is being sent to the property owner directing that the hedge be trimmed but this is to comply with a legal requirement that the sidewalk be kept clear and unobstructed, not to maintain sight lines at this intersection.
Stop signs on local streets should also be visible to approaching traffic from at least 155 feet away. The stop signs on the approaches to Wetmore Ave along 35th Street and 36th Street are clearly visible to approaching vehicles from at least 155 feet away. Because the eastbound approaches to Wetmore Ave along 35th Street and 36th Street are particularly steep the City has already installed “STOP AHEAD” signs mid-way between Colby Ave and Wetmore Ave to reinforce to drivers that there is a stop at the bottom of the hill. The City of Everett is in the process of replacing all of our “STOP” signs with new, highly reflective signs to improve their visibility so the signs at these intersections will soon be replaced with even more visible signs.
It appears that no crashes have been reported to the Everett Police at the intersection of 36th Street and Wetmore Ave in recent years. The intersection of 35th Street and Wetmore Ave does have an average of 1.5 reported crashes per year, but only about 1 crash every 2 years results in any injuries. While ideally there would be no vehicle crashes in Everett, the low incidence of injuries in this area is considered acceptable to the City. We will not be installing traffic calming circles at these locations because they restrict the ability of emergency responders (particularly fire department vehicles) while they have proven to provide little to no reduction in crashes or excessive speeding at locations where they have been installed.
It has been several years since the City of Everett collected speed data along Wetmore Ave near your home. We recently placed a traffic counter along Wetmore Ave in this area to collect vehicle speed and volume data. If this data shows excessive vehicle speeds at specific times of day we will forward that information to the Everett Police Department and request emphasis patrols to address the speeding at those times. As soon as we have reviewed the data currently being collected I will let you know our findings.
If you have any further traffic related questions or concerns please feel free to contact me.
Michael Brick, P.E.
Associate Traffic Engineer
City of Everett Public Works
From: Timothy Ellis Sent: Friday, April 22, 2016 4:33 PM To: Michael Brick Subject: RE: dangerous intersections on Wetmore Ave
Thanks for the thoughtful response. However, I do feel somewhat like my point was not quite understood. My main concern is not that the stop signs are not visible or that people are otherwise not aware of them. My concern is that especially on the steep hill eastbound on 36th, people just don’t care to stop. Adding a “stop ahead” sign and making the stop signs more reflective will likely do nothing to change that.
Also, the location that you’ve put the speed/volume strips up at 34th street are not likely (in my opinion based on my observations) to measure nearly as much speeding as we see down the stretch of Wetmore between 37th and 36th. Since that portion has the steepest hill, it seems that most of the speeders are going their fastest at the bottom as they pass through the intersection of 36th & Wetmore, and may have slowed somewhat by the time they get to 34th.
I understand the downsides of the traffic calming circles, but I also think that something more than just improving existing stop sign visibility and possible “emphasis patrols” would be prudent to prevent a serious incident from eventually occurring here. I also find it odd that the city would be willing to go on record saying that a dangerous intersection like this “is considered acceptable to the City.” That seems like the kind of statement that might be problemati should there ever be a serious injury (or worse) that results in a lawsuit.
Obviously I still think some sort of modification would be advisable, even if it were just to make the intersections at 35th and 36th into four-way stops. With a wider, flatter north-south route one block west on Colby, I don’t see the harm in intentionally slowing traffic on Wetmore.
Red light cameras are sold by the companies that install them and the cities that use them as a “safety” feature. Whether or not they actually improve safety is up for debate, but there is no doubt that they are big money makers for the cities that use them. If cities were primarily concerned with safety instead of generating revenue they would get rid of red light cameras and replace them with a yellow light line.
A Yellow Light Line?
tl;dr – Paint a yellow line on the road. If you’re traveling the speed limit as you approach an intersection and you’ve passed the yellow line when the light turns yellow, just keep going and you’ll clear the intersection before the light turns red. If you’re behind the yellow line, hit the brakes because the light will turn red before you clear the intersection.
How it Works
Actually there isn’t much more to it than that. Here’s what a city would need to do to implement yellow light lines:
use the speed limit and the length time the traffic light stays yellow to calculate distance
paint the yellow light line on the street at the distance calculated in step 1
there is no step 3
Simple, effective, and cheap.
Why It’s Needed
Intersections controlled by traffic signals have a basic design flaw that red light cameras only serve to exacerbate. Drivers are unsure of how long they have to clear the intersection once the light turns yellow. Should you slow down or speed up? Every intersection has different timing, and when an intersection is equipped with a red light camera that doles out $124 tickets, drivers are much more likely to slam on the brakes even if they could make it through safely. This leads to more rear-end collisions.
With yellow light lines, that ambiguity is completely eliminated with a simple, clear visual. If you’ve passed the line when the light turns yellow, continue on at the speed limit and you will safely clear the intersection before the light turns red. If the line is in front of you, you’ll need to stop. No more uncertainty, no more slamming on the brakes.
Yellow Light Line Calculator
In order to help visualize this concept I’ve created this handy calculator. Simply edit the speed limit and/or the yellow light length to see how far from the intersection the yellow light line would be painted.
It’s not illegal to be in the intersection when the light turns red, it’s illegal to enter the intersection after the light turns red. – davethegr8
Indeed, the relevant law here in Washington State (RCW 46.61.055) indicates that it is only illegal to enter the intersection on a red light. However, since the purpose of the yellow light line is not to adhere to strict legal definitions but rather to improve safety, I think it would be best to measure the distance from the end of the intersection rather than the entrance.
How about telling people what you did so they know what the lines are? – Sir_Dude
This is a good point. Above I jokingly said “there is no step 3,” but in reality step 3 would be driver education.
Oh, and how are these lines going to work with heavier vehicles? An SUV is going to need more room to stop than a Prius. One line isn’t going to work for all cars. – Sir_Dude
The yellow light line is not placed based on how long it will take you to stop. The line is placed based on where you can clear the intersection while traveling at the speed limit.
Example: A driver in a Prius is driving the limit on a 35mph road and the light stays yellow for three seconds. They will travel 154 feet during the three seconds that the light is yellow. A driver in a big rig, will still travel the same 154 feet if they are driving 35mph for three seconds. So we paint the yellow light line 154 feet from the end of the intersection.
If three seconds is not enough time for a big rig to stop, then the length of time the light is yellow should be adjusted by the city. This obviously would move the location of the yellow light line, but the correct location of the line is not variable for different vehicles, it depends only on the speed limit and the length of time the light is yellow.
Currently, judgement is all drivers depend on. If you suddenly give drivers a “tip” for determining if they should go or stop, what will change? People tend to be aware of their current speed, their braking capability based on vehicle characteristics, and how far they have before the stop line. – steve_mcgee
It is true that drivers are (or should be) aware of those things. However, what drivers are often unaware of is how long the light will stay yellow, and whether or not that is enough time to make it through the intersection from their location when it turns yellow. This issue is exacerbated by the fact that different intersections have different yellow light timing. The yellow light line is a simple way of providing exactly that piece of information to drivers.
Light timing changes (gets shorter) on many intersections late at night. The timing would be off on clearing the intersection or you’d need two lines. – eran76
The overall cycle of a given traffic signal may get shorter at night, but the length of time the light is yellow is constant regardless of how long the light stays red or green, and does not change throughout the day.
Like this idea? Contact your local city council and point them to this post. Share it on your favorite social media site and spread the word. Or if you’re really ambitious, file a statewide citizen’s initiative. If you feel like living dangerously, you can run the calculator for the intersections in your neighborhood, grab some yellow paint, and engage in some “Guerrilla Public Service” like L.A. artist Richard Ankrom, who installed his own freeway sign in 2001.
I’ve also provided a handy embed code above so you can easily share the yellow light line calculator.
Or maybe you think I’m a clueless idiot and this is an incredibly stupid idea? Point out the flaws in my logic in the comments below.
With the news a few weeks ago of the death of six climbers on Mount Rainier, I found myself wondering… just how dangerous is climbing Rainier, anyway? Is it really more dangerous than other risky activities that we do every day?
For example, thirty thousand people in the United States die every year in automobile accidents, but since we don’t see front page headlines about every single fatal collision, perhaps we just perceive the risk to be lower than climbing a mountain. Maybe mountain climbing is just as dangerous as your daily commute, but your perception is skewed.
In order to answer my question, I collected fatality rate data on a variety of activities to compare with climbing Rainier. Here are the risky activity contestants, and the average annual number of fatalities that occurred during each over the last ten years or so.
walking: ~4,000 fatalities
bicycling: ~600 fatalities
driving a car: ~30,000 fatalities
driving a motorcycle: ~4,000 fatalities
commercial flight: ~14 fatalities
skydiving: ~22 fatalities
Dungeness crab fishing: ~3 fatalities
climbing Mount Rainier: ~1 fatality
I wanted to include a good variety of activities, from things we all do every day like walking, riding a bicycle, or driving, to things that most of us probably don’t do, but are widely considered to be dangerous, like skydiving and professional Dungeness crab fishing, an activity that is widely regarded as the “deadliest” occupation in the country.
To compare everything on a relatively level playing field, I divided the total number of deaths over the last ten-ish years in each activity by the total number of trips taken in that activity in the same period, then multiplied by 100 million to bring all the numbers up to a scale that’s easier to visually compare.
Here’s the result:
Okay then! As it turns out, mountain climbing is ridiculously more dangerous than every other activity I was able to find data on. It’s not even remotely in the same league. Climbing Mount Rainier is 14 times more deadly than the “deadliest job” of fishing for crab in Alaska.
Now, it’s worth noting that normalizing for deaths per 100 million trips isn’t totally fair, since most people who attempt to summit Rainier will probably only do it once or twice in their lives, while the average person probably takes 50 to 100 thousand trips in a car through the course of their lifetime. Your odds of dying in a car wreck on any given trip are fairly low, but the odds that you might die in a car wreck sometime in your lifetime are much higher.
To quantify that, the odds that you’ll die in an attempt to summit Rainier are roughly 0.02 percent. The odds that you’ll die on any given trip in your car is 0.0000038 percent. But the odds that you’ll die in a car wreck sometime in your life is roughly between 0.19 percent and 0.38 percent—considerably higher than your odds of dying in a single attempt to summit Rainier. In other words, your chances of dying from driving at some point in your life are about 19 times greater than your chances of dying while climbing Rainier.
Still, I was surprised that climbing Rainier is that dangerous per trip. A 0.02 percent fatality rate sounds low, but it’s way, way higher than every other activity on the list. Of course, it’s not even remotely the most dangerous thing you can do. If I had included a bar for climbing Mount Everest, it would have made everything else on the chart look minuscule. Everest has around a one percent fatality rate—1,000,000 deaths per 100 million trips compared to “just” 15,942 for Rainier. And according to Mental Floss, there are at least five mountains even more dangerous than Everest—including Annapurna in Central Nepal, with a 22 percent death rate (22,000,000 deaths per 100 million trips).
So basically I won’t be climbing any mountains. Ever.