Drone by Nature

UAV Mission Preparation : From Mission Understanding to the GO/NO-GO Decision

UAV Mission Preparation : From Mission Understanding to the GO/NO-GO Decision

1 - Understanding the Mission Objective

UAV mission preparation begins long before airspace analysis or aircraft checks. The first step is to clearly understand why the UAV is being deployed and what the mission is expected to achieve.

The initial information provided by the client or mission requester gives the UAV team a general understanding of the operation. This first request then needs to be refined in order to understand the actual conditions under which the mission will be conducted.

From my operational experience, several pieces of information are particularly important at this stage: the intended area of operation, the nature of the mission, the expected start time and duration, and the result or service expected from the UAV team.

For example, a short observation task and continuous surveillance of the same area may require very different preparations. Mission duration can influence aircraft selection, battery requirements, crew organisation and the ability to maintain continuous aerial coverage.

The mission may also involve requirements beyond simply flying the aircraft. Real-time video transmission to a command post is a good example. In some operational environments, providing an aerial view is only part of the requirement. That imagery may also need to be transmitted live to those responsible for coordinating the operation. This requirement needs to be identified early, as it can affect the equipment, communications systems and overall organisation required for the mission.

Understanding the mission also means making an important distinction between the operational effect required and the technical solution used to achieve it.

A mission requester may, for example, ask the UAV team to monitor the northern and eastern sectors of a site. It is then the responsibility of the UAV team, as the subject-matter expert, to assess the requirement and propose the most appropriate operating position and flight concept.

The objective may be to select a position that provides effective coverage of both sectors while minimising the need to relocate the crew and its equipment during the operation. The proposed solution can then be presented to the person responsible for the overall operation for approval.

In other words: The requester defines the operational need. The UAV team translates that need into a safe and achievable aerial solution.

This does not mean that the UAV team operates without constraints. The proposed solution must remain compatible with the applicable regulatory framework, operational environment, airspace structure and safety requirements. These elements will form part of the next stages of mission preparation.

If information is missing, unclear or contradictory, the operator should not hesitate to go back to the requester before continuing the planning process.

A few additional questions at the beginning of the process can prevent an entire mission from being built around a misunderstanding. A mission can be perfectly prepared from a technical perspective and still be the wrong mission if the original objective was not properly understood.

2 - Analysing the Operating Environment and Airspace

Once the mission objective has been clearly understood, the next step is to determine whether the environment in which the UAV will operate allows the mission to be conducted safely.

This assessment must consider both the ground environment and the airspace surrounding the area of operation.

An initial assessment can be carried out using mapping and satellite imagery tools. In France, for example, Géoportail can be used alongside tools such as Google Maps. In other countries, equivalent national or local resources may be available.

The objective is not simply to locate the mission area, but to understand the environment in which the UAV team will be operating.

Terrain characteristics should be assessed, including elevation changes, hills, mountains, rivers and other natural obstacles. Infrastructure that may affect the operation should also be identified: motorways, railway lines, power lines, populated areas, as well as particular or sensitive sites such as government facilities, prisons or energy infrastructure.

Understanding the aviation environment

The assessment must then be extended to the aviation environment.

Airports, aerodromes, heliports, model aircraft sites and any other aviation activities that could interact with the mission should be identified.

Where relevant, aeronautical information can then be used to develop a more detailed understanding of the area: runway orientations, aerodrome traffic patterns, arrival and departure routes, as well as any particular airspace structure that could affect the operation.

The objective is therefore not simply to identify the nearest airport. The UAV team must identify all aviation activities and relevant airspace stakeholders that could interact with its intended operating volume.

Selecting the right operating position

All of this information contributes to an essential decision: selecting the UAV team’s operating position.

The closest position to the area of interest is not necessarily the safest or most effective one. Whenever the mission allows it, I prefer an isolated position, away from populated areas and with as little presence of uninvolved people as possible.

