Arns Innovations
Prepared for Delta Air Lines leadership • Airport Carbon Supply Architecture for SAF
Executive decision
Prepared for Delta Air Lines leadership · Prepared by Arns Innovations
Delta Air Lines logo
Prepared for Delta Air Lines

The decision: architect one airport carbon node.

Delta is not being asked to buy equipment, select a capture vendor, fund a speculative fuel plant, or commit to a new operating company.

Delta is being asked to authorize Arns Innovations to lead a bounded 90-day Airport Carbon Supply Architecture mandate for one Delta-selected hub, so the full airport carbon stack can be mapped, ranked, and translated into a decision-grade SAF and carbon-recycling pathway.

Mandate
90 days

One bounded architecture sprint before vendor selection, capital commitment, fuel-pathway lock-in, or operating-vehicle formation.

Site boundary
One hub

Delta selects the first airport environment. Arns maps the source stack, rights logic, partner interfaces, MRV, and go / no-go path.

Output
Go / no-go

Delta receives a decision-grade source-ranking model, partner stack, rights framework, and next-step recommendation.

What changes
Architecture first
Delta stays in the owner-side position while technical, commercial, legal, and operating options are clarified.
What gets ranked
Full stack
Terminal airflow, central utility plants, CHP, boilers, backup generation, utilities, parcels, and regional sources are screened together.
What is avoided
Premature lock-in
The mandate avoids committing Delta too early to one vendor, one conversion route, one fuel producer, or one capital structure.
Strategic result
Airport standard
The goal is a repeatable airport-linked carbon supply architecture Delta can help define before the market matures.
The regroup decision is simple: authorize one structured architecture mandate, not a technology purchase.
Executive reading path

The first five pages are the executive case. The remaining pages are technical and commercial support.

This deck is intentionally structured so Delta leadership can understand the decision in five pages, then use the rest of the deck to pressure-test the math, source hierarchy, integration hurdles, rights logic, pathway selection, and final 90-day mandate.

How to read it
Pages 1–5 are the leadership pitch. Pages 6–19 are the diligence appendix. The entire deck is written so the decision remains architecture-first, Delta-controlled, and non-binding until the source data supports advancement.
Why Delta / why now

Delta is not just a customer for SAF. Delta can help define how airports participate in SAF feedstock formation.

The best first partner is not merely the airline that wants cleaner fuel. It is the airline with hub density, operational credibility, fuel exposure, airport relationships, public visibility, and the strategic need to turn future SAF supply into a repeatable infrastructure pathway.

Network logic
Hub density
A first hub can become a comparable template across Atlanta, Salt Lake City, Detroit, Minneapolis, Los Angeles, Seattle, and other strategic nodes.
Demand logic
SAF scarcity
Delta’s long-term challenge is not only buying SAF. It is helping create credible, traceable, and localizable supply pathways.
Airport logic
Fuel adjacency
Airports already connect airflow, stacks, utilities, thermal systems, land, safety systems, fuel farms, and airline operations.
Leadership logic
Standard-setting
A Delta-led architecture can become a reference pathway for airport carbon nodes rather than a one-off sustainability demonstration.
What Delta controls

Demand, credibility, and hub selection

Delta can choose the first operating environment, convene the right internal functions, and evaluate whether airport carbon supply deserves pre-FEED, pilot, partner diligence, or no-go status.

What the mandate protects

Optionality before commitment

The work clarifies the pathway before Delta is locked into one vendor, one e-fuel route, one project developer, one operating company, or one capital stack.

For Delta, the strategic value is not one device. It is the chance to help define the airport carbon-node standard before SAF feedstock infrastructure is fully formed.
The airport carbon stack

Start with the full airport carbon stack, not HVAC alone.

The strongest architecture treats one airport as a multi-source carbon supply system: terminal airflow is the visible aviation-facing layer, while CHP, boilers, central utility plant exhaust, backup generation, and regional enterprise sources may provide the first higher-density screening lanes.

1

Dense stack sources

CHP, cogeneration, boilers, central utility plants, backup generation, turbines, and fuel-cell exhaust where present. These sources may provide the first bankable CO₂ lanes because concentration and continuity can exceed terminal airflow.

2

Visible airport airflow

