Aviation Incident Archives - Page 18 of 29

Maryland, United States: A FedEx Express cargo aircraft experienced a mechanical failure on Wednesday when its nose landing gear collapsed while the plane was parked outside a maintenance hangar at Baltimore-Washington International Thurgood Marshall Airport (BWI). The incident occurred on Feb. 4, 2026, involving an Airbus A300-600F freighter, registered N682FE, which was undergoing scheduled maintenance at the time. The aircraft, operated by FedEx Express, settled forward as the nose gear gave way, coming to rest on the airport ramp. There were no injuries to FedEx personnel or emergency responders at the scene. Airport fire and rescue crews were dispatched promptly after the collapse was reported. A spokesperson for BWI-Marshall confirmed that emergency units responded and secured the area. Commercial passenger operations were unaffected, as the aircraft was in a designated cargo and maintenance zone well clear of active passenger facilities. In a statement to WBAL-TV 11 News, FedEx said it was aware of the incident and thanked its teams and first responders for their quick action. The company reiterated that no injuries resulted from the gear collapse. The Airbus A300-600F involved is part of FedEx’s older freighter fleet and has been in service for more than two decades. According to aircraft registry data, N682FE was delivered in 1999 and has been a long-serving cargo workhorse for the carrier. The Federal Aviation Administration (FAA) is expected to inspect the aircraft and investigate the cause of the landing gear failure. Officials have not yet released details regarding preliminary findings, and it remains unclear whether the collapse stemmed from a mechanical defect, maintenance error, or another factor. Airport authorities and FedEx investigators are coordinating with federal regulators to determine contributing causes and to prevent similar events in the future. As of this writing, there has been no indication of broader fleet groundings or operational impacts beyond the immediate response and inspection activities.

FedEx Cargo Plane Nose Gear Collapses During Maintenance At BWI-Marshall Airport

Aviation Today News Desk / February 6, 2026

Maryland, United States: A FedEx Express cargo aircraft experienced a mechanical failure on Wednesday when its nose landing gear collapsed […]

Brussels, Belgium: A Scandinavian Airlines (SAS) Airbus A320neo operating flight SK2590 from Brussels Airport (BRU) to Copenhagen (CPH) narrowly avoided a serious runway incident on Thursday evening after pilots inadvertently initiated a takeoff roll on a taxiway rather than the designated runway, aviation tracking data and eyewitness reports confirm. The flight, cleared for departure from Runway 07R shortly after 21:00 UTC, taxied toward the runway but instead turned onto a parallel taxiway (identified as E1/V1) and began accelerating as if commencing a normal departure. Flightradar24 data shows the aircraft reached approximately 107 knots (around 198 km/h) before the crew recognised the error and aborted the takeoff, applying heavy braking and reverse thrust to bring the aircraft to a stop near the end of the taxiway and adjacent grassy area. All 135 passengers and crew disembarked safely, and there are no reported injuries. Airport fire and rescue services assisted passengers, who were later rebooked onto alternate flights to Copenhagen. SAS’s Head of Communications, Alexandra Lindgren Kaoukji, confirmed the incident to Danish broadcaster TV 2, stating that the flight from Brussels to Copenhagen was canceled due to an “irregularity.” She confirmed the airline’s account of an aborted departure and that passengers were accommodated on subsequent services. Belgian civil aviation authorities have initiated a formal investigation into the circumstances that led to the aircraft taking the wrong surface for departure. Investigators will review air traffic control communications, flight crew procedures, and airport surface signage and lighting, particularly given the complex layout of taxiways and runways at one of Europe’s busiest hubs. The taxiway departures are rare and emphasise the importance of rigorous cross-checks by flight crews and air traffic controllers to ensure correct runway alignment before high-speed acceleration. Any final determinations about human factors or procedural issues will await the outcome of the official investigation

Incidents

SAS A320neo Narrowly Avoids Runway Incident After Taxiway Takeoff Attempt In Brussels

Aviation Today News Desk / February 6, 2026

Brussels, Belgium: A Scandinavian Airlines (SAS) Airbus A320neo operating flight SK2590 from Brussels Airport (BRU) to Copenhagen (CPH) narrowly avoided

