Boeing 737 Archives - Aviation Today

Austin, United States: A Southwest Airlines Boeing 737-700 operating a scheduled flight from Austin, Texas, to Phoenix, Arizona, returned to its departure airport shortly after takeoff after the flight crew reported a problem with one of the aircraft's engines. The incident occurred on June 4, 2026, involving Southwest Flight WN375. According to available flight information, the 21-year-old Boeing 737 departed Austin-Bergstrom International Airport at approximately 11:53 a.m. local time and initially climbed to about 13,000 feet while en route to Phoenix. During the climb, the pilots reported issues with the aircraft's right-hand engine and requested a return to Austin. The crew did not immediately land because weather conditions in the Austin area required the aircraft to remain airborne while awaiting a suitable opportunity to return. The aircraft descended to a lower altitude and remained in the vicinity of the airport before being cleared for approach. The Boeing 737 landed safely back at Austin approximately 40 minutes after departure. Following the landing, emergency personnel conducted an inspection of the aircraft on the runway as a precautionary measure. No fire was detected and no injuries were reported among passengers or crew. After receiving clearance from airport emergency responders, the aircraft taxied back to the terminal under its own power, where passengers disembarked normally. A subsequent inspection identified damage to the right engine. The U.S. The Federal Aviation Administration (FAA) later confirmed that investigators found "metal debris and damage to the right engine." Authorities have not disclosed the source of the debris, and the cause of the engine malfunction remains under investigation. Reports indicate that the flight crew did not receive an engine fire warning during the event, suggesting the problem may have been detected through abnormal engine indications, vibrations, performance parameters, or physical evidence rather than an onboard fire alert. The aircraft involved was a Boeing 737-700, one of the older variants in Southwest Airlines' fleet. The jet is reported to be approximately 21 years old. The FAA has opened an investigation into the occurrence. As of the latest available information, the aircraft remained out of service pending further inspection and maintenance actions. No injuries were reported

Southwest Returns To Austin After Engine Problem; FAA Finds Metal Debris In Right Engine

Aviation Today News Desk / June 6, 2026

Austin, United States: A Southwest Airlines Boeing 737-700 operating a scheduled flight from Austin, Texas, to Phoenix, Arizona, returned to […]

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

Wuzhou, China: The crash of China Eastern Airlines Flight 5735 crash continues to raise critical questions more than four years after the disaster, as newly surfaced U.S. investigative data points toward deliberate cockpit actions while Chinese authorities maintain silence, citing national security concerns. On March 21, 2022, a Boeing 737-800 operated by China Eastern Airlines plunged from cruising altitude into mountainous terrain in Guangxi, killing all 132 passengers and crew on board. The aircraft, en route from Kunming to Guangzhou, entered a near-vertical descent from approximately 29,000 feet, leaving investigators initially baffled due to the absence of distress calls or clear external triggers. Early findings released by the Civil Aviation Administration of China (CAAC) ruled out conventional causes such as mechanical failure, severe weather, or hazardous cargo. The aircraft was deemed airworthy, the crew qualified and medically fit, and no evidence of explosives was found. Flight data and cockpit voice recorders were recovered and analyzed with assistance from international agencies, including the National Transportation Safety Board (NTSB), yet interim reports issued between 2022 and 2024 stopped short of identifying a definitive cause, describing the event as “very complicated and very rare.” Attention began to shift toward possible human involvement after early assessments indicated that control inputs from the cockpit forced the aircraft into its steep descent. However, no official conclusion was publicly endorsed, and the investigation appeared to stall as updates from Chinese authorities became increasingly limited. A significant breakthrough emerged in 2026 following the release of previously undisclosed materials through a Freedom of Information Act (FOIA) request to the NTSB. According to flight data recorder analysis, both engine fuel control switches were moved to the “cutoff” position approximately 23 seconds before the recording ceased. This action resulted in an immediate loss of engine thrust, followed by autopilot disengagement and aggressive forward control inputs that drove the aircraft into a rapid descent. The loss of electrical power shortly afterward caused the recorder to stop, leaving the final moments of the flight undocumented. The cockpit voice recorder, which continued operating briefly on backup power, was successfully recovered and analyzed. However, its contents have not been made public. The NTSB confirmed that it does not retain copies of the audio, and access remains under the control of Chinese authorities, making it a crucial yet unavailable piece of evidence in determining the sequence of events inside the cockpit. While the available data suggests that the shutdown of both engines was unlikely to be accidental and is consistent with deliberate manual input, investigators have not identified which pilot may have acted or under what circumstances. The data also does not establish motive, leaving open possibilities ranging from intentional action to incapacitation or other in-flight scenarios. Reports speculating about a possible struggle in the cockpit have surfaced in some media outlets but remain unverified and are not part of any confirmed investigative findings. Despite the emergence of these critical details, the CAAC has yet to release a final accident report, well beyond the timeline prescribed under international aviation norms. Officials have indicated that disclosing further information could endanger national security or disrupt social stability, an explanation that has drawn concern from global aviation bodies and safety experts. Under standard practices, accident investigations are expected to produce a final report within one year to ensure that safety lessons are shared across the industry. The continued lack of transparency has left several fundamental questions unanswered. Without access to the cockpit voice recordings and a comprehensive official report, the exact cause of the crash remains unresolved.

