Vehicle Ferry Capacity: Lane-Metres, Tonnage, Height, and Why It Matters
It's a peak Saturday. The 11:15 sailing shows "full" — 60 cars, sold out — and the queue at the terminal is forty deep. The skipper looks at the deck and counts eighty lane-metres of empty floor: enough for sixteen motorbikes, four small hatchbacks, and a single-axle camper trailer. The booking screen disagrees. It says zero. The ferry sails three tonnes lighter and twelve metres shorter than it could have. Multiply across a season and you have one of the most expensive accounting errors in vehicle ferry operations — and it isn't on the books anywhere.
Why "one car, one spot" stopped working
Vehicle ferries don't sell spots. They sell a finite quantity of three things at once: length of deck, weight on the deck, and height clearance under any covered area. A 1.4-metre hatchback and a 5.8-metre Land Cruiser both consume "one vehicle space" in a flat-count system. On the actual deck they consume different amounts of three different resources. A motorbike sits in 1.5 lane-metres. A car-and-trailer rig takes 9.5. A refrigerated truck weighs eleven tonnes and stands 3.9 metres tall — too tall for the covered deck on a small RoRo with a 3.5-metre clearance, but fine on the open deck.
The flat-count model — "this ferry has 60 vehicle spaces" — is a convenient abstraction. It's also the wrong shape for the physical reality. Once peak season exposes the gap between the abstraction and the deck, the cost shows up in three places at once: refused-but-fittable vehicles at the dock, manifests that don't match what's actually on board, and capacity-utilisation reports that systematically underestimate the operator's real load factor.
Operators running tide-aware schedules, mixed cargo, and dynamic seasonal loads have always known this. The question is whether the booking system on top of the operation knows it too.
What multi-dimensional capacity actually looks like
A vehicle ferry has several capacity dimensions that all need to clear before a vehicle gets a place on the deck. Get one wrong and the deck doesn't load. Track only one and you sell the wrong sailings full and leave the right ones half-empty.
The dimensions that matter:
Lane-metres: total length of vehicle deck, by lane. A 200-lane-metre deck holds any combination of vehicles whose summed length fits — six 4.5-metre cars and ten 1.5-metre motorbikes (42 + 15 = 57 lane-metres), one 18-metre B-double, or a Tetris-style mix.
Tonnage: how much weight the deck can carry. A vessel rated to 80 tonnes deck-load will refuse a heavy-truck combination that fits the lane-metres but exceeds the gross.
Height clearance: the lowest overhead obstruction on covered decks. A 4.2-metre fridge truck cannot board a deck rated to 3.8 metres, regardless of length or weight. A hard stop, not a percentage adjustment.
EV spaces: electric vehicles need either charging-equipped bays or, more commonly today, a known count of fire-safety-segregated spots. Conventional vehicles can use EV spots; EVs can only use EV-marked spots.
Vehicle class restrictions: motorbikes forbidden from the open-truck deck in heavy weather; hazmat loads to the open deck with separation distances; trade vehicles to the lower deck. Constraints that override "length fits" — the deck has rules about which vehicles, not just how many metres.
Each gets checked independently for every booking. A walk-up Land Cruiser on the 11:15 needs lane-metres available and open-deck height clearance and tonnage budget still in the green. That's not pedantry — it's the safety boundary the maritime authority will ask the operator to evidence if anything goes wrong.
The math: 200 lane-metres, loaded two ways
Pick a typical regional vehicle ferry. 200 lane-metres of usable deck, 70 tonnes gross deck-load, 3.8 metres covered-deck clearance. Average ticket revenue $52 per vehicle. Peak Saturday sailing.
Loaded as flat count (60-vehicle ceiling): The booking system caps at 60 vehicles regardless of mix. By 9 AM, 60 cars are booked and the sailing locks. The 11:15 departs with 60 cars averaging 4.6 lane-metres each = 276 lane-metres planned, but the deck is only 200, so dock crew turn vehicles away at boarding. Effective load: 200 lane-metres (the deck is physically full at 43 cars). 17 paid passengers shuffled to the 13:30. Revenue captured: 60 × $52 = $3,120.
Loaded by actual capacity: The booking system sells against the real number — 200 lane-metres. The 11:15 fills with a realistic mix: 35 cars (4.6m avg = 161m), 8 motorbikes (1.5m = 12m), one panel van (5.2m), one car-and-trailer rig (9.0m), one ute with kayaks (5.0m). Total: 192.2 lane-metres. 7.8 still bookable — room for two more motorbikes or a small car. Effective load: 196.2 lane-metres (98% deck utilisation). 46 vehicles ticketed at a class-weighted average of ~$48 = $2,208 — less per sailing on the surface.
Now the second pass. The flat-count scenario also turned away 17 vehicles that didn't fit the 60-vehicle ceiling but would have fit the 200-lane-metre deck. The accurate-capacity scenario re-sells those onto the same sailing as motorbikes and small cars. Revenue actually captured: 46 + 8 reclaimed walk-ups = 54 vehicles × $48 = $2,592 on the 11:15, with the queue cleared so the 13:30 doesn't lose customers either. Across a peak day of 6 sailings, the accurate-capacity model captures ~$2,800 more in revenue with a tenth of the dock-side conflict.
The number to focus on isn't the per-sailing delta. It's the lane-metres lost per peak day — the number of metres of empty deck that left the dock because the booking abstraction couldn't see them. For most operators we've spoken to, the back-of-envelope figure runs 60 to 120 lane-metres per peak day per vessel. Across a 90-day peak season, that's somewhere between 5,400 and 10,800 lane-metres of unsold deck — equivalent to 12 to 24 fully-loaded sailings, never run.
That's not a marketing number. It's a measurement problem.
What to look for in a booking platform
The capability to model this isn't exotic, but it is specific. Some checks for any operator evaluating a system on vehicle-ferry vertical fit:
Lane-metres as a tracked unit of capacity, not a derived field calculated after the fact. The system should let you set a deck's total lane-metres and consume from it per vehicle, per vehicle class, per sailing.
Tonnage as a parallel track — same vehicle reduces lane-metres and tonnage in the same transaction, both checked independently before the booking confirms.
Height as a constraint per deck or per deck-section, not a free-text warning. A 4.2-metre vehicle should be unbookable onto a 3.8-metre covered deck via any channel — direct, OTA, agent, walk-up POS — without the operator manually intervening.
EV spaces as their own count, with the option to release unsold EV-marked spots to conventional vehicles at a configurable point before departure.
Trailers as bookable items in their own right — not bolted onto the towing vehicle's record. A car-and-trailer is two units of inventory: the car (4.5m, 1.5 tonnes) and the trailer (3.0m, 0.5 tonnes), each ticketed, each priced, each loaded independently. Detach the trailer at the destination and it's the trailer's own record that travels back.
A vehicle catalogue with real make/model/year/body-type dimensions, so the customer answering "2019 Toyota HiLux" doesn't have to type "5.3 metres, 2.1 tonnes, 1.85 metres tall" themselves. The dimensions land on the booking automatically.
Per-class loading rules — motorbikes forbidden from the open-truck deck, hazmat to the open deck only, trade vehicles to the lower deck. Configured once, enforced everywhere.
Manifest output that names what's on board, by vehicle class, lane-metres consumed, weight contribution, and overhead clearance occupied — the document the maritime authority will ask for.
A platform that handles two or three of these is fine for a single small vessel. A platform that handles all of them is the difference between accurate capacity selling and an annual peak-season write-off.
A back-of-envelope formula for your own ferry
Three numbers, ten minutes. Worth doing before any peak season.
Take your average sailing's effective deck length: lane-metres available after operational margins (the metres you'd actually sell to a customer, not the metres on the survey drawing).
Multiply by the percentage of vehicles you turned away or shuffled to a later sailing during last peak season, expressed as a fraction of total bookings. If you don't have the number, the dockmaster's gut figure is close enough for this calculation.
Multiply by your average vehicle revenue.
Lane-metres × turn-away fraction × $/vehicle = annual revenue left on the dock.
Operators running 200-lane-metre decks at 15% peak-season turn-away with $50 average vehicles are looking at roughly $1,500 per peak day, $135,000 per 90-day season. That's a single, deck-load-shaped capacity gap with a number attached. The figure should be uncomfortable. It's a useful uncomfortable.
The follow-up question — which of those turn-aways would have fit if the system understood the deck? — decides whether the gap is solvable through software or whether the operator genuinely needed a second vessel. Most of the time, on the operations we've talked to, the gap is solvable.
Where this goes next — EVs, councils, audit
Three forces are moving the multi-dimensional-capacity question from "useful" to "non-optional" over the next few seasons.
EVs. EV share of new vehicle sales has climbed into double digits across Australia, the UK, and Europe over the past three years (see the Federal Chamber of Automotive Industries for Australian monthly figures; the UK SMMT and European ACEA publish equivalents). On ferries serving popular EV routes, the mix already runs higher than the national average. EVs are heavier than equivalent combustion vehicles, require fire-safety segregation under maritime guidance (both the Australian Maritime Safety Authority and the UK Maritime and Coastguard Agency have issued advisory material), and increasingly come with onboard-charging expectations. Dedicated EV spaces stop being a flag in the booking flow and start being a hard count the system has to hold and release independently.
Council and PSO-contracted operations. Operators running under council Public Service Obligation contracts, regional subsidies, or community-service routes face audit requirements that flat-count capacity reporting can't satisfy. The auditor wants to see lane-metres delivered, tonnes carried, vehicles refused-and-why, refunds processed, weather cancellations communicated — the deck-level truth with timestamps. Operators on lane-metre-accurate systems are exporting it; operators on flat-count systems are reconciling it manually after the fact.
Insurance and incident investigation. After any deck-load-related incident — a rollover in a swell, a stability warning the master had to clear — the post-incident review reaches for the manifest. A manifest that says "60 vehicles" doesn't answer the questions the marine surveyor will ask. A manifest that says "47 vehicles, 187.2 lane-metres, 62.3 tonnes deck-load, no vehicle exceeded 3.6 metres overhead" does.
These pressures converge. The booking system implemented when the schedule was simpler and the cargo was mostly cars is the same one now being asked to satisfy EV segregation, council audit, and insurance documentation. It's not a graceful fit.
Capacity that matches the deck
Vehicle ferries have always had length, weight, and height constraints. Skippers and dockmasters have always done the mental Tetris. The question is whether the booking system on top is helping or working against them.
The practical move for any operator evaluating their options is to model one peak sailing on paper — actual deck, actual mix, actual queue — and compare it to what the current booking system would have allowed. The gap is usually visible inside an hour. So is the revenue.
JetSetGo's multi-modal booking platform models vehicle capacity along all the dimensions above — lane-metres, tonnage, height, EV spaces, vehicle catalogue, trailers as separate ticketed items, per-deck loading rules, and manifests that report against each.
Two related reads: The Hidden Economics of Ferry Operations → covers the per-sailing revenue mechanics, and Peak Season Capacity Management: Mathematical Models That Actually Work → covers the broader load-factor question.
Book a demo → to see vehicle deck capacity configured against a sailing of your own.