Galveston, United States: New federal investigative findings reveal critical communication misunderstandings and extremely limited visibility as major factors immediately preceding the December 22, 2025, crash of a Mexican Navy medical flight in Galveston Bay that killed six people and left two seriously injured, according to the preliminary report released by the U.S. National Transportation Safety Board (NTSB). The Beechcraft B300 aircraft, registered ANX1209 and operated by the Mexican Navy, was on a humanitarian medical mission coordinated with the Michou y Mau Foundation. The flight was transporting a severely burned pediatric patient from Mérida, Mexico, to Shriners Children’s Hospital in Galveston, Texas, when it crashed into West Bay during its approach to Scholes International Airport shortly before 3:15 p.m. local time. According to the NTSB preliminary report, Houston Approach Control cleared the flight crew for an RNAV (GPS-based) approach to Runway 14 but did not clear the aircraft to land. The flight crew’s initial readback mistakenly stated they were “cleared to land,” prompting controllers to twice clarify that the aircraft was cleared only for the approach and not for landing. Controllers then directed the crew to contact the tower. Despite repeated clarifications, the crew’s responses indicated persistent misunderstanding. During the final stages of the approach, air traffic controllers issued multiple low-altitude alerts, but received no further communication from the flight crew before radar contact was lost. The preliminary report and weather observations confirmed dense fog and severely restricted visibility during the aircraft’s final descent. Controllers advised the crew that cloud ceilings near the airport were approximately 300 feet, a condition that significantly limits visual reference and places heavy reliance on instrument procedures. Local weather data and witness accounts indicate visibility at times was as low as approximately a quarter mile with heavy sea fog common along the Texas Gulf Coast under certain conditions further complicating the approach. The aircraft impacted the waters of West Galveston Bay approximately half a mile from the shoreline. Six occupants including the pilot, co-pilot, two flight crew members and two passengers were fatally injured. Two passengers, reported to be a flight nurse and the mother of the pediatric patient, survived with serious injuries. Search and rescue operations immediately following the crash involved the U.S. Coast Guard, Texas Department of Public Safety, Galveston County Sheriff’s Office and local first responders. The wreckage was located in shallow water, facilitating recovery efforts. The NTSB’s preliminary report is part of an ongoing investigation to determine all contributing factors. These factual reports do not assign probable cause but document the circumstances surrounding the accident based on available data, including air traffic control communications and radar information. Federal investigators will continue to analyze cockpit voice recordings, flight data, maintenance records and meteorological data. A final report typically released 12–24 months after an accident will include a probable cause determination and safety recommendations aimed at preventing similar tragedies.

Investigation

NTSB Preliminary Report Cites Miscommunication, Low Visibility In Galveston Bay Crash

Aviation Today News Desk / February 5, 2026

Galveston, United States: New federal investigative findings reveal critical communication misunderstandings and extremely limited visibility as major factors immediately preceding

Kolkata, India: A Turkish Airlines Airbus A330 on a scheduled service from Kathmandu, Nepal, to Istanbul, Turkey made a full emergency landing at Netaji Subhash Chandra Bose International Airport, Kolkata, on Wednesday afternoon after the crew reported a fire in the aircraft’s right engine shortly after take-off. The flight, operating as THY-727, departed Tribhuvan International Airport at approximately 1:28 PM local time with 236 people on board 225 passengers and 11 crew members. Within four minutes of take-off, the pilots received a warning of a possible fire in the right engine and immediately shut down the affected unit. Following standard emergency procedures, the captain declared a PAN PAN distress call, an international aviation signal indicating an urgent situation and elected to divert the long-haul flight to Kolkata rather than continue towards its planned destination. Air traffic control at Kolkata was informed of the situation, and a full emergency response was activated, deploying firefighting and rescue units ahead of the aircraft’s arrival. The Airbus A330, capable of flying on a single engine, landed safely at around 2:49 PM IST without incident. Officials from both Nepal and Indian aviation authorities confirmed that no injuries were reported among passengers or crew. Tribhuvan International Airport briefly suspended operations for about 15 minutes following the alarm. After landing, the aircraft was parked at Kolkata Airport and underwent detailed technical inspection to determine the exact cause and extent of the engine malfunction. Passengers were reportedly accommodated in local hotels while arrangements were made for onward travel, including plans for a replacement aircraft earlyThursday morning.

Incidents

Turkish Airlines Flight Makes Emergency Landing In Kolkata After Engine Fire Mid-Air

Aviation Today News Desk / February 5, 2026

Kolkata, India: A Turkish Airlines Airbus A330 on a scheduled service from Kathmandu, Nepal, to Istanbul, Turkey made a full