Terminal return air, exhaust air, mixed air, and AHU interfaces preserve the aviation-facing narrative. HVAC is strategically valuable even when it is not the highest-volume first capture lane.

3

Utility and siting interfaces

Thermal loops, parcels, rooftops, mechanical rooms, fuel farms, logistics corridors, and safety boundaries determine whether capture, purification, compression, and routing can be integrated.

4

Regional enterprise aggregation

Hotels, campuses, warehouses, grocery distribution, cold chain, stadiums, retail, and foodservice assets can later expand the airport proof into a regional carbon supply corridor.

5

Rights and MRV layer

The value is not only the physical CO₂. It is the right to access, meter, capture, allocate, route, and monetize the carbon stream without double counting or ownership confusion.

6

SAF routing layer

Verified CO₂ must be matched to hydrogen, clean power, e-fuel partners, certification constraints, book-and-claim structures, and offtake demand before it becomes a real fuel pathway.

HVAC makes the story legible. Dense airport energy sources make the first screen credible. Regional enterprise sources make the network scalable. Rights and MRV make it financeable.
Why Arns Innovations

Arns Innovations is the owner-side opportunity architect before this becomes a vendor, capital, or operating-company decision.

Arns Innovations was built to turn fragmented technology, infrastructure, IP, rights, and market demand into decision-ready commercialization pathways. For Delta, Arns is not proposing to sell a capture device or operate a fuel plant. Arns is proposing to architect the pathway first.

Arns mandate

Define the airport carbon supply pathway

  • Inventory and rank terminal airflow, stack sources, utility interfaces, parcels, partner assets, and rights boundaries.
  • Translate complex airport and fuel-system inputs into a bounded Delta leadership decision.
  • Preserve Delta’s optionality before vendor selection, fuel-pathway lock-in, capital deployment, or project-company formation.
  • Coordinate technical, commercial, IP, MRV, SAF, partner, and operating-vehicle logic inside one architecture.
What this is not

Not a premature Carbon Recycling ask

  • Carbon Recycling is not the current decision.
  • A future carbon recycling operating layer becomes relevant only if Delta elects deployment after the architecture proves real.
  • Any future operator, SPV, vendor stack, or development company should follow the approved Arns architecture rather than lead the proposal.
  • The immediate ask is an Arns Innovations architecture mandate.
Role
Architect
Define the decision path before the market tries to reduce the opportunity to one machine or one vendor.
Control layer
Rights
Clarify access, metering, allocation, environmental attributes, and commercialization control before deployment.
Partner layer
Stack
Map capture vendors, e-fuel partners, airport stakeholders, hydrogen sources, and SAF offtake interfaces.
Output
Decision
Give Delta a clear go / no-go pathway, not another open-ended concept discussion.
The current Delta decision is an Arns Innovations architecture mandate. Carbon Recycling becomes relevant only if Delta elects deployment after the pathway proves real.
Strategic thesis

Airport-native carbon-to-SAF becomes credible when Delta evaluates one hub as a complete carbon supply system.

The thesis is not that terminal airflow alone fuels aviation. The thesis is that airport-controlled airflow, dense energy-system CO₂, utility interfaces, carbon supply rights, and regional enterprise sources can be ranked and assembled into a staged SAF-feedstock architecture.

Narrative layer

Airflow remains the visible airport-facing story

  • The terminal is not the refinery. The terminal is one carbon front end.
  • Airport systems already move, condition, meter, and control large volumes of air.
  • The public-facing logic remains intuitive: airport air and airport energy can become part of future fuel formation.
  • Delta keeps the story understandable without overclaiming the volume from airflow alone.
Credibility layer

Denser airport sources strengthen the first screen

  • CHP, boilers, and central utility plant exhaust may outrank HVAC as the first capture lane where available.
  • Regional partner assets can aggregate with the airport to increase SAF-feedstock scale.
  • Hydrogen, clean power, certification, MRV, and fuel logistics are screened before capital is committed.
  • The result is an airport carbon supply architecture, not an HVAC-only DAC claim.
The Phase 1 objective is to rank one Delta-selected hub as a multi-source airport carbon supply system, beginning with the highest-density CO₂ streams and expanding into airflow and regional sources as the network proves out.
Airport carbon supply architecture

The updated model uses six linked layers so Delta can evaluate one airport as a complete carbon supply system.

