passenger flight Archives - Aviation Today

South Carolina, United States: A Southwest Airlines Boeing 737-800 operating Flight WN4761 from Orlando International Airport (MCO) to Manchester-Boston Regional Airport (MHT) diverted to Charleston International Airport (CHS) on Monday, July 20, after the flight crew detected indications of a suspected fuel leak while cruising over South Carolina. No injuries were reported among the passengers or crew. Flight WN4761 departed Orlando International Airport at 8:54 a.m. ET from Terminal A, Gate 125, on a scheduled nonstop service to Manchester, New Hampshire. The aircraft climbed normally for approximately one hour before reaching a cruising altitude of 37,000 feet over South Carolina. The aircraft involved was an 11-year-old Boeing 737-8H4, registered as N8662F. While the aircraft was at cruise altitude, the crew identified indications of a possible fuel leak and declared an emergency by transmitting the 7700 transponder code. The code is the internationally recognized general emergency squawk used by flight crews to alert air traffic control that an aircraft requires immediate priority handling. Following the emergency declaration, air traffic control cleared the aircraft for an expedited descent and arranged for the flight to divert to Charleston International Airport. The Boeing 737-800 subsequently landed safely on Runway 15, with emergency response vehicles standing by as a precaution. No injuries were reported among those onboard. The precise nature of the fuel leak indication remains unclear. It has not been established whether the aircraft experienced an actual structural or mechanical fuel leak or whether the warning resulted from a sensor or valve-related anomaly. The aircraft remained at Charleston after the diversion, where maintenance personnel began a detailed inspection to determine the root cause of the suspected fuel leak indication. Southwest Airlines had not publicly disclosed the cause of the issue or confirmed when the Boeing 737-800, N8662F, would return to service at the time of the report. Southwest arranged a replacement aircraft to continue the disrupted service. A newer Boeing 737 MAX 8, registered as N8881L, was dispatched to Charleston to transport the affected passengers to Manchester-Boston Regional Airport. Passengers reportedly waited approximately four hours on the ground before boarding the replacement aircraft. The flight eventually continued to Manchester, arriving about five hours later than its originally scheduled arrival time of 11:50 a.m. ET.

Southwest Boeing 737-800 Diverts To Charleston After Suspected Fuel Leak Mid-Air

Aviation Today News Desk / July 21, 2026

South Carolina, United States: A Southwest Airlines Boeing 737-800 operating Flight WN4761 from Orlando International Airport (MCO) to Manchester-Boston Regional […]

Montevideo, Uruguay: A LATAM Airlines Chile Airbus A320 safely returned to Montevideo, Uruguay, after suffering an apparent engine malfunction shortly after departure on Thursday, July 2, forcing the crew to discontinue the climb and conduct a precautionary landing. The aircraft, operating Flight LA2399 from Carrasco International Airport (MVD), Montevideo, to Jorge Chávez International Airport (LIM), Lima, Peru, had just departed Runway 25 when the aircraft's right CFM56 engine reportedly began emitting flames shortly after becoming airborne. According to aviation incident reports, the flight crew halted the climb at approximately 3,000 feet, entered a holding pattern to complete the required emergency procedures, and subsequently returned to Montevideo. The Airbus A320-200 landed safely on Runway 25 about 90 minutes after takeoff. The aircraft involved was an Airbus A320-200, registered CC-BLE, operated by LATAM Airlines Chile. Uruguay's Air Force confirmed that the aircraft experienced a malfunction in one of its engines. Videos circulating on social media showed flames and sparks from the right engine during the initial climb, although authorities have not confirmed the exact cause of the malfunction. Some eyewitness accounts suggested the possibility of a bird strike, but no official investigation has attributed the incident to bird ingestion. Following the safe landing, the scheduled flight to Lima was cancelled, and the aircraft remained grounded in Montevideo for technical inspections. The cause of the engine malfunction remains under investigation

Incidents

LATAM Airbus A320 Returns Safely To Montevideo After Engine Malfunction During Takeoff

Aviation Today News Desk / July 4, 2026

Montevideo, Uruguay: A LATAM Airlines Chile Airbus A320 safely returned to Montevideo, Uruguay, after suffering an apparent engine malfunction shortly

