Read our analysis: Drone Warfare
Legal advice for unmanned aircraft systems and the businesses that develop supply and operate them
Our Drone Warfare publication examines how unmanned technology brings together aviation regulation, technology law, international trade and Polish law. It illustrates the approach we bring to a drone project: understanding the system, its intended activities and the commercial relationships together. [S01]
At KG Legal Kiełtyka Gładkowski, we bring our technology, regulatory, intellectual property and transactional practice to the legal needs of the drone sector. We can support manufacturers, software developers, system integrators, operators, infrastructure owners and investors throughout development, market entry, deployment and expansion.
An unmanned aircraft system includes the aircraft and the equipment needed to control it remotely. A commercial project may also involve sensors, communications, cloud services, analytics, training datasets and customer platforms. Each element can carry different rights, obligations and liabilities. Our work connects those elements into a legal structure that supports the client’s intended business. [S04]
The firm’s published profiles describe advice on dual-use technology transfers involving technical datasets and algorithmic assets, together with software development, maintenance and API licensing. The Legal 500 editorial profile also identifies our work in AI, cybersecurity and data protection. These capabilities provide a practical foundation for advising businesses whose value lies in the combination of equipment, code and information. [S02] [S03]
We advise on Polish and EU law and coordinate foreign-law input where a project involves other jurisdictions. Our drone services apply that experience to the particular product, operating model and supply chain. We connect the legal workstreams so that a software licence, operational permission, cloud arrangement and equipment contract support the same commercial project.
We begin by identifying what the client is developing or supplying, who will operate it, where it will be used and how revenue will be generated. Selling an aircraft, licensing flight-control software, providing inspections and operating a fleet through a subscription service create different responsibilities.
We prepare a written map of the relevant permissions, product rules, contractual roles, data flows and trade restrictions. The map identifies the evidence required, the responsible entity and the sequence of decisions before testing, launch or a transaction. Changes to payloads, autonomy, customers or geographical markets can then be assessed against that map.
The output is a decision-making tool for management, engineering, operations and sales. It identifies which entity must act, what can be documented contractually, where an authority decision is needed and which changes require a fresh assessment. We can then prepare the applications, contracts and internal procedures identified in that review.
We assess the appropriate route under the EU open, specific and certified operational categories. Product class markings and operational categories answer different questions; the applicable route depends on the proposed activity and its risks. For specific-category projects, the route may involve an operational authorisation, a declaration under a standard scenario or the privileges of a light UAS operator certificate. [S04]
Our services include legal support for operator registration, remote-pilot requirements, operational authorisation applications, cross-border operations, geographical-zone access and engagement with the Polish Civil Aviation Authority and relevant airspace bodies. We work with the client’s operational and engineering specialists on the legal elements of risk assessments and supporting documentation.
For operations beyond visual line of sight, automated inspections, drone-in-a-box deployments and fleet services, we examine the full operating model: supervision, locations, subcontractors, maintenance, communications and contingency responsibilities. We also address access to launch and landing sites and the relationship between aviation permissions and sector-specific permissions.
In Poland, we distinguish operator registration, pilot competence, operational authorisation, geographical-zone conditions and flight notification through DroneTower. We identify which requirements apply to the operation and how they interact. [S05] [S06]
We also advise on U-space and the digital services supporting drone operations. This can include certification requirements for U-space and common information service providers where applicable, obligations in designated airspace, service and data-sharing agreements, and information-security and continuity responsibilities. [S33]
For public-authority and defence projects, we assess whether the particular activity falls within an exclusion from the EU civil aviation framework and which national rules then apply. A public-sector customer or a security-related purpose does not by itself answer that question. We also distinguish the client’s role as an operator from its roles as a manufacturer, software supplier or contracted service provider. [S04] [S06]
We help manufacturers, importers and distributors establish which product requirements apply to the aircraft, controller, payload and associated equipment. The review can cover UAS product rules, conformity assessment, CE marking, declarations, technical documentation, instructions, traceability and market-surveillance responsibilities. Certification requirements must be assessed for the particular system and intended operation. [S04]
Radio equipment, connectivity, batteries and electronic components can introduce additional obligations. We identify the applicable radio and spectrum framework, cybersecurity requirements, battery and electronic-equipment rules, and any relevant exemptions. The assessment takes account of how components are integrated and of the role the client assumes in the supply chain. [S08] [S15] [S35]
We support supplier documentation, compliance warranties, change control, product withdrawals and corrective action. For outsourced manufacturing, we allocate responsibility for component substitutions, test evidence, production changes and access to records.
We help clients establish and protect rights in flight-control software, embedded firmware, interfaces, applications, designs, documentation and analytical tools. Our work includes ownership reviews, employee and contractor arrangements, assignments, patent and design strategy coordinated with the appropriate specialists, trade-secret protection and software licence design. We distinguish copyright in code and documentation from the possible protection of technical inventions, databases and industrial designs. [S23] [S24] [S34]
Licences should reflect how the system will be used. We address permitted users, devices and territories; modification and integration rights; access to source code; maintenance; security updates; sublicensing; and continuity if a supplier fails. Where a solution combines proprietary and open-source components, we review the relevant licences and distribution model.
For joint development, we distinguish existing intellectual property from project results and agree rights to improvements, derivative developments and commercial exploitation. We also address access, permitted use and exploitation of test results, telemetry and configurations, together with ownership of any protectable outputs. These arrangements help prevent dependence on a supplier whose legal rights do not match the customer’s operational needs.
Drone services can generate imagery, location information, telemetry, inspection results and datasets used to improve software. We identify which information constitutes personal data, who acts as controller or processor, the purpose and legal basis for processing, and whether a data protection impact assessment is required. Relevant work includes transparency, retention, access requests, processor agreements and privacy measures designed into the service. [S12] For public-authority operations, we distinguish GDPR processing from any applicable law-enforcement or national-security regime.
We structure rights to access, use, disclose and monetise operational data, taking account of contracts, intellectual property, confidentiality and the EU Data Act. A contractual allocation of data rights must respect statutory access rights and restrictions. We also assess rights to use customer material for model training, the origin of training datasets and the treatment of personal information in models and outputs. [S13] [S14]
For cloud platforms and distributed development teams, we map hosting locations, subprocessors, support access and transfers. GDPR transfer requirements, contractual security commitments and export controls are assessed separately because the same access arrangement can raise more than one legal issue. We draft cloud and SaaS terms, data-processing and data-sharing arrangements, transfer documentation and exit provisions.
We assess whether a function is an AI system, the client’s role in supplying or deploying it, and the rules applicable to its intended purpose. A drone using AI is not automatically classified as high-risk. The analysis must consider the AI Act’s classification criteria, the relationship with aviation product legislation and any relevant exclusion. [S09] [S10]
We help structure provider and deployer responsibilities, technical-documentation commitments, oversight arrangements, logging, incident escalation and change management. The assessment extends to third-party models, software updates and modifications that change the intended purpose or legal role of the parties.
For systems offered to both civil and defence customers, we document the relevant purposes and assess the boundary of the military, defence and national-security exclusion. A mixed market requires a differentiated analysis. We also distinguish legal obligations already applicable from requirements with a later application date. [S09] [S11]
We assess cybersecurity obligations at both product and organisation level. The Cyber Resilience Act, radio-equipment requirements and Poland’s implementation of NIS2 can affect different participants for different reasons. Coverage depends on the product, activity, size and applicable exclusions; supplying technology to a regulated customer can also create contractual requirements. [S08] [S15] [S16]
Our services include scope assessments, supplier-security terms, vulnerability-management responsibilities, incident-response procedures and legal support for reporting. We align software support periods, update commitments, access controls and subcontractor obligations with the operating model. For critical services, we address continuity, recovery, audit access, replacement suppliers and the export of data when a contract ends.
We draft and negotiate equipment sales, leasing, fleet-service, inspection, mapping, integration and maintenance agreements. The contracts address the deliverable the customer expects, acceptance criteria, installation, training, operating responsibility, availability, updates and remedies when performance falls short.
For manufacturers and suppliers, we prepare OEM, contract-manufacturing, reseller, agency and distribution arrangements. We review territory and customer restrictions, online sales, warranty handling, repairs, spare parts and competition-law constraints. [S29]
Technology schedules should match the regulatory allocation. A customer who operates the drone, a supplier who hosts the platform and a developer who updates the model may each control different risks. We translate those responsibilities into contract terms, insurance requirements, evidence obligations and workable escalation procedures.
We can support the legal assessment and procurement of detection, identification and counter-drone systems for airports, energy assets, industrial sites and other protected locations. The analysis addresses the proposed measure, the operator’s legal status, authorised personnel, notifications, data processing and responsibility for interference or other damage.
Polish law allows critical-infrastructure operators, in specified circumstances, to decide on the permissibility of using telecommunications-disruption devices for activities carried out by specialist armed security personnel. Its detailed conditions and public-authority oversight matter to system design and procurement. Technical availability alone does not establish a right to use a countermeasure. [S07]
Our work includes authority and permission assessments, service and supplier contracts, operating procedures, incident documentation and liability allocation. We coordinate the aviation, electronic-communications, security and critical-infrastructure aspects of the project.
We examine whether the aircraft, payloads, components, software or technology are controlled dual-use items, military items or subject to sanctions. The analysis considers technical specifications, destinations, counterparties and end use. Controlled transfers can include access to software or technical information from outside the EU, depending on the applicable rules. Military-item classification, a business concession and a transaction authorisation are separate questions. [S17] [S18] [S19] [S20]
We help structure import and export procedures, customs classification, origin and valuation, delivery terms, temporary movements for testing and repair, and documentary responsibilities. We also assess the tax treatment of equipment supplies, software licences and services, including VAT, withholding tax, transfer pricing and available research incentives where the conditions are met. [S21] [S22]
For international demonstrations, testing, repairs and after-sales support, we coordinate permissions, the customs procedure, insurance, ownership and return obligations. The same transaction may require a technical export-control classification and a different customs tariff classification. A delivery term or a contractual compliance clause does not replace the required legal analysis. [S17] [S18] [S21]
We assess contractual, product and operational liability across the manufacturer, software supplier, integrator, operator and customer. The review considers physical injury, property damage, defective data, service interruption, privacy infringements and cybersecurity incidents.
Our contract work addresses warranties, liability limits, indemnities, remedies, evidence preservation and responsibility for updates or unauthorised modifications. Insurance reviews consider the applicable compulsory cover and the actual activities, territories and exclusions in the policy, including Poland’s compulsory UAS insurance rules. We also support regulatory proceedings, contractual disputes and claims involving technology performance. [S06] [S25] [S32]
Where an incident occurs, a useful legal response depends on records of the product version, operating conditions, maintenance and decisions made by the parties. We build those evidence requirements into contracts and procedures before a dispute arises.
For manufacturers and software suppliers, we assess the transition to the new EU product-liability framework alongside the national rules applicable to the product and the incident. Contractual risk allocation and insurance must be considered separately from liability towards an injured third party. [S25]
We support the legal aspects of investment rounds, acquisitions, joint ventures and commercial partnerships involving drone businesses. Due diligence examines intellectual property, product and operational permissions, data rights, export controls, cybersecurity, key contracts and dependence on suppliers.
For public and defence opportunities, we assess the procurement route, participation requirements, consortium structure and rights to project results. Funding eligibility, ownership and control restrictions, reporting duties and repayment risks are reviewed against the actual programme and call. We also assess relevant investment-screening requirements and coordinate tax structuring. [S26] [S27] [S28]
The practice can support energy and utilities, renewable infrastructure, construction and surveying, agriculture and environmental monitoring, logistics and ports, emergency services, medical logistics, industrial inspection, media and security. Each sector adds its own operational and contractual requirements.
For example, agricultural spraying requires a separate assessment of pesticide and environmental rules; medical or dangerous-goods transport requires a review of the payload and delivery chain; infrastructure inspection raises questions about site access, confidential information and service continuity. These sector rules are considered alongside the aviation permissions. [S30]
We can begin with a legal feasibility review of the proposed system and business model. The output is a prioritised requirements map, an authority and permission schedule, a contract plan and a list of decisions needed before development, launch, deployment or investment.
To scope the work, we ask for the system description, intended operations, locations, target customers, supply chain, software and data arrangements, and the planned timetable. This allows the legal work to follow the commercial project as it develops.
We match the contract package to the technology, the operating model and the commercial transaction. The following examples show the agreements and responsibilities we can address.
| Workstream | Agreements | Principal issues |
| Research and joint development | R&D collaboration, consortium, university spin-out, prototype and evaluation agreements | Define the aircraft, payload, software or analytics being developed; distinguish existing IP from project results; allocate milestones, test permissions, publication rights, confidentiality, exploitation rights and funding obligations. |
| Aircraft and component supply | Equipment sale, OEM or ODM, component supply and contract-manufacturing agreements | Allocate specifications, component substitutions, conformity evidence, traceability, factory acceptance, warranty, recalls, delivery, spare parts and long-term component availability. |
| Fleet acquisition and leasing | Fleet purchase, equipment lease, managed-fleet and financing agreements | Address title and possession, configuration, maintenance, permitted operations, damage, insurance, replacement aircraft, software access and return conditions. |
| Software and technology licensing | Firmware, flight-control, application, API, SDK, AI-model and know-how licences | Define permitted devices, users, territories and purposes; integration, modification and sublicensing; source-code access; open-source conditions; updates and continuity when a relationship ends. |
| Software development and continuity | Development, integration, maintenance, support and source-code escrow agreements | Agree specifications, acceptance tests, ownership, security fixes, support periods, version control, documentation, escrow-release conditions and practical rights to maintain the system. |
| Data and model development | Data collection, annotation, training, data-sharing and joint-controller agreements | Document provenance, personal-data roles, permitted training and reuse, access rights, protectable outputs, confidentiality, retention and deletion. Address statutory user-access rights where applicable. |
| Cloud and communications | SaaS, hosting, cloud, connectivity and managed-service agreements | Identify hosting and support access, subprocessors, availability, security, audit rights, incident reporting, data extraction, switching and exit assistance. |
| Drone operations and customer services | Inspection, surveying, mapping, drone-as-a-service and outsourced-operation agreements | Allocate operator status, competence and permission responsibilities, site access, deliverables, accuracy and reliance, acceptance, weather disruption, incident records, insurance and liability. |
| Maintenance and training | Maintenance, repair, overhaul, remote-pilot training and technical-support agreements | Define competence requirements, service scope, maintenance records, permitted modifications, replacement parts, turnaround times and responsibility for returning the system to service. |
| Distribution and international supply | Reseller, distribution, agency, international sale and after-sales agreements | Address territory and competition rules, end use, licence conditions, sanctions, diversion, customs roles, tax, warranties, local support, suspension and termination. |
| Counter-drone procurement | Detection-system procurement, integration, security-service and support agreements | Allocate lawful authority for each measure, authorised personnel, notifications, operational limits, data processing, interference liability, incident records and corrective action. |
| Public projects and funded programmes | Tender, teaming, consortium, subcontract, framework and grant-implementation agreements | Review eligibility, ownership and control, supply and information security, audit, IP and access rights, contract changes, exploitation duties and repayment exposure. |
| Investment and acquisitions | Term sheets, investment, shareholders, joint-venture and acquisition agreements | Address IP and regulatory due diligence, controlled disclosures, investment screening and other consents, funding conditions, change of control, warranties and indemnities. |
| Client sector | Typical projects | Legal work |
| Manufacturers and component suppliers | Aircraft, controllers, payloads, sensors and batteries | Product classification and conformity, supplier evidence, manufacturing terms, IP, cybersecurity, warranties and international market access. |
| Software developers and system integrators | Flight control, autonomy, fleet platforms, analytics and interfaces | Development and licensing, integration responsibilities, open-source conditions, data and model rights, security updates and service continuity. |
| Energy utilities and critical infrastructure | Power networks, renewable assets, pipelines and industrial sites | Inspection permissions, site access, confidential asset information, continuity, customer contracts and lawful counter-drone procurement. |
| Construction surveying and property | Site surveys, progress monitoring, mapping and digital records | Flight and site conditions, accuracy and reliance on deliverables, geospatial and image rights, acceptance criteria and professional liability. |
| Agriculture forestry and environmental services | Crop and forest monitoring, environmental data and proposed spraying services | Data use, seasonal delivery commitments, land access and separate pesticide or environmental assessments where the proposed activity requires them. [S30] |
| Logistics ports and healthcare supply | Delivery trials, port operations and medical logistics | Operating model and airspace, launch and delivery sites, payload-specific rules, custody, service levels, handling requirements where relevant, insurance and continuity. |
| Public authorities and emergency services | Emergency response, civil protection and public-service operations | Applicable civil or state-operation framework, procurement, lawful data processing, information security and allocation of operating responsibilities. [S04] [S06] [S12] |
| Security and protected sites | Monitoring, detection, identification and counter-drone systems | Legal authority, personnel and notification requirements, surveillance data, procurement, operating limits and liability for interference or damage. [S07] [S12] |
| Media and commercial imaging | Filming, photography, events and commissioned aerial content | Operation and location permissions, image and copyright rights, privacy, commissioning terms, permitted reuse and delivery obligations. |
| Defence and mixed-use technology programmes | Drone systems, components and software offered for civil and defence applications | Purpose and item classification, strategic trade, concessions where required, procurement, controlled disclosure, IP and contractual use restrictions. [S17] [S18] [S19] |
| Investors and international groups | Financing, acquisitions, joint ventures and market expansion | IP and regulatory due diligence, investment screening, controlled data rooms, tax structure, change-of-control conditions and transaction documentation. [S28] |
Legal reference date 11 November 2026.
The map connects the principal legal frameworks with the decisions and documents a project may require. Applicability depends on the technology, intended purpose, role, location, customer and transaction. Each framework is assessed against those facts.
| Field and principal framework | Applicability and decision | Services and deliverables |
| Civil UAS operations Regulations 2018/1139 and 2019/947 [S04] [S06] | Classify the actual drone operation and any state-activity exclusion. Open, specific and certified categories differ from product classes. Registration and pilot competence are separate requirements. | Operational route opinion; permission and competence matrix; ULC representation; legal review of manuals and supporting evidence. |
| Specific operations and BVLOS Regulation 2019/947 and EASA SORA guidance [S04] | Assess operational authorisation, STS declaration or LUC privileges. Technical risk assessment and geographical-zone conditions remain relevant. | Application strategy; coordination with operational specialists; cross-border operation advice; change assessment after autonomy, software, payload or operating-area modifications. |
| U-space and airspace Regulations 2021/664, 2021/665, 2021/666 and 2023/203 [S33] | Rules depend on designated airspace and the provider or user role. U-space is not mandatory for every drone operation. | USSP and CISP certification support; service contracts; data-sharing, continuity and information-security allocation; zone analysis. |
| Polish operations and counter UAS Aviation Law and Crisis Management Act [S06] [S07] | Assess Articles 156a onward and 156ze; Article 6zj provides conditioned critical-infrastructure powers. Notification does not replace every permission. | Registration and DroneTower procedures; deployment opinion; authority engagement; SUFO arrangements; records and liability terms. |
| UAS product conformity Regulation 2019/945 [S04] | Product type, market role and intended use determine conformity, CE and class-marking responsibilities. Certification and operational approval are different questions. | Manufacturer, importer and distributor responsibility map; documentation and contract review; corrective-action and recall support. |
| Radio and connectivity Directive 2014/53/EU and Polish Electronic Communications Law [S08] | Assess radio equipment, frequency use and permissions. RED cybersecurity requirements have a transition to the CRA; exemptions need individual review. | Spectrum and market-access analysis; connectivity terms; supplier evidence; support for communications permissions and authority enquiries. |
| AI and autonomy Regulation 2024/1689 as amended by 2026/1744 [S09] [S10] [S11] | Identify AI functions, intended purposes and legal roles. Check Article 6 classification, Annex I Section B integration and purpose-specific exclusions. | AI inventory; classification and exclusion memorandum; development and procurement schedules; oversight, logging and change-management allocation. |
| Privacy and public-sector data GDPR and Directive 2016/680; Polish implementing laws [S12] | Personal-data processing, identifiability, purpose, competent-authority status and territorial scope matter. Sensors do not make every output personal data. | DPIA screening and assessments; controller and processor terms; notices; retention; incident and rights-request procedures; UODO representation. |
| Cloud and international data transfers GDPR Chapter V and Decision 2021/914 [S12] | Identify drone-platform recipients and remote support access, not only server location. GDPR transfer compliance and controlled-technology exports involve different tests. | Data-flow and subprocessor map; transfer assessments and SCCs where appropriate; access terms; cloud governance and exit provisions. |
| Connected-product data and switching Data Act Regulation 2023/2854 [S14] | Assess connected-drone and related-service data, user access, data-holder duties and covered fleet-platform or cloud switching. Statutory rights have defined scope and safeguards. | Data-access terms; supplier and customer schedules; lawful data commercialisation; confidentiality arrangements; portability and switching plans. |
| Training data and model rights GDPR; DSM Directive 2019/790; database law [S13] [S23] | Assess imagery and telemetry provenance, lawful sourcing, privacy, text-and-data-mining conditions, database rights and permitted model use. Raw data, databases and trained models need separate analysis. | Dataset rights review; acquisition and annotation agreements; training and reuse licences; provenance records; restrictions on disclosure and retraining. |
| Product cybersecurity CRA Regulation 2024/2847 and sectoral rules [S15] | Check connected drone-related commercial products and separately supplied software or components, certified-aviation and defence exclusions, market roles and support periods. | CRA scope review; legal product-security requirements; vulnerability and incident allocation; supplier diligence; support and update terms. |
| Organisational cybersecurity and resilience NIS2 Directive 2022/2555, CER Directive 2022/2557 and Polish laws [S07] [S16] | Sector, activity, size and designation tests differ. A critical customer can impose contractual requirements on a supplier outside direct statutory scope. | Scope and registration review; governance and reporting procedures; supplier contracts; continuity and audit arrangements; regulatory response. |
| Software and other intellectual property Polish Copyright Act; Directives 2009/24 and 96/9; industrial-property law [S23] [S34] | Distinguish copyright, database protection, patents, designs and trademarks. Establish title across founders, staff, contractors and partners. | IP-chain review; assignments; licences; open-source review; protection strategy with patent specialists; enforcement and infringement support. |
| Confidentiality and know-how Directive 2016/943 and Polish unfair-competition law [S24] | Trade-secret protection depends on the information and reasonable protective measures. Disclosure for development, investment or procurement needs control. | NDAs; access and publication rules; confidentiality clauses; employee and contractor obligations; response to misappropriation. |
| Dual-use exports and technical assistance Regulation 2021/821 and Polish strategic trade Act [S17] [S18] | Assess aircraft, sensors, components, software and technology against current control lists, end use, catch-all rules, authorisation conditions, technical assistance and sensitive intra-EU transfers. | Classification memorandum; licence strategy and applications; end-user evidence; internal procedures; record-keeping and reporting. |
| Military items and concessions Common Military List; Directive 2009/43; Polish 2000 and 2019 Acts [S18] [S19] | Military classification, a business concession and transaction authorisations are distinct. Check the current Polish armaments list and conditions. | Concession and licensing support; certified internal-control arrangements where required; supply and technology-transfer terms. |
| Sanctions and restricted trade Regulations 833/2014, 269/2014 and 765/2006; Polish sanctions Act [S20] | Assess parties, ownership/control, destination, items, services, end use and diversion risk under the current applicable regime. | Transaction review; screening and escalation procedures; contractual clauses; lawful derogation analysis; response to enforcement enquiries. |
| Customs and movement of goods UCC Regulation 952/2013, implementing rules and Combined Nomenclature [S21] | Tariff classification differs from export-control classification. Origin, valuation, royalties and the procedure chosen can affect aircraft imports, demonstrations, repairs and returns. | BTI support; origin and valuation analysis; customs-role allocation; procedures for imports, exports, repairs, returns and temporary use. |
| Tax and innovation VAT Directive 2006/112; Polish VAT, CIT and PIT Acts; treaties [S22] | Analyse the actual drone equipment, software licence or service, the locations and party relationships. R&D and IP Box benefits depend on eligibility and records. | VAT and royalty analysis; withholding-tax and transfer-pricing review; structuring; incentive assessment; evidence and documentation. |
| Distribution and competition Articles 101 and 102 TFEU; Regulation 2022/720; Polish competition law [S29] | Territorial, customer, pricing, online-sales and exclusivity arrangements require competition analysis; an export restriction does not validate unrelated restraints. | Agency and distribution models; competition review; reseller terms; coordination of commercial and mandatory trade restrictions. |
| Public and defence procurement Directives 2014/24, 2014/25 and 2009/81; Polish Procurement Law [S26] | Identify the applicable procurement route for drone equipment, software and services and any justified exception. Eligibility, remedies and contract changes depend on the procurement and legislation. | Bid and consortium support; tender challenges; subcontracting and supply-security clauses; contract negotiations and modifications. |
| Funded drone research and industrial programmes EDF 2021/697; SAFE 2025/1106; EDIP 2025/2643 [S27] | The instruments have different beneficiaries, purposes and eligibility. Calls, ownership/control, third-country links and results rights matter. | Eligibility and consortium review; grant and project agreements; IP allocation; audit, exploitation and repayment advice. |
| Investment and corporate transactions Regulation 2019/452; new 2026/1386 transition; Polish investment-control law [S28] | Assess the drone business, technology, investor and transaction. FDI screening, merger control, concession and licence changes, and funding conditions require separate assessments. | Due diligence; controlled data rooms; transaction conditions; filings and consent planning; investment and acquisition documents. |
| Liability and insurance Polish Civil Code and Aviation Law; Regulation 785/2004; insurance rules [S06] [S25] [S32] | Separate product, operator, contractual, professional and data-related exposure. The new Product Liability Directive has a future-product transition. | Warranties and indemnities; insurance-gap review; incident and evidence procedures; claims, administrative and commercial dispute support. |
| Sector and environmental requirements Pesticide, environmental, product-waste and payload-specific rules [S30] [S35] | An aviation permission does not settle spraying, dangerous goods, protected locations, battery or waste obligations. Assess the proposed use. | Sector-permission map; site and service terms; environmental and payload compliance coordination; supply-chain responsibility review. |
| Defence use and humanitarian law Applicable international humanitarian law; Additional Protocol I Article 36 [S31] | Existing rules continue to apply. The Article 36 obligation is a state obligation; a law firm can support analysis and evidence, not substitute for state review. | Legal support for state-review documentation, responsible-use terms, drone-supplier due diligence and contractual information and cooperation duties. |
These milestones are applied together with the scope, exclusions and transitional provisions of the relevant instrument. National implementation and the date on which an entity or product enters the regime can affect the result.
| Date | Milestone | Practical treatment |
| 13 November 2025 | Polish compulsory UAS insurance began applying | Review the statutory 0.25–20 kg band and the operator, activity and policy terms; contractual customers may require additional cover. [S06] [S32] |
| 1 January 2026 | End of the national standard-scenario declaration transition | Review any operation previously relying on a national-scenario declaration and establish the current EU STS, authorisation or LUC route. [S04] |
| 3 April 2026 | Polish KSC amendment entered into force | Assess whether the drone business or relevant infrastructure operator is in scope and identify its applicable transition. [S16] |
| 4 July 2026 | Polish critical-infrastructure amendment entered into force | Counter-drone projects must use Article 6zj and its conditions when assessing the operator’s decision and specialist armed-security activities. [S07] |
| 11 September 2026 | CRA reporting obligations began | Assess covered drone-related products and software, relevant actively exploited vulnerabilities and severe security incidents. [S15] |
| 12 September 2026 | Data Act product-design threshold | Article 3(1) concerns relevant connected products and related services placed on the market after this date; assess new drone and platform releases. [S14] |
| 3 October 2026 | KSC registration milestone | Government guidance gives this deadline for entities already meeting the criteria when the amendment entered into force. Other entry dates require separate analysis. [S16] |
| 2 December 2026 | Specified AI Act transition | Includes Article 50(2) compliance for relevant synthetic-content systems placed on the market before 2 August 2026 and specified new prohibitions; assess the actual drone-platform function. [S11] |
| 9 December 2026 | Product Liability Directive transition | National transposition deadline. Corrected Article 2(1) covers products placed on the market or put into service after 8 December 2026; check national implementation for equipment and software. [S25] |
| 12 January 2027 | Data Act switching charges | Charging switching fees is prohibited for covered data-processing services; review cloud and fleet-platform exit terms within scope. [S14] |
| 3 April 2027 | KSC implementation milestone | For the relevant existing cohort, government guidance identifies principal implementation and S46 connection obligations. [S16] |
| 2 December 2027 | Relevant Annex III AI requirements | Apply the amended Article 113 timetable where a drone-related AI function falls within the relevant classification; drone use alone does not establish that classification. [S10] [S11] |
| 11 December 2027 | Main CRA requirements apply | Review connected drone-related equipment, software and components, exclusions and product transition rules; RED cybersecurity repeal is aligned to this date. [S08] [S15] |
| 17 January 2028 | New EU FDI framework applies | Assess the transition for investments in drone and related technology businesses; current transaction obligations still require a separate review. [S28] |
| 2 August 2028 | Relevant product-related AI requirements | Assess Article 6(1), Annex I and the sectoral integration route for the particular product; do not treat all drone AI as automatically high-risk. [S09] [S10] [S11] |
| Project | Review focus | Indicative output |
| A manufacturer preparing an EU market launch | Review the aircraft, controller, payloads, software and supply chain; identify product, radio, cybersecurity, IP and trade requirements. | A product and market-role map, conformity-document review, supplier and customer contracts, licensing plan and list of decisions before launch. |
| An operator planning repeated infrastructure inspections | Assess the proposed sites, BVLOS or other operating model, airspace, customer relationship, subcontractors, data and insurance. | An operational-permission strategy, authority and site-access schedule, inspection contract, data terms and incident-responsibility framework. |
| A developer licensing a fleet platform or autonomous function | Review software ownership, model and dataset rights, open-source components, cloud access, security updates and the customer’s intended use. | A rights and regulatory assessment, software or SaaS licence, development and support schedules, training-data terms and exit arrangements. |
| An international supplier establishing a Polish distribution network | Assess product and market roles, territory and customer restrictions, controlled goods or technology, customs procedures and tax treatment. | Distribution and after-sales contracts, compliance clauses, permission and customs-role schedule, warranty arrangements and transaction documentation. |
| An infrastructure owner procuring a counter-drone system | Assess the proposed detection and countermeasure functions, statutory authority, security provider, notifications, data processing and damage exposure. | A deployment opinion, procurement and SUFO service terms, operating limits, notification procedures, incident records and liability allocation. |
| An investor acquiring or financing a drone business | Review IP title, permissions, product and cybersecurity exposure, data rights, controlled technology, key contracts and corporate consents. | A prioritised due-diligence report, controlled-disclosure arrangements, consent and filing plan, transaction conditions, warranties and indemnities. |
| A consortium preparing a funded drone-technology project | Review the call, participating entities, ownership and control, work packages, disclosures, existing IP and rights to results. | An eligibility assessment, consortium and subcontract terms, IP and exploitation schedule, confidentiality arrangements and reporting responsibilities. |
1. What is being supplied: an aircraft, components, software, data, an operational service or a combination?
2. Who will be the UAS operator, who will fly or supervise the system, and who will maintain it?
3. What aircraft, payloads, communications, autonomy and operating areas are proposed, including any BVLOS activity?
4. Which countries and sites are involved, and are the intended purposes civilian, public-sector, defence-related or mixed?
5. Which product evidence, registration, personnel competences, authorisations, declarations and airspace conditions apply?
6. Who owns the software and other protectable assets, and what rights are held in third-party and open-source components?
7. What imagery, telemetry, personal data or customer information will be collected, and may it be reused or used to train models?
8. Where will data and technical information be stored, and who can access them through cloud hosting, support or development?
9. Which export-control, sanctions, customs and tax rules affect the equipment, software, support and technology transfers?
10. Who decides when a software, model, component or payload change is made, and when must permissions or compliance evidence be revisited?
11. How will contracts and insurance address physical damage, inaccurate outputs, interruption, privacy incidents and cyber incidents?
12. What records, source access, spare parts, data export and transition assistance will be available if a supplier fails or a contract ends?
Commercial use alone does not determine the EU operational category. The legal route depends on the proposed activity and its risks. An operation may fall within the open category if its conditions are met, or require a specific-category route or certified-category assessment. Operator registration, remote-pilot competence, airspace conditions and Polish flight notification are separate issues. We identify the requirements for the actual operating model rather than treating a single licence as the answer. [S04] [S05] [S06]
The answer depends on the operation, locations and scope of the permission or privilege. Specific-category projects may use an operational authorisation, an applicable EU standard-scenario declaration or LUC privileges. Risk assessment, aircraft suitability, personnel, geographical-zone conditions and cross-border requirements must also be checked. Site access, customer contracts, communications, data processing and insurance require their own arrangements. We can coordinate the legal work with operational and technical specialists. [S04] [S05] [S06]
CE marking and, where relevant, a UAS class marking address product conformity. They do not confer an unrestricted right to fly. The operator must separately satisfy the rules for the operational category, pilot competence, airspace and the particular location. Cross-border operations may involve further procedures. We review product compliance and operating permissions together so that procurement assumptions match the intended deployment. [S04]
That requires a review of the source of the material, contracts, confidentiality, any copyright or database rights, personal-data obligations and applicable Data Act rights. Possessing a file or paying for an inspection does not resolve every right to reuse its contents. We draft clear collection, access, training, commercialisation and disclosure terms, and assess whether personal information may lawfully be used for the proposed model development. [S12] [S13] [S14] [S23]
Technical access to a device does not establish a legal right to use it. Polish law provides a conditional route for critical-infrastructure operators to decide on the permissibility of telecommunications-disruption devices used in activities carried out by specialist armed security personnel. The particular site, threat circumstances, statutory conditions, notifications and public-authority oversight must be examined. We assess the lawful role of each participant and reflect the result in procurement, service terms and operating procedures. [S07]
A civilian commercial description does not settle the export-control position. Aircraft, sensors, components, software and technology can require review under dual-use or military-item rules, sanctions and end-use controls. Remote access to controlled technical information may also matter. Customs classification is a separate exercise. We assess the technical specification, destination, parties, end use and proposed transfer before identifying any required authorisation and contractual conditions. [S17] [S18] [S19] [S20] [S21]
Contact KG Legal Kiełtyka Gładkowski with a description of your technology, planned activity and commercial objectives. We can identify the legal work required and propose a scope covering the relevant permissions, contracts, data arrangements and transaction requirements.
The sources below support the legal framework and published experience described on this page. Legislation is read together with its amendments, corrigenda, scope and transitional provisions. Official guidance assists interpretation but does not replace the enacted text.
KG Legal Drone Warfare published 26 August 2026
Legal 500 editorial profile and reported work highlights
Legal 500 firm supplied profile including software and API projects
EASA June 2026 Easy Access Rules for Regulations 2019/947 and 2019/945
Regulation 2019/947 consolidated text
Current consolidated Aviation Law Dz U 2026 item 1407
Act of 29 May 2026 Dz U item 815 including Article 6zj and commencement
Commission RED overview and 2026 cybersecurity transition
Polish Electronic Communications Law of 12 July 2024
Law enforcement Directive 2016/680
Polish law enforcement data Act
Standard contractual clauses Decision 2021/914
EDPB Guidelines 3/2019 on video devices
EDPB Opinion 28/2024 and explanatory release
Regulation 2023/2854 including Articles 29 and 50
Commission Data Act explanation
Commission legislative summary and application dates
Act of 23 January 2026 Dz U item 252
Government guidance on KSC scope and transitional duties
Commission export control and authorisation overview
Commission 2026 list update and commencement explanation
Current ministry dual use authorisation guidance
Current ministry armaments authorisation guidance
Amending Act of 13 March 2026 Dz U item 471
Polish armaments list of 27 May 2026 Dz U item 719
EU Common Military List of 23 February 2026
Polish Act of 13 June 2019 consolidation to be read with amendments
Polish Ministry of Foreign Affairs sanctions resources
Commission guidance on the no re export to Russia clause
Commission calculation of customs duties
Commission binding tariff information
UCC valuation and royalties guidance
Tax Administration R and D relief
Tax Administration withholding tax
Tax Administration transfer pricing
Polish Copyright Act consolidation and amendment record
Computer programs Directive 2009/24
DSM Copyright Directive 2019/790
Product Liability Directive 2024/2853
Official corrigendum of 7 May 2026 changing the Article 2 date
Commission product liability overview
Polish Public Procurement Law of 11 September 2019
Council Defence Omnibus adoption statement of 9 October 2026
European Defence Fund Regulation 2021/697
New EU Regulation 2026/1386 and transitional provisions
Current Polish ministry investment screening guidance
Polish Investment Control Act consolidation Dz U 2026 item 47
Vertical Block Exemption Regulation 2022/720
Commission guidance on drones and pesticide spraying
ICRC current explanation of autonomous weapons and existing law
Additional Protocol I Article 36
Regulation of 24 October 2025 Dz U item 1485
EASA U space regulatory instruments
EASA information security rules
Polish Industrial Property Law consolidation
EPO 2026 guidance on computer implemented inventions
Commission Batteries Regulation overview
Commission RoHS and WEEE explanation
#DroneLaw #UASLaw #AviationLaw #DroneTechnology #TechnologyLaw #DataProtection #IntellectualProperty #ExportControl