The architecture begins with carbon-source inventory and ranking, not with a pre-selected technology bias toward HVAC alone. Capture and conversion remain staged and site-specific.

1

Airport carbon-source inventory

HVAC airflow, CHP, boilers, central utility plants, fuel-cell exhaust, foodservice demand, and nearby corporate assets are mapped into one source inventory.

2

Source ranking + capture-pathway selection

Point-source first where feasible, airflow where strategic and scalable, hybrid capture where the airport carbon stack supports it.

3

Capture + conditioning

Technology-agnostic capture, drying, polishing, compression, storage, quality control, and regeneration interfaces.

4

MRV + carbon accounting

Source-by-source measurement, energy inputs, lifecycle accounting, routing logic, chain of custody, and credit allocation.

5

Regional enterprise aggregation

Airport sources can connect with nearby hotels, campuses, warehouses, retail, stadiums, and other corporate assets where it improves economics.

6

SAF / circular-carbon pathway

Hydrogen, synthesis partner, ASTM-compliant fuel route, fuel logistics, or alternate carbon use where SAF is not yet the best first destination.

01

Inventory

Rank airport carbon streams, not just terminal air loops.

02

Select

Choose dense exhaust first where available, then expand into airflow.

03

Condition

Dry, polish, compress, buffer, and meter the resulting CO₂.

04

Measure

Apply MRV, lifecycle accounting, and allocation logic source by source.

05

Aggregate

Connect airport and regional enterprise sources when scale matters.

06

Route

Send carbon to the best SAF or circular-carbon pathway for that phase.

Source math and equivalence

The model uses both airflow math and stack math. Airports are screened as carbon supply systems, not as HVAC alone.

Ambient-air capture remains important to the story. But public-source airport CHP and boiler data show that dense exhaust streams can materially exceed HVAC airflow as the first capture opportunity at selected hubs.

Airflow model
Annual CO₂ from airflow ≈ CFM × capture factor × uptime × ambient-CO₂ constant

At roughly 420 ppm CO₂, a continuous 1 million CFM stream contains about 11,450 tCO₂/yr at perfect capture, or about 9,730 tCO₂/yr at an 85% capture assumption.

This makes HVAC strategically meaningful while also clarifying why dense stack streams can outrank airflow in Phase 1 when they exist.

CHP screening model
CO₂/yr = MW × 8,760 × capacity factor × 3.412 ÷ electric efficiency × 53.06 kg CO₂/MMBtu

Screening assumptions used here: 85% capacity factor, 40% electric efficiency, 90% capture rate, and EPA’s 53.06 kg CO₂/MMBtu natural-gas emission factor.

This is screening math, not final engineering. Actual values require fuel records, operating hours, heat rate, stack data, and capture design.

HVAC equivalence
1M CFM ≈ 9,730

Approximate captured tCO₂ per year at 85% capture, using the ambient-air planning assumption above.

Existing airport CHP
≈ 510k tCO₂/yr

Approximate captured CO₂ from the 167.7 MW of publicly identified U.S. airport CHP capacity at 90% capture.

Remaining airport CHP potential
≈ 2.95M tCO₂/yr

Approximate captured CO₂ implied by the CHP Alliance’s 973 MW U.S. airport technical-potential figure at 90% capture.

Illustrative public-source airport model
AirportPublic source dataModeled stack CO₂ / yrModeled captured CO₂ / yrHVAC-airflow equivalence at 85%
JFK121.3 MW CHP~408,800 tCO₂~367,900 tCO₂~37.8 million CFM
DTW17.2 MW CHP~58,000 tCO₂~52,200 tCO₂~5.4 million CFM
LAX8.4 to 8.8 MW CHP~28,300 to 29,700 tCO₂~25,500 to 26,700 tCO₂~2.6 to 2.7 million CFM
MIA5.5 MW CHP~18,500 tCO₂~16,700 tCO₂~1.7 million CFM
SNA7.0 MW CHP~23,600 tCO₂~21,200 tCO₂~2.2 million CFM
BDL5.8 MW CHP~19,500 tCO₂~17,600 tCO₂~1.8 million CFM
ROC1.5 MW CHP~5,100 tCO₂~4,600 tCO₂~0.47 million CFM
SMF1.0 MW CHP~3,400 tCO₂~3,000 tCO₂~0.31 million CFM

