Connect with us

Regulations & Safety

Challenger 650 Crash in Maine Linked to De-Icing Limits and Wing Sensitivity

The Challenger 650 crash in Maine was linked to exceeded anti-icing fluid holdover time and wing contamination during heavy snow conditions.

Published

on

Challenger 650 Crash in Maine Linked to De-Icing Limits and Wing Sensitivity

A Bombardier Challenger 650 crashed shortly after takeoff from Bangor International Airport (BGR) on January 25, 2026, resulting in the loss of all six lives on board. According to analysis by the Aircraft Owners and Pilots Association (AOPA), the accident sequence suggests a loss of control caused by wing contamination, occurring as a severe winter storm impacted the region.

The aircraft, registered as N10KJ, was departing for France when it stalled and rolled moments after lifting off the runway. Preliminary data indicates that the time elapsed between the application of anti-icing fluid and the attempted takeoff may have exceeded the fluid’s effective life, known as “holdover time” (HOT). This tragedy has renewed industry focus on the specific aerodynamic sensitivities of the Challenger 600 series wings during winter operations.

The Critical Timeline: Exceeding the Holdover Time

Aviation safety experts and reporting from AOPA highlight the “Holdover Time” (HOT) as the central factor in the investigation. HOT refers to the estimated duration that de-icing and anti-icing fluids can prevent frozen contaminants from adhering to an aircraft’s surfaces. The length of this protection window fluctuates drastically based on precipitation type and intensity.

The Eight-Minute Gap

According to the available timeline, the Challenger 650 was treated with Type IV anti-icing fluid, a thick, green fluid designed to prevent ice accumulation, before taxiing for departure. Approximately eight minutes elapsed between the fluid application and the takeoff clearance. While Type IV fluid can provide protection for over 30 minutes in mild conditions, its effectiveness degrades rapidly in moderate to heavy snow.

AOPA analysis suggests that with visibility at the airport reported around 3/4 of a mile and temperatures near 3°F (-16°C), the snowfall intensity would likely be classified as moderate or heavy. Under these specific conditions, the effective holdover time for the fluid could drop to between two and nine minutes, or potentially zero minutes in heavy snow, rendering the protection ineffective before the aircraft even began its takeoff roll.

Corroboration from Allegiant Air

Further evidence of the extreme conditions emerged from a commercial flight operating at the same airport. Reports from Flight Global and Simple Flying indicate that an Allegiant Air Boeing 737 crew aborted their takeoff moments before the Challenger crash. The commercial crew reportedly radioed that their anti-ice fluid had failed and snow was sticking to the aircraft, citing unsafe visibility and surface conditions. This contemporaneous account strongly suggests that the weather had overwhelmed standard anti-icing measures at the airport.

The “Hard Wing” Vulnerability

The Bombardier Challenger 600 series, which includes the 601, 604, 605, and the 650 involved in this accident, utilizes a specific wing design that requires strict adherence to the “Clean Wing” concept.

Lack of Leading-Edge Slats

Unlike many other transport-category aircraft, the Challenger 600 series features a “hard wing” design, meaning it lacks leading-edge slats. Slats are movable aerodynamic surfaces on the front of the wing that extend to generate additional lift at low speeds. Without them, the wing is highly efficient at cruise speeds but becomes extremely intolerant to surface roughness or contamination during takeoff.

Advertisement

According to NTSB safety alerts and historical data cited by AOPA, ice accumulation as thin as 1/64th of an inch, comparable to the texture of medium-grit sandpaper, can disrupt airflow over the Challenger’s wing enough to cause a stall. This aerodynamic stall often manifests as an uncommanded roll immediately after the aircraft rotates, a sequence that matches preliminary descriptions of the Bangor crash.

Historical Precedents

The aviation industry has seen similar accidents involving this airframe family. Notable incidents include:

  • Birmingham, UK (2002): A Challenger 604 crashed on takeoff due to frost contamination on the wings.
  • Montrose, Colorado (2004): A Challenger 601 was lost during takeoff in light snow and mist, similarly attributed to wing contamination.

Investigation and Victim Identification

