How MRT Terminal Turnback and Reversing Capacity Work Using Mathematics

A railway can run trains quickly between stations and still be limited by what happens when each train reaches the end and has to become a train going the other way.

Terminal turnback capacity is the mathematics of reusing a finite set of terminal tracks, platforms and junction resources fast enough that arriving trains do not queue behind the end of the line.

The Timetable pillar owns the complete event plan. The Switches, Crossovers and Turnouts pillar owns physical junction geometry. The Signalling and Train Regulation pillar owns real-time movement authority.

This article owns one narrower public-safe question: how many trains per hour can a terminal reverse without becoming the bottleneck of the line?

Urban-rail research repeatedly finds that line capacity can be governed by the frequency with which trains can be reversed at terminal stations. Recent 2026 turnback-capacity work continues to model arrival spacing, platform occupation and reversal processes as the binding capacity problem.

The RFE — What Is a Turnback For?

convert each arriving train into a correctly sequenced departing train in the opposite direction quickly and regularly enough that terminal occupation does not destroy the headway the rest of the line is trying to deliver.

Prompt 1 — What Events Make Up a Turnback?

A public event sequence can be represented without publishing operating procedure:

arrival
→ platform occupation
→ passenger exchange
→ reversal preparation
→ movement to departure-ready state
→ departure

Let those durations be:

Tturn = Tarrive + Tdwell + Treverse + Tclear + Tmargin

These symbols are educational abstractions, not an operator sequence.

The key idea is simple: a terminal needs enough time and space to complete one train’s reuse before the next train needs the same constrained resource.

Prompt 2 — How Does Turnback Time Become Capacity?

If one terminal resource can complete one train every T seconds, a theoretical upper service rate is:

μterminal ≈ 3600/T trains per hour

But practical capacity must also include safe separation, junction conflicts, platform occupancy and variability.

So the useful terminal headway is better thought of as:

Hterminal = max(
arrival-separation requirement,
platform occupation requirement,
shared-resource conflict requirement,
departure regularity requirement
)

The line cannot sustainably operate at a headway smaller than the largest binding terminal constraint.

The end of the line is a server. If trains arrive faster than it can recycle them, the queue travels backwards into the railway.

Prompt 3 — Why Does Platform Occupation Matter?

A terminal platform is occupied from the moment one train needs the berth until the resource is clear for the next compatible use.

Let occupation interval be O_i=[a_i,c_i].

Two trains requiring the same exclusive resource must satisfy:

Oi ∩ Oj = ∅

or be separated according to the permitted operating arrangement.

This is a scheduling problem: terminal capacity depends not merely on how long reversal takes, but on how resource occupation intervals overlap.

Prompt 4 — What Is a Shared Junction Conflict?

Arriving and departing trains may need some of the same physical junction region at different times.

Represent each required movement as a task using resource r for interval I.

task k = (resource r, start tk, duration dk)

If tasks share the same exclusive resource, they cannot simply overlap.

This is the same mathematical family as machine scheduling in operations research.

The specific live routes, interlocking states and signalling sequence are intentionally not reproduced here.

Prompt 5 — Why Does Variance Reduce Terminal Capacity?

Suppose mean turnback time is E[T] but actual times vary.

A terminal scheduled at exactly the mean leaves little room for long events.

If train i arrives with deviation ε_i:

actual arrival = scheduled arrival + εi

and turnback duration varies by η_i:

actual turnback = planned turnback + ηi

then terminal conflict risk depends on ε_i+η_i, not only the planned schedule.

Recovery margin is therefore part of capacity.

Prompt 6 — Why Can Two Turnback Resources Be Better Than One?

If two terminal resources can serve trains in parallel, theoretical service capacity increases.

μtotal ≈ μ1 + μ2

But only if both resources are actually usable for the relevant sequence and do not share another bottleneck.

A common throat or junction can make:

two platform tracks
≠
twice terminal capacity

Research on two-tail-track terminals shows that flexible allocation can improve delay absorption, which is a reminder that redundancy is partly about how resources are scheduled, not merely how many exist.

Prompt 7 — How Does the Terminal Affect Fleet Requirement?

Full line cycle time includes terminal turnback.

Tcycle = Toutbound + Tturn,A + Tinbound + Tturn,B

Active train requirement is approximately:

N = ceil(Tcycle/H)

Longer terminal occupation can therefore require more trains for the same service headway.

A terminal improvement can create a fleet benefit even if interstation running time does not change at all.

Prompt 8 — How Does World Return Reveal a Terminal Bottleneck?

Useful public-safe metrics include:

arrival headway distribution;
platform occupation duration;
departure headway distribution;
queueing of trains approaching the terminal;
turnback-time variance;
recovery time after a delayed arrival;
fleet cycle-time deviation.

Define departure headway error:

eH,i = Hdeparture,i − Htarget

If |e_H| systematically increases after trains pass through the terminal, the terminal is consuming regularity rather than returning it.

A Fictional Terminal Example

Consider a fictional terminal with target line headway H=120 s.

Suppose average resource occupation for one complete arrival-to-clearance cycle is 105 s and planners preserve 20 s of effective variability/recovery allowance.

required terminal spacing≈105+20=125s

The rest of the line may be capable of 120 s, but this fictional terminal is not.

Useful service headway becomes at least about 125 s until the binding terminal constraint changes.

This is only a teaching example, not an MRT operating value.

Deletion Tests

Remove reversal time: an arriving train becomes a departing train instantly.
Remove platform occupation: multiple trains can use the same berth simultaneously.
Remove shared resources: arriving and departing movements never conflict.
Remove variance: every turnback takes exactly the planned time.
Remove recovery margin: one late arrival never affects the next departure.
Remove fleet cycle: terminal time has no effect on train requirement.
Remove World Return: departure irregularity never reveals a terminal bottleneck.

Terminal Paradoxes

The terminal is stationary infrastructure that can determine moving-line capacity.
A second platform or tail track may add less than double capacity if both share another constraint.
Reducing turnback time can improve fleet efficiency without making any train faster between stations.
A terminal can absorb delay or amplify it depending on how much margin remains.
The line can be uncongested everywhere except its final hundreds of metres and still be frequency-limited.

The Turnback Audit

What arrival headway reaches the terminal?
How long does each train occupy the relevant terminal resources?
Which resources are exclusive and which can operate in parallel?
What junction or throat conflicts constrain simultaneous use?
How variable are dwell and reversal durations?
How much recovery margin protects departure regularity?
What happens when one arrival is late?
How does terminal time change full cycle time and active fleet requirement?
Does a second resource add true independent capacity or share the same bottleneck?
What measured departure headway proves the terminal is returning trains to the line regularly?

World Return — The Terminal Must Return a Regular Train

train arrives
→ terminal resources are occupied
→ train becomes departure-ready
→ train departs opposite direction
→ departure headway is measured
→ compare with target and incoming delay
→ update timetable / resource plan as authorised

MRT terminal turnback works when the end of the line can recycle arriving trains into regular departures faster than the rest of the railway sends new trains towards it.

Reader-safety note: This article intentionally excludes Singapore MRT terminal layouts, crossover sequences, signalling logic, movement-authority rules, live turnback times, operating thresholds and recovery procedures. All numerical examples are fictional.

How MRT Terminal Turnback and Reversing Capacity Work Using Mathematics: Why the End of the Line Can Limit the Whole Line