Flight Incident Archives - Aviation Today

Florida, United States: A twin-engine Beechcraft King Air aircraft carrying 11 people crashed into the Atlantic Ocean off Florida’s east coast on May 12 after the pilot declared an in-flight emergency, triggering a large multi-agency rescue operation that ended with all occupants being recovered alive, according to updated statements from U.S. and Bahamian authorities. The aircraft was operating a regional flight in the Bahamas and had departed Marsh Harbour Airport in Abaco bound for Grand Bahama International Airport in Freeport when the emergency unfolded. Authorities said the aircraft went down roughly 50 miles east of Vero Beach and about 80 miles off Melbourne, Florida, in waters where deteriorating weather conditions were reported at the time. Initial information released by the U.S. Coast Guard stated that 10 people had been rescued, but officials later corrected the figure to 11 after completing accountability procedures for everyone onboard. According to the Bahamas Aircraft Accident Investigation Authority (AAIA), the pilot declared an emergency with air traffic control before communication with the aircraft was lost. Officials have not disclosed the exact nature of the emergency call, and investigators have not yet determined what caused the aircraft to crash into the ocean. No distress details involving engine failure, fire, fuel exhaustion or structural issues have been officially confirmed at this stage. The U.S. Coast Guard Southeast District coordinated the rescue effort after receiving the emergency alert. Rescue assets included a Coast Guard HC-144 Ocean Sentry/C-27 surveillance aircraft along with helicopters and support from maritime rescue agencies. Search crews located survivors in the water and recovered all 11 occupants before transporting them to Florida for medical evaluation. Authorities said several survivors were taken to Holmes Regional Medical Center in Melbourne, while others received treatment at nearby facilities. Officials have not released detailed injury information, but early reports indicated that no fatalities occurred during the accident. Weather conditions are expected to form a major part of the investigation. Meteorological reports from the region indicated unstable conditions along Florida’s east coast and northern Bahamas, including thunderstorms, gusty winds, heavy rain activity and rapidly changing visibility. The aircraft involved has been identified as a Beechcraft 300 King Air series twin-turboprop aircraft, a model widely used across the Caribbean and Bahamas for charter, medical evacuation and inter-island transportation because of its range and short-runway capability. Investigators from both the Federal Aviation Administration (FAA) and Bahamian aviation authorities are now examining the circumstances surrounding the crash. The probe is expected to include analysis of maintenance records, pilot qualifications, air traffic control communications, survivor interviews, weather data and any recoverable wreckage from the crash site. Officials have also not confirmed whether the aircraft remained intact after impact or whether it sank immediately following the ditching. The incident drew widespread attention because of the successful survival and rescue of all occupants despite the aircraft going down far offshore.

US Coast Guard Rescues 11 People After Beechcraft King Air Crashes Off Florida Coast

Aviation Today News Desk / May 13, 2026

Florida, United States: A twin-engine Beechcraft King Air aircraft carrying 11 people crashed into the Atlantic Ocean off Florida’s east […]

Denver, United States: A Frontier Airlines Airbus A321neo struck and killed a trespasser while departing Denver International Airport late on May 8, triggering an aborted takeoff, an engine fire, smoke inside the cabin, and an emergency evacuation that left 12 people with minor injuries, according to airport authorities, Frontier Airlines, the FAA and the NTSB. The aircraft, operating as Frontier Airlines Flight 4345 from Denver International Airport to Los Angeles International Airport, was carrying 224 passengers and seven crew members when the incident occurred at approximately 11:19 p.m. local time on Runway 17L. Officials said the unidentified individual breached the airport perimeter fence and entered the active runway area shortly before the collision. Denver International Airport confirmed the person was not believed to be an airport employee. Authorities stated the trespasser was struck by the aircraft during the takeoff roll and was pronounced dead at the scene. Frontier Airlines said the pilots immediately rejected the takeoff after reporting that the aircraft had struck a person on the runway. The impact resulted in a brief engine fire and smoke entering the cabin, prompting an emergency evacuation using inflatable slides. Official figures released by Frontier Airlines and cited by the NTSB confirmed that 12 occupants sustained minor injuries during the evacuation. Five people were transported to local hospitals for treatment, while the remaining injured passengers were treated at the airport. No fatalities or serious injuries were reported among passengers or crew. “We are gathering information about the emergency evacuation to determine if it meets criteria for a safety investigation,” NTSB spokesperson Sarah Taylor Sulick said early Sunday, adding that the agency might have more details in a few hours. A spokesman for the Denver Police Department said Sunday the investigation into the incident was ongoing and that the identity of the person on the runway will be confirmed and released by the Denver Office of the Medical Examiner. The CEO of the Denver airport, Phil Washington, said he knows there are questions still to be answered. “As this is an active investigation with numerous other agencies involved, it is going to take some time as we are still confirming what information we can share at this time,” Washington said in a statement. “This was a horrible and preventable tragedy that has affected many due to the actions of one person who apparently trespassed at an airport and lost their life as a result.” Flight tracking data reviewed by Flightradar24 showed the Airbus A321neo accelerated to approximately 127 knots before braking heavily and stopping on the runway. Emergency crews responded immediately and extinguished the engine fire. Passengers were later transported back to the terminal by bus, and Frontier arranged an alternate flight for most travelers. The affected runway remained closed for several hours before reopening Saturday morning. Federal authorities have launched multiple investigations into both the runway incursion and the emergency evacuation process. The National Transportation Safety Board said it is gathering information regarding the evacuation procedures, while the Federal Aviation Administration, local law enforcement and airport security officials are also examining how the individual gained access to the restricted airside area. U.S. Transportation Secretary Sean Duffy described the incident as a serious security breach and stressed that unauthorized access to airport movement areas poses extreme danger to both aircraft operations and public safety.

