Bicycle Austin 

Drivers are at-fault in 90% of cyclist and pedestrian fatalities. (report, p. 25)  •  In 40% of fatal car/bike crashes the driver was drunk. (source)

A volunteer project by Michael Bluejay.

Awarded "Best of Austin" by the Austin Chronicle.

Bicycle Austin forum

This forum’s roots date back to the very first bike email list in Austin, starting in 1994, and it played a part in the getting the segregated bike lanes you see all over town.  Be a part of history and make a post!

You are not logged in.

#1 2025-04-07 13:26:47

Jack
Member
Registered: 2013-03-27
Posts: 345
Windows 10Chrome 132.0

TXDoT needs a plan for carpooling or group transit for its employees

https://www.kut.org/austin/2025-04-07/t … ces-garage

Just a week into a push to get workers back into the office, employees with Texas' transportation agency are struggling to find parking.

So, they're parking illegally.

An employee with the Texas Department of Transportation reached out to KUT on Thursday, saying the agency is allowing workers to park in fire lanes at its 1,600-employee campus near Stassney Lane and Burleson Road. The person asked to remain anonymous for fear of retaliation.

Offline

#2 2025-04-07 23:13:12

MichaelBluejay
Webmaster
From: Austin, TX
Registered: 2008-05-26
Posts: 1,484
Website
MacintoshSafari 16.6

Re: TXDoT needs a plan for carpooling or group transit for its employees

Classic.  DPS workers parked in the bike lane along north Guadalupe for years.  Maybe still do, but I haven't been in that area for a while.

It's not just workers at some random business or agency doing the bad parking, it's workers at agencies responsible for TRANSPORTATION and ENFORCING LAWS that are doing it.  Nice.

Offline

#3 2025-04-08 17:28:39

dougmc
Administrator
Registered: 2008-06-01
Posts: 640
LinuxChrome 135.0

Re: TXDoT needs a plan for carpooling or group transit for its employees

Laws for thee, not laws for me.

Offline

Registered users online in this topic: 0, guests: 1
[Bot] ClaudeBot

Board footer

[ Generated in 0.006 seconds, 9 queries executed - Memory usage: 551.99 KiB (Peak: 569.06 KiB) ]