Connect with us

Regulations & Safety

Airbus Issues Fleet Action After Solar Radiation Incident on A320s

Airbus mandates software updates and hardware replacements for 6,000 A320s following a solar radiation incident compromising flight controls.

Published

on

Airbus Issues Precautionary Fleet Action Following Solar Radiation Incident

On November 28, 2025, Airbus announced a significant precautionary fleet action impacting approximately 6,000 A320-family aircraft, representing roughly half of the global fleet for this type. This decision follows a comprehensive investigation into a specific technical vulnerability triggered by environmental factors. The action is being coordinated with the European Union Aviation Safety Agency (EASA) and involves an Emergency Airworthiness Directive (EAD) to ensure the continued airworthiness of the affected airframes.

The catalyst for this widespread measure was a serious in-flight incident involving a JetBlue Airways flight on October 30, 2025. During a scheduled flight from Cancun to Newark, the aircraft experienced an uncommanded descent caused by corrupted flight control data. While the pilots successfully regained control and performed an emergency landing in Tampa, the event resulted in injuries to at least 15 passengers. Subsequent analysis identified that intense solar radiation had compromised the integrity of the flight control computer’s data processing.

We are seeing immediate operational responses across the aviation industry as airlines work to comply with the directive. The required maintenance actions vary depending on the age of the aircraft, ranging from software updates for newer models to hardware replacements for older units. This event has triggered notable financial fluctuations for major carriers and Airbus itself, while raising important questions regarding passenger compensation and the resilience of modern avionics against cosmic radiation.

Technical Analysis: The JetBlue Incident and Avionics Vulnerability

The investigation led by the National Transportation Safety Board (NTSB) and Airbus engineers pinpointed the root cause of the October 30 incident to a phenomenon known as a Single Event Upset (SEU). During the JetBlue flight, high-energy particles, attributed to solar flares or cosmic rays, struck the aircraft’s avionics system. This interaction caused a “bit flip” in the Thales ELAC 2 (Elevator Aileron Computer), changing a binary zero to a one, or vice versa. This microscopic alteration corrupted the data stream, leading the computer to interpret stable flight conditions as a command to initiate a dive, effectively overriding the autopilot systems.

The Role of the ELAC 2

The Elevator Aileron Computer (ELAC) is a critical component of the A320’s “fly-by-wire” architecture. It interprets pilot inputs and sensor data to manipulate the aircraft’s control surfaces, specifically the elevators for pitch control and ailerons for roll control. When the ELAC 2 experienced the radiation-induced data corruption, it commanded a sudden pitch-down maneuver. This highlights a specific vulnerability in modern, miniaturized electronics, which, while efficient, can be more susceptible to interference from high-energy atmospheric particles compared to older, larger components.

Industry experts have drawn parallels between this event and the Qantas Flight 72 incident in 2008. in that case, an Airbus A330 experienced a similar uncommanded pitch-down due to a data spike in its Air Data Inertial Reference Unit (ADIRU), also linked to cosmic radiation. These events underscore the challenge of designing redundancy systems that can distinguish between legitimate emergency maneuvers and data errors caused by transient environmental factors. The recurrence of such an event suggests that while rare, “bit flips” remain a persistent variable in aviation safety engineering.

“The fact that a single bit flip could cause a significant flight control excursion suggests a potential lack of sufficient redundancy or error-checking in the specific software version running on the ELAC 2.”, Aviation Safety Experts

Scope of the Fleet Action

The remedial action mandated by Airbus and EASA is divided into two distinct categories based on the hardware generation of the aircraft. Group 1, comprising approximately 4,000 newer aircraft, requires a software update. This process involves reverting the ELAC system to a previous software standard that has proven less sensitive to this specific type of data corruption. We understand that this update is relatively efficient, taking approximately 30 minutes per aircraft, allowing many carriers to perform the work overnight with minimal schedule disruption.