Incidents

Frontier Flight Kills Trespasser During Denver Takeoff, 12 Hurt In Evacuation

Aviation Today News Desk / May 11, 2026

Denver, United States: A Frontier Airlines Airbus A321neo struck and killed a trespasser while departing Denver International Airport late on

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

Chandigarh, India: A potentially serious aviation incident was narrowly avoided at Shaheed Bhagat Singh International Airport on May 5 after a passenger’s power bank caught fire onboard an IndiGo flight shortly after landing, prompting panic and an emergency evacuation that left six people injured. The incident involved flight 6E-108 from Hyderabad to Chandigarh, which had already landed and was taxiing toward the bay when the fire broke out inside the cabin. According to officials, the fire originated from a power bank stored in a seat pocket by a passenger seated in row 39C. The device suddenly ignited, producing smoke and flames that quickly spread inside the aircraft cabin. “After landing during a taxi into the bay at Chandigarh, a Power Bank kept in a pouch in the seat pocket by a passenger seated on 39C caught fire,” officials said. Passengers onboard reported a sudden build-up of smoke, triggering panic. “There was smoke in the cabin and people began panicking,” a passenger said. The cabin crew responded immediately, using onboard fire extinguishers to contain the blaze. “Cabin Crew used two fire extinguisher bottles to extinguish the fire,” officials said. As a precautionary measure, the crew initiated a full emergency evacuation, deploying all six slides. The aircraft was carrying around 198 passengers and six crew members, all of whom were evacuated safely. However, six passengers sustained injuries during the evacuation and were taken to hospital. The injuries were reported to be minor and largely occurred while using the evacuation slides. “All passengers and crew were safely evacuated,” officials said. Passenger Kapoor said several elderly travellers required medical attention. Ajay Verma, CEO of Chandigarh International Airport, said, “Emergency response teams acted immediately after the incident was reported, and all necessary protocols were followed to ensure passenger safety,” said. He added that airport authorities worked in coordination with airline staff and emergency services to manage the situation efficiently. Passengers described chaotic scenes during the evacuation and raised concerns over safety measures onboard. “Had this happened mid-air, it could have been much worse,” a passenger said. Some travellers also questioned the screening of electronic devices, particularly power banks, before boarding. Passengers alleged that airline staff failed to properly regulate the use and monitoring of power banks onboard, raising concerns about enforcement of safety norms. Some travellers questioned whether stricter checks or clearer instructions could have prevented the incident, pointing out that portable electronic devices, particularly lithium-ion batteries, pose known fire risks if not handled correctly. They urged airlines to reinforce guidelines and ensure better awareness among passengers regarding the safe storage and use of such devices during flights In its official statement, IndiGo confirmed the incident and reiterated its commitment to safety. “On 5 May 2026, while IndiGo flight 6E 108 from Hyderabad to Chandigarh was stationary after landing, an incident involving a customer's personal electronic equipment catching fire was reported,” the airline said. “In the interest of safety, an immediate evacuation was carried out and all the relevant authorities were immediately informed. All customers have been safely moved to the terminal and are being attended to by the team to ensure their well-being. The aircraft will undergo necessary checks before resuming operations. At IndiGo, the safety of our customers and crew remains our top priority,” the airline added. Authorities have initiated an investigation to determine the exact cause of the fire and assess adherence to safety protocols. The incident shows the risks associated with lithium-ion batteries, particularly power banks, which are known to pose fire hazards under certain conditions. Importantly, the fire occurred after the aircraft had landed, preventing what could have been a far more dangerous mid-air situation. Swift action by the cabin crew and airport emergency teams ensured the situation was contained without serious injuries. However, the incident has raised concerns regarding the handling and monitoring of portable electronic devices on flights.

