Strong lifecycle support develops over time.
Each new capability can create another way to solve a customer problem, support an asset, manage a constraint, or keep an aircraft operating. Over time, those capabilities begin to connect. Repair expertise informs material decisions. Supply-chain knowledge supports MRO. Internal processes improve turnaround. OEM relationships create access to additional products. Leasing, exchange, and trading provide alternatives when repair alone cannot meet the need.
The opportunity is significant, but so is the operational responsibility that comes with it.
A broader lifecycle solution works when the organization can sustain what it has built. That requires deliberate investment in expertise, leadership, processes, infrastructure, relationships, and internal control. Each layer should make the organization more capable of supporting the next.
Lifecycle Support Is Built Over Time
An aviation company can add a service to a capabilities list much faster than it can develop the expertise required to deliver that service consistently.
Real capability develops through repetition, investment, problem-solving, and accumulated knowledge. People learn the work. Processes evolve around it. Tooling and infrastructure improve. Supplier networks grow. Customer requirements become better understood. Over time, a service becomes something the organization can perform predictably rather than something it is simply willing to attempt.
Barry Startz’s career followed a similar progression. After beginning as a helicopter mechanic in the Army, he spent 35 years with the organization that eventually became TurbineAero. During that period, his responsibilities grew from hands-on mechanical work into APU testing, multiple product lines, supply chain, operations, and leadership.
That kind of progression illustrates an important principle for lifecycle organizations:
Breadth becomes stronger when it grows from depth.
The more thoroughly an organization understands each capability it builds, the easier it becomes to see where that capability connects to the next part of the lifecycle.
Capability Starts With Deep Experience
Technical experience creates context.
Someone who has repaired a component understands failure differently from someone who has only purchased it. Someone who has worked in supply chain sees availability differently from someone focused exclusively on production. Operations adds another perspective. Trading, leasing, sales, and customer support add others.
When those perspectives begin to connect, decisions can account for a larger portion of the asset’s lifecycle.
A repair event may also be a material problem. A material problem may have an exchange solution. An aging platform may require a different sourcing strategy than a newer program. A customer experiencing repeated availability problems may benefit from a rotable pool, additional in-house repairs, or another form of support.
Lifecycle capability grows as an organization becomes better at understanding those connections.
That makes technical depth valuable even as an organization becomes broader. The objective is to preserve expertise while applying it across a wider range of decisions.
Leadership Expands What the Organization Can Do
Individual expertise has limits. Organizational capability allows expertise to spread.
Barry’s move from mechanic into management required a different kind of development. He sought formal leadership training and continued investing in that education because leading people required skills beyond the technical knowledge he had already accumulated. His leadership philosophy eventually centered on the people performing the work: give them the resources, support, accountability, and opportunity required to succeed.
That connection matters in MRO because every additional capability eventually becomes a people challenge.
New programs require technicians who understand the work. New equipment requires training. Increased volume requires supervisors who can manage flow without becoming bottlenecks. Specialized knowledge has to move from experienced individuals into processes that others can learn and repeat.
Leadership therefore becomes part of lifecycle development.
An organization can broaden its capabilities as its people become prepared to execute them reliably.
That preparation protects quality while allowing knowledge to move beyond the people who originally developed it.
Growth Opportunities Can Open the Next Stage
A well-chosen opportunity can change much more than revenue.
During Barry’s time at Piedmont, agreements surrounding Honeywell APU programs created new leasing activity, additional product lines, customer relationships, and opportunities to expand operations. The organization added capabilities that then created access to additional work.
This is one way lifecycle capability can evolve naturally.
A customer need creates a new opportunity. Developing that capability creates knowledge, infrastructure, and relationships. Those resources make another adjacent capability possible.
The progression might look like:
Opportunity → capability → experience → adjacent opportunity → broader support
Each step can also give the organization greater control over the results it delivers. Additional repair capability may reduce turnaround exposure. A lease pool can provide another availability option. Better material access can keep a repair moving. A stronger internal process can improve predictability.
The advantage comes from building those capabilities in a sequence the organization can support.
Know When to Expand. And Know When to Improve Existing Capabilities First.
Expansion is one form of growth. Greater proficiency is another.
After describing several areas of investment and expansion, the conversation turns toward a different priority: spending time becoming exceptionally good at the capabilities already in place.
For a growing MRO, that period can be just as valuable as launching another program.
Established capabilities still offer room to improve:
- turnaround time,
- throughput,
- technician proficiency,
- process flow,
- quality,
- capacity,
- customer communication,
- and the consistency of the finished work.
Barry describes a point when an organization benefits from focusing its energy on becoming expert in the work it has already brought in before continuing to add new programs.
That creates an important rhythm for sustainable lifecycle growth:
Expand. Learn. Improve. Stabilize. Then evaluate the next opportunity.
The result is a capability structure that becomes stronger as it becomes broader.
Process Improvement Turns Growth Into Repeatability
Growth changes the operation.
More customers create additional scheduling pressure. Higher volume affects floor layout, staffing, material movement, tooling, inspection, documentation, and customer communication. Processes designed for a smaller workload eventually reach their limits.
That is where continuous improvement becomes part of growth rather than a separate initiative.
As Piedmont’s APU work increased, the operation incorporated lean processes and developed dedicated lines around specific product families. Capacity could then be added in proportion to demand instead of simply increasing everything at once.
The progression is straightforward:
Opportunity → demand → process improvement → repeatable execution → capacity
That sequence matters because sustainable capacity comes from the system around the work as much as the physical ability to perform the repair.
A shop can possess the tooling and technical knowledge for a program while still struggling with flow. Process design converts technical capability into dependable delivery.
Internal Capability Creates Greater Control
Every outside handoff introduces another variable.
Material may be unavailable. A specialized process may have a long queue. Transportation adds time. An outside supplier may have different priorities. Communication can slow decisions.
Strategic internal capability gives an organization additional control over those dependencies.
In his Greensboro operation, machining, rework, plating, painting, and other processes could be performed internally for portions of the APU and landing-gear workload. Barry connected that capability directly to navigating supply-chain pressure because certain work could continue without relying on another outside provider.
Current TAT materials continue to emphasize extensive in-house machining, plating, coating, and specialized repair as part of its MRO model. Tat Technologies
Internal capability is most valuable when it addresses an important source of uncertainty.
An organization might consider questions such as:
- Which external dependencies create the greatest turnaround exposure?
- Which recurring repairs justify internal investment?
- Where would additional control improve quality or responsiveness?
- Which processes reinforce several existing product lines rather than a single isolated service?
- Where does internal capability create new options for customers?
The goal is strategic control.
Each well-chosen internal capability can reduce the distance between a problem and the resources required to solve it.
Relationships Are Also Part of Capability
A lifecycle solution still depends on an ecosystem.
Supply-chain experience is valuable partly because experienced people know where to look when the normal path reaches a dead end. Barry describes using established relationships and industry contacts to find material when standard sourcing channels had already been exhausted.
Those relationships function like an extension of internal capability.
OEM partnerships can provide technical access, licensed programs, and long-term product support. Suppliers provide material and specialized processes. MRO partners create alternatives when internal capacity is constrained. Customers themselves provide operational information that can shape new solutions.
A strong lifecycle organization therefore develops two forms of control simultaneously:
the capability it owns and the network it can reliably activate.
That balance creates flexibility. Some problems are best solved internally. Others benefit from a partner with deeper specialization. The organization’s value comes from understanding the difference and having dependable options available.
The Aftermarket Extends the Useful Life of Aviation Assets
Lifecycle support becomes particularly important as aircraft and components mature.
OEM investment naturally evolves toward current and future platforms. Existing fleets still require material, maintenance, repairs, exchanges, engineering support, and specialized expertise for years afterward.
The aftermarket helps carry that expertise forward.
The Barry Startz conversation illustrates this transition through APU programs and other mature product lines. As OEM priorities evolve, specialized providers can assume greater responsibility for maintaining expertise, developing repair capacity, sourcing material, and continuing to serve operators using those assets.
That creates one of the aftermarket’s most important lifecycle roles.
A component that becomes less central to an OEM can remain critically important to the operator flying it.
The value of specialized lifecycle support often increases during that period because the available options begin to change. Repair capability, used serviceable material, inventory knowledge, exchange assets, leasing programs, and industry relationships can keep mature equipment economically viable.
Lifecycle support therefore follows the asset rather than a single product cycle.
Growth Should Improve the Customer’s Options
Capability expansion has a practical test:
Does it give the customer a better path forward?
A broader organization can offer several kinds of value when its capabilities work together.
A repair can return a component to service. Internal machining can shorten part of that repair path. Material resources can resolve shortages. A lease or exchange asset can support the customer while maintenance continues. Stronger supplier relationships can uncover another sourcing option. Specialized knowledge can sustain an older platform after support elsewhere becomes more limited.
Barry’s experience at Piedmont also illustrates how specialized providers can serve operators whose scale or requirements differ from the largest airline customers. The growth strategy he described included supporting customers who needed a focused response rather than the volume-oriented model of a much larger OEM environment.
That customer perspective helps keep lifecycle expansion disciplined.
The objective is not the longest possible list of services. The objective is a stronger set of connected options.
Build the Next Capability on a Stronger Foundation
Aviation lifecycle support develops layer by layer.
Technical expertise creates the starting point. Leadership helps that knowledge spread. New opportunities create reasons to expand. Process improvement makes the work repeatable. Internal capability increases control. Industry relationships expand the available options. Specialization creates depth. Customer needs help determine where the next investment belongs.
Then the cycle continues.
A useful progression is:
Learn → build → improve → stabilize → expand → integrate
Each pass through that cycle can broaden the organization’s ability to support an asset while strengthening the capabilities already in place.
That is what makes sustainable lifecycle growth different from accumulation.
The strongest organizations keep increasing the number of problems they can solve while preserving the quality, expertise, and operational discipline required to solve them well.
The strongest lifecycle capabilities are built one dependable layer at a time.