The National Transportation Safety Board (NTSB) and the FAA have launched a comprehensive investigation into the crash. Investigators are expected to focus on the specific fluid mixture used, the exact timeline of events, and the decision-making process regarding the weather conditions.

Local news outlets and the Bangor Daily News have identified the victims, who were traveling back to Europe after a fuel stop. The aircraft was owned by KTKJ Challenger LLC, an entity linked to the Houston-based law firm Arnold & Itkin. Among the identified victims were pilot Jacob Hosmer, passenger Tara Arnold (wife of the firm’s co-founder), and passenger Shawna Collins.

AirPro News Analysis

This tragedy underscores the unforgiving nature of winter flying, particularly for aircraft with high-performance laminar flow wings. While regulations regarding the “Clean Wing” concept are absolute, prohibiting takeoff with any adhering frost, ice, or snow, the practical application relies heavily on estimated holdover times. When weather conditions border on “heavy” snow, the margin for error evaporates. The corroborating report from the Allegiant Air crew suggests that the conditions at Bangor may have been beyond the capability of current anti-icing fluids, creating a scenario where no holdover time was sufficient.

Frequently Asked Questions

What is a “Hard Wing”?
A “hard wing” refers to an aircraft wing design that does not have leading-edge slats (movable devices that help create lift). This design is common on the Challenger 600 series and requires the wing surface to be perfectly clean to generate lift safely.
What is Type IV fluid?
Type IV is a thickened, green anti-icing fluid applied to aircraft surfaces to prevent ice from forming. It is designed to shear off the wing during the takeoff roll.
Why did the fluid fail in 8 minutes?
In heavy precipitation or extreme cold, the fluid becomes diluted by the falling snow more quickly. Once diluted beyond a certain point, it loses its protective properties, allowing ice to bond to the wing.

Sources

Photo Credit: AOPA

Continue Reading
Advertisement
Click to comment

Leave a Reply

Regulations & Safety

NTSB Investigates Runway Near-Collision at Newark Liberty Airport

On March 17, 2026, Alaska Airlines and FedEx planes nearly collided on intersecting runways at Newark Liberty. NTSB and FAA investigations are underway.

Published

on

This article is based on an official press release from the National Transportation Safety Board (NTSB).

Federal aviation authorities have launched urgent investigations into a serious runway incursion and close call at Newark Liberty International Airport (EWR). On the evening of Tuesday, March 17, 2026, a commercial passenger jet and a heavy cargo freighter came dangerously close to colliding while attempting to land.

According to an official public statement released by the National Transportation Safety Board (NTSB), the incident involved an Alaska Airlines passenger flight and a FedEx Express Cargo-Aircraft. The conflict occurred as both aircraft were navigating simultaneous approaches to intersecting runways, a complex maneuver requiring precise air traffic control (ATC) sequencing.

Disaster was ultimately averted by a last-second intervention from air traffic controllers. The event has renewed industry-wide scrutiny on airport runway configurations, ATC staffing levels, and the safety margins protecting the nation’s most congested airspace.

The Incident at Newark Liberty

Flight Details and Convergence

Based on preliminary incident reports, the conflict began at approximately 8:17 PM local time. Alaska Airlines Flight 294, operating a Boeing 737 MAX 9 arriving from Portland International Airport (PDX), and a FedEx Express Boeing 777 freighter arriving from Memphis International Airport (MEM), were both on their final descent into Newark.

The NTSB confirmed the core details of the convergence in their initial public disclosure:

The NTSB is investigating a close call at Newark Liberty Airport on March 17 in which an Alaska Airlines Boeing 737 overflew a FedEx Boeing 777 while both jets were attempting to land on crossing runways.

The Critical Go-Around

As the two Boeing aircraft converged on the intersecting runways, separation margins deteriorated rapidly. Preliminary flight tracking data indicates that the planes passed each other with a vertical and horizontal separation of roughly 300 to 325 feet (approximately 90 meters).

When the Alaska Airlines 737 MAX 9 descended to an estimated 150 feet above ground level, seconds away from touchdown, air traffic controllers recognized the imminent collision risk. Controllers immediately issued an urgent “go-around” instruction to the Alaska Airlines crew. The pilots complied without hesitation, aborting their landing and climbing sharply away from the FedEx freighter. The FedEx plane continued its approach and landed safely. No injuries to passengers or crew, and no damage to either aircraft, were reported.

