Analysis and commentary from the field.

Maintenance, repair, and overhaul capacity has tightened steadily across commercial and business aviation, and the operators who plan around that constraint — rather than reacting to it — are the ones protecting dispatch reliability heading into the next few years.

Three dynamics are worth tracking. First, engine shop visit demand has outpaced shop throughput in several major MRO hubs, which pushes turnaround times out even for operators with existing slot agreements — meaning contracted lead times signed two years ago may no longer reflect what a shop can actually deliver today. Second, labor availability remains the binding constraint more often than physical capacity: hangar space is frequently available where certified technicians are not, which means geographic MRO strategy increasingly has to follow labor markets rather than airport proximity. Third, parts availability — particularly for legacy and out-of-production airframes — has become a scheduling variable in its own right, not just a cost one.

For fleet operators, the practical response isn't simply "book earlier," though that helps. It's building slot flexibility into contracts, diversifying across more than one MRO relationship per aircraft type, and building parts-sourcing lead time into maintenance planning rather than treating it as an execution-phase problem. Operators who treat MRO capacity as a planning input — alongside fuel, crew, and route economics — rather than a fixed given are better positioned to absorb the next tightening cycle without it showing up as an on-time-performance problem.

None of this requires predicting exactly how tight capacity gets. It requires building enough optionality into fleet and maintenance planning that the operator isn't fully exposed to any single shop, region, or parts supplier when it does.

EN590 and D6 are two of the most frequently misrepresented product names in the fuel trading space — not usually through deliberate misrepresentation, but because "meets EN590 spec" and "verified against a certificate of analysis from an independent, accredited lab" are two very different claims, and buyers often treat them as interchangeable.

A specification name is not a guarantee. EN590 defines a set of parameters (cetane number, sulfur content, density, distillation range, and others); a seller stating "EN590" without a corresponding, verifiable certificate of analysis is making a claim, not providing evidence.

Certificates should be traceable to an accredited, independent laboratory — not the seller's own facility, and not a lab whose accreditation can't be verified against a recognized national or international body.

Sampling method matters as much as the result. A certificate is only as reliable as the sampling procedure behind it; buyers should understand whether samples were drawn at load, at discharge, or in-transit, since each carries different implications for what the certificate actually confirms.

D6 verification carries its own complications, given the product's association with fraudulent trading schemes in past years; buyers should treat unusually favorable pricing as a prompt for additional diligence, not a reason to skip it.

The underlying principle is the same across both products: specification compliance is a documentation and verification exercise, not a description. Buyers who build independent verification into the transaction — rather than relying solely on seller-provided paperwork — are the ones who avoid the costliest surprises in this market.

Defense procurement programs that cross borders rarely fail because the underlying capability doesn't work. They stall — sometimes for months, occasionally permanently — on a small set of recurring friction points that are foreseeable well before they become a crisis.

Export-control review starting too late. Programs frequently treat export-control and licensing review as a pre-delivery formality rather than a design-phase input. By the time the review happens, the technical configuration, partner list, or end-user structure may already be locked in ways that make compliance far more expensive to achieve — or force a redesign under time pressure. Early engagement with qualified export-control counsel, before partner and configuration decisions are finalized, is consistently cheaper than resolving conflicts after the fact.

Ambiguous ownership between government and industry partners. Cross-border programs often involve a government customer, a prime contractor, and one or more subcontractors or joint-venture partners across multiple jurisdictions. When responsibility for schedule, quality, and compliance isn't explicitly assigned at each handoff, the ambiguity surfaces as delay — each party assumes another is tracking a given risk until a milestone is missed and no one was.

Underestimating multinational stakeholder alignment time. A procurement timeline built around a single government's internal approval process routinely underestimates how long it takes to align two or more governments, or a government and an allied industry partner, on requirements, funding release, or delivery terms. This isn't a compliance problem — it's a planning problem, and it's usually solvable by building realistic alignment buffers into the schedule from the outset rather than treating cross-government coordination as a formality.