Investigation

NTSB Data Suggests Possible Deliberate Engine Shutdown In MU5735 Crash That Killed 132

Aviation Today News Desk / May 6, 2026

Wuzhou, China: The crash of China Eastern Airlines Flight 5735 crash continues to raise critical questions more than four years

Las Vegas, United States: A Southwest Airlines Boeing 737 operating a domestic flight from Las Vegas to Reno was forced to return shortly after takeoff after the captain was injured when a cockpit Heads-Up Display (HUD) unit detached and struck him on the head, leading to temporary incapacitation. The incident occurred on Southwest Airlines Flight WN568, which departed from Harry Reid International Airport, Las Vegas, at approximately 2:20 pm local time on 8th April, 2026. According to multiple reports, the aircraft had just begun its departure when the HUD assembly on the captain’s side detached unexpectedly. The unit, normally fixed above eye level to project flight data such as altitude and speed, reportedly fell forward during the takeoff roll and struck the captain with significant force. The impact left the captain dazed and disoriented, with reports indicating a possible mild concussion. The First Officer immediately assumed command of the aircraft and coordinated with air traffic control. Initially, the crew requested medical priority rather than formally declaring an emergency, though ATC later classified the situation as an emergency for handling purposes. The aircraft climbed briefly to around 7,000 feet before turning back to Las Vegas. ATC communications show the First Officer reporting, “Just a little bit of a captain incapacitation here. The HUD came down and hit him on the head on the takeoff roll.” The crew requested extended vectors to allow coordination with dispatch and assistance for the injured pilot. The aircraft was guided back to Runway 26L at Harry Reid International Airport, where it landed safely without further incident. Emergency medical services were standing by upon arrival. The captain was assisted off the aircraft in a wheelchair and received immediate medical evaluation for a head injury. After the incident, Southwest Airlines arranged a replacement crew, and the aircraft was cleared for departure again after a delay of approximately 90 minutes, eventually continuing the scheduled flight to Reno.

Incidents

Southwest Airlines Pilot Incapacitated As Cockpit HUD Struck His Head During Takeoff

Aviation Today News Desk / April 23, 2026

Las Vegas, United States: A Southwest Airlines Boeing 737 operating a domestic flight from Las Vegas to Reno was forced

Pittsburgh, United States: A United Airlines flight en route from Chicago to New York was forced to make an emergency diversion to Pittsburgh after the crew detected a suspicious beeping sound mid-air and treated the situation as a potential bomb threat, triggering a full-scale security response upon landing. The incident involved United Airlines Flight 2092, a Boeing 737, operating from Chicago O’Hare International Airport to New York LaGuardia Airport. According to multiple reports and air traffic control (ATC) audio recordings published on LiveATC, the flight crew became concerned after hearing a repetitive beeping noise originating from within the aircraft. In the cockpit communication, a crew member is heard stating, “We’ve got an issue… sequential beeping… one beep per second… treat this as a potential bomb.” The sound was reportedly first noticed by flight attendants and later traced to an area beneath the floorboards near a door, raising concerns of a possible explosive device onboard. At the time, the aircraft was cruising at approximately 37,000 feet over Lake Erie, prompting the pilots to immediately declare an emergency and initiate diversion procedures. The aircraft diverted to Pittsburgh International Airport, where it landed safely at approximately 11:45 a.m. local time. Onboard were 159 passengers and six crew members (total 165 people). Following landing, authorities ordered a rapid evacuation: Passengers exited the aircraft using emergency slides onto the runway Emergency services, including fire trucks and ambulances, were positioned nearby No injuries were reported during evacuation Video footage and eyewitness accounts confirmed that the evacuation was carried out as a precaution due to the perceived immediacy of the threat. The incident triggered a coordinated response involving: FBI agents Allegheny County Police Department Bomb squad (EOD units) Explosive-detection K9 teams Authorities conducted a comprehensive sweep of the aircraft, passengers, and all baggage after isolating the aircraft. Following an extensive inspection, officials confirmed that no explosive device or threat was found onboard. Police stated that bomb squad teams and K9 units completed a full sweep with negative results, and the situation was subsequently declared safe. The exact source of the beeping sound has not been officially confirmed, and authorities have not disclosed whether it originated from onboard equipment or another unidentified item.

