News

Civil Aviation

Pilot Training

Flight School Analysis

Aviation Jobs

Training

Services

About Us

Incidents

Chennai, India: An IndiGo Airbus A321neo operating flight 6E-723 from Kolkata to Chennai made a precautionary emergency landing at Chennai International Airport late Tuesday night, August 11, after its left engine became inoperative shortly before landing. The aircraft was carrying 224 passengers and crew members. A full emergency was declared at Chennai Airport at 11:29 p.m. IST, with emergency response teams placed on standby. The aircraft subsequently landed safely on Runway 25 at 11:37 p.m., with all 224 people on board safe and no injuries reported. The flight was scheduled to arrive at 11:30 p.m., making the actual landing seven minutes later than scheduled. According to officials from the Airports Authority of India (AAI), the aircraft reported the technical problem while approaching Chennai. The pilot noticed that the left engine had failed while preparing for landing and alerted air traffic control. Following the alert, airport authorities activated the emergency response arrangements to facilitate the aircraft's safe arrival. The emergency was formally withdrawn at 11:47 p.m., around 10 minutes after the aircraft touched down. Chennai airport authorities said normal operations continued following the incident, with no disruption to airport operations reported. The declaration of a full emergency was a precautionary measure that allowed airport fire, rescue and other emergency services to remain ready for the aircraft's arrival. The aircraft landed without an accident, and there was no reported evacuation, casualty or injury among the 224 people on board. At present, the specific technical cause of the left-engine failure has not been publicly established. The available reports describe the condition as a left-engine failure or a “left engine inoperative condition” and do not provide details about the nature of the malfunction, engine damage or whether a particular component failed. Further technical examination of the aircraft is expected to establish the cause.

IndiGo Airbus A321neo Makes Emergency Landing In Chennai After Left-Engine Failure

Aviation Today News Desk August 12, 2026

Chennai, India: An IndiGo Airbus A321neo operating flight 6E-723 from Kolkata to Chennai made a precautionary emergency landing at Chennai International

Myrtle Beach, United States: American Airlines Flight 1760, a Boeing 737-800 operating from Myrtle Beach International Airport in South Carolina to Charlotte Douglas International Airport in North Carolina, made an emergency return to Myrtle Beach on Monday, August 10, after reportedly striking a flock of birds shortly after takeoff and experiencing an engine malfunction. The aircraft took off from Myrtle Beach at about 8:11 a.m. local time and was only minutes into the flight when the crew reported the problem to air traffic control. According to air traffic recordings obtained through LiveATC.net, the pilot declared a Mayday, saying, “Mayday, mayday, mayday. We’ve got an engine problem here.” The crew subsequently reported an engine malfunction as the aircraft turned back toward Myrtle Beach. Reports indicate the aircraft had struck birds during its climb, with another pilot who witnessed the event telling air traffic control, “I saw he took up birds, it looked like, at least in the left side engine.” The reported bird ingestion involved the aircraft’s left engine, beneath the left wing. Passengers recorded video showing bright orange flames and sparks appearing from the left side of the aircraft beneath the wing. Passenger Patrick Gotwalt captured footage of the event, while witnesses on the ground also reported hearing several loud popping sounds and seeing orange flashes from the aircraft’s left side. Lindsey Mackey, who was on the ground near the beach, told CNN that she heard loud popping noises before noticing orange flashes coming from the aircraft’s left wing. The visual evidence showed what appeared to be flames or sparks coming from the area around the left engine as the aircraft continued flying back toward the airport. As the Boeing 737-800 returned, airport emergency personnel prepared for its arrival. Workers subsequently found substantial bird remains and debris on the runway. Radio communications from the airport included the statement, “We’ve got a lot of bird debris out here. We’re going to grab as many big pieces as we can.” The debris provided physical evidence consistent with reports that the aircraft had struck birds. Flight 1760 landed safely back at Myrtle Beach at approximately 8:40 a.m., after spending roughly 15 minutes in the air, according to reports. The aircraft taxied to the gate under its own power, allowing passengers to disembark normally. No injuries were reported. The flight was carrying 172 passengers/customers and nine crew members, according to the New York Post, although the airline's statement cited by The U.S. Sun referred specifically to the 172 customers aboard. American Airlines said the aircraft was removed from service for a maintenance inspection following the incident. In a statement, the airline said, “The aircraft landed safely and has been taken out of service to be inspected by our maintenance team.” The airline added, “Our team worked to get customers on their way to Charlotte (CLT) on a replacement aircraft.” American also thanked its employees for their professionalism and passengers for their understanding. The aircraft was therefore not continued to Charlotte after the emergency landing. American arranged a replacement aircraft so the affected passengers could continue their journey to Charlotte. Although video footage showed flames coming from the left engine area, the New York Post reported that there was no internal engine fire, indicating that the visible flames did not necessarily represent a sustained fire inside the engine. The aircraft was nevertheless removed from service for inspection. The Federal Aviation Administration confirmed that the aircraft landed at Myrtle Beach at about 8:40 a.m. and said it would investigate the incident. The investigation is expected to establish the precise nature of the engine malfunction and assess the bird-strike evidence. The bird remains recovered after the incident are also significant because wildlife remains from aircraft strikes can be examined to determine the species involved. The FAA's Smithsonian Feather Identification Lab program routinely analyzes bird remains from aircraft strikes to help identify the species and improve airport wildlife-management measures.