Jet2 Flight Declares Emergency Over UK After Pilot Becomes Incapacitated Mid-Air SEO DES: During approach, ATC was alerted after a pilot fell ill, emergency services were deployed and the remaining crew landed the aircraft safely at Manchester SOCIAL: A Jet2 Airbus A321 operating Flight LS980 from Lanzarote to Manchester declared a mid-air emergency during its final approach after one pilot became medically incapacitated. The crew activated Squawk 7700, prompting ATC to provide priority landing clearance and deploy emergency services. The remaining pilot landed the aircraft safely at Manchester. The affected pilot received medical attention. No passengers or crew were injured, and standard aviation safety protocols were followed throughout. Image: Transport Pixels (Flickr) Video: Jet 2 Manchester, United Kingdom: A Jet2 passenger aircraft declared a mid-air emergency during its approach to Manchester Airport on Tuesday evening after one of the pilots became incapacitated due to a medical issue, aviation and airline sources have confirmed. The aircraft, Flight LS980, an Airbus A321 bound from Lanzarote, Canary Islands to Manchester, transmitted a Squawk 7700 general emergency code, the international radio transponder signal indicating a critical in-flight emergency approximately 25 minutes before its scheduled landing. Flight data and reports indicate the Airbus A321 departed Lanzarote at about 15:45 GMT and initially progressed normally until the final stage of descent toward Manchester Airport. It was during this approach phase that the cockpit crew informed Air Traffic Control (ATC) that one pilot was unable to continue due to a sudden medical problem. In response, ATC provided priority handling and clearance for landing, while emergency services including fire, rescue and medical teams were placed on standby at the airport. Despite the sudden loss of one pilot, the remaining flight crew maintained control and continued the descent. The aircraft touched down safely on Runway 05L at Manchester Airport at approximately 20:14 GMT. Once on the ground, the incapacitated pilot was met by waiting medical personnel and taken for further assessment. There have been no reported injuries among passengers or cabin crew, and disembarkation occurred in a routine and orderly manner, according to airline and airport representatives. A Jet2 spokesperson told GB News the carrier had requested a priority landing after one of the pilots “felt unwell,” adding: “The aircraft landed safely and customers disembarked as normal.” Commercial jetliners such as the Airbus A321 typically operate with a captain and first officer. In the event one pilot becomes incapacitated, industry training and procedures direct the remaining qualified pilot to assume full control of the aircraft. Such protocols, regularly practiced in simulators, are designed to maintain safety during critical phases such as approach and landing. The use of Squawk 7700 ensures ATC and emergency services are rapidly made aware of in-flight emergencies so they can provide priority routing and ground support. Manchester Airport, one of Jet2’s principal UK hubs, confirmed that emergency equipment and teams were ready at the runway in anticipation of the flight’s arrival, reflecting standard safety protocol for declared emergencies.

Incidents

Jet2 Flight Declares Emergency At Manchester Airport After Pilot Becomes Incapacitated

Aviation Today News Desk / February 5, 2026

Manchester, United Kingdom: A Jet2 passenger aircraft declared a mid-air emergency during its approach to Manchester Airport on Tuesday evening

Mumbai, India: Two commercial aircraft operating at Chhatrapati Shivaji Maharaj International Airport (CSMIA) were involved in a ground collision involving their wingtips on Tuesday evening, prompting inspections and an immediate probe by aviation authorities. All passengers and crew onboard both flights were unharmed, officials confirmed. The incident occurred at approximately 7:30 pm IST when Air India flight AI 2732, bound for Coimbatore, was taxiing for departure and the IndiGo flight 6E 791 had just landed from Hyderabad and was taxiing toward the terminal. Both aircraft involved were narrow-body Airbus A320s. According to Air India, the right wingtip of its aircraft made contact with the wingtip of the IndiGo aircraft while maneuvering on the taxiway prior to taking off. The airline said the contact resulted in damage to its aircraft’s wingtip, and the aircraft was immediately grounded for technical checks as a precautionary measure. All passengers were safely deplaned, and ground teams began arranging alternative onward travel. IndiGo released a separate statement confirming that the wingtip of its aircraft operating flight 6E 791 touched the wing of another airline’s aircraft while taxiing after landing. The airline said all passengers disembarked safely, and its aircraft is undergoing maintenance inspection in line with standard protocols. The Directorate General of Civil Aviation (DGCA) dispatched a team from its Mumbai office to the site soon after the incident. DGCA officials confirmed both aircraft returned to their respective bays and were taken out of service pending inspection. The regulator has initiated an inquiry to determine the factors leading to the collision, focusing on ground vehicle and aircraft movement controls at the busy international airport. “No injuries have been reported among passengers or crew,” according to civil aviation sources, highlighting that the low-speed nature of the taxiing incident limited the impact to aircraft structures rather than human safety. The airport, which operates parallel runways and heavy traffic movements daily, did not report any significant disruptions to other flights following the incident. Authorities said that routine operations continued while the affected aircraft were inspected.

