Project developers often ask whether a carbon project can "sell into CORSIA". The better question is whether the project can produce units that satisfy CORSIA eligibility at the point an airline needs to cancel them.

That depends on the standard, methodology, crediting-period start, vintage, country, authorisation status, monitoring quality and buyer documentation. If any of those pieces is wrong, the project may still issue voluntary carbon credits but miss the aviation compliance market.

Step 1: choose a route that can plausibly qualify

Start with ICAO's current eligible-unit tables and programme decisions. Then work backwards to the project route. If the likely programme, methodology or activity type is outside the approved CORSIA scope, do not model CORSIA revenue as the base case.

This is especially important for project types where programme restrictions are narrow. Some carbon removal routes, REDD+ approaches or clean-cooking methodologies may have eligibility conditions that are more specific than the headline registry name suggests.

Step 2: check country and authorisation risk early

CORSIA eligibility increasingly depends on host-country authorisation and protection against double claiming. Developers need to understand whether the host country has a process for letters of authorisation, whether it is willing to authorise the project type, and what timeline is realistic.

If the host-country process is immature, that does not necessarily kill the project. But it should change the sales strategy. You may need to treat CORSIA as upside, not guaranteed revenue.

Step 3: design monitoring for airline diligence

Airline buyers and intermediaries will expect more than a registry issuance record. They will ask for clear documentation on vintage, authorisation, safeguards, methodology version, verification, cancellation and claim language. Weak data management makes a project harder to sell even if the credit is technically eligible.

Step 4: structure sales around eligibility uncertainty

If you sign an offtake for future CORSIA units, the contract needs to say what happens if eligibility is delayed, partially achieved or not achieved. Developers should avoid promising unconditional delivery of CORSIA-ready units before programme scope, host-country authorisation and issuance timing are clear.

A more balanced agreement may use staged pricing, eligibility conditions, replacement limits, or separate voluntary and CORSIA delivery tranches.

Live tool
Methodology Selector
Use this to narrow project route, registry fit and commercial assumptions before building a buyer pack.

Developer checklist before pitching CORSIA

For early-stage projects, keep CORSIA upside separate from the base feasibility case until authorisation and eligibility are materially clearer.

Open the feasibility workflow →

Useful official references

Build a CORSIA-ready buyer case

Screen standard fit, feasibility and pricing assumptions before claiming aviation compliance demand.

Open Methodology Selector →