Incidents

United Airlines Flight Diverted After Suspicious Beeping Mid-Air Triggers Bomb Alert

Aviation Today News Desk / April 20, 2026

Pittsburgh, United States: A United Airlines flight en route from Chicago to New York was forced to make an emergency

Bucharest, Romania: A serious in-flight medical emergency involving a TAROM Boeing 737 has raised renewed concerns over pilot fatigue after a co-pilot collapsed during a scheduled European service, prompting an emergency response and regulatory scrutiny. The incident occurred on April 16, 2026, during a return flight operated by Romania’s national carrier TAROM from Amsterdam Schiphol Airport to Bucharest Henri Coandă International Airport. The 57-year-old co-pilot had not slept the night before reporting for duty, a factor that investigators later identified as central to the event. The crew had earlier completed an outbound sector from Bucharest to Amsterdam, during which the co-pilot reportedly felt unwell. Despite his condition, he continued operating and joined the return flight shortly after arrival, reflecting a tight turnaround schedule. During the return leg, the co-pilot’s condition deteriorated. Reports indicate that approximately 50 minutes after departure he began feeling worse, and about 2 hours and 40 minutes into the flight, he lost consciousness in the cockpit. The captain declared an emergency and continued the flight, ensuring a safe landing in Bucharest. Medical teams were positioned on arrival and boarded the aircraft immediately to attend to the incapacitated crew member. Passengers reported to be 87 onboard were disembarked via rear stairs to allow rapid access to the cockpit. Initial findings reported that the pilot’s collapse was linked to extreme fatigue after “not sleeping a wink the night before,” reinforcing the seriousness of the situation. Romanian aviation authorities classified the occurrence as a “serious safety event,” citing the direct implications of cockpit incapacitation during flight.

Incidents

TAROM Co-Pilot Loses Consciousness Mid-Flight, Crew Fatigue Under Scrutiny

Aviation Today News Desk / April 20, 2026

Bucharest, Romania: A serious in-flight medical emergency involving a TAROM Boeing 737 has raised renewed concerns over pilot fatigue after

Faro, Portugal: A Jet2 Boeing 737-800 operating flight LS3643 from Bournemouth, United Kingdom, to Gran Canaria, Spain, made an emergency landing at Faro Airport in Portugal on April 16, 2026, after crew reported smoke inside the cabin during the flight. The aircraft, carrying 141 passengers, departed Bournemouth at approximately 09:54 BST on a routine service to the Canary Islands. While cruising at altitude, the flight crew detected smoke or fumes in the cabin, prompting them to declare a technical emergency and initiate an immediate diversion to Faro, the nearest suitable airport along the route. According to Portuguese civil protection authorities and airport officials, the pilots issued an emergency call shortly before landing. The aircraft touched down safely at Faro at approximately 12:24 local time, around two and a half hours after departure, with no injuries reported among passengers or crew. Faro Airport activated its emergency response protocols in advance of the landing. The operation triggered the airport’s preliminary intervention plan, leading to the deployment of around 95 personnel and 41 emergency vehicles, including firefighters, police units, and medical teams. Emergency crews were positioned strategically along the runway to ensure rapid response if required. Passengers disembarked normally after landing while the aircraft was taken for technical inspection to determine the source of the smoke. Authorities have not yet confirmed the exact cause of the incident. Some reports described the situation onboard as tense, with cabin smoke prompting a full emergency alert at the airport. A “red code” response was activated, mobilizing dozens of emergency vehicles and personnel as a precautionary measure, though the landing itself was conducted safely without further escalation. The aircraft remains under technical evaluation in Faro as investigations continue into the source of the smoke. The airline has not reported any injuries, and further updates are expected following inspection results.

Incidents

Jet2 Flight From Bournemouth To Gran Canaria Diverts To Faro After Cabin Smoke Mid-Air

Aviation Today News Desk / April 17, 2026

Faro, Portugal: A Jet2 Boeing 737-800 operating flight LS3643 from Bournemouth, United Kingdom, to Gran Canaria, Spain, made an emergency

