See a zone's work is to ensure that train maintains its schedule through their territory, WCR in this case maintained delay, adding 3 mins, which is fine considering upro 15 mins delay is assumed ontime by controlling manuals, if 22109 needs to reduce slack, TT has to be changed likewise.
A zone only agreea to a TT during introduction of a train, which it can feasibily deliver.

---

Agreed with you... But will request you to please answer the following:-

Why did CR accepted such aggressive schedule for 22110 when it knew it was a difficult task in case the train is handed over late? Anyways 3 times it has arrived BSL on time @ 05:30 (as per earlier TT) but then it never arrived LTT on time. It was delayed by around 30 mins+

---

And about NTES status...don't believe in it...Its usually observed Train status @ LTT is shown at Arrived at that time when it crossed Bhandup..:P

---

Donno what was up with CR who accepted the schedule they haven't maintained till date(for this train) this train also has arrived BSL ontime once, there are zonal bureaucracies involved while finalising TT for trains, seems like TT was aimed for higher mps like 120kmph, although 22109 in return performs beautifully with almost same schedule.
One thing is noticable, CR train timetables have almost equal average speeds for both up and down schedules of a train, 22110 TT seems to be made for making up to that avg speed.

---