Facebook Instagram Linkedin X-twitter Youtube

About Us
Contact Us
Advertisement

About Us
Contact Us
Advertisement

Aviation Newsletter

WhatsApp Channel

Latest News
Aviation Today Perspectives
Aviation Jobs
About Us

Latest News
Aviation Today Perspectives
Aviation Jobs
About Us

Subscribe Now

Latest News
Aviation Today Perspectives
Aviation Jobs
About Us

Latest News
Aviation Today Perspectives
Aviation Jobs
About Us

News

Civil Aviation

Pilot Training

Flight School Analysis

Aviation Jobs

Training

Services

About Us

Subscribe Now

Aviation Today News Desk

New Delhi: A SpiceJet flight preparing for departure from Delhi was disrupted earlier this week after the aircraft's air-conditioning system failed while passengers were still boarding. The incident, captured on video by passengers and widely shared on social media, drew criticism over cabin preparedness and passenger handling on the ground. Onboard Discomfort Escalates The incident occurred on July 15 on a domestic SpiceJet flight at Delhi’s Indira Gandhi International Airport. According to passenger reports and video evidence, the aircraft remained on the ground for an extended period with no active air-conditioning, leading to visibly distressed passengers. Several passengers can be seen fanning themselves and expressing discomfort, with rising cabin temperatures triggering tensions. The video footage captures passengers loudly demanding the crew “AC chala do” (turn on the AC), while others attempted to leave their seats in protest. The cabin crew reportedly made announcements asking passengers to remain seated and assured them that ground staff were working to resolve the issue. However, according to passengers on board, the delay lasted nearly 45 minutes, during which no effective cooling was provided. Unruly Behaviour and Passenger De-boarding As the situation escalated, two passengers were asked to deboard after allegedly arguing with the crew and attempting to approach the front galley. SpiceJet, in a brief internal report reviewed by airport sources, confirmed that the two individuals were offloaded for non-compliance with crew instructions. Security staff and airline representatives were called to the aircraft, and the situation was resolved without further delay. The aircraft was later cleared for departure after a technical inspection and resumption of cooling systems. The Directorate General of Civil Aviation (DGCA) has not issued a public statement but is understood to be monitoring the case as part of routine oversight. A preliminary review of aircraft readiness and turnaround procedures may follow, especially given the high ambient temperatures currently prevailing across North India. Cockpit Intrusion Incident In a separate and unrelated incident, another SpiceJet flight (SG 9282, Delhi to Mumbai) faced disruption on July 14 when two male passengers attempted to access the cockpit while the aircraft was taxiing. The flight was brought back to the parking bay, and the individuals were handed over to the Central Industrial Security Force (CISF). The flight departed with a significant delay after security clearance.

SpiceJet Flight Hit by AC Failure Sparks Passenger Outcry, Unruly Passengers Removed

July 18, 2025

