Looping services always have an issue with delay of buses. Now
you cannot compare 34, 36 with 27. 27 has a 4-5 minute frequency
compared to the other two which come around 9-12 mins interval.
With 27 if one bus is late, there is immediate bunching that is
unavoidable due to frequency. For 34, 36 if one bus is late and
comes after 15 mins (already 5 mins delay), the next bus will come
after 20 mins. Still 5 mins gap in between, so you don't see
bunching, but there is delay.
Having looping points far away from terminating point will
always lead to delays and is not avoidable especially during peak
hours and given erratic traffic conditions. I have often seen 2
buses on 34 and 2 buses on 36 bunch together. This means, a bus has
almost arrived 20-22 mins later. On 27, if a bus arrives 12 mins
later, you will see 3 buses together. So the issue is not
different.
Thank you sir, for practically agreeing to what I
said.
As for your "often seen 34/36 bunch together" I really dunno if
you were either so powerful to see what did not happen, or really
just making it up.
If not, why not you prove it? I travel daily past the sectors
both 34 and 36 plies. How would I not know what is happening?
And aren't you just contradicting yourself? First para, say
cannot compare with 27. Last para? Saying 34 and 36 "bunches" just
like 27. Hmmm.
BTW, since that is the case, why not just reduce the freq for
the long loop Punggol svc? And deploy DD on it to balance out the
problem?
On a last note, I can guarantee you 97% of the time you will see
36 arrive in almost balanced frequency at the airport (near the end
of trip).