Group 2 presents a more complex logistical challenge. This group includes approximately 2,000 older aircraft that require a physical replacement of the ELAC unit. Unlike the software patch, this hardware intervention could ground affected planes for days or even weeks, depending on the availability of spare parts from the supplier, Thales. Supply-Chain analysts have warned that this requirement could strain the availability of avionics components, potentially extending the grounding period for airlines with older fleets.

Advertisement

Operational Impact and Market Reaction

The announcement on November 28, 2025, caused immediate and severe repercussions in the financial-results markets and airline flight schedules. Airbus SE shares dropped to a four-week low of €202.45, reflecting investor concern over the scale of the recall and the potential reputational impact regarding supply chain resilience. However, the swift issuance of the directive is also being viewed by some as a responsible and necessary step to prioritize safety above operational continuity.

Airline-Specific Disruptions

Carriers with heavy reliance on the A320 family are facing the steepest challenges. JetBlue, an all-Airbus operator, saw its stock value plummet by more than 28%. This drop was compounded by an already weak financial outlook for 2025. Similarly, Wizz Air shares fell by approximately 12%, with the airline cutting its profit guidance and citing the grounding of aircraft as a primary driver for the revision. In the Indian market, carriers like IndiGo and Air India are facing significant groundings, with hundreds of flight cancellations expected over the initial weekend following the announcement.

Conversely, legacy carriers with more diverse fleets appear to be better positioned to absorb the shock. American Airlines confirmed that while approximately 340 of its aircraft are affected, it expects to complete the necessary software updates within 24 to 48 hours. British Airways and EasyJet have signaled that they expect “some disruption,” but the impact is mitigated by their mix of newer aircraft and the ability to deploy alternative planes to cover affected routes.

Consumer Rights and Compensation

A major point of contention emerging from this crisis is the eligibility of passengers for compensation regarding delays and cancellations. Airlines are expected to classify these disruptions as “Extraordinary Circumstances” or force majeure, arguing that solar radiation is an act of nature beyond their control. Under Regulations like EU261 and UK261, such a classification would typically exempt airlines from paying compensation.

However, legal experts and passenger rights advocates are likely to challenge this stance. Precedents set by court cases such as Sturgeon v Condor and Huzar v Jet2 have established that technical problems inherent to the normal operation of an airline are not extraordinary. The argument follows that since cosmic radiation is a known risk of high-altitude flight, and avionics are specifically designed to be shielded against it, a failure of that shielding or software constitutes a technical defect rather than a freak weather event. We anticipate that while airlines may initially deny claims, legal challenges could eventually force payouts if courts rule that the component failure represents a manufacturing or design weakness.

Concluding Section

The precautionary fleet action initiated by Airbus represents a massive logistical undertaking and highlights the intricate relationship between advanced aviation technology and the natural environment. While the immediate focus is on the rapid deployment of software updates and hardware replacements to ensure passenger safety, the long-term implications involve a re-evaluation of avionics redundancy and supply chain robustness. The industry must balance the benefits of miniaturized, digital fly-by-wire systems with the necessity of hardening these systems against rare but high-impact environmental anomalies.

As the situation develops, the aviation sector will be closely monitoring the speed of the hardware rollout for the 2,000 older aircraft and the legal outcomes regarding passenger compensation. This event serves as a reminder that as aircraft become more digitally dependent, their vulnerability to non-traditional threats, such as cosmic radiation, requires constant vigilance and evolution in engineering standards.

FAQ

Question: What caused the Airbus fleet action?
Answer: The action was triggered by a JetBlue flight incident where intense solar radiation caused a “bit flip” in the flight control computer, leading to an uncommanded descent. This revealed a vulnerability in the Thales ELAC 2 unit.

Advertisement

Question: Which aircraft are affected?
Answer: Approximately 6,000 Airbus A320-family aircraft are affected. About 4,000 newer planes require a software update, while roughly 2,000 older planes require a hardware replacement.

