Three thousand vehicle movements a day

Approximately 3,000 vehicle movements a day is the estimate attributed to the proposed 1,200 dwellings at Arrow Junction. It is the second-largest number in this file, and it is the one residents will feel first, longest and most often.

A vehicle movement is one trip in one direction. It is not one vehicle and it is not one household — it is an arrival or a departure. Movements are counted that way because that is what a road actually experiences. The distinction matters here only because it is the first thing anyone disputing the figure will reach for, and we would rather set it out than be corrected on it.

Where they go

Traffic generated at Arrow Junction does not remain at Arrow Junction. It loads onto a small number of corridors, each of which is already doing a job:

• State Highway 6. The regional spine. Movements added here are added to a route that carries through-traffic, freight and visitors, and that has limited alternatives when it is disrupted.
• Gibbston Valley Road. A local road serving an established valley, its residents and its visitor economy. Local roads absorb development traffic at a very different tolerance to a state highway.
• Crown Range Road. The alpine approach, with the constraints that come with it — gradient, weather, seasonal closure risk and a narrow tolerance for incident.

Those three names are the whole geography of this problem. A development's traffic effect is not what happens at its own entrance; it is what happens where its traffic joins everyone else's.

Accumulation is the effect, not volume

The instinct with a traffic number is to argue about whether it is big. That is the wrong argument. The effect of development traffic is where and when it accumulates: at intersections, on a single approach, in the hours when the corridor is already at its least forgiving, and in the seasons when the corridor is carrying its heaviest non-local load.

So the questions that decide a traffic case are not about the total at all:

• How are the ~3,000 movements distributed across the three corridors, and on what assumption?
• What is the peak-hour share, and at which intersections does it land?
• What is the assumed trip rate per dwelling, and what occupancy and vehicle ownership does it assume?
• Is construction traffic inside or outside the figure, and over what period?
• What safety assessment has been done for the Crown Range Road approach specifically, given its gradient and weather exposure?
• What mitigation is proposed, who builds it, who pays for it, and when relative to occupation?

On every one of those, what is available to us is the headline estimate and not the working behind it — [Source to be added]. A traffic figure without its distribution, its peak and its assumed trip rate is not something a reader can check, and it is not something a commissioner should have to accept on trust.

What the figure does and does not include

We do not know. That is the honest answer and it is worth stating plainly, because the difference between an estimate that includes construction, visitor and service traffic and one that does not is the difference between two quite different roads.

We have not adjusted the figure, scaled it, converted it to an hourly rate or applied a peak factor. Doing any of that would be inventing a number and attributing it to the applicant, which is the exact failure this site exists to avoid.

What we are asking for

The traffic modelling that answers these questions is the third milestone on our funding ladder — Support the Investigation. It is ordinary professional work, it is not cheap, and it is the only thing that turns a disputed headline into evidence a decision-maker can weigh.

Until it exists, this article says only what it can support: that a substantial daily movement figure is on the record, that it discharges onto three named and constrained corridors, and that the working behind it has not been published. Read the fuller case on Traffic & Transport. Ridgeburn Limited and Queenstown Lakes District Council may respond in full — that is our standing right of response.

Evidence statement

Classification: Analysis

Status: Ridgeburn Press analysis of a published estimate. Modelled figures are the applicant's; the distribution, peaks and assumptions behind them have not been published to us.

Author: Ridgeburn Press · Analysis

Last reviewed: 16 September 2026

Sources

1. Traffic generation estimate for the proposed Arrow Junction development, applicant material — [Source to be added]
2. Corridor and intersection assessment, SH6 / Gibbston Valley Road / Crown Range Road — [Source to be added]

Assumptions

• The ~3,000 daily vehicle movements figure is used exactly as published, with no hourly, peak or seasonal derivation by us.
• A vehicle movement is treated as one trip in one direction, the standard convention; the applicant's convention has not been confirmed to us.

What is not established

• The distribution of movements across the three corridors.
• The peak-hour share and the intersections it affects.
• The trip rate, occupancy and vehicle ownership assumptions behind the estimate.
• Whether construction traffic is inside or outside the figure.
• Any mitigation, its funding, or its timing relative to occupation.

Right of response

Ridgeburn Limited, Queenstown Lakes District Council and any person named here may respond in full. How to respond.