Incidents

Air India & IndiGo Aircraft Wingtips Collide At Mumbai Airport, No Injuries Reported

Aviation Today News Desk / February 4, 2026

Mumbai, India: Two commercial aircraft operating at Chhatrapati Shivaji Maharaj International Airport (CSMIA) were involved in a ground collision involving

San Antonio, United States: A Delta Air Lines passenger aircraft was forced to return and land safely at San Antonio International Airport Tuesday morning after a report of smoke from one of its engines prompted a precautionary emergency response. All passengers and crew members walked away without injury, and initial inspections found no active fire. The flight, carrying 143 people onboard, had just departed San Antonio en route to Atlanta when the flight crew reported signs of smoke coming from an engine shortly after takeoff. Flight operations personnel aboard the aircraft alerted air traffic controllers, and the pilots declared an emergency to secure priority access back to the airport runway. At approximately 11:03 a.m. local time, the San Antonio Fire Department and airport emergency responders were dispatched to the scene following the alert. Fire crews positioned along the runway stood by as the jet approached for landing, a standard precaution for possible in-flight mechanical issues. The aircraft touched down safely at about 11:20 a.m., and emergency services immediately inspected the plane on the tarmac. Despite the in-flight smoke report, responders found no flames, no active fire, and no evidence of ongoing combustion around the engine area. After a thorough check, emergency resources were scaled back and airport operations continued normally. Delta Air Lines confirmed that no injuries occurred during the event. Passengers were allowed to disembark normally once the aircraft had been cleared by authorities. The airline’s operations team is working with maintenance specialists to investigate the cause of the smoke indication reported by the crew. Delta representatives also stated that passengers affected by the disrupted flight are being rebooked on alternative services to reach their final destinations. The airline emphasized that the crew followed established safety procedures throughout the incident. Preliminary reports suggest that this emergency landing reflects the airline’s adherence to standard safety protocols for in-flight mechanical anomalies. Modern commercial jets are equipped with multiple warning systems designed to alert pilots to unusual conditions such as smoke, fire indicators, or engine malfunctions, ensuring swift action and passenger safety. San Antonio International Airport authorities noted that the quick cooperation between flight crews, air traffic controllers, and emergency services minimized risk and passenger disruption.

Incidents

Delta Air Lines Flight Makes Emergency Return To SAT After Engine Smoke, No Injuries

Aviation Today News Desk / February 4, 2026

San Antonio, United States: A Delta Air Lines passenger aircraft was forced to return and land safely at San Antonio

Investigation

NTSB Preliminary Report Cites Unqualified Second-In-Command In Greg Biffle Plane Crash

Aviation Today News Desk / February 3, 2026

North Carolina, United States: The National Transportation Safety Board (NTSB) has released a preliminary investigative report on the December 18,

Delhi, India: Air India has grounded one of its Boeing 787-8 Dreamliner aircraft after a pilot reported a possible defect in the fuel control switch mechanism, prompting a detailed inspection and coordination with the airframe manufacturer, Boeing. The aircraft, operating as AI132 from London Heathrow to Bengaluru, landed safely at its destination on February 2, after the flight crew observed abnormal behaviour in the left engine’s fuel control switch during pre-flight engine checks, according to airline officials. In a statement, Air India confirmed that a pilot flagged the issue and the aircraft was immediately taken out of service as a precautionary safety measure while the concern is investigated. The airline has informed the Directorate General of Civil Aviation (DGCA) and engaged Boeing to prioritise a technical evaluation. “After receiving this initial information, we have grounded the aircraft and are involving the OEM (original equipment manufacturer) to get the pilot’s concerns checked on a priority basis,” an Air India spokesperson said. The matter has also been formally communicated to India’s aviation regulator, the DGCA. Fuel control switches regulate the flow of fuel to an aircraft’s engines and are designed with safeguards to prevent unintended movement. On the Boeing 787, these switches must be lifted and then moved to change position, reducing the likelihood of accidental operation. However, if such a switch were to shift from thle “RUN” to the “CUTOFF” position in flight, it would immediately halt fuel flow, leading to engine shutdown. The focus on fuel control switch behaviour stems from the June 12, 2025 crash of Air India Flight AI-171, another Boeing 787-8, near Ahmedabad, which killed 260 people. A preliminary investigation by the Aircraft Accident Investigation Bureau (AAIB) found that both engine fuel control switches moved from RUN to CUTOFF in quick succession just after takeoff, resulting in dual engine power loss. That incident triggered extensive regulatory scrutiny. In July 2025, Air India announced it had completed precautionary inspections of the fuel control switch locking mechanism on all Boeing 787-8 aircraft and found no defects at the time. Following the recent pilot report, Air India has begun focused inspections of fuel control switches across its Boeing Dreamliner fleet. According to an internal company communication seen by Reuters, these checks have so far not identified a systemic issue with other aircraft. Air India has reiterated that passenger and crew safety remains its top priority. Boeing has said it is assisting with the review.