Magadan, Russia: Russian emergency authorities have confirmed the deaths of five people following the crash of a Mil Mi-8 helicopter that went missing earlier this week in the country’s Far Eastern region. The helicopter, operated by Magadan-based civil aviation company APK Vzlyot, had been en route from Chumikan to Magadan on July 14 when it lost radio contact and disappeared from radar. The aircraft was carrying three crew members and two technical staff at the time. Following an intensive search operation, Russia’s Ministry of Emergency Situations (EMERCOM) announced on July 16 that the wreckage was discovered near Cape Gadikan in Khabarovsk Krai, a remote and mountainous coastal area along the Sea of Okhotsk. All five individuals on board were found dead. “The search and rescue team located the aircraft's debris in a hard-to-reach area. There were no survivors,” a spokesperson for the Ministry stated. No Distress Signal Received Officials confirmed that no distress signal had been received from the helicopter prior to its disappearance. The emergency locator beacon reportedly failed to activate, which complicated the initial search efforts. Weather conditions in the region, known for heavy fog and rugged terrain, had also hampered aerial reconnaissance flights during the first two days of the operation. Criminal Investigation Underway Russia’s Investigative Committee has launched a criminal case under Article 263 of the Russian Criminal Code, which addresses violations of safety rules during air transport operations. The probe will focus on whether flight safety regulations were properly followed by the operator. Investigators are currently examining the crash site and are expected to retrieve flight documentation and inspect any recoverable components of the aircraft. There is no official comment yet regarding the helicopter’s technical condition or any preliminary cause of the crash. Background on the Aircraft and Operator The Mi-8 is a Soviet-designed medium twin-turbine helicopter widely used in both civil and military aviation. Despite its age, it remains in extensive service across remote regions of Russia due to its reliability and load-carrying capability. APK Vzlyot, the operator of the downed helicopter, provides cargo and passenger transport services across the Russian Far East. The company has not released a public statement as of this writing but is cooperating with authorities. This is a developing story. Further details will be provided as they are released by EMERCOM, the Investigative Committee, or Rosaviatsiya, Russia’s federal air transport agency.

Five Dead in Russian Mi-8 Helicopter Crash, Wreckage Found After 48-Hour Search

July 17, 2025

India: A Right to Information (RTI) response from the Directorate General of Civil Aviation (DGCA), as reported by The Times of India, has revealed that Indian airspace recorded 65 in-flight engine shutdowns over the past five years. The data also disclosed 11 Mayday calls between January 1, 2024, and May 31, 2025, four of which were linked to Hyderabad’s air traffic control region. Engine Shutdowns Involving Multiple Airlines and Aircraft The incidents spanned both domestic and foreign carriers, with shutdowns occurring during takeoff, in cruise, or as a precautionary measure following cockpit alerts. The DGCA identified key technical causes, including: Blocked or contaminated fuel filters Interrupted fuel supply Oil pressure loss Foreign object ingestion Turbine control unit malfunctions All 65 incidents were classified as reportable occurrences under India’s civil aviation regulations and were investigated by the concerned operators under DGCA supervision. “We continue to witness shutdowns due to recurring causes like fuel contamination or component wear. Every occurrence is tracked and mandates technical review,” said Capt. C. S. Randhawa, President of the Federation of Indian Pilots. Mayday Calls Highlight Critical Emergencies The DGCA confirmed that the 11 Mayday calls issued during the 17-month period were in response to severe emergencies requiring immediate crew response. These included engine fires, hydraulic failures, and other situations jeopardizing flight safety. “A Mayday is the most serious alert. When pilots call one, it means the situation demands urgent intervention be it fire, total engine loss, or system failure,” explained Anil Rao, Executive Member, ALPA-India. Though the RTI reply did not identify the specific flights or aircraft types, officials confirmed that all events were subject to post-flight safety reviews, many involving the Aircraft Accident Investigation Bureau (AAIB). BCAS Staffing Vacancies Raise Oversight Concerns Separately, the Bureau of Civil Aviation Security (BCAS), India’s aviation security watchdog, reported 224 vacancies out of 598 sanctioned posts as of March 2025. The shortfall represents a staffing gap of over 37%. A recent parliamentary standing committee had raised concerns that such vacancies may hinder effective regulatory oversight. Air India Express Crash Raises Safety Scrutiny The disclosure comes shortly after the Air India Express Flight IX-171 crash near Ahmedabad on June 12, 2025, in which an engine failure during climb-out was suspected based on preliminary reports. While the DGCA has not confirmed whether the case is counted among the 65 shutdowns, the timeline places it within the scope of the RTI data. Aviation regulators emphasize that twin-engine aircraft are certified under ETOPS to continue flying with one engine inoperative, but each incident is taken seriously. Investigations may lead to maintenance bulletins, airworthiness directives, or fleet-wide inspections. Lack of Public Safety Dashboard India currently does not provide a public-facing aviation safety dashboard like the FAA’s Aviation Safety Information Analysis and Sharing (ASIAS) system. Access to data on technical issues or Mayday calls remains limited, often requiring RTI filings. Increased transparency in aviation safety has been a growing demand among Indian aviation stakeholders. In its June 2025 report, a civil aviation working group recommended enhanced publication of anonymized safety statistics and the establishment of a centralized digital platform for incident data.

