Lithuania Releases Interim Report on Swiftair Cargo Plane Crash in Vilnius
Copyright © AirTeamImages.com - Paul Buchroeder
The Transport Accident and Incident Investigations Division under Lithuania's Ministry of Justice has published an interim report detailing the early findings of the safety investigation into the Swiftair cargo aircraft crash that occurred near Vilnius Airport on November 25, 2024. The tragic accident involved a Swiftair Boeing 737-400 (EC-MFE) operating a flight on behalf of DHL, resulting in the death of one pilot, severe injuries to the co-pilot and two passengers, and the destruction of the aircraft.
Overview of the Incident
According to the interim report, the aircraft departed Leipzig Halle Airport at 02:08 local time. Just over an hour later, it crashed during the final approach phase while descending into Vilnius. Based on initial data from the flight and cockpit recorders, the safety report aims to provide transparency and an overview of the circumstances that led to the accident.
Key Preliminary Findings
The investigation has identified several critical factors that contributed to the crash:
Hydraulic System B:
One of the central issues identified was malfunctioning the aircraft's B hydraulic system. Data from the Flight Data Recorder (FDR) showed that the system's electric and engine-driven pumps were turned off during the flight. This led to reduced control over the aircraft's configuration. The crew believed the flaps were extended, but they were not, significantly affecting the aircraft's handling on approach.
Image Source: Lithuania's Ministry of Justice
Anti-Ice System Conditions:
The crew discussed activating the anti-icing system due to suitable atmospheric conditions at 03:12. However, recorded data confirmed that the anti-icing systems were never engaged. The failure to activate this system in potentially icing conditions may have degraded the aircraft's performance.
Communication:
Communication issues between the flight crew and Vilnius Area Control Center were also issues. At 03:09, the captain attempted to contact air traffic control but received no response. After troubleshooting with the co-pilot, contact was successfully established at 03:10. Later in the approach, additional confusion occurred when the crew tried to switch to the aerodrome control frequency but used the wrong frequency on two occasions.
Timeline of Critical Events
-
02:08 – Aircraft departs Leipzig Halle Airport.
-
03:09 – First unsuccessful attempt to contact Vilnius ACC.
-
03:10 – Successful radio contact established and descent clearance received.
-
03:12 – Crew discusses anti-ice activation; switches remain off.
-
03:17 – Hydraulic system B pumps are deactivated.
-
03:26 – Aircraft enters final approach.
-
03:27 – Miscommunication occurs during frequency change.
-
03:27:56 – Flaps confirmed retracted by the co-pilot.
-
03:28:07 – Terrain warning system activates.
-
03:28:08 – Aircraft impacts terrain.
READ NEXT...
- 134174
Tracking Helicopters With AirNav Radar
Today we'll explore how to filter and track helicopters on AirNav Radar. Read this blog post to learn more... - 67594
Replay Past Flights with Playback
AirNav RadarBox officially launches the playback function on RadarBox.com, allowing users to replay the air traffic for a specific date and time in the past, within a 365-day period. Read our blog post to learn more about this feature. - 50349
AirNav Radar Features: NAVAIDs, Waypoints & Routes
This week AirNav RadarBox's feature of the week focuses on NAVAIDs, waypoints, and routes, a set of navigational features available on the Radarbox.com website.