A Gantt Chart Shows You the Plan. The Hard Part Is Showing You the Truth

Why a flight list is the wrong shape for an OCC

The obvious way to present a day's flying is a list, sorted by time. It is easy to build, easy to read, and it answers one question well: what happens next.

But movement control is not mostly about what happens next. It is about relationships between movements. Does this turn actually fit. Is this tail committed to two things at once. If this arrival slips forty minutes, what else moves. Can this aircraft be somewhere it is currently not scheduled to be, and what breaks if it goes.

A list encodes none of that. The relationships exist in the data, but the reader has to reconstruct them mentally, one question at a time, by holding several rows in their head and doing arithmetic. That works at three aircraft. It degrades badly by ten, and it degrades fastest exactly when the day is going wrong and the questions are arriving quickest.

How a movement board does arithmetic by geometry

The timeline's trick is that it converts calculation into perception. Give each tail a lane, run time horizontally, and place each movement where it actually falls. Suddenly the properties that mattered are physical ones.

This is the entire reason the format has survived. It is not that a timeline is prettier than a table. It is that a well-drawn one answers questions before they are consciously asked, and an operator under pressure has a limited budget for conscious questions.

Scheduling conflicts stop being calculations

The practical consequence is that a category of problem becomes visible instead of discoverable. An aircraft double-committed, a turn shorter than the station can service, a maintenance window sitting across a planned departure — each of these is a shape, and shapes get noticed in passing by an OCC controller who was looking at something else entirely.

Timing is what makes that valuable. The same conflict costs very different amounts depending on when it is found. Seen at seven in the morning against a late-afternoon departure, it is an administrative task with several comfortable options. Seen at half past three, it is a disruption, and the options remaining are the expensive ones. Nothing about the conflict changed; only the number of hours available to absorb it.

Where the OCC timeline stops: plan versus truth

Here is the part that gets skipped, and it is the part that decides whether a board is worth having.

A timeline is a drawing of a plan. It describes intention — what was supposed to happen, arranged by when it was supposed to happen. That is a perfectly good description of the operation until roughly the first delay of the day, at which point the drawing and the world begin to diverge, and the drawing has no inherent way of knowing.

A board that renders only the plan is therefore confidently wrong for most of the day, and worse, it is wrong in a reassuring way. Everything still looks orderly. The bars are still where somebody put them. So the useful question about an OCC display is never whether it has a timeline. It is how the timeline distinguishes between three quite different things:

• What was planned — the schedule as built, which remains the reference you are measuring against
• What is actually happening — actual times, current position, current status, drawn so the difference from plan is the thing you notice first
• What is simply unknown — the aircraft nobody has heard from, which is not the same as an aircraft running to schedule

That third category is the one most displays handle worst. An aircraft with no recent position and an aircraft confirmed on time will frequently be drawn identically, because the absence of bad news is treated as good news. It is not. Silence is a state, and a board that hides it trains its users to place equal confidence in a fact and in a gap.

The same applies to age. Information has a freshness, and a display that renders a two-minute-old position and a two-hour-old one with the same weight is quietly making a claim it cannot support.

A shared reference for the OCC and everyone around it

The other thing a timeline provides is less about visualisation than about organisational plumbing. Operations, engineering, crewing and the commercial side each carry their own mental model of the day, assembled from whatever they can see. Those models differ, and the differences usually stay hidden until something forces them into contact.

A shared board forces the contact early. Its real value is not that it makes everyone agree; it is that it makes disagreement happen in front of one artefact, at a point when the disagreement is still cheap. Two departments discovering at eight in the morning that they had different assumptions about an aircraft is a conversation. The same discovery at boarding is an incident report.

That only holds if the board is genuinely the same for everyone. The moment different roles are looking at meaningfully different pictures, it has become another place for the models to diverge — which is the fragmentation problem wearing a nicer interface.

Post-operations analysis: the same data, read afterwards

During the day a movement board answers questions about now. The records behind it answer a different and more valuable set of questions later, once nobody is under pressure.

Replayed across a quarter, the same data shows which turns were routinely optimistic rather than occasionally unlucky, which stations and which times of day absorb delay and which propagate it, and how far a single early disruption typically travelled through the rest of a tail's day. Those are planning answers, and they are the ones that reduce next quarter's disruption rather than managing this afternoon's.

Most operations never get to them, not because the data is missing but because it was only ever treated as a live display. The board was built to be watched, so it gets watched, and then the day is over.

What separates a useful movement board from a decorative one

Every serious operations product has a timeline now, which means its presence has stopped being informative. These are the questions that still separate them:

• Does it show actual against planned, or only the plan drawn confidently?
• Does an aircraft nobody has heard from look different to one confirmed on time?
• Does the display age — is old information visibly old?
• Can you see the constraint that makes a gap too short, or only the gap, leaving the operator to remember the rule?
• How many movements before it stops being scannable and people go back to asking a colleague?
• Can you act on it, or only look at it? A board that requires another system to make the change you just decided on has handed the decision back to a form

A movement board is a model of the operation, and every model is wrong in ways that matter less or more depending on how quickly it admits it. The good ones are not the ones that look calmest. They are the ones that tell you, early and without being asked, where they have stopped knowing what is going on.