"Influenced by Extremist Ideas" .. .. Al Arabiya Sources Reveal Special Details About Flydubai Co-Pilot

Listen to the article, the audio text is automatically generated by a machine system.

While details of the Fly Dubai incident are still unfolding, sources from Al Arabiya revealed that the co-pilot of flight 1073 heading to Tel Aviv spent most of his time outside the Sultanate of Oman, particularly in Syria, and was influenced by extremist ideas during his stay there.

The sources also mentioned that the co-pilot, named Hamam Al-Hamami, left Oman after being prevented by Omani authorities from practicing his flying profession before going to the UAE.

On board flight FZ1073 of Fly Dubai, the atmosphere of the flight from Dubai to Tel Aviv turned into an emergency situation after the co-pilot attacked the Indian captain of the plane with a knife.

During the flight, the aircraft sent the code 7700, used to indicate a general emergency, before later sending the code 7500, designated for reporting unlawful interference or the possibility of the aircraft being hijacked, and then returned to sending the code 7700.

Flight tracking data showed changes in altitude and course, while available information indicated that the aircraft, a "Boeing 737 Max 8," safely landed at Prince Sultan bin Abdulaziz International Airport in Tabuk after changing its course, with reports stating that all passengers are fine.

Following that, the Emirates News Agency reported that the Attorney General directed the formation of a team of public prosecution members to investigate the "Fly Dubai" incident en route from Dubai to Tel Aviv. This comes as Al Arabiya and Al Hadath correspondents reported that Saudi authorities continue their investigations into the Fly Dubai incident and that the Fly Dubai aircraft remains at Tabuk Airport, noting that the handling of passengers on the affected aircraft was in accordance with international protocols.

In this context, Saudi pilot Captain Essam Al-Saadawi stated that cockpit recordings are one of the most important keys to the investigation, as they reveal the events leading up to the declaration of an emergency.

He explained that the recordings could help determine the nature of the dialogue between the pilot and co-pilot, the sounds present in the cockpit, and whether there was another person, in addition to reconstructing the sequence of events that preceded the change in the flight path.

Communications between the crew and air traffic control also represent a crucial element in the investigation, as they can help identify who sent the distress call, the nature of the situation reported, and the information conveyed by the crew before landing.

He said: "If one of the pilots is injured and the other is able to communicate, the recordings will clarify what was said to air traffic control, how the emergency was declared, and what happened in those moments." Flight path data.

As for the flight data recorder, Al-Saadawi explained that it provides investigators with a wide range of technical data that helps reconstruct the aircraft's movement and the sequence of events. This data includes the aircraft's speed, altitude, direction, timing of course changes, and descent rate, along with information related to the aircraft's performance and control systems.

By matching this data with cockpit recordings and communications with air traffic control, as well as the technical inspection of the aircraft, investigators can build a timeline that begins before the course change and extends to the approach phase to Tabuk and landing.

Captain pilot Al-Saadawi emphasized that the images, videos, and circulating narratives cannot replace the technical investigation into an aviation incident with such circumstances.