AeroSphere — Implementation Roadmap

The integrated programme Gantt, the critical milestones, the critical dependencies and sequencing and the work-package schedule and critical path across the phased build.

AeroSphere Business PlanSection 12 › Implementation Roadmap

Section 12 · Business Plan

Implementation Roadmap

The integrated programme Gantt, the critical milestones, the critical dependencies and sequencing and the work-package schedule and critical path across the phased build.

The development programme is structured into four sequenced phases
over approximately 48 months, designed so that revenue-generating
operations begin in Phase 1 and build steadily as later phases are
commissioned. The integrated Gantt chart below sets out the critical
milestones, timelines and dependencies.

11.1 Integrated Programme Gantt

Figure 11.1
Figure 11.1 — Integrated implementation Gantt (Months 0–48), showing phases, work-streams, dependencies and critical milestones.

11.2 Critical Milestones

Milestone Target month Dependency Significance
Financial close Month 9 Approvals + funding Unlocks construction
Runway & apron complete Month 18 Earthworks, civils Enables flight operations
Passenger terminal open Month 21 Terminal build, systems First passenger revenue
Cargo precinct live Month 30 Warehousing, customs Cargo & cold-chain revenue
FBO / MRO operational Month 30 Hangars, certification Premium services revenue
Aerotropolis Phase 1 Month 42 Anchor tenants Property income at scale
Steady-state operations Month 48 All phases ramped Full cash generation

11.3 Critical Dependencies & Sequencing

The programme’s critical path runs through regulatory approvals and
financial close (Phase 0), the runway and terminal (Phase 1), and
anchor-tenant commitments (Phases 2 and 3). Key dependencies are managed
as follows:

  • Approvals before capital: environmental and
    aviation approvals are secured before major civil works commence,
    de-risking the largest capital tranche.
  • Revenue before completion: the passenger
    terminal opens in Month 21, generating revenue while later phases are
    still under construction.
  • Anchors before speculative build: cargo and
    property development proceeds on the back of committed anchor tenancy,
    limiting vacancy risk.
  • Parallel work-streams: operations on-boarding
    and route development run concurrently with construction to compress
    time-to-revenue.

11.4 Work-Package Schedule & Critical Path

The table below decomposes the programme into its principal work
packages, showing duration, logical predecessors and schedule float.
Packages with zero float lie on the critical path and receive priority
management attention, contingency and reporting.

Work package Months Duration Predecessor Float
WP1 — Approvals & financial close 0–9 9 mo 0 (critical)
WP2 — Bulk earthworks & services 6–14 8 mo WP1 (part) 0 (critical)
WP3 — Runway, taxiway & apron 10–18 8 mo WP2 0 (critical)
WP4 — Passenger terminal & systems 11–21 10 mo WP2 0 (critical)
WP5 — Airfield certification 18–21 3 mo WP3 1 mo
WP6 — Cargo precinct & cold chain 20–30 10 mo WP3, WP4 2 mo
WP7 — FBO / MRO hangars 20–30 10 mo WP3 3 mo
WP8 — Aerotropolis Phase 1 (property) 28–42 14 mo WP4, anchors 4 mo
WP9 — Ramp-up to steady state 21–48 27 mo WP4 onward n/a (continuous)
Schedule risk management

The critical path runs WP1 → WP2 → WP3/WP4 to first passenger
revenue in Month 21. A ~10% construction contingency and float on
non-critical packages provide schedule resilience; gated capital release
ties each tranche to completion of its predecessor
package.

Confidential — this business plan is provided to prospective investors and lenders for evaluation purposes only and may not be reproduced or distributed without the written consent of AeroSphere Gateway Holdings (Pty) Ltd.