Airlines

Air India Grounds Boeing 787‑8 LDN–BLR Flight After Pilot Reports Fuel Switch Defect

Aviation Today News Desk / February 3, 2026

Delhi, India: Air India has grounded one of its Boeing 787-8 Dreamliner aircraft after a pilot reported a possible defect

Orsk, Russia: Three people, including two aviation cadets and their instructor, were killed on Monday when a training aircraft crashed during a routine flight near the city of Orsk in Russia’s Orenburg Region, authorities confirmed. The aircraft, identified as a Diamond DA-series trainer operated by the St. Petersburg State University of Civil Aviation, disappeared from radar around 10:40 a.m. local time before crashing near the settlement of Dzhanatalap. Preliminary information from local officials indicates that two university students and an instructor were on board the aircraft at the time of the incident. All three occupants died on impact. According to Russian media sources citing operational services, the individuals have been provisionally identified as the pilot, Vasily N. (born 1989), and cadets Timofey K. (born 2005) and Dmitry S. (born 2004). Rescue teams from the Russian Ministry of Emergency Situations (EMERCOM) were dispatched immediately after the aircraft went down. Officials reported no post-impact fire at the crash site. In statements to state news agencies, the regional governor’s office said rescue operations were ongoing and that authorities were providing assistance to the victims’ families. Russian investigative bodies have launched inquiries into the cause of the accident. The Central Interregional Transport Investigations Directorate of the Russian Investigative Committee is leading the probe, in coordination with the Interstate Aviation Committee (IAC) and Russia’s civil aviation regulator, Rosaviatsiya. Officials have not yet released any preliminary findings on the circumstances that led to the aircraft’s descent. Specialists are expected to analyze flight data and wreckage to determine whether mechanical failure, weather, or human factors played a role. Regional authorities, including Orenburg Governor Yevgeny Solntsev, expressed condolences to the families of the deceased and affirmed support for the ongoing investigation. Senior representatives from Rosaviatsiya and the St. Petersburg State University of Civil Aviation are reported to be traveling to the crash site.

Aircraft Crashes

Three killed As Training Aircraft Crashes During Routine Flight Near Orsk In Russia

Aviation Today News Desk / February 3, 2026

Orsk, Russia: Three people, including two aviation cadets and their instructor, were killed on Monday when a training aircraft crashed

Aviation Incident

FedEx Cargo Plane Nose Gear Collapses During Maintenance At BWI-Marshall Airport

SAS A320neo Narrowly Avoids Runway Incident After Taxiway Takeoff Attempt In Brussels

NTSB Preliminary Report Cites Miscommunication, Low Visibility In Galveston Bay Crash

Turkish Airlines Flight Makes Emergency Landing In Kolkata After Engine Fire Mid-Air

Jet2 Flight Declares Emergency At Manchester Airport After Pilot Becomes Incapacitated

Air India & IndiGo Aircraft Wingtips Collide At Mumbai Airport, No Injuries Reported

Delta Air Lines Flight Makes Emergency Return To SAT After Engine Smoke, No Injuries

NTSB Preliminary Report Cites Unqualified Second-In-Command In Greg Biffle Plane Crash

Air India Grounds Boeing 787‑8 LDN–BLR Flight After Pilot Reports Fuel Switch Defect

Three killed As Training Aircraft Crashes During Routine Flight Near Orsk In Russia

Quick Links

Navigate

General Support

News Desk Support