Let's locate your record on the SACAA register.
FlightDocket is mission governance infrastructure for SACAA Part 101 UASOC holders, with Part 108 specific-category support through a JARUS SORA v2.5 assessment layer included in every tier. Onboarding begins with verification against the SACAA register. Enter your certificate number together with your registered email or CIPC company registration number so we can locate your record. Your registered SACAA contact address will receive an authorisation request — no data is disclosed until the onboarding is approved from that address.
Certificate details
Certificate number is required. Provide at least one of the two matching identifiers below.
ROC-00123 (current),
ROC-00124 (current),
ROC-00125 (revoked). Click below to pre-fill a working combination.
Authorisation received. Review and correct as needed.
The accountable manager on your SACAA record has authorised this onboarding. We have pre-populated the fields below from the register. Your record, your changes — edit anything that is out of date and your corrections are written into the tenant record at subscription. The platform records; the operator owns.
Entity
Accountable manager
Operating address
Declared fleet
Your subscription, sized to your operation.
Tell us about your typical month. The advisor picks the smallest tier that covers your baseline workload, and shows how rollover, advance credits, and self-service top-up packs absorb seasonal peaks — so you pay for governance infrastructure, not for headroom you don't use.
Every tier runs on the same mission governance platform. Tiers scale the active fleet and the monthly mission credit pool. Mission credit rates are flat — BVLOS, night operations, controlled airspace, and restricted-area work do not attract uplifts.
Indicative pricing. Tier structure is locked; final pricing is confirmed at general availability and subject to the FlightDocket service agreement.
Mission, Programme, Sortie — SACAA-aligned definitions.
These definitions align with CAR Part 101 (25th and 26th Amendment, 2023) and the TGM Part 101 Operations Manual (26 August 2025). Authoritative platform source: C-05 Mission Pipeline §§3.1-3.2 and §11.3, and C-06 Field Execution Amendment A1 (2026-04-08). The classification follows one Part 101 principle: SACAA approval is granted at the operation level, not the individual flight level. Record-keeping applies to every flight; approval applies to the operation that authorises those flights. Green markers denote single-mission family, blue markers denote programme family.
- Mission 20 MC · single flight event
- A single authorised flight event at one specific location, within a fixed time window measured in hours (not days). All flight parameters, land-access permissions, airspace data, weather, and the hazard profile are captured, validated, and approved through the full MAAR pipeline before the mission may fly. The result is a sealed operational record for that one mission.
- Micromission No charge · continuation inside a mission
- A battery change or short continuation flight inside an already-authorised mission's approved time window, at the same location, under the same authority. A micromission does not open a new approval cycle — it is a subordinate execution record against the parent mission, capturing the reality of flying more than one battery within a single approved window. Micromissions carry no mission credit charge — battery swaps inside an approved flight window are part of normal operations, not a billable event.
- Programme 30 MC header · multi-month envelope
- A parent operational envelope covering a defined location, mission type and subtype, access permissions, and hazard profile, valid for an extended duration — typically 1, 3, or 6 months, or a custom window. All parameters and supporting data are captured, validated, and approved once at programme level. Within the approved envelope, individual sorties are flown without resubmitting the same information. The programme header is charged as a single MC record when the programme is established.
- Sortie 10 MC · flight event inside a programme
- A single authorised flight event within an approved programme. A sortie inherits the programme's location boundary, access permissions, mission type/subtype, and hazard profile. It adds a specific time window (hours, not days), the assigned aircraft, and the assigned Pilot in Command. The platform revalidates against live weather, airspace status, and credential currency — the underlying operational authority comes from the parent programme.
- Microsortie No charge · continuation inside a sortie
- A battery change or short continuation flight inside an already-authorised sortie's approved time window, at the same location, under the same authority. A microsortie does not open a new approval cycle — it is a subordinate execution record against the parent sortie, capturing the reality of flying more than one battery within a single approved window. Microsorties carry no mission credit charge — battery swaps inside an approved flight window are part of normal operations, not a billable event.
This is how your workload sits against the recommended tier's monthly pool. The chart shows pool fit month by month; the panel below tells you how many months need pool, rollover, advance, or top-up packs.
Mission credits are flat — complexity never changes the rate. BVLOS, night, controlled airspace, and restricted operations consume the same MC as VLOS daytime work. Single 20 MC · Programme header 30 MC · Sortie 10 MC, all at R10/MC. Micromission and microsortie continuations are free — battery swaps inside an approved flight window carry no charge. Your monthly pool is included in the fixed subscription fee — only overflow beyond the pool creates extra billing, via cheap top-up packs. Source: C-14 v2 §2.1, §6.2, §6.4.
Once you are active on the platform, FlightDocket continuously tracks your three-month rolling MC consumption and recommends an upgrade or downgrade the moment your operation changes. You do not have to get this right on day one — the platform adjusts with you. Downgrades are recommended as readily as upgrades.
Annual escalation (planned): fixed subscription fee and MC rates are planned to escalate at CPI + 2% on contract anniversary from year 2 onwards with 60 days written notice. Year 1 is locked at launch rates. Operational quality is rewarded: quality operators progress through four trust levels — Assisted, Supervised, Delegated, Trusted — unlocking faster SLA, wider auto-approval of sorties, and higher queue priority. No surcharges apply. Trust is a recognition mechanism, not a penalty mechanism. All tenants start at Assisted. Excess assets: aircraft or PICs beyond the tier cap bill monthly at a tier-dependent rate, self-service, pro-rata, always shown before confirmation. SLA by trust level: SLA coverage is earned through demonstrated operational discipline, not purchased. Assisted tier (all new tenants) does not carry an SLA. Rejection and cancellation: platform-caused rejections refund 100% MC; tenant-error rejections refund 70%; NOTAM-forced cancellation notified within two hours refunds 100%.
Ready to subscribe.
Payment completes the onboarding. Once the payment gateway confirms, your tenant is provisioned automatically: platform access opens, user accounts are created, and the accountable manager receives a welcome email with the console URL and first-login credentials. The operational record starts from your first mission.
Bundle summary
This is the subscription configuration that will be submitted to the payment gateway when you proceed.
/v1/payment/checkout