Kuala Lumpur, Malaysia: A Singapore Airlines (SIA) flight from Kuala Lumpur to Singapore was delayed by nearly six hours on June 21 after the aircraft operating an earlier sector suffered a tyre-related incident upon arrival in Malaysia, marking the second such occurrence involving the same route this month. According to Singapore Airlines, two tyres on a Boeing 737-8 operating Flight SQ114 from Singapore to Kuala Lumpur deflated after landing at Kuala Lumpur International Airport (KLIA) on June 21. The incident occurred after the aircraft had completed its arrival into Kuala Lumpur. There were no reports of injuries. Because the aircraft could not continue normal operations, it was towed to a remote parking bay. All 152 passengers and eight crew members onboard SQ114 disembarked via buses and were transported to the terminal. The affected aircraft had been scheduled to operate the return service, Flight SQ113, from Kuala Lumpur to Singapore later the same day. However, the tyre damage rendered the aircraft unavailable, forcing Singapore Airlines to dispatch a replacement aircraft from Singapore. As a result, SQ113, carrying 143 passengers and eight crew members, departed Kuala Lumpur at 8:27 p.m. local time instead of its scheduled 2:35 p.m. departure. The flight subsequently arrived in Singapore at 9:38 p.m. Passengers received multiple delay notifications throughout the afternoon. According to reports, the airline initially advised travelers that the departure had been postponed until 4:35 p.m. due to technical issues affecting the incoming aircraft. The flight was later delayed again, with Singapore Airlines citing adverse weather conditions in Singapore for the final postponement. Affected passengers were provided with refreshments, snack packs, meal vouchers and assistance with onward travel arrangements, including rebooking of connecting flights where necessary. Singapore Airlines apologized for the disruption, stating that passenger and crew safety remains its highest priority. The airline also confirmed that the damaged tyres had been replaced and that the aircraft would return to service after the necessary maintenance actions. The June 21 occurrence follows another tyre-related incident involving the same Singapore-Kuala Lumpur service on June 13. On that occasion, Flight SQ114, also operated by a Boeing 737 MAX 8, experienced a double tyre burst during landing at KLIA at approximately 1:27 p.m. local time. The aircraft became disabled on the runway, prompting airport authorities to temporarily close one of KLIA's three runways. The affected runway remained unavailable for about six hours while emergency crews and maintenance personnel worked to clear the aircraft and inspect the pavement. Malaysia Airports later confirmed that flight operations resumed after aviation authorities completed safety checks and granted clearance for reopening. Investigations and technical assessments are expected to determine whether the tyre failures resulted from operational factors, runway conditions, foreign object debris, maintenance issues, manufacturing defects or other causes.

Incidents

Singapore Airlines Flight Delayed For Hours After Two Tyres Deflated At KLIA

Aviation Today News Desk / June 24, 2026

Kuala Lumpur, Malaysia: A Singapore Airlines (SIA) flight from Kuala Lumpur to Singapore was delayed by nearly six hours on

New York, United States: A Delta Air Lines Airbus A321neo landed safely at New York’s John F. Kennedy International Airport (JFK) on June 16 after reports of a possible nose-wheel tire issue prompted a large-scale emergency response from airport and city authorities. Delta Flight 1966 was operating a scheduled service from San Juan, Puerto Rico, to New York-JFK when concerns emerged regarding the aircraft’s nose landing gear during its approach into the airport. Initial reports received by emergency responders indicated that the inbound aircraft may have been experiencing issues involving its front tires, leading authorities to prepare for a potential emergency landing. According to the New York City Fire Department (FDNY), a call was received at approximately 4:45 p.m. local time reporting that the aircraft had "two flat front tires." In response, the department initiated a precautionary second-alarm standby deployment, dispatching 46 units and 141 fire and emergency medical personnel to JFK Airport. The aircraft, an Airbus A321neo operated by Delta Air Lines, was carrying 170 passengers along with six crew members, consisting of two pilots and four flight attendants. Flight tracking data shows the aircraft landed safely at JFK at approximately 5:31 p.m. local time. Emergency vehicles were positioned alongside the runway as a precaution while the aircraft completed its landing. Following touchdown, the aircraft remained under observation before being cleared to continue taxiing to the terminal. The aircraft was subsequently escorted to Terminal 4, where it arrived without incident. No injuries were reported among passengers or crew. Following the landing, Delta Air Lines clarified that the situation was less severe than initially reported. The airline stated that maintenance inspections identified damage and tread wear to one tire rather than multiple flat or blown tires. "There was some damage to one tire, but not a major situation given the maintenance team determined the aircraft was suitable to continue taxiing over to the gate for the tire replacement rather than having to do so on the taxiway," Delta said in a statement. The airline added that the aircraft was able to taxi under its own power and that the emergency response proved largely precautionary. Video footage captured by local news helicopters after the landing appeared to show the aircraft’s nose-wheel tires still inflated, further supporting Delta’s assessment that the tire had sustained damage rather than a complete failure. No evacuation was required, and passengers disembarked normally after arrival. Delta has not indicated any further operational impact resulting from the incident. The circumstances surrounding the tire damage have not been publicly disclosed, and there has been no indication of any broader safety issue involving the aircraft.