DGCA Confirms 65 Engine Shutdowns Since 2020 and 11 Maydays in Last 17 Months

July 17, 2025

Tuva, Russia: An Air China Airbus A350-900 operating as Flight CA967 from Shanghai Pudong to Milan Malpensa was involved in a serious airspace incident over southern Siberia after it climbed through an occupied flight level, coming dangerously close to a cargo aircraft. According to preliminary radar and ATC data, the Air China aircraft began a climb from 34,100 feet to 36,000 feet without receiving explicit clearance from Russian air traffic control. During this unauthorized climb, the aircraft came within approximately 300 to 400 feet vertically of an SF Airlines Boeing 767 freighter cruising at 35,000 feet on a crossing path. The incident occurred over the Tuva region of the Russian Federation at approximately 21:39 UTC. TCAS Resolution Prevents Collision Both aircraft were equipped with functioning Traffic Collision Avoidance Systems (TCAS), which detected the impending conflict and issued resolution advisories. Crews on both aircraft responded promptly to TCAS instructions. No collision occurred, and both flights continued to their respective destinations without further incident. The separation between the two aircraft fell significantly below the minimum vertical separation required under ICAO standards, which is 1,000 feet for aircraft at cruising altitude. Controller-Pilot Communication Discrepancies Cockpit audio recordings released on social media and verified by local media outlets reveal apparent miscommunication between the Air China crew and Russian air traffic control. In the audio, the pilot of the SF Airlines cargo aircraft can be heard questioning the Air China flight’s climb, stating that the aircraft had initiated the climb while only 20 nautical miles ahead and without clearance. The Air China pilot did not confirm that clearance was received and appeared to acknowledge that the climb had not been explicitly approved. Russian controllers can be heard instructing other aircraft in the vicinity to maintain level flight to avoid additional conflict during the incident. Investigation Authorities from the Civil Aviation Administration of China (CAAC) and Russia's Federal Air Transport Agency (Rosaviatsiya) have launched a joint investigation. Both regulatory bodies have confirmed that standard incident reporting procedures have been initiated and that flight data recorders, cockpit voice recordings, and ATC logs will be reviewed. Officials are examining possible causes including frequency congestion, language barriers, and incorrect readbacks. The Tuva region lies within a transition area where communication overlaps and limited coverage have previously been noted in operational reports. No passengers or crew were injured during the incident. Flight CA967 continued to Milan Malpensa, arriving on schedule. The SF Airlines Boeing 767 also completed its scheduled route without diversion. Authorities have not yet released the final investigation timeline. Air China has not issued a public statement as of this report.

Air China A350 Breaches Altitude Separation, Near-Miss with Cargo Jet Over Russia

July 16, 2025

