HeliGuardian · Crew guide

The Quickdraw crew manual

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).

Screens for
Page: quickdraw.heliguardian.com Covers the page as of 17 Nov 2026 · What's new Select a screen to enlarge it

Quick reference

QD-CREW

Start of shift

Quickdraw pageOpen, signed in
CallsignSet
EFB link fileIn Overlays (once)
HeliGuardianSigned in
Session time leftCovers the shift
Ready lineReady for a task

On a task

New TaskSelect
Incident positionEnter, check
Run settingsCheck mode, D
AnalyseSelect
Job cautionsRead
Candidate SitesWalk, cautions
ACANS overlayOn

After landing

I Landed HereSelect on the site
FieldChoose or create
RecceScore, send
Recces not sentNone on Ready
00

Terms

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.

TermMeaning
JobOne 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.
CallsignThe 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 FolderWhere 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 SiteA 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.
DThe aircraft's reference dimension in metres (13.65 m). It sizes the Landing Zone.
Landing ZoneThe 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 objectAnything 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 timeTime 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 roadThe point on a road a car can stop on that is nearest the patient on foot. The vehicle's drive ends there.
Vehicle optionWalk 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 SiteA 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 SiteA 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.
FieldA landing site held in HeliGuardian for your organisation, as one point, with a status and recces.
Known FieldA Field inside a Job's search radius. A Job run with a HeliGuardian sign-in assesses every Known Field (chapter 06).
RecceAn assessment of a Field held in HeliGuardian: score 0 to 5, size, shape, surface, slope, surrounds, access, downwash and notes.
PolygonAn 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 ReadingThe Job's assessment applied at a point selected on its map (chapter 09).
Crew's PointA 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 chipOne coded finding in a Point Reading: a label in capitals (e.g. SLOPE) and a sentence with the measured value (chapter 09).
HeadingA 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 sourceOne 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.
01

Before the shift