First, this helps reduce the potential consequences of a UAV failure. A sufficiently clear area may also provide an emergency landing option if required. But the value of an isolated operating position is not limited to ground risk.

The presence of members of the public around the Remote Pilot can also become a human-factor issue and a source of distraction. People approaching the crew, observing the operation, asking questions or having to be moved away require attention at a time when the team needs to remain fully focused on the mission.

The closest operating position is therefore not necessarily the best one. The best position is the one that allows the mission to be accomplished while keeping the associated risks under control.

The selected position must, of course, remain compatible with the intended concept of operations, whether the mission is conducted under VLOS or, where permitted by the applicable framework, BVLOS conditions.

Considering communication requirements

The choice of operating position may also be influenced by communication requirements. When real-time video transmission is required to a command post or another operational location, network availability and reliability become factors that need to be considered during mission preparation.

Depending on the available systems and operational architecture, transmission may rely on a cellular network, a local network or, where necessary and available, a satellite solution.

Connectivity should therefore not be something discovered at the moment of take-off: it is part of the operating environment that needs to be assessed.

Author-approved photograph with confirmed public-use rights
Figure 1 - Pre-flight airspace assessment. Reviewing aeronautical charts and airspace constraints as part of UAV mission preparation.

Coordinating the use of airspace

Once the potential operating position and flight volume have been identified, the airspace assessment can become more precise.

Where several aviation stakeholders or specific airspace structures are involved, coordination with each relevant organisation may be required several days before the mission.

This coordination can be used to present the intended operation, define the operating area, planned altitude and operating times, and obtain any required authorisations or access credentials under the applicable framework.

The objective is to ensure that the UAV operation can safely coexist with other aviation activities in the area.

One principle should always remain in mind : operating a UAV does not give it priority over manned aircraft.

Keeping the assessment dynamic

However, the assessment carried out during mission planning cannot be considered final. A mission may be prepared several days in advance, while the aviation, meteorological or operational environment can change in the meantime.

As the mission approaches, relevant aeronautical information should therefore be reviewed and updated. Depending on the country and applicable framework, this may include NOTAMs, the AIP, AIP Supplements, as well as available meteorological information and forecasts.

On the day of the mission, another assessment is required. Where prior coordination has been established, contact with the relevant stakeholders allows the planned conditions to be confirmed: operating area, flight altitude, operating times and expected duration.

During the flight, when operating close to an airport, aerodrome, heliport or other relevant aviation activity, airspace awareness must continue to be maintained. Where appropriate and permitted within the operational framework, monitoring the relevant aeronautical frequency can help the UAV team maintain situational awareness of surrounding air traffic.

This radio monitoring can provide early awareness of aircraft arriving, departing or operating near the UAV operating area, allowing the team to adapt or temporarily suspend the operation if necessary. It complements visual observation of the surrounding airspace and any coordination established before the mission.

Available aeronautical and meteorological information should also be reassessed. Where relevant, observations and forecasts such as METARs and TAFs can contribute to this assessment.

Airspace assessment is therefore not a snapshot taken during mission planning. It is a continuous process that must be updated until the moment of take-off.

An area that was perfectly suitable several days earlier may no longer be suitable on the day of the mission: deteriorating weather conditions, a new airspace restriction, unexpected aviation activity, an authorisation that has not been confirmed, or a change in operational conditions.

Assessing the environment is therefore not only about determining where the UAV can fly. It is about determining whether the planned mission can still be conducted within acceptable safety conditions.

And if all the necessary conditions are no longer met, the decision must be straightforward: NO-GO.

3 - Preparing the Aircraft, Crew and Contingency Plan

Once the mission has been clearly understood and the operating environment assessed, the next step is to prepare the resources that will actually be used to conduct the operation  and to anticipate what will happen if something does not go as planned.

This is not simply about having a UAV that is capable of flying. The aircraft must be suitable for the mission, properly configured and tested. The crew must understand their roles and the procedures they may have to apply.

Finally, contingency measures should be prepared before take-off so that the crew does not have to improvise when something goes wrong.

