Products · Heavy-Lift and Civil Logistics

Logistics Configuration for Mountain Delivery

Mountain delivery is an altitude and terrain problem before it is a payload problem. Density altitude quietly removes payload margin.

2 of 10Method note

Overview

Calculate at the density altitude of the actual delivery point, not at the valley launch site.
Identify a landing or hover-drop point that is genuinely reachable and genuinely flat enough.
Terrain relief can block the direct line for the datalink even when it does not block the flight path.
Plan for a wind that differs between the valley and the ridge on the same day.

Mountain logistics is dominated by density altitude and wind

Two physical effects decide whether a mountain logistics route works, and neither appears in a payload figure. The first is density altitude: as elevation rises, air density falls, rotors produce less thrust for the same power, and the aircraft's effective payload capacity drops. A route that works at sea level can be impossible at the same mass two thousand metres higher, and the shortfall is not linear with mass.

The second is wind, and mountain wind is not ordinary wind. It flows over terrain and produces lift on windward slopes and turbulence and rotor on lee slopes; it accelerates through saddles and gaps; and it changes direction with time of day as slopes heat and cool. A route planned against an average wind figure will meet conditions worse than that figure on a predictable fraction of days, and those days are when the programme loses its schedule.

So the first thing to establish for a mountain route is the elevation profile and the wind distribution along it, not the payload. Get the elevation gain, the highest point, the passes and saddles the route crosses, and the wind behaviour at those specific features. That information, more than any aircraft specification, determines whether the route is viable at the mass you need.

Route design and the launch point problem

Mountain routes are usually constrained at both ends. The lower launch point is often fine — accessible, with space — and the upper delivery point is the difficulty: a small ledge, a ridge, a valley floor with obstacles, or a slope with no flat ground at all. Survey the delivery point as carefully as the launch point, because it is where the aircraft has the least margin and the least room.

Where the delivery point cannot accept a landing, the options are a hover release or a low-pass drop, and they have different requirements. A hover release needs stable hover capability at that elevation with the load attached, which is the most demanding condition in the whole flight. A low-pass drop needs less hover performance but requires the load to survive impact and the drop area to be clear and suitable — and it trades precision for feasibility.

Route design should also account for the return leg being different from the outbound leg. Outbound is loaded and usually uphill; return is lighter and downhill. Wind that helped outbound may oppose the return, and the elevation profile that cost energy on the way up may not give it back. Plan the round trip as two different legs rather than as one symmetric route.

Load handling in thin air and turbulent conditions

Payload capacity at altitude is lower, and the temptation is to load to the sea-level figure and hope. That is the failure mode to design against. Establish the capacity at the highest point of the route with the wind margin applied, and set the operating load below it with a documented margin. Write the limit into the operating procedure rather than leaving it to crew judgement.

Load dynamics matter more in turbulence. A slung load that is benign in smooth air becomes a pendulum in mountain rotor, and it can drive the aircraft in ways the flight controller cannot reject. Where the route crosses turbulent features, prefer a rigidly mounted load in a secured container, and keep the load's centre of gravity close to the aircraft's intended envelope.

Cold and moisture are part of the same environment. Batteries lose usable capacity in cold, and mountain sites are frequently cold and damp even in summer, particularly at dawn and dusk when wind is often calmest and flying is otherwise most attractive. Plan battery management around the actual temperature at the launch altitude, not around the temperature at the base.

Operating windows and programme realism

Mountain routes have narrower operating windows than flat-terrain routes, and the programme should be planned on that basis. Wind typically builds through the day as slopes heat; weather can arrive quickly and locally; and the combination of a narrow calm window and a long turnaround can mean one usable sortie per day rather than the several the plan assumed.

That reality argues for measuring the window before committing to a schedule. A short period of on-site observation — wind by hour, cloud base, temperature, and how often conditions exceed the operating limit — converts an assumed schedule into a realistic one. It costs days and it is the cheapest insurance available for a mountain programme.

It also argues for designing the programme so a lost day is recoverable. Buffer in the schedule, the ability to add sorties on good days, and a defined rule for what happens when a delivery cannot be completed — including whether the load comes back or is left at a safe intermediate point.

Configuring a mountain route

The configuration we would propose starts with a route survey: elevation profile, highest point, saddles and passes, delivery point survey, and wind distribution by hour. From that we derive the achievable payload at the highest point with margin, and the sortie count the realistic window supports.

Where a route pushes beyond standard capability — very high elevation, long legs, unusual load geometry — it should be scoped as engineering work with a field trial before volume commitment. Our field testing and data collection work covers running that trial, and operating environment requirements covers formalising the environment envelope.

Send your route profile, elevation gain, delivery point description, load mass and dimensions, and the season you need to operate in to our engineering team. We will tell you what is achievable and what is not, and we will say so before you plan a schedule around a capability the route does not support.