Skip to content

Facebook Instagram Linkedin X-twitter Youtube

About Us
Contact Us
Advertisement

About Us
Contact Us
Advertisement

Aviation Newsletter

WhatsApp Channel

Search

News
Pilot Training
Flight School Analysis
Civil Aviation
Aviation Jobs
Training
Services
More

News
Pilot Training
Flight School Analysis
Civil Aviation
Aviation Jobs
Training
Services
More

Search

News
Pilot Training
Flight School Analysis
Civil Aviation
Aviation Jobs
Training
Services
More

News
Pilot Training
Flight School Analysis
Civil Aviation
Aviation Jobs
Training
Services
More

News

Civil Aviation

Pilot Training

Flight School Analysis

Aviation Jobs

Training

Services

About Us

Contact Us

Search

Aviation Today News Desk

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.

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

April 20, 2026

South Carolina, United States: Four people were killed after a single-engine aircraft crashed shortly after departure near Union County Airport on April 17, with federal investigators now examining the cause of the fatal accident. According to the Federal Aviation Administration (FAA), the aircraft involved was a Mooney M20P, which went down at approximately 6:30 p.m. local time near the airport shortly after takeoff. All four occupants on board were killed in the crash. Authorities said the aircraft had departed from Union County Airport and was en route to Ellijay, Georgia, a route often used for short private flights across the region. Local officials later confirmed the identity of all four victims: James Moffatt (60), identified as the pilot Leasa Moffatt (61) Andrew Moffatt (30) William Moffatt (28) The identities were released by the Union County Coroner’s Office after next of kin had been notified. According to the coroner, the four people were members of the same family and were flying from the Raleigh-Durham, North Carolina area to the Huntsville, Alabama area. Emergency crews responded following reports of smoke near the airport area. Due to difficult terrain, the South Carolina Forestry Commission had to deploy heavy equipment, including a bulldozer, to clear access to the wreckage site. Authorities confirmed the aircraft was a single-propeller plane that had crashed in a wooded area near the airport. No survivors were found at the scene. The National Transportation Safety Board (NTSB) has taken the lead in the investigation, working alongside the FAA, Union County Sheriff’s Office, and the coroner. Investigators will focus on three primary areas: The pilot The aircraft The operating environment, including weather and flight conditions Officials indicated that the wreckage may be removed from the site in the coming days as part of the investigative process. The NTSB noted that determining a probable cause could take 12 to 24 months, which is standard for general aviation accident investigations.

4 Family Members Killed In Small Plane Crash Shortly After Takeoff In South Carolina

April 20, 2026

California, United States: Joby Aviation has announced a strategic partnership with Air Space Intelligence (ASI) to accelerate the integration of electric vertical take-off and landing (eVTOL) aircraft into the United States National Airspace System (NAS), marking a critical shift from aircraft development to airspace readiness. The collaboration, revealed on April 7, 2026, focuses on deploying ASI’s AI-powered Flyways platform as a core coordination layer to manage high-density eVTOL traffic, an emerging challenge as the industry approaches commercialization. While much of the eVTOL race has historically centered on aircraft design such as range, noise, and efficiency the partnership highlights a growing industry concern: airspace congestion at scale. With Joby eVTOL nearing FAA type certification and preparing for early commercial operations under the White House-backed eVTOL Integration Pilot Program, the focus is now shifting toward managing potentially hundreds of simultaneous flights across major urban corridors such as New York, Miami, and Dallas. The companies aim to address this challenge before large-scale deployment begins. At the center of the collaboration is ASI’s Flyways AI, built on its PRESCIENCE platform, which creates a four-dimensional digital model of airspace by integrating real-time traffic data, weather inputs, and demand forecasts. This system enables air traffic controllers to anticipate congestion and optimize routing proactively rather than reacting after disruptions occur. Bernard Asare, President of Civil Aviation at Air Space Intelligence, emphasized the importance of this shift, stating, “Scaling advanced air mobility requires more than new aircraft… it requires a new operating system for the airspace.” He added that the platform provides predictive awareness to coordinate high-density operations “proactively, not reactively,” bringing these capabilities to eVTOL operations from the outset. Unlike earlier initiatives that focused primarily on drone traffic management systems, this partnership of eVTOL is designed to integrate directly with existing air traffic control (ATC) workflows rather than operate as a parallel system. Flyways AI will augment controller decision-making within the current NAS infrastructure, a move that could prove critical in gaining regulatory acceptance and operational scalability. The companies confirmed that joint demonstrations, including live operational exercises, are expected before the end of 2026, aligning with Joby’s planned commercial launch timeline. These trials are expected to validate how AI-driven coordination performs in real-world, high-density airspace environments. The partnership builds on ASI’s existing experience in conventional aviation, where its technology already supports major stakeholders, including airlines and U.S. defense operations. The company’s systems reportedly manage a significant portion of U.S. air traffic, strengthening its credibility in safety-critical environments. Meanwhile, Joby eVTOL continues to advance toward commercialization. The company recently completed piloted demonstration flights in California and has been selected to participate in multiple projects under the U.S. government’s eVTOL Integration Pilot Program, which enables early operations across several states.

