Sizing a Ropeway: From Riders-per-Hour to Headway

Most explanations of gondola capacity start with a cabin size, a spacing, and a speed, then multiply forward to a riders-per-hour figure. That's the right way to understand the arithmetic, but it's the wrong direction for the question a planner usually actually has: "we need to move about this many people an hour — what does the line have to look like to do that?" Running the same formula backward turns out to be just as revealing, and it exposes a planning trade-off that's easy to miss when you only ever calculate forward.

Starting from a target instead of a design

Suppose the target is 1,800 riders per hour — a reasonably busy line. Cars-per-hour times riders-per-car has to equal that target, so once a cabin size is chosen, the required cars-per-hour (and from it, the required headway and spacing) falls straight out of the arithmetic. Three very differently sized cabins, all aimed at the identical 1,800-riders-per-hour target, land on three very different operating pictures:

• 6-person cabins need a car every 12 seconds — at 5 m/s, that's a cabin every 60 meters.
• 10-person cabins need a car every 20 seconds — at 5 m/s, a cabin every 100 meters.
• 30-person cabins need a car every 60 seconds — at 5 m/s, a cabin every 300 meters.

All three configurations hit exactly 1,800 riders per hour at full capacity — the calculator confirms each one precisely. What differs entirely is how busy the line feels: the 6-person option runs a car past any given point five times as often as the 30-person option, even though both move identical numbers of people per hour.

It's worth being precise about what stayed fixed to make that comparison fair. Line speed was held at 5 m/s across all three, and spacing was the only variable allowed to move to hit the target — which is exactly why the resulting headways line up so cleanly with cabin size. Fix speed and target ridership, and headway is forced to scale in direct proportion to cabin size: a cabin twice as big needs exactly twice the headway to move the same number of people per hour. That's a direct, useful consequence of the underlying formula, not a coincidence of the specific numbers chosen here.

Why headway is the real design variable

Riders-per-hour is the number a planning document quotes, but headway is the number that actually drives engineering decisions. A 12-second headway demands cabins, grips, and a control system all capable of cycling through the terminal that quickly, over and over, all day — a materially harder mechanical problem than a system that only needs to process a cabin every 60 seconds. Small, frequent cabins buy a smoother-feeling ride and shorter waits, but they ask more of the terminal machinery and the grip-cycling hardware discussed elsewhere on this site. Large, infrequent cabins ask less of the terminal cycle, but they demand a stronger cable and structure capable of carrying a much heavier single load, and a much longer, more awkward wait for whoever's unlucky enough to arrive just after one departs on a quiet afternoon.

There's also a load-factor dimension worth folding in here, covered in more depth elsewhere on this site: the 1,800-riders-per-hour target used throughout is a maximum, assuming every cabin departs full. A real line rarely runs at 100% load, which means all three configurations above would, in practice, need to be specified with some margin above the raw target — a planner working from an expected average ridership, rather than a hard ceiling, would size each of these three options a little larger than the numbers above to leave room for a genuine peak. That doesn't change the shape of the trade-off between the three cabin sizes, only the absolute numbers each one would actually be built to.

What a shorter headway means for the wait itself

Headway sets a natural ceiling on how long anyone waits at a quiet station: roughly half the headway, on average, for a rider who shows up at a random moment while cars keep arriving at that steady interval. The 6-person, 12-second-headway option above works out to an average wait around 6 seconds; the 10-person, 20-second option to about 10 seconds; the 30-person, 60-second option to about 30 seconds. Those figures scale directly with cabin size in this comparison, which is worth noticing: bigger cabins moving the same total ridership come with a systematically longer typical wait, not a shorter one, because a bigger cabin needs fewer, more widely spaced departures to hit the same hourly total.

The trade-off in one sentence

Given a fixed ridership target, more cabins spaced closer together beats fewer cabins spaced further apart on wait time and ride frequency, while fewer, larger cabins beats many small ones on how much single-cabin engineering and how much per-cabin cost the system needs to carry. Neither approach is a strictly better answer — a planner is really choosing between "many small mechanical cycles happening constantly" and "occasional large mechanical events," and the right choice depends heavily on terrain, budget, and how the ridership target is expected to arrive across the day, none of which the raw capacity number alone can tell you.

Cost tends to track this same split in practice, though not always in the direction people expect. More cabins circulating at short headway means more grip assemblies to build, inspect, and eventually overhaul, as covered in this site's grip article — a genuinely recurring operating cost that scales with cabin count. Fewer, larger cabins concentrate cost differently: a heavier cabin demands a stronger cable, sturdier towers, and a more powerful drive to move that mass at line speed, all one-time capital costs rather than a distributed, ongoing maintenance burden. Neither cost profile is simply cheaper than the other in general — which one wins depends on the specific project's balance of capital budget against long-run operating budget, a balance this capacity arithmetic can inform but not settle on its own.

Where the constant-speed assumption comes from

All three scenarios above intentionally held line speed fixed at 5 m/s and let spacing move to hit the target, which isolates spacing and cabin size as the two variables actually doing the work. In a real design, line speed is itself a variable worth adjusting — a faster line shortens the ride and, at any given cabin spacing, shortens headway too, letting a smaller cabin hit a higher target than the numbers above suggest. That's a genuinely separate lever from the capacity math here, covered on its own in this site's ascent-time and line-speed article, linked below. Speed isn't a free lever, though — there are practical and safety-driven ceilings on how fast a line can run, particularly around detachable-grip terminal mechanisms and passenger comfort at boarding, so treating speed as infinitely adjustable to hit any target would be a mistake. It's one more variable in the sizing exercise, not an escape hatch from it.

It's worth running the numbers to see how much of a lever speed actually is. Take the 10-person, 100-meter-spacing option from above and push line speed from 5 m/s to 7 m/s while holding spacing fixed: headway drops from 20 seconds to roughly 14.3 seconds, and the achievable riders-per-hour rises from 1,800 to about 2,520 — a genuine capacity gain from the same cabin and spacing, purchased entirely by running the cable faster. That's a real, useful lever, but it's also exactly why line speed shows up so often in ropeway spec sheets: it's one of the few variables that can meaningfully change a system's capacity after the cabins and towers are already built.

A jig-back system breaks this model entirely

Everything above assumes continuous circulation — a steady stream of cabins looping around a circuit at a fixed spacing, which is what the capacity formula on this site models. A jig-back aerial tramway, where typically one or two large cabins shuttle back and forth rather than circulate, doesn't have a "spacing" in this sense at all, and hits its hourly ridership target through an entirely different mechanism: cabin size and the round-trip cycle time, not headway between many cars. Sizing one of those systems is genuinely different arithmetic, covered in a companion article linked below. It's a useful reminder that "riders per hour" as a single headline figure can hide two completely different underlying designs — always worth asking which model actually produced the number before comparing two systems by that figure alone.

Run your own target

The Cable Car Capacity & Throughput Calculator runs this math in the forward direction — plug in a cabin size, spacing, and speed to see the riders-per-hour it produces, then adjust spacing until you land on whatever target you have in mind. See several carrier sizes laid out side by side at one fixed spacing and speed on the Cable Span Reference, or work through the underlying headway concept in more depth in How Many People Can a Gondola Line Actually Move? and Jig-Back Aerial Trams vs Continuous-Circulation Ropeways.