01Overview
Executive Summary
The EU marine sector faces the widest regulatory perimeter of any maritime market, and in 2026 the most important fact about it is that the headline deadline has moved. The high-risk obligations everyone planned for on 2 August 2026 have been deferred, but the deferral is provisional, the binding perimeter around the AI Act is broad, and member-state divergence is now the dominant operational risk.
On 7 May 2026 the Council and Parliament reached provisional political agreement on the Digital Omnibus on AI, deferring high-risk obligations for Annex III standalone systems to 2 December 2027 and for Annex I product-embedded systems, the category that catches AI in machinery, marine equipment, and recreational craft, to 2 August 2028. It also adds a new Article 5 prohibition on AI-generated child sexual abuse material and non-consensual intimate imagery from 2 December 2026. Until the package is published in the Official Journal, expected before 2 August 2026, the original AI Act timeline remains the legal baseline.[1][2]
Treat the Omnibus deferral as breathing room, not relief. The member states ahead on enforcement will be the first to act, and the perimeter around the AI Act is binding now.
For the EU marine sector the binding 2026 perimeter is broader than the AI Act alone. FuelEU Maritime and the EU Emissions Trading System extension already apply, the European Maritime Single Window environment became applicable on 15 August 2025, Cyber Resilience Act reporting begins on 11 September 2026, the new Product Liability Directive, which expressly captures software and AI as products, must be transposed by 9 December 2026, and the IMO MASS Code was adopted on 22 May 2026 and takes effect on 1 July 2026.[3][4][5][6]
The risk-weighted action list for an EU marine operator runs in sequence: GDPR-aligned data governance now, NIS2 and IACS cyber posture now, an AI inventory and Article 50 transparency by 2 August 2026, an Article 5 prohibited-practice screen by 2 December 2026, and a high-risk quality-management programme aligned with the emerging European standard through 2027 and 2028. This report maps each layer to the AI now entering EU marine organisations and sets out the steps an operator can take now.
02Framework
The AI Act and Where the Omnibus Moved It
Regulation (EU) 2024/1689 entered into force on 1 August 2024 with a staggered timeline. The architecture is intact, and the amendments under negotiation change the dates and a handful of mechanics, not the risk-based structure.
The original timeline and the amendments
Article 5 prohibitions and Article 4 AI literacy applied from 2 February 2025, and general-purpose AI obligations under Articles 51 to 55 from 2 August 2025. The Commission's proposal of 19 November 2025 and the 7 May 2026 political agreement defer the high-risk dates to 2 December 2027 for Annex III standalone systems and 2 August 2028 for Annex I product-embedded systems. They grant a three-month grace period on the Article 50(2) generative-AI watermarking obligation, moving it to 2 December 2026 for models released before 2 August 2026, recast Article 4 AI literacy from a binding obligation into an encouragement, postpone the national regulatory-sandbox deadline to 2 August 2027, and add the new Article 5 prohibition effective 2 December 2026.[1][2]
The political agreement still requires formal adoption by Parliament and Council and publication in the Official Journal. Until then, the original timetable remains the legal baseline, which is why governance programmes are best built against both timelines at once.[1]
How the risk tiers reach marine
- Article 5 prohibited practices, in force since 2 February 2025, reach emotion-recognition systems on bridges or in port control rooms where they touch the workplace, AI-driven crew scoring, and untargeted biometric profiling of passengers at ferry and cruise terminals.
- Article 6 with Annex I, product-embedded high-risk, catches AI components placed on the market under the Recreational Craft Directive, the Machinery Regulation, and the Marine Equipment Directive. The AI Act layer here is deferred to 2 August 2028, and the Omnibus narrows the safety-component definition where product safety rules already deliver equivalent protection.
- Article 6 with Annex III, use-case high-risk, catches AI in critical infrastructure such as port and vessel traffic services, in employment such as crew recruitment and scheduling, in biometric passenger boarding, and in border and coast-guard contexts. This layer is deferred to 2 December 2027.
- Article 50 transparency applies from 2 August 2026, except the watermarking obligation which moves to 2 December 2026 for pre-existing models. It reaches customer-facing booking and concierge chatbots, AI-generated marketing imagery for charter platforms, and AI-generated voyage documentation.
- General-purpose AI obligations have applied since 2 August 2025 and are untouched by the Omnibus, so marine deployers of GPAI-based assistants rely on documentation from the upstream model provider.[2]
Penalties
The Article 99 penalty tiers are unchanged: up to EUR 35 million or 7 per cent of global annual turnover for prohibited practices, up to EUR 15 million or 3 per cent for other high-risk obligations, and up to EUR 7.5 million or 1 per cent for supplying incorrect information.[1]
The harmonised standard is late
CEN-CENELEC committee JTC 21 published prEN 18286, the AI quality management system standard for EU AI Act regulatory purposes, for enquiry on 30 October 2025. It translates the Article 17 quality-management obligations into auditable controls, with an annex mapping to the Regulation. The January 2026 enquiry vote did not reach the required support, with a large body of comments under resolution, and publication is now targeted for the fourth quarter of 2026 at the earliest. ISO/IEC 42001 sits outside the EU harmonisation track, though prEN 18286 includes a mapping annex to it. Presumption of conformity under Article 40 will arise only once a final standard is cited in the Official Journal.[7]
03Perimeter
The Binding Perimeter Is Wider Than the AI Act
The instruments below apply now or arrive on fixed dates, and several reach AI directly. Together they form the binding perimeter an EU marine operator works inside while the AI Act high-risk dates sit in the future.
The Data Act
The Data Act (Regulation (EU) 2023/2854) has applied since 12 September 2025. It governs access to and sharing of data generated by connected products and related services, which reaches connected vessels, port IoT, predictive-maintenance telemetry, and engine OEM data-sharing arrangements directly.[8]
NIS2
The NIS2 Directive (Directive (EU) 2022/2555) was due for transposition by 17 October 2024. By March 2026, twenty-one of twenty-seven member states had transposed it, and in May 2025 the Commission sent reasoned opinions to nineteen member states for incomplete transposition. Maritime transport, ports, and vessel-traffic services are explicitly in scope. Penalties for essential entities reach EUR 10 million or 2 per cent of global annual turnover, with named management liability. For a cross-border marine operator, the practical consequence is inconsistent registration portals and uneven enforcement through 2026.[9]
The Cyber Resilience Act
The Cyber Resilience Act (Regulation (EU) 2024/2847) entered into force on 10 December 2024. Notified bodies stand up from 11 June 2026, the Article 14 vulnerability and incident reporting obligation begins on 11 September 2026, and full requirements apply from 11 December 2027. Reporting runs through a single ENISA platform. Equipment governed by the Marine Equipment Directive is carved out, but connected onboard IT, port systems, and most products with digital elements used in the broader marine sector are in scope. Penalties run up to EUR 15 million or 2.5 per cent of turnover.[5]
The Product Liability Directive
The new Product Liability Directive (Directive (EU) 2024/2853) entered into force on 8 December 2024 and must be transposed by 9 December 2026, applying to products placed on the market after that date. Software and AI systems are expressly products, and AI system providers under the AI Act are treated as manufacturers. The directive introduces rebuttable presumptions of defectiveness and causation where a claimant faces excessive technical difficulty, alongside disclosure obligations. The withdrawn AI Liability Directive means civil liability for AI now consolidates here.[6]
The Machinery Regulation and the Recreational Craft Directive
The Machinery Regulation (Regulation (EU) 2023/1230) applies from 20 January 2027 and captures AI-enabled safety components, which reaches shipyard automation, marina equipment, and the new generation of yard cranes. The Recreational Craft Directive (Directive 2013/53/EU) continues to govern CE marking of watercraft between 2.5 and 24 metres, engines, and listed components. AI-enabled components such as AI-assisted navigation, anti-collision, and autopilot, placed on the EU market separately, become subject to that directive's conformity assessment, the AI Act when classified as Annex I safety components from 2 August 2028, and the Product Liability Directive from 9 December 2026.[10]
04Privacy
GDPR and the Data-Protection Picture
The GDPR is the data-protection foundation under every AI use, and the case law and guidance around AI training have moved as much as the legislation.
The proposed amendments
The Commission's parallel Digital Omnibus on the digital legislative framework, also of 19 November 2025, proposes to amend the GDPR by extending the breach-notification timeline from 72 to 96 hours for high-risk breaches, introducing a relative interpretation of personal data consistent with recent case law, and adding a legitimate-interest ground for AI training through a new Article 88c. It also touches the ePrivacy rules, NIS2 reporting through a single ENISA portal, and the Data Act. As at June 2026, this package has not reached political agreement and is moving through the ordinary legislative procedure, so its content can shift.[11]
The EDPB position and national guidance
The EDPB's Opinion 28/2024, adopted on 17 December 2024, established that an AI model trained on personal data cannot be assumed anonymous and must be assessed case by case, set out a three-step legitimate-interest test for AI training and deployment, and addressed the cascading effect of unlawful training data into downstream systems. France's CNIL has issued the most operationally usable national guidance, across recommendations in February, June, and July 2025 covering legitimate interest, web scraping, data-subject rights, and the GDPR status of AI models.[12]
The intention of the GDPR already supports responsible AI. The EDPB confirmed it, and the most useful national guidance shows how to apply it.
The enforcement picture is unsettled
The most significant recent development is that the only finalised GDPR penalty against a generative-AI provider has been overturned. The Italian Garante's EUR 15 million fine against OpenAI, issued in late 2024, was annulled by the Court of Rome in a judgment of 18 March 2026, on the jurisdictional ground that the Garante lost competence once OpenAI's Irish establishment was recognised. AI-related data-protection case law in the EU is therefore in motion in mid-2026, which counsels documentation and caution rather than reliance on any single precedent.[13]
05Safety
The Product-Safety and Cyber Stack in Practice
For an organisation that builds, integrates, or places AI-enabled products on the EU market, the product-safety and cyber instruments interlock. A single AI-enabled navigation component can sit inside the Recreational Craft Directive for CE marking, the Cyber Resilience Act for its digital elements, the AI Act as an Annex I safety component once that date arrives, and the Product Liability Directive for civil exposure. The governance task is to treat documentation as the connective tissue across all four.
The practical discipline the Product Liability Directive introduces is the one to internalise first, because it bites earliest and applies broadly. For AI-enabled marine equipment, recreational craft, and software, an operator benefits from maintaining training-data lineage, validation records in the conditions of intended use, post-market monitoring evidence, and incident logs sufficient to rebut the presumptions of defectiveness the directive creates. That same evidence base serves the Cyber Resilience Act's reporting obligation and the AI Act's technical-documentation requirements, which is why a single, well-kept evidence pack does most of the work across the stack.
06Maritime
The EU Maritime Instruments
The maritime-specific layer sits alongside the digital stack, and several instruments carry data, cyber, and AI implications directly.
- European Maritime Single Window environment (Regulation (EU) 2019/1239). Applicable since 15 August 2025, with decentralised Maritime National Single Windows linked to SafeSeaNet through the EMSA-supported Reporting Interface Module. Implementation has been uneven across member states.[4]
- FuelEU Maritime (Regulation (EU) 2023/1805). Applies from 1 January 2025 to ships of 5,000 gross tonnes and above calling at EEA ports, with the first verified report due 31 January 2026 and a penalty of EUR 2,400 per tonne of VLSFO-equivalent energy above the limit, multiplied by the greenhouse-gas-intensity gap. The ISM company holds responsibility, and an expulsion order is possible after two consecutive non-compliant years.[3]
- EU Emissions Trading System for shipping. Applies from 1 January 2024 to ships of 5,000 gross tonnes and above, with surrender phasing of 40 per cent for 2025, 70 per cent for 2026, and 100 per cent for 2027, and methane and nitrous oxide brought into scope from 1 January 2026.[18]
- EMSA. In its 2025 to 2027 programming, the European Maritime Safety Agency is expanding satellite-AIS and Earth-observation analytics, integrating machine learning for risk assessment and vessel-position prediction, supporting MASS-related training and the STCW revision, and providing common components for the single-window environment.[20]
- IMO MASS Code. Adopted at MSC 111 in London on 22 May 2026, the non-mandatory Code takes effect on 1 July 2026 for cargo ships, with the Experience-Building Phase framework to be developed at MSC 112 in December 2026, a mandatory Code targeted for adoption by 1 July 2030, and SOLAS entry into force on 1 January 2032. The master remains legally responsible whether on board or in a certified Remote Operations Centre.[14]
- The cyber baseline. IMO Resolution MSC.428(98) has required cyber risk management in the ISM safety management system since 1 January 2021. IACS UR E26 and E27 apply to ships contracted for construction on or after 1 July 2024, with E26 governing the ship as an integrated platform and E27 the individual onboard systems. The first such newbuilds are entering their cyber-relevant surveys through 2025 and 2026, and the absence of E26 and E27 style artefacts is increasingly treated as a finding under MSC.428(98) on existing vessels as well.[15]
Three of the EU's largest flag registries are operated by Malta, Greece, and Cyprus, and AI governance expectations flow through the Document of Compliance holder for cyber risk and the FuelEU and ETS administering authority for emissions. Greek-controlled tonnage dominates EU shipowner exposure, reflected in Greece chairing MSC 111.
07Divergence
Member-State Implementation
Member-state divergence is now the dominant operational risk, because the AI Act applies uniformly in principle while enforcement capacity and national law arrive at very different speeds. As at June 2026, only around eight of twenty-seven member states had formally notified a single point of contact to the Commission, and most missed the Article 70 deadline of 2 August 2025.
Italy is the first member state with a comprehensive national AI law, Law No. 132/2025, in force from 10 October 2025. It designates AgID as the notifying authority and the National Cybersecurity Agency as the market-surveillance authority and single point of contact, preserves the Garante for data protection, and introduces aggravated criminal penalties for AI-assisted offences. Spain runs the most operational national architecture through AESIA, the supervision agency operating since 2024 with full sanctioning powers from 2 August 2025, which in December 2025 released sixteen guidance documents and templates widely considered the most detailed national interpretation of the AI Act available. Germany designated the Bundesnetzagentur as market-surveillance authority and single point of contact, and its Cabinet approved the draft implementation law in February 2026. France is moving through the DGCCRF for market surveillance with the CNIL retaining fundamental-rights and data-protection powers, and Ireland has adopted a decentralised model coordinated by a national AI office.[16][17]
The signal for operators is to watch the states that are ahead, since Spain through AESIA, Italy through the Garante and the cybersecurity agency, and Germany once its law is enacted will be the first to act.
08Application
AI Use Cases and Classification by Marine Segment
Each EU marine segment maps to a different combination of AI Act classification and adjacent obligation. The table reflects the post-Omnibus position where the deferral applies.
| Segment | Characteristic AI use cases | Likely classification and obligations |
|---|---|---|
| Commercial shipping operators | Voyage optimisation, predictive maintenance, FuelEU and ETS automation, bridge decision support | Mostly limited-risk (Article 50 transparency); Annex I high-risk if integrated as onboard safety components (to 2 Aug 2028); GDPR and NIS2 cyber layer |
| Ports and terminals | Vessel traffic services, berth scheduling, autonomous yard equipment, biometric gates, port community systems | Critical-infrastructure and biometric Annex III high-risk (to 2 Dec 2027); NIS2 essential-entity status |
| Shipbuilders and equipment manufacturers | Design AI, robotic welding and inspection, AI safety components | Machinery Regulation (Jan 2027); AI Act Annex I high-risk (Aug 2028); CRA for connected products (Dec 2027); PLD from 9 Dec 2026 |
| Recreational craft and superyachts | AI-assisted navigation, anti-collision, autopilot, customer profiling on charter platforms | RCD CE marking; AI Act Annex I (deferred); GDPR for profiling; PLD strict liability for AI-enabled craft |
| Ferry, passenger, and cruise operators | Biometric boarding, passenger profiling, health and dietary data | Biometric Annex III high-risk; GDPR Article 9 special-category processing; EDPB Opinion 28/2024 anonymity considerations |
| Marine insurers and P&I clubs | AI underwriting, claims, sanctions screening | Annex III high-risk (creditworthiness and life insurance); DORA where a financial entity; GDPR Article 22 automated decisions |
| Marine surveyors and classification societies | AI defect detection, digital classification | Providers of high-risk AI where outputs drive certification; ISO/IEC 42001 increasingly required by clients |
The EU marine market is also where AI deployment is most visibly concrete. Named programmes already in scope for the AI Act, GDPR, NIS2, and CRA reporting include fleet-wide predictive analytics at A.P. Moller-Maersk, a multi-year AI partnership at CMA CGM, port-wide digital-twin programmes at Rotterdam and Valenciaport, an autonomous-corridor letter of intent among Rotterdam, Antwerp-Bruges, and North Sea Port, and the supervised autonomous service of the Yara Birkeland, which operates with a small supervisory crew pending full unmanned certification.
09Exposure
Enforcement and Penalties at a Glance
The table consolidates the penalty exposure across the regimes that reach EU marine businesses.
| Regime | Maximum exposure |
|---|---|
| AI Act, Article 99 (prohibited practices) | EUR 35 million or 7% of global annual turnover |
| AI Act, Article 99 (other high-risk obligations) | EUR 15 million or 3% |
| AI Act, Article 99 (incorrect information) | EUR 7.5 million or 1% |
| GDPR, Article 83 | EUR 20 million or 4% of global turnover |
| NIS2, essential entities | EUR 10 million or 2%, with named management liability |
| NIS2, important entities | EUR 7 million or 1.4% |
| Cyber Resilience Act | EUR 15 million or 2.5% (essential requirements) |
| Data Act | Member-state penalties, expected to mirror GDPR ceilings |
| Product Liability Directive | Civil liability with rebuttable presumptions; disclosure obligations |
| FuelEU Maritime | EUR 2,400 per tonne VLSFO-equivalent excess, multiplied by the intensity gap; expulsion possible |
| EU ETS (maritime) | Surrender obligations; member-state sanctions for non-surrender |
10Timeline
Compliance Timeline
The dates below consolidate the milestones that shape AI governance for the EU marine industry. Rows marked Active are in force now.
| Date | Milestone | Status |
|---|---|---|
| 1 Jan 2021 | Cyber risk required in ISM safety management systems (IMO MSC.428(98)) | Active |
| 1 Aug 2024 | EU AI Act enters into force | Active |
| 1 Jul 2024 | IACS UR E26 and E27 apply to new ships contracted on or after this date | Active |
| 1 Jan 2025 | FuelEU Maritime applies; EU ETS surrender phasing continues | Active |
| 2 Feb 2025 | AI Act Article 5 prohibitions and Article 4 AI literacy apply | Active |
| 2 Aug 2025 | AI Act general-purpose AI obligations apply; AESIA gains sanctioning powers | Active |
| 15 Aug 2025 | European Maritime Single Window environment applicable | Active |
| 12 Sep 2025 | Data Act applies | Active |
| 10 Oct 2025 | Italy's Law 132/2025 in force | Active |
| 30 Oct 2025 | prEN 18286 published for CEN enquiry | Active |
| 19 Nov 2025 | Commission proposes the Digital Omnibus (AI and digital framework) | Active |
| 1 Jan 2026 | EU ETS methane and nitrous oxide in scope | Active |
| 31 Jan 2026 | First verified FuelEU Maritime report due | Active |
| 18 Mar 2026 | Court of Rome annuls the OpenAI / Garante fine | Active |
| 7 May 2026 | Digital Omnibus on AI political agreement | Active |
| 22 May 2026 | IMO adopts the non-mandatory MASS Code at MSC 111 | Active |
| 11 Jun 2026 | CRA notified bodies stand up | Active |
| 1 Jul 2026 | IMO MASS Code takes effect for cargo ships | Upcoming |
| 2 Aug 2026 | AI Act Article 50 transparency; original high-risk date unless adoption precedes it | Upcoming |
| 11 Sep 2026 | CRA Article 14 vulnerability and incident reporting begins | Upcoming |
| 2 Dec 2026 | AI Act watermarking and new Article 5 prohibition; PLD transposition by 9 Dec | Upcoming |
| Dec 2026 | IMO MSC 112 to develop the MASS Experience-Building Phase | Upcoming |
| 20 Jan 2027 | Machinery Regulation applies | Upcoming |
| 2 Aug 2027 | National regulatory-sandbox deadline | Upcoming |
| 2 Dec 2027 | AI Act Annex III high-risk obligations apply; CRA full requirements (11 Dec) | Upcoming |
| 2 Aug 2028 | AI Act Annex I (product-embedded, including marine craft) applies | Upcoming |
| 1 Jan 2032 | Mandatory IMO MASS Code targeted entry into force | Upcoming |
11Action
Recommendations
The steps below are sequenced against the dates that bite, regardless of when the Omnibus is formally adopted.
By 2 August 2026
Complete an enterprise AI inventory
Map every system to its provider or deployer role and to the Annex I, Annex III, GPAI, and Article 50 categories. The AESIA guidance and the CNIL recommendations are the strongest current operational references.
Stand up Article 50 transparency controls
Chatbot disclosure, deep-fake labelling, and generative-AI watermarking for any model released on or after 2 August 2026, with the grace period giving pre-existing models until 2 December 2026.
Screen all AI systems against the new Article 5 prohibition
Effective 2 December 2026, the prohibition reaches non-consensual intimate imagery and CSAM. For charter, hospitality, and crew-engagement platforms relying on generic image generation, document a safe-harbour design or remove the feature.
Confirm NIS2 status by jurisdiction
Register in each member state of establishment and brief the board on personal management liability.
Reflect IACS UR E26 and E27 evidence in the safety management system
Include network segmentation, software bills of materials per system, vulnerability logs, incident response, and recovery test records.
Build Cyber Resilience Act reporting capability
Ready for 11 September 2026 for any connected product on the EU market.
By 9 December 2026
Treat the revised Product Liability Directive as a documentation discipline
Maintain training-data lineage, validation records in the conditions of intended use, post-market monitoring evidence, and incident logs sufficient to rebut the presumptions of defectiveness.
Implement FuelEU pooling and onshore-power strategies
Plan for the first verified report and beyond.
Through 2027 and 2028
Align high-risk quality-management programmes with prEN 18286
As it progresses to final status, even though it is unlikely to confer presumption of conformity before late 2026 at the earliest, since it is the baseline notified bodies will reference. Keep ISO/IEC 42001 certification as a parallel commercial signal and a useful gap-filler.
Engage national notified bodies and notifying authorities early
Queues for Annex III conformity assessments will form from 2027.
Strategic posture
Treat the Omnibus deferral as breathing room, not relief, and align autonomous-vessel programmes to both the MASS Code Experience-Building Phase from 1 July 2026 and the December 2027 Annex III date, which are now reconciled.
Benchmarks that would change these recommendations
A failure of the Omnibus to be formally adopted by 2 August 2026 would bring the original Annex III deadline into force on that date. Publication of prEN 18286 as a harmonised standard would accelerate the Article 40 conformity route. A material change to NIS2 in the digital-framework Omnibus, the MSC 112 outcome on the Experience-Building Phase, and the first enforcement decisions by AESIA or the AI Office would each shift the picture.
12Method
Caveats and Provisional Positions
This is a first-edition report, written for an environment that is moving on several tracks at once. The positions below are accurate as at June 2026 and carry the qualifications noted.
The Omnibus on AI is provisional. Every deferred date is contingent on formal adoption by Parliament and Council and publication in the Official Journal, expected before 2 August 2026. Until then, the original AI Act dates legally apply, so governance programmes are best built against both timelines.
prEN 18286 is still a draft. The January 2026 enquiry vote did not reach the required support, and publication is targeted for the fourth quarter of 2026 at the earliest. Article 40 presumption of conformity depends on citation in the Official Journal, not the draft.
National authority designation is incomplete. Only around eight of twenty-seven member states had formally notified a single point of contact by early 2026, and several national penalty regimes are not yet final.
NIS2 transposition is fragmented. Nineteen member states received reasoned opinions in May 2025, and twenty-one of twenty-seven had transposed by March 2026, so cross-border operators face inconsistent portals and uneven enforcement.
The OpenAI / Garante precedent has been annulled. The Court of Rome's March 2026 judgment overturned the only finalised GDPR penalty against a generative-AI provider, so AI-related data-protection case law is unsettled.
The digital-framework Omnibus amending the GDPR, ePrivacy rules, NIS2, and the Data Act had not reached political agreement as at June 2026 and could shift breach thresholds, the definition of personal data, and AI-training legal bases.
Industry-claimed savings. Figures circulated for AI-driven fuel and downtime savings come from industry and aggregator analysis rather than audited filings, and the Yara Birkeland operates with a supervisory crew rather than fully unmanned.
The Marine Equipment Directive carve-out from the Cyber Resilience Act covers specific shipboard equipment only, and does not extend to the broader port, terminal, and connected-product ecosystem.
This report is open to peer review, industry feedback, and correction. If you identify positions that would benefit from refinement, I welcome hearing from you.
13Conclusion
Conclusion
The EU marine sector operates inside the most comprehensive AI and digital regulatory framework in the world, and 2026 is the year the framework's headline deadline moved while its perimeter held firm. AI is already running in voyage optimisation, predictive maintenance, port automation, biometric boarding, underwriting, and the FuelEU and ETS compliance work that touches every operator. The governance question is which instrument each use activates, and whether the documentation exists to demonstrate it.
The deadline moved. The perimeter did not. FuelEU, NIS2, the Data Act, and the cyber and product-liability rules apply now, and the AI Act sits on top of them.
Two points carry the most weight. The first is that the AI Act deferral does not reduce the binding load, because FuelEU Maritime, the EU ETS, the Data Act, NIS2, and the single-window environment apply now, and the Cyber Resilience Act and Product Liability Directive arrive on fixed 2026 dates. The second is that member-state divergence has become the operational risk that matters most: the same AI use can meet a detailed Spanish interpretation, an Italian criminal overlay, and a still-forming framework elsewhere, all at once.
The work this quarter is the inventory, the data governance, the cyber posture, and the documentation. Those serve every instrument in the stack, whatever the AI Act dates finally settle on.
The practical route is the one that serves the whole stack at once. Build the AI inventory, ground the data governance in the GDPR and the EDPB position, bring the NIS2 and IACS cyber posture up to standard, stand up Article 50 transparency, and keep the documentation that the Product Liability Directive, the Cyber Resilience Act, and the AI Act all demand. The EU maritime sector has long carried the densest compliance load in shipping. Extending that discipline to how AI is governed is the natural next step, and the operators that build the evidence base now will be ready whichever way the dates settle.
If this report has identified questions for your organisation
AI inventory, classification, and governance mapping are core components of the Compass AI Blueprint, Southern Sky AI's structured AI readiness and adoption roadmap for maritime organisations.
The Blueprint begins with the same foundations this report calls for: identifying the AI an organisation uses, mapping the AI Act, privacy, cyber, product-safety, and maritime obligations those tools activate, and building a governance framework proportionate to operational profile and regulatory exposure.
Compass AI Navigator then carries that work forward as a continuing relationship, keeping the policy current as the AI Act timetable, the Cyber Resilience Act, and your operation evolve.
The Engagement Guide sets out how both work together.
14Sources
References
- [1]EU AI Act, Regulation (EU) 2024/1689, EUR-Lex
- [2]Digital Omnibus on AI, provisional political agreement (7 May 2026); analysis, Hogan Lovells
- [3]FuelEU Maritime (Regulation (EU) 2023/1805), European Commission
- [4]European Maritime Single Window environment (Regulation (EU) 2019/1239), EMSA
- [5]Cyber Resilience Act (Regulation (EU) 2024/2847), European Commission summary
- [6]Product Liability Directive (Directive (EU) 2024/2853), EUR-Lex
- [7]prEN 18286, Artificial intelligence, Quality management system for EU AI Act regulatory purposes, CEN-CENELEC
- [8]Data Act (Regulation (EU) 2023/2854), European Commission
- [9]NIS2 Directive (Directive (EU) 2022/2555), European Commission
- [10]Machinery Regulation (Regulation (EU) 2023/1230) and Recreational Craft Directive (Directive 2013/53/EU)
- [11]Digital Omnibus on the digital legislative framework (GDPR, ePrivacy, NIS2, Data Act amendments, 19 November 2025); analysis, Sidley
- [12]EDPB Opinion 28/2024 on AI models (17 December 2024); CNIL AI guidance
- [13]Court of Rome annulment of the OpenAI / Garante fine (judgment of 18 March 2026), European Law Blog analysis
- [14]IMO adopts the non-mandatory MASS Code at MSC 111 (13 to 22 May 2026), IMO
- [15]IMO Resolution MSC.428(98), Maritime Cyber Risk Management in Safety Management Systems; IACS UR E26 and E27
- [16]Italy Law No. 132/2025 (national AI law, in force 10 October 2025)
- [17]Spain, AESIA (Agencia Española de Supervisión de la Inteligencia Artificial); Germany, Bundesnetzagentur AI market surveillance
- [18]EU Emissions Trading System for maritime transport, European Commission
- [19]ISO/IEC 42001:2023, AI management system
- [20]EMSA Single Programming Document 2025 to 2027, European Maritime Safety Agency

