Cross-border aircraft engine training can create export-control obligations long before an engine, tool, or component moves. For ITAR-controlled MRO programs, the central question is not simply whether a deemed export license is needed, but which technical data, defense services, parties, nationalities, destinations, and later customer support activities require authorization.
Determine Jurisdiction Before Selecting an Authorization
An effective licensing strategy begins with jurisdiction and classification. An aircraft engine used in a military application is not automatically controlled under the International Traffic in Arms Regulations, and technical information is not controlled merely because it concerns maintenance. The companies must establish whether the engine, related components, technical orders, work scopes, drawings, software, and training materials are ITAR-controlled, subject to the Export Administration Regulations, controlled under another U.S. regime, or governed primarily by foreign law.
Origin also matters. If the engine and technical data were developed in Israel, Israeli export-control requirements may govern the initial release. ITAR restrictions could still apply to incorporated U.S.-origin defense articles or technical data, including information previously exported from the United States under limitations on reexport or retransfer. The parties should trace the technology’s origin, contractual restrictions, prior licenses, and approved end uses rather than relying solely on the engine’s country of manufacture.
Why the Absence of Hardware Does Not Eliminate Export Controls
Sending technical orders by email, providing access to a cloud repository, sharing a screen, conducting hands-on instruction, or discussing controlled repair methods can constitute an export or release. Under the EAR, a release of controlled technology to a foreign national in the United States is generally analyzed as a deemed export. Under the ITAR, similar conduct is typically evaluated as an export of technical data or the furnishing of a defense service to a foreign person.
Employee citizenship and immigration status are therefore material. A U.S. company’s workforce may include U.S. persons and foreign persons, and the authorization analysis can differ for each group. Location alone does not resolve the issue: training in Israel, training in the United States, and remote instruction may each create distinct export, reexport, import, or foreign-law obligations.
Build the Authorization Around the Entire MRO Program
Where ITAR-controlled technical data and defense services are involved, a Technical Assistance Agreement, or TAA, is often the appropriate authorization mechanism. A TAA can generally be structured to cover defined training, maintenance assistance, technical exchanges, and participating foreign parties over a specified program period. It is not simply an individual license issued once for every employee who attends a class.
The application typically must be submitted by an eligible U.S. applicant. Depending on the transaction, that may be the U.S. MRO provider, a U.S. affiliate of the foreign manufacturer, or another U.S. person responsible for furnishing the controlled assistance. The agreement should identify the relevant foreign parties, countries, facilities, end users, sublicensees, employee nationalities, technical data, defense services, program purpose, and transfer methods.
Cover Downstream Support Before Training Begins
The authorization must address the complete operating model, not just the first training event. If Company B will later support Companies C and D, those activities may involve additional exports of technical data, defense services, or both. Customer support through troubleshooting calls, field service, remote diagnostics, repair instructions, or access to technical portals can be controlled even when no documents are formally delivered.
A single TAA may sometimes cover multiple approved parties and destinations when they are properly disclosed and accepted. Separate agreements, amendments, or other approvals may be needed when the customers, countries, end uses, employee populations, or technical scope differ materially. Hardware licenses are also separate from agreement authorization. A permanent export license for a defense article does not automatically authorize technical training, while a TAA generally does not authorize every shipment of engines, parts, tooling, or components.
Repair must also be distinguished from modification or upgrade work. Returning an engine to its previously approved configuration is generally analyzed differently from enhancing military capability, changing performance, or introducing a new configuration. A work scope that expands during execution can therefore invalidate assumptions made during licensing.
Implement Controls for Data, Personnel, and Engine Movements
Before engaging in ITAR-controlled activity, a U.S. company should determine whether registration with the Directorate of Defense Trade Controls is required. Registration is typically a prerequisite for certain regulated activities, but it is not an export authorization and does not independently permit technical-data transfers or defense services. The company must still obtain and comply with the appropriate agreement, license, exemption, or other approval.
A transaction matrix can clarify the required authorization architecture. It should map every transfer from Company A to Company B, from Company B to each foreign customer, and among employees, subcontractors, freight providers, and technology platforms. Each line should identify the item or information, jurisdiction, classification, transfer method, origin, destination, end user, employee nationality, authorization, and applicable provisos.
Control Execution After Approval
A technology control plan should translate approval conditions into daily operating rules. Access to technical data should be role-based and restricted by nationality, location, project, and need to know. Controls should cover email, cloud storage, collaboration tools, video conferences, mobile devices, printing, visitor access, training rooms, remote maintenance systems, and oral discussions. Nondisclosure agreements support confidentiality but do not replace government authorization.
The compliance team should also maintain attendance records, data-access logs, training acknowledgments, executed agreement documents, shipment records, and evidence that provisos were communicated to all relevant functions. Changes involving a new customer, facility, nationality, subcontractor, country, engine configuration, or work scope should trigger review before activity continues.
Physical engine movements require a parallel analysis. Temporary imports, subsequent exports, permanent imports, customs entries, and electronic export filings may require different authorities. Eligibility for an exemption generally depends on exact facts, including ownership, origin, condition, purpose, duration, and whether the engine will be repaired or modified. U.S. authorization also does not displace Israeli requirements or the import and export laws of the customer countries.
Frequently Asked Questions
How Many Deemed Export Licenses Are Needed for an MRO Training Program?
There is no universal number. One properly scoped TAA may cover a broader project involving several approved parties, employees, and destinations, while separate authorizations may be required for hardware, additional countries, foreign-person employees, or activities outside the agreement. The answer follows the transaction structure rather than a simple person count.
Is Training Controlled If No Technical Documents Are Delivered?
Yes, potentially. Oral instruction, demonstrations, observations, screen sharing, and hands-on training can release controlled technical data or constitute a defense service. Compliance teams should assess what knowledge will be conveyed, not merely whether a drawing or manual changes possession.
Can Trained U.S. Employees Support Foreign Customers Automatically?
No. Authorization to receive training does not necessarily authorize later assistance to foreign customers. Companies C and D, their locations, nationalities, end uses, facilities, and proposed support activities should generally be included in the original authorization or addressed through an amendment or separate approval before support begins.
Does DDTC Registration Replace a TAA or Export License?
No. Registration generally establishes the registrant’s status within the ITAR framework, but it does not approve a transaction. Technical assistance, data transfers, and physical shipments must each be supported by the applicable authorization, exemption, or agreement and performed within its conditions.
How Stable Software Can Help
Turn Complex Authorizations Into Controlled Workflows
Managing an international MRO program requires more than securing an approval. Compliance teams must connect parties, classifications, destinations, employee access, technical data, licenses, agreement provisos, and shipment records throughout the transaction lifecycle. Manual spreadsheets and disconnected inboxes make that relationship difficult to monitor as projects change.
Stable Software helps importers, exporters, and customs brokers centralize trade data, standardize compliance workflows, and improve visibility across international operations. With structured records and automated processes, organizations can identify missing information earlier, maintain stronger audit trails, and coordinate licensing and customs requirements more efficiently. Trade teams evaluating an ITAR-controlled MRO program can use Stable Software to build a more scalable operational foundation while retaining qualified legal and export-control counsel for transaction-specific determinations.
