How to build military liaison into a civil drone flight plan

Planning a commercial drone flight near military activity takes more than checking a map and filing an operational plan. Airspace status can depend on the location, the time and the activity taking place. Civil-military coordination should therefore be treated as a distinct planning task, not as a final box to tick.

The steps below are a working checklist, not a substitute for the applicable rules or an airspace authorization. Requirements and contact routes differ between Norway, Sweden, Denmark and other European states. Confirm the current process with the relevant authorities before committing a crew or aircraft.

1. Define the flight before asking for coordination

Write down the intended operating area, dates and time windows, altitude, aircraft and mission purpose. Mark the launch and recovery points, planned route, expected duration and any alternate areas. Include the operating method and the limits the crew will observe.

Be precise about uncertainty. If the schedule has flexibility, state the usable window rather than implying a single fixed slot. If the route or operating area may change, identify what could change and what would require a new coordination check.

This gives a liaison contact enough context to understand what is being proposed. It also helps the operator compare the planned flight with the airspace information available for the relevant place and time.

2. Check the airspace and identify the coordination route

Use current official information to check for restricted or prohibited areas, temporary restrictions and other relevant airspace activity. Check the intended operating period, not just the date on which the plan is drafted. A static map view is not a confirmation that the airspace will be available when the aircraft flies.

Next, establish which authority or military contact is responsible for the area and what process applies. Do not assume that a general inquiry, a routine filing or an application to one body also reaches the military organization that needs to be consulted. If the route is unclear, ask the relevant aviation authority to identify the appropriate channel before treating the plan as coordinated.

Where a mission crosses a national boundary, check each country’s requirements separately. Familiarity with one Nordic state’s process does not establish that the same steps or contact points apply in another.

3. Make the request specific and keep it factual

When contacting the responsible party, provide the operating details in a concise, consistent format. Include the location, requested time window, altitude, aircraft details, mission type, responsible operator and a reliable contact method for the operating period. Explain any constraints that matter to the request, such as a narrow weather window or a fixed site access period.

Ask what information is missing, whether the proposed window is acceptable, and what conditions the operator must meet. Request a clear statement of the outcome and any limits attached to it. Record who provided the response, when it was received and which version of the plan it covers.

Do not treat silence as consent. Nor should a positive response be read more broadly than its stated area, timing or conditions. If the flight plan changes after coordination, check whether the change needs fresh review before operations continue.

4. Turn the response into crew actions

Before the flight, brief the remote pilot and relevant support personnel on the coordination outcome. Put the authorized operating area and time window, applicable restrictions, contact details and escalation steps where the crew can use them. Make sure everyone understands who is responsible for monitoring updates and who can stop the operation.

Agree in advance what the crew will do if the airspace status changes, the planned contact cannot be reached, the aircraft leaves its intended operating area, or the mission can no longer meet its conditions. The safe response may be to delay, relocate, land or abort. Choose actions that fit the operation and the applicable requirements; do not improvise them after a problem begins.

Set a final pre-flight check against current official information and the recorded coordination response. If a key detail differs, pause and resolve it. A coordinated plan is useful only while its assumptions remain valid.

5. Keep an auditable record

Retain the submitted plan, relevant replies, the airspace checks, crew briefing and any changes made. After the flight, record whether the operation followed the agreed limits and note any coordination issue that should affect later missions. This gives the operator a basis for improving its process and showing how it managed airspace risk.

For recurring work, review the checklist when the operating area, mission profile, national process or contact route changes. Do not carry an old coordination result forward to a new flight without checking whether it still applies.

Where advisory support can help

When an operator cannot establish the right liaison route or translate a response into operational controls, outside advice may help clarify the planning task. North Sky Aviation Consultancy offers drone operations and counter-UAS consulting, regulatory compliance assistance and military liaison, and says it works across Norway, Sweden, Denmark and the wider European region. Its advisory work includes helping organizations navigate EASA regulations and Norwegian aviation law.

That support does not replace the responsible authority’s decision or the operator’s duty to meet applicable requirements. The practical test is simpler: before launch, can the team show what airspace information it checked, who it coordinated with, what conditions apply and what it will do if those conditions change?