Mid-air scare: Delhi-bound IndiGo A320 flight makes emergency landing in Patna after bird hit
NEW DELHI: An
IndiGo
flight bound for Delhi with 175 passengers made an emergency landing in Patna as engine develops technical slag due to bird hit on Wednesday.
"IGO5009 Patna to Delhi reported bird hit after takeoff at 0842 IST, one dead bird in pieces found on runway during inspection.
The same was advised to the aircraft through the Approach Control Unit.
Message received from the approach control unit that aircraft requested to come back to Patna due to vibration in one engine. Local stand-by declared and aircraft landed safely at 0903 IST on runway 7. All passengers are safe," a statement issued by Patna airport said.
According to FlightRadar24, flight 6E 5009, an Airbus A320 (VT-IFL), took off from Patna at 8.41am but was diverted back shortly after take-off.
The flight was scheduled to land at Delhi's IGI Airport at 10.15 am.
Try Our AI Features
Explore what Daily8 AI can do for you:
Comments
No comments yet...
Related Articles
Time of India
4 hours ago
- Time of India
Breaking News Live Updates: Fire breaks out in Dwarka's Radisson Blu Hotel
13 Jul 2025 | 06:21:05 AM IST Breaking News Live Updates: Fire breaks out in Dwarka's Radisson Blu Hotel Breaking News Live Updates: Fire breaks out in Dwarka's Radisson Blu Hotel
&w=3840&q=100)
Business Standard
12 hours ago
- Business Standard
Air India crash: Pilots Sabharwal, Kunder remembered as calm, skilled men
Seconds before Air India flight 171 crashed while ascending from Ahmedabad, the fuel control switches of both its engines were cut off, a preliminary investigation report said on Saturday, suggesting a catastrophic pilot error. The Airlines Pilots Association of India disagreed with the report, saying the investigation is "shrouded in secrecy" appears to be biased against the pilot and has come to a conclusion hastily. The report by the Aircraft Accident Investigation Bureau (AIIB) neither concluded any reason for the switches moving nor apportioned explicit blame for the crash. It also did not identify the pilots in the voice recording. At the controls was First Officer Clive Kunder, 32, while Sumeet Sabharwal, a veteran with 30 years of experience at Air India, was the senior cockpit occupant in command monitoring the flight. Below are brief profiles of the two pilots: Captain Sumeet Sabharwal: The 56-year-old veteran with 30 years of experience at Air India had logged 15,638 flying hours, including 8,596 on the Boeing 787. He was also an Air India instructor. Sabharwal had called his family from the airport on the fateful day, assuring them that he would contact them again after landing in London. His colleagues and co-pilots in Mumbai remembered him as a gentleman, known not just for his flying skills, but for his grounded nature. Co-pilot Clive Kunder: The 32-year-old had 3,403 hours of flying experience, with 1,128 on the Dreamliner. A resident of Goregaon in Mumbai, Kunder had worked for a year as an aeronautical engineer before successfully chasing his dream to be a pilot. His neighbours remembered him as a good-natured man fond of sports who used to play cricket in the building compound. On June 12, the London-bound Boeing 787 Dreamliner began to lose thrust almost immediately after taking off from the Ahmedabad airport and ploughed into a medical college hostel, killing all but one of the 242 onboard and another 19 on the ground in the deadliest aviation accident in a decade. The AAIB report said the aircraft took off at 08:08:39 UTC (13:38:39 IST) and at about 08:09:05 UTC (13:39:05 IST) one of the pilots transmitted 'MAYDAY MAYDAY MAYDAY'. According to a chronology laid out in the report by the Aircraft Accident Investigation Bureau, both fuel control switches - which are used to turn the engines off - were moved to the cutoff position almost immediately after takeoff. At the Jal Vayu Vihar housing complex in Mumbai's Powai area, where Captain Sabharwal lived, his family members refused to speak to media persons. Security personnel at the entrance stopped journalists from entering. Captain Sabharwal's 92- year-old father Pushkaraj Sabharwal was seen entering the building. A senior citizen, who lives in the same complex, said the media should not bother Sabharwal's aged father and other family members, as they know nothing. "Do you think the pilots will give up their lives deliberately," he asked. "Whatever information you want to collect, you should collect it from Ahmedabad," the man said, adding that the "owner of the airline company" should be asked about what went wrong with the plane. In Goregaon's Ram Mandir locality, family members of Co-pilot Clive Kunder were not present in their home. (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.)
Hindustan Times
18 hours ago
- Hindustan Times
Air India flight AI171 engines moved from CUTOFF to RUN, but…: What AAIB report said
The Aircraft Accident Investigation Bureau (AAIB) on Friday released its preliminary report on the Air India crash in Ahmedabad that killed 260 people, offering the first official reconstruction of the final seconds of the doomed Air India Flight 171 (AI171). AAIB released its preliminary report a month after the Air India flight 171 crashed seconds after take off from Ahmedabad.(Bloomberg) According to the AAIB preliminary report, while both Boeing 787-8 engines were successfully commanded to restart, one of them—Engine 2—failed to recover 'core speed deceleration' and continued to lose thrust, ultimately contributing to the fatal Air India crash. The 15-page report, published exactly one month after the June 12 flight crash, provides critical technical details surrounding India's worst aviation disaster in decades. The Air India flight crashed shortly after takeoff from Ahmedabad airport. Fuel cutoff initiated mid-flight According to the AAIB report, the Boeing 787-8 reached a maximum indicated airspeed of 180 knots at 13:38:42 IST (08:08:42 UTC). Immediately after this, both engines' fuel cutoff switches moved from the 'RUN' position to 'CUTOFF', effectively stopping fuel supply to both engines and initiating a dangerous drop in thrust. Also Read | Air India plane crash report: What happens when fuel switches flip from 'run' to 'cutoff' during takeoff 'The aircraft achieved the maximum recorded airspeed of 180 Knots IAS at about 08:08:42 UTC, and immediately thereafter, the Engine 1 and Engine 2 fuel cutoff switches transitioned from RUN to CUTOFF position one after another with a time gap of 01 sec,' the preliminary report states. 'The Engine N1 and N2 began to decrease from their take-off values as the fuel supply to the engines was cut off.' Also Read | Air India crash probe report: 10 points on fuel cut, what pilots told each other In a chilling exchange captured on the cockpit voice recorder, one pilot is heard asking, 'Why did you cut off?' The other responds, 'I did not do so.' Both engines attempted relight Within seconds, both engines were commanded back to 'RUN'. 'As per the EAFR, the Engine 1 fuel cutoff switch transitioned from CUTOFF to RUN at about 08:08:52 UTC…Thereafter, at 08:08:56 UTC, the Engine 2 fuel cutoff switch transitions from CUTOFF to RUN,' AAIB report notes. 'The EGT was observed to be rising for both engines, indicating relight. Engine 1's core deceleration stopped, reversed and started to progress to recovery," the preliminary report added. Also Read | Air India flight 171 crash: What AAIB preliminary report reveals – and doesn't However, things did not pan out same for the second one, as the report says, 'Engine 2 was able to relight but could not arrest core speed deceleration and re-introduced fuel repeatedly to increase core speed acceleration and recovery.' Distress call and crash At 08:09:05 UTC, moments after the engines failed to stabilise, one of the pilots issued a 'MAYDAY' call to Air Traffic Control. According to the AAIB: 'The ATCO enquired about the call sign. ATCO did not get any response but observed the aircraft crashing outside the airport boundary and activated the emergency response.' The EAFR recording ended at 08:09:11 UTC. Crash Fire Tenders left the airport at 08:14:44 UTC to begin firefighting and rescue operations. They were joined by the local administration's fire and rescue services, but by then, the aircraft had already been engulfed in flames. The preliminary report did not place blame on either Boeing or General Electric.