Vancouver, Canada: A stolen Cessna 172 aircraft caused a significant security incident and temporary flight disruptions at Vancouver International Airport (YVR) on Tuesday afternoon, prompting an emergency response by airport authorities and federal law enforcement agencies. According to a statement issued by the Richmond Royal Canadian Mounted Police (RCMP), the aircraft was reported stolen from the Victoria Flying Club, based at Victoria International Airport, shortly after 1:00 p.m. PDT. The plane was identified as having departed Victoria without authorization and subsequently entered Vancouver’s controlled airspace without prior clearance. Airport officials and air traffic controllers monitored the aircraft as it approached and circled the airspace above Vancouver International Airport. Flight tracking data showed the Cessna maneuvering erratically at low altitude, raising immediate concerns among air traffic personnel. Out of precaution, the airport implemented a full ground stop on all inbound arrivals at approximately 1:15 p.m., halting flight operations while authorities coordinated a response. At approximately 1:45 p.m., the aircraft made a safe landing at YVR. The RCMP, supported by YVR Security and RCMP Air Services, moved quickly to secure the aircraft and arrest the individual who was taken into custody without incident on the airfield. No injuries were reported during the event, and the aircraft sustained no apparent damage. A total of nine inbound flights were diverted during the lockdown period, and dozens more were delayed. The temporary ground stop lasted for approximately 39 minutes, with normal flight operations resuming shortly after 2:00 p.m. The Vancouver Airport Authority later confirmed that while residual delays were expected, the airport had returned to regular operational status. In an official update, Richmond RCMP stated that the individual taken into custody is believed to have acted alone. The identity of the suspect has not yet been disclosed, and no motive has been confirmed at this stage of the investigation. Authorities confirmed that the individual did not possess clearance to operate the aircraft and is not believed to be a licensed commercial pilot. The Transportation Safety Board of Canada (TSB) has been notified and is assessing whether a formal investigation will be opened. Meanwhile, the RCMP has launched a criminal investigation into the unauthorized use of the aircraft, including potential violations of the Canadian Aviation Regulations and other federal statutes. The Victoria Flying Club, operator of the aircraft, issued a brief statement acknowledging the incident and confirmed it is fully cooperating with investigators. Airport operations at YVR have since stabilized, and the airport authority has advised travelers to monitor airline communications for any residual delays or schedule adjustments. No further public safety threats are currently associated with the event, according to police. Authorities are expected to release additional details as the investigation progresses.

Stolen Cessna Causes Disruption at Vancouver Airport, Suspect Had No Pilot License

July 16, 2025

London, United Kingdom: Four people were killed when a medical transport aircraft operated by Zeusch Aviation crashed shortly after takeoff from London Southend Airport on Sunday, July 14. Authorities have confirmed that all four occupants onboard the Beechcraft B200 Super King Air perished in the incident. The UK’s Air Accidents Investigation Branch (AAIB) and Essex Police are continuing a full investigation into the cause of the crash, which occurred just seconds after the aircraft lifted off from Runway 05. Fatalities Confirmed In an official statement released Monday, Essex Police confirmed the deaths of all four individuals aboard. Chief Superintendent Morgan Cronin stated: "Sadly, we can now confirm that all four people on board died. We are working closely with partner agencies, including the Air Accidents Investigation Branch, to recover all available information." Formal identification of the victims is ongoing, and their families are being supported by liaison officers. While official identities have not yet been published by Essex Police, documents reviewed by Britain’s national news agency PA indicate that the deceased included two Dutch pilots, a 31-year-old Chilean-born German flight nurse, and another foreign medical staff member. The nurse, later identified by multiple media outlets as Maria Fernanda Rojas Ortiz, was reportedly on her first day of duty aboard the aircraft. Crash Circumstances The aircraft, registered in the Netherlands and operated by Zeusch Aviation, was performing a medical repatriation flight bound for the Netherlands, following earlier stops in Greece and Croatia. The flight was designated SUZ1. Witnesses and preliminary flight data suggest the aircraft became airborne, banked sharply to the left, inverted, and descended rapidly before crashing into the ground near the airport perimeter. The impact produced a large fireball and thick smoke visible across much of Essex. Emergency services from Essex Police, Fire and Rescue, ambulance services, and Southend Airport personnel responded within minutes. A full cordon was established, and nearby roads were closed as a precaution. A Civil Aviation Authority (CAA) air exclusion zone remains in place over the site. The crash site was secured to facilitate recovery of wreckage, flight recorders, and technical components, which are now being examined by AAIB inspectors. London Southend Airport suspended all flights immediately following the crash. The airport remains closed as of Tuesday, July 15, with no estimated time for reopening announced. Airlines have advised passengers to check for updates and alternative travel arrangements. Investigation Continues The AAIB has deployed a multidisciplinary team to Southend to investigate the circumstances leading to the accident. Both the cockpit voice recorder (CVR) and flight data recorder (FDR) have been located and are undergoing analysis. No preliminary findings have yet been published. In a statement, Zeusch Aviation acknowledged the loss of its crew and support staff and expressed full cooperation with UK authorities: "We are devastated by this tragic event. Our thoughts are with the families of our crew and colleagues. We are assisting investigators and will continue to share relevant updates in due course." Authorities have urged members of the public who witnessed the crash or captured it on video to provide their materials directly to investigators rather than share them on social media. Chief Superintendent Cronin added that the priority now is “to support the families affected and establish the full facts behind what happened.”