Joby Aviation Partners With ASI To Enable Scalable eVTOL Operations In U.S. Airspace

April 19, 2026

San Francisco, United States: An Air India co-pilot was denied entry into the United States and deported back to India after allegedly being found in possession of marijuana upon arrival in San Francisco, triggering internal and regulatory investigations. The pilot was travelling from Delhi to San Francisco on Tuesday as a “deadheading” crew member, a standard aviation practice where flight crew travel as passengers to position themselves for operational duty. The co-pilot was scheduled to operate a subsequent return flight from San Francisco to India, reportedly to Kolkata, but was unable to do so following the incident. Upon arrival at San Francisco International Airport, US authorities allegedly discovered marijuana in the pilot’s baggage during routine inspection procedures. Following the discovery, the pilot was deemed “inadmissible” under US laws and was not permitted to enter the country. He was subsequently sent back to India on the next available flight without being allowed to leave the airport premises. Air India confirmed the development in an official statement, saying, “One of our crew members travelling from Delhi to San Francisco on April 14, for positioning to operate a subsequent flight, was found to be inadmissible as per local laws and has been sent back to India.” The airline has since derostered the pilot and initiated an internal investigation into the matter. Reiterating its stance, Air India stated that it maintains zero tolerance for legal violations and will take “appropriate strict disciplinary action” in accordance with company policies. The incident has also been reported to India’s aviation regulator, the Directorate General of Civil Aviation (DGCA), which is expected to examine the case under existing safety and conduct regulations. While the full extent of regulatory action remains unclear, the case typically invites scrutiny under strict aviation norms governing substance possession and professional conduct.

Air India Co-Pilot Deported From US Over Alleged Marijuana Case, Probe Underway

April 18, 2026

Pune, India: Flight operations at Pune Airport were temporarily suspended late Friday night after an Indian Air Force (IAF) aircraft was involved in a hard landing incident that rendered the runway unusable for several hours, before authorities restored operations early Saturday morning following emergency repair work. The disruption began at approximately 10:25-11:00 PM on April 17, when an IAF fighter aircraft experienced a “hard landing” during arrival. A senior IAF officer said the exact cause of the incident would be established only after a formal court of inquiry. Given Pune Airport operates a single runway under a dual civil-military use model, the incident resulted in an immediate and complete suspension of both arrivals and departures. As per the Airport Director, IndiGo cancelled 31 arrivals and 34 departures, while Air India cancelled three arrivals and three departures. SpiceJet called off two arrivals and three departures, and Akasa Air cancelled two arrivals and three departures. Air India Express also reported five arrivals and five departures being cancelled. Authorities have not officially disclosed the exact aircraft type involved in the incident. However, it has been consistently identified as an IAF fighter aircraft across reports. The aircrew onboard were confirmed safe, with no injuries reported. Officials also confirmed that there was no damage to civilian property or airport infrastructure beyond the runway obstruction. The runway was declared temporarily unavailable late Friday night. All take-offs and landings were halted, affecting numerous scheduled night flights. Airlines were alerted, and multiple flights were cancelled, delayed, or diverted due to the closure. Union Minister of State for Civil Aviation Murlidhar Mohol confirmed the disruption and estimated that runway restoration would take around five hours. The Indian Air Force, in its official communication, stated, “Pune runway is temporarily unavailable due to an incident involving an IAF aircraft. The aircrew are safe and there is no damage to civil property. Efforts are underway to operationalise the runway and resume normal operations at the earliest.” Minister Mohol added, “Thankfully, the aircrew are safe and there has been no damage to civil property… it may take approximately 5 hours to restore normal runway operations.” Following the incident, airport authorities and the IAF initiated rapid recovery and inspection work “on a war footing” to clear the runway and ensure safety compliance. Authorities confirmed that all necessary safety checks were completed before reopening the airport to commercial traffic. Officials have not released a confirmed cause, and a detailed investigation is underway.

