What Is an Approved Maintenance Programme?
The Approved Maintenance Programme (AMP) is the regulatory document that defines every scheduled maintenance task, every interval, every check — for every aircraft in your fleet.
It is the legal basis for all scheduled maintenance. Everything that happens on a maintenance line — every component replacement, every inspection interval, every airworthiness review — is traceable back to the AMP. If the AMP is wrong, the maintenance is wrong. If the AMP revision is not approved, the tasks derived from it are not compliant.
This is not a supporting document. It is the foundation of your operation’s airworthiness.
Why Does the AMP Matter More Than Most Operators Recognise?
Because it is the document a regulator checks first when something goes wrong.
An airworthiness finding — a missed inspection, a task performed at the wrong interval — traces back to the AMP. Was the task specified correctly? Was the revision in force at the time of the maintenance event? Was the AMP revision approved before the task was scheduled?
If the CAMO Manager cannot answer these questions instantly, from the system, with a full audit trail — the finding becomes a systemic issue, not an isolated error.
The AMP is also dynamic. AD compliance may require an AMP revision. Component changes may trigger interval updates. Every change to the programme must be documented, approved, and cascaded to the affected task schedule — in the right sequence, with the right evidence.
How Are Most Operators Managing the AMP Today?
The honest answer is: manually. And the manual approach creates systematic risk.
At most operators, the AMP lives in a Word document on a shared drive. Revisions are tracked with file naming conventions: “AMP_v12_final.docx” → “AMP_v12_final_FINAL.docx” → “AMP_v13_approved_USE THIS.docx.”
Revision history exists in an email thread. Regulatory approval is tracked on a spreadsheet — or remembered by the CAMO Manager. The link between an AD and the AMP revision it triggered is noted in someone’s inbox.
When the regulator asks to see the current approved AMP with its full revision history, somebody spends two days assembling documents from scattered sources. When an audit finding identifies a task performed against a superseded revision, the CAMO team cannot immediately demonstrate why — because the link between the approved AMP version and the task schedule was never documented in the system.
This is not negligence. It is the predictable result of using document management tools for a live, dynamic compliance process.
What Are the Different Approaches to AMP Management?
Manual Management — Word Docs and Shared Drives
The current state for most operators. Version control is manual. Regulatory approval is tracked separately. The link between the AMP and the maintenance planning system is re-entered manually when intervals change. Audit readiness requires manual document assembly.
Document Management Systems
A step up from shared drives — platforms like SharePoint, Confluence, or dedicated document management software. Version control improves. Access controls are cleaner. But the fundamental problem remains: the AMP is still a document, not a live operational tool. It is still disconnected from the maintenance planning system. When an interval changes in the AMP, someone still has to update the task schedule manually.
Integrated CAMO Platform
The AMP is not managed as a document — it is managed as the engine that drives maintenance planning. Changes to the programme flow automatically into task scheduling. Regulatory approval is tracked within the platform. The link between an AD and the resulting AMP revision is documented at source. Management can see pending revisions, outstanding approvals, and tasks being executed against the current approved revision — in real time, on a dashboard.
This is the AircraftCloud model.
Manual AMP Management vs. Integrated Platform: The Comparison
Criteria | Current State (Manual) | AircraftCloud Platform |
Version control | Manual file naming | Automatic revision tracking |
Regulatory approval tracking | Email threads / spreadsheet | Built-in approval workflow with status visibility |
Link to maintenance planning | Manual re-entry of task intervals | Automatic cascade to scheduled tasks |
AD/SB-driven AMP revisions | Manual cross-reference | Linked: AD triggers AMP revision workflow |
Management visibility | None until someone compiles a report | Dashboard: pending revisions, approval status, live |
Audit readiness | 2+ days assembling documents | Instant: full revision history with approval trail |
What Are the Benefits of Integrated AMP Management?
Automatic cascade to task scheduling. When an AMP revision is approved in AircraftCloud, the updated intervals flow directly into the maintenance planning module. No re-entry. No risk of discrepancy between the approved programme and the live task schedule.
AD-triggered revision workflows. When an AD requires an AMP revision, the link is created in the platform — not reconstructed from email threads six months later during an audit. The workflow guides the revision, tracks the regulatory submission, and confirms approval before affected tasks are scheduled.
Real-time management visibility. The CAMO Manager’s dashboard shows pending AMP revisions, outstanding regulatory approvals, and the revision status of every scheduled task. Not in the next weekly report. Now.
Audit readiness that takes seconds, not days. The full revision history — every version, every approval, every change note — is in the platform. When the regulator asks, the CAMO Manager opens the screen. No document assembly required.
What Are the Benefits of Going Cloud-Native From Day One?
The cost of a wrong software decision at the startup stage is not just financial — it is operational and regulatory.
- AOC delay. A system that isn’t functioning during the regulator’s audit will delay approval. Every month of delay is a month of revenue lost.
- Compliance risk. A system that isn’t integrated with the maintenance programme means manual cross-referencing — and manual cross-referencing creates gaps that auditors find.
- Migration cost. Switching systems 18 months into operation means data migration, retraining, and a period of compliance risk. It is significantly more expensive than choosing correctly at the start.
The selection decision a startup airline makes before its first aircraft arrives shapes its compliance posture and operational capability for years.
What Are the Risks of Staying With Manual AMP Management?
The risks are not theoretical. They are the documented failure modes of CAMO operations that rely on document management for a live compliance process.
- A version of the AMP in use at the maintenance line is not the approved version. Nobody caught it because version control is a file-naming convention.
- An AD required an AMP revision within 30 days. The revision was submitted on day 28. Regulatory approval was not tracked. The approval came back on day 45, and tasks were scheduled before approval was confirmed.
- At the next audit, the regulator asks for a complete revision history. The CAMO team produces it after two days of document recovery. The regulator notes the gap.
These are not edge cases. They are the predictable outcomes of using the wrong tools for a compliance-critical process.
What Is the Best Approach for CAMO Teams?
The AMP is not a document. It is an operational tool. Managing it as a document — in a folder, with version numbers in the filename — creates compliance risk that grows with every revision.
The right approach is a platform where the AMP is the engine of maintenance planning — where revisions trigger workflows, where approvals are tracked in the system, where the link between a directive and the resulting programme change is documented at source, and where management can see the current status of the programme without requesting a report.
For CAMO Managers and Continuing Airworthiness Managers evaluating how to improve AMP governance, the question is not whether an integrated approach is better. It is how quickly the transition can be made.
AircraftCloud provides integrated AMP management as a core platform capability — not an add-on, not a future roadmap item.
Want to See What Integrated AMP Management Looks Like in Practice?
A platform walkthrough will show you the revision workflow, the approval tracking, the cascade to task scheduling, and the CAMO dashboard — live, not in a slide deck.
Book a 30-minute walkthrough for your CAMO team. [Schedule via Calendly →]
