Start a component pool with one readiness problem
A shared stock list is not yet a support programme. Begin with one fleet-readiness problem, identify compatible units and agree who receives access when two members need the same component at once.

Illustrative image—not evidence of a real case or verified capability.
Choose a problem members actually share
An airline may hold a valuable component that rarely moves while another operator searches urgently for a compatible unit. That suggests a coordination opportunity, but it does not prove that the first unit can support the second fleet. Start with a narrow component family, a stated operating area and a small group of participants willing to provide evidence. Examine compatible configuration, actual demand, removal patterns, repair support and transport constraints. Avoid selecting the pilot solely because an item has a high book value. The useful question is whether shared access could address a specific readiness gap under realistic conditions, not whether a large inventory number looks impressive in a presentation.
Separate ownership from committed access
For each candidate unit, establish identity, control, evidence status, location and the period during which access is actually offered. The owner may retain title while accepting a defined access obligation; the precise arrangement needs its own agreement. Exclude incompatible holds and reservations without counting the same restriction twice. Record whether a unit is physically ready, awaiting inspection or still expected from repair. A planned contribution is not available capacity. Lufthansa Technik's published pooling description combines defined service levels, repair management and home-base stock considerations. That is an established provider's example, not evidence that a proposed local pool already has the same assets, logistics or guarantees.
Agree the uncomfortable simultaneous-demand case
The allocation rule matters most when there is not enough eligible stock for everyone. Agree how urgency is substantiated, which contractual priorities apply, who resolves a conflict and what alternative response is offered when the pool cannot fulfil a request. A larger contribution should not silently create an unlimited technical or commercial entitlement. Preserve the reason for each allocation and the evidence available at that time. A software ranking can organise information, but the responsible people retain the decision within the programme's rules. In a pilot, a transparent unsuccessful allocation may teach more than several easy deliveries because it reveals whether the members actually understand the promise they are buying.
Plan the return path before the first issue
A pool can look healthy on its opening day and weaken after repeated issues if returns and repair are unclear. Define the returned Core obligation where applicable, inspection responsibilities, repair-routing decisions and how the available population is replenished. Identify who pays which costs and how unresolved damage or record issues are handled. Keep the shared access programme separate from a maintenance release or permission to install. A hypothetical airline receiving a unit still needs its own applicable technical acceptance and operational decisions. The pool coordinates an agreed resource; it does not transfer every participant's authority to a platform administrator or make an unsuitable component suitable through membership.
Measure the pilot against an explicit alternative
Record requests, eligible responses, unmet demand, time to supported offer, physical delivery and the cost of maintaining committed capacity. Compare these with a stated alternative such as separate stockholding or spot sourcing over the same scope and period. Include administration, repair, transport and unused-capacity costs where relevant; do not present the inventory's headline value as a saving. Review concentration risk if several members rely on the same repair route or transport bottleneck. Begin with a reversible pilot and agree its review date and exit arrangements. A programme earns a stronger promise from observed capacity and performance, not from describing a future national network as if it already existed.
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.