Selecting the right aircraft for the mission

The aircraft should be selected according to the operational requirement identified during mission preparation.

If the mission requires thermal imagery, the selected UAV must provide the appropriate capability. If weather conditions are challenging or expected to deteriorate, resistance to wind and environmental conditions becomes an important consideration.

For longer operations, endurance may become one of the main selection criteria. The objective is therefore not necessarily to select the most capable aircraft available, but rather the aircraft that provides the right operational value for that specific mission.

Whenever possible, I also prepare a second aircraft as a spare. A technical failure affecting the primary UAV should not necessarily result in the loss of the entire operation if another suitable system is available.

The same principle applies to energy management. The number of batteries is planned according to the expected mission duration, with additional capacity available in case the operation lasts longer than anticipated. For extended operations, I also bring an external power source and the appropriate chargers so that batteries can be rotated and recharged in the field.

Redundancy does not replace preparation. It simply provides another option when something unexpected happens.

Preparing the equipment before deployment

Technical preparation should, as far as possible, be completed before arriving on the operational site.

Firmware and software versions for the aircraft, batteries and remote controller are checked. Sensors are inspected and cleaned when necessary. Storage media are prepared and formatted directly through the system that will use them. Communication equipment, including VHF when required, is also configured with the appropriate frequencies for the operation.

Software updates require particular attention. An update discovered in the field immediately before or during an operation should not normally be installed unless it is required for operational or safety reasons.

A new version may change system behaviour or introduce an incompatibility that has not yet been tested by the crew. Whenever possible, updates should therefore be completed early enough to allow the system to be tested before operational deployment.

The principle is simple : Mission day is not the time to discover how a new software configuration behaves.

Configuring the aircraft for the operation

Before take-off, the aircraft configuration must reflect the operation that is actually going to be conducted.

This includes the planned flight height, distance limits, Return to Home point and the aircraft behaviour in the event of a lost command-and-control link  whether that means holding position, landing or automatically returning, depending on the environment and the selected contingency procedure.

The RTH point must also remain consistent with the crew’s actual position. If the Remote Pilot moves during the operation, and the system allows it, the RTH configuration should be reassessed so that an automatic recovery does not send the aircraft towards a location that is no longer appropriate.

Battery condition is also part of the pre-flight checks. An abnormal voltage difference between individual cells may indicate a battery that should not be used operationally. In my own practice, a battery showing an excessive cell imbalance is removed from service and clearly marked so that it cannot accidentally be used again during the operation.

During long missions, battery management becomes part of the operational organisation itself. For example, I may deploy with around ten batteries. Once the first batteries have been used, they are allowed to cool before being connected to an external power source for recharging while other batteries continue supporting the operation.

Battery alerts and return thresholds are also configured before flight so that the decision to return is not left until energy margins become critical.

Preparing the crew as carefully as the aircraft

A properly prepared aircraft is not enough if the crew itself is not prepared.

In my operational environment, I work with an Aerial Observer. The observer understands the mission, operating area, planned flight height, route and communication methods.

The briefing must also cover the Emergency Response Plan (ERP) and clearly establish everyone’s responsibilities.

The Aerial Observer is not simply an additional pair of eyes. The observer contributes directly to operational safety and may handle VHF or telephone communications, contact relevant organisations, or call emergency services when required.

If the Remote Pilot suddenly becomes incapacitated, and when the crew organisation, training and aircraft configuration allow it, the observer should know what action has been planned to secure the aircraft. In my operations, this can include activating the predefined Return to Home function.

If the UAV crashes and someone is injured, the observer must be ready to contact emergency services without unnecessary delay.

The same principle applies to other emergencies. If a battery catches fire, for example, the observer should know where the appropriate emergency equipment is located and be able to bring it to the incident area while the situation is being managed.

This organisation is naturally easier when the Remote Pilot and Aerial Observer are operating close to each other, particularly during VLOS operations. In some BVLOS operations, however, crew members may be geographically separated. This makes clearly defined communications, responsibilities and emergency procedures even more important.

