Unlawful Interference Embraer ERJ-190AR 4K-AZ65, Wednesday 25 December 2024
ASN logo
 
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. You can contribute by submitting additional or updated information.

Date:Wednesday 25 December 2024
Time:06:28 UTC
Type:Silhouette image of generic E190 model; specific model in this crash may look slightly different    
Embraer ERJ-190AR
Owner/operator:Azerbaijan Airlines
Registration: 4K-AZ65
MSN: 19000630
Year of manufacture:2013
Engine model:General Electric CF34-10E
Fatalities:Fatalities: 38 / Occupants: 67
Other fatalities:0
Aircraft damage: Destroyed
Category:Unlawful Interference
Location:5 km NW of Aktau Airport (SCO/UATE) -   Kazakhstan
Phase: Approach
Nature:Passenger - Scheduled
Departure airport:Baku-Heydar Aliyev International Airport (GYD/UBBB)
Destination airport:Grozny Airport (GRV/URMG)
Investigating agency: AIID Kazakhstan
Confidence Rating: Information is only available from news, social media or unofficial sources
Narrative:
Azerbaijan Airlines flight J28243, an Embraer ERJ-190AR, crashed near Aktau Airport, Kazakhstan, after having declared an emergency. Flightradar24 data shows the aircraft having fluctuating altitude and speed data. There were 67 passengers with 29 surviving the crash.

Flight 8243 took off from Baku International Airport (GYD) in Azerbaijan at 03:55 UTC on a flight to Grozny Airport (GRV), Russia, that usually takes about one hour. The Russian Federal Agency for Air Transport (Rosaviatsiya) stated that during that morning the situation in the area of Grozny airport was 'very difficult'. At that time, Ukrainian military drones were reported to be carrying out attacks in the cities of Grozny and Vladikavkaz. Rosaviatsiya states that the airspace was closed as a result, without stating the timeframe of the closure in relation to flight 8243. In addition, there was 'dense fog' in the area of Grozny Airport, according to Rosaviatsiya. Metar data from 05:02 UTC show that there was an overcast cloud deck at 800 feet with a visibility in fog of 3500 m. Rosaviatsiya goes on to state that the aircraft made two attempts to land at Grozny, which were unsuccessful. The flight was then offered other airports for diversion and the flight crew decided to proceed to Aktau Airport. Flightradar24 ADS-B data stopped at 04:25 UTC reappeared at 06:07 UTC when the flight showed up over the Caspian Sea, squawking 7700 (emergency). Altitude and speed data are available from 05:14 UTC, showing fluctuating altitude and speed as the aircraft heads to Aktau Airport. According to local media, Kazaeronavigatsiya stated that the flight crew had reported problems controlling the aircraft.

Videos show that the aircraft collided with terrain in a right wing low, nose down altitude. The aircraft broke up and a fire erupted. Post accident photos show that the main cabin area was consumed by the ensuing crash fire. The tail section came to rest upside down away from the main wreckage and was free of fire damage.

Multiple videos, purportedly of flight J28243, were shared on social media. They show the oxygen masks had dropped in the cabin at some point before the accident. Also, a passenger was supposedly interviewed after surviving the accident. He stated having heard an explosion during the descent or approach. He also reported observing that shrapnel had perforated his life vest. Another in-flight video shows a hole in a flap track fairing on the left-hand wing. Additionally, post accident video footage of the tail section shows multiple small holes in the tailfin as well as horizontal stabilizer.

On December 27, Azerbaijan Airlines released a statement, reporting that it was suspending flights to several additional Russian airports after flights to Grozny and Makhachkala had already been suspended on December 25. This decision was made in accordance with the Azerbaijan State Civil Aviation Authority, and was based on the preliminary results of the investigation, "due to physical and technical external interference" and considering "potential risks to flight safety".

On December 28, according to RT news, "Russian President Vladimir Putin has called his Azerbaijani counterpart, Ilham Aliyev, to express condolences for the deadly plane crash that occured in Kazakhstan this week, the Kremlin said on Saturday. Putin offered an apology for the fact that an incident 'took place in Russian airspace,' adding that it occurred during a Ukrainian drone raid, which was being repelled by air defenses."

