Weird spotting for 172AM06 (57Y
slot) today
SMB159L came back to CCK INT at 1150am. BC got off after parking
the bus, with EDS showing OFF SERVICE. At 12pm, BC went
onto another bus (TIB546A) and was preparing the bus for service.
172AM06 was scheduled to leave int at 1154am but BC only drove out
TIB546A to 172 berth at 1207pm. Worse thing is behind bus (SMB58U)
got e-pulled to 180 at that time so no bus came back to int
after SMB159L to start trip, so all had to wait for 172AM06 to
finish changing bus. Next bus, TIB714G on 172AM01 haven even reach
int when TIB546A left int. Good thing not much people waiting.
However, thats not all...
The ez link machine was running on 302 route details, duty as
30206. PIS also showing 302 route details. BC didnt realise at
first but guessed he finally realised after the bus left Lot One
stop. BC just let the meter run as though it's on 302 until it
reaches 7.5km and prompts BC to end trip. BC had to "reduce the km"
so that the meter will not hit 7.5km. As a result, some pax could
not tap out as some had board the bus at, say 6.2km, but when tap
out, it was 4.4km. But this also means the remaining pax enjoyed
feeder fares rather than trunk fares...
TIB546A was later spotted in the evening doing
172PM06...