An emergency procedure should never be discovered when the emergency is already happening.

Author-approved photograph with confirmed public-use rights
Figure 2 - Pre-flight checks: The Remote Pilot verifies the aircraft and flight controls before take-off, ensuring the equipment is ready for the mission.

Testing before the mission actually begins

Take-off does not necessarily mean that the mission has started.

After take-off, I initially stabilise the aircraft at a low height - typically around five metres when the environment allows it - and perform a final functional check. I verify roll, pitch, climb and descent response. I also test the camera movements, zoom functions and thermal capability when required for the mission.

The purpose is to identify a problem while the aircraft is still close to the crew and can easily be recovered, rather than discovering it after reaching the operational area.

But the check does not stop there. Once the aircraft’s basic functions have been confirmed, I climb to the planned Return to Home altitude and perform a full 360-degree visual check of the surrounding environment.

The objective is to verify that no obstacle around the operating position could interfere with an automatic return at that altitude. If an obstacle is identified, the RTH altitude is reassessed and, when operational and regulatory conditions allow, increased to provide a safer return trajectory. This local check complements, but does not replace, assessment of the full potential return route.

This is an important distinction : An RTH altitude defined during planning remains theoretical until it has been confronted with the aircraft’s actual operating environment.

The functional check is also about more than determining whether the aircraft can physically fly. A UAV may have fully functional motors, navigation and flight controls and still be unsuitable for the mission.

If thermal imagery is essential to the operational requirement but the thermal sensor is unavailable, I do not continue the mission. The same applies if long-range observation is required but the necessary zoom capability is not functioning.

The aircraft might still be able to perform part of the task, but if it cannot deliver the required operational result, continuing the flight would not fulfil the original mission objective.

Airworthy does not necessarily mean mission-ready.

A spare aircraft is not a shortcut

If an anomaly requires the primary aircraft to be replaced, the spare UAV should not simply be launched and sent directly into the mission.

The essential configuration must be checked again : flight limits, RTH settings and location, battery condition, lost-link behaviour and any other parameters required for the operation. After take-off, the same low-level functional checks and RTH environment assessment should be performed before the spare aircraft is committed to the operational area.

But having a spare does not mean that the mission must continue at all costs. If the first aircraft experiences an anomaly that may originate from the operating environment rather than from the aircraft itself - for example, significant navigation degradation or several abnormal sensor behaviours occurring together - the situation should first be understood before exposing another aircraft to the same conditions.

Redundancy helps manage a failure. It should never be used to ignore a hazard that has not been understood.

Preparing an operation, not simply a drone

At this stage, the difference between preparing an aircraft and preparing a UAV operation becomes clear.

The crew needs the right aircraft, sufficient energy reserves, appropriate communications, clearly understood emergency procedures and, whenever possible, a viable backup solution.

The aircraft must then demonstrate that it can perform not only the flight itself, but also the operational function for which it was selected. Only then is the system truly ready to begin the mission.

The objective is not simply to have an aircraft capable of flying. The objective is to have an aircraft, a crew and a contingency plan capable of completing the mission safely.

4 - The Final GO/NO-GO Decision

The final decision belongs to the Remote Pilot

A UAV mission may be urgent, high-priority or particularly important to the requesting authority. However, the importance of a mission does not necessarily mean that all the conditions required for an immediate take-off have been met.

In my operational environment, the operational commander defines the mission and its objectives. However, as the Remote Pilot, I am responsible for deciding when the aircraft can safely take off, based on the actual operating conditions and the applicable regulatory framework.

This distinction is essential. An operational commander may urgently need aerial imagery. They may also be under significant pressure as an event develops. But operational urgency does not eliminate aviation risks.

If the necessary conditions are not met, I prefer to explain why additional time is required rather than rush into a take-off. Sometimes, waiting just a few minutes is enough.