Question: Is it safe to fly on an Airbus A320?
Answer: Yes. The Emergency Airworthiness Directive ensures that affected aircraft are either updated or grounded until fixed. Airlines are legally required to comply with these safety measures before operating the aircraft.

Question: Will I get compensation if my flight is cancelled?
Answer: It is currently debated. Airlines may claim “extraordinary circumstances” to avoid payouts, but legal precedents regarding technical defects suggest passengers may have grounds to claim compensation under EU261/UK261 regulations.

Sources

Sources: Airbus Press Release

Photo Credit: Airbus

Continue Reading
Advertisement
Click to comment

Leave a Reply

Regulations & Safety

Stolen Cessna 172 Crashes into Hangar at Van Nuys Airport

A stolen Cessna 172 crashed into a hangar at Van Nuys Airport. Suspect arrested; FAA and FBI investigate security breach at busy general aviation airport.

Published

on

This article summarizes reporting by NBC Los Angeles and Jonathan Lloyd.

Stolen Cessna 172 Crashes into Hangar at Van Nuys Airport

A security breach at Van Nuys Airports (VNY) early Thursday morning resulted in the theft and subsequent crash of a single-engine aircraft. According to reporting by NBC Los Angeles, a suspect broke into a flight school facility and attempted to commandeer a Cessna 172 before crashing the plane into a nearby hangar building. Authorities have confirmed that the aircraft never successfully became airborne.

Law enforcement officials, including the Los Angeles Airport Police (LAXPD) and the FBI, responded immediately to the scene. The suspect was taken into custody without incident, and no injuries were reported on the ground or in the aircraft. The incident has prompted a federal investigation into the security protocols at one of the world’s busiest general aviation airports.

Timeline of the Theft and Crash

The incident began in the pre-dawn hours of December 18, 2025. According to a timeline compiled from reports by NBC4 and KTLA, the suspect trespassed onto the airport grounds around 4:00 AM. The individual targeted a flight training facility located near the 7900 block of Balboa Boulevard, an area densely populated with Commercial-Aircraft academies and hangars.

The Break-in and Attempted Taxi

After gaining access to the flight school, the suspect boarded a white single-engine Cessna 172. Around 5:00 AM, the suspect attempted to operate the aircraft. NBC Los Angeles reports that the plane was stolen directly from the flight school’s ramp.

“A small plane crashed in a building at Van Nuys Airport after it was stolen from a flight school, officials tell NBC4 Investigates.”

— NBC Los Angeles

While the suspect managed to start the engine and begin taxiing, they lost control of the aircraft before reaching a runway. The plane surged forward and impacted a hangar nose-first. Aerial video footage broadcast by KTLA showed the aircraft’s nose embedded in the metal siding of the structure, leaving a distinct hole in the exterior wall. The propeller and nose cone sustained significant damage, rendering the aircraft inoperable.

Suspect and Legal Proceedings

Following the crash, LAXPD officers arrested the suspect at the scene. CBS Los Angeles and other local outlets have identified the individual as 37-year-old Ceffareno Michael Logan. He was booked on suspicion of burglary and theft of an aircraft.

Advertisement

According to verified reports from Patch and NTD News, bail for Logan has been set at $150,000. As of the latest updates, authorities have not disclosed a motive for the theft, nor have they confirmed whether the suspect possessed any prior flight training or a pilot’s license. The swift arrival of law enforcement prevented any further attempts to move the aircraft or flee the scene.

Investigation and Aftermath

The investigation has expanded beyond local police to include federal agencies. Both the Federal Bureau of Investigation (FBI) and the Federal Aviation Administration (FAA) are on-site to assist LAXPD. Their inquiry will likely focus on how the suspect breached the perimeter and accessed the aircraft keys or ignition system.