From the preliminary report and ATC transcript:

Upon the approach to Grozny, flight J28243 reported loss of both GPS (04:25 UTC) along with a terrain warning later being triggered (04:37 UTC). On their first approach to Grozny the flight requested an NDB approach to runway 26 due to the loss of GPS. They were subsequently cleared for an NDB V approach via the Remka1X arrival procedure. However a go around was initiated after an unstable approach and loss of LNAV heading again with the crew reporting loss of GPS (04:53 UTC). The crew requested a second approach NDB for runway 26. During this approach Grozny Tower loses flight J28243 from the dispatcher radar (05:01 UTC) flight J28243 requests vectoring (05:06 UTC) and asks if they should lower the landing gear. Grozny Tower reports flight J28243 to be 26km from the runway. After being cleared down to 500m, flight J28243 requests distance for further decent reporting maintaining 500m (05:09 UTC). Grozny Tower responds they see the altitude as 330m and flight J28243 responds their data shows 500m (05:09 UTC). Grozny Tower then clears flight J28243 to land (05:10 UTC), there is no response from flight J28243 until they state they are proceeding to Baku (05:11 UTC). Grozny Tower then responds with vectors.

The CVR registers a sonic boom at 05:13:31 UTC with the audible alarm for disabling the autopilot and automatic throttle being triggered. Following this multiple events are recorded, the 3rd hydraulic system dropped to 0 PSI with fluid level dropping to 0% (05:13:34), the control surfaces (Elevator, Aileron, Rudder) are fixed in the zero position - they will remain this way for the rest of the flight , a failure of the aircraft pitch trim system is recorded, the PIC stats the alarm on the EICAS screen is 'DOOR... SERVICE DOOR AFT OPEN' (05:13:36), the beginning of cabin depressurization is recorded (05:13:39), the 1st hydraulic system dropped to 0 PSI with fluid level dropping to 0% (05:13:47), and the pressure in the 2nd hydraulic system dropped to 4 PIS (05:13:54). At 05:13:56 UTC the CVR registers a second sonic boom.

At 05:14 UTC Grozny Tower instructs flight J28243 to expedite climb. The captain then contacts the cabin crew to clarify the situation with a flight attendant reporting, "Two seats exploded, I... um, I can't go over because the passengers are standing up, I'm reseating them.". Flight J28243 then contacts Grozny Tower stating "Grozny, we lost control, bird strike in the cabin. A bird strike and two seats in the cabin exploded", Grozny Tower asks what assistance is required and flight J28243 then request the nearest airport with good weather for landing specifying Minvody (225km northwest of GRV) (05:16 UTC). Grozny Tower responds "Azerbaijan 8243, at the 16-minute mark" twice before saying their message was unclear.

From 05:17 UTC - 05:26 UTC there is discussion of alternate airports with flight J28243 informing Grozny Tower of a loss of hydraulics at 05:22 UTC, before being told to switch to Rostov Control at 05:26 UTC. With Rostov Control flight J28243 further discusses alternates before deciding on Aktau. During this time flight J28243 informs Rostov Control that both engines are operational but aileron and elevator control is lost (05:39 UTC). Later they request descent to a lower altitude as oxygen is running low in the passenger cabin with some passengers losing consciousness stating that it is likely an oxygen cylinder exploded (05:52 UTC).

At 06:02 UTC flight J28243 contacts Aktau Tower requesting emergency landing on runway 11 and informing them that the aircraft is being managed by thrust levers due to loss of control surfaces. They are then vectored in for a visual approach. During the approach at 06:27:58 UTC the aircraft collided with the ground. 38 persons suffered fatal injuries, 16 serious injuries, and 13 minor/none injuries.

