US ITAR and EAR - Export Control and Data Security
Shipping documents, marking and export filing – US ITAR and EAR - Export Control and Data Security

US ITAR and EAR - Export Control and Data Security ITAR 123.22 and EAR 758.1: File export information on time and report technical data exports to DDTC

What does ITAR 123.22 and EAR 758.1 require?

Every ITAR export of a defense article, including articles transiting the United States, requires electronic export information before export: hardware filings to U.S. Customs and Border Protection at least 8 hours before departure by air or truck and 24 hours before departure by sea or rail, with limited emergency provisions (123.22(a)-(b)(2)). For technical data, the exporter self-validates and reports DSP-5 technical data licence exports directly to DDTC, notifies DDTC before the first export under an agreement, and reports exemption-based technical data exports from a U.S. port with the notification accompanying the shipment (123.22(b)(3)). The EAR requires EEI in AES for tangible exports that need a licence, go to Country Groups E:1 or E:2, are 600-series or 9x515 items, use STA or VEU, or exceed $2,500 per Schedule B number, among other cases (758.1(b)).

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 2 controls across 1 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

  • 758.1 758.1 Electronic Export Information (EEI) filing in AES
  • 758.2 758.2 Automated Export System participation

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Shipping documents, marking and export filing – US ITAR and EAR - Export Control and Data Security

Query this from an agent

The graph holds this control, the 2 it maps to, and the evidence behind each claim, over MCP and REST.