Crews were observed later in the morning extracting the damaged Cessna from the hangar wall and towing it back to the flight academy’s facility. Despite the dramatic nature of the event, airport operations at Van Nuys were not significantly disrupted, as the crash was contained within the flight school’s specific ramp area.

AirPro News Analysis: General Aviation Security

While commercial airports operate under the strict passenger screening protocols of the TSA, general aviation (GA) airports like Van Nuys face different security challenges. VNY is a massive facility with multiple access points for Private-Jets businesses, hangars, and flight schools. This incident highlights the vulnerability of “insider” areas where aircraft are parked.

Although rare, the theft of aircraft is a known risk in the aviation industry. In 2018, a ground service agent stole a Q400 turboprop from Seattle-Tacoma International Airport, a tragedy that ended in a fatal crash. Fortunately, in this instance at Van Nuys, the suspect failed to achieve flight, preventing a potentially catastrophic outcome over the densely populated San Fernando Valley. We anticipate this event will trigger a review of after-hours key storage and perimeter security standards for flight schools operating at VNY.

Sources

Photo Credit: KTLA5

Continue Reading

Regulations & Safety

US Government Admits Liability in 2025 Washington DC Mid-Air Collision

The U.S. government admits fault in the 2025 mid-air collision near Ronald Reagan Washington National Airport that killed 67, citing FAA and Army errors.

Published

on

This article summarizes reporting by AP News.

US Government Admits Liability in Fatal Collision Between American Eagle Jet and Army Helicopter

In a significant legal development following the deadliest United States aviation accident since 2001, the U.S. government has formally admitted liability for the mid-air collision that claimed 67 lives earlier this year. According to court filings submitted in December 2025, the Department of Justice acknowledged that negligence by both Federal Aviation Administration (FAA) air traffic controllers and U.S. Army pilots caused the tragedy.

The crash, which occurred on January 29, 2025, involved American Eagle Flight 5342 and a U.S. Army Black Hawk helicopter operating near Ronald Reagan Washington National Airport (DCA). As reported by AP News, the government’s admission comes in response to a lawsuit filed by the family of a victim, signaling a potential shift in how the remaining legal battles regarding the disaster will proceed.

Government Concedes Negligence in Court Filing

The lawsuit, filed by the family of passenger Casey Crafton, alleges that failures in communication and protocol led directly to the catastrophe. In a move that legal experts describe as unusually swift for complex aviation litigation, the government did not contest its role in the accident.

In the filing, the government stated that it:

“owed a duty of care to plaintiffs, which it breached.”

, U.S. Department of Justice filing, via AP News

By admitting liability, the government effectively removes the need for a trial to determine fault regarding its own agents (the FAA and the Army). The legal focus will likely shift toward determining the amount of damages owed to the families of the 64 people on the regional jet and the three crew members on the helicopter.

Operational Failures Behind the Crash

The collision occurred at night while the American Eagle CRJ700, operated by PSA Airlines, was on approach to DCA from Wichita, Kansas. The Black Hawk helicopter was conducting a training mission involving night vision goggles. Investigations cited by AP News and preliminary NTSB data highlight two primary causes for the disaster: air traffic control errors and pilot deviations.

Advertisement

FAA Controller Errors

According to the reports, the FAA controller at DCA utilized “visual separation” procedures, asking the helicopter pilots if they had the incoming jet in sight. Once the pilots confirmed they did, the controller transferred the responsibility for maintaining safe distance to the helicopter crew. Following the incident, the FAA has reportedly restricted the use of visual separation for helicopters operating in this congested airspace.

Army Pilot Deviations

The government’s admission also encompasses errors made by the Army flight crew. Investigators found that the helicopter was flying significantly higher than permitted for its specific route. While the limit for “Route 4” was 200 feet, the Black Hawk was operating between 278 and 300 feet, approximately 78 feet above the ceiling for that corridor.