American Airlines Flight 1760 Makes Emergency Landing After Bird Strike Damages Engine

Aviation Today News Desk August 12, 2026

Myrtle Beach, United States: American Airlines Flight 1760, a Boeing 737-800 operating from Myrtle Beach International Airport in South Carolina to

SWISS A330 Diverts To Dublin After Smoke From Power Bank Reported Over Atlantic Flight

Aviation Today News Desk August 11, 2026

Dublin, Ireland: A SWISS Airbus A330-300 operating flight LX52 from Zurich to Boston was diverted to Dublin after smoke was reported

Baramati, India: A Cessna 172S training aircraft operated by Academy of Carver Aviation Pvt. Ltd. veered off the runway during a training exercise at Baramati Airfield in Maharashtra’s Pune district on Sunday, August 9, 2026. The aircraft, registered VT-SEX, had two people onboard flight instructor Captain Chirag Shashikant Doifode and cadet Abhijeet Jundre. Both escaped unharmed. The incident occurred at about 12:30 pm. The four-seat aircraft was conducting a Circuit and Landing Emergencies training exercise, during which the trainee was required to practise landing following an emergency scenario. Police and aviation authorities said the aircraft was involved in rejected-take-off exercises as part of the training sequence. According to the Ministry of Civil Aviation, the DGCA-approved Academy of Carver Aviation aircraft “suffered a runway excursion at Baramati Airfield.” The ministry said the aircraft “was involved in a Circuit and Landing Emergencies (CL Emergencies) training exercise” and was unable to stop within the paved runway surface before veering onto the extended paved area beyond the runway threshold. A DGCA Air Safety team was sent to the site to conduct a preliminary investigation. Police said the aircraft initially entered the runway through Link Bravo and lined up at the threshold of Runway 29, where it carried out a rejected take-off exercise. It was subsequently positioned at the threshold of Runway 11 for another rejected take-off exercise. During the sequence, the aircraft could not be brought to a complete stop and continued beyond the runway before veering onto the grassy area. Police said the aircraft travelled roughly 20 feet beyond the runway end before entering the grass. Inspector Narayan Pawar said, “The brakes of the aircraft seem to have not worked,” while adding that the situation was under control. Pune Rural Deputy Superintendent of Police Chaitanya Kadam confirmed that both occupants were safe. The aircraft sustained damage during the runway excursion. The Ministry of Civil Aviation said, prima facie, damage was found to the propeller, engine cowling and nose landing gear, with a detailed assessment to be conducted by the competent authorities. The cause of the incident has not yet been established. Police said investigators were examining whether the aircraft developed a technical problem or whether another factor contributed to the runway excursion. A senior police official said, “It is too early to comment on anything,” as the investigation was still at an early stage. Pune Rural Superintendent of Police Sandip Singh Gill said the aircraft skidded while landing. In a statement reported by Economic Times, Gill said: “An aircraft VT-SEX was involved in a runway excursion incident at Baramati Airfield during a training exercise, with Capt Chirag Shashikant Doifode and Cadet Abhijeet Jundre on board. No injuries have been reported.” The aircraft involved was a Cessna 172S, a four-seat single-engine trainer. The DGCA’s list of approved flying training organisations as of March 30, 2026, lists VT-SEX as a Cessna 172S operated by Academy of Carver Aviation Pvt. Ltd., whose flying base is near Baramati Airport. Carver Aviation’s own fleet information also lists VT-SEX among its training aircraft. There was therefore no injury to the cadet, no injury to the instructor and no fatality in the August 9 incident. The aircraft was not carrying passengers beyond the two flight-training occupants, and the incident occurred during a scheduled training exercise rather than a passenger operation. The incident has nevertheless renewed scrutiny of safety conditions at Baramati. Hindustan Times described it as the seventh aircraft accident or incident linked to Baramati’s aviation and flight-training operations since 2022, prompting calls for a broader review of infrastructure, operational systems and oversight. Aviation expert Dhairyashil Vandekar said the latest incident should trigger a comprehensive review of the airfield. “It is important that the safety and confidence of trainee pilots must be paramount,” Vandekar said, adding that Baramati’s infrastructure and operational systems need to keep pace with the volume of flying activity. He called for appropriate air traffic services, modern navigation and communication systems and stronger emergency-response infrastructure. The DGCA is now examining the circumstances and contributing factors behind the August 9 runway excursion. At present, authorities have not attributed the incident to a confirmed brake failure, mechanical defect, pilot error or any other specific cause. The investigation is expected to establish what led the Cessna 172S to leave the paved runway during the training exercise.

