Sky-Watch: aircraft products and an evolving ownership perimeter

Sky-Watch combines a Danish aircraft business with the reporting and market reach of a US listed parent. Its commercial story now extends beyond the RQ-35 Heidrun: an additional aircraft, an internally developed sensor suite and a Dutch support programme create different opportunities for equipment suppliers, software partners and service providers.

The useful starting point is the operating company. Sky-Watch A/S identifies its headquarters in Støvring, Denmark, and separately lists a Singapore company for its Asia-Pacific presence. Its current company information also identifies AIRO Group Holdings as the parent. This is the Danish aircraft manufacturer at sky-watch.com; the similarly named Canadian satellite-data business has a different website and commercial activity.

Danish accounts inside a wider group

Sky-Watch's 2025 annual report records revenue of DKK522.561 million, compared with DKK515.018 million in 2024. Profit for 2025 was DKK149.380 million, and the average number of full-time employees was 118, versus 81 a year earlier. These are the Danish company's figures. Management describes supply-chain restructuring and product adaptations during 2025 as responses to changing requirements, particularly those emerging from Ukraine.

The combination of almost unchanged sales and a larger workforce is more informative than either number alone. It suggests a business spending organisational effort on a changing product and production base. It does not establish how many additional aircraft the extra staff could produce. A supplier evaluating an assembly or testing proposal would therefore want to understand which product generation and delivery programme the work supports, rather than applying the historical revenue figure to a presumed uniform production line.

AIRO's 2025 Form 10-K identifies Sky-Watch as a wholly owned subsidiary and records its acquisition in March 2022. AIRO trades on Nasdaq under AIRO; Sky-Watch A/S is not itself the separately listed issuer. The parent also has activities outside the Danish drone company, making consolidated figures unsuitable substitutes for Sky-Watch's statutory accounts.

This corporate structure matters in a negotiation. An international presentation may use the parent's brand, while manufacturing work, product support or an invoice involves a particular subsidiary. Group ownership can offer access to other capabilities, but responsibility for a proposed delivery should still be tied to the named contracting entity and the specific support package.

A portfolio organised around shared elements

The current product directory divides the offering into aircraft platforms, the Zentra Sensor Suite and Mission Software. RQ-35 Heidrun and RQ-70 Dainn sit within the aircraft category. This organisation presents software and sensing as parts of a continuing product architecture, rather than treating every aircraft sale as an isolated airframe transaction.

Commercially, shared elements can connect several otherwise separate purchasing decisions. A customer adding another aircraft type may also need software support, replacement sensor assemblies and updated training material. A component manufacturer may encounter common requirements across more than one platform. The relevant question is whether commonality exists in the supplied configuration and contractual support arrangement; the product-family diagram alone cannot establish interchangeability between individual delivered systems.

Sky-Watch's platform overview describes a shared ground-control architecture, payload logic and software approach across the RQ family. The business implication is a potential common support base. It also creates a need to manage configuration changes carefully: an update introduced for one aircraft must have a clearly stated applicability to the other, especially where customers operate different purchase generations.

A hypothetical electronics supplier illustrates the distinction. Selling a replacement module against a stable drawing is one proposition. Supporting a module that is expected to evolve alongside two aircraft and their software is another. The latter needs an agreed process for engineering changes, retention of earlier configurations and pricing for small replacement batches. Those commercial responsibilities can be more significant than the first production quantity.

Zentra moves part of the supply chain inside

In a 9 July 2026 delivery announcement, AIRO reported completion of an order containing the first operational deployment of Zentra on RQ-35. The delivery occurred in the second quarter. The release identifies Sky-Watch as the suite's developer but does not name the customer or disclose that order's value.

That is a stronger commercial milestone than a product unveiling because it describes a delivered configuration. It also changes how an external imaging supplier should interpret the account. A company developing its own integrated suite may still purchase constituent hardware, manufacturing services or specialist engineering. However, the appropriate discussion is about the boundary of the internally owned system, not an assumption that the manufacturer needs an entire third-party payload.

For a buyer, internal ownership concentrates responsibility for coordinating aircraft and sensor changes. The benefit must be assessed through the actual support offer: replacement arrangements, repair responsibility and software compatibility across the installed fleet. A proprietary suite can simplify accountability while also making the manufacturer's continuing support commitment more important to the customer.

Dutch procurement connects deliveries with service

Sky-Watch's June 2026 newsroom announcement says the Netherlands Ministry of Defence selected RQ-35 following a competitive procurement managed by COMMIT. It describes deliveries during 2026 and a seven-year support agreement. The same newsroom dates the RQ-70 introduction to Eurosatory in June. These are distinct milestones: an announced customer programme for one platform and the introduction of another.

The support term gives the Dutch programme particular commercial significance. It extends the supplier relationship beyond delivery into a period in which components, software and staff knowledge may change. For an industry partner, a repair capability or documentation service could therefore be relevant to the continuing programme even when it has no role in the first aircraft shipment. Whether such work is subcontracted remains a separate commercial question.

A service provider assessing the opportunity should build its proposal around the installed configuration and support responsibilities. A plan for repair turnaround has a different cost structure from holding replacement equipment or maintaining training records. Combining those into an unspecified support fee would obscure the activity that produces value and the party carrying inventory risk.

Read the parent's backlog definition carefully

AIRO's 13 August 2026 results report a US$163 million drones backlog at 30 June. Its definition includes both definitive customer arrangements and certain NATO-country funding allocations awaiting administrative completion. It excludes US backlog and uses a stated currency-conversion date. This is a parent-defined measure of prospective business, not Sky-Watch's recognised revenue or a list of completed contracts.

The same results announcement reports Blue UAS certification for RQ-35. That is a company-reported programme milestone for the named platform; it should be kept separate from the launch of RQ-70 and from any assumption that every configuration offered internationally has identical approval status.

The definition is useful precisely because it explains why a commercial pipeline can move differently from shipments. A supplier planning materials needs a purchase schedule attached to its own order, even where the customer's investor presentation shows substantial anticipated activity. Conversely, delayed recognition in one quarter does not necessarily identify a lost programme; contract timing and customer acceptance can change the reporting pattern.

Sky-Watch can be compared with Quantum Systems' manufacturing and international programme structure when assessing how an aircraft supplier scales across markets. Delair's product and customer record provides another reference for separating an established platform from adjacent development activity. The useful comparison is the organisation of delivery, software and sustained support, with each company's financial and ownership figures kept within their own reporting boundaries.