The Interface Is Still Working

airBaltic does not look like a company in crisis. Its planes are still taking off, its website is still selling tickets, and passengers are still moving between Riga, Tallinn, Vilnius and the rest of Europe. The aircraft are modern, the cabin crews are working, and the interface still feels alive.

Behind that interface, the airline is trying to raise emergency financing from its bondholders. It has a €380 million bond due in 2029, a €30 million Latvian government loan due in August, and a credit rating under pressure. The company can carry millions of passengers and still struggle to generate enough cash to support the system underneath them.

The plane can be full and the airline can still be broken.

Most people experience a company through its visible layer. We see the app, the ticket, the airport screen, the cabin and the arrival notification. When these things work, we assume the company behind them is healthy. The service becomes evidence that the system is functioning.

But interfaces can continue working long after the underlying structure has become unstable. A plane taking off tells us that the airline had enough operational capacity to complete that flight. It tells us almost nothing about the cost of the aircraft lease, the interest on the debt, the maintenance obligations accumulating in the background, or whether the airline has enough cash to survive another winter.

A functioning interface can be the final layer of normality covering a system under extreme pressure.

In technology, growth is usually presented as proof that a product is working. More users, more transactions and more engagement all appear as positive signals. Airlines have their own version of this language: more passengers, more routes, more aircraft and more revenue.

Each new passenger also creates an obligation. Every route requires crews, fuel, airport agreements, maintenance capacity and replacement aircraft when something fails. Every new aircraft can bring another lease payment. Growth increases the surface area of the system, and eventually the surface can become larger than the structure supporting it.

airBaltic built much of its strategy around the Airbus A220. A single modern aircraft type promised efficiency, a simpler fleet and a better passenger experience. The airline then planned to expand toward nearly one hundred aircraft.

That same decision concentrated its risk. When engine inspections and maintenance delays grounded part of the fleet, airBaltic had fewer alternatives. The standardisation that made the system efficient also made it fragile.

This is common in interaction design. The smoothest experience is often created by hiding complexity from the user. The passenger sees a direct route because aircraft, crews, maintenance schedules, airport slots and financing have already been coordinated behind it. The user sees one simple button because hundreds of decisions have already been made by the system.

Hiding complexity improves usability. It also makes fragility harder to see.

airBaltic is legally an airline company, but functionally it behaves like regional infrastructure. For Latvia, it is more than a brand selling tickets. It feeds Riga Airport, connects local businesses to European markets, supports tourism and gives the country relevance as an aviation hub. Its network also affects Estonia and Lithuania, where many routes may never be important enough for larger airlines to maintain on their own.

A normal company can be allowed to shrink or disappear when its business model stops working. Infrastructure is harder to abandon because its disappearance creates costs across the entire surrounding system.

This leaves the Latvian government in a difficult position. It owns most of the airline, absorbs much of the financial risk and faces political anger whenever more support is needed. At the same time, letting the company collapse could damage Riga Airport and weaken Baltic connectivity for years.

The state is expected to behave like an investor while carrying responsibilities no normal investor has.

Lufthansa adds another layer to the story. It owns a minority stake and already uses airBaltic aircraft and crews inside its wider network. Latvia is also negotiating with another strategic investor, with the continued role of Riga as the airline's main hub forming a central condition.

A future rescue could keep the planes flying and the crews employed while gradually changing what airBaltic actually is.

The green tails could remain visible across Europe. The brand could survive. More of the airline's capacity, however, could be used to operate flights for larger groups. The independent ambition of building a major Baltic carrier could slowly become the safer role of supplying aircraft, crews and regional connectivity to somebody else's network.

From the outside, this would look like survival. Inside the system, it would be a transfer of agency.

The airBaltic crisis shows why organisations cannot be judged only through their customer-facing layer. A polished interface can coexist with a damaged balance sheet. Record passenger numbers can coexist with a liquidity crisis. A company can keep delivering its service while losing control over the conditions that make delivery possible.

The interface often fails last.

By the time passengers notice that routes have disappeared, flights have been cancelled, or the brand has become part of something larger, the important decisions may already have happened in government meetings, debt negotiations and restructuring documents far away from the airport.

airBaltic is still flying.

That does not mean the system underneath it is working.

AI authorship note

This essay began with Kris Haamer asking what was happening with airBaltic and looking for the Raw Drafts angle. AI helped research the airline's financing crisis, identify the contrast between the visible passenger experience and the invisible financial system, and shape the final paragraph structure. Kris selected the argument, requested the paragraph form and made the publication decision.