Oman authority probing AI Express aircraft incident at Muscat on May 15

Oman Transport Safety Bureau OTSB is investigating the incident of an Air India Express aircraft hitting and damaging runway edge lights at the Muscat airport during take-off roll on the night of May 15, according to sources.The take-off of the aircraft, which was bound for Kannur in Kerala, was aborted.


PTI | New Delhi | Updated: 25-05-2026 18:26 IST | Created: 25-05-2026 18:26 IST
Oman authority probing AI Express aircraft incident at Muscat on May 15
This image is AI-generated and does not depict any real-life event or location. It is a fictional representation created for illustrative purposes only.

Oman Transport Safety Bureau (OTSB) is investigating the incident of an Air India Express aircraft hitting and damaging runway edge lights at the Muscat airport during take-off roll on the night of May 15, according to sources.

The take-off of the aircraft, which was bound for Kannur in Kerala, was aborted. The plane VT-AXR, a Boeing 737-800 NG, which was involved in the incident, is grounded at Muscat.

The sources said an accredited representative from the Aircraft Accident Investigation Bureau (AAIB) is part of the probe being done by the OTSB. The two pilots who were in the cockpit at the time of the incident have been derostered pending investigation, they added.

The sources said the runway edge lights were damaged during the take-off roll, as the aircraft was reportedly not aligned with the centre of the runway.

In a statement on Monday, an Air India Express spokesperson said it was actively engaging with the OTSB in investigating the incident involving its aircraft at the Muscat airport on May 15.

''Further updates may be issued when appropriate by the relevant authorities. We provided an alternative aircraft and accommodation where required to all impacted guests to facilitate their journeys to Kannur,'' the spokesperson said.

Queries sent to OTSB remained unanswered.

Details about the number of passengers who were onboard at the time of the incident could not be ascertained.

(This story has not been edited by Devdiscourse staff and is auto-generated from a syndicated feed.)

Give Feedback