Incidents

Delta Lands Safely At JFK After Tire Damage Report Triggers Major Emergency Response

Aviation Today News Desk / June 18, 2026

New York, United States: A Delta Air Lines Airbus A321neo landed safely at New York’s John F. Kennedy International Airport

Copenhagen, Denmark: Scandinavian Airlines' long-awaited return to India after a 17-year absence suffered an unexpected setback when its inaugural Copenhagen–Mumbai service was forced to return to Denmark after spending nearly four hours in the air due to a pending regulatory approval. Flight SK969, operated by an Airbus A330-300, departed Copenhagen Airport on June 2, 2026, for what was intended to be the carrier's first scheduled service to India since 2009. However, the aircraft left approximately four to four-and-a-half hours behind schedule before beginning its journey toward Mumbai. According to flight-tracking data, the aircraft continued southeast across Europe and into the Caucasus region before reversing course while over Azerbaijan. After remaining airborne for roughly four hours, the aircraft returned to Copenhagen, turning the launch flight into what several aviation observers described as an "eight-hour flight to nowhere." SAS confirmed that the aircraft returned because a final regulatory approval required for the service had not been received as anticipated. "The flight returned to Copenhagen because the final approval from the relevant authorities was not issued as expected," the airline said. The carrier indicated that it had completed months of preparations for the route and had expected the remaining authorization to be finalized before the flight reached Indian airspace. However, that approval had not been secured by the time the aircraft was approaching the latter stages of its journey toward India. Neither SAS nor Indian regulators have publicly identified the specific authorization that remained outstanding. As a result, the exact nature of the missing clearance remains unclear. The incident overshadowed what had been planned as a significant milestone for the Scandinavian carrier. The Copenhagen-Mumbai route marks SAS's first India service in 17 years and forms part of the airline's broader strategy to expand its long-haul network following its transition into the SkyTeam alliance. SAS had positioned Mumbai as a key destination linking Scandinavia with one of the world's fastest-growing aviation markets. The airline had planned to operate the route five times weekly using Airbus A330 aircraft, strengthening connections between Northern Europe, India and North America through its Copenhagen hub. The route also represented SAS's return to a market it exited in 2009 during a period of restructuring and changing long-haul economics. Passengers onboard the inaugural service ultimately returned to Copenhagen instead of reaching Mumbai, creating significant disruption for travelers who had boarded what was expected to be a historic relaunch flight. Following the incident, reports indicated that SAS temporarily suspended subsequent Mumbai services while working with authorities to resolve the approval issue. The airline stated that it was actively engaged with regulators and expected operations to begin once all necessary authorizations were secured. As of the latest updates, SAS continues to work toward obtaining the remaining clearance required to fully launch the service, though neither the airline nor authorities have announced a definitive timeline for regular operations to commence.

Incidents

SAS’ First India Service In 17 Years Turns Back Mid-Air Over Pending Regulatory Approval

Aviation Today News Desk / June 6, 2026

Copenhagen, Denmark: Scandinavian Airlines’ long-awaited return to India after a 17-year absence suffered an unexpected setback when its inaugural Copenhagen–Mumbai

