Swiftair DHL cargo plane crashes near Vilnius airport

Swiftair DHL cargo plane crashes near Vilnius airport

What was a Spanish Swiftair-operated Boeing 737-400 freighter, flying for DHL, doing when it crashed on short final at Vilnius Airport? The aircraft was covering the Leipzig-Vilnius route, a cargo flight that, according to data tracked by commercial aviation observers, ran almost daily. The accident left at least one person dead, with debris scattered in a populated area close to the runway. Weather conditions were good. That is the first uncomfortable piece of the puzzle: an airplane crashing on approach with visibility more than sufficient for visual flying.

What is known about the accident and the Leipzig-Vilnius route

The flight departed from Leipzig, a major logistics hub in eastern Germany, and landed in Vilnius, which serves as a distribution center for cargo in the Baltic region. This route was not arbitrary: Spain’s primary cargo airports are Vitoria and Zaragoza—neither has a port—and Vilnius plays that same role for the Baltics. Some point out that such routes, with origins and destinations obscure to the general public, are routine in air freight transport.

The company, Swiftair, is largely unknown to the average passenger. It operates mainly freighters, with a fleet that may reach around 50 aircraft within its parent group structure. An industry veteran summarizes the paradox: “It was hard work, but the company was quite serious regarding maintenance, training, and procedures.” Others who have worked there describe an organization with issues, characterized by high turnover among technicians who leave as soon as they obtain their licenses.

Aircraft history and company background

The 737 is a long-lived model. In cargo operations, it is common to see aircraft older than 25 years, although in top-tier airlines the average age is significantly lower. The lingering question in the analysis is whether the plane was nearing retirement or still had many hours and cycles ahead. It depends on usage, not just the calendar date. Some recall flying in 22-year-old units that already felt “old.”

The company’s track record also factors into the equation. Ownership is linked to former Air Force pilots, according to circulating reports, and the safety officer of one of the group’s subsidiaries was aboard as captain. That detail is disorienting: this was not a training flight nor a low-cost charter. It was the first flight of the weekly rotation.

Technical hypotheses: GPS, ILS, and autopilot modes

One theory that gained significant traction involved GPS jamming or signal interference. The technical response is firm: in commercial aviation, GPS is a backup instrument, not a primary navigation system. En route flights use INS and VOR-DME; approaches rely on ILS. If the signal is lost, it recovers without permanent damage to instrumentation. “When you enter Israeli airspace, your GPS always drops out,” one pilot summarizes.

More weight is given to the ILS clue. Apparently, a Beechcraft was conducting calibration checks on the signal around those dates. A video shows a sudden nose-down descent. Could the aircraft have captured the wrong glide path? Did the autopilot’s approach mode fail? On a 737, switching from AP ILS mode to manual should leave the aircraft trimmed. If it did not, the transition could have been rough.

The stall hypothesis was also considered. At low altitude, with an aircraft of this type, a stall is practically unrecoverable. The natural design tendency is to pitch down, worsening the problem if it occurs near the ground. And all this under visibility conditions that, on paper, allowed seeing the runway miles before touchdown.

Human factor: tower, readback, and fatigue

Communication with Vilnius Tower was not clean. Audio reveals confusion between Runway 18 and 19—in reality, it is the same runway, designated 01/19—and the frequency was difficult to hear clearly. The controller’s lack of readback adds noise to the sequence. These are not proofs of anything, but they sketch a scenario of high workload on both sides of the radio.

Fatigue is another variable. It was the first flight of the rotation, ruling out accumulated weekly tiredness, but not early-morning wake-up fatigue. Two miles out, the aircraft was not stabilized. In aviation, that is a red flag.

Geopolitical context: cargo, NATO, and suspicions

Leipzig hosts a NATO logistics node and is the operating base for Ukrainian An-124s serving the Alliance since the 1990s. Vilnius is a cargo hub for the Baltic states. Against this backdrop, theories about what the plane was carrying proliferate. Some claim it transported weapons, while others recall military convoys accumulating at bottlenecks in Eastern Europe. There is no official confirmation of any of this.

The shadow of sabotage also looms. A previous attack on a DHL logistics center in Leipzig is mentioned. And, as always, there is the temptation to attribute the crash to Moscow. It is the loudest hypothesis and the one with the least evidence on the table.

---

The report will take time. Meanwhile, the uncomfortable question is not who shot it down, but how an aircraft with good visibility, a Spanish crew, and a known route ended up on the ground two miles from the runway. Those who know do not have an answer. Those who don’t have already chosen a culprit.