More than one-quarter of ********** flights experienced delays on Friday as the ******* worked to return service to normal following a technical malfunction the previous day.

********** had warned travellers early Friday morning they should be prepared for further flight disruptions. In its daily travel outlook, the carrier said that while its IT system was stable, flights may be affected at nine of Canada’s busiest airports, including Toronto’s Pearson, Montreal, Vancouver and Calgary.

Thursday’s outage led to more than 500 flights – over three-quarters of its trips – to be ******* or cancelled on the day, creating what the ******* said were “rollover effects” just prior to the weekend.

A total of 144 ********** flights, or 27% of the *******’s scheduled load, had been ******* Friday as of around 4:30 p.m. EDT, along with 33 cancellations, according to tracking service FlightAware.com.

An additional 56 flights with ********** Rouge saw delays, one-third of its daily load, plus 23 cancellations.

“********** has stabilized its communicator system and it is functioning normally. However, due to the effects of Thursday’s IT issues on our schedule, some flights may be ******* this morning as we reposition aircraft and crew,” it said in an emailed statement.

“Customers are advised to check the status of their flight before going to the airport. Our flexible travel policy remains in effect for customers to change their travel plans at no charge.”

The ******* did not clarify when it expected its flight schedule to fully return to normal.

Thursday’s **********, sourced to the system used by the ******* to communicate with aircraft and monitor their performance, came one week after ********** grounded its planes for about an hour when the same system experienced a separate issue.

That day, 241 ********** flights – 46% of its trips – were *******, according to FlightAware. Another 19 flights were also cancelled.

********** said it has been in the process of upgrading the communicator system.