Skip to content

For flight dispatch offices

Plan, brief and follow every flight you dispatch.

Feasibility checks before you accept, flight plan records and briefing packs, and live tracking on one board, for dispatch offices supporting several operators' fleets.

Before you accept a trip, Aviagrid checks it against permits, slots, crew duty, airport hours, fuel and handling. Problems surface before the client hears yes, not after.

Sound familiar?

Where the day goes today

  • Feasibility checked too late

    Airport hours or crew duty problems found after the trip is confirmed.

  • Briefings assembled by hand

    Weather, NOTAMs, permits and contacts pasted into a PDF for every leg.

  • Fleets in different systems

    Each operator client sends schedules in its own format.

  • No single view of the day

    Nobody can see every active flight and every open task at once.

Before and after

The same morning, two ways

Drag the handle to compare an inbox-and-spreadsheet desk with the same work on one board.

Scene J · Before and after

On the left, how most trip support desks run today: forwarded email chains, a shared spreadsheet and WhatsApp groups. On the right, the same work on one Aviagrid board. Drag the handle to compare.

  1. Before: unread email threads, a trips spreadsheet with clashing highlighted cells and WhatsApp messages asking who has the permit
  2. After: every trip on one board, grouped by stage, with a clear status on each card
  3. Drag the handle, or use the arrow keys, to move between before and after

A day in the life

A dispatch shift

A Global 6000, N417AG, for a made-up operator, Sandline Air Charter: KTEB to EGLF with a fuel stop at CYYZ planned.

  1. 0400Z

    23:00 EST

    Schedule received

    Sandline's scheduler sends a three-leg request through their client portal.

    Client & supplier portals
  2. 0403Z

    Feasibility check runs

    Permits, slots, crew duty, airport hours, fuel and handling are checked. The EGLF slot shows a warning.

    Flight dispatch & planning
  3. 0410Z

    Slot resolved

    The dispatcher requests a new EGLF slot 30 minutes later. The check turns green.

    Permits & slots
  4. 0420Z

    Trip accepted

    The trip moves to Planning with tasks assigned to the overnight team.

    Live operations board
  5. 1100Z

    06:00 EST

    Briefing pack built

    Weather, NOTAMs, permits and handler contacts assembled into one PDF per leg.

    Flight dispatch & planning
  6. 1400Z

    09:00 EST

    Wheels up

    N417AG departs KTEB. The leg moves to In flight and appears on the map.

    Live operations board
  7. 2050Z

    20:50 BST

    Arrival

    The aircraft blocks in at EGLF. Block times are captured for billing.

    Live operations board

Illustrative example. Companies, people and registrations are made up.

Every active flight on the map

Scene C · Flight map

Every active flight on the map

Every active trip on one live map, drawn as route-cyan arcs with the aircraft moving along them. The next arrival pulses, and a side panel keeps the UTC clock and ETAs in view for the whole desk.

  1. Active trips are drawn as arcs between real airports.
  2. Aircraft move along their routes in near real time.
  3. The next arrival pulses so nobody misses the handover.
  4. The side panel ticks in UTC and lists every ETA.

“Check it before you accept it, brief it without retyping it.”

Aviagrid dispatch principle

See a feasibility check on your own routing

Bring a recent trip and we will run the checks and build the briefing pack with you.

Book a demo