JFK is also useful because public permit materials show six hot-water generators totaling 315 MMBtu/hr by nameplate, while public annual heat-input tables indicate those boilers are intermittent and much smaller in practice than the airport’s CHP source. ATL provides the opposite lesson: public permit materials show major boiler capacity even without a public CHP proof point.

Integration hurdles

The hardest risks are real, which is why the program must be architected before it is bought.

A credible Delta program leads with the constraints: pressure drop, regeneration heat, airport safety, hydrogen access, land, fuel certification, and economic exposure. These are de-risked by architecture and site evidence, not by optimism.

01 · Air systems

Pressure drop and passenger environment

Capture must be designed around fan power, air quality, comfort, humidity, maintenance access, redundancy, and no degradation of terminal operations.

02 · Regeneration

Thermal service and duty cycle

Sorbent regeneration requires heat or electrical input. The program must define where low-grade heat, electrified thermal loops, or dedicated regeneration skids make sense.

03 · Hydrogen and power

The real economic center of gravity

CO₂ capture creates feedstock. Hydrogen and clean electricity determine whether conversion to SAF is viable at the selected site or should be regionalized.

04 · Airport constraints

Safety, siting, permitting, and fuel logistics

Compression, storage, hydrogen, synthesis, and fuel handling introduce safety and permitting requirements that must be designed with airport, utility, and fuel partners.

05 · Certification

Fuel qualification and blending pathway

The output must map to ASTM-governed pathways and credible fuel partners. A pilot can prove feedstock and architecture before claiming finished-fuel scale.

06 · MRV

Traceable carbon and allocation logic

The system needs measurement, reporting, verification, chain-of-custody, and airline allocation logic from the first data-room phase.

De-risking stance
The first mandate does not purchase equipment. It defines whether a specific airport node has the airflow, energy, parcel, partner, and fuel-pathway conditions to justify equipment selection.
Phased program

A credible Delta pathway begins with architecture, then moves into pre-FEED, pilot, and repeatable standard.

This structure gives Delta useful knowledge at each gate and avoids forcing a capital decision before site data, partner readiness, and economics have been normalized.

Phase 0

Architecture mandate

Define the airport carbon-to-SAF boundary, data request, candidate sites, source-ranking logic, partner stack, rights framework, and initial go / no-go criteria.

Phase 1

Feasibility and pre-FEED

Map AHU and utility data, pressure-drop risks, capture options, parcel constraints, hydrogen access, SAF pathway, MRV, and airport approvals.

Phase 2

Pilot capture system

Install and operate a bounded capture and conditioning node to prove CO₂ output, energy penalty, operating reliability, MRV, and partner interfaces.

Phase 3

Airport standard

Convert the validated configuration into a repeatable hub template for Delta network expansion and airport-sector adoption.

Gate 1

Is the system real?

Validated airflow, capture factor, duty cycle, and operational feasibility.

Gate 2

Is the pathway viable?

Credible CO₂ conditioning, hydrogen, power, conversion, MRV, and fuel logistics.

Gate 3

Is the standard repeatable?

Clear economics, risk allocation, partner model, and hub-sequencing logic.

Technology and economics

The first return is decision quality. The long-term return is a repeatable SAF infrastructure option.

This analysis does not pretend precision before the data room. It defines what can be scoped now, what must be learned on site, and where Delta’s option value compounds.

Economic stack

Value is phased, not overpromised

Near term: decision-quality valueEngineering learning, site evidence, partner alignment, policy leverage, risk mapping, and a clearer Delta position in airport-SAF infrastructure.
Mid term: feedstock and hub valueMeasured CO₂ output, MRV, utility coordination, capture-node replication, and a fuel-partner pathway that can be evaluated against other SAF supply options.
Long term: standard-setting valueA repeatable airport carbon-to-SAF infrastructure method that can scale across Delta hubs and influence airport development globally.
Dominant variables

The dominant variables

  • Fan-power penalty and pressure drop.
  • Sorbent performance, lifetime, and regeneration energy.
  • CO₂ purity, drying, compression, and storage.
  • Clean electricity access and hydrogen production or procurement.
  • Conversion pathway, fuel partner, certification, and blending logistics.
  • MRV and chain-of-custody requirements.