Complete once at the start of each shift, before tasking.

  1. Open https://quickdraw.heliguardian.com in Safari or Chrome. Sign-in requires HTTPS; a http:// address does not work.
  2. Sign in with the email and password from the invitation. Accounts are created by invitation only.
  3. Optional, Safari: Share › Add to Home Screen places a Quickdraw icon on the home screen.
  4. Sign-in opens the Ready screen.
  5. Settings › HeliGuardian Account: sign in with the HeliGuardian username and password. This account is separate from Quickdraw's. With it, the EFB Folder is the organisation's and the Callsign is chosen from its aircraft. Without it, the EFB Folder is PERSONAL, Jobs do not assess Known Fields, and Nearby fields, Create a Field, I Landed Here and recces are disabled (chapter 13).
  6. On Ready, choose the Callsign (signed in to HeliGuardian: from the organisation's aircraft; otherwise type it). The tag beside it names the EFB Folder: the organisation, or PERSONAL.
  7. On the iPad running ACANS: Settings › EFB › Download Linked File (HME56.kml for HME56), then move the file as in Quickdraw in ACANS below. The file is for that Callsign in the current EFB Folder: with it in place, ACANS shows every Job run for that Callsign in that folder, from any device. A Callsign used both for the organisation and as PERSONAL needs a file for each.
  8. Check that Signed in on Ready covers the shift. If not, sign out and in again (Settings) for a full session.
NoteSet as My Default (chapter 04) stores the Callsign and Run settings against the Quickdraw account; they are filled in at every sign-in, on any device.
CautionA Job run without a Callsign is not written to the EFB. Ready shows an amber warning while the Callsign is empty.
CautionLink files downloaded before 17 November 2026 no longer work: the server answers them with This EFB link is retired. Download the Callsign's link file again and replace the old one in the ACANS Overlays folder.
CautionWhen the Quickdraw sign-in expires during a Job, a login screen replaces the page. The Job continues on the server; after signing in, open it from Last job.
02

The Ready screen

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.

  • 1Status line. Ready for a task (green) when all three conditions hold: the sign-in has time left, the server answered its last check, and the Callsign is valid. Otherwise it states the failed condition (table below).
  • 2Callsign. Signed in to HeliGuardian: a drop-down of the organisation's aircraft (callsign · registration). Otherwise: typed. The same value as Settings › Callsign; the EFB link and Last job follow it.
  • 6EFB Folder tag: the organisation's name, or PERSONAL. It follows the HeliGuardian sign-in.
  • 3EFB link. The Callsign's link file; opens Settings at the download.
  • 4Last job. The Callsign's most recent Job in this EFB Folder, from any device: position, time (Z), Candidate Site count, whether it was sent to the EFB, radius. Selecting it opens the Job. A failed Job writes nothing to the EFB and shows not on the EFB.
  • 5New Task. Opens incident position entry.
123456
Ready, signed in to HeliGuardian, Callsign chosen
123456
Ready, signed in to HeliGuardian, Callsign chosen
123456
Ready, signed in to HeliGuardian, Callsign chosen

Status line values

Status lineConditionAction
Ready for a taskAll 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 CallsignConditionAction
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.
12
No Callsign chosen
12
No Callsign chosen
12
No Callsign chosen

Recces not sent

  • 1While one or more recces are held on the device without HeliGuardian's confirmation of receipt, Ready shows N recce(s) not sent, which opens Recces not sent (chapter 13). With none held, the row is absent.
1
One recce held on the device
1
One recce held on the device
12
One recce held on the device
03

Incident position entry

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.

A. OS grid reference

  1. Select OS GRID .
  2. Select the 100 km square . The nine squares are the device's own square (HERE) and its neighbours. For another square, select OTHER and its two letters; letters that form no square are disabled.
  3. Enter the easting digits, then the northing digits , without a space.
  4. Read the hint line. Type one more digit: odd digit count. Grid reference complete: usable. A 4, 6 or 8-figure reference is taken as the centre of its square; 10 figures is a 1 m square.
  5. Check the position in the other formats, shown under the entry (second screen).
  6. ANALYSE or ENTER submits the Job.
NoteSelecting another of the nine squares keeps the digits entered. OTHER clears the reference.

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.

12345
100 km square selection
12345
100 km square selection
123
100 km square selection
12345
TL 30095 77152, complete
12345
TL 30095 77152, complete
123
TL 30095 77152, complete

B. Latitude and longitude

  1. Select the format: DD (decimal degrees), DDM (degrees, decimal minutes) or DMS (degrees, minutes, seconds).
  2. Enter the hemisphere first. N and S share keys with digits: 8/N, 2/S . Then the latitude digits.
  3. ENTER moves to the longitude (or select the LON field ).
  4. E or W (6/E, 4/W), then the longitude digits, until the hint reads Position complete.
  5. ANALYSE or ENTER.

FMT cycles the formats. A complete position is converted to the new format; an incomplete one is cleared, and the hint states it.

123
The same position in DD
123
The same position in DD
1
The same position in DD

Keys

KeyFunction
DELDeletes the last character.
CLEARClears the entry (lat/long: both fields).
ENTERLat/long: latitude to longitude. On a complete position: as ANALYSE. A keyboard Enter key is equivalent.
SETPlaces the position on the map and closes the entry without submitting a Job. New Task reopens it with the position filled in.
ANALYSESubmits 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.
CANCELCloses the entry with no change.

A. OS grid reference

  1. Select OS GRID .
  2. Select the 100 km square , or type its two letters. The nine squares are the device's own square (HERE) and its neighbours; OTHER opens the letter grid for any other square.
  3. Type the easting digits, then the northing digits, without a space.
  4. Read the hint line. Grid reference complete: usable. A 4, 6 or 8-figure reference is taken as the centre of its square; 10 figures is a 1 m square. The position in the other formats is shown beneath.
  5. Enter, or ANALYSE (below the Run settings), submits the Job.

A grid reference or decimal latitude, longitude pasted on the page is entered. A click on the map sets the position.

12345
100 km square selection
12345
100 km square selection
123
100 km square selection
12
TL 30095 77152, complete
12
TL 30095 77152, complete
12
TL 30095 77152, complete

B. Latitude and longitude

  1. Select DD, DDM or DMS.
  2. Type the hemisphere letter (N or S), then the latitude digits .
  3. Enter or Tab moves to the longitude: E or W, then the digits, until the hint reads Position complete.
  4. Enter, or ANALYSE.

Changing format converts a complete position; an incomplete one is cleared, and the hint states it.

Keys and buttons

Key or buttonFunction
BackspaceDeletes the last character.
EnterLat/long: latitude to longitude. On a complete position: as ANALYSE.
TabMoves between the latitude and longitude fields.
SETPlaces the position on the map and closes the entry without submitting a Job.
ANALYSESubmits 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.
CANCELCloses the entry with no change.
1
The same position in DD
1
The same position in DD
1
The same position in DD
04

Run settings

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.

  • 1Search radius around the incident: 500 to 2500 m, in 100 m steps (− and +). Job time and server memory rise with roughly the square of the radius.
  • 2Clearance mode, Day · 2D circle or Night · 2D × 4D box (the Landing Zone), and D in metres; night D is limited to 60 m. On completion the Job also computes the other mode (chapter 06).
  • 3Map features from: Ordnance Survey (OS National Geographic Database; authoritative) or OpenStreetMap. The choice affects mapped features only (roads, water, land cover, field boundaries, land use). LIDAR terrain and road routing are the same for both.

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.

123
Run settings, upper part
123
Run settings, upper part
12
Run settings, upper part
  • 1Add the LIDAR survey's hedges, drains and woods (trial; off by default). When on, the Job reads the LIDAR point cloud along its walking routes and adds the hedges, walls, drains and gaps found there to the map features. Use only when asked to evaluate it.
  • 2Set as My Default stores these values and the Callsign against the Quickdraw account; they are filled in at every sign-in, on any device. When the page differs from the stored values it shows Changed from your defaults.
CautionClearance mode and D are not set automatically by time of day. Check both before a night task.
12
Run settings, lower part
12
Run settings, lower part
12
Run settings, lower part
05

While a Job runs

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.

  • 1Finding sites, with the position and radius submitted.
  • 2Stages. Completed stages are ticked; the running stage shows seconds elapsed. Stage durations vary widely between Jobs, so the figure is time spent, not time remaining. A slow Data source (e.g. the OpenStreetMap server being asked again) is stated above the stages.
  • 3Show all known fields: the number of Known Fields being assessed. Shown with a HeliGuardian sign-in.
  • 4Known Fields, listed when HeliGuardian answers and before the Job has assessed them: name, distance and direction from the incident, status, last recce date and score. The walk column reads not checked yet until the Job completes.
NoteOn completion, with a Callsign set, the Candidate Sites are written to the Callsign's EFB file in the Job's EFB Folder. No download is needed; set the Callsign's ACANS overlay ON (Quickdraw in ACANS, part C).
1234
Known Fields listed before completion
1234
Known Fields listed before completion
1234
Known Fields listed before completion

Known Field screen

  • 1Walk to patient (– until assessed) and distance and direction from incident.
  • 2Outcome. Before completion: Not checked yet. After: Landable, Offered on its recce's word, or Not offered with the reason (chapter 06).
  • 3Recces: every recce HeliGuardian holds for the Field, newest first. The newest is shown in full (size, shape, surface, slope, surrounds, access route, ambulance suitability, RV point, landowner, permission, notes); older recces are collapsed.

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.

123
A Known Field before completion
123
A Known Field before completion
123
A Known Field before completion
06

The Candidate Site list

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.

  • 1Map controls: Settings, Layers, Show all sites, Measure.Rail: Ready, New Task, the Job, Layers; Settings at the foot. Polygons, Measure and Recces not sent are in the top bar.
  • 2Job cautions: conditions applying to every Candidate Site (table below).
  • 3Day · 2D / Night · 2D × 4D. On completion the Job recomputes the Candidate Sites in the other clearance mode from the same data. Selecting the other mode displays that result without a new Job; the line beneath states the mode the Job ran in. If selected before the other result is ready, it is displayed when ready. The EFB file, the KMZ and the 3D view follow the mode displayed.
  • 4Best first / Nearest first: list order (below).
  • 5Exclude locked sites removes Locked Candidate Sites and displays the next unlocked Candidate Sites the Job found in their place. Show all known fields (on by default when the radius contains Known Fields) adds each offered Known Field that is not already a listed Candidate Site, and lists those not offered with the reason. Neither switch changes rank.
NoteThe Callsign's EFB file follows the display: clearance mode, order, both switches, and a Measure result (chapter 10).
12345
The Candidate Site list
12345
The Candidate Site list
12345
The Candidate Site list

Candidate Site rows

  • 1Grabber: switches the panel between half and full height (chapter 08).
  • 2Row: symbol and rank; distance and compass direction from the incident (e.g. 7 m SW); the first caution (amber text); Walk time (e.g. 0:07). Selecting the row opens the Candidate Site screen (chapter 07).
  • 3Locked Candidate Site: grey square symbol; the row reads Locked with the requirement. Its Walk time is measured from the main entrance.
123
Candidate Site rows
23
Candidate Site rows
23
Candidate Site rows

Known Fields in the list

The Job assigns each Known Field one outcome:

OutcomeConditionResult
LandableQuickdraw'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 wordQuickdraw'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 offeredNeither 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).

  • 1Offered Known Field: a Candidate Site ranked after the Job's own (Site 6 · known field A). The letter matches its hexagon on the map.
  • 2Known Field not offered: name, last recce, distance from the incident, reason.
  • 3Open 3D view: the Job in 3D, in a new tab (chapter 12); the line beneath gives the point cloud's state. The line above states whether Point Readings are available (chapter 09).
  • 4Layers and Job details (chapters 11, 12).
