EXCLUSIVE SAS- India Flags Rule Breach as Mission Aborted Mid Air

 Neelam Mathews

June 15, 2026

India Flags Rule Breach as Mission Aborted Mid Air

Neelam Mathews

 

AerospaceDiary gives a detailed write up on what happens when a nation’s guidelines are taken for granted.

The SAS SK969 Airbus A330‑300 (LN‑RKM), operating the carrier’s flagship return to India in 17 years, departed Copenhagen four hours late on June 2 for Mumbai, was forced to turn back while over Azerbaijan. The instruction was relayed by Iran Air Traffic Control (ATC), the next Flight Information Region (FIR), after India cautioned SAS lacked the Directorate General of Civil Aviation (DGCA) landing clearance.

India cannot directly radio an aircraft outside its airspace, so the message moves through the FIR chain.

Four messages sent to senior SAS leadership remain unanswered. Despite the severe embarrassment, operational lapse and dereliction this incident represents, SAS has issued no statement on whether the matter is being investigated internally. Passengers suffered losses on hotel and travel bookings in Mumbai, while SAS absorbed an estimated half‑million‑dollar hit and reputational damage, and possible insurance liability.

SAS Oversight

Interestingly, a contradictory statement by SAS said: “SAS completed all necessary operational and regulatory preparations for the launch……... Based on ongoing discussions with the relevant authorities, SAS had every expectation that the remaining formal approval would be finalized while the flight was en route. As the approval was not finalized as anticipated, the flight could not continue as planned.” So why did it? An aviation official told Aerospace Diary on anonymity SAS was hoping it could ‘slip in.’ Else did they really expect DGCA to be awake at mid night to give permission for the flight to land in India?’

“The responsibility for documents that need to be cleared lies primarily with the airline’s (SAS) own dispatch and engineering teams, which must verify aircraft documents, permits, crew legality and the flight plan before departure,” confirmed Nivedita Bhasin, Retd Flight Safety Executive Director and 787 Capt. with Air India.

 

 

Speculation- What are we missing?

A lack of transparency inevitably fuels rampant speculation, We could not confirm any. One report suggests ownership of the company was not clear in the documents or ignored.

SAS cannot meet DGCA’s 50% EU/EEA‑control rule because only 26% Danish and 10% French ownership qualify today. The remaining shares sit mainly with US fund Castlelake and other non‑EU investors, whose stakes don’t count. Until this transfers to Air France–KLM when they will acquire 60.5% of SAS, it cannot claim majority. SAS can realistically fly to India only after the Q4 ownership transfer is completed. Until then, DGCA cannot issue operating authorisation. This is the rule.

SAS’s documentation error likely reflects the organisational distraction during its transition to Air France‑KLM control, stretched regulatory teams and miscommunication between Copenhagen, headquarters and the India station. With integration workstreams underway and reporting lines shifting, approvals may have been assumed rather than verified, creating conditions in which the crucial DGCA clearance was missed.

If the reports regarding the absence of approval for a wet-leased aircraft are accurate, the issue goes beyond a mere administrative lapse and enters the realm of regulatory non-compliance, explained Chandwani. Research. Our research shows suggests this was unlikely.

Legal Aspects

Foreign carriers operating into India are governed by the Aircraft Act, 1934, the Aircraft Rules, 1937, and the Civil Aviation Requirements issued by the DGCA.

The turning back of SAS’ flight raises significant regulatory and liability concerns. “Available information suggests that the flight was dispatched before receipt of the final operating clearance from the DGCA,” Sonam Chandwani Managing Partner at KS Legal & Associates said.

“From a legal standpoint, an airline cannot presume that a pending approval will necessarily be granted and commence operations on that basis. Regulatory approvals are conditions precedent to operation, not procedural formalities. If the flight was dispatched in anticipation of receiving clearance while en route, it could be viewed as a breach of the statutory framework governing civil aviation,” added Chandwani.

The implications would have been far more serious had the aircraft suffered an accident or been forced to divert to another jurisdiction explained Chandwani. While an emergency landing in a third country would not itself attract any legal consequence, “investigations by insurers and aviation authorities would invariably examine whether the flight was being operated in accordance with all applicable permissions and approvals.”

Regulatory non-compliance does not automatically invalidate insurance coverage, particularly vis-à-vis passengers and third parties, but insurers could reserve rights, dispute indemnity or seek recovery depending upon the wording of the policy and the nature of the breach, she explains.

While international conventions, including the Montreal Convention, would continue to govern passenger claims, any finding that the airline knowingly operated without mandatory approvals could expose it to allegations of negligence and increase regulatory and civil liability exposure.”

The incident is therefore likely to trigger an internal compliance review within SAS. Airlines are expected to have robust pre-departure legal and regulatory checks to ensure that all permissions are in place before commercial operations commence. Any failure in such procedures would necessitate corrective measures, revision of internal protocols and possibly enhanced oversight by regulators, added Chandwani.

At present, the episode appears to be more a case of regulatory overreach by the operator rather than a safety event. Nevertheless, aviation law treats compliance with licensing and approval requirements as an integral component of safety itself.

Past Turnbacks

Airlines across the world have faced mid‑air turnbacks triggered by dispatch and documentation failures - from Lufthansa and Emirates returning over missing overflight permits, to Qantas and Cathay Pacific due to crew‑document lapses, Jetstar and Korean Air over dangerous‑goods paperwork errors, and British Airways and United for ETOPS (Extended Operation) non‑compliance. Qatar Airways and Turkish Airlines have been turned back over landing‑permit issues, while Lufthansa and Air Canada have faced airworthiness logbook errors. Even Air India, in February 2026, was forced to return after a documentation mismatch flagged during en‑route checks.

IndiGo’s inaugural Amsterdam service was forced to return from UAE airspace because the airline’s own documentation for the onward sector was incomplete. UAE ATC simply enforced procedure: without full clearances, a flight cannot be handed over to the next FIR. The lapse lay with IndiGo, not UAE authorities said Amit Singh Founder, Safety Matters Foundation.