Quick answer

Treat a helicopter supply drop as a coordinated logistics task: agree on who is flying, what the ground squad needs, where the current approach is safe and which prompt the active aircraft and seat show. The official game and store pages describe US helicopters in supply-drop context. The Patch 1.3 notes report fixes for a misleading HQ supply-helicopter prompt, supply-drop UI flicker and supply VFX/collision behavior, but they do not publish a universal action key or a fixed drop route.

Who does what

| Role in the task | Responsibility | Evidence boundary | | --- | --- | --- | | Pilot | Fly the current aircraft, read the active prompt and leave the area after the task. | The live client determines the seat controls and prompt. | | Logistics passenger or ground lead | State the requested objective, timing and safe receiving area. | Do not treat a role label as proof of a particular inventory, cooldown or drop quantity. | | Receiving squad | Confirm the request, keep the approach clear and report whether the intended task was completed. | A squad call is coordination evidence, not a universal aircraft rule. |

Official Patch 1.2 notes also describe Pilots and Logistics Officers riding as helicopter passengers. That role context helps explain the workflow; it does not settle every seat action or platform binding.

Before flight

  1. Open [Controls → Pilot] through the Helicopter Controls guide and read the current action labels.
  2. Ask the squad for one clear logistics objective instead of a vague request to “drop somewhere.”
  3. Confirm the receiving area from the live map and match, not from a permanent landing-zone or route claim.
  4. Identify an approach and a way out. If the area becomes blocked or contested, the pilot should abort and report the change.
  5. Agree on the prompt, seat and communication channel that will confirm the task.

Drop workflow

  1. Brief. Say the objective, approach, receiving area and abort condition.
  2. Approach. Reduce speed early enough to keep the aircraft controllable and keep the route visible.
  3. Check the prompt. Read the action shown by the current aircraft and seat. Do not copy a letter from a different layout or a community post.
  4. Complete the action. Use the current client prompt when the aircraft state and location support the supply task.
  5. Confirm. Have the ground squad report the result, then leave or reposition according to the next objective.

This sequence is deliberately task-first. The reviewed official sources confirm the supply-drop use case and Patch 1.3 fixes, but they do not provide a complete current key table, payload value, cooldown or map-wide drop rule.

Common failure states

The HQ prompt is misleading

Patch 1.3 specifically reports a fix for a misleading Supply Helicopter prompt at HQ. If the current client still shows a confusing prompt, record the build, aircraft, seat and location before reporting it; do not replace the prompt with a guessed binding.

The supply action does not appear

Check the active seat, aircraft and current prompt first. Then confirm that the squad’s request is actually the supply task rather than transport or another support job. A public catalogue cannot prove what your current preset displays.

The UI flickers or the supply effect looks wrong

Patch 1.3 reports a supply-drop UI flicker fix and supply VFX/collision fixes. Recheck the current build and capture the exact symptom if it persists; do not infer that the drop failed from a visual effect alone.

The approach is no longer safe

Use the Hot LZ Insertion guide for the land-or-abort decision. Logistics value does not override a blocked approach or a changed squad objective.

Ground coordination

Give the receiving squad a short, repeatable call:

  • the task being requested;
  • the area or live-map landmark being used;
  • the preferred approach and the condition that cancels it;
  • the signal that confirms the delivery or asks for a reset.

Do not publish a permanent supply route, fixed helipad or guaranteed drop location from one match. The current mode, objective and live terrain decide whether the plan is useful.

Media context

Official launch media shows helicopters in the Vietnam battlefield; it is visual context, not evidence of payload values, routes or keybinds.Official HLL Vietnam game pageChecked: 2026-09-03

The image supports the supply-and-battlefield context of the task. The source does not establish which aircraft, seat or prompt a current match will provide.

Frequently asked questions

What should I check before a Hell Let Loose Vietnam helicopter supply drop? Confirm the squad objective, receiving area, approach, abort condition, active seat and current aircraft prompt before attempting the task.

Does Patch 1.3 reveal the universal supply-drop key? No. It reports prompt, UI, VFX and collision fixes, while the current Controls → Pilot prompt remains the source for the active layout.

Can a public keybind list prove that a supply drop will work? No. A catalogue can be a lead, but the aircraft, seat, preset and current client prompt decide the action available in your match.

What should the pilot do when the receiving area becomes unsafe? Communicate the change, abort the approach, regain a stable flight state and wait for a new task call instead of forcing the delivery.

Sources

Last verified: September 3, 2026. Official helicopter context and Patch 1.3 supply-related notes were checked; exact prompts, bindings, payloads and routes require the current client and match.