1234
Foot of the list
1234
Foot of the list
1234
Foot of the list

Best first and Nearest first

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.

  • 1Order selector.
  • 2States the order in use. Rank numbers are unchanged: Site 3 remains Site 3 on the map and in the EFB.
12
Nearest first
12
Nearest first
12
Nearest first

Job cautions

CautionConditionEffect
Crop and grass state not checkedThe satellite vegetation index (NDVI) was not read.Crop height and long grass are not assessed at any Candidate Site.
Final approach requiredThe 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 footNo 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 areaThe map source returned no features.Roads, water, buildings and boundaries were not applied: every Candidate Site is unchecked against them.
Map features unavailableThe map source failed.As above.
[Data source]: not read / fell backOne Data source failed or used its fallback.The line beneath states the consequence; detail in Job details.
Known fields not checkedNo HeliGuardian sign-in, or the HeliGuardian read failed.The Job has no Known Fields.

Map symbols

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.

IncidentThe position entered
Candidate Site, greenSuitable land use, by rank
Candidate Site, amberConditional land use, or a Known Field offered on its recce's word
Locked Candidate SiteSquare: key-holder or code required
RVRendezvous Point for Site 5
Patient roadRoad point nearest the patient on foot
Known Field, offeredBy map letter
Known Field, greyNot offered, or not yet assessed
07