Furthermore, technical discrepancies were noted in the helicopter’s equipment. The investigation revealed that the barometric altimeter may have displayed an altitude 80 to 100 feet lower than the aircraft’s actual position, potentially misleading the pilots. The use of night vision goggles was also cited as a factor that may have limited the crew’s peripheral vision and depth perception.

AirPro News Analysis

The speed at which the U.S. government admitted liability, less than a year after the incident, is notable. In many aviation disasters involving state actors, litigation can drag on for years over jurisdictional and immunity claims. We assess that this early admission is likely a strategic decision to limit the scope of discovery. By conceding fault now, the government may prevent a prolonged public trial that would expose granular, potentially sensitive details regarding military training operations and air traffic control systemic vulnerabilities in the nation’s capital.

Ongoing Legal Disputes with Airlines

While the government has accepted its share of the blame, the legal battle continues for the private carriers involved. American Airlines and its regional subsidiary, PSA Airlines, are also named defendants in the lawsuit. Both airlines have filed motions to dismiss the complaints against them, arguing that the sole responsibility lies with the government entities that controlled the airspace and the military aircraft.

Attorneys for the victims’ families, however, argue that the airlines failed to mitigate known risks associated with flying into the highly congested airspace around Washington, D.C. The outcome of these motions will determine whether the airlines must also pay damages or if the U.S. taxpayers will bear the full financial burden of the settlements.

Frequently Asked Questions

When is the final NTSB report expected?
The National Transportation Safety Board is expected to release its final report on the probable cause of the accident in early 2026.

What safety changes have been made since the crash?
The FAA has permanently closed the specific helicopter route (Route 4) involved in the crash. Additionally, regulators have prohibited the simultaneous use of certain runways at DCA during urgent helicopter missions and restricted visual separation procedures for helicopters.

Advertisement

How many people died in the accident?
The crash resulted in 67 total fatalities: 60 passengers and 4 crew members on the regional jet, and 3 crew members on the Army helicopter.

Sources

Photo Credit: NBC News

Continue Reading

Regulations & Safety

Why Proper Maintenance of Aircraft Wheel Bearings Is Critical for Safety

Airbus technical data shows aircraft wheel bearing failures result mainly from maintenance errors. Proper torque, cleaning, and lubrication are essential for safety.

Published

on

This article is based on technical guidance and safety publications from Airbus and additional industry safety reports.

The Hidden Danger in the Gear: Why Wheel Bearing Maintenance Cannot Be Rushed

Aircraft wheel bearings are among the most stressed components in aviation. Despite supporting loads of up to 500 tons and enduring temperature shifts from sub-zero cruising altitudes to the intense heat of braking, they remain largely hidden from view. According to a technical safety publication by Airbus, the failure of these components is rarely due to design flaws but is almost exclusively the result of improper maintenance.

At AirPro News, we have reviewed the latest guidance from Airbus’s “Safety First” initiative, alongside broader industry data, to understand why these small components continue to pose significant risks to flight safety. The consensus across manufacturers and regulators is clear: strict adherence to maintenance protocols is the only barrier against catastrophic failure.

The Mechanics of Failure

The primary cause of bearing failure, as identified by Airbus and industry data, is maintenance error. Specifically, the issues revolve around incorrect torque application, contamination, and inadequate lubrication. Aircraft use “tapered roller bearings” designed to handle both the weight of the aircraft (radial loads) and side-to-side movement (axial loads). When these bearings are mistreated, the consequences are severe.

The “Double-Torque” Procedure

One of the most critical and frequently misunderstood aspects of wheel installation is the torque procedure. According to Airbus technical guidelines, a specific “double-torque” method is required to ensure the bearings are seated correctly without being overtightened.

The process generally involves three distinct steps:

  1. Initial Seating: A high torque is applied while rotating the wheel. This step is crucial to “seat” the rollers and eliminate free play.
  2. Back-off: The nut is loosened to relieve stress on the components.
  3. Final Torque: A specific, lower torque is applied to set the correct “preload.”

