News

Civil Aviation

Pilot Training

Flight School Analysis

Aviation Jobs

Training

Services

About Us

Incidents

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

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

Aviation Today News Desk April 21, 2026

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

Nashville, United States: A serious aviation incident involving two Southwest Airlines Boeing 737 aircraft near Nashville International Airport has prompted a federal investigation after the jets came within close proximity following an air traffic control error that placed them on conflicting flight paths. The incident occurred as Southwest Flight 507, a Boeing 737 MAX 8 arriving from Myrtle Beach, initiated a go-around during its approach, while Southwest Flight 1152, a Boeing 737-700, was departing for Knoxville from a separate runway. According to preliminary findings and air traffic control audio reviewed by investigators, a controller issued a turn instruction to the arriving aircraft that inadvertently directed it into the departure path of the other jet, creating an immediate loss of safe separation. Air traffic control communications captured during the event indicate a rapidly escalating situation, with multiple instructions issued in quick succession, including climb directives that were later revised. In the cockpit, one of the pilots indicated the aircraft had already passed the point of conflict, reflecting how little time remained to resolve the situation through conventional means. Both aircraft subsequently received alerts from the onboard Traffic Collision Avoidance System (TCAS), which generated coordinated Resolution Advisories. The system instructed one aircraft to climb while directing the other to descend, allowing the crews to take immediate corrective action. Flight data suggests the jets of Southwest Airlines came within approximately 500 feet of each other, a distance considered a near midair collision under aviation safety standards. Despite the severity of the encounter, both flights continued safely with no reported injuries. Early assessments point to air traffic control error as the primary factor, compounded by the complexity of simultaneous runway operations during a go-around. Weather conditions, including reported gusty winds in the Nashville area, may also have contributed to the challenging operating environment at the time. The Federal Aviation Administration has launched a formal investigation and is expected to review controller actions, radar data, flight recordings, and adherence to separation protocols. Southwest Airlines stated that its flight crews responded in accordance with safety procedures and are cooperating fully with authorities. On April 15, 2026, a near-collision occurred at Charlotte Douglas International Airport when an American Airlines aircraft was forced to abruptly brake on the taxiway after a truck crossed directly in front of it, narrowly avoiding impact. The cockpit radio transmissions captured the crew reporting the close call to air traffic control. No injuries were reported, and the aircraft was able to continue and depart after a brief delay. The incident occurred on the airport tarmac and has drawn attention to ground movement safety, coming shortly after a fatal aircraft-vehicle collision at New York’s LaGuardia Airport, emphasising ongoing concerns over coordination between aircraft and ground vehicles.

Southwest Jets In Near Midair Collision Over Nashville After ATC Error, FAA Probes

Aviation Today News Desk April 21, 2026

Nashville, United States: A serious aviation incident involving two Southwest Airlines Boeing 737 aircraft near Nashville International Airport has prompted a

Manila, Philippines: A Philippine Airlines (PAL) domestic flight en route from Dumaguete to Manila was forced to make an emergency landing at Iloilo International Airport on Sunday afternoon after experiencing a reported oxygen supply issue while at cruising altitude. Flight PR 2544, operated by an Airbus A320, diverted and landed safely in Iloilo at approximately 4:30 p.m., according to airline and airport advisories. Initial reports indicate that the issue arose after the aircraft reached its cruising altitude of around 32,000 feet, when the cabin reportedly experienced insufficient oxygen supply. The incident is likely a pressurization-related malfunction, which can affect oxygen availability inside the cabin. Aviation protocols require immediate descent or diversion in such cases, as reduced cabin oxygen at high altitude can pose serious risks to passengers and crew. Despite the mid-air emergency, the aircraft landed safely without structural damage or fatalities. However, several passengers required medical attention upon arrival, primarily due to breathing discomfort and distress experienced during the flight. Passenger accounts cited in regional reports described a deteriorating cabin environment, including heat, poor ventilation, and difficulty breathing as the situation unfolded mid-flight. Flight PR 2544 is a routine domestic service connecting Dumaguete (Sibulan Airport) to Manila (Ninoy Aquino International Airport), typically operating with an Airbus A320 aircraft and a flight duration of approximately 1 hour and 20 minutes. Following the emergency landing, affected passengers were assisted by ground personnel, with arrangements made for onward travel. Authorities and the airline have initiated standard technical inspections and incident review procedures to determine the exact cause of the malfunction. No official statement detailing the root cause had been released at the time of reporting, but investigations are expected to focus on the aircraft’s environmental control and pressurization systems.