The Candidate Site screen

Opened from a row or from the site's map symbol. The map centres on the Candidate Site.

  • 1‹ Sites: back to the list.
  • 2Walk to patient; distance and direction from incident.
  • 3Cautions: slope in the Landing Zone; DNO poles and towers with distance and bearing from the site; land use conditions.
123
Site 1
123
Site 1
123
Site 1

Site data

  • 1Rank (Ranked 1 of 5), score out of 100, surface.
  • 2Data: slope in the Landing Zone, mean and maximum; ground height (ft AMSL, LIDAR DTM; not surveyed here in a survey gap); area of the connected clear ground; percentage of the Landing Zone clear; distance to the nearest road; surface; number of the 8 approach axes clear, where computed.

Lower on the screen:

  • The way to the patient: Foot to scene (Walk time); Final approach (distance on foot past a barrier, no time); Vehicle-assisted total and drive leg, where a Vehicle option exists; barriers crossed; field edges crossed where no gate is mapped.
  • Show the route on the map (on by default).
  • Wind and sky: modelled 10 m wind direction (°M, from) and speed with gusts (kt); Sun and Moon bearing (°M) and elevation; Moon phase and illumination. Display only; the analysis does not use them.
  • Nearby fields, Create a Field here, I Landed Here (chapter 13).
12
Site 1, site data
12
Site 1, site data
12
Site 1, site data

Candidate Site on a Known Field

  • 1When an offered Known Field is within 150 m of the Candidate Site, the screen shows Known field [name] is on this site, with the Field's last recce date and score.
  • 2The Field's recces: newest in full, older collapsed.
12
Site 5, on Known Field Low Road Farm
12
Site 5, on Known Field Low Road Farm
12
Site 5, on Known Field Low Road Farm

HeliGuardian functions

  • 2Nearby fields: Fields within 1 km of the Candidate Site's centre.
  • 3Create a Field here: a new Field at the Candidate Site's centre.
  • 4I Landed Here: records the landing position and opens a recce.

All three require a HeliGuardian sign-in; without one they are disabled and the reason is stated beneath. Procedures: chapter 13.

234
Lower part of the screen
234
Lower part of the screen
234
Lower part of the screen

Locked Candidate Site

  • 1States the Closed Site (e.g. a school), the requirement (key-holder or code), and the time to the patient via the main entrance.

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.

1
Site 2, locked
1
Site 2, locked
1
Site 2, locked
08

