Air India Delhi-San Francisco flight returns after 8-hour mid-air snag

Share:
Audio Loading voice…
Air India Delhi-San Francisco flight returns after 8-hour mid-air snag

Synopsis

Air India's Delhi-to-San Francisco flight turned back after more than eight hours in the air — reportedly diverting while over Chinese airspace — marking the second safety-related incident involving the airline in under a week. With around 230 passengers stranded and the fault still undisclosed, scrutiny of Air India's technical reliability is intensifying.

Key Takeaways

Air India Flight AI173 bound for San Francisco returned to Delhi on 27 May after a mid-air technical issue.
The Boeing 777-300ER was airborne for more than eight hours and reportedly began diverting while over Chinese airspace .
Approximately 230 passengers were on board; all landed safely.
Air India has not disclosed the exact nature of the technical fault; the aircraft will undergo a detailed inspection.
The incident follows an engine fire on Air India Flight AI2802 (Bengaluru–Delhi) on 21 May , the second Air India safety event in under a week.

An Air India flight operating from New Delhi to San Francisco was forced to turn back to Indira Gandhi International Airport on Wednesday, 27 May, after remaining airborne for more than eight hours due to a mid-air technical issue. The airline confirmed that Flight AI173, carrying approximately 230 passengers, returned in accordance with established safety procedures.

What Happened Mid-Air

According to flight-tracking data from Flightradar24, the Boeing 777-300ER aircraft had already been airborne for over three hours and was reportedly in Chinese airspace when the crew initiated a diversion back toward Delhi. The aircraft ultimately touched down safely after a total flight time exceeding eight hours. Air India has not disclosed the precise nature of the technical fault, stating only that the plane will undergo a detailed technical inspection in line with the airline's safety standards.

'The aircraft landed safely and will undergo technical inspection in line with Air India's safety standards,' the airline said in a statement.

Passenger Arrangements

Air India expressed regret over the disruption and confirmed that ground teams were actively assisting affected passengers. The airline said it was working to make alternative travel arrangements at the earliest opportunity.

'We regret the inconvenience caused to the passengers and are making alternative arrangements to fly them to their destination as soon as possible,' the airline stated. It added that passengers were being offered refreshments, hotel accommodation, or rescheduling based on individual preference.

A Second Incident Within a Week

The turnaround comes less than a week after a separate Air India safety event. On 21 May, Flight AI2802, operating from Bengaluru to Delhi, experienced an engine fire indication during its final approach into Delhi airport. Air India confirmed the incident on X, stating that the cockpit crew received a fire warning from one of the engines during descent, which was subsequently confirmed as genuine.

'The crew followed all standard operating procedures and landed the aircraft safely at Delhi airport. All passengers and crew are safe and have disembarked normally,' Air India said in its 21 May post on X.

Safety Scrutiny Ahead

Two technical incidents involving Air India aircraft within seven days are likely to draw attention from India's aviation regulator, the Directorate General of Civil Aviation (DGCA), though no regulatory action has been announced as of this report. The airline has maintained that both aircraft were handled in full compliance with safety protocols. The outcome of the technical inspection on Flight AI173's Boeing 777-300ER is expected to determine when the aircraft returns to service and whether further disclosures about the fault are made.

Point of View

The other a confirmed engine fire — raise legitimate questions about the airline's maintenance pipeline during its ongoing fleet expansion. Air India has been aggressive in adding wide-body aircraft as it rebuilds post-privatisation, but scale without proportionate maintenance capacity is a known risk in aviation. The DGCA's response, or lack of one, will be telling. Passengers deserve a full technical disclosure, not just reassurances that procedures were followed.
NationPress
14 Jul 2026

Frequently Asked Questions

Why did Air India Flight AI173 turn back to Delhi?
Air India Flight AI173 returned to Delhi on 27 May due to a mid-air technical issue, though the airline has not disclosed the exact nature of the fault. The Boeing 777-300ER was airborne for over eight hours before landing safely at Indira Gandhi International Airport.
How many passengers were on board Air India Flight AI173?
Approximately 230 passengers were on board the Delhi-to-San Francisco flight. All passengers landed safely, and Air India said ground teams were providing refreshments, hotel accommodation, or rescheduling as required.
When did Air India's Flight AI173 start diverting back to Delhi?
According to flight-tracking data, the aircraft reportedly began diverting back toward Delhi after flying for more than three hours, while it was in Chinese airspace.
What was the Air India engine fire incident on 21 May?
On 21 May, Air India Flight AI2802 operating from Bengaluru to Delhi received a fire warning from one of its engines during final approach into Delhi airport. The crew followed standard procedures, landed safely, and all passengers and crew disembarked normally, the airline confirmed.
Will Air India face regulatory action over these incidents?
No regulatory action by the Directorate General of Civil Aviation (DGCA) has been announced as of this report. Air India has stated that both incidents were handled in full compliance with safety protocols, and the aircraft involved in the 27 May incident will undergo a detailed technical inspection before returning to service.
Nation Press
The Trail

Connected Dots

Tracing the thread behind this story — newest first.

8 Dots
  1. Latest 1 month ago
  2. 3 months ago
  3. 3 months ago
  4. 8 months ago
  5. 8 months ago
  6. 11 months ago
  7. 1 year ago
  8. 1 year ago
Google Prefer NP
On Google