Loss of Directional Control on landing
Thread Starter
Loss of Directional Control on landing
I'm confused about this one.
Possible mechanical items are engines incl reversers, brakes, severe wind gusts, and of course coupled with pilot reactions.
My first look checked to see whether it hadwing mounted engines or tail mounted. I couldn't even make out an engine in the photo
OK the text suggests wing mounted
'Aircraft lost control twice after landing’ - The Times of India
Aircraft lost control twice after landing' (India)
MUMBAI: Preliminary investigations into Saturday's landing goof-up involving an Indigo flight from Chandigarh have revealed that the aircraft lost control twice before the pilot brought it under control.
The commander and the co-pilot of flight 6E 433 were de-rostered on Sunday pending a probe by the Directorate general of Civil Aviation (DGCA) into the incident.
The flight, with 140 passengers on board, deviated from the center-line of the runway and went left towards the shoulder, breaking five lights in the process. It then went further up to the unpaved area.
The pilot reportedly tried to steer the aircraft back to the runway and brought it back till the shoulder, but it veered off again towards the unpaved patch. It was only in the second attempt that the plane was brought back on the runway.
The Airbus A-320 landed at Mumbai airport at 6.35pm and went-off the 60-feet wide runway into the unpaved patch. It came back to the runway towards the taxiway without notifying the air traffic control. The incident was discovered eight minutes later when a Mumbai International Airport Pvt Ltd staffer spotted the five damaged runway lights.
On Sunday, a preliminary draft was made and the pilots were summoned for a statement, said director general of civil aviation Arun Mishra.
An Indigo spokesperson said that a gust of wind caused the incident. However, a DGCA official said that "the pilot seems to have lost control due to a technical glitch because of which the aircraft didn't turn towards the designated taxiway".
The DGCA will be taking the wind pressure reading from the meteorological department to verify the airline's contention and submit a total assessment report on Monday.
The primary findings by DGCA officials also show that while the aircraft was to vacate the main runway by a taxiway on the right side, it went off in the opposite direction. It first went left and broke one light on the runway's edge. While attempting to get back on the runway from the unpaved patch, it broke three more lights and went back towards the patch. In the second attempt, the aircraft damaged one more light.
"Eventually, the aircraft vacated through a taxiway which is about 300 m from the one it was originally supposed to take," said a DGCA officer. The aircraft speed at that moment was around 60-80 knots, which is usual while landing.
Officials said that not informing the air traffic control and apron control about the incident was another grave error. "The lights were broken and there were shards of glass on the runway. In such a situation, it isn't safe for other aircraft landing later. The runway has to be clear of metal and glass," said an airport official. "Fortunately, the incident was detected in 10 minutes before more flights started coming in."
Airport officials said the airline also changed the tyre of the aircraft without telling the apron control. "The tyre is replaced only if it is not working and it has to be notified as per rules," said an official.
Possible mechanical items are engines incl reversers, brakes, severe wind gusts, and of course coupled with pilot reactions.
My first look checked to see whether it hadwing mounted engines or tail mounted. I couldn't even make out an engine in the photo
OK the text suggests wing mounted
'Aircraft lost control twice after landing’ - The Times of India
Aircraft lost control twice after landing' (India)
MUMBAI: Preliminary investigations into Saturday's landing goof-up involving an Indigo flight from Chandigarh have revealed that the aircraft lost control twice before the pilot brought it under control.
The commander and the co-pilot of flight 6E 433 were de-rostered on Sunday pending a probe by the Directorate general of Civil Aviation (DGCA) into the incident.
The flight, with 140 passengers on board, deviated from the center-line of the runway and went left towards the shoulder, breaking five lights in the process. It then went further up to the unpaved area.
The pilot reportedly tried to steer the aircraft back to the runway and brought it back till the shoulder, but it veered off again towards the unpaved patch. It was only in the second attempt that the plane was brought back on the runway.
The Airbus A-320 landed at Mumbai airport at 6.35pm and went-off the 60-feet wide runway into the unpaved patch. It came back to the runway towards the taxiway without notifying the air traffic control. The incident was discovered eight minutes later when a Mumbai International Airport Pvt Ltd staffer spotted the five damaged runway lights.
On Sunday, a preliminary draft was made and the pilots were summoned for a statement, said director general of civil aviation Arun Mishra.
An Indigo spokesperson said that a gust of wind caused the incident. However, a DGCA official said that "the pilot seems to have lost control due to a technical glitch because of which the aircraft didn't turn towards the designated taxiway".
The DGCA will be taking the wind pressure reading from the meteorological department to verify the airline's contention and submit a total assessment report on Monday.
The primary findings by DGCA officials also show that while the aircraft was to vacate the main runway by a taxiway on the right side, it went off in the opposite direction. It first went left and broke one light on the runway's edge. While attempting to get back on the runway from the unpaved patch, it broke three more lights and went back towards the patch. In the second attempt, the aircraft damaged one more light.
"Eventually, the aircraft vacated through a taxiway which is about 300 m from the one it was originally supposed to take," said a DGCA officer. The aircraft speed at that moment was around 60-80 knots, which is usual while landing.
Officials said that not informing the air traffic control and apron control about the incident was another grave error. "The lights were broken and there were shards of glass on the runway. In such a situation, it isn't safe for other aircraft landing later. The runway has to be clear of metal and glass," said an airport official. "Fortunately, the incident was detected in 10 minutes before more flights started coming in."
Airport officials said the airline also changed the tyre of the aircraft without telling the apron control. "The tyre is replaced only if it is not working and it has to be notified as per rules," said an official.
Join Date: Jan 2008
Location: Houston
Posts: 6
Likes: 0
Received 0 Likes
on
0 Posts
I couldn't even make out an engine in the photo
Here's the link to where that photo originated. It was, of course, taken in Toulouse.
Photos: Airbus A320-232 Aircraft Pictures | Airliners.net
Join Date: Feb 2013
Location: The Wood
Posts: 248
Likes: 0
Received 0 Likes
on
0 Posts
It might have had something to do with the fact they were trying to land an A320 on a 60 foot wide runway! That's an 18 meter wide runway. I might lose directional control too! 
squeaky bum time. In fact, it's well outside limits. I thought 30 meters was minimum for A320.
squeaky bum time. In fact, it's well outside limits. I thought 30 meters was minimum for A320.
Last edited by WhyByFlier; 11th Mar 2013 at 22:27.