All Four Aboard Killed in Southend Airport Crash, AAIB Recovers Flight Recorders

July 15, 2025

Dubai, United Arab Emirates: Emirates has launched an extensive series of pilot recruitment roadshows across the UK, Ireland, and Europe as part of its ongoing global hiring campaign. The initiative aims to recruit experienced pilots for its growing fleet and support its operational expansion over the next several years. The airline is actively hiring for positions including First Officer, Direct Entry Captain, and roles under its Accelerated Command Program. These in-person sessions offer qualified pilots a chance to directly engage with Emirates’ recruitment and flight operations teams. UK & Ireland – July 2025 Emirates is hosting roadshows in five major cities during July: Dublin: 17–18 July Edinburgh: 19 July Birmingham: 21–22 July London Stansted: 24–25 July London Gatwick: 27–28 July These sessions are designed for experienced commercial pilots currently based in or near the UK and Ireland. Pilots will receive comprehensive briefings on career progression, lifestyle in Dubai, training standards, and compensation packages. Central & Southeast Europe – December 2025 The campaign continues in December, with roadshows scheduled for: Athens, Greece – 8–9 December Belgrade, Serbia – 10–11 December Budapest, Hungary – 13–14 December These sessions are open to pilots based in the Balkans, Central, and Eastern Europe. Emirates aims to tap into strong regional pilot talent and provide opportunities for those looking to transition into a global flying career. Emirates' Hiring Focus The recruitment drive supports Emirates' plan to hire over 550 pilots in 2025, with a multi-year goal of 1,500 new pilots by 2027. The airline continues to receive new aircraft and expand its route network, increasing demand for skilled flight crew across its widebody fleet. All candidates are expected to meet Emirates' standard requirements, including: Valid ICAO ATPL Recent flying experience on modern multi-engine jets English language proficiency (ICAO Level 4 minimum) Clean flight safety record What to Expect at the Roadshows The sessions include detailed presentations on: Emirates' training and operational standards Flight schedules, roster stability, and upgrade opportunities Tax-free salary and benefit structure Relocation and family support in Dubai Pilots attending the roadshows will also have the opportunity to speak directly with Emirates representatives to understand eligibility, selection process, and career progression. Registration and More Information Walk-ins are welcome, and pre-registration is optional. Emirates encourages all interested pilots to visit the official careers portal to confirm attendance, review requirements, and stay informed: 🔗 www.emiratesgroupcareers.com/pilots

Emirates Begins Pilot Hiring Roadshows Across UK, Ireland, Greece, Serbia and Hungary

July 15, 2025