Advertisement

Official Investigations and Systemic Context

NTSB and FAA Response

Both the NTSB and the Federal Aviation Administration (FAA) have officially opened investigations into the March 17 incident. The primary focus of these inquiries will be to determine the root cause of the sequencing failure that allowed the two aircraft to breach standard safety buffers.

Investigators are currently securing and analyzing radar data, ATC audio communications, and the flight data recorders from both the Alaska Airlines and FedEx aircraft. The agencies will evaluate whether the loss of separation was the result of human error, technological shortcomings, or systemic operational strains at the airport.

AirPro News analysis

We note that Newark Liberty International Airport frequently utilizes intersecting runways to boost overall flight throughput. While this is a standard and highly efficient operational feature used to manage heavy traffic in the New York metropolitan airspace, it requires flawless coordination. Any miscalculation in timing or communication can lead to severe runway incursions.

This incident puts a renewed spotlight on the ongoing strain within the U.S. air traffic control system. Newark operates within one of the most complex pieces of airspace in the country, making it particularly vulnerable to sequencing challenges. Furthermore, this event adds to a growing list of highly publicized near-misses at major U.S. airports over the past few years, which have previously prompted the FAA to hold emergency safety summits.

However, while the 300-foot proximity of the two aircraft is undeniably alarming, aviation safety experts often emphasize that such incidents demonstrate the resilience of the system. The final layers of aviation safety, specifically, vigilant ATC monitoring and immediate pilot responsiveness, functioned exactly as designed to prevent a catastrophic accident.

Frequently Asked Questions

What happened at Newark Airport on March 17, 2026?

An Alaska Airlines Boeing 737 MAX 9 and a FedEx Boeing 777 freighter experienced a close call when both aircraft attempted to land on intersecting runways at the same time. Air traffic control issued a last-minute go-around order to the Alaska Airlines flight, preventing a collision.

How close did the two planes get?

Preliminary data suggests the two aircraft passed within 300 to 325 feet of each other before the Alaska Airlines crew aborted their landing at approximately 150 feet above the ground.

Who is investigating the incident?

The National Transportation Safety Board (NTSB) and the Federal Aviation Administration (FAA) are both conducting official investigations into the event.

Advertisement

Sources

Photo Credit: FlightRadar24 – aviationbrk

Continue Reading

Regulations & Safety

FAA Suspends Visual Separation Between Airplanes and Helicopters in Busy Airspace

FAA mandates radar separation for airplanes and helicopters in Class B, C, and TRSA airspace to improve safety after 2025 mid-air collision.

Published

on

This article is based on an official press release from the Federal Aviation Administration.

The Federal Aviation Administration (FAA) and U.S. Transportation Secretary Sean P. Duffy have announced a sweeping new safety protocol aimed at preventing mid-air collisions between airplanes and helicopters. The new measure, issued as a general notice (GENOT), officially suspends the use of visual separation between these aircraft types in busy airspace sectors.

According to the FAA’s press release, air traffic controllers will now be required to use radar to actively manage and separate airplanes and helicopters at specific lateral or vertical distances. The rule applies to Class B and Class C airspace, as well as Terminal Radar Service Areas (TRSA), where helicopters frequently cross arrival and departure paths.

This regulatory shift follows a year-long review by the FAA’s safety team, which utilized artificial intelligence tools to analyze cross-traffic data and incident reports nationwide. The review was prompted by a tragic mid-air collision near Ronald Reagan Washington National Airport (DCA) in early 2025.

Moving Away from “See and Avoid”

Historically, visual separation allowed air traffic controllers to advise pilots of nearby traffic, shifting the responsibility to the flight crews to remain visually clear of other aircraft. However, the FAA’s recent data analysis concluded that this “see and avoid” method is no longer a sufficient safety mitigation tool in high-traffic areas.

FAA Administrator Bryan Bedford emphasized the need for proactive risk mitigation in the agency’s official statement.