IAF Aircraft Hard Landing Shuts Pune Airport; Operations Resume After Disruption

April 18, 2026

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.

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

April 17, 2026

Washington, United States: The Federal Aviation Administration has launched an investigation after airline pilots were recorded making animal noises over an active air traffic control (ATC) frequency near Ronald Reagan Washington National Airport, raising concerns over professionalism and radio discipline in controlled airspace. The incident occurred on April 12, 2026, when audio later widely circulated online captured what appeared to be pilots operating regional aircraft engaging in non-essential transmissions, including repeated “meowing” and barking sounds, over a shared aviation frequency. Reports indicate the aircraft involved were operating as regional services for major U.S. carriers, the crews reportedly operating on behalf of American Eagle (MQ) and Delta Connection (DL) though no crew identities have been officially confirmed. According to multiple recordings and consistent reporting across outlets, the exchange began with one pilot transmitting “meow… meow,” followed by another responding with dog barking sounds such as “woof.” The interaction escalated into repeated transmissions including “meow meow meow meow,” interspersed with additional barking noises. Air traffic control then intervened, instructing, “You guys need to be professional pilots.” When the behavior persisted briefly, a sharper remark followed: “This is why you still fly an RJ,” referencing regional jet operations. The transmissions are believed to have taken place on the 121.5 MHz “guard” frequency, a channel reserved strictly for emergency communications and continuously monitored by both pilots and controllers. The misuse of this frequency can interfere with distress calls, block critical instructions, and increase operational risk, particularly in congested airspace such as Washington, D.C. The FAA confirmed it is reviewing the incident, stating it is “aware of the audio and is reviewing the situation.” The agency noted that regulations prohibit non-essential communication below 10,000 feet and require all radio transmissions to be directly related to the safe operation of the aircraft. It further added that the authenticity of the third-party recording must be verified before any enforcement action is considered, reiterating that all potential violations are investigated even in the absence of an immediate safety incident. The incident has drawn criticism from within the aviation community. Dennis Tajer of the Allied Pilots Association stated that the guard frequency “is not entertainment” and serves a critical safety function that must be preserved. The incident has gained widespread attention due to its occurrence in one of the United States’ most tightly controlled airspaces and its rapid spread across social media and aviation forums. While no operational disruption has been reported, the case has renewed focus on cockpit professionalism and the importance of strict adherence to communication discipline.

Pilots Under FAA Review For Non-Essential Radio Transmissions In Washington Airspace

April 17, 2026

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.

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

April 17, 2026

Melawi, Indonesia: All eight people on board a helicopter were killed after the aircraft crashed in a remote, forested area of Indonesia’s West Kalimantan province, authorities confirmed on Friday, following an overnight search operation that located the wreckage in difficult terrain. The aircraft, identified as an Airbus H130 helicopter operated by Matthew Air Nusantara, lost contact shortly after takeoff on Thursday morning while flying within Melawi district in Borneo island. According to Indonesia’s National Search and Rescue Agency (Basarnas), the helicopter disappeared from radar approximately five minutes after departure from a plantation helipad and was later found crashed about 3 kilometres from its last known contact point, in a densely forested and hilly area. “The location of the crash or loss of contact is in a densely forested area with steep hilly terrain,” said Mohammad Syafii, head of Basarnas, as quoted by Reuters. Officials confirmed that the aircraft carried six passengers and two crew members, all of whom died in the crash. The 2 crew members were identified as Pilot in Command, Captain Marindra W, and Engineer on Board, Harun Arasyid along with 6 passengers Patrick K, Victor T, Charles L, Joko C, Fauzie O, and Sugito. Rescue teams recovered wreckage, including parts believed to be the tail section of the helicopter, during the search operation involving military and police units. The plantation area from which the helicopter departed is reportedly owned by the palm oil company Citra Mahkota, according to rescue officials cited in international reports. Search and recovery efforts were significantly slowed due to dense jungle terrain and steep hills, forcing rescue teams to rely on combined aerial reconnaissance and ground movement through difficult forest access routes. Authorities have not yet determined the cause of the crash. Investigators are currently examining all possible factors, including mechanical failure and weather conditions, though no official conclusion has been released. “The cause of the crash remains unclear,” Basarnas officials said, confirming that a full investigation is underway.