New Delhi, India: A ground collision between two commercial aircraft operated by SpiceJet and Akasa Air at Indira Gandhi International Airport has prompted a regulatory investigation, after both planes sustained damage during taxi operations on Thursday afternoon. The incident occurred at approximately 2:15 PM at Terminal 1, involving a SpiceJet Boeing 737-700 (VT-SLB) arriving from Leh and an Akasa Air Boeing 737 MAX 8 scheduled to operate flight QP1406 from Delhi to Hyderabad. According to the Directorate General of Civil Aviation (DGCA), the SpiceJet aircraft was taxiing into its designated parking bay after landing when its right winglet struck the left horizontal stabiliser (tail section) of the Akasa aircraft. The Akasa aircraft had already been pushed back from its bay and was positioned for engine start, effectively stationary at the time of impact. Preliminary findings indicate that the SpiceJet aircraft had been cleared by air traffic control to taxi toward bay No. 106 after confirming separation from the Akasa aircraft. However, during the manoeuvre, the aircraft reportedly executed a turn without wing walker clearance, leading to contact between the two planes. Flight tracking data and initial reports suggest the SpiceJet jet was pulling into the gate, while the Akasa aircraft was in pushback or preparing to taxi out for departure. The collision resulted in visible structural damage to both aircraft: SpiceJet: Right winglet damaged Akasa Air: Left-hand horizontal stabiliser damaged The winglet of the SpiceJet aircraft briefly lodged into the Akasa aircraft’s tail section following impact. No injuries were reported. All passengers and crew onboard the Akasa aircraft were safely disembarked, and the airline arranged alternate travel for passengers bound for Hyderabad SpiceJet described the incident as a “ground occurrence while taxiing”, confirming that its aircraft has been withdrawn from service pending checks. Akasa Air stated that its aircraft was stationary when the contact occurred, and confirmed that all standard safety protocols were followed after the incident. The Directorate General of Civil Aviation has launched a detailed investigation into the incident. The probe will examine ground handling procedures, ATC instructions, aircraft separation standards, and taxi coordination protocols.

Incidents

SpiceJet Jet Hits Stationary Akasa Aircraft At Delhi Airport, DGCA Orders Probe

Aviation Today News Desk / April 17, 2026

New Delhi, India: A ground collision between two commercial aircraft operated by SpiceJet and Akasa Air at Indira Gandhi International

Mexico City, Mexico: In a landmark ruling that reshapes the narrative of one of Cuba’s deadliest aviation disasters, a Mexican court has held charter airline Aerolíneas Damojh (Global Air) responsible for the 2018 crash of a Boeing 737 in Havana, concluding that the aircraft suffered from severe maintenance failures and “should never have flown.” The decision, based on court documents dated March 31 and reviewed by multiple international outlets, marks a significant legal departure from earlier findings that attributed the accident primarily to pilot error. An independent expert assessment presented during proceedings determined that the crash of Cubana de Aviación Flight 0972 was an “institutional accident” caused by systemic maintenance negligence. The report emphasized that the pilots were merely the “final line of defense” and were unable to prevent the catastrophe once critical failures had already developed. The judge accepted these findings and ruled that the aircraft’s operator, Global Air, bore responsibility for placing an unfit aircraft into service. The court ordered Global Air to pay USD 1.5 million in compensation to each of the families of the four Mexican crew members who initiated the lawsuit. Notably, the airline failed to appear in court and was tried in absentia, while the aircraft’s insurer also named in the case was ultimately cleared of financial liability. Legal representatives for the plaintiffs described the ruling as “groundbreaking”, arguing that it validates long-standing concerns about the airline’s maintenance practices and operational standards. The accident occurred on May 18, 2018, when a Boeing 737-200 (registration XA-UHZ) crashed shortly after takeoff from José Martí International Airport in Havana while operating a domestic flight to Holguín. Of the 113 people onboard, 112 were killed, making it one of the deadliest aviation disasters in Cuba in decades. Only one passenger survived. The aircraft was owned and operated by Global Air, a Mexican charter airline, and was leased to Cuba’s state carrier Cubana de Aviación under a wet lease agreement. The Mexican ruling directly contradicts Cuba’s 2019 official investigation, which attributed the crash primarily to pilot error and weight miscalculation, citing deficiencies in crew performance and operational procedures. In contrast, the Mexican court concluded that chronic maintenance deficiencies and systemic oversight failures were the root cause, reframing the accident as a broader organizational failure rather than an isolated human error. Global Air had faced prior operational scrutiny in Mexico, including temporary suspension following the crash as authorities examined its compliance with safety regulations. Reports cited during the case highlighted a history of technical issues and complaints, raising questions about the aircraft’s airworthiness long before the accident occurred. Beyond the initial lawsuit, broader legal proceedings are underway. Lawyers representing victims confirmed that: A class-action civil lawsuit covering all victims is in progress A criminal complaint for homicide has been filed against the airline and responsible parties However, the criminal investigation in Mexico has reportedly stalled due to limited cooperation from Cuban authorities. Samuel González, counsel for the victims’ families, described the judgment as a hard-fought and “groundbreaking” decision for Mexico. He said the ruling reinforces early admissions made in Havana by the airline’s own head of maintenance, who acknowledged to relatives that the aircraft should not have been cleared for operation. “That aircraft operated for nearly a decade without proper maintenance,” González said. “The crash occurred in Cuba, but the risk was universal.” Efforts to reach representatives of the airline for comment were unsuccessful. González also indicated that the carrier may be moving toward bankruptcy proceedings, warning that any attempt to misuse the process would be legally challenged.

