Fatal I-405 Crash Blamed on Audi Exceeding 100 MPH, WSP Says

A driver of an Audi was arrested on suspicion of vehicular homicide after a fatal rollover crash around 10 p.m. Thursday Sept. 12 on southbound Interstate 405, according to the Washington State Patrol.

Updated: 12:15 a.m. Friday

According to Washington State Patrol Trooper Chris Webb, the driver who was arrested was drove the Audi in excess of 100 mph and struck a BMW in the rear. The BMW rolled and caught fire. The driver of the BMW died at the scene, he said.

Webb reported that troopers believe the driver of Audi may have been under influence of drugs, possibly meth. The driver and passenger in the Audi were taken to Overlake Hospital Medical Center for injuries, he reported. 

Two other vehicles were also struck in the collision, though none reported serious injuries, he said.

The freeway remained closed for at least two hours after the initial crash as troopers investigate, Webb said.

Original story:

One person is dead and all southbound lanes were blocked for at least an hour after a fatal rollover and crash on Interstate 405 in Bellevue near NE 4th Street, according to the Washington State Patrol.

All lanes of southbound I-405 at NE 4th were blocked around the time of the collision, at about 10 p.m., according to the Washington State Department of Transportation. 

According to Washington State Patrol Trooper Chris Webb, preliminary indications are that a vehicle may have hit two other vehicles, and then rolled. That vehicle was previously reported at a "high rate," he wrote on Twitter. 

The crash is being investigated as vehicular homicide because an additional vehicle may have been involved in the collision, Webb reported.

The person who died was in the vehicle that rolled over, he reported.

More information will be posted to this breaking news story.

** Editor's Note: the story originally had the incorrect direction of the blockage, due to incorrect information initially reported by the Washington State Department of Transportation. This has been corrected.