Cessna 172S Suffers Runway Excursion At Baramati During Training, 2 Escape Unhurt

Aviation Today News Desk August 10, 2026

Baramati, India: A Cessna 172S training aircraft operated by Academy of Carver Aviation Pvt. Ltd. veered off the runway during a

Atlanta, United States: Delta Air Lines Flight 2204 returned to Hartsfield-Jackson Atlanta International Airport on August 8 after fumes were reported in the flight deck shortly after departure, prompting an emergency landing and evacuation on the taxiway. The Boeing 757-200 was operating from Atlanta to Orlando International Airport in Florida when the flight crew detected the fumes and followed procedures to return to Atlanta. According to the Federal Aviation Administration, the aircraft landed safely at about 8 a.m. local time. The aircraft was carrying approximately 200 passengers and six crew members. After landing, passengers were evacuated using the aircraft’s emergency slides onto the taxiway rather than remaining onboard. Video shared by a passenger on TikTok showed passengers moving toward the exits and sliding onto the tarmac, while crew members could be heard directing them to leave their belongings behind and evacuate. A passenger, Jordan Conlin, who was traveling with his family, told Fox 5 Atlanta that the pilot announced that he and the co-pilot were wearing oxygen masks because of fumes in the cockpit and that the aircraft was turning back to Atlanta. Conlin also recalled the pilot instructing passengers to “brace” during the landing, describing the evacuation as chaotic as passengers left the aircraft. One crew member and one passenger received medical attention following the incident, while the remaining passengers were transported by ground crews to the terminal. Delta subsequently arranged a replacement aircraft to take the passengers to Orlando. Delta confirmed that the crew followed established procedures after reports of fumes in the flight deck and said a slide evacuation took place on a taxiway. The airline apologized to passengers, saying safety remained its top priority. The FAA said it is investigating the incident. The agency confirmed that Flight 2204 returned safely to Atlanta after reported smoke in the cockpit and that passengers evacuated via emergency slides onto the taxiway. The aircraft was taken for inspection following the incident. No fatalities were reported, and the available reports indicate that the aircraft landed safely before the evacuation was carried out. The precise source of the fumes or smoke has not been established publicly. The FAA investigation and aircraft inspection are expected to provide further information about what caused the reported condition in the flight deck.

