The pilot of an Indian airlines plane with 115 passengers on board while coming from Delhi to Kolkata today suspected some engineering problem and requested the ATC at NSC Bose International Airport to arrange for precautionary landing.
All arrangements were immediately made to meet any emergency situation. But the aircraft landed safely, AAI sources said.
Sources in Indian said the same plane flew to Bangkok with 55 passengers on board after minor repair and check up, which took about two hours.
The pilot of an Indian airlines plane with 115 passengers on board while coming from Delhi to Kolkata today suspected some engineering problem and requested the ATC at NSC Bose International Airport to arrange for precautionary landing.
All arrangements were immediately made to meet any emergency situation. But the aircraft landed safely, AAI sources said.
Sources in Indian said the same plane flew to Bangkok with 55 passengers on board after minor repair and check up, which took about two hours.
Is this an article worth to be made into a "news"???
__________________
Light travels faster than sound...thats why people appear bright, until you hear them talk!
Every minor incident concerning IC is covered in great detail as if there was a major disaster... while much more serious issues affecting 9W are not even mentioned in the papers!! Sounds like a pattern to me...
Mumbai, November 11: Twice on Saturday, and in a span of less than seven hours, an Alliance Air Boeing 737-2A8 was called back to the Chhatrapati Shivaji International Airport due to a “technical snag”.
While Alliance Air, a fully owned subsidiary of Indian Airlines, did not confirm the nature of the snag, Newsline has learnt that on both occasions the fault was the same— air speed indicator failure, meaning the pilot doesn’t know what speed the aircraft is flying at.
In aviation parlance, this is a “no-go snag”, which means the aircraft cannot proceed and must land immediately. “Although there are two other alternate indicators—one on the co-pilot’s side, and one in the centre panel—it’s a no-go snag if any one of the three indicators malfunction. It could jeopardise flight safety, it’s that critical,”’ said an airline engineer.
In the first instance, the aircraft had a rejected take-off around 8:40 am. “The plane was going full throttle on the runway, when there was a sudden jerk and it stopped,” said Kripa Raman (42), a passenger on the flight (CD 7561) headed to Vizag via Hyderabad.
Strangely, the same aircraft was later scheduled for a flight (CD 7179) to Mangalore. This time, it took off at 2:52 pm. “However, within minutes of being airborne, there was an air speed indicator failure on the commander’s panel. The plane then made a precautionary landing around 3:30 pm,” said an airline source.
“It was only after the snag was rectified and the aircraft cleared by the engineers that the aircraft was scheduled for the Mangalore flight,” said K Bharati, Deputy General Manager (Public Relations), Indian Airlines. The aircraft has been grounded for repairs.
Meanwhile, the 51 passengers travelling to Hyderabad were accommodated on an Indian Airlines flight at 10:15 am, while the 64 Vizag-bound passengers were put on another Alliance Air flight at 12:30 pm. Also, most of the 83 passengers on the second flight were accommodated in hotels.
The aircraft in question is over 26 years old, and has been with the national carrier since 1982. In fact, Alliance Air has 11 Boeing 737s with an average age of 25 years.
P1 side ASI is critical unit,especially on T/O roll.They had to reject if they did not know their Vr.Even if there were two Backups but its the Commanders Decision.
Bangalore-Delhi flight lands in Hyderabad after fault Bangalore, Dec 3 (UNI)
A Bangalore-Delhi Indian flight landed in Hyderabad in emergency conditions following a warning signal by the aircraft avionic system, airlines sources said. The IC-903 took off from Bangalore at 1850 hours and the pilot, as a matter of ‘‘utmost caution’’, landed at the nearest Hyderabad Airport at 2010 hours, they said. It could not be immediately ascertained when the snag in the plane was noticed. The same flight took off from Hyderabad for Delhi at 2130 hours after necessary repair work.
NEW DELHI: The Indira Gandhi International (IGI) Airport witnessed high drama for several hours late on Sunday night when an Indian Airlines flight skidded off the runway after landing.
While the 130 passengers on board Airbus A-320 had a miraculous escape, the plane got stuck in such a way that the main runway was blocked for nearly seven hours.
Luckily, visibility was high and the secondary runway could be used.
It was 11 pm on Sunday when IC-402 landed on the main runway here from Kolkata. Just as the plane swerved from the main runway to a taxiway for reaching the domestic terminal, it developed a hydraulic snag, which affected steering control. The Airbus went off the taxiway and its nose wheel and right wheel went onto the adjoining kutcha ground, said airport sources.
On their part, an airline spokesperson admitted "the plane had landed safely, but after slowing down, it went a few feet off the runway."
Emergency vehicles like ambulances and firetenders were rushed to the aircraft. "Luckily for passengers, there have been no rains in Delhi recently, and the ground was firm and not muddy. This prevented the plane from tilting to one side. Stepladders were used to bring out passengers and they were taken to the arrival terminal in coaches. The baggage was also taken out from the stuck plane," said an official.
With passengers gone, it was time to deal with another trouble.
The plane had got stuck in such a way that its rear portion protruded on to the main runway and it had to be closed for all aircraft movement. Good visibility proved to be the saving grace as the secondary runway could be pressed into service.
Being smaller in length, planes going on long haul sectors with full load of passengers, cargo and fuel prefer to use the longer runway to take a full run-up before taking off.
"Two such airlines, Continental and American, which fly to the US first wanted to wait for the main runway to be cleared so that they could avoid taking off from the smaller one. But after a long wait, they decided to opt for the secondary runway," said an official.
All other incoming and outgoing aircraft immediately opted for the secondary runway to avoid delays.
Meanwhile, efforts were on to remove the stuck plane from the taxiway. Being its technical base, Indian had all the required equipment at IGI to tow the plane, but lack of manpower at night and waiting for a team from the Directorate General of Civil Aviation (DGCA) for inspection meant that the plane could be moved to a hangar only around 5.30 am. The main runway was free for regular use around 6 pm — a good seven hours after the incident.
The incident revived memories of an Air Sahara plane skidding off the runway during last year's torrential monsoon in Mumbai and remaining stuck there for over two days.
For Indian, this was the second case of technical snag on Sunday. In the afternoon, its Bangalore-Delhi flight was delayed for several hours and when it finally took off, it had to land at Hyderabad after developing another fault.
Most news reports, including Times Now, even went to the extent of saying it was an Indian flight with 320 pax!!
NDTV had news on this in its India 60 minutes programme from 8 pm to 9 pm (Dec. 5, 2006). Was the second last news item.
Sonia Singh interviewed a pax who was on board --- Rakesh Vaid who is a frequent flier. Said they landed and the plane kept continuing to run. Was sitting in front, so guess it must have been J. There was a jolt and said he saw from his window seat that they were in mud/rough.
Says the cabin crew then made the announcements "of the outside temp being ... and that if you have any prob to contact ..." Rakesh said he had to get up and tell the cabin crew that something was wrong. Pilot then came on the PA to say it was a hydraulic failure.
Sonia then said IA and AI pilots generally get the flak for bad flying, but what was it in this case. Rakesh praised the pilot and said it was presence of mind, also praised Bombay emergency services for sending the fire tenders out in a few seeconds.
Sonia, as usual(!!!!) kept saying "a happy ending after a miraculous landing for 300 passengers." NDTV also had okay graphics to go with the story. Repeatedly showed an IA plane landing and rolling sideways into the mud.
It was an A320 (VT-EPE)!! But it was 300 pax for Sonia Singh!!!
Crew320. Plz clarify how the cabin crew could make the annoucements as soon as the plane landed, as this pax Rakesh says?
They should start the announcements after a visual check outside and only when the plane begins taxing back to the terminal, right? Have clarified this once with a senior IA cabin crew member.
Sonia, as usual(!!!!) kept saying "a happy ending after a miraculous landing for 300 passengers." NDTV also had okay graphics to go with the story. Repeatedly showed an IA plane landing and rolling sideways into the mud.
It was an A320 (VT-EPE)!! But it was 300 pax for Sonia Singh!!!
VT-EPE???
I had flown in that aircraft on 27th Nov on MAA-BOM...
__________________
Light travels faster than sound...thats why people appear bright, until you hear them talk!
Crew320. Plz clarify how the cabin crew could make the annoucements as soon as the plane landed, as this pax Rakesh says?
They should start the announcements after a visual check outside and only when the plane begins taxing back to the terminal, right? Have clarified this once with a senior IA cabin crew member.
KCM, as per company policy I cannot really speak much when press is involved. However, what I can say is that the announcements are generally started when the aircraft is about to get off the runway and enter the taxiway. Simple reason being, in most of the cases after landing thrust reversers are used and it makes a lotta noise inside the cabin.
There are a lot of airports where the distance between the taxi-in point and the bay is hardly a few minutes. So the cabin crew incharge for the announcements start it a little early to be on the safer side. Also, the fact that the Delhi sector has an additional announcement for connecting international passengers to use the complimentary coach demands the crew to finish it all intime.
However, a mistake is a mistake and this might be one of them. Its amazing how effective the PR depts of most of the private airlines are when compared to IC. A few days ago an IT aircraft had its slide/raft inadvertently deployed in HYD, did that reach out to anyone in India?? Isnt opening the door in the armed position by an IT crew not considered a mistake more serious than continuing an announcement after a jolt...
MEL, the recorded announcement option is disabled and not used on any of the IC aircrafts...
crew320 wrote:However, a mistake is a mistake and this might be one of them. Its amazing how effective the PR depts of most of the private airlines are when compared to IC. A few days ago an IT aircraft had its slide/raft inadvertently deployed in HYD, did that reach out to anyone in India?? Isnt opening the door in the armed position by an IT crew not considered a mistake more serious than continuing an announcement after a jolt...
But then C320, aren't IC in the business for longest time however have the poorest safety record in the last 3yrs and lately there hasn't been a single week without an IC Incident, God bless none turned into a accident, whereas each incident had the potential, Probably Qudos to the IC crew for all of this. If IC hadn't been a govt owned entity the DGCA would shut it down Lock, Stock and Barrel for the repeated IFShutdowns.
IMO the Jolt was a far more serious incident, situational awareness is very important for the cabin crew especially during the 2 most critical phases of flt. We all have seen the fate of the A343 at YYZ (correct?) which overshot the runway on ldg. Inadvertent slide deployment is a common occurence worldwide, though i don't condone it in anyway, same numty hosties.