{"id":76805,"date":"2024-12-08T13:28:23","date_gmt":"2024-12-08T07:58:23","guid":{"rendered":"https:\/\/aviationa2z.com\/?p=76805"},"modified":"2024-12-08T13:28:29","modified_gmt":"2024-12-08T07:58:29","slug":"air-india-attempts-take-off-from-taxiway-at-goa","status":"publish","type":"post","link":"https:\/\/aviationa2z.com\/index.php\/2024\/12\/08\/air-india-attempts-take-off-from-taxiway-at-goa\/","title":{"rendered":"Air India Pilots Tries to Take off from Taxiway at Goa Airport"},"content":{"rendered":"\n

GOA-<\/strong> Tata Group-owned Air India (AI)<\/a> pilots mistakenly attempted to take off from the taxiway at Goa Airport on Thursday, December 5, 2024.<\/p>\n\n\n\n

The incident occurred at the new Manohar International Airport (GOX) in Mopa, Goa.<\/p>\n\n\n\n

\"Tata
Photo: Robin HARDY<\/a><\/figcaption><\/figure>\n\n\n\n

Air India Taxiway Take off<\/h2>\n\n\n\n

According to reports, the alert Air Traffic Controller (ATC) notified Air India pilots that they were attempting to take off from the taxiway and not from the runway. Following this, the crew immediately rejected the takeoff.<\/p>\n\n\n\n

At the point ATC alerted, the Air India plane was over 100 knots <\/strong>and was expected to lift off. However, they were able to reject the takeoff timely and returned safely back at the terminal.<\/p>\n\n\n\n

\"\"
Photo: FlightRadar24<\/figcaption><\/figure>\n\n\n\n

The incident occurred on Air India flight AI2592 <\/strong>from Goa (GOX) to Hyderabad (HYD). It was operated by Airbus A320neo<\/a>, registered as VT-EXT, a 7.7-year-old plane.<\/p>\n\n\n\n

According to FlightRadar24 data, the Air India flight attempted to take off from Taxiway A, instead of Runway 10\/28 which is confirmed by the airport map.<\/p>\n\n\n\n

\"Air
Photo: AIP India<\/figcaption><\/figure>\n\n\n\n

As per the data, the Air India flight began to roll at 3:47 AM UTC, and within a minute it rejected the takeoff. The A320neo successfully stopped at A2 point as seen in the map.<\/p>\n\n\n\n

It used the runway to make a turn and returned to the terminal. The airline canceled its flight following the incident. Luckily no injuries were reported onboard the aircraft to any passengers or crew.<\/p>\n\n\n\n

The Indian watchdog, the Directorate General of Civil Aviation (DGCA) has begun its probe into the incident. It has marked this incident as a serious breach of safety. Furthermore, DGCA has ordered Air India to submit a detailed analysis report on this incident.<\/p>\n\n\n\n

\"Tata
Photo: avgeekwithlens\/ Harsh Tekriwal<\/figcaption><\/figure>\n\n\n\n

Assumptions: Why did It happen? <\/h2>\n\n\n\n

Such incidents are extremely rare and can occur once in thousands of flights if not millions.<\/p>\n\n\n\n

I think (just an assumption and should wait for official confirmation), that Air India pilots got confused with the new airport markings and could have thought the taxiway A as RWY 10\/28.<\/p>\n\n\n\n

While there are chances that the crew are not properly trained with Goa Airport configurations.<\/p>\n\n\n\n

Also, there is a possibility that the flight is likely operated by a new recruit or pilot who never flew from the GOX earlier.<\/p>\n\n\n\n

Well, all these are just assumptions and possibilities and we will wait for the official probe report by the airline and the final report by DGCA India.<\/p>\n\n\n\n

\"\"
Photo: avgeekwithlens\/ Harsh Tekriwal<\/figcaption><\/figure>\n\n\n\n

Similar Incident<\/h2>\n\n\n\n

Well, this is not the sole incident, a few similar incidents have occurred in the past.<\/p>\n\n\n\n

In February 2024, IndiGo Airlines (6E) <\/a>aircraft experienced a navigational anomaly during landing at Delhi International Airport (DEL). This triggered a brief operational disruption that temporarily closed runway 28\/10 for 15 minutes.<\/p>\n\n\n\n

The Airbus A320, operating flight 6E2221 from Amritsar, encountered navigation challenges upon approach, ultimately missing its intended taxiway and arriving at the runway’s dead end<\/a>.<\/p>\n\n\n\n

Similarly, Dallas-based Southwest Airlines (WN) flight WN4805, traveling from Portland, Maine to Baltimore, Maryland, took off from the closed runway <\/a>at 5:42 a.m., despite a clear Notice to Airmen (NOTAM) explicitly prohibiting runway usage until 5:45 a.m.<\/p>\n\n\n\n

Feature and Other Images by Harsh Tekriwal | AvgeekwithLens<\/a><\/p>\n\n\n\n

Stay tuned with us. Further, follow us on social media for the latest updates.<\/p>\n\n\n\n

Join us on\u00a0Telegram Group\u00a0<\/a>for the Latest Aviation Updates. Subsequently, follow us on\u00a0Google News<\/a><\/p>\n\n\n\n

\n
British Airways A380 Stuck After Taking Wrong Turn on Taxiway at Boston<\/a><\/blockquote>