Carbon-Accounted Per-Flight
GHG Protocol Scope 1/2 Per-Flight Ledger
As regulatory and customer pressure grows for scope-specific carbon accounting in aviation operations, drone fleet operators need per-flight CO2 records that are transparent, reproducible, and aligned to an accepted accounting standard. The CAPFL engine (M227) computes deterministic per-flight CO2 from energy consumed and IEA grid intensity factors, tracks battery wear fraction, and issues carbon credit suitability certificates for qualifying missions — without operating as a carbon credit broker.
Capability specification
- 01
Deterministic CO2 computation: energy_kwh × grid_intensity_g_per_kwh / 1000 (GHG Protocol Scope 2)
- 02
IEA country grid intensity factor registry: global_baseline 450, EU 230, Türkiye 380 g/kWh seed profiles
- 03
Battery wear fraction tracking clamped to [0, 1]
- 04
Carbon credit suitability certificate: four-condition AND-gate (CO2, wear, class, mission type)
- 05
Defense, search-rescue, training, and other missions explicitly excluded from credit suitability
- 06
56-test green suite covering CO2 math boundaries, wear clamping, and suitability AND-gate
How it works
Flight Energy Submission
Post-flight energy consumption (kWh) is submitted with mission class, payload weight, and the applicable IEA grid intensity profile. Payload weight zero or below produces no intensity_per_kg_km output — the engine does not fabricate this value.
CO2 and Wear Computation
CO2 is computed deterministically from energy and grid intensity. Battery wear fraction is computed and clamped to [0, 1]. Both values are written to the chain-hashed per-flight ledger record.
Suitability Certificate
A credit suitability assessment applies a four-condition AND-gate: CO2 below threshold, wear below 0.30, mission class in {delivery/inspection/agriculture/mapping}. Missions that do not meet all four conditions receive a non-suitable certificate — the engine does not suppress or adjust the result.
Standards we follow
- STD-01
GHG Protocol Scope 1 and Scope 2 — Greenhouse Gas Accounting Standard
- STD-02
IEA World Energy Statistics — grid intensity reference values
- STD-03
NIST FIPS 180-4 — Secure Hash Standard (ledger chain hash)
Areas served
This capability is deployed across 14 operational regions. Regulatory alignment details vary by jurisdiction — consult engineering for jurisdiction-specific deployment guidance.
Frequently asked questions
Does the platform sell carbon credits or operate as a carbon offset registry?
No. The CAPFL engine produces structured per-flight CO2 ledger records and carbon credit suitability certificates. Interacting with a carbon offset registry — submitting credits, receiving credit units, facilitating trades — is outside the platform's scope. That is the territory of specialist offset registries operating under jurisdiction-specific regulatory frameworks.
Why are defense and search-rescue missions excluded from carbon credit suitability?
Carbon credit programmes typically require that qualifying activities be additional — meaning they represent deliberate, voluntary emission reduction efforts. Defense, search-rescue, and training missions are undertaken for mission-critical or legally mandated purposes, not primarily for emission reduction. Including them would misrepresent the nature of the activity to a credit registry.
Talk to engineering
For capability evaluation, integration guidance, and deployment scoping, submit a brief to the engineering team.
Submit engineering brief