Skip to main content

Arkia’s 2026 Loss Could Reach $80 Million, Report Says

Arkia could end 2026 with losses of about $80 million, according to a report published on November 14. The Israeli airline reportedly needs immediate financing to cover salaries and flight operations, while employees are concerned about their November wages. The reported financial pressure includes losses on long-haul services to New York, Bangkok, Phuket and Hanoi. Fuel was estimated to account for about 45% of flight costs, compared with an anticipated 25%, with increased fuel expenses reportedly contributing more than $50 million to the losses. Loss-making long-haul routes are expected to face reductions in service or frequency, according to the report. It also cites an industry assessment that two narrow-body aircraft would need to be sold. Arkia is marketing discounted flights for 2027, with advance ticket purchases bringing in cash before those journeys take place. The disclosure follows the Nakash brothers’ November 12 announcement of an agreement for an investor group to take control of the airline. The reported financing package envisages about $30 million from the investors and $8.5 million from the Nakash group. Employees, who hold approximately 22% of Arkia, are concerned about dilution of their stake and job losses.

Sources

Secondary sources:12
Courtroom-sketch editorial illustration of an Arkia Boeing 757 taxiing at Amsterdam Schiphol Airport, based on an archival July 2013 photograph and used as aviation context for the reported 2026 loss estimate.

Commentary

Add Your Voice
Loading comments…

Related articles

  1. Nakash Brothers Sign Agreement for Investor Group to Take Control of Arkia
  2. Arkia Owners Reportedly Consider Stock-Market Shell Merger
  3. Israir CEO Says Arkia Acquisition Review Is Preliminary
  4. Arkia Owners Warn of Share Dilution Unless Employees Join Funding Round
  5. Alrov Sets November 4 Share Delisting After Akirov Tender Offer

Voices

Write about thisPost a clip

Something went wrong

We couldn't complete that action. Check your connection and try again.