The map and the panel

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.

  • 1Grabber. Select: half and full height. Drag down: title bar only. Drag up: restores the panel.
  • 2Show all sites: fits the incident and all Candidate Sites to the screen.
  • 3Zoom: + and −, or pinch.
  • 4Measure (chapter 10), in the top bar.
Map selectionResult
Candidate Site symbolOpens the Candidate Site screen.
Route, RV or Patient roadA label.
Known Field hexagonThe Field's outcome and recces.
Any other point inside the radius, with a finished Job displayedA Point Reading (chapter 09).
Any point, with the entry open or on ReadySets the incident position.

Wind barbs, Sun and Moon

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.

1234
The map with all Candidate Sites shown
234
The map with all Candidate Sites shown
34
The map with all Candidate Sites shown
09

Point Readings

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.

Availability

  • 1The line at the foot of the list states whether Point Readings are available for the Job, or why not.

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.

1
Availability line
1
Availability line
1
Availability line

The Point Reading screen

Titled Your point, it takes the place of the Candidate Site screen. The Landing Zone and the walking route are drawn in white.

  • 1Verdict: whether the displayed mode's Landing Zone (e.g. A 27.3 m day circle for D 13.65 m), centred on the selected cell, fits. It fits when, at some orientation, every cell in it is surveyed, inside the search radius, not excluded (water, Polygons, power-line buffers, excluded land use) and free of surface objects over 2 m, and the slope at its centre is within Max slope.
  • 2Walk to patient; distance and direction from the incident.
  • 3Reason chips (below), each followed by its sentence.

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.

ConditionTitle in ACANS
A walking route reaches the patientHME56 | Walk 4:37
…and the Landing Zone does not fitHME56 | Walk 4:37 | NO LZ
No walking route (NO ACCESS), or only a straight-line estimateHME56 | No walk
Outside the search radiusHME56 | 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.

123
Landing Zone fits
123
Landing Zone fits
123
Landing Zone fits
123
Landing Zone does not fit
123
Landing Zone does not fit
123
Landing Zone does not fit

Reason chips

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:

OutlineEffect
RedA 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.
AmberThe Landing Zone fits. The finding is a caution a Candidate Site here would carry.
GreyInformation 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.

ChipRaised whenOutline
SLOPERed: LIDAR slope in the Landing Zone exceeds Max slope (7°). Amber: the zone fits and its maximum slope exceeds 5°.Red / amber
OBSTRUCTIONSRed: 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
ROADThe Landing Zone is on a road carriageway: landing requires a police road closure.Red / amber
NO SURVEYPart of the Landing Zone has no LIDAR survey; slope and surface objects there are unknown.Red
POWER LINEThe 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
WATERMapped water or tidal ground in the Landing Zone.Red
YOUR POLYGONInside an active No Access or No Landing Polygon of the Job's Callsign.Red
EXCLUSION ZONEInside a mapped excluded land use (e.g. solar farm, substation, cemetery) or a wire inferred between mapped pylons.Red
TOO LITTLE ROOMThe Landing Zone does not fit clear of obstacles at any orientation.Red
PAST THE RADIUSThe Landing Zone extends beyond the search radius, where the Job assessed nothing.Red
SMALL CLEARINGThe Landing Zone fits, but the connected clear ground is smaller than Min area (100 m²). The sentence gives both areas.Red
NO ACCESSNo walking route from the point reaches the patient on the Job's ground model.Red
LOCKEDInside 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 AVAILABLENo 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 REQUIREDThe walking route is 500 m or shorter. A Vehicle option is computed only beyond 500 m.Grey
WALKING IS QUICKERThe Walk time is no longer than the Vehicle option's total. The sentence gives both.Grey
VEHICLE NOT WORKED OUTThe drive was not computed: no road router on this server, or the data needed was not kept for this Job.Grey
CLOSER FOOT ROUTE AVAILABLEAn offered Candidate Site has a shorter Walk time. The sentence names it and gives both times.Grey
10

Measure

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.

  1. Select Measure (ruler) on the map in the top bar. Drawing starts and the panel lowers.
  2. Select each corner of the area, then the first corner again to close it.
  3. The result is drawn on the map with side lengths and listed in the panel.
  4. The result stays on the map, in every view, until Clear Measurement in the Measure panel.
  5. With a finished Job displayed, the result is added to that Job's KMZ, its EFB file and its 3D view, in the rectangle and units selected. The EFB file is rewritten when the result arrives, when Largest / Unobstructed or the units change, and when it is cleared. The line under Clear Measurement states the outcome. A Job displayed later takes the result over; a Job displayed with no result on the device shows its own.
  • 1Draw Another Area: replaces the area.
  • 2Largest / Unobstructed: the rectangle displayed. Metres / Feet: units. Both settings are stored on the device.
  • 3Largest rectangle: length, width, bearing of the long side (°M, both directions).