The risk lies in the details. If a technician skips rotating the wheel during the initial torque application, the rollers may not align, leading to a false torque reading. This can result in loose bearings that vibrate and wear prematurely, or tight bearings that overheat and seize.

Real-World Consequences

The failure of a wheel bearing is not merely a maintenance inconvenience; it is a direct threat to the structural integrity of the aircraft. When a bearing seizes, it can generate enough friction to weld components together or shear axles, leading to wheel separation.

Airbus and TSB Canada Data

In one notable case study highlighted by Airbus, an A330 aircraft lost a wheel during takeoff. The investigation revealed that a seized bearing destroyed the axle nut, allowing the wheel to eject from the landing gear. This is not an isolated event. Data from the Transportation Safety Board of Canada (TSB) underscores the prevalence of this issue.

Advertisement

“A study revealed 67 occurrences of nosewheel bearing failures on A319/A320/A321 aircraft worldwide between 1989 and 2004.”

— TSB Canada Data

Cross-Fleet Vulnerabilities

While the Airbus “Safety First” article focuses on their fleet, the physics of bearing failure applies universally. Reports from the UK Air Accidents Investigation Branch (AAIB) detail an incident involving a Boeing 737-800 where a seized bearing generated sufficient heat to compromise the chrome plating and base metal of the axle, causing it to fracture.

Similarly, an investigation into an Embraer EMB-145 (registration G-EMBP) found that moisture contamination due to improper seal installation led to severe overheating and subsequent axle failure. These incidents confirm that regardless of the airframe manufacturer, the root causes, contamination and torque errors, remain consistent.

Industry Best Practices

To mitigate these risks, manufacturers and technical organizations like Timken have established “gold standard” maintenance manuals. The following practices are considered non-negotiable for airworthiness:

  • Cleaning is Critical: Technicians must remove all old grease. Old lubricant can hide “spalling” (flaking metal) or heat discoloration (blue or straw-colored metal), which are early signs of fatigue and overheating.
  • Pressure Packing: Hand-packing grease is often insufficient. Industry standards recommend using pressure packing tools to ensure grease penetrates behind the cage where the rollers contact the race.
  • Grease Compatibility: Mixing clay-based and lithium-based greases can cause the mixture to break down, destroying its lubricating properties. Lithium-based grease is generally preferred for its water-repelling capabilities.
  • Wheel Rotation: As emphasized in the torque procedure, the wheel must be rotated while tightening the nut to align the rollers.

AirPro News Analysis

The Human Factor in Maintenance

While the technical steps are well-documented, we believe the persistence of these failures points to a human factors challenge. Wheel bearings are “hidden” components; unlike a tire that shows visible tread wear, a bearing often looks pristine until the moment it fails catastrophically. This lack of visual feedback places an immense burden on the maintenance process itself.

In high-pressure line maintenance environments, the requirement to rotate a wheel while torquing it, a process that relies on “feel” and patience, can be a trap for technicians rushing to clear an aircraft for departure. The data suggests that safety in this domain relies less on new technology and more on a disciplined adherence to the basics: cleaning, inspecting, and respecting the torque procedure.

Regulatory Context

Regulators continue to monitor these risks closely. The FAA has previously issued Airworthiness Directives, such as AD 2012-10-09 for Cessna 560XL aircraft, following reports of brake failure linked to loose bearing components. Furthermore, the FAA Safety Team (FAASTeam) frequently issues alerts reminding operators that “grease is not just grease,” warning that using unapproved substitutes constitutes a violation of FAR Part 43.

Whether operating a General Aviation aircraft or a commercial airliner, the message from the industry is uniform: take care of the wheel bearings, and they will carry the load.

Advertisement

Sources

Photo Credit: Airbus

Continue Reading
Advertisement

Follow Us

newsletter

Latest

Categories

Tags

Popular News