Incidents

Power Bank Fire On IndiGo Flight In Chandigarh Triggers Emergency Evacuation; 6 Injured

Aviation Today News Desk / May 6, 2026

Chandigarh, India: A potentially serious aviation incident was narrowly avoided at Shaheed Bhagat Singh International Airport on May 5 after

Helicopter Crash

Helicopter Crash In Ticino Injures Six After 20-Metre Fall, Cause Under Investigation

Aviation Today News Desk / May 5, 2026

Mezzovico-Vira, Switzerland: A helicopter crash in Mezzovico-Vira left six people injured on Monday afternoon after the aircraft fell from a

Hays County, United States: A late-night aviation tragedy in Texas Hill Country has left five people dead after a twin-engine aircraft crashed near Wimberley in Hays County on April 30, 2026. According to local authorities and federal officials, the aircraft identified as a Cessna 421C went down at approximately 11:00 p.m. in a wooded area off Round Rock Road, triggering an immediate emergency response from fire and rescue crews. All five occupants onboard, including the pilot and four passengers, were pronounced dead at the scene. Flight tracking data indicates the aircraft was traveling from Amarillo to New Braunfels when it encountered trouble during the latter phase of the journey. Data shows the aircraft made a sudden sharp turn before entering a rapid descent, dropping from approximately 13,600 feet to around 7,000 feet within a short span. Radar contact was lost shortly thereafter. Officials said the aircraft impacted the ground at a high rate of speed, suggesting a catastrophic loss of control prior to the crash. Residents in the area reported hearing a loud explosion-like sound, followed by vibrations and visible flames. Several described seeing a fireball at the crash site moments after impact. Emergency crews were dispatched shortly after 11:05 p.m. and remained at the site through the night and into the following morning to manage the fire and begin recovery operations. Authorities confirmed that another aircraft had been flying along a similar route at the time of the incident. The second aircraft reportedly lost contact with the crashed plane but continued safely and landed in New Braunfels without incident. While the exact cause remains unknown, early reports indicate there may have been thunderstorm activity in the region at the time of the crash. Investigators have not confirmed whether weather played a direct role. No evidence has emerged to suggest a mid-air collision. The aircraft involved was a Cessna 421C, a pressurized, twin-engine aircraft commonly used for private and business travel. The Federal Aviation Administration (FAA) and the National Transportation Safety Board (NTSB) have launched a formal investigation. A preliminary report is expected within weeks, while the final report could take up to one to two years.

Aircraft Crashes

Five Onboard Killed After Twin-Engine Aircraft Crashes Near Wimberley In Hays County

Aviation Today News Desk / May 2, 2026

Hays County, United States: A late-night aviation tragedy in Texas Hill Country has left five people dead after a twin-engine

Mandera, Kenya: An EBB Air Embraer aircraft operating on the Nairobi-Mandera route veered off the runway during landing at Mandera Airstrip on Friday morning, in a runway excursion incident that triggered an emergency response but left all passengers and crew safe. According to confirmations from aviation authorities and multiple reports, the aircraft departed from Jomo Kenyatta International Airport (JKIA) in Nairobi at around 6:55–6:56 a.m. carrying 32 passengers and 4 crew members, before arriving in Mandera at approximately 8:30–9:10 a.m. local time. Preliminary reports indicate that the aircraft lost control after touchdown and overran the runway, eventually coming to rest in nearby vegetation or bushes beyond the paved surface of the airstrip. Images circulating from the scene show the aircraft partially embedded in bushy terrain, with its fuselage extending off the runway area. Some visuals also indicated light smoke from the aircraft’s structure following the impact. All 36 occupants were safely evacuated with the assistance of ground emergency teams deployed immediately after the incident. Authorities confirmed that no fatalities or injuries occurred, despite significant damage to the aircraft. The Kenya Airports Authority (KAA) stated that rescue teams responded promptly and secured the scene shortly after the aircraft came to a stop near the airstrip perimeter. The aircraft involved is reported to be an Embraer regional aircraft operated by EBB Air, identified in some aviation records as registration 5Y-EBB. The flight was a scheduled domestic service connecting Nairobi and Mandera, a route that serves government, humanitarian, and commercial travel in Kenya’s northeastern region. Aviation authorities have launched an investigation to determine the cause of the runway excursion. While the exact reason has not been confirmed, early considerations include landing conditions, runway surface factors, or possible technical issues. No official conclusion has yet been issued. The Mandera Airstrip, located near the Kenya–Somalia–Ethiopia border region, is known for handling limited traffic, primarily charter, humanitarian, and regional domestic flights.