The first Delta decision is the architecture mandate that determines whether the opportunity has a defensible airport-specific path before any formal SOW for later execution is advanced.
Pathway selection

PtL / eSAF is the airport-native route because it uses captured CO₂, hydrogen, and clean power rather than scarce biological feedstocks.

HEFA, ATJ, and biomass / waste FT all matter for near-term SAF supply. But if Delta wants an airport-linked fuel architecture built around captured terminal CO₂, PtL is the pathway that most directly fits the physics of the system.

How the current SAF lanes compare

Each pathway solves a different problem

HEFAMost commercially mature and currently dominant, but limited by fats, oils, and greases and by competition with other sectors for those feedstocks.
Alcohol-to-JetUseful bridge pathway that can leverage alcohol infrastructure, but still depends on alcohol supply, carbon intensity, and conversion economics.
Biomass / waste FTScalable in principle, but heterogeneous feedstocks, aggregation, contamination, and project execution have often been difficult in practice.
PtL / eSAFUses CO₂, hydrogen, and renewable electricity. It removes the biological feedstock ceiling, but replaces it with an economic ceiling driven by power and hydrogen.
Why this architecture points to PtL

The airport capture layer belongs in a CO₂-native fuel system

  • Airport HVAC capture creates a measured CO₂ front end, not a waste-oil or ethanol feedstock stream.
  • Delta can still procure HEFA or ATJ, but those pathways do not require airport airflow to exist.
  • PtL is the only major SAF family whose core inputs directly match the airport-carbon architecture: captured CO₂, clean hydrogen, and low-carbon electricity.
  • The strategic upside is long-term scale without land, crop-yield, or feedstock collection ceilings.
  • The strategic constraint is economics, so the objective is hydrogen efficiency, power discipline, and kerosene yield rather than simply “making e-fuel.”
Bottom line
HEFA and ATJ help Delta buy SAF. PtL / eSAF gives Delta a path to shape future airport-native fuel infrastructure.
PtL route choice

The winning PtL route is the one that maximizes certified kerosene per electron, kilogram of hydrogen, and ton of captured CO₂.

Once Delta chooses PtL as the destination pathway, the next question is not simply whether synthetic fuel can be made. The question is which route minimizes hydrogen waste, minimizes electricity burden, and maximizes ASTM-compatible jet output.

Route 1Combustion RWGS + FT

Technically viable, but least attractive on hydrogen efficiency

  • Consumes hydrogen or methane-derived fuel for heat to drive reverse water-gas shift.
  • Burns valuable hydrogen into water instead of preserving it for jet-fuel output.
  • Creates the weakest economics when hydrogen is the dominant variable.
Route 2Electrified RWGS + FT

Most aligned with a premium airport PtL architecture

  • Replaces combustion heating with electrified RWGS, avoiding direct hydrogen burn.
  • Becomes more attractive when paired with recycle loops, heat integration, and high-value kerosene targeting.
  • Best fit when Delta wants a system optimized around clean power, hydrogen discipline, and certified jet yield.
Route 3Methanol-to-Jet

Important comparator, but watch carbon and hydrogen losses

  • Can look simpler at first because methanol is a familiar intermediate.
  • Carbon losses in methanol-to-olefins upgrading can reduce overall carbon and hydrogen efficiency.
  • Needs to be judged by delivered jet-fuel yield, not by intermediate-product elegance.
Delta screening rule

Route selection criteria

  • ASTM-certified kerosene yield per ton of captured CO₂.
  • Hydrogen efficiency and effective electrolyzer burden.
  • Total electricity intensity after recycle and heat integration.
  • Ability to recycle light ends and avoid non-target product build-up.
  • Partner bankability, operability, and pathway-certification maturity.
Technology diligence note

Use vendor claims as benchmarks, not assumptions

Topsoe argues that an integrated Fischer-Tropsch pathway with electrified RWGS, recycle, and SOEC-linked hydrogen can outperform combustion RWGS and methanol-to-jet on hydrogen and electricity efficiency. That is strategically useful guidance, and those performance figures are best treated as vendor-claimed benchmarks to diligence through independent techno-economic review.

PtL removes the land and feedstock ceiling. The remaining battle is economics, and that is largely a hydrogen-efficiency and electricity-efficiency problem.
Site sequence

