Ramping up: what a production increase does to the schedule

We wrote earlier about the aircraft backlog and its downward pressure on schedules — deliveries that slip, routes that can’t launch, capacity reshuffled rather than added. This is the other side of the same story. When the line finally moves and aircraft do arrive, the schedule doesn’t get simpler. It gets bigger, and it gets rewritten again.

The number, and where it’s pointing

The combined Airbus and Boeing order backlog reached a record 16,683 jets at the end of April 2026 — on the order of twelve years of production at current rates, with Airbus at roughly 9,247 and Boeing around 6,758. That is demand the manufacturers are under real pressure to work down, and the ramp is visible in the delivery figures: in the first quarter of 2026, Boeing delivered 143 aircraft to Airbus’s 114.

The rate targets tell the same story. Boeing has been cleared to raise 737 MAX output from 42 to 47 aircraft per month. Airbus is still pushing toward its A320-family “rate 75” goal — though it has pushed the target back amid Pratt & Whitney engine shortages — against a 2026 delivery ambition of roughly 870 aircraft.

Metric (2026)	Value
Combined order backlog (end-April)	~16,683 jets
— Airbus / Boeing	~9,247 / ~6,758
Q1 deliveries (Boeing / Airbus)	143 / 114
737 MAX rate (approved)	42 → 47 per month
Airbus 2026 delivery target	~870

(Figures are drawn from 2026 industry reporting cited below; order-book and rate numbers move month to month.)

An inducted aircraft is an empty schedule

Here’s the part that gets lost in the manufacturing coverage. A frame rolling off the line is not, by itself, capacity. It’s a liability until it’s flying — leased or bought, insured, crewed, and sitting on a ramp. The value only appears when it’s written into a schedule and turning revenue flights.

So every induction sets off a chain of schedule work:

• New frequencies. The simplest use of a new aircraft is more of what you already fly — a fourth daily on a trunk route, a Saturday added to a seasonal one. Each is a new set of flight-leg records with their own days of operation and period.
• New routes. A frame can open a city pair the network didn’t serve. That’s not one row; it’s an out-and-back, its return, the connecting banks it feeds, and the downstream itineraries that only exist once the leg does.
• A fresh rotation per tail. Every aircraft needs a workable day: a chain of legs that starts and ends where maintenance and crew expect it, with turn times that hold. Add a tail and you’re not editing one flight — you’re threading a whole rotation through the existing fabric.
• Cascading knock-ons. A new widebody frees a narrowbody that was covering a route it was too big for, which frees a regional jet somewhere else. One delivery can touch three fleets’ worth of assignments.

A delivery is often reported as the end of a story. For a scheduling team it’s the start of one: the aircraft arrives as a blank in the plan, and the schedule has to be rewritten to fill it.

Ramp-up multiplies the rewrites

A one-off delivery is manageable. A sustained rate increase is a different regime. When output climbs from 42 to 47 airframes a month across a program, an airline taking those deliveries is absorbing new metal continuously through the season — not loading a fresh fleet plan once a year and living with it.

Each induction lands on a date that itself keeps moving, because ramp-ups rarely run to plan; engine and supplier constraints still slide individual frames by weeks. So the schedule gets reissued mid-season, again and again, as the actual arrival dates firm up. The planning team is reading a new schedule file each time and confirming it still hangs together: no aircraft double-booked, no rotation that can’t physically turn, no frequency added to a market that can’t absorb it.

That reissue cadence is exactly what makes the SSM/ASM messaging layer busy in a growth phase — incremental changes flowing on top of the last full schedule, each of which has to be read correctly against what came before.

Reading a growing schedule, quickly

All of this is a data operation before it’s anything else. The raw material is a SSIM file — the fixed-width, 200-byte-per-line format the industry exchanges schedules in, where a single multi-carrier feed can span millions of flight-leg records. Every new frequency and every new route is more rows in that file. Growth makes the file bigger and the read slower exactly when you need it faster.

And because SSIM carries no distances and gives times as local values against a UTC-variation field, working out whether a new rotation actually closes — that the aircraft gets back in time to fly its next leg — takes correct date expansion and honest block-time arithmetic, not eyeballing a spreadsheet.

This is the gap SSIM Toolkit is built for. It opens the real schedule file locally, in seconds, and lets you explore the rebuilt schedule — new flights, routes, aircraft, and rotations — then analyse what the growth actually did: capacity and frequency per market, how the hub structure shifted, where the network thickened. Validation and deconfliction run over the same data, so an added frequency that collides with an existing rotation surfaces before it reaches operations rather than after.

Crucially, it does this entirely on your own machine — your schedule data never leaves it. When the fleet plan is a moving target in the good direction, being able to read each rebuilt schedule fast and trust it is just as valuable as it is when deliveries are slipping.

The backlog will take years to work down, and every aircraft that clears it arrives as a schedule waiting to be written. The teams that keep up will be the ones who can read the growth as fast as it lands.

You can read more about the local, deterministic approach on the SSIM Toolkit product page.

---

Sources

• Aerospace Global News — Airbus & Boeing have 12 years of aircraft backlog after April order surge
• Forecast International — Airbus and Boeing Report May 2026 Orders and Deliveries