Investigation

Mexican Court Rejects Pilot Error, Blames Maintenance In 2018 Cuba Crash That Killed 112

Aviation Today News Desk / April 13, 2026

Mexico City, Mexico: In a landmark ruling that reshapes the narrative of one of Cuba’s deadliest aviation disasters, a Mexican

Berlin, Germany: A Ryanair Boeing 737-800 operating flight FR315 from Bucharest to Berlin made an emergency landing at Berlin Brandenburg Airport on April 8, 2026, prompting a large-scale response from airport emergency services. The aircraft was on a routine short-haul service from Bucharest Henri Coandă International Airport to Berlin when the crew reported a technical anomaly during the final phase of the flight. As a precaution, the pilots declared an emergency, allowing air traffic control to prioritise the aircraft’s approach and prepare ground response teams. According to flight data, the aircraft departed Bucharest at approximately 17:42 local time and landed in Berlin at around 18:40–18:41 CEST after a flight of just over two hours. The aircraft touched down safely on runway 06R under controlled conditions. Immediately after landing, it was surrounded by multiple fire trucks and emergency vehicles positioned around the aircraft as part of standard safety protocol. Images from the scene showed more than a dozen emergency vehicles encircling the aircraft while crews monitored the situation for any signs of fire or further technical risk. Authorities treated the situation as precautionary, a common procedure when an aircraft reports a potential onboard issue. Initial reports indicate the emergency was triggered by an “onboard anomaly” or technical issue detected during approach. However, no confirmed fire, smoke, or visible damage has been reported, and the exact cause remains under investigation. Aviation protocols require that even minor system warnings be treated seriously, often leading to emergency declarations and full airport readiness to mitigate any potential escalation. All passengers and crew onboard the aircraft were reported safe. There were no injuries, and passengers disembarked normally after safety checks were completed on the ground. Airport operations resumed shortly after the incident, with no major disruption reported beyond the immediate response.

Incidents

Ryanair Flight Declares Emergency After Technical Anomaly, Lands Safely In Berlin

Aviation Today News Desk / April 9, 2026

Berlin, Germany: A Ryanair Boeing 737-800 operating flight FR315 from Bucharest to Berlin made an emergency landing at Berlin Brandenburg

Boeing 737

Southwest Returns To Austin After Engine Problem; FAA Finds Metal Debris In Right Engine

Skymark Boeing 737 Makes Emergency Return To Haneda After Tire Rupture

NTSB Data Suggests Possible Deliberate Engine Shutdown In MU5735 Crash That Killed 132

Southwest Airlines Pilot Incapacitated As Cockpit HUD Struck His Head During Takeoff

United Airlines Flight Diverted After Suspicious Beeping Mid-Air Triggers Bomb Alert

TAROM Co-Pilot Loses Consciousness Mid-Flight, Crew Fatigue Under Scrutiny

Jet2 Flight From Bournemouth To Gran Canaria Diverts To Faro After Cabin Smoke Mid-Air

SpiceJet Jet Hits Stationary Akasa Aircraft At Delhi Airport, DGCA Orders Probe

Mexican Court Rejects Pilot Error, Blames Maintenance In 2018 Cuba Crash That Killed 112

Ryanair Flight Declares Emergency After Technical Anomaly, Lands Safely In Berlin

Follow Us

Quick Links

Navigate

General Support

News Desk Support

Follow Us