123
Largest rectangle
123
Largest rectangle
123
Largest rectangle

Unobstructed rectangle

  • 1Unobstructed: the largest rectangle that contains no LIDAR cell 1 m or more above the ground model (including objects outside the area that overhang it) and no unsurveyed cell, nor any ground kept clear of an overhead wire. Its LIDAR part reflects the ground at the survey date.
  • 2Length, width and long-side bearing of that rectangle.

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.

CautionUnsurveyed ground is never reported as clear. When the LIDAR check cannot run (no survey, or the area is over 1 km on a side) the reason is stated and no unobstructed rectangle is given.
12
Unobstructed rectangle
12
Unobstructed rectangle
12
Unobstructed rectangle
Obstruction list
Obstruction list
Obstruction list
11

Layers

Opened from the map's Layers controlLayers in the rail, or from the foot of the list. ‹ Sites returns.

  • 1Strength: opacity of the suitability overlay over the satellite image.
  • 2Overlay key: landable (Landing Zone clear); too close to an obstacle; steep (over Max slope); obstacle over 1 m (trees, buildings); restricted zone; water; power line.

Below: Wind and sky at the sites (on/off, with the forecast model and run time) and Where OS map data covers.

12
Layers, upper part
12
Layers, upper part
12
Layers, upper part

Obstructions detected

  • 1Each obstruction and crossing class the Job found, with its count; all off by default. Ticking a class draws it.
  • 2Hide all.

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.

12
Obstruction classes
12
Obstruction classes
12
Obstruction classes
12

Job details and the 3D view

Both are at the foot of the Candidate Site list.

Job details

  • 1Download KMZ: the Job as displayed (mode, order and switches, given in brackets), with any Measure result over it (chapter 10), for Google Earth or another EFB application. Not needed for the Callsign's EFB, which reads the link file.
  • 2Data sources: each Data source, its status (green worked, amber fell back, red failed) and what it returned. A failed or fallen-back Data source is also stated as a Job caution.
12
Job details
12
Job details
12
Job details

The 3D view

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.

  • View: suitability overlay on the satellite image; satellite image only; or the LIDAR point cloud. The point cloud is prepared after the Job; the line under the button reads Point cloud: ready when it is available.
  • Camera: drag to orbit; pinch or scroll to zoom; two-finger drag or right-drag to pan. From above and Patient are preset views. Heights sets vertical exaggeration.
  • Measurement: a Measure result over the Job (chapter 10), as the map shows it: the area drawn (white, dashed), LIDAR obstructions (orange), the ground kept clear of each overhead wire (purple; red where it reaches the largest rectangle while that is shown), each wire dashed on the ground beneath it (its height is not known), and the rectangle with its sides and long side labelled. Laid on the bare ground; seen faintly through terrain and trees. Read again each time the tab is selected and when the Job tab changes it. The tick hides it.
  • ← Back to Quickdraw closes the tab.

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.

13

HeliGuardian Fields and recces

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

Nearby fields on a Candidate Site lists the Fields within 1 km of its centre, nearest first, and draws them on the map.

  • 1Field row: map letter, name, distance and bearing (°M) from the Candidate Site, status, last recce date. Selecting the row centres the map on the Field.
  • 2Add Recce: opens a recce of that Field.
12
Nearby fields
12
Nearby fields
12
Nearby fields

Create a Field

  1. Create a Field here first lists the Fields HeliGuardian holds within 1 km of the Candidate Site and frames them on the map, to prevent duplicates. Selecting one creates nothing and offers a recce of it.
  2. If the Field is not listed: No, a New Field .
12
Duplicate check
12
Duplicate check
12
Duplicate check
  • 1Name (required).
  • 2Nearest landmark (required).
  • 3Elevation, whole feet AMSL (required). Pre-filled from the LIDAR DTM at the Candidate Site's centre; empty in a survey gap. Editable.
  • 4Create Field and Add Recce: creates the Field in HeliGuardian and opens its recce.

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).

1234
New Field
1234
New Field
1234
New Field

I Landed Here