Delta Flight 2204 Makes Emergency Return To Atlanta After Fumes Reported In Cockpit

Aviation Today News Desk August 10, 2026

Atlanta, United States: Delta Air Lines Flight 2204 returned to Hartsfield-Jackson Atlanta International Airport on August 8 after fumes were reported

Sydney, Australia: A Jetstar Airbus A320 and a Qatar Airways Boeing 777 came dangerously close to a collision while moving on the ground at Sydney Airport on Sunday morning, August 9, after the Jetstar crew was forced to brake abruptly to avoid the Qatar aircraft. The incident occurred at about 7:00am local time at Sydney Kingsford Smith Airport. The Jetstar A320, operating flight JQ402 from Sydney to Gold Coast Airport, was taxiing for departure when its crew observed the Qatar Airways Boeing 777 being towed by an aircraft tug on a crossing taxiway. The ATSB said both aircraft were brought to an abrupt stop, preventing a collision. According to Australian media reports, the Jetstar aircraft stopped about 50 metres from the Qatar 777. The sudden braking caused a rear cabin crew member aboard the Jetstar aircraft to fall and suffer a broken wrist. No Jetstar passengers were injured. JQ402 was carrying 151 passengers and six crew members, according to Australian media reports. The flight was subsequently cancelled and passengers were rebooked onto later services. The Qatar Boeing 777 was not operating a passenger departure at the time. It had arrived at Sydney from Doha and was being repositioned under tow after passengers had disembarked. The aircraft therefore had no passengers onboard during the near-collision. The precise sequence that brought the two aircraft into such close proximity remains under investigation. Jetstar said its aircraft was following air traffic control instructions when its pilots were forced to brake firmly after another aircraft came into close proximity. The airline has also begun its own investigation. The ATSB said there was damage to the connection between the Qatar 777's nose landing gear and the aircraft tug. Investigators will examine data from both aircraft and air traffic control, while interviewing the flight crew, tug operators, air traffic controllers and other witnesses. CCTV and other recorded information will also be reviewed. ATSB Chief Commissioner Angus Mitchell said it was too early to determine where the communication or coordination breakdown occurred. Investigators will establish what instructions were issued, how they were understood and why the aircraft came so close before the final stop. The incident has also drawn attention to air traffic-control staffing pressures at Sydney Airport. ABC reported that air traffic control was operating under restrictions between 6:00am and 8:00am on Sunday, limiting the number of aircraft moving through the airport. More than 150 flights had also been affected by roster constraints in the days leading up to the incident. However, there is currently no official finding that the staffing situation caused the near-collision. The ATSB investigation will determine whether communication, coordination, ground movements, procedures or other factors contributed. Two people involved in the ground operation, an air traffic ground controller and the tug operator were stood down for mandatory drug and alcohol testing, which the federal transport minister described as standard post-incident procedure. Their stand-down should not be interpreted as a finding of fault. The ATSB has asked anyone with video of Sunday's incident or its immediate aftermath to provide footage to investigators. The investigation remains ongoing.

Jetstar A320 And Qatar 777 Narrowly Avoid Collision During Taxiing At Sydney Airport

Aviation Today News Desk August 10, 2026

Sydney, Australia: A Jetstar Airbus A320 and a Qatar Airways Boeing 777 came dangerously close to a collision while moving on

