'Debris On Runway': DGCA On Air India's Missed Landing Attempt After Diversion To Chennai
The DGCA said the Air India flight AI2455 from Thiruvananthapuram to Delhi was diverted to Chennai on Sunday after the crew suspected a weather radar malfunction.
The Directorate General of Civil Aviation (DGCA) has said that Air India flight AI2455, operating from Thiruvananthapuram to Delhi on Sunday evening, was diverted to Chennai after the crew suspected a malfunction in the aircraft's weather radar during turbulent conditions.
It added that the flight attempted to land but had to make multiple go-arounds after a departing flight reported debris on the left side of the runway.
According to the DGCA, the Airbus A320 (registration VT-TNL) was scheduled to depart at 7.15 pm, IST, but left Thiruvananthapuram at 8.04 pm IST, delayed by 49 minutes due to a late arrival from Delhi caused by a previous diversion and operational reasons.
While en route, the crew experienced moderate turbulence and observed that the weather data displayed on the radar was not accurate, prompting the precautionary diversion, it mentioned.
'On 10.08.2025, Air India A320 aircraft VT-TNL was scheduled to operate flight AI2455 (Thiruvananthapuram-Delhi) with a scheduled time of departure of 19:15 IST. Due to the late arrival of aircraft from Delhi (Weather Diversion+ consequential+ commercial) aircraft departed Thiruvananthapuram at 20:04 IST, i.e. with a total delay of 49 minutes," the DGCA statement mentioned.
'To avoid overweight landing and burn extra fuel, the aircraft with the ATC clearance orbited 25NM northeast of Chennai for 43 minutes (from 21:25IST to 22:08IST)," the letter mentioned.
'After the aircraft was cleared for approach Runway 25 at Chennai, at 2219IST aircraft was instructed to carry out a missed approach by ATC as departing Gulf Air flight GFA053 (Chennai-Bahrain) reported debris on the left side of the runway."
'Apron control carried out an inspection of the runway, and nothing was observed. The aircraft was given landing clearance, and it landed safely at 22:39 IST. During the engineering inspection, no deficiency was observed. However, as a precautionary measure, the WX radar transreceiver was replaced with a serviceable one," it stated.
AIR INDIA SPOKESPERSON STATEMENT
Following the DGCA statement, a spokesperson for Air India said, 'Air India clarifies that flight AI2455 of 10 August operating from Thiruvananthapuram to Delhi was diverted to Chennai as a precautionary measure after the pilot detected a suspected technical issue and in view of the weather conditions en route to Delhi."
'It was decided to divert to Chennai instead of Bengaluru as the weather in Chennai was clear," they said.
'As the aircraft was overweight for an immediate landing, the pilot had to hold over Chennai to reduce weight, and no emergency was declared," the statement mentioned.
'During the first landing approach, the ATC asked the pilots to initiate a go-around as another aircraft that had taken off from the same runway had reported a suspected foreign object debris (FOD) on the runway," Air India said.
'After following a standard go-around, the flight made a normal and safe landing. We would like to reiterate that the decision to divert to Chennai was taken in the best interest of the safety of our passengers and crew," it added.
AIR INDIA's PRECAUTIONARY LANDING
Air India plane flying from Thiruvananthapuram to Delhi was diverted to Chennai Sunday evening due to a technical issue, the airline said.
The flight AI2455, operated with an Airbus A320 aircraft, was airborne for more than two hours, according to information available on the flight tracking website Flightradar24.com.
'The flight crew of AI2455 operating from Thiruvananthapuram to Delhi on 10 August made a precautionary diversion to Chennai due to a suspected technical issue and given the weather conditions en route," the airline said in a statement.
Air India said the flight landed safely in Chennai, where the aircraft will undergo the necessary checks.
Alternative arrangements are being made to fly the passengers to their destinations at the earliest, Air India said, and regretted the inconvenience caused.
Later, senior Congress leader and Chairman of Parliament's Public Accounts Committee KC Venugopal claimed that the Air India flight carrying him and several other MPs from Thiruvananthapuram to Delhi 'came frighteningly close to tragedy".
Urging an investigation by the DGCA and the Ministry of Civil Aviation, Venugopal, in an X post, wrote, 'Air India flight AI 2455 from Trivandrum to Delhi — carrying myself, several MPs and hundreds of passengers — came frighteningly close to tragedy today."
'What began as a delayed departure turned into a harrowing journey. Shortly after take-off, we were hit by unprecedented turbulence. About an hour later, the Captain announced a flight signal fault and diverted to Chennai," he wrote.
'For nearly two hours, we circled the airport awaiting clearance to land, until a heart-stopping moment during our first attempt — another aircraft was reportedly on the same runway. In that split second, the Captain's quick decision to pull up saved every life on board. The flight landed safely on the second attempt," he said.
ALSO READ | Congress vs Air India vs BJP In Big Row After Flight Diversion To Chennai
About the Author
Vani Mehrotra
Vani Mehrotra is the Deputy News Editor at News18.com. She has nearly 10 years of experience in both national and international news and has previously worked on multiple desks.
Get breaking news, in-depth analysis, and expert perspectives on everything from politics to crime and society. Stay informed with the latest India news only on News18. Download the News18 App to stay updated!
view comments
Location :
New Delhi, India, India
First Published:
August 11, 2025, 13:03 IST
News india 'Debris On Runway': DGCA On Air India's Missed Landing Attempt After Diversion To Chennai
Disclaimer: Comments reflect users' views, not News18's. Please keep discussions respectful and constructive. Abusive, defamatory, or illegal comments will be removed. News18 may disable any comment at its discretion. By posting, you agree to our Terms of Use and Privacy Policy.
Try Our AI Features
Explore what Daily8 AI can do for you:
Comments
No comments yet...
Related Articles
Time of India
3 days ago
- Time of India
Severe weather, non-timely action in re-routing plane probable causes for IndiGo incident in May: DGCA
Advt Severe weather and non-timely action in re-routing the aircraft clear of weather were the probable causes that led to IndiGo's Delhi-Srinagar flight incident where the aircraft's nose radome was damaged on May 21, according to the probe findings by aviation regulator May 21, IndiGo's A321 neo aircraft VT-IMD while operating flight 6E-2142 from Delhi to Srinagar encountered severe weather, including hail, during cruise. After landing in Srinagar, the aircraft radome was found damaged, Minister of State for Civil Aviation Murlidhar Mohol told the Rajya Sabha on incident was investigated by the Directorate General of Civil Aviation (DGCA)."The investigation has revealed that severe weather existing en-route and non-timely action in re-routing the aircraft clear of weather was the probable cause of the occurrence," the minister said in a written May 23, two days after the incident, DGCA had said IndiGo flight crew initially attempted to return but as they were close to the thunderstorm cloud, they decided to penetrate the weather."Subsequently, they encountered hailstorm and severe turbulence. Crew chose to continue at the same heading to exit the weather by the shortest route towards Srinagar," it had said in a in a thunderstorm cloud, the regulator had said warnings of Angle of Attack fault, Alternate Law protection lost, backup Speed scale unreliable were triggered."Due to updraft and downdraft encountered by the aircraft the Autopilot tripped and aircraft speed had wide variations. As a result, Maximum Operating Speed/Maximum operating Mach (VMO/MMO) warnings and repeated stall warnings were triggered," it had May 21, the flight crew had sought permission to enter Pakistan airspace to avoid turbulence but the request was rejected.
Hindustan Times
3 days ago
- Hindustan Times
‘Severe weather, delayed re-routing to blame for IndiGo flight damage'
: Severe weather and non-timely action in re-routing the aircraft were the probable causes that led to the IndiGo's Delhi-Srinagar flight incident where the aircraft suffered damages to its radome on May 21, the Directorate General of Civil Aviation (DGCA) found in its investigation. 'Severe weather, delayed re-routing to blame for IndiGo flight damage' The IndiGo A321 neo aircraft VT-IMD while operating flight 6E 2142 from Delhi to Srinagar encountered severe weather, including hail, during cruise. Due to this, the aircraft radome was found damaged after landing. The incident was investigated by aviation regulator DGCA. 'The investigation has revealed that severe weather existing en-route and non-timely action in re-routing the aircraft clear of weather was the probable cause of the occurrence,' Union minister of state for civil aviation Murlidhar Mohol told the Rajya Sabha in a written reply on Monday. He was responding to a question from AAP lawmaker Sanjay Singh. The incident occurred when the aircraft, while cruising at FL360, entered hailstorm and severe turbulence near Pathankot. No passenger was injured in the incident. According to the crew statement, they requested the Northern control (IAF) for deviation towards left (International Border) due to weather on the route, however it was not approved. Later, the crew contacted Lahore to enter into their airspace to avoid the weather but the same was refused too. 'Crew initially attempted to return but as they were close to the thunderstorm cloud, they decided to penetrate the weather. Subsequently, they encountered hailstorm and severe turbulence. The crew chose to continue at the same heading to exit the weather by the shortest route towards Srinagar,' the DGCA said in a statement on May 23, two days after the incident. 'While in thunderstorm cloud, warnings of Angle of Attack fault, Alternate Law protection lost, backup Speed scale unreliable were triggered. Due to updraft and downdraft encountered by the aircraft the Autopilot tripped and aircraft speed had wide variations,' it added. As a result, Maximum Operating Speed/Maximum operating Mach (VMO/MMO) warnings and repeated stall warnings were triggered, it said. 'During this period the aircraft rate of descent reached 8500 fpm. Crew flew the aircraft manually till they exited the hailstorm. After carrying out all check list actions (ECAM actions), the crew declared PAN PAN to Srinagar ATC and requested for RADAR vectors and made a safe landing with Auto Thrust operating normally,' it added.
Indian Express
3 days ago
- Indian Express
IndiGo plane's nose damage incident: DGCA probe reveals severe weather, non-timely action in rerouting as probable causes
Aviation safety regulator Directorate General of Civil Aviation's investigation into the May 21 incident in which an IndiGo Airbus A321 aircraft suffered a damaged nose after flying through a severe hailstorm has identified severe weather and 'non-timely action' in rerouting the aircraft to keep it clear of inclement weather as the probable causes, Minister of State for Civil Aviation Murlidhar Mohol informed the Rajya Sabha on Monday. 'IndiGo A321 neo aircraft VT-IMD while operating flight 6E-2142 from Delhi to Srinagar encountered severe weather, including hail during cruise. After landing at Srinagar, the aircraft radome was found damaged. The incident has been investigated by Directorate General of Civil Aviation (DGCA). The investigation has revealed that severe weather existing en-route and non-timely action in re-routing the aircraft clear of weather was the probable cause of the occurrence,' Mohol stated in a written response to a question in the Upper House. No further information was provided by Mohol on the DGCA investigation into the incident. Two days after the incident, the DGCA had said that the pilots flying operating that flight had requested the Indian Air Force Northern Area Control for deviation towards the India-Pakistan international border to avoid inclement weather, and later contacted the Lahore air traffic control (ATC) to briefly enter Pakistani airspace—a no-go zone for Indian aircraft—to circumvent the storm. Both these requests were denied, and the flight crew decided to go through the inclement weather and continue the journey to Srinagar, the DGCA had said then based on the pilots' statement. 'While cruising at FL360 (36,000 feet), aircraft entered hailstorm and severe turbulence near Pathankot. As per crew statement, they requested Northern control (IAF) for deviation towards left (International Border) due to weather on the route, however it was not approved. Later crew contacted Lahore to enter into their airspace to avoid the weather but the same was refused too. Crew initially attempted to return back but as they were close to the thunderstorm cloud, they decided to penetrate the weather. Subsequently, they encountered hailstorm and severe turbulence. Crew chose to continue at same heading to exit the weather by the shortest route towards Srinagar (sic),' the DGCA had said on May 23. At the time, sources in the Indian Air Force had said that the Northern Area Control's advice to the pilots was within the frame of the ban on Indian aircraft in Pakistani airspace, adding that the flight was assisted immediately in coordinating its route diversion. 'The aircraft was immediately assisted in coordinating their route diversion by contacting Delhi Area and passing requisite contact frequencies of Lahore control for overflight weather diversion request. Once Lahore refused overflight clearance, and the aircraft proceeded towards Srinagar, the flight was subsequently professionally assisted till a safe-landing at Srinagar airfield by giving control vectors and groundspeed readouts,' the IAF sources said. Air traffic services at the Srinagar airport are also under the control of the IAF. In the aftermath of the Pahalgam terror attack, as diplomatic relations between India and Pakistan deteriorated, Pakistan shut its airspace to Indian aircraft and airlines, banning them from overflying its airspace. In the case of the IndiGo Delhi-Srinagar flight, Lahore ATC did not allow the use of its airspace despite the urgent weather situation that the aircraft was grappling with in view of the airspace closure. The aircraft departed from Delhi at 5:13 pm on May 21, according to flight tracking data. Around 45 minutes into the flight, when the aircraft was passing over the Pathankot area, the seat belt signs were switched on by the flight crew, which was followed by severe turbulence for a few minutes and a hailstorm hitting the aircraft's fuselage. The aircraft landed at the Srinagar airport at around 6:30 pm. Given the damage to the nose of the aircraft, it was grounded in Srinagar for necessary maintenance and inspections. According to the pilots' statement to the aviation safety regulator, the aircraft sounded various technical warnings while navigating the thunderstorm. These included warnings of 'angle of attack fault, alternate law protection lost, and backup speed scale unreliable'.
