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

cockpit

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

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

Aviation Today News Desk / April 9, 2026

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

United Airlines Jet Near-Miss With Black Hawk Helicopter; FAA Probes Safety Breach SEO DES: Preliminary radar data shows the aircraft came within about 525 ft vertically and 1,400 ft horizontally, notably below standard separation safety limits SOCIAL: A United Airlines Boeing 737 narrowly avoided a mid-air collision with a U.S. Army Sikorsky UH-60 Black Hawk near John Wayne Airport on March 24, 2026, after the helicopter crossed its approach path. The aircraft came within unsafe separation limits before pilots responded to a TCAS alert and landed safely. The Federal Aviation Administration has launched an investigation into airspace procedures, coordination, and possible violations of visual separation rules. Image: 4300streetcar (Wikimedia) Video: Flight Radar24, United Airlines Santa Ana, United States: A United Airlines passenger jet narrowly avoided a mid-air collision with a U.S. Army Black Hawk helicopter while approaching John Wayne Airport on Tuesday night, prompting a federal safety investigation. The incident occurred at approximately 8:40 p.m. on March 24, 2026, when United Airlines Flight 589, a Boeing 737-800 arriving from San Francisco, was on final approach when a military helicopter crossed directly in front of its flight path, according to the Federal Aviation Administration. Preliminary radar data shows the two aircraft came within roughly 525 feet vertically and about 1,400 feet horizontally, distances significantly below standard separation requirements. Air traffic controllers had alerted the flight crew to nearby helicopter activity moments before the collision. The pilots visually identified the aircraft and received a Traffic Collision Avoidance System (TCAS) resolution advisory, prompting immediate corrective action. The crew leveled the aircraft and continued the approach, landing safely without incident. The aircraft was carrying 162 passengers and 6 crew members. No injuries were reported, and the helicopter also landed safely. The California Army National Guard confirmed the helicopter was conducting a routine training mission and was operating under Visual Flight Rules along a designated route while maintaining communication with air traffic control. The FAA has launched a formal investigation into the near-miss, focusing on whether existing safety protocols were followed and if the incident violated recently implemented restrictions on “visual separation” between aircraft near major airports. The agency has increasingly moved away from reliance on pilot visual separation in congested airspace, requiring controllers to ensure radar-based spacing after a series of high-risk incidents involving helicopters and commercial aircraft. Investigators are also reviewing air traffic control procedures, coordination between military and civilian aircraft, and whether systemic safeguards functioned as intended prior to the activation of onboard collision-avoidance systems. The incident comes after the fatal mid-air collision on January 29, 2025, near Ronald Reagan Washington National Airport involving American Airlines Flight 5342 and a U.S. Army Sikorsky UH-60 Black Hawk during final approach over the Potomac River. The helicopter, on a night training mission, entered the jet’s flight path at around 300 feet, leading to a collision that killed all 67 people onboard both aircraft. The National Transportation Safety Board concluded the crash resulted from systemic failures and human error, including the helicopter’s altitude deviation, possible misidentification of traffic, communication gaps, and air traffic control’s reliance on visual separation. The report also cited flawed airspace design and inactive tracking systems, stating the accident was entirely preventable and highlighting the need for stricter separation rules and better coordination between military and civilian operations.

United Airlines Jet Near-Miss With Black Hawk Helicopter; FAA Probes Safety Breach

Aviation Today News Desk / March 27, 2026

Santa Ana, United States: A United Airlines passenger jet narrowly avoided a mid-air collision with a U.S. Army Black Hawk

