Shocking Runway Overrun On Takeoff At Belgrade Airport

Shocking Runway Overrun On Takeoff At Belgrade Airport

23

As I wrote about earlier this week, an absolutely wild accident took place at Belgrade Airport on Sunday night. As several days have now passed, more details are emerging about what happened, and it only makes this incident even stranger. Let’s cover everything we know as of now.

Embraer E195 has bizarre takeoff from Belgrade Airport

As reported by The Aviation Herald, this incident happened on Sunday, February 18, 2024, and involves Air Serbia flight JU324, scheduled to operate from Belgrade (BEG) to Dusseldorf (DUS). The flight was operated using a 16-year-old Embraer E195 with the registration code OY-GDC.

This aircraft actually belonged to Marathon Airlines, a Greek charter airline. The airline has been operating five Embraer jets on behalf of Air Serbia since June 2023, to allow the airline to add capacity. This aircraft even has the Air Serbia livery.

At 5:38PM local time, the aircraft attempted to take off from runway 30L. Runway 30L is 11,483 feet (3,500 meters) long, so that’s plenty for a jet of this size. However, the aircraft started its takeoff roll at taxiway D5, so it was doing a midfield takeoff. Taxiway D5 only gave the aircraft 4,175 feet (1,273 meters) to take off.

That wasn’t enough runway length, so the aircraft ended up overrunning the runway, and not just by a little bit:

  • The aircraft collided with some ground equipment at the end of the runway
  • The aircraft then became airborne 1,650 feet (500 meters) past the end of the runway (!!!!!!)
  • The aircraft then struggled to climb, and only made it to 50 feet above ground level 6,700 feet (2,050 meters) past the end of the runway (!!!!!!!!!!!!)

The aircraft stopped its climb at 4,000 feet, burned off fuel, and then returned to Belgrade, where it landed around 55 minutes after departure. The aircraft actually first made a low pass over the airport so that the landing gear could be checked, prior to then making a second approach, where a successful landing was performed.

Fortunately there were no injuries among passengers. Passengers were deplaned once the plane was on the ground, and were reportedly just told that there was a minor issue with the aircraft.

Flight path for Air Serbia flight JU324

Below you can see a video taken by a passenger from inside the cabin.

This is an unbelievable event on so many levels

The damage to this aircraft is nothing short of distressing, and passengers and crew should be counting their lucky stars that this didn’t have a very different ending:

  • It’s not just that there’s a tear in the fuselage, but you can see how this is right at the root of the wing
  • The aircraft only became airborne 1,650 feet after the end of the runway, so imagine all the additional obstacles it could have hit
  • Clearly the aircraft also initially struggled to climb, since it took nearly an extra mile for the aircraft to go from airborne to 50 feet above ground level
The badly damaged Embraer E195

Of course the logical question is why the pilots decided to take off at intersection D5, giving them less runway than the aircraft needed. Did they mess up their takeoff calculations? Were they just confused about which intersection they were taking off from? Midfield takeoffs aren’t at all uncommon, but of course they need to be from an intersection that leaves enough room to safely get airborne.

Here’s what we do know, based on air traffic control communications:

  • The aircraft was cleared to taxi to runway 30L at D6, but instead taxied to runway 30L at D5
  • The air traffic controller pointed out that the pilots entered the runway at the wrong intersection, and specifically warned them that they’d only have 1,273 meters, and said “I assume that is not enough”
  • The air traffic controller told the pilots to calculate what they’d need to have sufficient space, and even gave them permission to backtrack on the runway to the D6 intersection
  • After a moment, the pilots claimed they had enough space to depart from the D5 intersection, and then proceeded with their departure

This incident really defies logic. It’s bad enough when pilots make a mistake and no one catches on to it, but in this case the air traffic controller warned them about exactly what they did, but the pilots proceeded anyway.

Air Serbia ceases cooperation with Marathon Airlines

Following this incident, Air Serbia has announced that it has cut ties with Marathon Airlines effective immediately. Here’s how Air Serbia CEO Jiri Marek describes that decision, per EX-YU Aviation:

