Late on Tuesday night, a Boeing 737 crashed into the Arabian Sea. There’s no such thing as a straightforward aviation accident, and the circumstances surrounding this are particularly strange — the pilots reported navigation issues, and moments later the plane start descending rapidly, only to then climb rapidly, before finally plunging over six miles, and going “missing.”
In this post:
K2 Airways Boeing 737 to Karachi crashes after navigation issues
This accident happened late at night on Tuesday, July 7, 2026, and involves a flight by Pakistani cargo carrier K2 Airways. The 27-year-old Boeing 737-400 with the registration code AP-BOI was enroute from Sharjah (SJH) to Karachi (KHI), with five people onboard.
The plane took off from the United Arab Emirates at 8:02PM Pakistani standard time, and was supposed to operate a routine 730-mile to Pakistan. The first roughly 75 minutes of the flight were believed to be routine.
However, the problems started at around 9:18PM, while the plane was around 180 miles from Karachi. At that point, the pilots reported to air traffic control that they were having navigational system issues.
Just one minute later, the plane rapidly descended from around 35,000 feet to around 30,000 feet, only to then rapidly climb up to 36,000 feet. However, that lasted for a matter of seconds, and at that point, the plane started a very steep descent, whereby it went from that altitude to sea level in just two minutes. Radar contact was lost at 9:22PM local time.
Below you can see the Flightradar24 data for what happened, as well as a side profile of the plane’s final minutes. As you can see, the plane actually started a turn as it began descending and then climbing. It’s worth noting that turn was away from the closest airport, rather than toward it.
Search and rescue efforts are underway, and my thoughts are with those onboard and their families. Suffice it to say that striking a body of water with a negative descent rate of over 22,000 feet per minute doesn’t translate to great odds for survivability.
For what it’s worth, this plane was initially delivered in 1999, and flew for Aeroflot, before being transfered to Garuda Indonesia, before being converted to a freighter in 2011.
Mechanical issue, intentional act, or missile, to blame?
It’s a pretty tense time for aviation globally, especially given the region in which this happened. So while it’s too early to know anything for sure, I see a lot of people online speculating that this could’ve been an intentional act (based on the very steep descent profile), or wondering if the plane was shot down by a missile (given that this happened not far from the Gulf region, and the conflict there).
Obviously I have no clue what happened. To state the obvious, most accidents happen during takeoff and landing, and to see a plane just fall out of the sky while at cruising altitude is incredibly rare. As a matter of fact, if you look at major aircraft accidents over the past couple of decades, a vast majority that happened mid-flight were either sabotage or acts of terrorism. That’s of course not to say that happened here, but it’s just reality.
The plane hasn’t even found yet, but no matter what the cause of this ends up being, this is unusual:
- If this was an intentional act, you wouldn’t typically first see reports of navigation issues, followed by a turn, then a descent, then a climb, and then a descent into the sea
- If the plane was struck by a missile, you would expect it to just fall out of the sky, rather than there first being reports of navigation issues
- If the plane was indeed having major mechanical issues, you still wonder how the plane went from having navigation issues to being in the sea a matter of minutes later
So we’ll see how this all plays out. Unless or until there’s evidence to the contrary, my assumption would be that there was some catastrophic failure, and that the crew did everything they could to save this plane. I can’t imagine how rough their final minutes were.
Bottom line
A K2 Airways Boeing 737-400 flying from Sharjah to Karachi disappeared from radar over the Arabian Sea, around 180 miles from its destination. The pilots reported navigation issues with the plane — moments later the plane descended steeply, then climbed steeply, and then plunged 35,000 feet in just two minutes, before disappearing from radar. My thoughts are with those onboard and their families… this is just awful.
My read on this:
You may be taking "navigational issues" too literally, as in taking as a given that this was properly diagnosed in the very limited time that they had, and that the nav system was, in fact, the issue and not merely a symptom.
More likely, in my opinion, the plane is on autopilot cruising, something (who knows what) happens and the result is a control surface failure. This leads to the plane...
My read on this:
You may be taking "navigational issues" too literally, as in taking as a given that this was properly diagnosed in the very limited time that they had, and that the nav system was, in fact, the issue and not merely a symptom.
More likely, in my opinion, the plane is on autopilot cruising, something (who knows what) happens and the result is a control surface failure. This leads to the plane changing course in an unexpected/unwanted way, and the pilot's initial guess was the nav system itself was fouling up rather than immediately recognizing that the directional changes were the result of the nav systems attempting to fight against flight control surface(s) which failed. The rapid climb and rapid descent may have come about from the pilot began hand-fly the craft with defective control surface(s), perhaps compounding the problem by applying rudder/control inputs under forces exceeding the safe operating limits of the airframe.
Which US ships were in the area? Electronic jamming and then an SM-2 hit it?
No, this is the Russian way. Shoot first and not care.
Look up Iran Air Flight 655.
This sounds like some kind of autopilot/stabilizer trim problem, perhaps complicated by incorrect crew inputs, that led to a stall/spin. In the heat of the moment a crewmember might have simply misspoke or misunderstood what was going on.
Maybe UGH is not the best way to start a title on an article about a plane crash that cost five lives no matter how it happened. I love reading your articles, but the whole one word comment followed by a colon in the title is exhausting. This one is a bit inappropriate. Maybe tragic: or horrific: or awful: or something similar would have been a better choice. Just saying… or maybe just stop using the whole colon thing entirely.
TIL Boeing was still producing 400s in 1999.
I think the only possibility that explains all these things happening is the prospect not of a missile but of the extensive amount of electronic warfare weapons being used by naval and air assets in that region. GPS spoofing, radar interference, etc by any of the actors in the guld region right now sounds like the least unlikely explanation.
Boeing 737. Bingo!
I promise I won't call you an ahole.
This is another indication that the middle eastern countries does nothing but try to kill their own people in the pursuit of making Americans look bad. They would never have don't that to an Airbus.
Thank goodness we have Israel to police the middle east now and good job that Trump is in control of the situation.
It's time we ban unsavoury countries from purchasing our planes.
Are you Ok? Please remove tinfoil from your ears.
They just let any idiot post on the internet.
What brilliant insight! Perhaps matters will be clearer still once you take your head out of Bibi's rear end?
A debris field has been identified and Pakistani Navy is bringing up parts of the fuselage. Pictures on official Pakistani Gov. websites. RIP. Hoping they find the recorders.
A slight climb before free fall reminds me of TWA800 and USS Vincennes.
Local media reporting that the aircraft was being ferried home after undergoing repairs.
What is "Ugh" in the title supposed to mean? Seems a little blaze vs. the "gut wrenching" title for the UPS accident "awful" for the RJ bus accident and "devastating" for the DCA accident a few years back
Yeah I agree, definitely out of place.
I actually viewed it as a way to signal "I'm telling you about this but don't think I don't feel badly about it."
What are "navigational issues"?
GPS spoofing and jamming is common in the area.
What happens to older aircraft in that part of the world when GPS is turned off?
The last previous flight shown on FlightAware was June 24, from Sharjah to Islamabad. So, when did it return to Sharjah, and why is it taking off two hours after sunset?
RIP to the crew.
Condolences to the families. The struggle to control the aircraft in the final moments are chilling.
Boeing solved that rudder hardover problem, right?
Constant GPS jamming and spoofing in this area. Would explain a “navigation issue” but doesn’t explain the end result.
If in conjunction with the auto-pilot?
Maybe shot down by the bad guys idk! Prayers goes to all on board tho! Sick world
“Maybe shot down by the bad guys idk!”
Sometimes saying nothing is better than saying anything. This is a case of that.
Perhaps you meant to write “First!!!!!!!11!!!!”
The UGH had n I thing to do with this story or any other. It was not intentional by all means. It was a comment on the 100 degree weather we r having.
Ugh was ment for another conversation. This is my first group chat. My apologies
The bad guys are not the ones you probably imply. Same bad guys as USS Vincennes.
Spoken like a true lobotomy patient.