The first site is best chosen by carbon-supply strength and authorization readiness, not by symbolism alone.

The screening question is no longer “Which airport has the biggest terminal?” It is “Which airport offers the best mix of dense CO₂ sources, visible aviation-facing airflow, utility readiness, hydrogen access, fuel-logistics fit, and partnerability?”

ATL

Delta’s flagship strategic supply hub

01

Public permit materials indicate major boiler capacity above the 250 MMBtu/hr threshold. Even without a public CHP proof case, ATL is a strong boiler-and-campus screening node.

Best use: Delta’s flagship carbon supply study if the data room confirms boiler, utility, and parcel readiness.

DTW

Delta-relevant CHP proof source

02

Public CHP data point to roughly 17.2 MW of airport CHP, making DTW one of the clearest Delta-hub examples of dense point-source CO₂ already inside an airport context.

Best use: Delta-priority pilot candidate where airport-energy logic and Delta hub relevance align.

JFK

External proof benchmark

03

JFK’s 121.3 MW CHP system is the clearest public proof case that an airport can host material stack CO₂. It is less about Delta-hub primacy and more about proving the model is real.

Best use: benchmark case for source hierarchy, stack capture logic, and utility integration design.

LAX

Utility-plant benchmark

04

LAX combines public CHP references with a major central-utility-plant context, making it useful for utility-system and parcel-integration benchmarking.

Best use: compare airport utility-plant logic against Delta’s own hub options and west-coast partner strategy.

SLC / MSP / SEA

Readiness screen

05

These hubs may still be excellent Phase 1 candidates if utility structure, clean-power access, or airport partnership conditions prove stronger than at more obvious symbolic sites.

Best use: disciplined screening against the carbon-supply criteria, not automatic exclusion.
For Delta, the opening move is to start with the strongest airport carbon supply system, rank the highest-density sources first, and keep HVAC as the visible airport-native expansion layer.
Defensibility

The defensible value is in the system configuration, data model, and repeatable airport method.

For Delta leadership, this proposal is not a consulting memo or a single-device pitch. It is the first expression of a proprietary airport infrastructure method: a way to rank, configure, validate, and commercialize carbon-to-SAF supply architecture across airport assets.

01

Source-ranking logic

Method for ranking HVAC loops, CHP exhaust, boiler flue gas, central utility assets, gates, parcels, and regional partners by SAF-feedstock viability.

02

Airflow-to-carbon model

Standardized normalization of CFM, stack output, capture factor, uptime, pressure drop, regeneration energy, and CO₂ conditioning output.

03

Partner-stack orchestration

Repeatable configuration of airport, airline, utility, capture vendor, hydrogen provider, conversion partner, fuel logistics, and MRV roles.

04

MRV and allocation

Measured chain-of-custody logic for assigning captured carbon, SAF feedstock, credits, airline offtake, and reporting value.

05

Phased deployment gates

Decision architecture that moves from data room to pre-FEED to pilot system to airport standard without premature capital exposure.

06

Repeatable hub template

A transferable method for applying the architecture across Delta hubs and later across airports globally.

The defensible value is not the existence of CO₂ capture. The defensible value is the airport-specific architecture that turns airflow, utilities, hydrogen, fuel logistics, airline demand, and carbon allocation into one repeatable SAF supply pathway.
Commercial architecture

The hidden value is carbon supply rights, allocation, and control — not only capture hardware.

A Delta-led airport carbon supply architecture should define who can measure, route, allocate, claim, and commercialize captured CO₂ before Delta is locked into a vendor, fuel pathway, project developer, or capital structure.

01

Captured CO₂ ownership

Define who controls captured CO₂ at the source, after conditioning, during storage, and after routing.

02

Environmental attributes

Separate physical CO₂ custody from credits, reductions, book-and-claim logic, and sustainability reporting value.

03

SAF-feedstock allocation

Determine how captured airport carbon can be assigned to downstream PtL / eSAF pathways and fuel claims.

04

Delta offtake priority

Preserve Delta’s strategic access to fuel, attributes, data, and first-mover hub replication rights.

05

Airport + utility rights

Clarify airport, utility, landlord, energy-plant, and terminal-system participation before site work begins.

06

MRV chain of custody