Records the actual landing position for a recce. Opened from the Candidate Site used.

  • 1Use This Device's Position: a new high-accuracy fix. A refused permission, an unavailable fix or a timeout is stated.
  • 2Choose on the Map: the landing position is the point selected.
12
Landing position source
12
Landing position source
12
Landing position source
  • 1Landing position: grid reference; source (device fix, with accuracy and time, or chosen on the map); ground height (LIDAR DTM). A map selection, or dragging the marker, moves it.
  • 2HeliGuardian fields near here: Fields within 1 km of the landing position, nearest first, with distance and bearing. Selecting one opens its recce.
  • 3New Field Here: creates a Field at the landing position (elevation from the LIDAR DTM there), then opens its recce.
123
Landing position and nearby Fields
123
Landing position and nearby Fields
123
Landing position and nearby Fields

The recce

Header: Field name, its last recce date, this recce's date.

  • 1Score, 0 to 5 (six buttonsa drop-down): 0 Unusable; 1 Poor (particular caution even in ideal conditions); 2 Fair (usable in ideal conditions, with specific considerations); 3 OK (no specific considerations beyond normal care); 4 Good (suitable in most conditions with normal care); 5 Very good (unlikely to present challenging conditions). A recce sent without a score is recorded as 0; Quickdraw requires confirmation first.
  • 2i: the score definitions.
  • 3Size: length and width (m), and notes.

What you saw: shape, surface, slope, surrounds, access, downwash; free text.

123
The recce, upper part
123
The recce, upper part
123
The recce, upper part
  • 1Notes: free text.
  • 2Attach Quickdraw's measurements (on by default): adds a line at the start of the notes, marked Measured, not observed, giving the Job, the Candidate Site, the landing position and its source, and the LIDAR slope (maximum and mean) and ground height at the Candidate Site's centre with the survey name. The recce's slope gradient is set from the same measurement.
  • 3Send to HeliGuardian. If the HeliGuardian session has ended, a sign-in box opens, with Send Later.

The recce is held on the device from the first character entered until HeliGuardian confirms receipt. Leaving the screen does not discard it.

123
The recce, lower part
123
The recce, lower part
123
The recce, lower part

Recces not sent

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.

  • 1Each held recce: Field, time created (Z), Job and Candidate Site, and the reason it was not sent.
  • 2Send: sends again. Selecting the recce opens it to complete, edit or delete.
NoteWhen a send's outcome is unknown (the connection dropped after sending), Quickdraw checks HeliGuardian for the recce before sending again; a recce is not duplicated. A new Field and its recce are held together: the Field is created first, and only once.
CautionHeld recces are stored in this browser on this device, per Quickdraw account. They are not visible on another device. Clearing the browser's site data deletes them.
12
Recces not sent
12
Recces not sent
12
Recces not sent
14

Settings and Polygons

Opened from the gear on the mapthe gear at the foot of the rail. Done returns to the previous screen.

  • 1Callsign: the same value as on Ready, with the EFB Folder tag.
  • 2Polygons (below): a row in Settings: in the top bar.
  • 3Download Linked File: the Callsign's EFB link file for the current EFB Folder (Quickdraw in ACANS). Each Callsign in each EFB Folder has its own.
  • 4Run Settings under Task defaults (chapter 04).
1234
Settings, upper part
1234
Settings, upper part
123
Settings, upper part
  • 1HeliGuardian Account: sign-in state; opens the HeliGuardian screen.
  • 2Crew Manual: this manual, in a new tab.
  • 3What's New: the change log, newest first.
  • 4Layout: Automatic selects Touch for a touch screen and Console for a mouse or trackpad (chapter 16). Stored on this device only.
  • 5Sign Out of Quickdraw, with the sign-in time remaining.
12345
Settings, lower part
12345
Settings, lower part
2345
Settings, lower part

Settings › HeliGuardianSettings: the HeliGuardian section

  • 1Signed in: the HeliGuardian user and organisation, the session's fixed end time (Z), and its idle timeout; HeliGuardian ends the session at whichever comes first. Signed out: username and password fields. Quickdraw's server holds the HeliGuardian session; the password is not stored.
  • 2Sign Out of HeliGuardian.
CautionHeliGuardian allows one web session per user. Signing in from Quickdraw ends a HeliGuardian portal session; signing in to the portal ends Quickdraw's. A send after the session has ended opens a sign-in box.
12
Settings › HeliGuardian
12
Settings › HeliGuardian
12
Settings › HeliGuardian

