• Welcome to RAIL - Back On Track Forum.
 

Article: Prime timing

Started by ozbob, February 28, 2013, 17:04:20 PM

Previous topic - Next topic

ozbob

From the Brisbane mX 28th February 2013 page 1

Prime timing

Half baked projects, have long term consequences ...
Ozbob's Gallery Forum   Facebook  X   Mastodon  BlueSky

ozbob

Sent to all outlets:

28th February 2013

Not the full story ...

Greetings,

Peak ontime performance for trains has improved in SEQ.  However, out of peak ontime performance for trains also needs to be made publicly available.  Many disruptions occur outside peak times and these are very disruptive and often add long delays to journey times.  A peak snap shot is not the full picture, is it?  Transperth ( http://www.transperth.wa.gov.au/AboutUs/Surveysandstatistics.aspx ) can make available complete data, why not Queensland Rail?

Today, another level crossing incident and bridge strike ( http://railbotforum.org/mbs/index.php?topic=1862.msg120615#msg120615 ). Clearly, the present campaigns and sanctions are not effective.  Put these idiots off the road absolutely, 12 months first offence, life for a second offence. Full cost recovery and maximum fines.  Not rocket science ...

Best wishes
Robert

Robert Dow
Administration
admin@backontrack.org
RAIL Back On Track http://backontrack.org
Half baked projects, have long term consequences ...
Ozbob's Gallery Forum   Facebook  X   Mastodon  BlueSky

somebody

Best in 8 years?  Didn't we have a big problem a month ago?

ozbob

Been the odd issue for sure, but I think overall peak OTP has improved, data seems to suggest that.  Still a lot of disruptions around the clock.  The full OTP profile of all lines from first to last service should be available.  There are lot of delay impacts that are being hidden, which outside peak times can be very significant too due to the poor frequency and failed connections etc. 
Half baked projects, have long term consequences ...
Ozbob's Gallery Forum   Facebook  X   Mastodon  BlueSky

somebody

Notice that the data doesn't even consider that there was a peak hour on 29/1/2013 - because it was that disrupted.  Really there was but with about 75%+ of services cancelled.

🡱 🡳