California, United States: A United Airlines Boeing 737-800 operating Flight 1189 from San Francisco to Los Cabos, Mexico, returned to San Francisco International Airport (SFO) on Thursday after one of its tires was damaged during the takeoff roll, prompting the aircraft to turn back shortly after departure. Few media, citing air traffic control audio, reported that the tire burst during the takeoff roll, while United officially described the incident as damage to one tire. Flight-tracking data showed the aircraft turning back after roughly an hour in flight before landing safely at SFO at about 11:44 a.m. The aircraft was a Boeing 737-800 carrying 165 passengers and eight crew members. Despite the reported tire damage during departure, the aircraft completed the return flight and landed safely at its departure airport. United said there were no reported injuries among those onboard. United Airlines confirmed the incident in a statement, saying, “United flight 1189 sustained damage to one tire while departing San Francisco and safely returned to the airport.” The airline did not specify whether the tire failure was caused by a mechanical defect, debris, wear or another factor, and it did not identify the exact tire involved. Passengers were not taken directly into the terminal after landing. Instead, United said customers “deplaned via airstairs on the tarmac and were taken by bus to the terminal.” The procedure followed the aircraft’s return to SFO while the aircraft and the damaged tire were being inspected. United said it arranged another aircraft to continue the passengers’ journey to Los Cabos later that afternoon, stating, “We've arranged for a different aircraft to take them to Los Cabos later this afternoon.” This allowed the affected passengers to continue their original trip after the Boeing 737-800 was taken out of service for inspection. The incident also affected airport operations, the blocked runway caused delays to some other flights at SFO. There was no reported crash or emergency landing accident, but the circumstances surrounding the tire damage remain under review. The Federal Aviation Administration has said it will investigate the incident. As of the latest available update there are no further FAA findings and official cause has not been released.

United Flight 1189 Returns To SFO After Tire Damage During Takeoff, FAA Probes

Aviation Today News Desk August 7, 2026

California, United States: A United Airlines Boeing 737-800 operating Flight 1189 from San Francisco to Los Cabos, Mexico, returned to San

Sydney, Australia: The Australian Transport Safety Bureau (ATSB) has launched an investigation into a serious runway incursion involving two Qantas-operated aircraft at Sydney Airport after an air traffic control clearance resulted in one aircraft being instructed to cross an active runway while another was still landing. The incident occurred on 27 July 2026 at approximately 08:14 local time, and although no collision occurred, the safety watchdog has classified it as a breakdown in coordination and opened a formal investigation. According to the ATSB, the occurrence involved Qantas Flight QF124, a Boeing 737-800 registered VH-XZG, which had arrived from Queenstown, New Zealand, and QantasLink Flight QLK424D, a De Havilland Canada Dash 8 Q400 registered VH-QOC, arriving from Canberra, Australian Capital Territory. Preliminary information released by the ATSB states that after landing on Runway 25, the Boeing 737 was instructed by air traffic control to taxi and cross Runway 34L. At the same time, the Dash 8 Q400 had been cleared to land on Runway 34L and was still completing its landing roll along the active runway. As the Boeing approached the runway crossing point, air traffic controllers recognised the developing conflict. The ATSB said the 737 crew stopped the aircraft before entering Runway 34L, while the Dash 8 continued its landing roll on the runway. Because the Boeing halted short of the runway, the two aircraft remained separated and no collision occurred. No injuries or aircraft damage were reported, and both aircraft subsequently continued normal ground operations. The ATSB has not released the number of passengers or crew on board either flight. The safety bureau has opened investigation AO-2026-086 to determine the factors that led to the runway incursion. Investigators will examine the sequence of air traffic control clearances, coordination between controllers, recorded radio communications, surveillance data, aircraft movements, human factors and operational procedures. The investigation will also assess whether any broader systemic issues contributed to the occurrence. In its initial investigation notice, the ATSB described the event as involving a breakdown of coordination between aircraft movements on intersecting runways. The agency noted that evidence collection is underway, including interviews with relevant personnel and analysis of operational data. A final report is expected before the end of 2026, although the timeline may change depending on investigative findings. The incident has renewed attention on staffing pressures within Australia's air traffic control system. Recent media reports have highlighted controller shortages and increased workload at Sydney Airport, with industry representatives raising concerns over staffing levels. Airservices Australia has acknowledged workforce challenges and said it is recruiting and training additional controllers, while noting that qualification training takes several years before recruits can work independently in complex airspace. Airservices Australia confirmed it is cooperating fully with the ATSB investigation and said safety remains its highest priority. The organisation has not provided further comment while the independent investigation is ongoing. Qantas also confirmed it is assisting the ATSB and stated that both flight crews were operating in accordance with air traffic control instructions issued during the event.