“This was a very serious incident, we are aware of the potential consequences that could have occurred. That’s why we very quickly made the decision to terminate cooperation with Marathon Airlines, regardless of the fact that it is a certified European airline. The decision was necessary because the safety of our passengers comes first. We will wait for the final results of the investigation, but this step was inevitable. We will contact all passengers from the flight, familiarise them with the procedure, what to do and how to fill out the compensation form. We will take appropriate measures as a matter of priority and in accordance with our regulations”.

Bottom line

An Air Serbia flight operated by Marathon Airlines had a bizarre accident, whereby the plane took off from an intersection that didn’t leave it with enough runway to actually safely take off. So the aircraft hit ground equipment, and only started to get airborne 1,650 feet past the end of the runway. The damage to the aircraft was immense, and this could have had a very different outcome.

We’ve now learned that air traffic control even warned the pilots how little runway they had remaining, but the pilots proceeded anyway. Unbelievable.

What do you make of this Belgrade Airport incident?

Conversations (23)
The comments on this page have not been provided, reviewed, approved or otherwise endorsed by any advertiser, and it is not an advertiser's responsibility to ensure posts and/or questions are answered.
Type your response here.

If you'd like to participate in the discussion, please adhere to our commenting guidelines. Anyone can comment, and your email address will not be published. Register to save your unique username and earn special OMAAT reputation perks!

  1. Kurt Guest

    OY - Danish registration - how come?

  2. VladG Diamond

    BEG was my home airport for many years. The most chilling fact of all is that there is a big billboard on the motorway right after the end of the runway. Seeing the takeoff trajectory and knowing how low the aircraft was flying, they must have missed it by mere metres. The ILS equipment is relatively lightweight, but had they hit the billboard, this story would have a VERY different ending.

  3. red_robbo Gold

    "Fortunately there were no injuries among passengers",
    followed by
    "....but a lot of seat cushions required deep cleaning."

  4. Samo Guest

    Can't wait for Mentour video on this one! :)

  5. dander Guest

    Not a fan of mid runway take offs. The runway behind you is not doing anything for you

  6. neogucky Gold

    I'm curious how this played out for the passengers. Judging by the damage of the fuselage they should have noticed the "crash" when taking off. Telling them then about a "small technical problem" should raise some eyebrows. Then they deplane and someone says "be careful not to step into the kerosine leaking out of the big hole next to the wing".

    1. Satellite Guest

      There are videos from the cabin, e.g https://www.reddit.com/r/aviation/s/2hYRlLdkyR

  7. ConcordeBoy Diamond

    Seems to be leaking fluid in the video, I'm guessing that's fuel, as there's also foam (proactively?) placed underneath it. That makes their flight time and go-around all the more scary. Wow!

    I definitely want to hear the explanation about this!

  8. notafit Guest

    If aircraft displays had this (https://flightsafety.org/asw-article/topi-an-easy-fix-to-a-nagging-problem/) on the PFDs/HUDs, none of these incidents would even happen.

    1. Eskimo Guest

      Or if you really trace it back to human error, then removing human from the system is the real solution.

    2. Samo Guest

      I doubt that. In this case, pilots were informed they don't have enough runway and decided to take off anyway. Having an instrument tell them something they already know would not help.

  9. Evan Guest

    He/She should be practicing his flying when nobody else is on the plane.

  10. steve64 Guest

    Simon (AvHerald) has corrected some distances.
    In measuring how far the plane was from the end of the runway ay different 'event points', he was measuring from the displaced threshold of runway 12R ( the same strip of concrete as 30L [this flight's departure runway] only in the opposite direction. That displaced threshold is only for planes landing on 12L (they have to land farther down 12L than the start of the pavement). For...

    Simon (AvHerald) has corrected some distances.
    In measuring how far the plane was from the end of the runway ay different 'event points', he was measuring from the displaced threshold of runway 12R ( the same strip of concrete as 30L [this flight's departure runway] only in the opposite direction. That displaced threshold is only for planes landing on 12L (they have to land farther down 12L than the start of the pavement). For this flight taking off on 30L, the pavement beyond the displaced threshold is available for the takeoff roll. Simon has corrected his 'beyond the runway' measurements to be from the actual end of the runway, not from the 12L displaced 'end'. So while this incident was still close to tragedy, the plane wasn't as far beyond the runway as was originally reported when it started hitting things and becoming airborne.

    My American brain has a hard time visualizing a distance in meters so I don't know if Lucky's article is using the original or updated 'beyond the runway' measurements. I suspect the former.

    1. Eskimo Guest

      Your American brains have hard time converting units.

      I suspect that is why the computer thinks the runway is long enough for takeoff.

  11. Razor18 Guest

    Sorry, misread the time stamps. It really looks like altitude started to increase only way past the rwy end... I dunno how accurate is ADS-B altitude datas, but still, how they avoided the road and the treeline, shown on the Google Earth image taken on June 2022...

    1. Albert Guest

      But you are right that the airport fence is about 800m from the end of the runway.
      https://avherald.com/h?article=5151ede4 says 500m which seems more believable.

  12. Razor18 Guest

    Claiming the plane was airborne after 3600 past the runway is totally false. There is a line of trees and a highway intersection within 3600 feet. Also, look at the ADS-B record. Even if barely, but the plane became airborne before reaching the end of the runway.
    https://globe.adsbexchange.com/?icao=459c83&lat=44.826&lon=20.282&zoom=14.7&showTrace=2024-02-18&trackLabels

  13. William Guest

    Reminds me of Comair/Delta Connection 5191 in Lexington, which of course had a far more tragic outcome

  14. UncleRonnie Guest

    Bring on the flight recorder playback!!!

  15. Scarba Guest

    It is hard to believe that the aircraft travelled 3,600 feet beyond the end of the runway before becoming airborne.

  16. Marco Guest

    Looking at the FlightRadar24 playback it shows that they tried to land for a first time but had to do a go-around, they only landed successfully on the second attempt 10 minutes later.

    1. satellite779 Guest

      That was a low flyby to check landing gear. A part of ATC communication (that's missing many parts spoken by pilots) can be found on this reddit post: https://www.reddit.com/r/aviation/s/H7QbPpYJDj

      Also, video from a security camera: https://www.reddit.com/r/aviation/s/tXMiYnZ1Gw

  17. Peking Duck Guest

    "Fortunately there were on injuries among passengers." I think you mean no injuries?

Featured Comments Most helpful comments ( as chosen by the OMAAT community ).

The comments on this page have not been provided, reviewed, approved or otherwise endorsed by any advertiser, and it is not an advertiser's responsibility to ensure posts and/or questions are answered.

steve64 Guest

Simon (AvHerald) has corrected some distances. In measuring how far the plane was from the end of the runway ay different 'event points', he was measuring from the displaced threshold of runway 12R ( the same strip of concrete as 30L [this flight's departure runway] only in the opposite direction. That displaced threshold is only for planes landing on 12L (they have to land farther down 12L than the start of the pavement). For this flight taking off on 30L, the pavement beyond the displaced threshold is available for the takeoff roll. Simon has corrected his 'beyond the runway' measurements to be from the actual end of the runway, not from the 12L displaced 'end'. So while this incident was still close to tragedy, the plane wasn't as far beyond the runway as was originally reported when it started hitting things and becoming airborne. My American brain has a hard time visualizing a distance in meters so I don't know if Lucky's article is using the original or updated 'beyond the runway' measurements. I suspect the former.

2
red_robbo Gold

"Fortunately there were no injuries among passengers", followed by "....but a lot of seat cushions required deep cleaning."

1
Samo Guest

Can't wait for Mentour video on this one! :)

1
Meet Ben Schlappig, OMAAT Founder
5,163,247 Miles Traveled

32,614,600 Words Written

35,045 Posts Published

Keep Exploring OMAAT