“Following the mid-air collision near Ronald Reagan Washington National Airport (DCA), we looked at similar operations across the national airspace. We identified an overreliance on pilot ‘see and avoid’ operations that contribute to safety events involving helicopters and airplanes,” Bedford said.

The agency highlighted two recent near-miss incidents that underscored the urgency of the new mandate. On February 27, 2026, American Airlines Flight 1657 on final approach to San Antonio International Airport was forced into a converging course with a police helicopter, which had to make an evasive left-hand turn. Just days later, on March 2, 2026, a Beechcraft 99 landing at Hollywood Burbank Airport experienced a similar conflict with a helicopter that required an evasive right-hand turn.

Operational Impacts and Priority Clearances

The suspension of visual separation is expected to have immediate operational impacts on both helicopter operators and commercial airlines. The FAA noted that helicopter pilots, who are accustomed to receiving immediate approval to transit through certain busy areas, may now face routing adjustments or delays while controllers establish safe radar separation.

Advertisement

Furthermore, the new protocol includes provisions for urgent missions. When helicopter pilots conducting medical or law enforcement operations request clearance through heavy-traffic zones, commercial airline operations may experience disruptions to accommodate these priority flights.

U.S. Transportation Secretary Sean P. Duffy framed the changes as part of a broader, ongoing effort to reform airspace safety following the DCA tragedy a year ago.

“The tragedy over the Potomac one year ago revealed a startling truth: years of warning signs were missed, and the FAA needed dire reform,” Duffy stated in the release. “Using innovative data analysis, the safety team at the FAA has identified the need for enhanced protocols at all airports across the National Airspace System.”

AirPro News analysis

We note that the FAA’s decision to suspend visual separation in Class B, Class C, and TRSA airspace represents a significant operational shift for air traffic control. By mandating radar separation for mixed airplane and helicopter traffic, the agency is prioritizing absolute spatial deconfliction over the efficiency previously afforded by visual flight rules in terminal areas. While this will undoubtedly enhance safety margins and reduce the risk of mid-air collisions, it is likely to increase the workload for air traffic controllers and introduce new complexities in managing arrival and departure flows at the nation’s busiest airports. The reliance on AI tools to evaluate these high-volume areas suggests a modernization of the FAA’s approach to airspace risk management, moving from reactive measures to data-driven, proactive policymaking.

Frequently Asked Questions

What is visual separation?

Visual separation is an air traffic control procedure where controllers advise pilots of nearby aircraft and allow the pilots to maintain safe distances visually, rather than relying on standard radar separation distances.

Where does the new FAA rule apply?

According to the FAA, the suspension of visual separation between airplanes and helicopters applies to Class B and Class C airspace, as well as Terminal Radar Service Areas (TRSA).

Will this affect commercial airline flights?

Yes. The FAA has indicated that airline operations may face disruptions or delays when urgent medical or law enforcement helicopters require priority clearance through heavy-traffic areas under the new radar separation rules.

Sources: Federal Aviation Administration

Photo Credit: FAA

Advertisement
Continue Reading

Regulations & Safety

Virgin Australia Flight Emergency Due to Vape Battery Fire in Cabin

Virgin Australia flight VA328 made an emergency landing at Melbourne after a vape’s lithium-ion battery caught fire, with no injuries reported.

Published

on

This article summarizes reporting by ABC News.

A Virgin Australia flight from Brisbane to Melbourne was forced to declare a mid-air emergency on Sunday, March 15, 2026, after a passenger’s vape device caught fire in the cabin. According to reporting by ABC News, the incident prompted an immediate and large-scale response on the ground.

“A Virgin Australia flight makes an emergency landing at Melbourne Airport after a vape caught fire onboard,” reported ABC News.

Flight VA328, operated by a Boeing 737-800, was on its descent when the lithium-ion battery inside the e-cigarette experienced a thermal runaway. The swift actions of the cabin crew, who utilized a fire-proof containment bag, prevented any injuries or structural damage to the aircraft.

The event highlights the ongoing and severe risks associated with lithium-ion batteries in aviation, reinforcing why global aviation regulators mandate that such devices remain strictly in the passenger cabin rather than the cargo hold.

The In-Flight Emergency and Crew Response

Smoke in the Cabin