United States: Air travel across the United States experienced major disruption on Monday as severe weather systems swept across multiple states, grounding flights and straining airline operations. According to the latest data from tracking services and airport authorities, over 5,490 flights were delayed and 865 flights canceled as of mid-day, affecting both domestic and international operations. Airports Most Severely Affected The weather-related disruption has impacted some of the country’s busiest aviation hubs. Dallas–Fort Worth International Airport (DFW) recorded the highest number of delays and cancellations, with 648 delays and over 315 cancellations reported. In the Midwest, Chicago O’Hare International Airport (ORD) reported over 417 delays and more than 50 cancellations. The Northeast corridor, a critical region for airline operations, was also significantly affected. Boston Logan International Airport (BOS) saw more than 340 delays, while New York-area airports experienced mounting cancellations and extended ground delays due to active thunderstorms and air traffic management restrictions. In the South, Hartsfield–Jackson Atlanta International Airport (ATL) logged over 450 delays, making it one of the hardest-hit airports in the Southeast. Additional delays were reported at Philadelphia International Airport (PHL), where airlines struggled with storm-related ground stoppages and equipment slowdowns. Airlines Respond to Operational Challenges Major U.S. carriers including Delta Air Lines, American Airlines, United Airlines, JetBlue, and Spirit Airlines have been forced to either cancel or significantly delay flights across their domestic networks. Several airlines activated contingency plans, reassigning crews and equipment to minimize disruption to operations. Airlines have issued advisories for passengers traveling through impacted airports, urging them to check their flight status before leaving for the airport and allowing additional time for check-in and boarding. Many have also offered travel waivers, allowing rebooking without penalty for flights scheduled between July 14 and July 16. FAA Implements Weather-Related Traffic Flow Measures The Federal Aviation Administration (FAA) confirmed that weather-related traffic management initiatives were in place at multiple locations, including Newark Liberty International (EWR), John F. Kennedy International (JFK), and LaGuardia Airport (LGA). These include ground delay programs and flow restrictions to safely manage the volume of aircraft during active thunderstorms and low-visibility conditions. In addition, ground stops were temporarily imposed in parts of Florida, including Orlando, Fort Lauderdale, and Miami, as the storm system extended into the Southeast. Summer Travel Season Compounded by Weather The timing of the disruption comes during one of the busiest travel periods of the year. The summer season has already posed challenges for air traffic control and airport operations, with record passenger volumes, tight crew scheduling, and ongoing staffing pressures. According to data from the U.S. Department of Transportation, travel volumes in July 2025 are trending above pre-pandemic levels, making the impact of operational disruptions more severe for both airlines and travelers. Flight Disruption Likely to Continue Meteorologists have forecast continued storm activity along the East Coast and Midwest through Tuesday, increasing the likelihood of further disruptions. Airlines are urging passengers with flexible travel plans to consider alternative dates. Airport authorities across affected cities have also issued travel advisories and are working with airlines and ground handling teams to manage crowd control and terminal congestion. Passengers are advised to stay updated through airline apps, official airport websites, and the FAA’s real-time flight status portal.

Severe Storms Trigger 5,000+ Flight Delays and 800 Cancellations Across U.S. Airports

July 14, 2025

