Engine outcomes are often decided upstream: capacity, traceability, and the choices you make early. In this episode, Rick Tobey breaks down how ‘can it fly?’ becomes a strategic decision, and what strong teams do to keep engine programs moving when timelines tighten.
In the engine market, it’s tempting to talk about outcomes as if they’re decided by effort alone (how hard a team works, how badly an operator needs a solution, how urgent the timeline feels.)
In reality, outcomes are usually decided by something less dramatic and far more practical: constraints.
Shop access. Lead times. Limited repair pathways. The records that determine whether a part is usable. The small decisions that either keep an engine program moving, or cause it to stall.
In a Meet the Experts episode of Nose to Tail, Jet Midwest’s Rick Tobey walks through what those constraints look like in real life, and how experienced teams make decisions inside them without losing momentum or standards.
When people talk about the engine market being tight, they’re often talking about parts availability. That’s part of it, but it’s not the full picture.
The bigger picture looks like a stack of bottlenecks:
1) Capacity and access
Even when material exists, the work has to move through systems that have real limits—especially repair and shop capacity. If access is competitive, timelines stretch. Not because people don’t care, but because the queue is real.
2) Repair pathways
In some lanes, options are narrow. Repair capability can be concentrated. That means the path forward isn’t just about finding a part—it’s about finding a viable route to a finished, acceptable solution.
3) Traceability
The unglamorous truth: records decide value. Traceability determines whether material is usable, sellable, and acceptable to the next person in the chain. It’s not admin. It’s the difference between a solution and a dead end.
If you want to understand how engines move, start here. Not with marketing. With the constraints that shape what’s possible.
This is the gist of the whole conversation, and it’s the decision that quietly shapes everything that follows:
Can it fly?
Or are we committing to teardown and a longer cycle?
That question is strategic because it changes the entire decision tree:
Need help evaluating an engine path?
A teardown isn’t just an action. It’s a commitment to a process that can take time and coordination across multiple steps. When the market is constrained, that commitment matters even more.
This is also where a lot of “shortage” talk becomes clearer. Tight markets don’t just change availability. They change the economics of time. Sometimes the best move is the move that can actually move now, and that starts with asking the right first question.
When constraints are real, teams don’t win by wishing them away. They win by reducing the friction they control.
The point is simple and widely applicable: small delays compound.
So strong teams focus on the basics that prevent compounding:
This is where expertise shows up. Not in a heroic moment at the end of a process, but in the quiet discipline that prevents the process from slowing down in the first place.
In tight systems, optionality becomes practical. When the standard path is slow, blocked, or not acceptable to a specific operator, teams look for another compliant route forward.
That’s where discussions like DER repairs enter the conversation. The point isn’t to shortcut standards. The point is to create more acceptable pathways when the default pathway can’t meet the real-world constraint.
The nuance here is important: acceptance varies. Different operators have different technical philosophies. What is acceptable for one customer may be a hard “no” for another. That reality changes the path forward—and it’s one of the reasons experienced teams build more than one plan.
Rick also shares a future-facing moment that opens up a bigger question.
Additive manufacturing doesn’t just change how parts are built. It changes what’s possible to build.
If a component can only exist because a new process allows it—if complexity becomes “free” in certain design contexts—then the next question becomes unavoidable:
How will those parts be repaired?
How will the support ecosystem evolve?
How will capability and standards catch up to what the tool now allows?
It’s a reminder that constraints don’t disappear. They change shape. The work stays the same: understand the system, anticipate the bottlenecks, and build capability around the reality in front of you.
Engine programs don’t move on urgency alone. They move on decisions made early, discipline in execution, and the ability to navigate constraints without losing standards or momentum.
In other words: bottlenecks don’t eliminate outcomes.
They define how you earn them.
If you’re facing long lead times, here are 3 ways we can help…
Rick Tobey is the Director of Engine Programs at Jet Midwest, where he helps evaluate engines, plan the best path forward (fly vs. teardown), and guide the technical and operational decisions that keep engine programs moving. His work sits at the intersection of shop capacity, records/traceability, repair pathways, and real-world timelines—turning constraints into a plan that can actually execute.
Rick is the first guest in Meet the Experts, a Nose to Tail series featuring the specialists inside Jet Midwest who live the work behind the work.
Need help evaluating options, timelines, or repair pathways? We’ll help you clarify what’s possible and map a path forward.
