Operating a fleet with two or more aircraft types is not uncommon across Southeast Asia, Africa, and the Pacific. Regional airlines, corporate flight departments, and government aviation units routinely manage combinations — a turboprop alongside a narrowbody jet, or a legacy type alongside a modern glass-cockpit variant. On the ground, those combinations create significant administrative complexity. In the air, they create compliance obligations that multiply with every airframe.
The question most operators reach too late is a simple one: does the Continuing Airworthiness Management Organisation software currently in use actually support a mixed fleet — or has it simply been stretched to accommodate one?
This piece examines the specific capabilities that CAMO software must demonstrate when the fleet includes more than one aircraft type. These are not aspirational features. They are the baseline requirements for lawful, efficient, and auditable airworthiness management across a diverse fleet.
Why Mixed Fleets Expose Software Limitations Faster
Single-type operators encounter the limitations of inadequate software slowly. A team managing one aircraft type can develop workarounds, spreadsheet supplements, and manual cross-referencing routines that mask underlying system gaps for months or years.
Mixed-fleet operators do not have that luxury. When a Maintenance Programme Review becomes due simultaneously for two aircraft types operating under different regulatory approvals, or when an Airworthiness Directive applies to one engine variant but not another on the same platform, manual workarounds collapse quickly. The documentation requirements are different. The threshold calculations are different. The approval chains are different.
Software that was built around single-type assumptions will surface those assumptions at the worst possible moment — usually during an audit or an AOG event.
What Multi-Type Programme Management Actually Means
The Maintenance Programme is the operational core of any CAMO function. For a mixed fleet, the software must be capable of holding, managing, and independently executing distinct Maintenance Programmes for each aircraft type — not variations of a single template.
Each Maintenance Programme carries its own task library, its own interval logic, its own MPD or CMR references, and its own amendment history. When regulators or the Type Certificate Holder issue revisions, those revisions must be traceable to the specific programme version they affect, and the software must support controlled updates that do not inadvertently alter programme data for other types in the fleet.
Operators should verify during software evaluation that the system creates genuine programme separation — distinct configuration sets, version histories, and approval records per type — rather than a tagging or filtering approach that sits on top of a shared programme structure.
Variant-Specific AD and SB Applicability
Why Applicability Logic Is Non-Negotiable
Airworthiness Directives and Service Bulletins are rarely fleet-wide in their applicability. A directive may apply to aircraft manufactured before a certain date, to those fitted with a specific engine serial-number range, or to airframes that received a particular modification embodied at service. Across a mixed fleet, the applicability matrix becomes substantial.
CAMO software must be capable of resolving AD applicability at the individual airframe level, not at the type level. This means the system holds enough configuration data per aircraft — build standard, modification status, installed equipment, and part numbers — to correctly determine whether a given directive applies, is already embodied, or is not applicable.
Managing Repetitive Thresholds Across Types
Repetitive ADs require the system to track initial compliance, calculate the next-due threshold based on the specific aircraft’s operational parameters, and flag the item against the operator’s planning horizon. Where two aircraft types carry ADs with similar subject matter but different threshold structures, the software must handle each independently without cross-contamination of interval logic.
Operators evaluating systems should ask specifically how the software handles superseding directives — cases where a later AD cancels or amends an earlier one. The system should automatically update applicability records and flag affected aircraft without manual intervention
Cross-Fleet Component Tracking and Part Interchangeability
In mixed fleets, components sometimes move between airframes — either because they are interchangeable by parts manufacturer approval, or because operational necessity drives the transfer. CAMO software must maintain a complete, time-stamped record of every component installation and removal across every aircraft in the fleet, regardless of type.
This tracking has two dimensions. The first is traceability: being able to reconstruct the full service history of a component regardless of how many aircraft it has been installed on. The second is interchangeability management: confirming that a component approved for one aircraft type is actually permissible on another before it moves.
Systems that hold component records at the aircraft level, with no cross-fleet visibility, will create documentation gaps the moment a part transfers between types. The software must treat the component as the primary record holder, with aircraft associations as linked entries rather than standalone records.
Multi-Regulatory Approval Management
A mixed fleet frequently means multiple regulatory environments. An operator may hold approvals under EASA, GCAA, CAAS, or DGCA depending on where aircraft are registered and where the CAMO approval is held. Different types in the fleet may fall under different regulatory frameworks even within a single organisation.
CAMO software must support the maintenance of separate regulatory compliance records per aircraft, including approval references, audit findings, and corrective action histories. Importantly, the system should allow these to be managed independently without the record-keeping for one regulatory environment affecting another.
Organisations planning fleet expansion into new jurisdictions should also confirm that the software is capable of adding regulatory frameworks without requiring a full system reconfiguration or a new software instance.
Scheduling Across Dissimilar Maintenance Intervals
Unified maintenance scheduling across a mixed fleet is one of the most practically demanding capabilities a CAMO system must provide. Each aircraft type carries its own interval structure — calendar limits, flight-hour limits, cycle limits, and combined limits — and the scheduling engine must resolve these independently while surfacing the consolidated picture to planning teams.
The risk in underpowered systems is that planners default to the most conservative interval across the fleet to ensure compliance, accepting unnecessary maintenance costs as the price of simplicity. A properly configured CAMO system eliminates this trade-off by calculating each aircraft’s actual next-due items precisely, allowing efficient scheduling without compliance compromises.
Operators should evaluate whether the system can produce a merged planning view — showing items due across all aircraft types in a single horizon — while retaining type-specific calculation logic underneath.
Audit Trail Integrity Across the Fleet
Regulatory audits of CAMO organisations with mixed fleets are more demanding than single-type audits. Auditors will examine whether the organisation has maintained equivalent standards of documentation and compliance management across all types, and whether the records for each type can be produced independently and completely.
CAMO software must support the generation of type-specific audit packages — complete documentation sets for a single aircraft type extracted from the broader fleet record — without requiring manual collation. Every record entry, approval action, and programme amendment must carry a timestamp, a user reference, and a clear association with the aircraft type it affects.
Organisations that rely on generic document management systems rather than purpose-built CAMO software consistently struggle to produce these packages efficiently. The audit preparation time alone — measured in person-days for a mixed fleet — represents a significant operational cost that purpose-built software should eliminate.
Evaluating CAMO Software for Mixed-Fleet Operations: A Practical Framework
When assessing CAMO software for a mixed-fleet environment, the evaluation should include the following specific questions:
- Does the system maintain genuinely separate Maintenance Programmes per aircraft type, with independent version control and approval records?
- How does the system resolve AD applicability for individual airframes within a type, including variant-specific and modification-dependent applicability?
- Can components be tracked across aircraft types with full installation history visible at the component level?
- Does the system support multiple regulatory approval environments within a single installation?
- Can the scheduling engine produce a consolidated planning view while retaining type-specific interval logic?
- How are superseding directives handled, and is the update process automated or manual?
- Can the system generate type-specific audit packages without manual document collation?
The answers to these questions will reveal more about a system’s suitability for mixed-fleet operations than any feature list or demonstration environment. CAMO software for diverse fleets must be built around the structural complexity of that diversity — not retrofitted to accommodate it.
Managing multiple aircraft types is a permanent feature of aviation operations across growth markets. The organization that manage it well do so because their airworthiness infrastructure — including the software at its centre — was selected with that complexity in mind from the outset.