London, United Kingdom: A twin-engine turboprop aircraft operated by Zeusch Aviation crashed shortly after takeoff from London Southend Airport on Saturday, July 13, prompting the temporary closure of the airport and an ongoing investigation by UK aviation authorities. Aircraft and Flight Information The aircraft involved was a Beechcraft B200 Super King Air, registered to Netherlands-based Zeusch Aviation. According to flight data and initial confirmations from the operator, the aircraft was conducting a medical transport mission at the time of the crash. The flight was reportedly en route to the Netherlands, having earlier stopped in Greece and Croatia. It was designated as flight SUZ1. The incident occurred moments after the aircraft departed from Runway 05 at Southend Airport in Essex. Witnesses and preliminary flight path data indicate the aircraft became airborne before sharply banking left, inverting, and descending rapidly to the ground, resulting in a fireball and thick black smoke visible from several kilometers away. Emergency Response Emergency services responded within minutes. Essex Police confirmed that fire and rescue personnel, ambulances, and airport fire crews were immediately deployed to the crash site, located near the end of the airport's main runway. A cordon was established around the wreckage, and the public was advised to avoid the area. Authorities have not confirmed the number of individuals onboard at the time of the crash or released any information on casualties, though recovery operations have been ongoing since Saturday afternoon. Airport Closure London Southend Airport suspended all operations in the aftermath of the crash. As of Monday, July 14, the airport remains closed while the investigation continues. Flight departures and arrivals have been cancelled or diverted, and passengers have been advised to check with airlines for alternative arrangements. Investigation The UK’s Air Accidents Investigation Branch (AAIB) has launched an official investigation into the crash. Inspectors and recovery teams have been deployed to the scene to secure flight data recorders and other evidence critical to understanding the cause of the incident. The AAIB has not yet released any preliminary findings or official statements on possible mechanical failure or pilot action. Zeusch Aviation has issued a brief statement acknowledging the accident and confirming that the aircraft was operating under its command. The company expressed cooperation with the AAIB and local authorities and stated that more information would be shared as it becomes available. Eyewitness Reports Several individuals near the airport, including those on nearby roads and golf courses, reported seeing the aircraft experience difficulties moments after takeoff. Some described the aircraft waving or banking before entering what appeared to be an uncontrolled descent. Others reported hearing a loud explosion and seeing a plume of smoke rising above the crash site. Local authorities have requested that individuals who witnessed the incident or recorded video footage provide their material directly to investigators rather than share it publicly. As of this report, no formal casualty figures or identities have been released. The AAIB is expected to issue an initial update in the coming days once primary data, including the cockpit voice recorder and flight data recorder, is recovered and analyzed. Operations at Southend Airport will remain suspended pending clearance from investigators and relevant safety authorities. Authorities have asked the public to refrain from speculation and allow the investigative process to proceed. Further details will be shared following the release of the AAIB’s preliminary report.

Small Aircraft Crashes Seconds After Takeoff from Southend Airport, UK AAIB Probes

July 14, 2025

