Skip to main content

Yemenia to maintain regular Sanaa-Moroni flights

Yemenia has reneged on a decision to suspend all flights to Moroni after the crash of one of its planes off the Comoros Islands, saying on Saturday that regular Sanaa-Moroni flights would continue.

ADVERTISING

AFP - Yemenia went back on a decision to suspend all flights to Moroni after the crash of one of its planes off the Comoros Islands, saying on Saturday that regular Sanaa-Moroni flights would be maintained.

"We have cancelled all additional flights between Sanaa and Moroni but we are keeping the regular, twice weekly flights" between the two capitals, Yemenia's chief executive office Abd al-Khaleq al-Qadhi told AFP.

But Qadhi said the airline would halve the frequency of those flights if there were not enough passengers.

Earlier, a Yemenia statement issued in Paris said that all flights to the Comoros would be suspended in the aftermath of Tuesday's crash of an Airbus A310 near Moroni that killed 152 people.

A 12-year-old girl was the only survivor.

"In light of serious incidents in recent days and major risks that some passengers posed to airport staff, our company and passengers, Yemenia has decided to no longer serve Moroni for an indefinite period from July 3 until the situation eases," it said in a statement.

Yemenia's lawyer in France, Laurent-Franck Lienard, told AFP that the airline would however continue to fly to other destinations -- including Paris-Sanaa, Paris-Kuala Lumpur and Paris-Jakarta.

On Thursday, the airline suspended services from Marseille -- home to a large Comoran expatriate community, and Qadhi confirmed the flights were cancelled indefinitely.

Yemen's civil aviation chief Hamed Ahmed Faraj also confirmed that Sanaa-Moroni and Sanaa-Paris flights would be maintained.

"Yemenia continues regular flights between Sanaa and Paris, and Sanaa and Moroni," Faraj said in remarks carried by Yemen's official news agency Saba.  "We have only suspended additional flights," Faraj said.

This page is not available

The page no longer exists or did not exist at all. Please check the address or use the links below to access the requested content.