For operating Teams

Prepare the operation with fewer blind spots.

Coordinate assigned people, aircraft, equipment and flight requests in one Team-scoped workspace, then move a complete pack into UASOC review.

Team operations

From assigned resources to a review-ready flight pack.

AirKo links planning to readiness. The request shows what must be resolved, who owns the next action and which version is moving forward.

  1. 01

    Scope

    A workspace bounded to your Team

    Work only with the pilots, aircraft, equipment and operations assigned to your Team. Another Team’s records remain out of view.

  2. 02

    People

    Coordinate readiness without overexposure

    See reviewed operational status and upcoming expiry dates while sensitive medical source documents stay restricted to authorised reviewers.

  3. 03

    Planning

    Build the request from real dependencies

    Match crew, aircraft, payload and equipment to the mission; capture its Job Safety Stage, risk controls, permissions and supporting material.

  4. 04

    Workflow

    Resolve blockers before authorization

    Review the Team submission, respond to returned items and send a controlled flight-pack version forward for UASOC review.

Role clarity

Clear boundaries protect the decision path.

Team control stays meaningful because organisation-wide actions and UASOC authorization do not quietly move into the Team role.

Team creation
A Team manager can manage assigned resources and review submissions, but only the UASOC activates or creates a Team.
Cross-Team access
A Team cannot see another Team’s pilots, aircraft, flight requests or supporting records.
Flight authorization
A Team manager cannot issue a UASOC flight release unless that person has separately been granted the authorised-person role.
Material changes
A material change after authorization invalidates the prior release and creates a new flight-pack version for UASOC review.

Submission path

Know where the request stands.

Returned-for-changes and rejected outcomes remain part of the record. Corrected submissions move forward as controlled versions rather than replacing what was previously reviewed.

01Mission drafted
02Dependencies checked
03Team review
04Changes resolved
05UASOC review
06Decision recorded

See AirKo in context

Walk through a Team operation end to end.

See how a Team assembles a flight request, clears its own blockers and hands a controlled version into UASOC review.

Request a demonstration