BIS removed NS controls from qualifying sub-three-hour drones, but classification, military design, end use, and destination still determine licensing.
The Bureau of Industry and Security removed the NS control from qualifying sub-three-hour drones. It did not make them broadly NLR.
NLR is a transaction result, not a product attribute. It applies when the EAR imposes no license requirement on the item, destination, parties, or end use. Change one of those facts and the result may change.
Commercial systems often compress that conclusion into a model label. A record may say NLR eligible or exportable without a license. Both are too broad. One configuration may fall only within 9A012.a.1, while the same airframe with a different sensor is also described by another subparagraph. The aircraft may be shipped NLR to one civil customer and require a license when a covered military end user or a Part 746 destination enters the order.
BIS said many civilian UAVs and certain associated software and technology may now move NLR to most destinations. The operative product-level statement is more precise. An item controlled only under 9A012.a.1 no longer carries an NS reason for control. The transaction still needs a release decision.
Revised 9A012.a covers UAVs or unmanned airships designed for controlled flight outside the operator's direct natural vision and meeting at least one listed technical parameter. Paragraph a.1 now captures those with maximum endurance below three hours. Paragraph a.2 captures those at three hours or more.
The number is not an ordinary mission estimate. The Technical Notes direct exporters to calculate endurance under International Standard Atmosphere conditions at sea level in zero wind. A brochure claim, expected battery life at a customer's site, firmware-limited setting, and tested maximum capability are not necessarily interchangeable. The classification file needs the engineering basis for the value it uses.
Endurance is only the first test. A UAV capable of a maximum range of at least 300 kilometers remains subject to MT1 regardless of payload. A UAV meeting the parameters of 9A120 also remains MT controlled. Range and endurance should be documented separately because a platform can remain below three hours and still cross the MT range threshold.
Installed equipment creates another classification test. Paragraphs 9A012.a.3 through a.5 separately cover UAVs incorporating specified thermal imaging or radar equipment, lasers, or inertial equipment using controlled accelerometers or gyroscopes. Those subparagraphs retain NS1 and AT1.
That makes removable payloads, mission kits, integrated navigation equipment, and customer modifications part of the licensing analysis. A short-endurance UAV that is also described by 9A012.a.3, a.4, or a.5 cannot be treated as controlled only under a.1. The controls applicable to the additional paragraph also apply.
Software and technology require a separate item-level analysis. BIS removed the NS reason from specified 9D001, 9D002, 9D004, and 9E001 items associated with 9A012.a.1. AT1 remains, and MT1 continues for technology related to MT-controlled UAVs. The software file must identify the hardware and function it supports instead of inheriting a result from a commercial product family.
The revised 9A012 license requirements are uneven by design. NS1 applies to the entry except for a.1. AT1 applies to the entire entry. MT1 applies to UAVs and remotely piloted vehicles with at least 300 kilometers of maximum range and to UAVs meeting 9A120.
A qualifying aircraft reaches the new AT1-only baseline only after the reviewer rules out the separate NS-controlled equipment paragraphs and the MT tests. The phrase sub-three-hour does not do that work.
The final rule does not settle every configurable-range question. Until BIS provides more guidance, a reviewer should document whether a software limit changes maximum capability, whether it can be altered, and whether another control station, data link, fuel load, or flight profile changes the result. The file should record the governing configuration rather than the most convenient operating setting.
Aircraft at three hours or more carry NS1 and AT1, with MT1 added when the range or 9A120 test is met. Specified sensor and navigation configurations keep their own NS treatment regardless of endurance.
The order review should keep product classification apart from transaction authorization.
| Question | Exact stop condition | Evidence required | Available route |
|---|---|---|---|
| Is the UAV described in USML Category VIII | The item is a defense article | Jurisdiction analysis, technical data, shipped configuration | Follow the ITAR path |
| Was a non-USML UAV specially designed for military use | The section 772.1 analysis points to 9A610.a | Military customer requirements, design history, civil comparison, feature matrix | Apply 9A610 controls and test any available authorization |
| Does the complete configuration fall only in 9A012.a.1 | Another 9A012 paragraph or ECCN also describes it | Endurance calculation, installed and optional equipment list, classification memorandum | Use the AT1 baseline only when a.1 is the sole applicable 9A012 paragraph |
| Does the 300 km test or 9A120 apply | MT1 attaches | Maximum range method, payload assumptions, propulsion and link configuration | Apply the MT license requirement or a valid exception |
| Does an applicable reason for control require a license to the destination | NS, RS, MT, AT, or UN produces a Country Chart or destination restriction | ECCN paragraph, reasons for control, Country Chart and destination analysis | NLR only when every applicable reason clears |
| Does Part 744 apply | A party, end use, end user, knowledge standard, or BIS notice triggers a license | Party roles and ownership, end-use statement, military-use review, red-flag resolution | Follow the specific Part 744 license requirement |
| Does Part 746 apply | An embargo or special destination control displaces the ordinary result | Ultimate destination, routing, in-country transfer and access locations | Follow the specific Part 746 authorization and exception limits |
| Does software or technology receive the same relief | The item is not limited to the 9A012.a.1-related scope or remains MT controlled | Hardware relationship, software function, technology scope, recipient access | Apply its own 9D or 9E classification and transaction screens |
| Is STA proposed for 9A610.a | Any A:5, payload-range, section 740.20(g), 600-series, party, use, notice, or record condition fails | BIS item approval, party locations and nationalities, ultimate use and user, consignee statement, notices and records | Use STA only within the approved item and transaction scope |
Do not assign NLR at the product-family level. Record the result for the shipped configuration and the named transaction.
BIS paired the removal of NS controls with a deliberate addition to BIS Part 744 military end-use and end-user controls. The final rule adds 9A012.a.1 and specified related software and technology to supplement no. 2 to Part 744, the list used for the military end-use and military end-user controls in section 744.21.
The additions cover the a.1 UAVs as well as specified development software under 9D001, production software under 9D002, other software under 9D004, and development technology under 9E001. The listed scope preserves military screening even when the ordinary classification and destination analysis would otherwise produce NLR.
BIS end-use and end-user guidance states the broader rule plainly. Part 744 restrictions can apply when no license would otherwise be required because of the item's classification or destination.
A list screen alone is not enough. BIS says the Military End-User List is not exhaustive, so exporters must evaluate whether an unlisted party meets the regulatory definition. The intended mission, the customer's functions, intermediaries, ownership, delivery location, and known diversion indicators can all matter.
The party record should also identify transaction roles. BIS guidance notes that restrictions can attach when a listed person is the applicant, purchaser, or consignee, not only the end user or recipient. A screen that stores one customer name without the legal names, addresses, ownership, and role of each party cannot support the Part 744 conclusion. Distributor and integration arrangements need the same role map as direct sales.
Refresh the screen before export, reexport, transfer, or release whenever the end user, integration partner, mission, payload, destination, or access path changes. Later software updates, technical releases, replacement payloads, and remote access also need their own treatment. Clearance of the original hardware shipment does not settle them.
A favorable Country Chart result does not override BIS Part 746 embargo and destination restrictions. An intermediary in an eligible country does not cure a prohibited onward transaction. The record should cover the ultimate destination, in-country transfers, intermediate routing, end-user location, and places where controlled software or technology will be accessed.
Part 746 can also restrict a license exception that otherwise appears available. Product and destination status should therefore remain separate fields in the release record. Changing one should reopen the other instead of inheriting an old NLR label.
The final rule also changes the classification boundary for military UAVs that are not on the USML. BIS concluded that some of those aircraft now warrant control under 9A610.a.
The practical test is broader than a product name or sales channel. BIS said a non-USML UAV designed or modified to meet a military customer's needs by adding at least one feature or capability that would not also be included for civil or commercial purposes should be reviewed under 9A610.a and the section 772.1 definition of specially designed. The significance of the feature is not the deciding factor.
Product history now carries regulatory weight. Customer requirements, military-only features, engineering changes, configuration baselines, and the relationship between civil and military variants may decide whether an aircraft belongs in 9A012 or 9A610.a.
A civilian brochure is weak evidence when internal design records show a military requirement. The reverse is also true. A sale to a government body does not by itself establish military design. The file should connect the customer's requirements to the engineering choices and then apply the regulatory definition.
A 9A610.a aircraft does not receive the AT-only baseline available to a qualifying 9A012.a.1 item. It carries NS1, RS1, AT1, and UN controls, with MT1 added when the UAV or RPV has a maximum range of at least 300 kilometers regardless of payload. The rule also created 9A610.y.33 for specified lower-sensitivity parts and accessories, but that paragraph does not decide the classification of the aircraft or of parts that are not listed there.
STA may be available under BIS Part 740 License Exception STA conditions for qualifying aircraft to Country Group A:5 when they cannot deliver at least 500 kilograms of payload to a range of at least 300 kilometers. For 9A610.a, that technical and destination test is not enough. BIS must have made the specific end item eligible under section 740.20(g).
The two range tests should remain separate. MT1 attaches at 300 kilometers of maximum range regardless of payload. The STA exclusion pairs a 500-kilogram payload with 300 kilometers of range. A UAV can be MT controlled without meeting that particular STA exclusion, so one calculation cannot stand in for the other.
Even after BIS approval, the transaction must satisfy the 600-series restrictions in section 740.20(b)(3). Those include permitted locations and nationalities, a qualifying ultimate governmental or otherwise authorized end use and end user, completion of the authorized 600-series chain, and any applicable Major Defense Equipment value limit. Section 740.20(d) separately requires the ECCN disclosure, prior consignee statement, shipment notification, and records. Parts 744 and 746 still apply.
The distinction is consistent with Traverse's earlier analysis of the BIS UAE A:5 final rule at 91 FR 43034. A country-group change can open an STA path without clearing the item, recipient, use, or transaction.
The rule calls for three linked records.
The engineering configuration record should support endurance and range under the applicable Technical Notes. It should identify installed and optional equipment, firmware state, control station, data link, propulsion assumptions, and the hardware relationships for software and technology. A model name is not enough when sensors or mission kits change the paragraph.
The jurisdiction and classification record should move in order from USML Category VIII to military design under 9A610 and then to the exact 9A012 paragraph. It should connect customer requirements and engineering changes to the section 772.1 analysis. The result should state every applicable reason for control instead of stopping at the ECCN number.
The transaction release record should resolve the relevant Country Chart requirements and Parts 744 and 746 for the named parties, use, destination, and route. For 9A610.a STA, it should identify the BIS-approved end item, every party's eligible location and nationality, the qualifying ultimate end use and end user, section 740.20(g) approval, the 500-kilogram and 300-kilometer restriction, completion of the 600-series chain, any applicable Major Defense Equipment limit, and all consignee-statement, notice, reporting, and recordkeeping conditions.
The three records need shared change triggers. Firmware, payload, customer, mission, routing, destination, or access changes should reopen the affected analysis before the next export, reexport, transfer, or release.
Removing NS1 eliminates one licensing layer, not the need for a defensible release record. For a qualifying 9A012.a.1 configuration, the exporter must still document why the remaining capability, military-design, end-use, end-user, and destination controls do not require a license for the transaction.
Foreign availability helps explain the policy direction in the final rule and Executive Order 14307 on American drone exports. It is not transaction authority. BIS Part 768 foreign-availability procedure has a separate process for formal determinations, and the final rule does not state that BIS made one through that process.
Endurance alone cannot establish the result. A short-endurance aircraft with controlled range, equipment, military design, destination, parties, or end use can remain licensable. A commercial label cannot establish 9A012.a.1, and the Military End-User List cannot establish that an unlisted customer is outside section 744.21.
Future BIS guidance on configurable range, removable payloads, or military-specific features could change documentation practice. Amendments to 9A012, 9A610, section 744.21, supplement no. 2 to Part 744, or Part 746 could change the governing test. State Department changes to USML Category VIII could move the jurisdictional boundary.
For now, exporters with genuine civil platforms can remove an NS licensing burden from qualifying configurations. Turning that relief into faster order acceptance requires proof of the paragraph, the remaining capability controls, military design, parties, end use, and destination.
The license gate did not disappear. It moved closer to the facts that distinguish one configuration, customer, and mission from another.
Today's analysis is open to everyone. A free account opens the full archive and full tool output. No card required.