ATSB Investigates Runway Incursion Involving Two Qantas Aircraft At Sydney Airport

Aviation Today News Desk August 5, 2026

Sydney, Australia: The Australian Transport Safety Bureau (ATSB) has launched an investigation into a serious runway incursion involving two Qantas-operated aircraft

Kenya Airways Boeing 737-800 Suffers Tyre Burst After Landing At Cape Town

Aviation Today News Desk August 5, 2026

Cape Town, South Africa: A Kenya Airways Boeing 737-800 suffered a tyre burst after landing at Cape Town International Airport in

New Delhi, India: An Air India Airbus A320 operating flight AI2379 from Phuket, Thailand, to New Delhi encountered severe turbulence on Tuesday, August 4, leaving several passengers and cabin crew with minor injuries before the aircraft landed safely at Indira Gandhi International Airport (DEL). The incident occurred during the flight's final phase, although reports differ on the exact timing. While early media reports said the turbulence struck during the aircraft's descent into Delhi, Air India later clarified that the aircraft encountered turbulence while in cruise, resulting in a brief change in altitude. The Airbus A320, carrying 134 passengers, landed safely shortly after 11:00 a.m. IST. All passengers and crew disembarked normally after arrival, with Air India's airport and medical teams meeting the aircraft at the gate. According to PTI, 12 people, including passengers and cabin crew, sustained minor injuries during the turbulence event. Other reports indicated that around 10 passengers and two cabin crew members were taken to the Medanta medical facility at Delhi Airport for precautionary medical assessment. Seven passengers were later moved to Fortis Hospital in Vasant Kunj for further evaluation, scans, and observation. Air India said there were no serious injuries. Some early reports stated the aircraft experienced a sudden altitude drop of approximately 300 feet during the turbulence, causing unrestrained occupants to be thrown against the cabin interior and resulting in minor injuries. Air India, however, described the event as a "momentary change in altitude" without confirming the reported altitude deviation. Speaking to news agency ANI, a passenger on board the flight claimed the aircraft experienced a sudden jolt about an hour and a half into the journey while most passengers were asleep. According to the passenger, the aircraft abruptly dropped and swayed violently for nearly two to three minutes, leaving several people injured. In an official statement, Air India said, "The safety and well-being of our passengers and crew remain Air India's highest priority." The airline added that a small number of passengers and crew members requiring medical assessment were taken to the airport medical facility as a precaution and confirmed that it is providing all necessary assistance while cooperating with the relevant authorities reviewing the incident.

Air India AI2379 Hits Severe Turbulence; 12 Injured Before Safe Landing In Delhi

Aviation Today News Desk August 4, 2026

Update 05 August, 2026: Air India has since confirmed that flight AI2379 experienced a sudden loss of altitude during cruise before

Incidents

IndiGo Airbus A321neo Makes Emergency Landing In Chennai After Left-Engine Failure

American Airlines Flight 1760 Makes Emergency Landing After Bird Strike Damages Engine

SWISS A330 Diverts To Dublin After Smoke From Power Bank Reported Over Atlantic Flight

Cessna 172S Suffers Runway Excursion At Baramati During Training, 2 Escape Unhurt

Delta Flight 2204 Makes Emergency Return To Atlanta After Fumes Reported In Cockpit

Jetstar A320 And Qatar 777 Narrowly Avoid Collision During Taxiing At Sydney Airport

United Flight 1189 Returns To SFO After Tire Damage During Takeoff, FAA Probes

ATSB Investigates Runway Incursion Involving Two Qantas Aircraft At Sydney Airport

Kenya Airways Boeing 737-800 Suffers Tyre Burst After Landing At Cape Town

Air India AI2379 Hits Severe Turbulence; 12 Injured Before Safe Landing In Delhi

Quick Links

Navigate

General Support

News Desk Support