Parking reactivation records
Preservation and de-preservation records for storage exit
CAMOs, operators, lessors use this page when Aircraft exiting long-term storage puts the Storage preservation log under review. The work traces Storage preservation log and De-preservation task package to Maintenance task-card evidence, Inspection result, current status data, and supplied acceptance criteria. Findings identify missing source pages, unsupported applicability, serial or location conflicts, and open corrective evidence. The buyer receives a cited register, evidence map, request list, and closure plan.
When this review is needed
- A Aircraft exiting long-term storage is approaching and the records owner needs a page-level proof set.
- The summary status uses shorthand that cannot be defended without the underlying task, release, or configuration record.
- A counterparty has asked which exceptions are true blockers and which are retrieval issues.
The problem
Preservation log evidence often looks complete until the reviewer asks which page proves the actual aircraft, engine, component, or location. The review focuses on those trace points instead of accepting inherited status language.
What gets reviewed
- Confirm each required storage task has a dated accomplishment record for the storage period.
- Review de-preservation cards against the approved storage exit plan supplied by the operator or CAMO.
- Check preservation gaps for follow-up inspections or documented engineering dispositions.
- Tie reactivation defects to rectification records and release entries.
- Separate missing routine storage logs from unresolved airworthiness findings.
Scope this review
Tell us the asset, the event, and the evidence in scope, and we will outline a focused first engagement.
Send a representative, redacted record set and we will scope the review.
What gets validated
- Pass when storage interval, task accomplishment, defect closure, and release evidence align.
- Fail when preservation logs stop before the aircraft actually left storage.
- Pass when missed tasks have documented follow-up action and acceptance by the responsible organization.
- Fail when de-preservation is summarized in one release entry with no task package.
Evidence normally required
- program task list for parking period
- periodic preservation logs
- de-preservation work package
- reactivation inspection records
- defect and rectification list
- aircraft logbook release
Common discrepancies
- Calendar preservation tasks missing during a period of extended parking.
- De-preservation work package signed but referenced inspection sheets absent.
- Defects found at reactivation closed in maintenance tracking but not in source records.
- Start and exit dates inconsistent across status reports.
What is at stake
If the gap survives to closing or delivery, the next owner may inherit a disputed status line and a harder retrieval problem. Schedule, reserve, or acceptance decisions can then rest on assumptions instead of records.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Frame Long Term
Confirm the exact event, affected file set, buyer role, and decision standard before any preservation log is treated as sufficient.
Trace Exit Preservation
Walk the named evidence from index entry to source artifact and mark where the trail supports, conflicts with, or fails to answer the page-specific question.
Sort Review Records
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package Reactivation Exiting
Deliver the exception list, evidence map, and owner sequence in a form that can move directly into remediation, submittal cleanup, or transaction negotiation.
What the buyer receives
- Exit preservation discrepancy log with source-page citations
- Evidence map for accepted, rejected, and unresolved lines
- Targeted retrieval list for records owners
- Closure brief for technical and commercial decision makers
Who uses the output
- CAMO manager uses the register to decide which lines can be accepted or escalated.
- records manager uses the evidence map to request missing technical records.
- reactivation lead uses the closure plan for transaction, audit, or delivery decisions.
How the work fits into the transaction or program
The decision is whether the storage-period records prove the aircraft was preserved and de-preserved to the program, so reactivation and any transfer stand on evidence rather than assertion; the completed preservation task cards during storage (recurring engine/APU runs or inhibiting, desiccant changes, tire/hydraulic tasks), the de-preservation work package at exit, calendar-task compliance across the whole storage period, corrosion/inspection findings and their disposition, and the reconciliation. The evidence set centers on the completed preservation task cards during storage (recurring engine/APU runs or inhibiting, desiccant changes, tire/hydraulic tasks), the de-preservation work package at exit, calendar-task compliance across the whole storage period, corrosion/inspection findings and their disposition, and the reconciliation of frozen time/cycle and AD status to the reactivation baseline. The likely weak points are a preservation program that has no task-level evidence for the middle of a long park, missed calendar tasks discovered only at exit, de-preservation signed off without the matching induction record, and AD/time status that was never truly frozen. Handoff: CAMO manager, aircraft exiting long-term storage, Preservation and de-preservation records for storage exit.
Jurisdiction-specific considerations
EASA and FAA references are used as evidence context for recordkeeping and compliance support. The review does not treat one authority's record format as automatic acceptance by another authority or by a counterparty.
Regulatory limits
This work is an evidence review only. It does not approve a repair, modification, inspection, manual revision, aircraft, engine, appliance, or part, and it does not replace the regulator, authorized release personnel, operator, or maintenance organization.
What this review does not cover
- Physical inspection or borescope work outside the records set
- Engineering approval of repairs or alternate methods
- Commercial negotiation of credits or reserves
Specific to this review
- For this review, storage exit evidence is time-based, so the first check is the actual parked interval rather than the final release date.
- A recurring records trap is that a good reactivation file shows what was preserved, what was disturbed, and what was repaired before operation.
- Missed preservation tasks are record findings until the follow-up inspection or disposition is documented.
- The scope uses the Long Term Storage Exit question as the control point, so the review stays tied to Aircraft exiting long-term storage and the buyer decision behind it.
- The evidence starts with Preservation log and follows Preservation Evidence Review Records references until every exception has a source location and a reason code.
- The finding logic separates missing paperwork, conflicting status, stale revision data, and unsupported disposition because each class closes through a different owner.
- The timing matters for CAMO manager: the output is useful only if the unresolved items are visible before acceptance, submittal, handback, or negotiation pressure fixes the sequence.
- The boundary control keeps Parking Reactivation Exiting Proving questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
- The handoff value comes from Exit preservation discrepancy log with source-page citations; it gives the next reviewer a precise map instead of another broad request for a better file.
- The source discipline is stricter on this page than on a general audit because the claim being tested is Prove preservation and de-preservation task compliance when an aircraft exits long-term storage..
Sources
U.S. Government (eCFR). Records an owner or operator must keep, including total time in service, current status of life-limited parts, and AD compliance.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Federal Aviation Administration. FAA guidance on making and keeping maintenance records and acceptable recordkeeping practices.
Frequently asked questions
What makes this records review different from a general file audit?
The scope is tied to long term storage exit and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block aircraft exiting long-term storage or can be closed later without changing the decision.
What evidence has to be available before this work starts?
The starting point is preservation log, the current status source, and any index or matrix that tells reviewers where the supporting artifact should live. Missing inputs are logged as findings rather than filled with assumptions.
Who decides whether an open item is acceptable?
The review explains what the evidence supports and gives camo manager a closure path. Acceptance remains with the buyer, operator, authority, delegated engineer, or authorized person responsible for the underlying airworthiness or certification decision.
Relevant glossary terms
Related pages
Where this fits
Talk to an engineer who has done this work
We will walk through your current state, the records or evidence involved, and a scoped first engagement.
Talk through the aircraft, records, evidence, deadline, and next useful step.