An urgent mission does not justify a rushed take-off. The objective is not to challenge the requesting authority, but to provide the required aerial capability while maintaining an acceptable level of safety.

The final checks before take-off

Cartographic assessments, technical inspections and airspace coordination conducted during mission preparation provide an essential foundation. However, they do not replace a final assessment at the operating site.

In the final minutes before take-off, when the operation requires coordination with Air Traffic Control (ATC) or another relevant airspace authority, I contact the appropriate service. This communication allows me to confirm the applicable flight conditions, including authorised flight altitude, potential restrictions, surrounding air traffic activity and any relevant instructions. The service may also request a contact telephone number to ensure rapid communication if necessary.

I then perform a final assessment of the surrounding environment. On the ground, I check for people who could enter the operating area. In the air, I look for any aviation activity that could create a conflict with the UAV operation.

Weather conditions are also reassessed. Direct observation can reveal reduced visibility, precipitation, changing wind conditions or signs of strong gusts. However, these observations must be considered alongside relevant weather information, particularly when conditions are unstable.

Where relevant to the aircraft and mission, I may also review geomagnetic activity indicators. The Kp index offers context on geomagnetic conditions but is not a direct measurement of GNSS reliability.

Finally, I confirm the responsibilities of the Aerial Observer. The observer must understand the mission, their role in monitoring the surrounding airspace, the communication procedures and the actions required in an emergency.

Only after these final checks do I confirm the operational objective and make my decision: GO or NO-GO.

When conditions do not allow the mission to proceed

Sometimes, the conditions encountered at the operating site differ from those anticipated during preparation. Strong wind gusts, heavy precipitation or insufficient visibility may make the mission impossible with the aircraft initially selected.

In such situations, I explain to the requesting authority why the flight cannot safely proceed. This explanation is important. An operational commander may not necessarily understand the technical limitations of a UAV. They may not know that some aircraft are not designed to operate in heavy rain, or that strong gusts exceeding the manufacturer’s operating limits can compromise flight performance and safety.

Part of the Remote Pilot’s responsibility is to make these limitations understandable. Rather than simply announcing that the mission cannot be conducted, I try to identify an appropriate alternative.

If another available aircraft has the required capabilities, it may be considered after confirming its suitability for the mission and the applicable operating conditions. Otherwise I prefer to recommend postponing the mission for a few hours or even until the following day.

It is better to postpone a mission than to cause an accident by trying to complete it at all costs.

A NO-GO decision is not necessarily an operational failure. It may be the decision that protects people, equipment and the possibility of completing the mission later under safer conditions.

Operational pressure must not override safety limits

During professional UAV operations, the Remote Pilot may work under the authority of an operational commander who is not necessarily an aviation specialist.

The responsibilities of each person must therefore be clearly understood. The requesting authority understands the operational objective and the expected results. The Remote Pilot provides aviation expertise, assesses the flight conditions and determines whether the operation can be conducted within the applicable regulatory and safety framework.

These responsibilities complement each other, but they are not interchangeable.

When a disagreement occurs, my first approach is to explain the identified risks, the aircraft’s limitations and the conditions required to conduct the flight safely. The objective is to find a solution, not to create a conflict within the operational organisation.

However, if the conditions remain incompatible with safe flight, I maintain my decision not to take off.

Operational pressure must never lead a Remote Pilot to accept a risk they consider unacceptable. A dangerous decision does not become acceptable simply because a senior authority agrees to assume responsibility for its consequences.

Individual responsibilities must remain consistent with the applicable legal and regulatory framework. A written waiver cannot replace the necessary authorisations, risk assessments or safety obligations.

A GO decision can become a NO-GO

A decision to take off does not guarantee that conditions will remain acceptable throughout the mission. The operating environment is constantly evolving.

Weather conditions may deteriorate, unexpected aviation activity may appear, or the aircraft may develop a technical issue.

I have personally encountered situations where a warning appeared on the remote controller during flight, instructing me to land the aircraft immediately.