As the Boeing 737-800 (registration VH-YFU) neared Melbourne, flight attendants noticed smoke, a hissing noise, and small flames coming from a passenger’s vape. According to incident reports, the crew immediately followed standard operating procedures for onboard battery fires.

They successfully isolated the burning device and secured it inside a specialized fire-proof containment bag. To provide the cabin crew with the necessary time to manage the hazard safely, the flight deck executed a missed approach before continuing their final descent.

Declaring a PAN Call

During the incident, the pilots transmitted a “PAN” call to air traffic control. This internationally recognized urgency signal indicates a serious situation requiring priority handling, though it falls short of a “Mayday” life-threatening emergency. The transmission ensured that ground control was fully aware of the unfolding situation and could prepare accordingly.

Ground Coordination and Safe Landing

Priority Clearance at Melbourne Airport

Upon receiving the PAN call, air traffic controllers at Melbourne Airport placed several other arriving flights into holding patterns. This air traffic management decision ensured Flight VA328 had immediate and priority clearance to land without delay.

Advertisement

Simultaneously, a massive precautionary response was activated on the ground. More than 17 emergency vehicles, including fire engines, ambulances, and airport response units, were deployed and positioned along the runway on standby.

Post-Landing Procedures

The aircraft touched down safely between 4:20 p.m. and 4:45 p.m. AEDT. Aviation Rescue Firefighters met the plane on the tarmac, escorted it to the gate, and boarded to safely remove the damaged e-cigarette. Passengers disembarked normally without requiring any medical assistance.

Aviation Rules and Lithium-Ion Risks

The Danger of Thermal Runaway

Vape devices are powered by lithium-ion batteries, which can enter a state of “thermal runaway” if damaged, short-circuited, or faulty. This uncontrollable chain reaction produces intense heat, toxic smoke, and flames.

Aviation safety regulators worldwide require that vapes and power banks be carried exclusively in the passenger cabin as carry-on baggage. This rule exists so that if a fire occurs, the crew can detect and extinguish it immediately, a scenario that could be catastrophic if it occurred undetected in the cargo hold.

Airline Policies and Legal Implications

Virgin Australia strictly prohibits the use or charging of vapes and power banks during flights. Furthermore, vaping on an aircraft is a federal offense under Australian law. Accidental fires caused by negligence, such as the improper packing of a battery, can trigger investigations by the Civil Aviation Safety Authority (CASA), potentially resulting in substantial fines for the offending passenger.

AirPro News analysis

We observe that this incident is part of a growing industry concern regarding personal electronic devices. In July 2025, Virgin Australia experienced a similar scare when a passenger’s power bank ignited in an overhead locker on a flight from Sydney to Hobart, prompting major Australian carriers to introduce stricter guidelines.

The successful resolution of Flight VA328 demonstrates that current aviation safety protocols are highly effective when executed properly. The mandate to keep battery-operated devices in the cabin, combined with the availability of fire-proof containment bags, worked exactly as intended to avert a potential disaster. However, it also underscores the critical need for continued passenger education regarding the safe transport of lithium-ion batteries, as many travelers remain unaware of the severe risks these everyday items pose at altitude.

Frequently Asked Questions

Why are vapes allowed on planes if they are a fire risk?

Vapes and power banks must be kept in carry-on baggage so that if a battery malfunctions and catches fire, cabin crew can immediately detect and extinguish it. If these devices were placed in checked luggage, a fire in the cargo hold could go unnoticed until it becomes uncontrollable.

Advertisement

Was anyone injured on Virgin Australia Flight VA328?

No injuries were reported among the passengers or crew. The cabin crew successfully contained the fire, and the aircraft sustained no structural damage.

Can you use a vape on a commercial flight?

No. Virgin Australia, along with all other major airlines, strictly prohibits the use or charging of vapes during flights. Vaping on an aircraft is a federal offense in Australia and can lead to severe penalties.

Sources

Photo Credit: Virgin Australia

Continue Reading
Every coffee directly supports the work behind the headlines.

Support AirPro News!

Advertisement

Follow Us

newsletter

Latest

Categories

Tags

Every coffee directly supports the work behind the headlines.

Support AirPro News!

Popular News