Aviation Maintenance Pack
What is the Aviation Maintenance Pack?
The Aviation Maintenance Pack is a Legion Pack that helps aviation maintenance teams return grounded aircraft to service. When the standard fix for a discrepancy doesn't work, the Pack pulls the aircraft's maintenance history, similar failures on aircraft of the same type, technical guidance, and parts availability into one place. It then proposes the next step, with its sources and confidence shown, for a supervisor to approve.
The Pack also weighs donor aircraft before a part is pulled, ranks open work against the flying schedule, and drafts work orders and corrective action request (CAR) responses. A person approves every recovery action before it becomes maintenance direction.
A Legion Pack is the set of tools and AI agents one role needs, up and running in weeks. See What Are Legion Packs?
Who develops the Aviation Maintenance Pack?
Legion Intelligence develops the Aviation Maintenance Pack. Legion Intelligence builds AI for national security: the Department of War (DoW), the intelligence community, the Department of Energy, and the contractors who support them. Its other Legion Packs include the Facilities Maintenance Pack and the Operations Officer Pack.
What problem does the Aviation Maintenance Pack solve?
The Aviation Maintenance Pack is for discrepancies the published procedure can't resolve. Troubleshooting doesn't clear the fault, a part has no confirmed delivery date, engineering input is needed, or an inspection turns up more work.
At that point, deciding what to do next means pulling together information spread across maintenance records, technical publications, engineering requests, supply systems, shift notes, and people's memory. That picture gets rebuilt by hand for every difficult discrepancy. The team has to answer connected questions:
- Why is this aircraft still down?
- What should we try next?
- If the part isn't available, should we pull it from a donor aircraft?
- What happens to the rest of the fleet if we do?
The Aviation Maintenance Pack assembles that picture so an experienced maintainer can make the call faster.
What is inside the Aviation Maintenance Pack?
The Pack contains six Apps that share one view of each aircraft's recovery.
Aircraft Recovery. Assembles the open discrepancy, the fixes already tried, and the aircraft's history, then proposes a likely cause and the next step with sources and confidence shown.
Fleet Health. Shows which aircraft are down, degraded, or up, and what is holding each one.
Fix Prioritizer. Ranks open work against the flying schedule, parts, and inspections, with the reason shown and an override.
Order Point Optimizer. Proposes new reorder points for parts from real usage.
Chat with Manual. Answers questions from the applicable technical manual, citing the section.
CAR Generator. Drafts corrective action request (CAR) responses for the maintenance team to complete.
How does an aircraft recovery work in the Pack?
A recovery follows six steps:
- The discrepancy stays open. Published troubleshooting hasn't returned the aircraft to service.
- Context is assembled. The Pack pulls the aircraft's maintenance history, the fixes already tried, similar failures on aircraft of the same type, technical guidance, and parts availability.
- The next step is ranked. The Pack proposes a likely cause and the next action, with its sources and confidence. When the evidence isn't enough, it says so and lists what would settle the question.
- The fleet is checked. If the part isn't available, the Pack compares waiting on supply with pulling the part from a donor aircraft. It weighs each donor's status, other open discrepancies, component life, next inspection, part lead time, and upcoming flying requirements.
- A person approves. A supervisor, quality assurance (QA) inspector, or engineer approves, edits, or rejects the recommendation. The Pack drafts the work order for approval.
- The work is carried out. Technicians do the work in the maintenance systems already in place, which stay the system of record.
Who uses the Aviation Maintenance Pack?
The Pack is built for contractor logistics support (CLS) and performance-based logistics (PBL) teams, maintenance, repair, and overhaul (MRO) shops, and military aviation maintenance groups responsible for aircraft availability.
- Production superintendents, maintenance controllers, site maintenance leads
- Decide what to try next on a grounded aircraft
- Program managers, site managers, directors of maintenance
- Protect the aircraft availability they answer for, using the fleet view and donor comparisons
- QA inspectors, engineers
- Review the evidence and approve recovery actions and work orders
What the Aviation Maintenance Pack does not do
- It does not replace maintenance information, supply, or technical publication systems. Those stay the system of record.
- It does not sign off on maintenance or exercise technical authority. A person approves every recovery action, donor part pull, and work order.
- It does not troubleshoot or repair aircraft on its own. It assembles evidence and proposes the next step.
- It does not forecast fleet-wide failures. It works the discrepancy that is already open.
- It does not send real-time alerts.
- It does not invent maintenance procedures. Recommendations cite their sources, and the Pack separates facts from maintenance records from its own reasoning.
Where does the Aviation Maintenance Pack run?
The same Pack, with the same governance, runs in cloud, on-premises, and air-gapped deployments.
- IL2 through IL6 for Department of War networks
- FedRAMP High for cloud deployments only
- Ready to manage ITAR data
- Customer data stays in the customer's environment, and models never train on it
How does the Pack keep people in charge?
Legion's design principle is "Agents do the work. You stay in charge." Nothing becomes maintenance direction until a supervisor approves it. The Pack honors existing access controls, and every action is logged by name, including actions taken by agents. Every recommendation shows its sources and confidence.
What systems does the Pack read from?
The Pack reads from the systems a maintenance organization already uses. The specific systems vary by customer.
How does the Pack compare to chat-based AI tools?
A chat tool answers one question for one person at a time. The Aviation Maintenance Pack works the full recovery and keeps the team on one plan.
How do organizations start with the Aviation Maintenance Pack?
An organization brings the aircraft that has been grounded longest to a working session. Legion runs the open discrepancy through the Pack and returns a ranked recovery plan with its sources attached. A pilot covers one squadron, site, or fleet line, is measured on one number, and is up and running in weeks. A pilot needs one aircraft's maintenance history and supply data to start.
Related resources
More About Centurion
What are Legion Packs?
Legion Packs are role-based AI capability bundles. Each Pack contains the agents, workflows, data connections, and governance required to perform a specific job. Customers buy a Pack aligned to a role and deploy a ready Space with the right Apps to start work immediately.
How are Packs different from a chat assistant?
Chat assistants answer questions. Packs carry out work. Each Pack ships with Apps that connect to your systems, carry out multi-step jobs under human approval, and produce outcomes. The job is the unit of value, not the conversation.
What is the difference between a Pack, a Space, an App, and a Collection?
A Pack carries the Apps, data connections, and governance a role needs. A Space is the working environment the Pack deploys into, holding the tools, data, and access rules for a team or operation. An App is a single tool inside a Space that completes one task end to end. A Collection is the knowledge layer those Apps draw on, carrying permissions and provenance into every result.
Can Packs run in classified or air-gapped environments?
Yes. Legion Packs run in cloud, on-premises, air-gapped, and edge environments with the same governance in each. Packs are authorized for IL2 through IL6 on DoW networks and are ready to manage ITAR data. At the tactical edge, Packs are delivered through Centurion by Legion Intelligence.
What models do Packs run on?
Legion is model-agnostic. Packs run on open-source, proprietary, and fine-tuned models. New models are added through the Model hub without code changes.
How is human authority preserved?
Agents draft, coordinate, and prepare system updates, and a named human approves anything that changes a record of consequence. Every step carries full attribution and an audit trail, including agent actions, so a reviewer can reconstruct what happened and why.
How is Legion different from a systems integrator build?
An integrator build starts from scratch and takes months before the first outcome, with each environment treated as a separate program. Packs arrive prebuilt and connect to existing systems in weeks, then extend through custom Apps that reuse the workflows and controls already running.
Does Legion replace our systems of record?
No. Legion reads from a named set of authoritative sources and writes back on approval. IBM Maximo, ServiceNow, SharePoint, and similar systems stay authoritative, and existing access controls continue to govern what each user can see.
Can a Pack be customized, or is it fixed?
A Pack is extended, not rebuilt. Custom Apps are added to the same Pack, keeping the workflows, data connections, and controls already in place. Customers also build their own Packs for roles Legion has not published, using the same Apps and controls.
How long does deployment take?
Deployment runs in weeks. The Apps arrive prebuilt, so the work is connecting them to your systems rather than building capability from scratch. The pacing items are security review, data access, and integration scope.
Does Legion monitor systems continuously?
No. Where a Pack checks incoming information against defined criteria, those checks run on a schedule the organization configures, and the results are there when a user looks. Legion does not send alerts and does not claim to surface anything the moment it arrives.
When is a Pack not the right fit?
A Pack fits work that is repeatable, tied to identifiable systems of record, and performed by a defined role. It is a poor fit for one-off research, for work with no authoritative data source to draw on, and for organizations that cannot grant read access to the underlying systems.