Polygons

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.

  • 1Polygons of: the EFB Folder listed, the organisation or PERSONAL. It follows the HeliGuardian sign-in.
  • 2Folders, A–Z, with their contents counted. Selecting one opens it; the bar's ‹ goes up a level. Inside a folder, Rename Folder and Delete Folder are at the foot.Folders are a tree: ▸ / ▾ opens one in place and selects it; each folder row has rename and delete icons.
  • 3Polygon, A–Z after the folders: name, rule, active hours (e.g. Mon–Fri 08:00–16:00, or Always). Selecting it opens the editor.
  • 4Draw New Polygon: select each corner on the map, then the first corner again. Reads Stop Drawing while drawing.
  • 5New Folder: created in the folder open.
12345
Polygons, top level
12345
Polygons, top level
12345
Polygons, top level
A folder open
A folder open
A folder open

Polygon editor

  • 1Name.
  • 2Folder; selecting it opens the folder pickera drop-down. Changing it moves the Polygon.
  • 3Rule (required): No Access: no Candidate Site inside, and walking routes do not enter. No Landing: no Candidate Site inside; walking routes may cross. Rule In: Candidate Sites allowed where the map data excludes them, except inside a power-line buffer.

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.

1234
Polygon editor
1234
Polygon editor
1234
Polygon editor
15

Night use

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.

Ready, Dark appearance
Ready, Dark appearance
Ready, Dark appearance
Candidate Site list, Dark appearance
Candidate Site list, Dark appearance
Candidate Site list, Dark appearance
16

Layouts

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.

DeviceLayoutPanelControls
PhoneTouchSheet below the map: title bar, half or full height, moved by the grabber.Map buttons: Settings, Layers, Show all sites, Measure.
iPad, uprightTouchAs phone.As phone.
iPad, sidewaysTouchBeside the map, full height.As phone.
LaptopConsoleBeside 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).
  • 1Map buttons: Settings, Layers, Show all sites, Measure.
  • 2Grabber: panel height.
  • 3Panel.
  • 1Top bar: Map, Polygons, Measure, Recces not sent (with a count while recces are held); Callsign, server state, EFB file time, sign-in time remaining.
  • 2Rail: Ready, New Task, the Job, Layers; Settings at the foot.
  • 3Panel.
  • 4Measure, with Recces not sent to its right; each opens over the current screen.
  • 5EFB SENT: time (Z) the Callsign's EFB file was last written.
123
This device's layout
13
This device's layout
12345
This device's layout
17

Faults and messages

Quickdraw states every missing input, failed Data source and limit applied.

IndicationCauseAction
Page closed or device locked during a JobNone; the Job continues on the server.Reopen within 30 minutes to resume; after that, Last job on Ready.
Login screen during a JobQuickdraw sign-in expired.Sign in; open the Job from Last job.
Not ready: the server is not answeringNo server response.Check signal. Retried every 30 s. A Job submitted now fails.
Pick a grid square firstDigits entered before the 100 km square.Select a square, or OTHER and its letters.
Tap N or S first / Tap E or W firstLat/long digits before the hemisphere.Enter the hemisphere.
That field is full: DEL or CLEAR to change itAll digits entered.DEL or CLEAR.
That reference is outside the OS gridSquare or digits invalid.Check the reference.
Format changed; the unfinished entry was clearedFormat changed on an incomplete position.Re-enter.
Job failed: killed by SIGKILL, most likely out of memoryServer 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 disabledThe other clearance mode could not be computed; the reason is stated beneath.Run a Job in that mode.
Point Reading: ground clearedNo 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 rectangleLIDAR 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 measurementThe 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 checkedNo HeliGuardian sign-in, or the read failed.Sign in to HeliGuardian; run the Job again.
HeliGuardian controls disabled on a Candidate SiteStated beneath; normally no HeliGuardian sign-in.Sign in to HeliGuardian.
Sign-in box when sending a Field or recceHeliGuardian session ended (fixed end, idle timeout, or a portal sign-in).Sign in, or Send Later.
1 recce not sent on ReadyA 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 againThe PERSONAL folder could not be read.Send again.
ACANS overlay no longer updates; the link answers This EFB link is retiredThe link file was downloaded before 17 November 2026.Download the Callsign's link file again (Settings › EFB) and replace the old file in Overlays.
WarningCandidate Sites are derived from map and terrain data. They do not replace the crew's assessment of the site from the air.