&w=3840&q=100)
Hay found in aircraft wing delays Bangkok-bound Air India flight by 5 hours
The incident took place on June 25. Flight AI 2354, operated using an Airbus A320Neo, was scheduled to depart at 7:45 am but only took off at around 1:00 pm after the foreign object was removed and the plane was cleared for takeoff. The airline confirmed the presence of hay beneath the left wing but said the source of the debris remained unidentified.
'This was immediately attended to, and the aircraft was subsequently cleared for operation,' Air India was quoted as saying.
Crew change adds to delay of aircraft
Due to the crew reaching their regulatory duty time limits, a fresh set of personnel had to be arranged before the flight could depart. Under civil aviation rules, flight crew must not exceed a specified number of duty hours to ensure operational safety.
Passengers, who had already boarded, were disembarked and provided with refreshments during the delay. Details such as the number of passengers on board or the exact duration for which they remained at the airport were not disclosed by the airline.
DGCA heightens security after Ahmedabad plane crash
The handling agency responsible for the aircraft at Mumbai airport has been directed to carry out an investigation into the incident, which has also been reported to the Directorate General of Civil Aviation (DGCA).
This comes as India's aviation regulator has heightened scrutiny on airlines following the June 12 Ahmedabad plane crash. In a report released prior to the incident, the DGCA had flagged safety lapses. The findings, along with the plane crash, have led to increased pressure on all airlines. Air India has recently cut back on international and domestic flights and has also heightened safety checks, leading to delays and cancellations of several flights over the last week.
Try Our AI Features
Explore what Daily8 AI can do for you:
Comments
No comments yet...
Related Articles
The Print
10 hours ago
- The Print
‘Who audits the auditor?' AAIB's reports expose flaws in Indian aviation oversight—but spotlight on it too
The Air India crash in Ahmedabad has put the spotlight on the country's aviation sector. While the airline has been facing scrutiny after the 12 June crash that killed at least 275 people, the AAIB also drew criticism after it put out its preliminary report. New Delhi: Unsecured runways, faded or confusing markings, neglected wildlife hazards, overgrown vegetation—these are some of the findings of the Aircraft Accident Investigation Bureau (AAIB) in its final probe reports, highlighting a pattern of lapses in responsibility across all levels of airport management as well as regulatory oversight. This is the concluding part of ThePrint's three-part series. Read Part 1 here and Part 2 here . The concluding part of ThePrint's three-part analysis of AAIB's 68 final investigation reports on aircraft accidents put out since 2012 dwells on systemic failures that have largely escaped the headlines. While Part 2 focused on how the AAIB has cited pilot action in 67 percent of its final reports, Part 1 showed how various operators have faced flak from the Bureau for their recurring pattern of negligence and protocol violations. Eyes on the watchdog One prominent subject in the AAIB reports is the conflict between the AAIB and the Directorate General of Civil Aviation (DGCA). Take for example the 2020 Air India Express crash: Officials of the Directorate of Air Safety (DAS), a specialised division within the DGCA, 'did not agree to come and meet the investigation team' during their probe in the Kozhikode accident. The meeting was called to clarify and discuss ambiguities related to information the DGCA provided about the Flight Operations Quality Assurance monitoring, a system that collects and analyses flight data for safety oversight. The DGCA skipping the meet was a violation of the Aircraft (Investigation of Accidents and Incidents) Rules, 2017, the AAIB said. Moreover, it mentioned that the aviation watchdog's Civil Aviation Requirements (CAR) on monitoring of Digital Flight Data Recorder (DFDR) data for accident or incident prevention 'contains ambiguities in values of exceedance parameters'. 'These ambiguities were not addressed in spite of clear recommendations by the previous Court of Inquiry (COI) for the Mangalore crash 2010,' the AAIB noted. The COI probing the Air India Express Flight 812 crash, which claimed the lives of 158 people, recommended that CAR needs to be amended to remove any ambiguity regarding the exceedance limits (i.e., safety thresholds). However, the AAIB report notes that even though the CAR was revised in 2017, the amendments 'didn't address or remove any ambiguity regarding the exceedance limits'. The final report that came out in 2021 noted that the DGCA wasn't carrying out surveillance of flights operating to critical airfields and red-eye flights. As the primary investigating agency for aircraft accidents and incidents, the AAIB functions separately from the DGCA, which functions as a watchdog to oversee compliance with rules and regulations. In another instance, the AAIB found that, 'proper CAR compliance was not carried out by the regulator (the DGCA) before approval of the operator's Operations Manual'. This was mentioned in its final report of an accident involving an aircraft operated by the Directorate of Aviation (DoA), Madhya Pradesh in 2021. Moreover, the agency noted that the accountable manager at DoA was approved despite having no aviation background. Captain Amit Singh of Safety Matters Foundation called for an 'overhaul' to ensure safety in the skies. 'In Indian aviation, who audits the auditor? The need of the hour is a total overhaul, something drastic as the safety culture is beyond deterioration. Everybody is working for themselves; nobody is really bothered about safety. Past recommendations have also been buried,' Singh told ThePrint. Both the AAIB and the DGCA, Singh alleged, work for appeasement of the Ministry of Civil Aviation. 'Former airline guys working with them is also a conflict of interest. The appointments take place from the ministry. So how is the AAIB going to conduct probes independently? They are functioning in a bureaucratic manner.' 'There is a lack of independent human resources in the aviation bodies, with no clear safeguard against any conflict of interest. Half of the DGCA's posts are lying vacant,' Singh added. In July, Civil Aviation Minister Ram Mohan Naidu informed the Rajya Sabha that 190 out of 410 DGCA vacancies would be filled this year. Also Read: Air India crash: Data from recovered AI-171 Black Box downloaded, analysis underway Broken walls & guard In December 2015, a SpiceJet flight carrying 49 passengers hit wild boars while landing at Jabalpur. The AAIB identified the presence of wildlife in the operational area as well the runway as a contributing factor to the accident in its final report. It found 20 breaches in the airfield's perimeter wall as well as several openings at the bottom of the walls. 'They were adequate for the wildlife animals to enter the aerodrome premises at any time of the day,' the report noted. The Jabalpur airfield and Air Traffic Control (ATC) are controlled by the Airports Authority of India (AAI). Something similar happened in 2014 when a SpiceJet aircraft with 151 passengers hit a buffalo on the runway at Surat airport. Here too, the AAIB found multiple breaches in the boundary wall. Its report also noted that while the AAI rules stipulate daily inspection of perimeter and fence, no record was maintained. Another such case was reported at Karnataka's Jakkur aerodrome where the aircraft was substantially damaged in 2022. The AAIB report mentioned 'area near the broken perimeter wall not fully secured', as a contributory factor among others. 'Animal movement in the operational area was not identified by ATC,' it added. Moreover, the report noted that there was excessive bird activity on the runway and no measures were taken to restrict it. 'A portion (approximately 144 m) of periphery wall on the North Eastern side of the airfield, left of runway 26, is open. This open area is manned by a security guard, but no measure has been taken to secure it by means of barbed wires or fencing. Therefore, hazardous situations in the operational area due to a stray animal cannot be ruled out,' the AAIB stated. This aerodrome is owned by the Government Flying Training School (GFTS), Karnataka and ATC services are provided by the school. Missing markings & CCTV footage In its report on the 2021 accident of an Air India Express plane, the AAIB noted that the aerodrome operator at Vijayawada airport took no action in spite of repetitive observation by the regulator (DGCA) on aerodrome markings. Vijayawada airport is operated and managed by the AAI. The taxiway and apron markings weren't as per standards. In a few places, the erased taxiway markings were in white, which didn't match the tarmac and were still visible. 'It might create doubt in the mind of the crew,' the AAIB report said. The apron markings were faded and confusing. 'Alphabets and Digits are not as per standard sizes. Markings which are not in use were either not erased properly or were blurred. It has been noted in the past that ambiguity or confusion for the markings were raised by the pilots to ATC,' the AAIB stated. The report also noted that the ATC lacked surveillance in the apron area and that the aeronautical charts by the AAI were found to have not been updated. In June 2023, a Cessna 172S Skyhawk SP exited the runway and hit a paver machine at Bhiwani aerodrome—owned by the Haryana government—while carrying out a training flight. The aerodrome is leased to FSTC Flying School Private Limited for flight training in accordance with the DGCA-approved flying training organisation (FTO) permit. The final report notes that the CCTV cameras overlooking the runway were reported to be non-functional. However, this was not communicated to the DGCA as mandated by the DGCA Flying Training Circular 1 of 2022. Covering aspects like application process, instructor qualifications, and syllabus for training courses, the above-mentioned circular outlines the process for organisations to get authorisation to provide remote pilot training. (Edited by Tony Rai) Also Read: Recurring aircraft defects to faded runway lines, DGCA check reveals safety lapses at key airports
New Indian Express
2 days ago
- New Indian Express
Air India flight aborts take off in Kochi due to technical snag; MPs on board share ordeal
Air India flight AI 504 from Kochi to Delhi aborted take off on Monday due to a technical issue. Air India said the cockpit crew aborted takeoff following Standard Operating Procedures. All Passengers were disembarked, and an alternative aircraft was arranged.
Time of India
2 days ago
- Time of India
Viral Video: Greece-Germany Boeing 757 with 273 passengers on board catches fire mid-air, makes emergency landing; netizens demand probe
In yet another alarming aviation incident, a Condor flight carrying 270 passengers was forced to make an emergency landing in Italy after one of its engines caught fire shortly after take-off from Corfu, Greece. The incident added concerns to the growing list of Boeing mid-air emergencies. The incident comes just months after the tragic crash of Air India flight AI 171, a Boeing 787-8 Dreamliner, which veered off course and crashed into the hostel block of BJ Medical College in Ahmedabad, just 1.7 kilometres from the runway. The Boeing 757-300, operating as flight DE3665 to Düsseldorf, landed safely in Brindisi with no injuries reported, as per the Free Press Journal. These events, both involving Boeing aircraft, have intensified global scrutiny on the manufacturer's safety standards and raised fresh concerns among passengers and aviation experts alike. Scary visuals of a flight engine on fire mid-air go viral A German Condor flight en route to Düsseldorf was forced to make an emergency landing in southern Italy after suffering engine failure, reportedly due to a suspected bird strike. Soon after takeoff, the Boeing 757-330 (D-ABOK), flying from Corfu (CFU) to Düsseldorf (DUS), began emitting flames. Eyewitnesses reported seeing fire from the right engine's exhaust and hearing a loud explosion. There were 273 passengers on board the aircraft when the pilot executed an emergency Yesterday, Condor flight #DE3665, a Boeing 757-300 (D-ABOK) from Corfu to Düsseldorf, suffered engine surges shortly after takeoff with flames and loud bangs reported from the right crew shut it down, declared an emergency, and safely diverted to Brindisi, Italy,… Engine failure reported after take-off According to the Greek news source Phileleftheros, the incident took place on Saturday evening, August 16, shortly after the plane took off from Corfu International Airport around 8:00 pm local time. At about 1500 feet altitude, the right engine failed and caught fire. Islanders near the port area reported hearing a loud noise, which many described as an explosion, as the aircraft passed overhead. Meanwhile, the video footage recorded by locals and tourists showed flames and sparks erupting from the aircraft. This is when the pilots took immediate action and deactivated the affected engine, preventing further damage to the aircraft that made an emergency landing at Corfu airport. 🚨 BIG! Condor's Boeing 757 (D-ABOK) with 273 people on board BURST into flames right after takeoff from Corfu. Emergency landing in Brindisi, Italy.— What's happening with Boeing...? Netizens react to the viral Boeing aircraft video As soon as the video surfaced on social media, it quickly grabbed the attention of netizens. One said, "Scary the crew managed a safe emergency landing in Brindisi. While investigations will reveal the exact cause, such frequent reports are definitely raising serious concerns around Boeing's aircraft safety standards." 'Problem is with Boeing.. they keep trying to push the onus on Pilots to shrug off the accountability.. Air India Ahmedabad-London Flight was NOT a Pilot mistake as well.. That Jet had taken off (and got auto-fuel-shut-off),' another added. ' problem with Boeing full of PR mistake only.' 'If its Boeing Raven.. Its going to straight to Heaven,' one noted. "Boeing needs to be investig@ted"
