EVLOS in Practice: Visual Observer Roles, CRM Callouts, and Abort Criteria That Actually Work

EVLOS fails when comms fail.

Not because the pilot can't fly. Not because the aircraft isn't capable. EVLOS breaks down when the team doesn't share the same picture of what "safe" looks like in real time, and when the Visual Observer and pilot don't have a disciplined way to communicate what they're seeing.

If you want EVLOS to work, treat it like aviation. Roles are defined. Callouts are standardized. Decision triggers are agreed to before takeoff. The debrief loop closes the gap for the next flight.

First, the rule that catches people off guard: your Visual Observer must be certified

Transport Canada's Advanced Operations guidance is explicit. For EVLOS, the visual observer must have at least a Basic drone pilot certificate.

Advanced operations — Transport Canada

That matters for two reasons.

First, it's compliance. If your VO doesn't meet the minimum requirement, you are building risk into the operation before you even launch.

Second, it's competence. EVLOS depends on the observer's ability to recognize conflicts and hazards early enough for the pilot to act. That requires more than "good eyesight." It requires shared airspace literacy and standardized communication.

EVLOS basics in one sentence

EVLOS is flying a small drone beyond the pilot's visual line of sight while a trained, certified visual observer maintains the visual scan needed to help detect and avoid conflicts.

And regardless of how you structure it, the legal foundation is simple: if you are using visual observers to assist with detect and avoid, you must maintain reliable and timely communication between the pilot and each visual observer.

CARs section 901.20

That is the spine of EVLOS professionalism.

1) VO positioning: the geometry matters

A Visual Observer is not just "somewhere nearby." A good EVLOS setup starts with intentional geometry.

Position the VO where they can:

• see the portion of airspace where a conflict is most likely to appear
• maintain an unobstructed scan of the relevant sector
• communicate without delay or interference
• remain stationary and focused, not moving with distractions

Bad positioning looks like:

• VO standing behind the pilot with a blocked view
• VO inside a noisy crowd where comms are unreliable
• VO too far away to communicate promptly
• VO watching the drone but not the surrounding airspace

If the VO is watching only the aircraft, you are missing the point. EVLOS is about seeing the environment early enough to keep separation.

2) CRM callouts: the simple set that prevents most problems

In aviation, good CRM isn't fancy. It's consistent.

EVLOS teams do best with a small callout set everyone uses the same way, every time. The goal is speed and clarity, not conversation. Here is a practical core set:

Traffic callouts

• "Traffic, 2 o'clock, low, moving left to right."
• "Traffic, 12 o'clock, high, closing."
• "Traffic lost, last seen 3 o'clock, medium, moving away."

Hazard callouts

• "Birds, 11 o'clock, level, approaching."
• "People approaching boundary, south side."
• "Vehicle entering zone, west access."

Control callouts

• "Pause."
• "Abort."
• "Resume."

If your team is improvising language in the moment, you will lose time. Time is safety margin.

3) Pause vs abort: two different tools

This distinction is one of the easiest ways to raise your EVLOS professionalism.

Pause

A pause is a controlled stop in the operation to regain situational awareness and re-establish safe conditions. Use "pause" when:

• you have uncertainty
• you need a few seconds to re-check airspace or boundary control
• the hazard is developing but not yet critical
• comms quality degrades and you need to reset

A good pause has an immediate action tied to it. Hold position or return to a known safe point, then reassess.

Abort

An abort is a decision to terminate the planned profile because safety margins are no longer acceptable. Use "abort" when:

• you have a confirmed conflict trend you cannot resolve quickly
• a person or vehicle has breached the boundary in a way you cannot control
• comms are no longer reliable
• you have lost the ability to maintain your required separation
• the VO cannot continue effective scanning

The key is that "abort" is not emotional. It's pre-decided.

4) Decision triggers: write them down before the flight

EVLOS should never rely on "we'll figure it out." Create a short trigger list and brief it before launch. Keep it measurable.

Examples of solid EVLOS triggers:

• If comms drop for more than a defined time, pause immediately; if not restored by a second threshold, abort.
• If traffic is observed on a converging path and cannot be clearly deconflicted, abort.
• If any non-participant enters the sterile area, pause; if they cannot be controlled or redirected, abort.
• If wind or gusts exceed your pre-set limit, pause and reassess; if sustained, abort.

This is aviation thinking applied to RPAS. It prevents hesitation and reduces risk under pressure.

5) The debrief loop: how EVLOS teams get better fast

Most operators skip debriefing because they're busy. That is a mistake. A five-minute structured debrief improves EVLOS faster than another hour of random practice.

Debrief these four items:

1. What did the VO see first, and how early?
2. Were callouts short and unambiguous?
3. Did the pilot respond in a predictable way?
4. What should change next time — positioning, trigger thresholds, comms equipment, roles?

Then update your SOP and your briefing card. That is how you build a real operator system.

What to document on EVLOS flights

Documentation is not about bureaucracy. It's about repeatability and defensibility. At minimum, capture:

• names of pilot and VO, and VO certificate level (Basic or higher)
• comms method used and any comms interruptions
• VO position and sector responsibility
• planned triggers and whether any were activated
• any pauses or aborts and what caused them
• lessons learned and SOP updates

This turns EVLOS from a one-off skill into a professional capability.

Next step: get the VO brief card and EVLOS SOP package

If you want a ready-to-use set of standardized callouts, role assignments, and pause/abort triggers, download the "VO Brief + CRM Callouts Card" and the EVLOS SOP package from 4DUAV.

4DUAV Stan Store