The aircraft was completely destroyed and partially burned due to a post-crash fire. An examination of the damage to aircraft structures revealed numerous through and non-through damages of various sizes and shapes in the tail section of the fuselage, vertical stabilizer and stabilizer, elevator and rudder. Similar damage was found on the left engine and left wing as well as on the units and components of the aircraft. In some places the damage was observed to have a rectangular shape.

METAR:

Grozny:
URMG 250430Z 26001MPS 3600 BR OVC007 03/02 Q1025 R26/290250 NOSIG RMK MT OBSC OBST OBSC QFE754/1005
URMG 250500Z 24001MPS 3500 BR OVC014 03/02 Q1025 R26/290250 NOSIG RMK QFE754/1005=
URMG 250502Z 24001MPS 3500 BR OVC008 03/02 Q1025 R26/290250 NOSIG RMK MT OBSC OBST OBSC QFE754/1005
URMG 250528Z 00000MPS 3500 BR OVC012 03/02 Q1025 R26/290250 NOSIG RMK QFE754/1005
URMG 250530Z 16001MPS 3500 BR OVC012 03/02 Q1025 R26/290250 NOSIG RMK OBST OBSC QFE754/1005


Aktau:
UATE 250600Z 03005MPS 9999 BKN036 04/M01 Q1025 NOSIG RMK QFE767/1023
UATE 250630Z 04006MPS 9999 BKN036 04/M01 Q1025 NOSIG RMK QFE767/1023

Accident investigation:
cover
  
Investigating agency: AIID Kazakhstan
Report number: 
Status: Preliminary report
Duration: 1 month
Download report: Preliminary report

Sources:

Preliminary Report:
In Russian - https://www.flightradar24.com/blog/wp-content/uploads/2025/02/J28243_4K-AZ65_Preliminary-Report.pdf
Translated by flightradar24 - https://www.flightradar24.com/blog/wp-content/uploads/2025/02/Azerbaijan-Airlines-J28243-Translated-Preliminary-Report.pdf

https://tengrinews.kz/kazakhstan_news/krushenie-samoleta-azerbaijan-airlines-bliz-aktau-online-557947/
https://tengrinews.kz/kazakhstan_news/krushenie-samoleta-v-aktau-poyavilis-novyie-kadryi-557945/
https://tengrinews.kz/my-country/poyavilos-video-padeniya-samoleta-bliz-aktau-557931/
https://www.wsj.com/world/dozens-feared-dead-in-crash-after-passenger-flight-diverts-from-russia-fb2cdf2c
https://www.euronews.com/2024/12/26/exclusive-preliminary-investigation-confirms-russian-missile-over-grozny-caused-aktau-cras
https://www.rt.com/russia/610125-putin-baku-plane-call/
https://t.me/vchkogpu/53624

Flightradar24 blog post:
https://www.flightradar24.com/blog/azerbaijan-airlines-e190-crashes-near-aktau/

Azerbaijan Airlines statement Dec.27: https://x.com/azalofficial/status/1872616922459586994
https://www.flightradar24.com/data/aircraft/4k-az65#3879c26d
https://twitter.com/flightradar24/status/1871835753157939640/photo/1
https://x.com/BNONews/status/1871821182066114873

Grozny (URMG) runway 26 NDB V approach chart: http://www.caiga.ru/common/airinter/validaip/aip/ad/ad2/urmg/1-ad2-rus-urmg-102.pdf

Location

Images:



Photo: Press service of the Ministry of Emergency Situations of Kazakhstan


4K-AZ65 at Antalya Airport June 18, 2016; photo: Mehmet Mustafa Celik (CC:by-sa)

Media:

Revision history:

