Світ · Flight emergencyFlydubai Flight Lands Safely in Saudi Arabia; Crash-Attempt Allegations Remain UnprovenНаписано 30 вересня 2026 р. о 14:14 UTCДивитисяСтенограма0:09Fly Dubai Flight FC-1073 landed safely after an emergency diversion to0:15Saudi Arabia.0:16All passengers are safe and accounted for, but that does not establish everyone's0:19medical condition.0:20What forced the diversion, and do the later allegations establish a deliberate0:24attempt to crash the plane?0:29The passenger's flight ended in Tabuk, not at its scheduled destination near Tel0:33Aviv.0:34FC-1073 was flying from Dubai International Airport to Ben-Gurion International0:39Airport when it diverted on September 30th, 2026.0:42The landing is confirmed.0:43The precise location of the emergency is not.0:45Descriptions place different stages over Jordan, in Jordanian airspace, over Saudi0:49Arabia, or near the Jordan-Saudi Arabia border.0:52Without positions tied to timestamps, those descriptions cannot establish where the0:56cockpit event occurred.0:57They may describe different stages rather than contradictory locations for the same1:01moment.1:02The reported departure time is 0305 UTC, but that time has not been independently1:07verified.1:08No verified UTC landing time is established.1:11The aircraft's identification is also provisional, a Boeing 737 MAX 8, with another1:15identification specifying only a 737 MAX.1:19the exact model and registration remain unconfirmed by the airline or aviation1:23authorities.1:23A photograph caption identifying a 737-800 does not establish that this flight used1:29that model.1:30The aircraft transmitted 7700, then 7500, then 7700 again.1:36The middle code communicates unlawful interference.1:39It does not independently prove that a hijacking happened.1:42The sequence does not establish who selected the codes or why.1:45Exact times for the changes are unverified.1:47Receipt of the first signal is placed at about 9.08 that morning, but without an1:51established time zone.1:52That time cannot responsibly be converted to UTC or used to calculate how long the1:57emergency lasted.1:58Israel scrambled jets after the emergency raised hijacking concerns.2:02The aircraft deployed any interception or escort, and the military's underlying2:06assessment remain unestablished.2:08The early assessment was that the diversion was not believed to be a hijacking.2:12A physical fight between the pilots became the initial explanation, but that cause2:17is not independently established.2:18A complete airline statement confirming the cockpit fight explanation has not been2:22established either.2:24The directly reproduced description was simply an incident.2:27Later allegations went much further, that the co-pilot repeatedly stabbed the2:31captain, tried to seize control, and was subdued by crew and passengers.2:35Those actions remain alleged, not confirmed investigative findings.2:39Suspicion of terrorism and a possible attempt to crash the aircraft also emerged.2:44Neither suspicion establishes intent, a motive, or a final terrorism determination.2:49No direct statement from a named investigating authority establishes whether the2:52early no-hijacking assessment was formally revised.2:55The timing of publication does not establish the timing of an official reversal.2:59The terrorism framed account carries publication metadata of 082106 UTC.3:04Other accounts display later updates, 1210 without a separate time zone label, and3:081207 Israel time.3:10Those are publication markers, not verified times when authorities issued or changed3:13an assessment.3:15The early no-hijacking assessment lacks a sufficiently precise clock time to3:18reconstruct that official sequence.3:20A passenger feared the pilot intended to kill everyone aboard, but the account3:24expressly qualifies that interpretation with an acknowledgment of limited3:28understanding.3:29The fear is real testimony about the passenger's interpretation.3:33It is not proof of what the pilot intended or what happened in the cockpit.3:36The passenger figures differ by six, 174 versus 180.3:41Neither figure has been reconciled with an authoritative manifest or a confirmed3:45airline total.3:46Both are described as passenger counts, so the difference cannot be explained by3:50assuming one includes crew.3:51The total crew count is also unknown.3:54References to the two pilots do not establish how many cabin crew were aboard or the3:57total number of occupants.3:59No verified altitude trace supports the claimed 17,400 foot descent.4:03Other descriptions use an apparent 14,300-foot plunge in 37 seconds or a4:0817,500-foot drop.4:10None is substantiated by a verified time-stamped altitude trace.4:13Those figures cannot be averaged.4:15Chosen for dramatic effect, or treated as evidence of a deliberate crash attempt.4:19Even a verified descent would need its own context before it could establish what4:23was happening in the cockpit.4:25All passengers are safe and accounted for, but that wording does not establish a4:29zero injury count.4:30It does not confirm the captain's or co-pilot's condition or whether a stabbing4:34occurred.4:34A separate description of no casualties does not settle those medical questions.4:38No arrest, suspect identity, or charge is established, nor is a confirmed absence of4:43arrests.4:44The passenger safety update was carried at 0810 UTC, but that is not a verified4:50release time for the airline's own statement.4:52A complete public airline statement resolving the allegations remains unestablished,4:56as do direct Saudi Aviation Authority, Israeli military, and foreign ministry5:01statements resolving the cause and consequences.5:03The answer to the central question remains limited.5:06The flight made a safe emergency diversion, but the cause is unresolved.5:10The stabbing, seizure of control, and deliberate crash allegations have not been5:14established as investigative findings.5:16The passenger's journey also remains unfinished in the established account.5:20No replacement flight, onward departure time, or accommodation arrangement is5:24confirmed.5:24There is no established confirmation that they subsequently reached Tel Aviv.5:28Their confirmed arrival is in Tabuk, Saudi Arabia.Читати статтюХронологія історіїHeyDexКоротке відео ↗Хто що повідомивПункти, про які повідомило більше ніж одне видання✓One pilot stabbed the other aboard the flightНезалежно підтверджено · 13 видань✓Emergency landing of Dubai-to-Tel Aviv flight in Saudi ArabiaНезалежно підтверджено · 13 видань✓Aircraft sent emergency distress signals including possible hijacking codeНезалежно підтверджено · 13 видань✓Aircraft rapid descent altitude lossНезалежно підтверджено · 12 видань✓Plane landed safely in Saudi ArabiaНезалежно підтверджено · 11 видань✓Passengers and crew subdued the attackerНезалежно підтверджено · 11 видань✓Attacker tried to crash the plane or sabotage controlsНезалежно підтверджено · 7 виданьКожен рядок — твердження в тому вигляді, в якому ми записали його з матеріалу цього видання. Порівняно станом на 6 жовтня 2026 р. о 19:00 UTC.
