Launching Q1 2027. Join the waitlist for early access.
Back to Helicopter HEMS (Part 135)

Helicopter HEMS (Part 135) · Dispatch & tracking

Dispatch

One ops board releases and tracks inter-facility transfers and scene flights, so the mission lives in the system rather than only on the radio. It replaces reconstructing the mission timeline from the radio log afterward.

Launching the first quarter of 2027.

Dispatch release
Trip CMX-4471 · N680CO · 2 legs
Release signed — fuel, W&B, and weather attached
LegDepCrewStatus
KTEB → KPBI08:15Walker / ChenReleased
KPBI → KTEB16:40Walker / ChenPlanned
Block fuel
9,400 lb
ETE
2:25
KPBI wx
VFR
METAR/TAF · NOTAMs · fuel · W&B on one printable release

Illustrative — every screen reflects your own data.

Who it's for

HEMS dispatch desks releasing inter-facility transfers and scene flights who want the mission to live in the system rather than only on the radio.

What it replaces

Reconstructing the mission timeline from the radio log afterward instead of keeping the mission in the system as it happens.

What dispatch gives you

  • One ops board for inter-facility transfers and scene flights
  • The mission lives in the system, not only on the radio
  • No reconstructing the timeline from the radio log

One ops board for transfers and scene flights

An inter-facility transfer or a scene flight is released on one ops board, so the mission lives in the system instead of only on the radio. The flight is then tracked against the same release the desk created.

  • One ops board for inter-facility transfers and scene flights
  • The mission lives in the system, not only on the radio
Dispatch release
Trip CMX-4471 · N680CO · 2 legs
Release signed — fuel, W&B, and weather attached
LegDepCrewStatus
KTEB → KPBI08:15Walker / ChenReleased
KPBI → KTEB16:40Walker / ChenPlanned
Block fuel
9,400 lb
ETE
2:25
KPBI wx
VFR
METAR/TAF · NOTAMs · fuel · W&B on one printable release

The dispatch picture is the mission record

Because the release and its details are recorded as they happen, nobody has to reconstruct the mission timeline from the radio log afterward. The dispatch picture and the mission record are the same thing, built in real time.

  • No reconstructing the timeline from the radio log
Live tracking
FlightAware AeroAPI · token share links
Customer share link activeno login · expires on its own
TailRouteETAStatus
N680COKTEB → KPBI · FL41016:42Enroute
N221MOKDAL → KAUS · FL28009:18Climbing
N907HOScene → KDEN · 2,500HEMS
Position + ETA on the ops board · bring your own AeroAPI key

How an operator uses this

An inter-facility transfer or a scene flight is released on one ops board, so the mission lives in the system instead of only on the radio. Because the release and its details are recorded as they happen, nobody has to reconstruct the mission timeline from the radio log afterward. The dispatch picture and the mission record are the same thing.

Illustrative — every screen reflects what's in your own data, nothing more.

How it works

Dispatch, step by step

  1. Release an inter-facility transfer or scene flight on the ops board.

  2. The mission and its details live in the system, not only on the radio.

  3. Track the flight against the same release the desk created.

  4. Skip reconstructing the mission timeline from the radio log afterward.

Questions

Dispatch — frequently asked

How are HEMS missions dispatched?

Inter-facility transfers and scene flights are released and tracked on one ops board, so the mission lives in the system rather than only on the radio.

Do I have to reconstruct the mission timeline afterward?

No. Because the release lives in the system as it happens, the mission record is built in real time instead of reconstructed from the radio log.

Every Helicopter HEMS (Part 135) workspace also includes the platform-wide backbone — logbook, credentials, compliance, reporting, and audit trail.

See the backbone

See dispatch on your operation.

It's part of the Helicopter HEMS (Part 135) workspace. Request a demo or join the waitlist.