Date/timeContributorUpdates
25-Dec-2024 07:15 ASN Added
25-Dec-2024 07:17 ASN Updated [Location, Embed code, ]
25-Dec-2024 07:25 ASN Updated [Embed code, Photo, ]
25-Dec-2024 07:29 Captain Adam Updated [Total occupants, Nature, Narrative, Category, ]
25-Dec-2024 07:35 ASN Updated [Total occupants, Nature, Source, Narrative, Category, ]
25-Dec-2024 07:39 ASN Updated [Location, Nature, Narrative, ]
25-Dec-2024 07:43 Captain Adam Updated [Total occupants, Location, Narrative, Category, ]
25-Dec-2024 07:46 ASN Updated [Narrative, ]
25-Dec-2024 07:47 ASN Updated [Source, Embed code, ]
25-Dec-2024 07:54 ASN Updated [Narrative, ]
25-Dec-2024 08:48 vasilf Updated [Embed code, ]
25-Dec-2024 09:01 ASN Updated [Narrative, ]
25-Dec-2024 09:15 ASN Updated [Embed code, ]
25-Dec-2024 09:29 ASN Updated [Embed code, Narrative, ]
25-Dec-2024 10:21 vasilf Updated [Embed code, ]
25-Dec-2024 10:27 ASN Updated [Total occupants, Source, Narrative, ]
25-Dec-2024 10:30 ASN Updated [Total occupants, Source, Narrative, ]
25-Dec-2024 10:31 ASN Updated [Photo, ]
25-Dec-2024 10:35 ASN Updated [Location, Category, ]
25-Dec-2024 10:35 ASN Updated [Location, ]
25-Dec-2024 11:02 vasilf Updated [Phase, ]
25-Dec-2024 11:44 Iceman 29 Updated [Embed code, ]
25-Dec-2024 11:44 Aerossurance Updated [Embed code, ]
25-Dec-2024 11:46 Iceman 29 Updated [Embed code, ]
25-Dec-2024 13:01 ASN Updated [Embed code, Narrative, ]
25-Dec-2024 15:09 Iceman 29 Updated [Embed code, ]
25-Dec-2024 15:30 ASN Updated [Total fatalities, Source, Embed code, Narrative, ]
25-Dec-2024 15:40 ASN Updated [Narrative, ]
25-Dec-2024 15:46 ASN Updated [Embed code, ]
25-Dec-2024 16:42 vasilf Updated [Embed code, ]
25-Dec-2024 16:47 Iceman 29 Updated [Embed code, ]
25-Dec-2024 16:59 ASN Updated [Embed code, Narrative, ]
26-Dec-2024 07:39 Anon. Updated [Narrative, ]
26-Dec-2024 07:39 RubenKelevra Updated [Embed code, ]
26-Dec-2024 08:03 Anon. Updated [Narrative, Photo, ]
26-Dec-2024 08:08 ASN Updated [Narrative, ]
26-Dec-2024 09:56 Iceman 29 Updated [Embed code, ]
26-Dec-2024 10:25 Anon. Updated [Source, Embed code, Narrative, ]
26-Dec-2024 10:25 ASN Updated
26-Dec-2024 14:51 ASN Updated [Source, Narrative, ]
26-Dec-2024 15:32 ASN Updated [Narrative, ]
26-Dec-2024 16:28 Iceman 29 Updated [Embed code, Narrative, ]
26-Dec-2024 16:29 Iceman 29 Updated [Embed code, Narrative, ]
26-Dec-2024 19:11 ASN Updated [Photo, ]
26-Dec-2024 19:14 Dolly564 Updated [Source, ]
26-Dec-2024 19:14 ASN Updated [Embed code, ]
27-Dec-2024 12:35 elabbas Updated [Source, Narrative, ]
27-Dec-2024 12:50 ASN Updated [Source, Narrative, ]
27-Dec-2024 12:57 ASN Updated [Narrative, ]
28-Dec-2024 08:37 ASN Updated
28-Dec-2024 09:44 Iceman 29 Updated [Embed code, ]
28-Dec-2024 15:00 ASN Updated [Source, Narrative, ]
28-Dec-2024 18:18 The Navigator Updated [Source, Narrative, ]
29-Dec-2024 08:29 ASN Updated [Source, ]
03-Jan-2025 11:02 ASN Updated
06-Feb-2025 10:09 Paradoxial Updated [Source, Narrative, ]
06-Feb-2025 10:27 ASN Updated [Accident report, ]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2025 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org