Ahmedabad, India: The Aircraft Accident Investigation Bureau (AAIB) has released the preliminary report into the crash of Air India’s Boeing 787-8 Dreamliner, registration VT-ANB, which occurred on 12 June 2025 shortly after takeoff from Ahmedabad’s Sardar Vallabhbhai Patel International Airport. The scheduled flight, operating as AI171, was bound for London Gatwick Airport with 230 passengers, 10 cabin crew, and 2 flight crew on board. All 241 persons on board perished in the accident. Additionally, 19 fatalities were reported on the ground. Aircraft and Crew Information The aircraft involved was a Boeing 787-8 with serial number 36279, manufactured in 2013, and operated by Air India. Both engines were General Electric GEnx-1B series units, installed in March and May 2025 respectively. The aircraft had a valid Certificate of Airworthiness and had undergone its last Airworthiness Review on 22 May 2025. The Pilot-in-Command held an ATPL with over 15,638 hours of total flying experience, including 8,596 hours on type. The First Officer held a CPL with 3,403 hours of total flying experience, of which 1,128 hours were on type. Both pilots were based in Mumbai, had arrived in Ahmedabad the previous day, and had met required rest periods. The First Officer was the Pilot Flying for the accident flight. Sequence of Events On 12 June 2025, VT-ANB had earlier operated AI423 from Delhi and landed at Ahmedabad at 05:47 UTC. A post-flight defect regarding “STAB POS XDCR” was logged and addressed by on-duty maintenance personnel before the aircraft was released for its next flight. Flight AI171 was scheduled for departure at 07:40 UTC. The aircraft pushed back from Bay 34 at 07:48 UTC, taxied to Runway 23, and received takeoff clearance at 08:07:33 UTC. The aircraft began its takeoff roll at 08:07:37 UTC. According to data recovered from the Enhanced Airborne Flight Recorder (EAFR), the aircraft reached V1 at 08:08:33 UTC and rotation speed (Vr) at 08:08:35 UTC. It lifted off at 08:08:39 UTC and reached a maximum recorded indicated airspeed of 180 knots at 08:08:42 UTC. At that moment, both engine fuel control switches, first for Engine 1 and then for Engine 2, with a one-second interval transitioned from the “RUN” to the “CUTOFF” position. The data indicated an immediate decrease in N1 and N2 engine speeds, consistent with fuel supply being cut off. Cockpit voice recordings captured a pilot questioning the action, with one asking, “Why did you cut off?” and the other responding that he had not. No further verbal conflict or distress was recorded before the power loss. Power Loss and Emergency Response The sudden loss of thrust from both engines triggered the deployment of the Ram Air Turbine (RAT), visible on CCTV footage from the airport. The RAT began supplying hydraulic power by 08:08:47 UTC, confirming the engines were no longer providing power. At 08:08:52 UTC, the Engine 1 fuel control switch was moved back to “RUN,” followed by Engine 2 at 08:08:56 UTC. The Auxiliary Power Unit (APU) inlet door also began to open at this time, indicating an automatic start sequence. Both engines attempted relight: Engine 1 showed signs of core recovery, while Engine 2 relit but could not stabilize its core speed. At 08:09:05 UTC, a MAYDAY call was transmitted by one of the pilots. No further communication was received. The aircraft lost altitude rapidly and crashed into the BJ Medical College hostel complex approximately 0.9 nautical miles from the end of Runway 23. The impact caused destruction of five buildings and extensive fire damage. All occupants of the aircraft were fatally injured. According to the report, the Emergency Locator Transmitter (ELT) was not activated during the sequence. Recovery and Wreckage The wreckage was spread across an area of approximately 1000 feet by 400 feet. The vertical stabilizer, main landing gear, fuselage components, both engines, and nose gear were found at various distances from the initial impact point. The thrust levers were discovered near the idle position, though flight data indicated they were forward (takeoff thrust) until impact. The fuel control switches were found in the “RUN” position post-crash. The forward EAFR was successfully recovered and downloaded using equipment supplied by the U.S. National Transportation Safety Board (NTSB). It contained approximately 49 hours of flight data and two hours of audio, including the accident flight. The aft EAFR was too severely damaged to retrieve data. Ongoing Investigation The investigation team comprises AAIB India officers, subject matter experts, and international participants from NTSB (USA), Boeing, General Electric, the FAA, and authorities representing nations whose citizens were onboard. As of the preliminary report, there are no recommendations issued to operators or manufacturers of the B787-8 aircraft or GEnx-1B engines. Fuel samples tested from the bowsers and tanks used to refuel the aircraft were found satisfactory. Additional trace samples collected from the APU and refuel/jettison systems are being sent for further testing. Statements from witnesses and the sole surviving passenger have been recorded. Post-mortem analyses are underway to determine any relevant aeromedical findings. The AAIB emphasized that the investigation remains ongoing, and all evidence, including maintenance records, crew history, and system components, will continue to be evaluated.

Cockpit Voice Captures Fuel Cutoff Confusion in Air India AI171 Crash Preliminary Report

July 12, 2025

« Previous Page1 … Page101 Page102 Page103 Page104 Page105 … Page137 Next »

Facebook-f Instagram Linkedin-in X-twitter Youtube

AVIATION TODAY brings the latest in aviation and aims to cater information to professionals and Aviation Enthusiasts about the Industry.

Quick Links

About Us
Contact Us
Services
Advertise
FAQ

Navigate

Latest News
Civil Aviation
Pilot Training
Flight School Analysis
Aviation Jobs
Training

General Support

info@aviationtoday.in

News Desk Support

news@aviationtoday.in

Facebook-f Instagram Linkedin-in X-twitter Youtube

Terms of Use
Privacy Policy
Disclaimer

About Us
Latest News
Aviation Today Perspectives
Aviation Jobs
Contact Us
Advertisement

Aviation Newsletter

Facebook Instagram Linkedin X-twitter Youtube