Croatia Airlines Flight OU412 of Airbus A220-300 traveling from Split Airport, Croatia to Frankfurt Airport, Germany triggers widespread commercial flight disruption: New update you need to know

Croatia commercial airspace networks recorded a localized flight disruption on Saturday, May 16, 2026. A scheduled international departure suffered a high-speed rejected takeoff and subsequent runway excursion at Split Airport. This sudden operational safety event involving Croatia Airlines Flight OU412 on the route to Frankfurt forced a complete suspension of local airfield movements. The incident required a multi-agency emergency response to secure the airfield. Technical teams immediately initiated protocols to evaluate the structural integrity of the active infrastructure.

What Are the Technical Specifications of the Involved Croatia Airlines Fleet Asset?

The transport equipment utilized for this European service was an Airbus A220-300 narrow-body commercial passenger jet. Civil aviation registry data identifies this specific airframe by its official alphanumeric registration code 9A-CAN. Corporate fleet tracking documentation indicates the manufacturer delivered this twin-engine passenger aircraft to the operating carrier in June 2025. The aircraft had been in active regional service for less than one year prior to the incident in Split, Croatia. This generation of regional aircraft features advanced fly-by-wire flight control systems and highly efficient aerodynamic profiles designed for mid-range international transit corridors.

The internal arrangement of the aircraft carried a standardized passenger manifest for the international route to Frankfurt Airport, Germany. Total asset occupancy logs verify that 135 individuals were entirely on board during the scheduled flight sequence. This total figure includes a passenger load factor of 130 travelers. The operational workforce managing the airframe comprised 5 certified crew assets. The flight deck crew consisted of 2 pilots managing the primary navigation instruments and engine control systems. The cabin infrastructure was staffed by 3 professional cabin crew members responsible for safety compliance and passenger management.

Flight Profile and Technical Fleet Asset Specifications

Fleet delivery parameters establish the baseline operational history of the aircraft.

The operational readiness of the regional fleet depends on strict adherence to continuous airworthiness directives. The Airbus A220-300 model utilizes specialized turbofan engines engineered for quiet operation and lower emissions. The specific aircraft registration 9A-CAN represented one of the newer additions to the regional operator’s short-haul network. Fleet deployment records indicate the airframe was fully integrated into daily line operations between major European hubs. Maintenance logs and preceding inspection certificates indicate the asset met all baseline structural and operational requirements before entering the active taxiway system on the afternoon of the incident.

How Did the High-Speed rejected takeoff and runway excursion Transpire According to flight tracking telemetry?

The operational sequence began during the early afternoon peak traffic window at Split Airport, Croatia. The Airbus A220-300 was positioned onto the active surface of Runway 23 for departure processing. Environmental conditions permitted standard visual and instrument flight operations. At approximately 1:30 PM local time, the flight deck crew initiated engine power acceleration to commence the takeoff roll along the paved surface.

Official flight tracking telemetry captured the dynamic performance metrics of the accelerating aircraft along the runway structure. The data indicates the passenger jet reached an operational ground velocity of approximately 131 knots during the initial acceleration phase. At this critical high-speed junction, an unidentified operational anomaly prompted the flight crew to execute a mandatory rejected takeoff procedure. The flight deck pilots immediately pulled back engine power to initiate maximum emergency deceleration protocols.

During the high-speed deceleration phase, the airframe tracking data recorded an uncommanded directional deviation. The commercial jet drifted laterally away from the painted runway centerline structure. The vehicle partially departed the paved surface of Runway 23 entirely. The deceleration sequence concluded with one side of the aircraft landing gear coming to a complete stop within the unpaved grassy safety margins.

Chronological Order of Event Telemetry

• Positioning Phase: The Airbus A220-300 enters active Runway 23 at Split Airport, Croatia.
• Power Application: The flight crew initiates departure acceleration at approximately 1:30 PM local time.
• Velocity Acquisition: The airframe achieves an operational ground speed of 131 knots along the pavement.
• Abort Execution: The flight deck crew identifies an operational anomaly and triggers a rejected takeoff protocol.
• Directional Deviation: The decelerating aircraft drifts laterally away from the established runway centerline.
• Surface Departure: The airframe veers partially off the paved structure during the high-speed deceleration phase.
• Final Stoppage: One side of the regional jet comes to rest inside the adjacent grassy safety perimeter.

Takeoff roll velocities on Runway 23 crossed critical decision thresholds prior to deceleration.

Operating parameters for regional passenger jets dictate precise decision-speed velocity limits known as V-speeds. The documentation of a 131-knot velocity indicates the aircraft was operating close to its takeoff decision threshold when the abort sequence began. The application of maximum mechanical braking systems and aerodynamic spoilers represents standard operational behavior during an emergency stop. The unexpected lateral drift off the centerline suggests a loss of directional control during the deceleration phase. This performance deficit forms the core focus of technical data analysis by flight operations specialists.

What Structural and Airfield Infrastructure Damages Resulted From the Safety Anomaly?

