Most of the problems I’ve had with late running on Clarks buses have been caused by drivers starting their shifts late, with delays from that cascading across the entire day.
It’s not uncommon for them to do their first PM peak run out of the city with a 10-15 minute delay because of the driver using the motorway instead of the busway to get to Elizabeth St, only to end up getting stuck on a jam at Holland Park or Greenslopes.
Driver discipline is a big issue.
Very little of that is likely to be a problem with the 560 or 550 on weekends. From what I can see, only maybe 1 in 4 westbound 560s start life as a 555. Most are from other local routes like 565, 553, 563, 572 etc.
Hello, 560, my old friend.
Departing Hyperdome at 1:00 pm (due for departure at 12:45), but this is what the Translink app showed…apparently, the bus has already passed Golf Course Drive.
Seriously, is it that hard to get the real-time info correct?
Given the GCLR data keeps falling offline due to updates needed (offline as I type this), I wonder if the system still has some quirks happening to it
560 doing it’s thing, again.
Apparently, the school holiday timetable doesn’t work, either.
I’m really wondering what the point of the timetable review was, when it seems to have had minimal effect.
I’m looking at performance and I’m not sure how one of the buses managed to be delayed from 16 minutes to a whopping FIFTY ONE MINUTES, particularly right by the end of the trip at Browns Plains.
EDIT: I had a look at vehicle traces and the bus simply pulled aside at Vergulde Rd and sat in there for a whole half an hour.
Bus driver’s lunch break?
