ATC vs Pilot Showdown: Who is Right?

An audio of a Turkish Airlines Pilot coming in to land at Muscat International Airport, overriding the instructions of an Omani Air Traffic Controller (ATC), has been circulating on the internet and originally appeared on Professional Pilots Rumour Network (PPRuNE) shortly after the flight landed and was then shared on VASAviation on YouTube, as well as several aviation focused websites such as One Mile at a Time. And it seems everyone has an opinion. But in the aviation world, there are rules for EVERYTHING, so who was right?

The Incident: December 2025

On 26th December 2025, a Turkish Airlines flight en route to Muscat (MCT | OOMS) was instructed by ATC to descend to 2,200 feet. The pilot refused, stating there was a discrepancy with the safety data charts provided in the cockpit by the airline.

The dialogue intensified as both parties stood their ground:

• Pilot: “My chart says MSA is 3,600 feet. I am staying at 3,600”.
• ATC: “If I give you an altitude, you must follow”.
• Pilot: “I don’t follow anyone’s orders when it comes to the safety of my aircraft and my passengers”.

The controller explicitly stated, “I’m not playing with safety,” asserting that the assigned altitude (2,200 feet) was the correct local minimum for the vectoring area.

Technical Conflict: MVA vs. MSA

The dispute was due to two different altitude standards:

Minimum Safe Altitude (MSA): Found on pilot charts, this is the lowest altitude that provides at least 1,000 feet of clearance above all obstacles in a specific area. The pilot identified 3,600 feet as the restriction for the GESOS waypoint (a specific “spot” in the air, similar to a virtual signpost in the sky).

Minimum Vectoring Altitude (MVA): A lower safety threshold used only by controllers. Because ATC has high-resolution radar, they can safely guide (“vector”) planes at lower altitudes than the published MSA.

The Conflict: The controller prioritised separation (keeping planes away from each other), while the pilot prioritised segregation (keeping the plane away from the ground).

SOP Evaluation: PACE and Duty of Care

In any such case, both the pilot and the ATC have Standard Operating Procedures (SOP). The pilot utilised the PACE model (Probe, Alert, Challenge, Emergency) to manage the conflict. By stating his intention to remain at 3,600 feet, he moved into the Emergency/Ultimatum phase, which is required when a command leads to an unsafe condition.

On the other hand, Muscat ATC operated under ICAO Annex 11, which orders the prevention of collisions. While the controller asserted that 2,200 feet was the correct local minimum, they were required by (SOPs) to accommodate the pilot’s “unable” declaration by transitioning to a “Plan B” that was offered up by the pilot.

The Verdict: Safety Precedence

Under ICAO Annex 2 (Section 2.3.1) and Omani Royal Decree No. 76/2019,  the Pilot-in-Command (PIC) holds the final authority for the operation and safety of the aircraft. While ATC provides essential traffic management, the pilot is legally required to reject any instruction that compromises the aircraft’s safety.

Resolution and Recommendations

Ultimately, the pilot’s “Sceptical Forensic Mindset” was correct; when the pilot’s charts contradict ATC instructions, to prevent what the International Civil Aviation Organisation (ICAO) defines as Controlled Flight Into Terrain (CFIT), pilots must be cautious and prioritise the more conservative value.

The industry must take note and focus on Chart Synchronisation to ensure that all Aeronautical Information Publication (AIP) data matches third-party pilot charts. The incident underscores the importance of professional cooperation and “Safety First” leadership in high-pressure environments.

Both parties demonstrated a commitment to safety. Even if you believe the pilot should have followed the ATC instructions in the moment, no one can deny that the pilot gave a master class on how to maintain command and control in a stressful situation by keeping his head, his authority, and his cool.