Eight Killed As Helicopter Crashes In Indonesia’s West Kalimantan After Losing Contact

April 17, 2026

Washington, United States: The United States has moved a step closer to overhauling aviation safety rules following the passage of a major reform bill in April 2026, a direct response to the deadly midair collision near the nation’s capital that exposed critical gaps in airspace management and aircraft tracking. Lawmakers approved the legislation with strong bipartisan backing, signaling rare consensus on the need for systemic reform, though debate continues over whether the measures go far enough. The push for reform stems from the January 29, 2025 disaster involving American Airlines Flight 5342 and a U.S. Army UH-60 Black Hawk helicopter near Ronald Reagan Washington National Airport. The regional jet, operated by PSA Airlines, was on final approach when it collided with the helicopter conducting a routine night training mission. Both aircraft fell into the Potomac River, killing all 67 people on board 64 on the jet and three military crew making it the deadliest U.S. aviation accident in more than two decades. Investigations led by the National Transportation Safety Board quickly established that the crash was not caused by a single failure but by a chain of operational and systemic shortcomings. Air traffic controllers had cleared the jet for a runway change shortly before landing, while the helicopter crew, having been alerted to the aircraft’s presence, opted to maintain visual separation. However, a key part of the controller’s transmission indicating the jet’s altered flight path was likely not fully received, leaving both aircraft on converging trajectories in congested airspace. The preliminary report highlighted the risks of mixed military and civilian operations around Reagan National, one of the busiest and most complex airspaces in the country. It confirmed that standard procedures were being followed but underscored how those procedures themselves allowed little margin for error, particularly at low altitude and at night. The final report, released in early 2026, presented a far more critical assessment. Investigators pointed to flawed helicopter route design that permitted operations dangerously close to commercial flight paths, along with longstanding safety warnings that had not been adequately addressed. The report also cited high controller workload, gaps in communication, and a continued reliance on “see-and-avoid” practices instead of modern collision-avoidance systems. The NTSB concluded that the disaster resulted from systemic failures spanning regulatory oversight, airspace design, and operational decision-making. In the immediate aftermath, regulators imposed restrictions on helicopter traffic near Reagan National and began revising procedures for aircraft separation in high-density airspace. Yet the broader policy response unfolded in Congress, where lawmakers introduced competing reform proposals. The stricter ROTOR Act, which aimed to mandate comprehensive aircraft tracking systems with firm deadlines, passed the Senate but narrowly failed in the House, intensifying pressure for an alternative solution. That effort culminated in April 2026 with the passage of the ALERT Act in the House of Representatives. The legislation mandates the adoption of advanced collision-detection technologies, including ADS-B “In” systems, across much of the aviation fleet, while also requiring enhanced air traffic control procedures, expanded safety audits, and a comprehensive review of airspace design around major airports such as Reagan National. Investigators have indicated that the presence of such technology could likely have prevented the 2025 collision. Despite its overwhelming support, the bill has drawn criticism for allowing certain exemptions, particularly for military operations, and for setting implementation timelines that extend several years into the future. Families of the victims and some lawmakers argue that the reforms do not fully incorporate all safety recommendations issued by investigators and risk falling short of meaningful change. The legislation now moves to the Senate, where further negotiations are expected to reconcile differences between proposals and determine the final scope of reforms.

U.S. Lawmakers Advance Aviation Safety Reform After Deadly Washington Midair Collision

April 16, 2026

« Previous Page1 … Page18 Page19 Page20 Page21 Page22 … Page115 Next »

Follow Us

Facebook-f Instagram Linkedin-in X-twitter Youtube

AVIATION TODAY brings the latest in aviation and aims to cater information to professionals and Aviation Enthusiasts about the Industry.

Quick Links

About Us
Contact Us
Services
Advertise
FAQ

Navigate

Latest News
Civil Aviation
Pilot Training
Flight School Analysis
Aviation Jobs
Training

General Support

info@aviationtoday.in

News Desk Support

news@aviationtoday.in

Follow Us

Facebook-f Instagram Linkedin-in X-twitter Youtube

© Copyright 2026 Aviation Today. All rights reserved.

Terms of Use
Privacy Policy
Disclaimer

Search

About Us
News
Pilot Training
Civil Aviation
Flight School Analysis
Aviation Jobs
Training
Services
More
Contact Us
Advertisement

Aviation Newsletter

Facebook Instagram Linkedin X-twitter Youtube