A Croatia Airlines Airbus A220-300, registered 9A-CAN and delivered to the carrier in late June last year, skidded off the runway at Split Airport during its takeoff roll this afternoon. The aircraft, operating as flight OU412 from Split to Frankfurt, reached a speed of 131 knots before aborting takeoff and coming to a stop adjacent to the runway (pictured below). All passengers were safely evacuated, with no injuries reported. The cause of the incident remains unknown at this stage.
In a statement, Croatia Airlines said, “Croatia Airlines’ Airbus A220-300 aircraft, registered 9A-CAN, which was scheduled to operate today’s regular international flight OU412 from Split to Frankfurt, aborted its takeoff at Split Airport. There were 130 passengers and five crew members on board, including two pilots and three cabin crew. All passengers and crew members are safe, and no injuries have been reported". It addeed, "According to the initial available information, the crew aborted takeoff in line with prescribed safety procedures. Passengers have disembarked and are currently in the passenger terminal at Split Airport, where they are being provided with all necessary assistance for the continuation of their journey".
Croatia Airlines said it is in constant coordination with Split Airport, the relevant emergency services and aviation authorities. The airline added that the safety of passengers and crew remains its absolute priority, with further information to be released following the completion of the initial technical assessments and official procedures. Emergency services are currently working to remove the jet and determine the cause of the incident, while Croatia’s air accident investigation authority and civil aviation regulator have been notified.
All departures have now been delayed at Split Airport, while incoming aircraft are being diverted.
Good to hear everyone is safe
ReplyDeleteGosh. Thankfully everyone was ok. I assume pilots got some inidcation relatively late in the takeoff roll.
ReplyDeleteThe cowling of engine no. 1 seems to be damaged though…
ReplyDeleteFrom now hat I've heard, is that for some unknown reason the aircraft appear to veered of before the take off. The pilot decided to abort the take off and safely stopped the aircraft. Investigation is ongoing.
DeleteWhat was the weather like in SPU?
ReplyDeleteNot great but nothing extraordinary.
DeleteAre we sure? Tivat airport was closed this morning due to weather
DeleteMaybe strong winds blew them off the runway? Let's keep all those involved in our prayers.
DeleteThere is a video on Instagram and you can see that as it is about to rotate it turns to the right and ends up in the grass. I think winds are to blame.
Deletefullthrustnews is the profile.
video:
Deletehttps://x.com/i/status/2055667445965185425
This looks like engine went to zero and the plane got turned around...lucky lucky escape
DeleteGlad everyone is safe. That’s the only thing that really matters. The fact the crew aborted at high speed and everyone walked away shows the safety systems worked as intended.
ReplyDelete131 knots is no joke. That’s a serious rejected takeoff speed, so credit to the pilots for handling what must have been a very stressful situation professionally. Curious to know what triggered the abort so late in the roll.
ReplyDeleteAgree! The crew deserve praise. Aborting at that speed and getting everyone off safely without injuries is exactly what training is for.
DeleteAccording to the video this might be pilot mistake as the plane suddenly loses control and goes off runway.
DeleteBefore people start blaming the airline or Airbus, let’s wait for facts. Runway contamination, bird strike, tyre issue, warning indication - there are dozens of possibilities.
ReplyDeleteDon't think anyone is blaming either.
DeleteThis will create more of a mess for SPU than for OU honestly.
ReplyDeleteYep. Diverting inbound aircraft in the middle of the afternoon during summer operations could create a huge knock on effect.
DeleteThings like this happen ever once in a while...It is important that they do not have some systematic negligence in their procedures...
ReplyDeleteNot bad LF at all, glad everyone is safe
ReplyDeleteAccording to some unofficial information, the runway is supposed to be too short in these conditions. But judging by the pictures, this does not seem to be the main reason
ReplyDeleteShould they not take that into account before they start take off??
DeleteCould this be related to brakes, tyres or engine indication? 131 knots suggests they were very committed to departure before something serious happened.
ReplyDeleteA takeoff shouldn't be rejected for a tyre failure at high speed - it's much safer to continue, since the aircraft's ability to stop is significantly reduced.
DeleteFeel sorry for the passengers. Hope Croatia Airlines takes good care of them.
ReplyDeleteThey will.
DeleteThey are not. No one has checked in on us. They gave us one free drink. We have no idea where to go since we missed our connection. Information is being very rude and yelling at us and the elderly gentleman behind us.
DeletePlease keep us updated
DeleteThis is not pleasent. I was on an aborted takeoff a month ago on JU at Berlin Airport. We stopped normally on the runway but during those few seconds of breaking at full spped it was not pleasent. Pilot said they received an unusual indication.
ReplyDeleteI had it on a Lufthansa flight out of Frankfurt at high speed- I am a frequent an calm flyer but that was really frightening..
DeleteThe important takeaway is that everyone got out safely. Aircraft can be repaired or replaced.
ReplyDeleteAn aircraft being repaired and replaced by an airline in deep financial trouble is not something that can be easily done.
DeleteUnless insurance covers it which they might.
DeleteWhen i started reading i knew there was a 90% chance the flight was either to Munich or to Frankfurt.
ReplyDeleteNot may other possibilities are there, isn't it?
DeleteTake-off roll starred at 1128Z. Metar at that time was:
ReplyDeleteMETAR LDSP 161100Z 31017G27KT 9999 -RA FEW018 BKN045 13/10 Q0997 TEMPO SHRA FEW025TCU BKN045=
METAR LDSP 161030Z 32016KT 9999 -RA FEW018 BKN040 14/11 Q0997 NOSIG=
So the crosswind component was right around 15 knots (RWY05 used for take-off). I'm not rated on the A220 myself, but it looks like its dry runway takeoff crosswind limit is 32 knots
Forgot to include the 1130Z metar:
DeleteMETAR LDSP 161130Z 28017KT 240V300 9999 -RA FEW018 BKN055 13/10 Q0998 TEMPO SHRA FEW025TCU BKN045
How did the passengers evacuate? Did they use slides?
ReplyDeleteThe left engine looks to be damaged
ReplyDeleteWe were on that flight. We got absolutely zero assistance from the airline. No one asked if we were okay. We missed our connection in frankfurt and no one will tell us what to do. Information desk is just yelling at everyone. We are all just confused and looking for help.
ReplyDeleteDid you hear any unusual noises during the take-off roll?
Delete- They were towing the plane. It's not clear exactly what happened, but basically, it skidded during takeoff - Bralec
ReplyDelete- Bralka said: You could see a cloud of smoke, dust, and parts of lights flying,
Source: 24sata.hr
__________
I am interested in your opinion.
One of the possible things could be a "restrained" control lever for operating the vehicle while taxiing to the runways?
I apologize, it says that it is not a pilot error.
DeleteHowever, on another portal it is written that there could be a malfunction in the engines (which are said to be very typical for the A220) Pratt & Whitney. They mention that in the past 20% of the fleet was grounded due to these engines. (These engines have the most faults)
We don't know it wasn't pilot error since the investigation is not over. We can just speculate. Looks like wind and loss of control.
DeleteJudging by the statements and all the percentages, the cause could also be the engine. It is true, however, that the pilot handled the plane well in difficult conditions with 130 passengers.
Delete