Incidents

EBB Air Embraer Aircraft Veers Off Runway At Mandera Airstrip; All 36 On Board Safe

Aviation Today News Desk / April 25, 2026

Mandera, Kenya: An EBB Air Embraer aircraft operating on the Nairobi-Mandera route veered off the runway during landing at Mandera

New York, United States: A serious aviation safety incident unfolded at John F. Kennedy International Airport on April 20, 2026, when two commercial passenger jets came dangerously close during parallel approaches, prompting emergency evasive action and a federal investigation. The aircraft involved were Republic Airways Flight 4464, operating as an American Airlines service, and Jazz Aviation Flight 554, operating for Air Canada Express. Both aircraft were on final approach to parallel runways when the incident occurred at approximately 2:30 p.m. local time. According to preliminary findings, the American Airlines-operated regional jet deviated from its assigned approach path and entered the airspace of the Air Canada flight, which had been cleared to land on a parallel runway. Flight tracking data indicates the American aircraft descended sharply by roughly 600 feet while drifting into the adjacent approach corridor, creating an immediate conflict with the Air Canada jet. At their closest point, the two aircraft were separated by approximately 350 feet vertically and about 0.6 miles horizontally, well below standard separation minima. Both aircraft received Traffic Collision Avoidance System (TCAS) alerts, triggering urgent resolution advisories. Pilots responded immediately, executing coordinated evasive maneuvers in line with standard safety procedures. Air traffic controllers simultaneously issued corrective instructions. The Air Canada crew was directed to climb to approximately 3,000 feet, while the American flight was instructed to correct its trajectory. Cockpit audio from the incident captured warning alarms and urgent controller instructions, underscoring the severity of the situation. Both aircraft aborted their landings and executed go-arounds before repositioning for safe arrivals. No injuries were reported, and both flights landed without further incident. Airlines involved confirmed that crews followed established procedures. Air Canada stated its pilots “received a traffic warning… and took immediate action,” while Republic Airways confirmed its crew complied with resolution advisories and safely completed a go-around. The Federal Aviation Administration has launched a formal investigation into the incident, focusing on the deviation from the assigned approach path, air traffic control coordination, and adherence to separation protocols. The event is being treated as a significant loss-of-separation incident, with authorities expected to analyse flight data, ATC communications, and TCAS responses.

Incidents

Air Canada Express & American Airlines Jets Faced Near Mid-Air Collision; FAA Probes

Aviation Today News Desk / April 23, 2026

New York, United States: A serious aviation safety incident unfolded at John F. Kennedy International Airport on April 20, 2026,

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

Aircraft Crashes

Cessna Citation Aircraft Crashes In Bolivia After Loss Of Contact, Two Pilots Killed

Aviation Today News Desk / April 16, 2026

Cochabamba, Bolivia: A Cessna 550 Citation Bravo aircraft crashed in central Bolivia after losing contact with air traffic control shortly

Flight Incident

US Coast Guard Rescues 11 People After Beechcraft King Air Crashes Off Florida Coast

Frontier Flight Kills Trespasser During Denver Takeoff, 12 Hurt In Evacuation

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

Power Bank Fire On IndiGo Flight In Chandigarh Triggers Emergency Evacuation; 6 Injured

Helicopter Crash In Ticino Injures Six After 20-Metre Fall, Cause Under Investigation

Five Onboard Killed After Twin-Engine Aircraft Crashes Near Wimberley In Hays County

EBB Air Embraer Aircraft Veers Off Runway At Mandera Airstrip; All 36 On Board Safe

Air Canada Express & American Airlines Jets Faced Near Mid-Air Collision; FAA Probes

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

Cessna Citation Aircraft Crashes In Bolivia After Loss Of Contact, Two Pilots Killed

Follow Us

Quick Links

Navigate

General Support

News Desk Support

Follow Us