Detroit, United States: A Delta Air Lines Connection flight operating from Madison, Wisconsin, to Detroit, Michigan, declared a medical emergency after the co-pilot briefly lost consciousness during the aircraft’s approach and landing phase, according to airline statements and air traffic control (ATC) communications. The incident occurred on May 23, 2026, aboard a flight operated by Endeavor Air, a wholly owned regional subsidiary of Delta Air Lines. The aircraft departed from Dane County Regional Airport and was arriving at Detroit Metropolitan Wayne County Airport when the emergency unfolded. According to ATC audio, the captain informed controllers that the first officer had become incapacitated during the approach. In the transmission, the captain stated: “Declaring a medical emergency, my first officer’s incapacitated.” Air traffic controllers subsequently cleared the aircraft for priority landing. The aircraft landed safely in Detroit without further incident. Delta confirmed that paramedics met the flight after it taxied to the gate and that the first officer had regained consciousness by the time emergency personnel boarded the aircraft. The co-pilot was then transported to a hospital for medical evaluation. Flight tracking data indicated the flight completed the journey in approximately one hour and arrived around 20 minutes ahead of schedule despite the emergency declaration. No passengers or cabin crew members were reported injured during the incident. In a statement, Delta said safety remained its highest priority and praised the crew’s handling of the situation. The airline stated that the professionalism of the Endeavor Air crew and the response of emergency personnel helped ensure the flight concluded safely. The airline did not disclose the medical cause behind the co-pilot’s temporary loss of consciousness. There was also no indication of any technical or mechanical issue involving the aircraft itself. The incident also came days after another unrelated pilot medical emergency involving a Jet2.com flight traveling from Tenerife, Spain, to Birmingham, United Kingdom, which diverted to Porto, Portugal, after one of the pilots reportedly became unwell mid-flight.

Incidents

Delta Connection Flight Declares Emergency After Co-Pilot Loses Consciousness During Landing

Aviation Today News Desk / May 27, 2026

Detroit, United States: A Delta Air Lines Connection flight operating from Madison, Wisconsin, to Detroit, Michigan, declared a medical emergency

Tokyo, Japan: A Skymark Airlines Boeing 737 operating a domestic flight from Tokyo’s Haneda Airport to Fukuoka made an emergency return on Monday after the crew detected a landing gear tire abnormality mid-flight, later confirmed to involve a ruptured tire, according to Japan’s transport ministry and airline officials. The aircraft, carrying 169 passengers and crew, departed Haneda shortly after 3 p.m. local time and proceeded normally for nearly two hours before the flight crew identified a technical issue related to the landing gear system. Following standard safety procedures, the pilots declared an emergency and initiated a precautionary return to Haneda Airport. The aircraft landed safely back at Haneda without any injuries reported among passengers or crew members. The airline confirmed that all onboard remained safe throughout the incident and that the situation was handled in line with established emergency protocols. After landing, inspections conducted by airport authorities and Japan’s Ministry of Land, Infrastructure, Transport and Tourism confirmed that one of the aircraft’s tires had ruptured. Officials have not yet determined whether the damage occurred during takeoff, in-flight, or during landing gear operation after departure. Following the emergency landing, Haneda Airport temporarily closed Runway C to conduct safety inspections and remove any possible debris or rubber residue. The runway was later reopened at around 7:40 p.m. local time after checks confirmed safe operating conditions and no structural damage. Skymark Airlines operates a major domestic network from Haneda, connecting key cities across Japan, including Fukuoka, Sapporo, and Okinawa. The airline has not reported any further operational disruptions related to the incident, though the aircraft will undergo a detailed technical inspection before returning to service. Authorities are continuing to review the cause of the tire rupture as part of standard post-incident safety procedures.

Incidents

Skymark Boeing 737 Makes Emergency Return To Haneda After Tire Rupture

Aviation Today News Desk / May 26, 2026

Tokyo, Japan: A Skymark Airlines Boeing 737 operating a domestic flight from Tokyo’s Haneda Airport to Fukuoka made an emergency

Incidents

Etihad Airways Flight To London Returns To Abu Dhabi After Mid-Air Technical Issue

Aviation Today News Desk / May 21, 2026

Abu Dhabi, United Arab Emirates: Etihad Airways flight EY061 from Abu Dhabi to London Heathrow was forced to return to

