X:
Update: Caboolture, Sunshine Coast, Redcliffe Peninsula and Shorncliffe line trains travelling away from Central are delayed up to 40 minutes due to a signalling issue. (https://bit.ly/4mIdO0e)
QR FB:
SUNSHINE COAST, CABOOLTURE, SHORNCLIFFE AND REDCLIFFE PENINSULA LINES: Customers, due to a signalling issue at Northgate we are currently experiencing delays of up to 40 minutes for customers travelling in the outbound direction on the Sunshine Coast, Caboolture, Shorncliffe and Redcliffe Peninsula lines. Our crews are currently onsite and we will continue to keep you updated. We appreciate your patience while we work to resolve this issue and are online to assist you.
UPDATE 9:35am: Customers, rail replacement buses are now in full operation conveying customers between Eagle Junction station and the Domestic Terminal with minimal delays anticipated. Our teams remain onsite working to resolve the issue as quickly and safely as possible, and your continued patience is appreciated. We will continue to keep you updated and are online and available to assist.
5073 (doing a 150 inbound) has now entered Upper Mt Gravatt. And itâs entirely a full standing load. Thereâs still at least 70+ more people waiting at Platform 1 (inbound).
The fact that M1 is currently operating 10 minute headways around this hour just isnât good enough.
The amount of demand coming from the SE busway (for buses bound to the City) is extraordinary.
To avoid all the overcrowding from the M1s, Iâve decided my best bet to reach the City is hop on a 116 inbound. 116 is notorious for being a milkrun through the suburban streets of Moorooka. And those Moorooka residents wouldâve either hopped on the Ferny Grove line (or maybe the comparatively more frequent 125).
Yes, the high frequency 120 BUZ and 180 BUZ were all options I had in mind - but they too would be chockers full around this hour (due to Riverfire).
Update: 9023 (doing an M1 inbound) is full..!
Maybe council shouldâve considered express shuttle-style M1s.
Empty As! Itâs just me and one other guy. Sooo many people at Upper Mt Gravatt, still somehow with the false belief that a 150 inbound will turn up magically empty..
One more eyewitness account: all the M1s, 150s, and 555s that arrived at Platform 1 at 3-4pm (Upper Mt Gravatt) were at, or nearing crush load capacityâŚ
The 116 inbound Iâm on just passed the QEII Hospital bus stop, and there mustâve been 30+ people waiting at that bus stop, presumably for the high frequency 120 BUZ inbound!
116 inbound has just passed Hawthorne Street stop 44, and impressively, we are collecting Moorooka residents, despite the fact that we have a loooong way to go. Such a milkrun this infrequent route - and its now just standing room only. Weâve only just passed Moorooka station.
Yeah it was crush load on the M2 as well, people at PA Hospital inbound unable to board, and the next M2 was running late and already overloaded (at about 4:15pm). Not good!
On another note, just had to ring TL and put in a complaint about a driver - the 4:19pm (outbound) 203 service had the driver screaming F Bombs at the traffic for the whole bus to hear and he failed to take the Eastern Busway missing Stones Corner and Langlands Park busway stations. People also unable to board at Coorparoo earlier, routes 200 and 222 already at capacity.
Something interesting to note as well, it seemed that people were ignoring the inbound 203s to head to Riverfire and instead catching the outbound 203s to Carindale instead. I think the 205 really needs to run weekend services in the next change whenever that is, itâd certainly pick up loads, even when Riverfire isnât on.
Yeah, the 116 needs to be straightened out. Iâve created a draft route (named it 124) to service the eastern side of Moorooka, leaving the 116 straight down Ipswich Road and the western side of Moorooka.
I donât know how on earth 116 didnât get truncated back to - say - Dutton Park station for the BNBN. PA Hospital wouldâve also been a possible terminus I feel like
Wasnât quick enough to get a pic, but I saw a 555 in Adelaide St this morning where the rear desto flicked between â555â and âDeparts 1 minâ (on 2 lines). I can see this being particularly helpful at a terminus, when you see the bus, but donât know how soon it leaves. Has anyone else seen this?
A bunch of the newer buses especially operated by Kinetic and Transdev (and probably other non BCC operators) have this as well, itâs a very nice feature. The front desto does it too and the data seems pretty high definition, counting down in 10 second increments until it says âdeparts nowâ
I imagine itâs controlled by the smart ticketing hardware so I wonder if BCC could upgrade their destos to support it too
Itâs a different system provided by Consat Telematics.
It hijacks the destos and other things giving the driver detailed information about on-time running (up to the second!), a live route map with stops, passenger counting, and more. It works alongside the normal translink console as far as I know.
For the driver itâs a fantastic system, but for the passenger itâs more hit and miss: the desto text is usually horrible looking and quite inflexible, with special emphasis on the side panels, which usually have text overflowing as it doesnât fit.
One example is:
â572 SPRINGWOâ or â777 GC Airport - Exâ
Ventura in Victoria also uses this solution and they also have the same issues.
The stop announcements are also very robotic sounding, butchering a lot of name pronunciations and whatnot.
While I appreciate the âDeparts in X minutes,â and can put up with the âSPRINGWOâ and âLOGANHOLMâ on the side desto, youâre not wrong about the stop announcement voices. They are awful - very rigid and robotic, and its pronunciation does leave a LOT to be desired. It sometimes sounded like it was mixing up St as in Street, with St as in Saint - leading to announcements of the next stop being âElizabeth Saint Stop 82â.
