An aircraft in your hangar is not necessarily your aircraft
A C-check visit changes custody and work status, not necessarily ownership or operator authority. Keep one asset identity and a clear record of who is doing what.

Illustrative image—not evidence of a real case or verified capability.
Name the relationship instead of copying the asset
An airline sends an aircraft to an MRO for a scheduled visit. Both organisations need to see it, but creating two unrelated aircraft records makes later reconciliation harder. Preserve one identified asset with separate relationships for the owner, operator and maintenance custodian, together with the relevant dates and source. Location is another fact: an aircraft can be at the MRO while the operator's obligations remain elsewhere. A fleet view should explain why the asset appears for that user. Visibility in a maintenance workspace is not proof of ownership, registration or authority to operate. This distinction also applies to a standalone engine that an MRO has received for work.
Record the induction baseline
Before work starts, agree the identified aircraft or engine, the accepted scope, supplied configuration information, accompanying records and known discrepancies. Record custody handover and the condition observed at receipt without pretending that a visual intake check establishes complete airworthiness. Separate customer-supplied information from the MRO's own findings. A work reference connects the asset to the contracted activity; it should not expose the customer's entire operational record to every workshop user. If a document or accessory is missing, assign a question and owner. This baseline gives later changes a context and makes it possible to distinguish pre-existing observations from findings that emerge during the visit.
Keep installation as a relationship with a history
An installed component is still the same physical item represented in its inventory or component record. Link it to the aircraft, engine or assembly position with the appropriate evidence and dates, rather than creating a fresh item for each parent. When it is removed, preserve the earlier link and record the new location and condition. A replacement changes the current relationship, not the identity of the removed unit. Distinguish a proposed planning change from an authorised and recorded physical event. For customer-owned stock, maintenance custody must not grant the MRO unrestricted visibility of the owner's unrelated inventory. Share the information needed for the agreed work through controlled access.
Connect findings to a decision, not just a comment
During a visit, an additional finding can affect scope, material demand, cost or schedule. Record the observation and responsible assessment before asking the customer for a commercial decision. Keep technical disposition, contractual authorisation and actual accomplishment separate. The customer may accept a price while an engineering question remains open; a workshop may complete a task while the agreed delivery pack is still incomplete. Show those differences rather than forcing every activity into one percentage. A useful workspace identifies the next action and its owner for each open question. Messages help collaboration, but an important consent or technical record should remain identifiable without searching an entire conversation thread.
Hand back the records deliberately
ATA's aircraft-transfer work describes structured information sets for asset status, installed components and historic events. It illustrates why a current snapshot and its history serve different purposes; it does not establish that a particular software export implements the specification. For an MRO visit, define the required delivery records with the operator and keep their transfer and acknowledgement visible. Custody return, invoice settlement and the authorised maintenance release are different events. Do not mark an aircraft operational merely because the customer collected it or a commercial order closed. Preserve open record questions and their agreed treatment. The organisation's controlled processes and competent authorities govern the actual release and continuing-airworthiness obligations.
Reconcile both views with one synthetic visit
Use an illustrative aircraft, two engines and several component links to rehearse induction, a removal, a scope change and return. Ask the airline and MRO users to explain the same events from their own views. Confirm that the MRO's custody ends without deleting the history and that the airline still has one asset, not a duplicate created by the visit. Keep every sample clearly labelled. Synthetic fleet entries must never become public statistics about real airline capacity. If member records later contribute to intelligence, that needs a separate verified-claim, consent, provenance and publication process. An operational relationship is useful evidence, but it is not automatically an authoritative national fleet fact.
Sources & scope
This is editorial educational analysis. Licensed manuals are not reproduced; Iranian applicability and independent technical approval are not established. Actual operations require current controlled sources and authorized decisions.
Continue with the Library tools
Related reading
On this page
Test the idea, not just your memory
Short learning scenarios with explained answers—not a qualification test, training certificate or operational decision.