In such circumstances, I do not attempt to complete the ongoing observation at all costs. I apply the appropriate procedure, recover the aircraft when it is safe to do so and land it.

Once on the ground, I investigate the issue to understand its cause and determine whether the operation can safely resume. If no satisfactory solution can be found, I inform the requesting authority that the mission cannot continue with that aircraft.

The same reasoning applies when weather conditions deteriorate suddenly or when a new operational request requires the aircraft to operate outside the previously assessed and authorised area.

A new mission cannot automatically be accepted simply because the UAV is already airborne. The applicable safety conditions, airspace constraints and necessary authorisations must first be reassessed.

Having a second aircraft available may allow the operation to resume following a failure of the primary UAV. However, a spare aircraft does not justify continuing operations in an environment that has become unsafe.

A GO decision authorises the beginning of an operation. It is not an obligation to continue flying regardless of the circumstances.

Experience does not eliminate the risk of error

With experience, some decisions become faster. Remote Pilots become more familiar with their aircraft, identify operational constraints more easily and anticipate potential difficulties more effectively.

However, experience can also introduce its own risks. The first is overconfidence. An experienced Remote Pilot may be tempted to fly despite unfavourable weather conditions, believing that their piloting skills will allow them to manage the situation.

But knowing how to fly an aircraft does not mean being able to exceed its technical limitations.

The second risk is routine. When missions become repetitive, some checks may gradually be overlooked: aircraft condition, battery status, flight parameters or the latest weather information.

A procedure repeated hundreds of times may become almost automatic. But it is precisely when checks become familiar that we must ensure they are never treated as optional.

Finally, a lack of experience can create the opposite reaction : fear. A less experienced Remote Pilot facing a lost command-and-control link, an interrupted video feed or another degraded situation may become overwhelmed, particularly when the scenario was only briefly covered during training.

This highlights the importance of recurrent training, familiar emergency procedures and preparation for abnormal situations.

Experience should improve decision-making, not replace safety checks.

GO/NO-GO : a decision that must be continuously reassessed

UAV mission preparation allows the crew to understand the operational objective, assess the environment, select suitable equipment and organise the flight team.

The GO/NO-GO decision brings all these elements together to determine whether the operation can safely begin.

But that decision does not end at take-off. It must be reassessed whenever the mission evolves, the environment changes or an anomaly occurs.

The Remote Pilot must be able to take off when the necessary conditions are met, wait when an improvement is possible and interrupt the operation when safety requires it.

A GO decision is never a commitment to continue flying at all costs.

The true responsibility of a Remote Pilot is not only knowing when to take off, but also knowing when to wait, return or stand down.

Conclusion - Mission Preparation Is a Continuous Commitment to Safety

The success of a UAV mission does not begin at take-off.

It begins much earlier, when the Remote Pilot takes the time to understand the operational objective, assess the operating environment, and prepare the aircraft, crew and necessary contingency procedures.

Each stage of preparation serves the same purpose: to ensure that the mission can be conducted effectively while maintaining an acceptable level of safety.

However, thorough preparation does not mean that every risk has been eliminated. Operating conditions may change, operational priorities may evolve, and technical failures can occur without warning.

This is why mission preparation should never be considered a process that ends once the aircraft takes off. It provides the foundation for decisions that must be continuously reassessed throughout the operation.

A professional Remote Pilot must be able to adapt, communicate decisions clearly and, when necessary, interrupt or cancel a mission.

Experience, technical skills and reliable equipment are essential. But none of these can replace situational awareness, sound judgement and respect for operational limitations.

A good Remote Pilot is not someone who takes off in every situation. It is someone who knows when the conditions allow a safe flight.

Sometimes the best operational decision is to wait, return or stand down.

Because the success of a UAV mission is not measured solely by the results achieved, but also by how those results were achieved.

So, GO or NO-GO?

Picture of Robert Danger
Robert Danger

Related Posts

Key Takeaways

Rate this article

0/5 (0)

Share:
Close
Drone by Nature
rotate_right