GoAir Balked Landing (Passenger Video)
Passenger videos often appear scarier than the circumstances warrant, amplified by a lack of aviation experience to know how dangerous the situation actually is. This one is the clear exception to the rule.
This video was taken on Monday on GoAir flight G8-811D, a scheduled commercial flight from Nagpur to Bangladore with 180 passengers on board. It was posted in response to a news post stating that the aircraft landed outside the runway due to bad weather.
The passenger who took the video was quick to defend the flight crew on Twitter:
Yes the flight missed the runway but it didn't land there … The pilot saved us by taking off and ultimately landing in Hyderabad. I was on that flight.
Yes the flight missed the runway but it didn't land there … The pilot saved us by taking off and ultimately landing in Hyderabad. I was on that flight. pic.twitter.com/u8ha2HVX1k
— Shafeeq Hamza (@shamza) November 14, 2019
The thing is, although I appreciate the praise of the pilot, flights don’t just “miss the runway”…pilots do.
Mud on the left gear and tracks to the left runway confirms that the Airbus A320 touched down on the grass. According to the passenger, the pilot, presumably the captain, announced that he wasn’t comfortable landing because of the fog. Which is fair enough other than the fact that he did, in fact, land, if we count a touch-and-go (which I seem to recall I was always charged for as if it were a full landing). The wheel tracks alongside the runway last about 200 metres (650 feet).
Some news articles have claim the crew were suspended for their actions but as far as I can see, the Directorate General of Civil Aviation (DGCA), the Indian aviation body, are still investigating. The aircraft and the flight crew have been grounded pending the outcome, which is normal procedure.
Indian press reported that the number one engine stalled twice during the go around.
Due to bad weather at Bengaluru, the aircraft initiated a go around. During the go around process engine number 1 stalled. The power on the affected engine was reduced to idle and go around was continued. During climb number 1 engine again stalled and power was again reduced to idle. The aircraft was then diverted to Hyderabad with power on number 1 engine in climb detent,” an official said.
However The Aviation Herald’s incident report initially claimed that there’s no DGCA statement to confirms this.
A number of (but not all) media in India claim an unnamed source associated with the DGCA reported the left hand engine (PW1127G) stalled during the go around. On social media one journalist even claims to quote a statement by DGCA (editorial note: showing a blank sheet of paper with text, but no letter head, signature or other indication of any official document, no such document is available on any of the DGCA outlets), callsign of the aircraft was GOW811, no D attached to the flight number…
However, nine minutes after I quoted the above for this post, their report was amended to include a DGCA statement confirming the engine stall.
On 11.11.2019 Go Air A320 aircraft VT-WGR operated flight G8-811D(Nagpur-Bangalore). It was cleared for approach for R/W 09 at Bangalore. Due to bad weather at Bangalore aircraft initiated Go around. During the Go Around process No.1 engine stalled. The power on the affected engine was reduced to idle and Go around was continued. During climb No.1 Engine again stalled and power was again reduced to idle. The aircraft diverted Hyderabad with power on No.1 engine in climb detent.
After landing at Hyderabad mud deposit have been observed on left main landing gear, indicating that aircraft has rolled on to soft ground/ unpaved surface.
As per the crew aircraft has deviated to left during go around at Bangalore. Aircraft has been grounded for detailed investigation at Hyderabad.
DFDR data along with other recorder data is being analysed for further investigation.
The low cost airline has been in the news today for other reasons: DGCA gives IndiGo, GoAir till 24 Nov to replace P&W engines on A320 neo planes
After multiple incidents with the Pratt & Whitney engines on their Airbus 320 fleet, the DGCA gave GoAir and IndiGo a deadline of the 19th of November to replace those engines with over 3,000 hours (specifically that the engines need modified main gearboxes and new LPT blades). As of today, GoAir had placed modified engines on nine of their thirteen affected aircraft, a result that the DGCA described as below expectation. The original deadline was extended to the 24rd of November, rather unfortunate based on this week’s incident and the confirmation that one of the engines stalled on going around.
The investigation is continuing.