Operating instructions for Quickdraw: sign-in, incident position entry, Job settings, the Candidate Sites a Job returns, the map tools, and the exchange of Fields and recces with HeliGuardian. Screens and control locations are shown for the device selected below. A phone and an iPad use the Touch layout; a laptop uses the Console layout (chapter 16).
These terms have the meanings below throughout this manual. Values in brackets are Quickdraw's defaults; where a Run setting changes one, the chapter states it.
| Term | Meaning |
|---|---|
| Job | One analysis of one incident position, with the radius, clearance mode, D, limits, map source and Callsign as submitted. It runs on the server and ends complete or failed. |
| Callsign | The aircraft unit identifier (e.g. HME56). With a HeliGuardian sign-in it is chosen from the organisation's aircraft in HeliGuardian; without one it is typed (1 to 16 letters, digits or hyphens). The Callsign and the EFB Folder together identify the EFB file and the Last job. |
| EFB Folder | Where a Job's EFB files are written, and whose Polygons the Job applies. With a HeliGuardian sign-in: the organisation's folder, shared by its members. Without one: the user's own folder, shown as PERSONAL. Decided when the Job is submitted; the same Callsign in two folders is two separate EFB files. |
| Candidate Site | A landing site proposed by a Job, shown as Site 1, Site 2 … in rank order. Each is the best cell of a connected area of ground on which the Landing Zone fits clear of obstacles, within Max slope, with at least Min area of clear ground. Candidate Sites are at least 150 m apart. A Job returns up to 5. |
| D | The aircraft's reference dimension in metres (13.65 m). It sizes the Landing Zone. |
| Landing Zone | The clearance a Job requires at a Candidate Site. Day mode: a circle of diameter 2D. Night mode: a box 2D × 4D, at any orientation. |
| Surface object | Anything the LIDAR survey records above the ground: the first-return surface model (DSM) minus the ground model (DTM). Surface objects over 2 m inside the Landing Zone exclude it. Measure reports those of 1 m or more. |
| Walk time | Time on foot between a Candidate Site and the patient, along the route the Job computed over its ground model. Shown as minutes:seconds. |
| RV (Rendezvous Point) | Where a vehicle meets the crew: the nearest point, on foot, on a road a car can stop on. Nominated for a Candidate Site whose walking route to the patient is longer than 500 m. |
| Patient road | The point on a road a car can stop on that is nearest the patient on foot. The vehicle's drive ends there. |
| Vehicle option | Walk to the RV, drive to the Patient road, walk to the patient. Shown with the Walk time where an RV is nominated, unless it is no quicker. |
| Closed Site | A school, college, utility compound, allotment, play area or sports ground whose gates are treated as locked. Walking routes enter only at a notified access point or along a Public Right of Way. |
| Locked Candidate Site | A Candidate Site inside a Closed Site that no notified access point reaches. Its route starts at the site's main entrance, with a key-holder. |
| Field | A landing site held in HeliGuardian for your organisation, as one point, with a status and recces. |
| Known Field | A Field inside a Job's search radius. A Job run with a HeliGuardian sign-in assesses every Known Field (chapter 06). |
| Recce | An assessment of a Field held in HeliGuardian: score 0 to 5, size, shape, surface, slope, surrounds, access, downwash and notes. |
| Polygon | An area drawn in an EFB Folder, with a rule (No Access, No Landing or Rule In) and optional active hours. Every Job in that EFB Folder applies it. |
| Point Reading | The Job's assessment applied at a point selected on its map (chapter 09). |
| Crew's Point | A Point Reading sent to the Job's KMZ and EFB file with Send to EFB, titled with its Walk time. One per Job (chapter 09). |
| Reason chip | One coded finding in a Point Reading: a label in capitals (e.g. SLOPE) and a sentence with the measured value (chapter 09). |
| Heading | A direction written as text (wind, Sun, Moon, a bearing between two places, a slope's facing, a rectangle's long side): degrees magnetic, °M, from the World Magnetic Model 2025 at the place on the Job's date. On the map, barbs and symbols are drawn on true north. Where the model gives no variation (outside 2025 to 2030) the heading is true and written °T. |
| Data source | One input a Job reads (LIDAR, map features, power lines, weather …) with its status: worked, fell back, failed or skipped. A failed Data source does not fail the Job; it is stated. |
Complete once at the start of each shift, before tasking.
Ready shows whether the page can accept a task. While it is displayed, Quickdraw checks the server every 30 seconds and on each return to the page, and checks the sign-in.
| Status line | Condition | Action |
|---|---|---|
| Ready for a task | All conditions met. | None. |
| Ready, without a callsign: the sites will not go to the EFB. | Callsign empty. | Enter the Callsign. |
| Not a callsign: letters, digits and hyphens, 1 to 16. | Callsign invalid. | Correct it. |
| Not ready: the server is not answering. A Job sent now would fail. | Last server check failed. The Server line gives the time (Z) since when. | Check signal. The page retries every 30 s. |
| Not ready: the sign-in has expired. | No sign-in time left. | Settings › Sign Out of Quickdraw, then sign in. |
A line under the Callsign states a problem with it:
| Line under the Callsign | Condition | Action |
|---|---|---|
| Choose your aircraft. Without one, a Job's sites go to no EFB. | Signed in to HeliGuardian, no Callsign chosen. A saved or typed Callsign that is not one of the organisation's aircraft is cleared. | Choose the aircraft. |
| [Reason] Enter a callsign for your own EFB folder, or sign in to HeliGuardian again in Settings. | The HeliGuardian sign-in ended; the Callsign was cleared and the EFB Folder is PERSONAL. | Sign in to HeliGuardian again, or type a Callsign for PERSONAL. |
| [Organisation]'s aircraft could not be read: … | HeliGuardian did not return the aircraft list. The EFB Folder stays the organisation's. | Retry later. Until the list is read no Callsign can be chosen, and a Job's sites go to no EFB. |
| HeliGuardian lists no aircraft with a callsign for [organisation]. | The organisation's aircraft have no callsign in HeliGuardian. | Add the callsign in HeliGuardian. |
New Task opens a full-screen keypad.New Task opens a keypad in the panel; a selection on the map beside it sets the position.New Task (on Ready, or in the rail) opens the entry in the panel; the position is typed on the keyboard or selected on the map. The position is entered as an OS grid reference, or as latitude and longitude in one of three formats. All conversions are made on the server with OS's OSTN15 transformation.
USE MY POSITION enters the device position (location permission is requested once). A grid reference or a decimal latitude, longitude pasted on the page is entered. While the entry is open, a map selection sets the incident position.
FMT cycles the formats. A complete position is converted to the new format; an incomplete one is cleared, and the hint states it.
| Key | Function |
|---|---|
| DEL | Deletes the last character. |
| CLEAR | Clears the entry (lat/long: both fields). |
| ENTER | Lat/long: latitude to longitude. On a complete position: as ANALYSE. A keyboard Enter key is equivalent. |
| SET | Places the position on the map and closes the entry without submitting a Job. New Task reopens it with the position filled in. |
| ANALYSE | Submits the Job. Disabled until the position is complete. While a Job is running it reads REPLACE JOB. Every Job submitted stops any earlier Job for the same Callsign and EFB Folder still running, from any device: it is recorded as failed (Replaced by Job …) and only the new Job is written to the EFB. Jobs in another EFB Folder, and Jobs submitted later, are not affected. If the new Job is refused, the running Job continues. |
| CANCEL | Closes the entry with no change. |
A grid reference or decimal latitude, longitude pasted on the page is entered. A click on the map sets the position.
Changing format converts a complete position; an incomplete one is cleared, and the hint states it.
| Key or button | Function |
|---|---|
| Backspace | Deletes the last character. |
| Enter | Lat/long: latitude to longitude. On a complete position: as ANALYSE. |
| Tab | Moves between the latitude and longitude fields. |
| SET | Places the position on the map and closes the entry without submitting a Job. |
| ANALYSE | Submits the Job; disabled until the position is complete. While a Job is running it reads REPLACE JOB. Every Job submitted stops any earlier Job for the same Callsign and EFB Folder still running, from any device: it is recorded as failed (Replaced by Job …) and only the new Job is written to the EFB. Jobs in another EFB Folder, and Jobs submitted later, are not affected. If the new Job is refused, the running Job continues. |
| CANCEL | Closes the entry with no change. |
The Run settings row on the entry screen summarises the values the next Job uses, e.g. 1500 m · D 13.65 m day · 7° · 100 m² · lines 20 m · OS. Selecting it opens the page; ‹ Position returns. The same page is at Settings › Task defaults.The Run settings are listed below the position in the entry panel; the line above them summarises what the next Job uses.
Limits a Candidate Site must meet: Max slope (7°; at most 20°), Min area of clear ground (100 m²), and the Power-line buffer (20 m either side of wires inferred between mapped pylons; 0 disables it). Distribution-network (DNO) conductors are buffered separately by voltage band; this value does not affect them.
The incident is shown on the map as a magenta diamond. The Job runs on the server; the device may be locked or the page closed. A page reopened within 30 minutes reopens the Job; after that, open it from Last job.
If the Job completes while a Known Field screen is open, the screen changes to the Candidate Site the Field became, or to the Field's outcome if it was not offered.
On completion the panel lists the Candidate Sites in rank order and the map shows each with its walking route to the patient. Ranking weights Walk time most heavily.
The heading gives the count and the sources used, e.g. 6 sites · 1 locked · 1 known field added · OS + LIDAR survey.
The Job assigns each Known Field one outcome:
| Outcome | Condition | Result |
|---|---|---|
| Landable | Quickdraw's own checks find a Landing Zone within 75 m of the Field's HeliGuardian position. | The best cell there is a Candidate Site. |
| Offered on its recce's word | Quickdraw's checks fail within 75 m, but the Field has a recce and its HeliGuardian status is Active. | A Candidate Site at the HeliGuardian position, amber, with each failed check listed as Against it. |
| Not offered | Neither of the above (never recced, or not Active), or the ground is a land use Quickdraw excludes. | Listed with the reason; not a Candidate Site. |
An offered Known Field within 150 m of a listed Candidate Site is not listed separately; that Candidate Site's screen names it (chapter 07).
Best first: the Job's rank. Nearest first: the same Candidate Sites by Walk time; a Locked Candidate Site by its time from the main entrance; a Candidate Site with no computed walking route last.
| Caution | Condition | Effect |
|---|---|---|
| Crop and grass state not checked | The satellite vegetation index (NDVI) was not read. | Crop height and long grass are not assessed at any Candidate Site. |
| Final approach required | The patient is inside or behind a barrier (e.g. a building). Walking routes end at its way in. | The remaining distance and the barrier are stated; no time is given for that distance. |
| Patient believed unreachable on foot | No walking route from any Candidate Site reaches the patient (e.g. open water, slope beyond the carry limit). | Walk times end where the routes end. |
| No map data covers this area | The map source returned no features. | Roads, water, buildings and boundaries were not applied: every Candidate Site is unchecked against them. |
| Map features unavailable | The map source failed. | As above. |
| [Data source]: not read / fell back | One Data source failed or used its fallback. | The line beneath states the consequence; detail in Job details. |
| Known fields not checked | No HeliGuardian sign-in, or the HeliGuardian read failed. | The Job has no Known Fields. |
The page and the EFB file use the same symbols. A Candidate Site is green when its land use is suitable; amber when its land use is conditional (made surfaces such as car parks, school grounds, playgrounds, retail, industrial and utility sites) or when it is a Known Field offered on its recce's word; a grey square when locked.
Opened from a row or from the site's map symbol. The map centres on the Candidate Site.
Lower on the screen:
All three require a HeliGuardian sign-in; without one they are disabled and the reason is stated beneath. Procedures: chapter 13.
The way to the patient starts with the distance inside the site to the main entrance (declared, with the key-holder; no time), then the walk from the main entrance. Exclude locked sites on the list replaces Locked Candidate Sites with the next unlocked ones.
The panel is a sheet below the map with three heights: title bar only, half, full.Held sideways, the panel is beside the map at full height. Held upright, the iPad behaves as a phone: the panel is a sheet below the map with three heights (title bar only, half, full) and a grabber.The panel is beside the map at full height; the map takes the rest of the window.
| Map selection | Result |
|---|---|
| Candidate Site symbol | Opens the Candidate Site screen. |
| Route, RV or Patient road | A label. |
| Known Field hexagon | The Field's outcome and recces. |
| Any other point inside the radius, with a finished Job displayed | A Point Reading (chapter 09). |
| Any point, with the entry open or on Ready | Sets the incident position. |
Each Candidate Site carries a wind barb; the shaft points into the wind, drawn on true north (the text gives it °M). Half barb 5 kt; full barb 10 kt; pennant 50 kt. The Sun and Moon symbols sit beyond the barb on their bearing, drawn on true north, labelled with elevation; a faded symbol is below the horizon. Both are switched in Layers.
A Point Reading applies the Job's assessment at a point selected on the map: whether the Landing Zone fits there, the Walk time to the patient, and the Vehicle option. It uses the ground model the Job built, so its results agree with the Job's Candidate Sites. Screens in this chapter are from a recorded Job near Lincoln.
Point Readings are available while a finished Job is displayed and its ground model is held on the server. The server holds it while any page displays the Job and deletes it 30 minutes after the last such page closes; a selection after that states that the ground was cleared, and the Job must be run again. On Ready, or with the entry open, a map selection sets the incident position instead.
Titled Your point, it takes the place of the Candidate Site screen. The Landing Zone and the walking route are drawn in white.
Then: Vehicle option (With a vehicle); slope; surface objects; ground height; clear ground area (stated as at least when it extends beyond 250 m); the way to the patient; and what a Point Reading does not compute that a Candidate Site has (e.g. score, or a route from a Closed Site's main entrance). Selecting the other clearance mode recomputes the reading in that mode. ‹ Sites, or opening a Candidate Site, discards it unless it is the Crew's Point.
Send to EFB, at the foot of the screen (Add to the KMZ when the Job has no EFB file), makes the point the Job's Crew's Point, replacing any sent before. Quickdraw reads the point again in the displayed mode and rewrites the EFB file with the switches as last set; the line under the button states the outcome. On the map and in the file it is drawn in white: its Landing Zone (dashed in the file when it does not fit), its walking route, its Vehicle option where there is one (the walks to and from the road, the drive, an RV without a number and the Patient road), and a mark titled with the Walk time. The title never gives the Vehicle option's time.
| Condition | Title in ACANS |
|---|---|
| A walking route reaches the patient | HME56 | Walk 4:37 |
| …and the Landing Zone does not fit | HME56 | Walk 4:37 | NO LZ |
| No walking route (NO ACCESS), or only a straight-line estimate | HME56 | No walk |
| Outside the search radius | HME56 | Outside radius |
The map shows the same title under the mark. The Crew's Point stays until Take Off the EFB on its screen, another point is sent, or another Job is run; selecting its mark opens its screen. Selecting the other clearance mode sends it again in that mode.
A reason chip records one finding of the Point Reading, as a label and a sentence giving the measured value and the limit. The reading shows one chip per finding. The outline colour gives the finding's effect:
| Outline | Effect |
|---|---|
| Red | A reason the Landing Zone does not fit at this point, or that no walking route reaches the patient. A Job could not place a Candidate Site here. |
| Amber | The Landing Zone fits. The finding is a caution a Candidate Site here would carry. |
| Grey | Information on the Vehicle option, or on a Candidate Site with a shorter Walk time. No effect on the Landing Zone. |
Where the Landing Zone fits, only SLOPE, OBSTRUCTIONS and ROAD can appear among the Landing Zone chips, in amber, at the thresholds a Candidate Site's cautions use.
| Chip | Raised when | Outline |
|---|---|---|
| SLOPE | Red: LIDAR slope in the Landing Zone exceeds Max slope (7°). Amber: the zone fits and its maximum slope exceeds 5°. | Red / amber |
| OBSTRUCTIONS | Red: surface objects in the Landing Zone exceed 2 m (trees, buildings, vehicles). Amber: the zone fits and its tallest surface object exceeds 0.5 m. | Red / amber |
| ROAD | The Landing Zone is on a road carriageway: landing requires a police road closure. | Red / amber |
| NO SURVEY | Part of the Landing Zone has no LIDAR survey; slope and surface objects there are unknown. | Red |
| POWER LINE | The Landing Zone is inside a power-line buffer: a DNO conductor's (by voltage band), or the Power-line buffer around wires inferred between mapped pylons. | Red |
| WATER | Mapped water or tidal ground in the Landing Zone. | Red |
| YOUR POLYGON | Inside an active No Access or No Landing Polygon of the Job's Callsign. | Red |
| EXCLUSION ZONE | Inside a mapped excluded land use (e.g. solar farm, substation, cemetery) or a wire inferred between mapped pylons. | Red |
| TOO LITTLE ROOM | The Landing Zone does not fit clear of obstacles at any orientation. | Red |
| PAST THE RADIUS | The Landing Zone extends beyond the search radius, where the Job assessed nothing. | Red |
| SMALL CLEARING | The Landing Zone fits, but the connected clear ground is smaller than Min area (100 m²). The sentence gives both areas. | Red |
| NO ACCESS | No walking route from the point reaches the patient on the Job's ground model. | Red |
| LOCKED | Inside a Closed Site that no notified access point reaches. The walk shown ignores the locked boundary; a Candidate Site here would be walked from the main entrance. | Amber |
| NO VEHICLE ROUTE AVAILABLE | No walking route reaches a road a car can stop on, from the point or from the patient; or the route to the road starts behind a locked gate. | Grey |
| NO VEHICLE ROUTE REQUIRED | The walking route is 500 m or shorter. A Vehicle option is computed only beyond 500 m. | Grey |
| WALKING IS QUICKER | The Walk time is no longer than the Vehicle option's total. The sentence gives both. | Grey |
| VEHICLE NOT WORKED OUT | The drive was not computed: no road router on this server, or the data needed was not kept for this Job. | Grey |
| CLOSER FOOT ROUTE AVAILABLE | An offered Candidate Site has a shorter Walk time. The sentence names it and gives both times. | Grey |
Measure computes, for an area drawn on the map: the largest rectangle inside it at any orientation; the LIDAR surface objects of 1 m or more inside it; the overhead wires reaching it; and the largest rectangle clear of both. A Job is not required.
Below: the drawn area (m²), then each LIDAR obstruction, tallest first, with height (rounded up) and plan area. Selecting an obstruction centres the map on it.
Then each overhead wire whose kept-clear ground reaches the area, read as a Job reads them: a DNO line, kept clear by your Power-line Buffer standoff for its voltage band; a DNO pole or tower, by its 5 m footprint; and a wire inferred between two pylons of the map data selected under Run settings (OS or OpenStreetMap), by the Power-line buffer under Run settings. On the map, each wire is purple and the ground kept clear of it dashed; red where it reaches the largest rectangle while that is shown.
Opened from the map's Layers controlLayers in the rail, or from the foot of the list. ‹ Sites returns.
Below: Wind and sky at the sites (on/off, with the forecast model and run time) and Where OS map data covers.
Crossings (ways through a boundary) are graded by evidence: Best (a mapped gate, entrance or named crossing); Good (a road passes through); Probable (a path passes through); Possible (a path ends at a boundary that names no obstruction). A grey row: none found, or the map source does not distinguish the class. When the Job used the LIDAR survey trial, a final section lists what the survey added.
Both are at the foot of the Candidate Site list.
Open 3D view opens the Job in a separate tab; the Job tab is unchanged. It shows the terrain around the incident with the Candidate Sites, routes, RVs and Landing Zones in the displayed mode and order.
The 3D data is held while any page displays the Job and deleted 30 minutes after the last such page closes; the button then states that it is unavailable.
Quickdraw reads your organisation's Fields from HeliGuardian and writes new Fields and recces to it. Every function requires a HeliGuardian sign-in (Settings › HeliGuardian). Nothing is written to HeliGuardian until a create or send control is selected.
Nearby fields on a Candidate Site lists the Fields within 1 km of its centre, nearest first, and draws them on the map.
Position: the Candidate Site's centre, as a 10-figure grid reference (computed on the server) and latitude, longitude; not editable. Visibility: Private (your organisation only).
Records the actual landing position for a recce. Opened from the Candidate Site used.
Header: Field name, its last recce date, this recce's date.
What you saw: shape, surface, slope, surrounds, access, downwash; free text.
The recce is held on the device from the first character entered until HeliGuardian confirms receipt. Leaving the screen does not discard it.
On the laptop, a recce opened from Landed is shown below the Field list on the same screen.
A recce whose send fails (no connection, HeliGuardian not answering, session ended) is held in Recces not sent, opened from Ready.
Opened from the gear on the mapthe gear at the foot of the rail. Done returns to the previous screen.
Polygons belong to an EFB Folder. The organisation's Polygons are edited by any member signed in for it and applied to every Job of its aircraft; PERSONAL Polygons apply to the user's own Jobs. Every Job applies every Polygon of its EFB Folder during its active hours, in whatever Polygon folder. Polygon folders organise the list only. Polygons held per Callsign before 17 November 2026 were deleted.
Active hours: per day, on/off with start and end, UK local time. All days off: always active. An end earlier than the start runs past midnight. Delete Polygon is at the foot; Cancel and Save are in the bar, with Save and Cancel. The shape cannot be edited: delete and redraw.
The page follows the device's Light or Dark appearance setting.
Settings › Display & Brightness › Dark. Screen brightness is set separately.
The Console layout uses its dark colour scheme in both appearance settings; the Touch screens follow the setting.
For a night task, set Night · 2D × 4D box and D in Run settings before submitting. For a Job already run in day mode, Night · 2D × 4D on the list displays the night result.
Quickdraw has two layouts. Touch is used on a phone and an iPad; Console is used with a mouse or trackpad. Settings › Layout › Automatic selects by the device's main pointer; Touch or Console overrides it on that device. Every function in this manual is in both layouts; only control locations differ.
| Device | Layout | Panel | Controls |
|---|---|---|---|
| Phone | Touch | Sheet below the map: title bar, half or full height, moved by the grabber. | Map buttons: Settings, Layers, Show all sites, Measure. |
| iPad, upright | Touch | As phone. | As phone. |
| iPad, sideways | Touch | Beside the map, full height. | As phone. |
| Laptop | Console | Beside the map, full height, dense. | Top bar (Map, Polygons, Measure, Recces not sent; Callsign, server, EFB file time, sign-in time) and rail (Ready, New Task, the Job, Layers; Settings). |
Quickdraw states every missing input, failed Data source and limit applied.
| Indication | Cause | Action |
|---|---|---|
| Page closed or device locked during a Job | None; the Job continues on the server. | Reopen within 30 minutes to resume; after that, Last job on Ready. |
| Login screen during a Job | Quickdraw sign-in expired. | Sign in; open the Job from Last job. |
| Not ready: the server is not answering | No server response. | Check signal. Retried every 30 s. A Job submitted now fails. |
| Pick a grid square first | Digits entered before the 100 km square. | Select a square, or OTHER and its letters. |
| Tap N or S first / Tap E or W first | Lat/long digits before the hemisphere. | Enter the hemisphere. |
| That field is full: DEL or CLEAR to change it | All digits entered. | DEL or CLEAR. |
| That reference is outside the OS grid | Square or digits invalid. | Check the reference. |
| Format changed; the unfinished entry was cleared | Format changed on an incomplete position. | Re-enter. |
| Job failed: killed by SIGKILL, most likely out of memory | Server memory exceeded. | Run again with a smaller search radius. |
| Walk time shown as – | No walking route computed from that Candidate Site. | Read its way to the patient. |
| Day or Night selector disabled | The other clearance mode could not be computed; the reason is stated beneath. | Run a Job in that mode. |
| Point Reading: ground cleared | No page displayed the Job for 30 minutes. | Run the Job again. |
| This Job has no 3D view. | 3D data unavailable for this Job. | None; Candidate Sites are unaffected. |
| Measure: no unobstructed rectangle | LIDAR check not run (no survey, or area over 1 km on a side), or no ground clear of both LIDAR obstructions and overhead wires. | Read the stated reason; reduce an area over 1 km. |
| Measure: … The rectangle keeps clear only of the wires listed. | An overhead-wire source could not be read, or DNO lines are not held for the area (e.g. outside a licence area in the data). | Treat wires as unchecked there; look for wires and poles before landing. |
| Measure: Overhead wires Not checked for this measurement | The result was measured before overhead wires were checked. | Draw the area again. |
| Measure: On this map only: there is no finished Job on screen to add it to. | No finished Job is displayed. | Display the Job; the result is added to it. |
| Measure: On this map only: it could not be added to the Job (…) | The server refused or did not answer. | Change Largest / Unobstructed or the units to send it again, or draw the area again. |
| Measure: The EFB copy was not changed: Job … has published to … since this one. | A newer Job holds the Callsign's EFB file. | Display the newer Job; the result is added to it. |
| Known fields not checked | No HeliGuardian sign-in, or the read failed. | Sign in to HeliGuardian; run the Job again. |
| HeliGuardian controls disabled on a Candidate Site | Stated beneath; normally no HeliGuardian sign-in. | Sign in to HeliGuardian. |
| Sign-in box when sending a Field or recce | HeliGuardian session ended (fixed end, idle timeout, or a portal sign-in). | Sign in, or Send Later. |
| 1 recce not sent on Ready | A recce is held on the device. | Open it and Send when connected. |
| Job refused: You are not signed in to HeliGuardian. Sign in again, or send it as PERSONAL. | The Job was sent for the organisation but the HeliGuardian session has ended. It is never moved to PERSONAL automatically. | Sign in to HeliGuardian again, or sign out of it and send as PERSONAL. |
| Job refused: You are signed in to HeliGuardian for another organisation now. Choose the callsign again. | The HeliGuardian sign-in changed organisation after the Callsign was chosen. | Choose the Callsign again. |
| Job refused: [Callsign] is not one of your organisation's aircraft in HeliGuardian. | The Callsign is not in the organisation's aircraft list. | Choose an aircraft from the list, or add it in HeliGuardian. |
| Job refused: Could not check [Callsign] with HeliGuardian: … | HeliGuardian did not answer the aircraft check. | Send again. |
| Job refused: Your EFB folder is unavailable right now; try again | The PERSONAL folder could not be read. | Send again. |
| ACANS overlay no longer updates; the link answers This EFB link is retired | The link file was downloaded before 17 November 2026. | Download the Callsign's link file again (Settings › EFB) and replace the old file in Overlays. |