The lateral deviation of the airframe caused immediate contact with fixed airfield objects located along the perimeter of Runway 23. Official data verified by Split Airport, Croatia management and passenger handling logs confirmed the technical parameters of the physical damage sustained by the airframe and the local infrastructure. The physical data confirms that the Airbus A220-300 sustained external physical damage during the runway excursion. The fuselage and wing structures collided directly with a vertical airfield marker sign. The kinetic impact also destroyed several runway edge illumination lights situated along the paved boundary.

The flight deck crew successfully secured the propulsion systems and activated standard emergency grounding protocols on the field. Flight attendants coordinated a rapid, controlled disembarkation of all 130 passengers directly onto the airfield surface. Specialized airport emergency personnel arrived at the taxiway environment within designated response timelines. Ground crews utilized specialized transit assets to safely transfer all 135 individuals from the active field to the main terminal building. Official passenger handling logs verified that all travelers and crew members escaped the event completely unharmed, reporting zero physical injuries.

Collisions with ground-based guidance markers compromised secondary airport systems.

The destruction of airfield signage and edge lights requires immediate remediation to maintain compliance with international regulatory standards. Airfield marker signs provide critical visual guidance to pilots navigating the complex taxiway networks during low-visibility operations. The fracturing of multiple runway edge lights also impacts the lighting circuits that define the safe landing parameters of the runway surface. Engineering crews must perform comprehensive electrical isolation tests to ensure that the damaged circuits do not compromise the integrity of the remaining visual aid systems across the wider facility.

What Immediate Air Traffic Mitigation Protocols Were Enforced Following the flight disruption?

The immobilization of the commercial passenger jet forced an immediate freeze on all local runway movements. Air traffic control personnel implemented a temporary suspension of all arrivals and departures at Split Airport, Croatia. This operational freeze generated a cascading flight disruption across regional European aviation networks. Incoming international flights were actively intercepted by regional controllers and diverted to alternative landing facilities.

Scheduled departures originating from the facility faced immediate cancellations or prolonged scheduling delays. Ground operations teams deployed heavy specialized recovery equipment to the unpaved perimeter of Runway 23. Technical teams conducted systematic towing maneuvers to extract the airframe from the grassy safety zone. The runway remained completely closed until maintenance crews cleared all broken illumination debris from the pavement.

Regional diversion vectors reallocated incoming commercial traffic to alternative international airfields.

The closure of a primary runway at a key European regional airport triggers extensive air traffic management interventions. Air traffic control centers must coordinate with neighboring airspace sectors to redirect airborne flights to designated alternate airports. This process requires real-time calculations of fuel reserves, landing weights, and terminal gate availability at adjacent facilities. The operational backup affects airline crew scheduling limits and passenger connecting itineraries across multiple international hubs. This operational friction emphasizes the broad economic impact of localized airfield safety events.

Which Regulatory Agencies Are Directing the Investigation Into This Event to Ensure aviation safety?

The preservation of physical and digital flight data remains a mandatory requirement under national transport safety legislation. Croatia Airlines initiated immediate compliance protocols with state emergency services and regional transport management bodies. Two independent government entities assumed primary legal jurisdiction over the physical accident site and the technical flight datasets. These authorities will direct all structural and mechanical inquiries into the event.

The Croatian Civil Aviation Agency took immediate control of the operational oversight logs and crew certification data. Simultaneously, the Air, Maritime and Railway Accident Investigation Agency launched a comprehensive technical inquiry to identify the underlying cause of the runway excursion. Investigators will download and analyze the flight data recorders and cockpit voice logs. The investigation will evaluate the braking dynamics, aerodynamic control surfaces, and tire friction coefficients under high-speed deceleration parameters. The goal remains to establish definitive safety directives to preserve global aviation safety baselines.

National transport accident investigation boards initiated data collection protocols for the black box telemetry.

The retrieval of the solid-state flight data recorder and the cockpit voice recorder represents a critical phase of the safety investigation. Technical experts will analyze thousands of parameters, including engine thrust settings, brake pressures, and rudder inputs. This objective data will be cross-referenced with air traffic control voice logs and environmental weather recordings. The final analytical reports are designed to uncover systemic issues rather than assign individual blame. These findings will determine whether modifications to regional pilot training or aircraft component designs are required to prevent a recurrence.

The rapid containment of the Croatia Airlines Flight OU412 incident highlights the critical value of robust emergency response frameworks. While the initial high-speed rejected takeoff caused a complex runway excursion, the adherence to strict safety procedures prevented injuries. The temporary flight disruption at Split Airport, Croatia highlighted the sensitivity of modern aviation hubs to sudden runway closures. As the technical investigation progresses under the oversight of national transport boards, the detailed data extracted from flight tracking telemetry will be used to reinforce broader aviation safety directives. The continuous monitoring of these regional incidents ensures that international flight networks maintain the highest possible operational standards for global travel.

Image: Croatia Airlines