Manila-Bound Philippine Airlines Flight Diverts To Iloilo After Mid-Air Oxygen Issue

Aviation Today News Desk April 21, 2026

Manila, Philippines: A Philippine Airlines (PAL) domestic flight en route from Dumaguete to Manila was forced to make an emergency landing

Bengaluru, India: A Fly91 passenger flight operating from Hyderabad to Hubballi was diverted to Bengaluru on Sunday evening after adverse weather conditions over north Karnataka made landing at Hubballi airport unsafe. The aircraft, which had departed Hyderabad in the afternoon, was unable to complete its approach due to poor visibility and intense weather activity in the region, leading to an extended holding pattern for 3 hrs before the crew decided to divert as a precautionary measure resulting in an operational delay of around 2.5 to 3 hours. According to airline confirmation, the flight was scheduled to land in Hubballi around 4:30 pm but encountered deteriorating weather conditions during descent. The aircraft reportedly circled the Hubballi airspace for an extended period as pilots assessed landing feasibility. When conditions failed to improve, the crew diverted the flight to Bengaluru’s Kempegowda International Airport, where it landed safely. Passengers onboard experienced significant anxiety during the prolonged airborne phase, with reports and visual accounts suggesting distress inside the cabin as the aircraft continued holding over the region. Some passengers reportedly expressed concern over the extended circling, while cabin crew maintained communication and reassured passengers throughout the flight. Despite the tense situation, no medical emergencies or injuries were reported. All 22 passengers were reported safe. Fly91, in its official statement, categorically denied any technical malfunction and clarified that the diversion was carried out strictly due to weather-related safety concerns. The airline stated that the decision to hold and subsequently divert the aircraft was in line with standard operating procedures and aviation safety norms. It emphasized that the aircraft was fully serviceable and that the crew followed all regulatory guidelines issued for operations under adverse weather conditions. After diverting to Bengaluru, the aircraft landed safely and was later repositioned once weather conditions over Hubballi improved. The flight subsequently continued operations, ensuring passengers reached their destination. Officials reiterated that the safety of passengers remained the highest priority throughout the incident and that all procedures followed were in accordance with aviation safety protocols.

Fly91 Hyderabad-Hubballi Flight Diverts To Bengaluru Amid Severe Weather Conditions

Aviation Today News Desk April 20, 2026

Bengaluru, India: A Fly91 passenger flight operating from Hyderabad to Hubballi was diverted to Bengaluru on Sunday evening after adverse weather

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.

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 diversion

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

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 a

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

Aviation Today News Desk April 18, 2026

San Francisco, United States: An Air India co-pilot was denied entry into the United States and deported back to India after

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

Aviation Today News Desk April 18, 2026

Pune, India: Flight operations at Pune Airport were temporarily suspended late Friday night after an Indian Air Force (IAF) aircraft was

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

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 landing

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

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 Airport

Incidents

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

Southwest Jets In Near Midair Collision Over Nashville After ATC Error, FAA Probes

Manila-Bound Philippine Airlines Flight Diverts To Iloilo After Mid-Air Oxygen Issue

Fly91 Hyderabad-Hubballi Flight Diverts To Bengaluru Amid Severe Weather Conditions

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

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

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

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

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

Quick Links

Navigate

General Support

News Desk Support