Latest news with #VT-IMD
Time of India
13 hours ago
- Climate
- 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
15 hours ago
- Climate
- 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
a day ago
- Climate
- 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'.
&w=3840&q=100)
Business Standard
a day ago
- Climate
- Business Standard
Severe weather, delayed re-routing likely caused May IndiGo incident: DGCA
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 DGCA. On 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 Monday. The 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 reply. On 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 statement. While 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 said. On May 21, the flight crew had sought permission to enter Pakistan airspace to avoid turbulence but the request was rejected. (Only the headline and picture of this report may have been reworked by the Business Standard staff; the rest of the content is auto-generated from a syndicated feed.)
Time of India
a day ago
- Climate
- Time of India
Severe weather, non-timely action in re-routing plane probable causes for IndiGo incident in May: DGCA
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 DGCA. On 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 Monday. Productivity Tool Zero to Hero in Microsoft Excel: Complete Excel guide By Metla Sudha Sekhar View Program Finance Introduction to Technical Analysis & Candlestick Theory By Dinesh Nagpal View Program Finance Financial Literacy i e Lets Crack the Billionaire Code By CA Rahul Gupta View Program Digital Marketing Digital Marketing Masterclass by Neil Patel By Neil Patel View Program Finance Technical Analysis Demystified- A Complete Guide to Trading By Kunal Patel View Program Productivity Tool Excel Essentials to Expert: Your Complete Guide By Study at home View Program Artificial Intelligence AI For Business Professionals Batch 2 By Ansh Mehra View Program The incident was investigated by the Directorate General of Civil Aviation (DGCA). by Taboola by Taboola Sponsored Links Sponsored Links Promoted Links Promoted Links You May Like AI is changing the way you learn a language Talkpal AI Learn More Undo "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 reply. On 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. Live Events "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 statement. While 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 said. On May 21, the flight crew had sought permission to enter Pakistan airspace to avoid turbulence but the request was rejected.
