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.
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.
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.
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.
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. 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.
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.
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.
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.
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.
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. No injuries were reported among the passengers or crew. The cabin crew successfully contained the fire, and the aircraft sustained no structural damage.
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.
The In-Flight Emergency and Crew Response
Smoke in the Cabin
Declaring a PAN Call
Ground Coordination and Safe Landing
Priority Clearance at Melbourne Airport
Post-Landing Procedures
Aviation Rules and Lithium-Ion Risks
The Danger of Thermal Runaway
Airline Policies and Legal Implications
AirPro News analysis
Frequently Asked Questions
Why are vapes allowed on planes if they are a fire risk?
Was anyone injured on Virgin Australia Flight VA328?
Can you use a vape on a commercial flight?
Sources
Photo Credit: Virgin Australia
Regulations & Safety
NTSB Preliminary Report on 2026 Deerfield Cessna Crash
The NTSB preliminary report details a 1976 Cessna crash near Deerfield, Illinois, highlighting severe weather and erratic flight path factors.
This article is based on an official preliminary report from the National Transportation Safety Board (NTSB), supplemented by third-party reporting and aviation data.
On Wednesday, March 4, 2026, a 1976 Cessna T210M Turbo Centurion crashed into a residential neighborhood in an unincorporated area of Lake County near Deerfield, Illinois. The sole occupant and pilot, 75-year-old Chester Wojnicki, was killed upon impact. Miraculously, despite the aircraft striking a densely populated townhome complex, there were no injuries reported on the ground.
The National Transportation Safety Board (NTSB) has released its preliminary report regarding the incident. The ongoing investigation is currently focusing on severe weather conditions, erratic flight tracking data, and the potential for spatial disorientation during the aircraft’s final approach to Chicago Executive Airport.
We are reviewing the NTSB’s initial findings, alongside flight tracking data and local emergency response reports, to understand the sequence of events that led to this tragic aviation accident.
According to the NTSB preliminary data and flight tracking information from Global ADS-B Exchange, the flight departed from Dane County Regional Airport in Madison, Wisconsin, at 8:49 p.m. CST. The intended destination was Chicago Executive Airport in Wheeling, Illinois.
Weather conditions were rapidly deteriorating as the aircraft neared its destination. METAR data recorded heavy fog, low clouds, and poor visibility in the area. A weather report issued just 10 minutes after the 9:45 p.m. crash indicated a vertical visibility of only 200 feet and a ground visibility of half a statute mile.
The NTSB’s preliminary findings highlight an erratic flight path during the pilot’s attempted GPS approach to Runway 16. ADS-B data shows the aircraft was consistently flying below the approach’s minimum required altitudes, beginning from the initial approach fix.
Furthermore, the aircraft deviated left and right of the designated course prior to impacting the terrain. Air traffic control (ATC) audio suggests the pilot may have experienced confusion regarding his altitude and proximity to the ground in the final minutes of the flight. The control tower lost contact with the aircraft shortly before the crash, and no distress signals or Mayday calls were reported. The aircraft impacted the ground 2.6 nautical miles northwest of the destination runway, on the 800 block of Swallow Street. Witnesses reported hearing the plane strike the tops of trees before crashing into the backyard of the townhome complex.
During the crash, the plane clipped a roofline and severed two Nicor gas meters, embedding its propeller into the side of a home. First responders from the Lincolnshire-Riverwoods Fire Protection District and local utility crews quickly secured the area, containing a minor gas leak and preventing any post-crash fire. All townhomes remained habitable following the incident.
The Lake County Coroner’s Office confirmed that the pilot, Chester Wojnicki of Mount Prospect, Illinois, died from blunt force injuries sustained in the crash. Wojnicki was a highly experienced aviator and served as the president of the American Polish Aero Club Chicago (APA).
The local aviation community remembers him as a generous and mechanically skilled individual who owned a local electrical and heating repair business. Neighbors in the townhome complex expressed profound relief that the crash did not result in a larger catastrophe. Speaking to CBS News, one local resident highlighted the miraculous outcome for the neighborhood:
“For 50 years, planes have been flying over this area… it’s very, very fortunate that the lord was watching over us last night.”
While the NTSB preliminary report provides raw data and factual observations from the crash site, a final probable cause report will likely take 12 to 24 months to be published.
Based on the preliminary data, aviation safety experts, including analysts at the AOPA Air Safety Institute, suggest that spatial disorientation is a highly probable factor in this accident. Spatial disorientation occurs when a pilot loses their sense of direction, altitude, or airspeed. This physiological condition is frequently exacerbated by night flying in heavy fog and zero-visibility environments.
The combination of a 200-foot ceiling, a high-workload instrument approach, and potential confusion during ATC advisories creates a scenario where even veteran pilots can become disoriented. The absence of a Mayday call further supports the theory that the pilot may not have realized the severity of the altitude deviation until the final seconds of the flight. We will continue to monitor the NTSB’s ongoing investigation for further official updates and safety recommendations.
When did the Deerfield plane crash occur? What type of aircraft was involved? Were there any injuries on the ground?
Flight Details and Deteriorating Weather
Erratic Approach and ATC Communication
Ground Impact and Community Response
Remembering the Pilot
Investigating the Probable Cause
AirPro News analysis
Frequently Asked Questions
The crash occurred on Wednesday, March 4, 2026, at approximately 9:45 p.m. CST.
The aircraft was a single-engine 1976 Cessna T210M Turbo Centurion.
No. Despite crashing into a residential townhome complex and severing two gas meters, there were no ground injuries and no post-crash fires.
Sources
Photo Credit: Paul Valade – Daily Herald
Regulations & Safety
2025 Aviation Safety Report Highlights Flight Trends and Lithium Battery Risks
Airbus reports 35.2 million flights in 2025 with six hull loss accidents and rising lithium battery fire risks from billions of portable devices.
This article is based on an official press release from Airbus.
The commercial aviation industry saw continued growth in 2025, safely transporting more than five billion passengers across the globe. According to an official press release from Airbus, air traffic reached an estimated 35.2 million flights last year, representing an increase from the nearly 34 million flights recorded in 2024.
Despite the rise in global air traffic, flying remains a highly secure mode of transportation. However, the evolving landscape of aviation requires continuous vigilance from all stakeholders. Airbus emphasized that managing safety risks effectively means meticulously analyzing the circumstances of every incident to develop actionable solutions for the entire aviation community.
As the industry looks ahead, the passenger traffic outlook for 2026 suggests a continuing rebound over the next two to three years. Airbus projects a trend toward a long-term annual growth rate of approximately 3.6%, which brings both increased risk exposure and a more complex operational environment.
In its recent safety review, Airbus reported that the past year recorded six accidents resulting in hull losses, three of which were fatal. This marks a shift from 2024, which saw four fatal accidents and twelve hull losses. While the overall accident rate remains low, the manufacturer noted that the recurring nature of these events underscores the need for enhanced safety measures.
Addressing the underlying causes of these accidents requires a combination of advanced technology, human vigilance, and teamwork. The emergence of new operators, novel types of operations, and evolving geopolitical threats all contribute to an increasingly complex operational environment.
“Fostering a positive safety culture based on open communication and strong safety leadership is essential to install, grow, and deploy effective safety measures across organisations,” stated Sophie Rougé, head of Safety Governance at Airbus.
A significant safety concern highlighted in the Airbus press release is the proliferation of Portable Electronic Devices (PEDs) on commercial flights. With over five billion passengers flying in 2025, the commercial aviation network carried an estimated 20 to 25 billion PEDs.
The sheer volume of these devices elevates the risk of lithium battery fires, which Airbus describes as a serious safety threat demanding collective attention. Passengers are now an integral part of the safety equation, and the industry must work collaboratively to anticipate and mitigate these risks. Regulators such as the FAA and EASA, along with global organizations like ICAO and IATA, continually update their guidance to support stakeholders in managing this hazard. We observe that the reduction in total hull losses from twelve in 2024 to six in 2025 is a positive indicator for global aviation safety, even as total flight volumes increased. However, the ratio of fatal accidents to total hull losses shifted, reminding the industry that severe outcomes remain a persistent challenge.
Furthermore, the staggering estimate of up to 25 billion portable electronic devices entering aircraft cabins annually highlights a critical shift in cabin safety management. As passengers carry more lithium-ion powered devices, from smartphones to laptops and medical equipment, cabin crews will likely require enhanced training and specialized containment equipment to handle potential thermal runaway events mid-flight.
According to Airbus, air traffic reached an estimated 35.2 million flights in 2025, up from almost 34 million in 2024.
The Airbus safety statistics report indicates there were six accidents resulting in hull losses in 2025, three of which were fatal.
With an estimated 20 to 25 billion Portable Electronic Devices carried on flights in 2025, the sheer volume increases the risk of lithium battery fires, making it a serious safety threat that requires industry-wide mitigation.
Sources: Airbus
2025 Flight Safety Statistics: Analyzing Accident Trends and Lithium Battery Risks
Introduction to 2025 Aviation Safety
2025 Accident Trends and Safety Culture
Hull Losses and Fatalities
The Growing Threat of Lithium Battery Fires
Managing Portable Electronic Devices
AirPro News analysis
Frequently Asked Questions (FAQ)
How many commercial flights took place in 2025?
How many aviation accidents occurred in 2025?
Why are lithium batteries a concern for flight safety?
Photo Credit: Airbus
Regulations & Safety
SAS A320neo Wrong Taxiway Takeoff Incident at Brussels Airport
A SAS Airbus A320neo nearly took off from a taxiway at Brussels Airport, aborted at 127 knots with no injuries. Preliminary AAIU report details contributing factors.
This article is based on an official preliminary report from the Belgian Air Accident Investigation Unit (AAIU).
On March 6, 2026, the Belgian Air Accident Investigation Unit (AAIU) released a preliminary report detailing a severe aviation incident that occurred at Brussels Airport (BRU). According to the official AAIU documentation, on the evening of February 5, 2026, a Scandinavian Airlines (SAS) Airbus A320neo mistakenly attempted to take off from a parallel taxiway instead of its assigned runway. The aircraft reached a high speed before the flight crew realized the error and executed an emergency rejected takeoff (RTO).
The AAIU has officially classified the event as a “Serious Incident” under ICAO Annex 13 due to the high probability of an accident. The aircraft, operating as Flight SK2590 to Copenhagen with 165 passengers and crew on board, narrowly avoided a catastrophic collision with temporary fences and nearby aviation fuel storage tanks. Fortunately, no injuries were reported, and passengers were safely transported back to the terminal.
We have reviewed the preliminary findings, which highlight a complex “Swiss cheese” alignment of environmental, technical, and human factors. The report emphasizes that multiple overlapping issues contributed to the crew’s loss of situational awareness, rather than a single point of failure.
According to the AAIU timeline, the incident unfolded between 21:00 and 21:04 local time. The flight crew was cleared to take off from Runway 07R via an intersection designated as C6, rather than utilizing the full length of the runway. Operating in total darkness, the crew mistook taxiway “Outer 10” for intersection C6 and subsequently aligned the Airbus A320neo with Taxiway E1, which runs parallel to the active runway.
The preliminary report states that the crew initiated the takeoff roll down the taxiway, accelerating rapidly. The aircraft reached an Indicated Airspeed (IAS) of 127 knots (approximately 146 mph). The AAIU notes that the critical “V1” speed, the velocity beyond which a takeoff can no longer be safely aborted, was calculated at 132 knots for this specific flight, placing the aircraft just 5 knots away from the point of no return.
As the aircraft accelerated down Taxiway E1, the First Officer noticed that the forward visual perspective appeared unusually narrow and that the Captain was not responding to standard operating procedure callouts. Realizing the aircraft was not on the runway, the First Officer intervened.
“Stop, stop, stop, stop.”
, First Officer, SAS Flight SK2590, as recorded in the AAIU preliminary report.
At 21:04:09, the Captain immediately aborted the takeoff by applying full reverse thrust and maximum braking. The AAIU report details that at the moment the abort was initiated, the aircraft had only about 520 meters (1,705 feet) of taxiway remaining before it would have collided with temporary fences. While still moving at roughly 40 knots, the First Officer instructed a right turn to avoid the approaching barriers. The aircraft came to a complete halt in just 14 seconds, stopping near the intersection of taxiways V1 and C1, mere meters from the runway guard lights and the airport’s fuel storage farm.
The AAIU preliminary report does not assign blame but rather identifies several contributing factors. Environmental conditions played a significant role; the incident occurred after civil twilight in total darkness. Furthermore, the runway and taxiway surfaces were wet, which the AAIU notes caused glare and made painted ground markings highly difficult to read.
Infrastructure and procedural elements also compounded the risk. The specific intersection is officially designated as a “hot spot”, an area with a known history or high risk of runway incursions. The AAIU report highlights that the illumination for a crucial intersection sign was inoperable at the time. Additionally, the red stop bar lights at the taxiway/runway intersection extinguished before the crew arrived at the holding point, depriving the pilots of a critical visual reference.
According to the investigation, the SAS Airbus A320neo was not equipped with optional safety software such as the Runway Awareness and Advisory System (RAAS), Airbus Runway Overrun Prevention System (ROPS), or Take-Off Surveillance 2 (TOS2). While aviation regulators do not currently mandate these systems, their absence is noted in the report as they are designed to provide auditory and visual alerts if a takeoff is attempted from a taxiway.
From an Air Traffic Control (ATC) perspective, the AAIU notes that the control tower supervisor had combined the ground and air frequencies. A single air traffic controller was managing both frequencies and dividing their attention among seven different aircraft. Following the report’s release, Belgium’s ATC agency, Skeyes, publicly stated that this staffing arrangement strictly adhered to existing safety guidelines for that time of night and emphasized their full cooperation with the investigation under a “Just Culture” framework.
We note that this incident serves as a textbook example of the critical importance of modern Crew Resource Management (CRM). Historically, steep cockpit hierarchies often prevented junior First Officers from correcting senior Captains, sometimes with fatal results. In this instance, the First Officer’s immediate, assertive command directly prevented a disaster, demonstrating that modern CRM training is functioning exactly as intended.
Furthermore, the absence of systems like RAAS or TOS2 on the incident aircraft highlights an ongoing industry debate. While airlines are legally compliant without these systems, wrong-surface events remain a persistent threat in commercial aviation. As the AAIU continues its investigation, we anticipate that the final report may include safety recommendations urging broader adoption of these technological safety nets, especially for operations at complex airports during low-visibility conditions.
Were there any injuries on SAS Flight SK2590? How fast was the aircraft traveling before the abort? When will the final investigation report be released? Sources:
SAS A320neo Narrowly Avoids Disaster in High-Speed Taxiway Takeoff Incident at Brussels Airport
The Sequence of Events: A High-Speed Near-Miss
Misalignment and Acceleration
The Critical Abort and Evasive Action
Contributing Factors Identified by Investigators
Environmental and Infrastructure Challenges
Equipment and Air Traffic Control Context
AirPro News analysis
Frequently Asked Questions (FAQ)
No. According to the AAIU report, all 165 passengers and crew members were unharmed and safely transported back to the terminal via bus. The aircraft sustained only minor tire and landing gear damage due to high-speed braking.
The AAIU confirmed the aircraft reached 127 knots Indicated Airspeed (IAS) on the taxiway. The V1 speed (the speed at which takeoff must continue) was 132 knots.
The current AAIU report is strictly preliminary. A final report, which will include binding safety recommendations, is expected to be published in approximately one year, likely in early 2027.
Belgian Air Accident Investigation Unit (AAIU) Preliminary Report: AAIU-2026-02-05-01
Photo Credit: Belgian Air Accident Investigation Unit
-
Regulations & Safety4 days agoSouth Korea Audit Finds Cost-Cutting in Jeju Air Flight 2216 Crash
-
Defense & Military1 day agoUSAF Awards Boeing $2.33B Contract for E-7A Wedgetail Development
-
Aircraft Orders & Deliveries3 days agoDe Havilland Delivers First Refurbished Dash 8-400 to ANA Group
-
MRO & Manufacturing2 days agoÖAMTC and Airbus Sign Long-Term Contract for H135 H140 H145 Helicopters
-
Commercial Aviation6 days agoFAA Issues Nationwide Ground Stop for All JetBlue Flights in 2026
