How to Test Your Defense System in Ukraine

Every wasted testing programme we have seen started the same way: a system went to Ukraine because someone senior wanted it to have been there. The programme produced footage, a few enthusiastic operator quotes and nothing a procurement office could act on. Before anything moves, settle two questions.

The first is what kind of proof you need. Environmental and electromagnetic qualification against the MIL-STD family is a laboratory job with a certificate at the end of it, and it belongs upstream of any field work — deploying an unqualified system means the failures you meet are the ones you could have found on a bench. Operational evidence is a different product entirely, and what battlefield testing actually proves sets out precisely where the line falls.

The second is who the result is for. If the audience is your own engineering roadmap and a foothold in the Ukrainian market, the state platform is built for that. If the audience is a board, an investor or an allied tender, you need an evaluation you commission and own. That choice has its own guide — independent T&E versus Brave1’s “Test in Ukraine” — and everything below applies whichever way you go.

The third is whether the system will function here at all — a question worth answering before a licence is filed, not after a crate lands. The most common wasted trip is a platform that flies clean on a home range and loses its link the moment it meets dense electronic warfare; a video or control link that is analog, or simply never hardened against jamming, is the usual culprit. A short remote assessment against your own specifications — link type, frequency plan, autonomy fallback — separates “ship it now” from “fix the link first,” and the fix is far cheaper than the export licence and freight it saves.

Scoping is where a test becomes evidence or fails to. It happens under a mutual non-disclosure agreement signed before technical detail changes hands, and it produces a written evaluation plan. Six things have to be on paper before a crate is packed.

1. 1The mission profile. Not “an ISR drone” but the sortie you are claiming: range, altitude band, payload, launch and recovery method, expected electronic-warfare environment, day or night, and the sector type. A system that performs on a long static front with dense jamming tells you little about a maritime approach.
2. 2The measures. What is being counted — sorties attempted, targets acquired, link held under jamming, time to first fix, recovery rate, mean time between failures. Each measure needs a definition an outsider would apply the same way.
3. 3The failure criteria. Agreed in advance, because a criterion written after the data arrives is a marketing decision. State what counts as a mission failure, a system failure and an operator error, and who adjudicates the difference.
4. 4The sample. How many airframes or units, how many sorties, across how many crews and sectors. Thirty sorties by one crew in one sector is a story; the same thirty across three crews and two sectors starts to be a pattern.
5. 5Training and support. Who trains the operators, in what language, with what documentation, and what spares and consumables travel with the system. Underestimating this is the most common reason a programme loses its first two weeks.
6. 6Ownership and disclosure. Who holds the raw data, who holds the report, what may be published, what is anonymised, and what happens to the report if the relationship ends. Settle this before the first sortie, because after it the answer is a negotiation.

One clause deserves its own line: what happens to hardware that does not come back. Systems are damaged and destroyed in this work — that is the point of it — and the programme needs a written position on write-offs, on the disposal or return of remains, and on whether a destroyed unit counts against the sample or is replaced. Brave1’s platform provides guidance on the handling of damaged and destroyed equipment as part of its regulatory support, and an independent evaluation should carry the equivalent clause in the contract.

This is the step foreign teams consistently underestimate. Moving a defense article into Ukraine for evaluation is a licensed international transfer at both ends, and the two authorisations are independent of each other. Neither is difficult; both take time, and they run on other people’s calendars.

Classify the item first, because the classification decides which US regime applies and therefore which form you file. A US export runs the order of review: an item on the US Munitions List is a defense article controlled by the State Department’s DDTC under ITAR; if it is not on the USML you check the Commerce Control List, and something subject to the EAR but not listed there is EAR99, controlled by the Commerce Department’s BIS. The two regimes carry different forms, timelines and end-use rules, and a Commodity Jurisdiction request to DDTC — or a classification request to BIS — buys certainty when the boundary is unclear. Treating a dual-use item as ITAR, or the reverse, is the first and most expensive error in this step.

Your side. A US applicant temporarily exporting an unclassified defense article for demonstration or testing files a DSP-73 with the Directorate of Defense Trade Controls. The licence is built for exactly this case: the article goes out for a defined period of under four years, it comes back, and title does not transfer while it is abroad. An application has to state one end-use and is generally limited to a single geographic region. An EU applicant works to Regulation (EU) 2021/821 for dual-use items and to national licensing under the EU Common Position for items on the Common Military List, which means the authority you deal with is your own member state’s.

The Ukrainian side. Ukraine controls this through the State Export Control Service, which issues a conclusion — a distinct instrument from an import permit — authorising temporary import of military or dual-use goods for demonstration at exhibitions, advertising or the conduct of tests, without transfer of ownership. The applicant must be registered with the Service as a subject of international transfers, which in practice means a Ukrainian entity files it: your evaluator, your industrial partner or a designated importer. The published administrative service lists a term of 15 calendar days for a conclusion whose stated purpose is demonstration or testing, against 30 for the general case, and the state fee is nominal — tens of hryvnia for a single-use document.

The range is a controlled environment where a result can be reproduced and a failure can be explained. It exists in the sequence for three reasons, and none of them is ceremony. It confirms the system survived shipping and reassembly. It gives you a performance baseline measured in conditions you control, so that any later degradation at the front can be attributed to something rather than argued about. And it is where operator training actually lands, because a crew that first meets your system in a contested sector is not testing your system, it is testing its own learning curve.