None of these are exotic risks. They're the ordinary friction of doing business across jurisdictions and organizations — which is exactly why they're so consistently underestimated in program planning.

Institutions operating across both the U.S. and Latin American markets face a positioning problem that's easy to underestimate: the strategic narrative that works domestically in one market often reads as tone-deaf, over-formal, or simply irrelevant in the other — and running two disconnected narratives creates its own credibility cost.

A few patterns worth naming. U.S. institutional audiences tend to respond to precision and quantified outcomes — market share figures, efficiency metrics, defensible growth cases. Latin American institutional audiences, particularly in government-adjacent and infrastructure sectors, more often respond to relationship continuity and long-horizon commitment — evidence that an institution is a durable, present partner rather than an opportunistic entrant. Neither preference is superior; they're different risk calculations, and a positioning strategy that only speaks to one leaves real value on the table with the other.

The stronger approach isn't translating one market's narrative into the other's language — it's identifying the subset of the strategic story that's genuinely true in both registers (operational reliability, for instance, tends to matter everywhere) and building outward from that shared core, rather than maintaining two separate stories that happen to describe the same institution.

This matters more, not less, as institutions expand their footprint across the region: a positioning strategy that only works in one market becomes a growth constraint the moment expansion depends on the other.

Remote advisory has gone from an operational compromise to, in many cross-border mandates, the more effective default — but it isn't universally the right model, and the distinction matters more than the general trend.

Remote advisory works well when the mandate is primarily analytical or strategic — market entry evaluation, positioning strategy, vendor assessment based on documentation and structured interviews. It also works well when the client's stakeholders are themselves distributed across multiple countries, since a remote advisor isn't privileging any one location by default, and can often move faster between time zones than an advisor based in a single physical office.

It works less well in three situations. First, when trust-building requires physical presence — early-stage relationships in markets where in-person meetings are the norm for establishing credibility, particularly in parts of Latin America and in government-adjacent work generally. Second, when the mandate requires direct observation of physical operations — a facility, a fleet, a supply chain — where remote review of documentation is a poor substitute for walking the floor. Third, when a program has reached a decision point that genuinely benefits from an in-person working session — not every meeting needs one, but some do, and treating all meetings as equivalent whether remote or in-person tends to slow down exactly the moments that need speed.

The practical implication for institutions evaluating advisory partners: ask not "can this be done remotely" but "which parts of this mandate benefit from presence, and which don't" — and expect a credible advisory partner to be able to answer that question specifically, rather than defaulting entirely to one model or the other.

Operating across aviation, strategy, fuels, and defense means we get approached with mandates that don't fit neatly into a single practice — which is generally the point of a cross-sector advisory firm, but it also means we've had to be disciplined about which mandates we take on. Three questions come up in nearly every intake conversation.

Does this require genuine cross-sector judgment, or does it just touch multiple sectors? A mandate that happens to involve both aviation and financing questions isn't automatically a cross-sector mandate — sometimes it's an aviation mandate with a financing component that a specialist could handle perfectly well. We're most useful when the sectors genuinely interact — when the fuel-sourcing decision affects the fleet strategy, or the defense-program timeline depends on a regulatory question that spans jurisdictions — not when a client simply wants one firm to coordinate what could be several independent engagements.

Can we be genuinely independent on this one? Non-conflicted advice is easier to promise than to structure. Before taking on a mandate, we look at whether we have — or could reasonably be perceived to have — a competing relationship with another party to the same transaction or program. If we can't clear that bar cleanly, we say so early rather than after the engagement has started.

Is the client's timeline realistic for the complexity involved? Cross-border and cross-sector mandates are the ones most likely to have timelines built around a single-sector assumption — a procurement timeline that doesn't account for multinational regulatory review, for instance. We'd rather have that conversation at intake than discover it three months into an engagement.

These aren't formal criteria so much as a discipline we've found keeps engagements productive for both sides — which, over enough mandates, turns out to matter more than almost anything else in cross-border advisory work.