24/7 standby, crew duty, and dispatch for HEMS bases.
Helicopter Emergency Medical Services is a Part 135 specialty with its own base-manning and standby patterns. It runs as a first-class operation on top of the Part 135 platform — crew duty, reserve standby, dispatch, and fatigue risk in one place.
Launching the first quarter of 2027.
Jump to a feature
Tap any chip to jump to its section below.
- 24/7 standby rotation
- Crew duty board
- Fatigue risk board
- Dispatch
- Live tracking + share links
- Crew credentials
+9 more supporting features lower on the page
Inside the Helicopter HEMS workspace
01Standby & crew
24/7 standby rotation
Each base runs a 24/7 standby rotation as LONG_CALL and SHORT_CALL with callout handling, so manning the base around the clock is a live board, not a paper roster. The desk sees who's up and who's been used. It replaces the standby roster taped to the base wall.
Replaces: the standby roster taped to the base wall
- Per-base 24/7 standby rotation
- LONG_CALL / SHORT_CALL with callout handling
- Who's up and who's been used — a live board, not a paper roster
How an operator uses this
A HEMS dispatch shift
A HEMS shift starts with the standby board, not a paper roster — each base's 24/7 rotation shows who's up as LONG_CALL or SHORT_CALL with callout handling, so around-the-clock manning is a live screen. The crew duty board shows rest and duty across the base, so a crew running out of legal duty on a long shift is visible before the next launch.
An inter-facility transfer comes in and gets released on the ops board, so the mission lives in the system instead of only on the radio. A token share link goes to the receiving hospital coordinator, who sees the inbound aircraft's position and ETA without a login — replacing the calls they'd otherwise make.
A crew member's NVG currency is lapsing, flagged on the credentials vault before it benches them, and the fatigue risk view blends documented duty load with self-reported sleep — deterministic and traceable to its inputs, not a black-box prediction. The whole base reads from one screen rather than a roster, a radio log, and a spreadsheet.
Illustrative — every screen reflects what's in your own data, nothing more.
Illustrative — every screen reflects your own data.
02Standby & crew
Crew duty board
A live duty board shows rest and duty status across the base roster, so a crew that's run out of legal duty on a long shift is visible before the next launch. It replaces tracking duty by memory at 0300.
Replaces: tracking duty by memory at 0300
- Live duty/rest status across the base roster
- A crew out of legal duty visible before the next launch
- Replaces tracking duty by memory at 0300
Illustrative — every screen reflects your own data.
03Standby & crew
Fatigue risk board
A fatigue risk view blends documented duty load with crews' self-reported sleep and rest, with every score traceable to its inputs — deterministic and explainable, not a prediction model. On long standby rotations this replaces judging crew fatigue by feel.
- Blends documented duty load with self-reported sleep
- Every score traceable to its inputs
- Deterministic and explainable — not a prediction model
Illustrative — every screen reflects your own data.
04Dispatch & 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.
Replaces: reconstructing the mission timeline from the radio log afterward
- 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
Illustrative — every screen reflects your own data.
06Dispatch & tracking
Crew credentials
Type ratings and qualifications — including NVG currency — live on the credentials vault with expiry alerts, so a lapsing qualification surfaces before it benches a crew member. It replaces tracking specialty currencies on a side list.
Replaces: tracking specialty currencies on a side list
- Type ratings and qualifications, including NVG currency
- On the credentials vault with expiry alerts
- A lapsing qualification surfaces before it benches a crew member
Illustrative — every screen reflects your own data.
In every operation
The platform backbone, under every Part
The platform-wide backbone — the same under every FAR Part.
Auto-fills from completed flights, manual entry, and ForeFlight CSV import/export.
Certificates, ratings, medicals, and type ratings with auto-expiry alerts and document storage.
Priority/status/assignee work orders, parts with reorder thresholds, vendors, and purchase orders.
Every requirement on a Compliant → Due-Soon → Overdue timeline with a weekly admin digest.
Utilization, currency, and activity KPIs with CSV export.
Every mutation recorded with actor, entity, and timestamp — searchable and exportable.
Read-only links for FAA/POI/external auditors that expire automatically — no shared logins.
Bearer-token REST API (scoped) and HMAC-signed outbound webhooks for HRIS, ERP, and ops integrations.
Tenant isolation, role-based access, per-employee surface restrictions, TOTP 2FA, and GDPR data export/erasure.
Today
What's slowing you down
- 24/7 base manning on a paper roster
- Mission timeline reconstructed from the radio log
- Crew fatigue on long standby rotations tracked by feel
With AviationAlley
What changes
- Per-base standby rotation with callout tracking
- Dispatch and live tracking with hospital-coordinator share links
- Fatigue risk surfaced from duty load and self-reports
Why operators switch
What we have. What incumbents don't.
| AviationAlley | Status quo |
|---|---|
| HEMS standby on one platform with Part 135 ops | Separate roster, radio log, and spreadsheet |
| Hospital-coordinator live-tracking share links | Phone calls for position and ETA |
Recommended for Helicopter HEMS (Part 135)
Enterprise plan
Unlimited seats · priced to your fleet
Every module — Part 121 pilot bidding, AQP, multi-base. For regional carriers and multi-center training networks.
- All operation modules
- Full PBS with the contract rule library
- Multi-base + AQP
- Per-center white-label
- Dedicated customer success manager
Frequently asked questions
Helicopter HEMS (Part 135) — common questions
Is HEMS its own product or part of Part 135?+
It's a Part 135 specialization. You get the full Part 135 platform — dispatch, crew currency, billing, MEL — plus the HEMS base-standby rotation, crew duty, and fatigue surfaces, all in one operation rather than a separate tool.
Can a receiving hospital see the flight position?+
Yes. Generate a token share link and the hospital coordinator sees live position and ETA without a login or an account. Live tracking uses FlightAware's AeroAPI with your own key.
How is 24/7 base standby managed?+
Each base runs a 24/7 standby rotation as LONG_CALL and SHORT_CALL with callout tracking, paired with a live duty board and a fatigue risk view — so around-the-clock manning and crew rest are visible on one screen instead of a paper roster.
Built for Helicopter HEMS (Part 135).
See it on your operation. Request a demo or join the waitlist.