REX Saab 340 Turboprop Flight Diverts To Parkes Airport After Mid-Air Engine Issue SEO DES: At about 13,000 feet, the crew detected an electrical fault on the right side of the aircraft, accompanied by abnormal engine (right) readings SOCIAL: A Regional Express Saab 340B operating Flight ZL6469 from Griffith to Sydney diverted to Parkes Airport on February 22 after the crew shut down the right engine due to electrical and abnormal engine indications at 13,000 feet. The aircraft landed safely on Runway 04 about 75 minutes later with no injuries reported. The Saab 340B (VH-RXE) returned to service roughly 36 hours after inspections. The Australian Transport Safety Bureau has been notified and is reviewing the occurrence to determine whether a formal investigation is required. Image: Bidgee (wikimedia) Video: Rex Parkes, Australia: A Regional Express (REX) Saab 340B turboprop flight was forced to divert and make an unscheduled landing at Parkes Airport (NSW) on February 22 after the crew shut down one of its engines following electrical and engine indications. Flight ZL6469, operating from Griffith to Sydney, was at around 13,000 feet when the crew detected an electrical fault on the right side of the aircraft, accompanied by abnormal engine readings from the No. 2 (right) General Electric CT7-9B engine. Following standard safety procedures for engine and systems abnormalities, the pilots elected to shut down the affected engine mid-flight and declared a diversion to the nearest suitable airport. The twin-engine turboprop then entered holding patterns south of Parkes before descending and landing safely on Runway 04 approximately 75 minutes after the issue was first identified. All passengers and crew disembarked without injury, with emergency response teams on standby as a precaution. The aircraft involved in the incident, registered VH-RXE, is part of REX’s Saab 340 fleet, a workhorse on Australia’s regional network. Following the diversion, the aircraft was taken out of service for detailed inspection and maintenance checks and was returned to scheduled service roughly 36 hours later, according to operational updates. In line with aviation safety protocols, the Australian Transport Safety Bureau (ATSB) has been made aware of the occurrence and awaits additional technical data from the operator before determining whether a formal investigation will be undertaken. Officials have indicated that such decisions hinge on further review of flight data and systems information provided by REX. In-flight engine shutdowns, while uncommon, are addressed in flight crew training and aircraft certification standards. Twin-engine turboprop aircraft such as the Saab 340 are designed to maintain controlled flight and safe landings on a single functioning engine when necessary.

REX Saab 340 Turboprop Flight Diverts To Parkes Airport After Mid-Air Engine Issue

Aviation Today News Desk / February 26, 2026

Parkes, Australia: A Regional Express (REX) Saab 340B turboprop flight was forced to divert and make an unscheduled landing at

transparent reporting and genuine implementation by airlines. New Delhi, India: In a new circular dated November 20, the DGCA has ordered stricter measures to address pilot fatigue, signalling a shift in the regulator’s approach from mere duty-hour limits to systemic fatigue-risk management. The DGCA initiated this crackdown after an audit of all scheduled airlines found that many operators were uncertain about the scope and content of “annual fatigue training.” Officials noted that fatigue-reports from crew members had not been reaching DGCA for several months, especially following the implementation of the first phase of revised duty and rest norms on July 1, 2025. Under the broader regulatory overhaul of 2025, the DGCA had already increased the minimum weekly rest period for pilots from 36 to 48 hours and set stricter limits on night duty, night-landing frequency and consecutive night flights. Still, regulators found that merely limiting duty-hours was not enough fatigue risk persisted when scheduling, rostering and crew-management systems failed to account for real-world operational stresses. The new circular aims to close that gap. The new measures mean that airlines must now build internal processes, not just comply with hours-based restrictions. Mandatory training for schedulers/dispatchers, a fatigue-reporting system, and a review committee these steps aim to ensure safety proactively, rather than reactive incident-based enforcement. For flight-crew, this may encourage a culture of openness about fatigue; the quarterly reporting system and independent review could reduce pressure on pilots to “tough it out.” For airlines, compliance will demand more than roster-planning operators will need to implement fatigue-awareness training, document reporting and follow-up, and coordinate across departments (scheduling, operations, HR). The November 25 circular builds on changes introduced earlier in 2025. In February, DGCA told the court that a revised framework for flight duty time limitation (FDTL) would be phased in from July 1, with full implementation by November 1. Under that framework: weekly rest was raised to 48 hours, night-duty definitions were revised, and caps placed on night landings and consecutive night flights. Simultaneously, DGCA released a draft “Fatigue Risk Management System” (FRMS), offering airlines a performance-based alternative to prescriptive duty-hour limits if operators can demonstrate through data that fatigue risk remains low. However, the regulator clarified that adoption of FRMS would remain optional; airlines may choose to continue under the standard duty-hour/rest rules.

DGCA Tightens Pilot Fatigue Rules, Mandates Training And Quarterly Reporting

Aviation Today News Desk / November 26, 2025

New Delhi, India: In a new circular dated November 20, the DGCA has ordered stricter measures to address pilot fatigue,

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