A large aircraft programme can seem to advance when its presentations change faster than its asset schedule. Investors need milestones linked to documents and individual aircraft. Contracted, acquired, delivered and available are useful distinctions because each answers a different question. Combining them into a single fleet count conceals the technical, commercial and operating work still required.
Define evidence for each status
A contracted aircraft needs an identified agreement and a statement of outstanding conditions. Acquisition requires evidence that the relevant transaction completed and an explanation of the interest acquired. Delivery concerns the agreed handover and acceptance process. Availability concerns readiness for the intended use with the responsible operator.
These are reporting definitions to be made precise for each project. They should not be assumed to establish an identical legal event across every jurisdiction or transaction structure.
Attach the count to an asset schedule
Use a stable identifier for each aircraft, or identify when an order remains unallocated to a particular airframe. Connect status dates, documents, counterparties and unresolved dependencies. A dashboard should let a reviewer reconcile the headline total without inferring that a signed future delivery agreement means an aircraft is already operational.
The same schedule should explain removals and changes. A proposed substitution, cancelled commitment or delayed acceptance belongs in the record rather than disappearing into a revised aggregate.
Prevent duplicate opportunities
ALFA’s whitepaper documents an acquisition programme comprising 105 training aircraft and a separate package of two Airbus H135 helicopters and one Diamond DA42. It explicitly treats the H145 opportunity file as separate from that combined programme. The materials do not establish that ALFA has purchased or received these aircraft.
Any future consolidated reporting should reconcile those files before adding totals. Different presentations can describe related opportunities without creating additional assets, and an ecosystem narrative does not settle ownership or transaction participation.
Keep operating measures behind the right milestone
Once an aircraft is available, utilisation, maintenance status, interruptions and lease collection can become relevant measures. Define each measure and name the accountable source. An invoice is different from a payment received, just as a planned flying schedule is different from recorded use. Proposed lease revenue should remain separate from realised receipts.
FAA's safety-assurance framework emphasises checking whether controls continue to work through information, analysis and assessment. Applied to project reporting, that suggests a dashboard should surface exceptions and corrective action as well as positive activity.
Make the next decision visible
For each outstanding milestone, show the dependency, responsible party and evidence needed for completion. A report becomes useful when investors can see what would change its status and which assumptions remain provisional. ALFA's whitepaper calls for precisely this separation of aircraft stages. Following it would support clearer communication without turning proposal values, partner operating history or source-reported opportunities into ALFA-owned assets or token-holder rights.