Ukraine has dedicated proving ranges open to Ukrainian and allied systems, including one in the west of the country well away from the contact line. Range work also gives you a benchmark: against a live population of well over a hundred Ukrainian manufacturers producing in the same categories, a capability figure means something. In isolation it is a number on a datasheet.

Keep the range phase short and instrumented. Its output is a baseline data set and a trained crew, and both are inputs to the phase that follows.

The front is where the variable no laboratory models is introduced: an opponent with a budget who is actively working to defeat your system. In Ukraine that opponent iterates fast. A fielded jamming approach is generally expected to be countered or evaded within about three weeks, and RUSI recorded a precision munition whose effectiveness fell from roughly 70% in 2022 to about 8% by 2025 without the munition changing at all — the environment around it was redesigned. The band under continuous drone observation and fire runs 20 to 25 kilometres on both sides of the contact line, and the commander of Ukraine’s 7th Airborne Assault Corps expects it to reach 30 by the end of 2026.

Four things determine whether this phase produces evidence or anecdote.

• The unit has to fly the mission you are claiming. A reconnaissance company and a strike company will use the same airframe differently and will report different things. Match the unit to the mission profile written at scoping.
• Conditions get recorded, every time. Date, sector, weather, the electronic-warfare picture, operator experience. An undated result is close to useless for anything touching the electromagnetic spectrum, because the environment it describes has moved on.
• Failures get counted alongside successes. A report with no failures in it is read by procurement officers as a report with no methodology in it.
• Somebody neutral is present. Operator feedback is invaluable and it is also subjective; an evaluator whose job is the measurement rather than the mission is what makes the resulting numbers portable.

Expect attrition, and expect the useful findings to be uncomfortable. The systems that come back from this phase with a clean sheet are usually the ones that were never really exposed.

Documentation written afterwards is reconstruction. Documentation written during is evidence. The record that survives contact with a procurement board has a predictable shape: the evaluation plan agreed at scoping, a sortie log with conditions attached to each entry, a failure register with adjudications, the raw measures, and a change log of every modification made to the system mid-programme.

That last item is the one teams skip and later regret. Field modifications are normal and often the most valuable output of the whole exercise, but a result measured on a modified system and reported against the original configuration is not a result. Log the change, note the sortie it took effect from, and segment the data accordingly.

Handle classification and operational security as you go rather than at write-up. Unit identities, sector geometry, dates tied to specific operations and anything that would reveal a tactic all need anonymising at the point of capture. Doing it at the end means someone has to guess what mattered.

The output of a testing programme is not a data set. It is a document that changes a decision, and there are two audiences for it that want different things from the same evidence.

For your engineers, the redirect.What the battlefield rewarded, what it punished, what the next iteration should carry and — usually more valuable — which planned features the evidence says are not worth funding. This is the part that protects an R&D budget, because a programme that discovers a design assumption is wrong at version two has bought itself the money it would have spent being wrong at version four.

For buyers and boards, the white paper. The same findings translated into the doctrine and evaluation vocabulary an allied procurement officer uses, with methodology stated, conditions described, failures included and operational specifics anonymised so the document can travel. A white paper that can be attached to a tender response or put in front of an investment committee has to be legible to people who were not there.

Whether that document is yours to hold is decided by the route, and it is the reason the route question sits at step zero rather than here. Once the paper exists, the next moves open up quickly: an allied buyer procuring the validated system, a manufacturing footprint, or the wider set of routes into Ukraine’s defense market that validation is often the first step of.

There is no single answer, but the shape is consistent enough to plan against. Scoping and contracting occupy the first weeks and are largely within your control. Licensing runs in parallel and is not: the stated review periods are short, and the preparation that precedes them — end-use documentation, the Ukrainian counterparty’s paperwork, translations, certified copies — is what sets the real date. Shipping and customs clearance follow. Range work and crew training are measured in days once the hardware is in country. The frontline phase is measured against sortie count rather than calendar days, and sortie count is a function of weather, sector activity and the unit’s own operational tempo, none of which you schedule.

Two planning rules follow. Start the licensing conversation on day one, in parallel with scoping, because it is the critical path in almost every programme. And treat the evidence as perishable once you have it: electromagnetic findings in particular describe an environment that is being actively redesigned, so a result that sits unused for a year is a historical document.

• Deploying before qualification. The failures you find are the ones a bench would have caught, and the interesting questions never get asked.
• Starting the licensing late. The single most common cause of a programme slipping a quarter, and the most avoidable.
• No written failure criteria. Without them, every ambiguous outcome is resolved in the direction the person writing the report prefers.
• One crew, one sector, one fortnight. Too small a sample to distinguish a system property from a local condition.
• Sending hardware without spares, consumables or documentation. The programme spends its first weeks solving logistics instead of collecting data.
• Leaving ownership of the report unsettled. The awkward conversation arrives at exactly the moment the result becomes commercially valuable.
• Treating combat use as export clearance. Having been used in Ukraine says nothing about what your own government will license you to sell, and the two questions get confused routinely.

Each of these is cheap to fix at the planning stage and expensive to fix afterwards, which is a good argument for spending real time on step zero.