Bhopal, India: An Air India flight operating from Mumbai to Bhopal executed a precautionary “priority” landing at Bhopal’s Raja Bhoj Airport on Sunday after the crew detected a technical issue mid-air, prompting the activation of full emergency protocols. The flight, identified as AI633, was carrying 175 persons onboard, including 166 passengers and nine crew members, according to airport officials. The aircraft landed safely at approximately 3:20 PM, with no injuries reported among passengers or crew. According to official statements, the flight crew reported a technical issue to Air Traffic Control (ATC) while en route from Mumbai. In line with standard operating procedures, the pilots opted for a precautionary landing to ensure safety. Airport authorities immediately activated prescribed safety protocols, with coordinated response from ATC, airline ground staff, the Central Industrial Security Force (CISF), and airport fire and rescue services. This ensured a controlled and incident-free landing. Following the landing, technical teams inspected the aircraft and subsequently declared it unserviceable, pending further checks and rectification of the fault. The airline confirmed that the aircraft would undergo detailed inspection before returning to service. Air India stated that the crew’s decision to land was taken “as per standard operating procedure” after detecting the issue mid-flight, reinforcing that safety remained the top priority. As a precautionary measure, the airline cancelled the return leg (AI634) from Bhopal to Mumbai, which had 178 passengers booked. Passengers onboard the affected flight were safely deplaned, and alternative travel arrangements were initiated by the airline. Some reports noted tense moments during the flight, though the situation remained under control throughout. Authorities confirmed that no injuries or untoward incidents occurred, and the situation was handled in accordance with established aviation safety procedures. The exact nature of the technical fault has not yet been disclosed, and further investigation or engineering assessment is expected.

Incidents

Air India Flight Makes Precautionary Landing In Bhopal After Mid-Air Technical Snag

Aviation Today News Desk / April 27, 2026

Bhopal, India: An Air India flight operating from Mumbai to Bhopal executed a precautionary “priority” landing at Bhopal’s Raja Bhoj

Valletta, Malta: A KM Malta Airlines flight bound for Paris was forced to return to Malta shortly after departure due to a cockpit crew planning error that breached internal training requirements, according to airline statements. Flight KM478, operating from Malta International Airport to Paris Charles de Gaulle, departed as scheduled early in the morning but turned back less than 30 minutes into the journey after the captain identified a discrepancy in crew composition. The aircraft was being operated with a trainee co-pilot (cadet) who, under aviation regulations and company procedures, must be supervised by a qualified training captain. However, the assigned captain on the flight was not certified as an instructor, rendering the operation non-compliant with internal and regulatory training standards. The issue came to light shortly after departure, as the aircraft approached airspace near Sicily. Upon identifying the irregularity, the captain decided to discontinue the flight and return to Malta as a precautionary measure. Flight tracking data shows the aircraft deviating from its planned route, looping near the Sicilian coast before heading back. The flight then entered a holding pattern to burn fuel and reduce landing weight before safely landing at Malta International Airport. The aircraft remained airborne for approximately 90 minutes, including the time spent circling prior to landing. The airline emphasized that the return was a procedural and precautionary decision, not driven by any technical fault or safety emergency. In statements the airline confirmed that: The aircraft was fully airworthy All crew members held valid licenses Passenger safety was never at risk The captain acted in line with the airline’s “safety-first” operational philosophy after determining that the crew configuration did not meet internal requirements. Preliminary findings indicate that the incident was caused by an administrative or rostering error, which led to the trainee pilot being paired with a regular captain instead of a training-qualified instructor. Aviation regulations require cadet pilots to operate under the supervision of specially qualified training captains during line training flights, making such pairing essential for compliance. Following the safe return, affected passengers were accommodated on a later flight operated with a compliant crew composition. The airline has apologised to passengers and launched an internal investigation to determine how the error occurred and to implement measures to prevent a recurrence.

Incidents

KM Malta Flight Bound For Paris Returns Mid-Air After Trainee Pilot Assignment Error

Aviation Today News Desk / April 21, 2026

Valletta, Malta: A KM Malta Airlines flight bound for Paris was forced to return to Malta shortly after departure due

passenger flight

Southwest Boeing 737-800 Diverts To Charleston After Suspected Fuel Leak Mid-Air

LATAM Airbus A320 Returns Safely To Montevideo After Engine Malfunction During Takeoff

Singapore Airlines Flight Delayed For Hours After Two Tyres Deflated At KLIA

Delta Lands Safely At JFK After Tire Damage Report Triggers Major Emergency Response

SAS’ First India Service In 17 Years Turns Back Mid-Air Over Pending Regulatory Approval

Delta Connection Flight Declares Emergency After Co-Pilot Loses Consciousness During Landing

Skymark Boeing 737 Makes Emergency Return To Haneda After Tire Rupture

Etihad Airways Flight To London Returns To Abu Dhabi After Mid-Air Technical Issue

Air India Flight Makes Precautionary Landing In Bhopal After Mid-Air Technical Snag

KM Malta Flight Bound For Paris Returns Mid-Air After Trainee Pilot Assignment Error

Follow Us

Quick Links

Navigate

General Support

News Desk Support

Follow Us