Map measurement, reporting, verification, source attribution, energy inputs, and routing logic source by source.

07

Claims boundaries

Define what Delta, the airport, utilities, vendors, and fuel partners can safely claim, report, or market.

08

Regional participation

Set terms for hotels, campuses, warehouses, stadiums, retail, and foodservice sources that may aggregate with the hub.

09

Hub replication rights

Protect the repeatable template so one validated hub can become a Delta network architecture, not a one-off study.

10

Operating-vehicle trigger

Define when a future developer-operator or managed CO₂ services layer becomes useful — after architecture approval.

Arns Innovations is the architecture layer that defines these rights before Delta is locked into a vendor, fuel pathway, developer, or capital deployment.
Operating model

Architecture first. Operating vehicle only after Delta has a decision-grade pathway.

The clean structure keeps Arns Innovations in the architecture role now, while leaving room for a future carbon recycling operating layer, project SPV, vendor stack, or infrastructure partner only if the mandate validates a real deployment path.

Now

Arns Innovations architecture mandate

  • Lead the 90-day airport carbon supply architecture sprint.
  • Map sources, rights, utilities, siting, partner interfaces, MRV, and SAF routing.
  • Keep Delta in control before vendor, capital, project-company, or fuel-pathway decisions.
  • Deliver a bounded go / no-go recommendation and next-step SOW if warranted.
Only if validated

Future deployment layer

  • A carbon recycling operating layer or SPV becomes useful only after Delta approves advancement.
  • That layer could coordinate capture vendors, project finance, site onboarding, MRV, CO₂ aggregation, routing, and recurring operations.
  • The operating layer should be tech-agnostic and rights-aware, not tied to one premature device decision.
  • Delta can evaluate this later with data, not in the regroup conversation.
No premature capital ask

Delta is not being asked to finance the platform now.

The first request is a paid or authorized architecture mandate. Capital questions belong after source data, partner stack, and go / no-go logic are clarified.

No premature vendor lock

Capture vendors should compete inside the architecture.

The mandate defines what each source requires before Delta is asked to pick equipment, developer, conversion route, or operating model.

No premature company diligence

Carbon Recycling is an optional future layer.

The current counterparty for the regroup is Arns Innovations as architecture lead. A future operating layer follows the approved pathway.

The correct sequence is architecture mandate → source and rights validation → pre-FEED or pilot decision → optional operating vehicle.
Decision path

Next step for Delta: authorize a 90-day Airport Carbon Supply Architecture mandate for one Delta-selected hub.

This mandate determines whether terminal HVAC airflow, CHP / boiler / central utility plant exhaust, airport energy infrastructure, nearby enterprise sources, hydrogen supply, carbon allocation rights, and downstream fuel-conversion partners can be structured into a defensible airport-native carbon-to-fuel pathway with a clear go / no-go output. The regroup can begin at the strategy and authorization level; detailed AHU, boiler, CUP, utility, and rights data would only be requested after Delta authorizes the bounded mandate.

01 · Data room

Gather the full airport carbon stack

Secure candidate terminal, AHU, central utility plant, CHP, boiler, turbine, fuel-cell, exhaust-stack, thermal-loop, utility, parcel, airport-partner, rights, and fuel-logistics information.

02 · Source + rights ranking

Rank the best CO₂ streams first

Screen dense stack sources, visible airflow sources, utility interfaces, parcel options, hydrogen access, SAF-partner fit, and carbon supply rights inside one architecture model.

03 · Basis of design

Define the architecture boundary

Produce a site-specific concept basis, capture-pathway logic, preliminary MRV structure, carbon allocation framework, partner map, and phased implementation path without overcommitting to one technology too early.

04 · Go / no-go

Deliver a bounded Delta decision

Provide a clear recommendation on pre-FEED, partner diligence, pilot structuring, operating-vehicle design, or a no-go based on real airport and market conditions.

Authorization language

Authorize Arns Innovations to lead a 90-day Airport Carbon Supply Architecture mandate for one Delta-selected hub. The output is a decision-grade architecture package, source-ranking model, partner stack, rights and allocation framework, and go / no-go recommendation. If Delta elects to proceed, Arns can then prepare a formal SOW for pre-FEED, pilot structuring, partner diligence, and/or operating-vehicle design.