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.

Live tracking
FlightAware AeroAPI · token share links
Customer share link activeno login · expires on its own
TailRouteETAStatus
N680CLKTEB → KPBI · FL41016:42Enroute
N221MXKDAL → KAUS · FL28009:18Climbing
N907HMScene → KDEN · 2,500HEMS
Position + ETA on the ops board · bring your own AeroAPI key

Illustrative — every screen reflects your own data.

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

How an operator uses this

An inter-facility transfer or scene flight is released on one ops board, so the mission lives in the system instead of only on the radio and doesn't have to be reconstructed from the radio log afterward. Live position and ETA come from FlightAware's AeroAPI on your own key, and a token share link lets a receiving hospital coordinator see the inbound aircraft without a login — replacing the calls they'd otherwise make. Crew type ratings and qualifications, including NVG currency, live on the credentials vault with expiry alerts, so a lapsing specialty currency surfaces before it benches a crew member.

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

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.