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.
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.
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.
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
Regulations & Safety
FAA Investigates Southwest Airlines Ground Collision at PVD
Two Southwest Boeing 737s collided during pushback at Rhode Island T.F. Green Airport on June 11, 2026. FAA investigation opened.

This is a developing story. Information may change as official details are released.
This article summarizes reporting by WPRI, NBC 10, Daily Voice, and CBS News Baltimore.
The Federal Aviation Administration (FAA) has opened an investigation after two Southwest Airlines Boeing 737 aircraft collided during pushback at Rhode Island T.F. Green International Airport (PVD) late on June 11, 2026.
The ground collision resulted in no reported injuries but forced the cancellation of both flights and the grounding of the involved aircraft for mandatory safety inspections. According to reporting by the Daily Voice and NBC 10, the incident highlights ongoing operational challenges on airport ramps, occurring just weeks after a similar event involving the same carrier at another East Coast facility.
Details of the ground collision
At approximately 10:45 p.m. local time, Southwest Airlines Flight 3515, bound for Ronald Reagan Washington National Airport (DCA), was pushing back from its gate. During the maneuver, the aircraft’s wing made contact with the tail of Southwest Airlines Flight 3409, which was scheduled to depart for Chicago Midway International Airport (MDW).
Both aircraft returned to their respective gates following the contact, allowing passengers to deplane normally. Southwest Airlines confirmed that no injuries occurred among passengers or crew members. The carrier subsequently canceled both flights and reaccommodated the affected travelers.
“Southwest Airlines is aware of an incident involving two of our aircraft at Rhode Island T. F. Green International Airport. We are investigating further and will be thoroughly inspecting the two aircraft,”
the airline stated in remarks provided to local media, adding that safety remains its highest priority.
Local media outlets, including NBC 10, reported passenger accounts suggesting that Flight 3515 continued to move briefly after the initial impact. These accounts claim passengers verbally alerted the flight crew to the collision. Neither Southwest Airlines nor the FAA has officially verified these specific passenger narratives, and the official sequence of events remains under investigation.
Regulatory response and recent precedent
The FAA confirmed on June 12, 2026, that it is investigating the circumstances surrounding the collision. Ground operations during pushback rely heavily on coordination between flight crews and ground personnel, particularly in ramp areas where air traffic controllers do not maintain direct communication with the aircraft.
This event follows a comparable occurrence on May 4, 2026, at Baltimore/Washington International Thurgood Marshall Airport (BWI). In that instance, two Southwest Airlines Boeing 737s clipped wings during pushback operations. The FAA investigated the BWI incident, noting the specific communication dynamics between ground crews and the flight deck in non-controlled ramp sectors.
AirPro News analysis
We note that while ground collisions during pushback rarely pose a severe threat to passenger safety, they represent a significant operational and financial burden for carriers. Ramp incidents require immediate grounding of the involved airframes, triggering mandatory structural inspections and potential repairs. The recurrence of pushback-related contact within a single airline’s network over a short period may prompt internal reviews of ground handling procedures, wingwalker positioning, and ramp communication protocols. Until the FAA concludes its investigation, the specific cause of the PVD collision remains undetermined.
Sources: WPRI
Photo Credit: Zachary Reis
Regulations & Safety
Turkish Airlines 777-300ER Wing Strike at Antalya Airport
A Turkish Airlines Boeing 777-300ER struck a radar antenna pole taxiing at Antalya Airport, prompting evacuation and a formal investigation.

This is a developing story. Information may change as official details are released.
This article summarizes reporting by Hürriyet.
A Turkish Airlines (TK) Boeing 777-300ER sustained damage and prompted a passenger evacuation after its right wing struck a ground radar antenna pole while taxiing at Antalya Airport (AYT) on June 11, 2026.
The incident, which occurred at approximately 20:00 local time following Flight TK2430 from Istanbul, resulted in minor injuries among the passengers. According to official statements reported by Hürriyet, the widebody aircraft was maneuvering toward its parking position on Apron-1 when the collision occurred, leading to an immediate evacuation on the tarmac.
Conflicting passenger and injury reports
Following the evacuation, official sources provided conflicting figures regarding the number of passengers on board and the extent of injuries. In a public statement, Turkish Airlines Senior Vice President of Communications Yahya Üstün confirmed the evacuation, stating that 267 passengers were safely removed from the aircraft. The airline reported that one passenger sustained minor injuries and was in good health.
Conversely, the Turkey Ministry of Transport released a separate statement indicating a higher passenger count. The ministry reported that the aircraft was carrying 284 adult passengers and four infants. Furthermore, the government authority stated that three passengers suffered minor injuries during the event. Both entities confirmed that the aircraft, registered as TC-LKD, was towed to a parking area after the necessary safety checks and passenger removal were completed.
Investigation into the ground collision
A technical investigation into the ground collision has been initiated by the Turkey Ministry of Transport and the General Directorate of State Airports Authority (DHMI). The official cause of the incident remains under investigation.
While the airline noted the aircraft was approaching its parking position, preliminary remarks from the Ministry of Transport suggested the Boeing 777-300ER made contact with the radar pole after entering an incorrect taxiway line. Final determinations regarding the aircraft routing, ground control instructions, and the sequence of events will be established by the investigating authorities.
AirPro News analysis
Ground collisions involving widebody aircraft like the Boeing 777-300ER often highlight the tight tolerances required when maneuvering large airframes around airport infrastructure. While we await the official investigation findings, safety reviews following such events typically examine airport taxiway markings, lighting, and the clarity of ground control communications. The discrepancy in passenger manifests between the operator and the regulator is a notable detail, though initial reporting conflicts frequently occur in the immediate aftermath of an evacuation before final reconciliations are completed.
Sources: X.com
Photo Credit: X
Regulations & Safety
NTSB Final Report: Southwest Flight 4273 Turbulence Encounter
NTSB cites ATC communication delays and sector overload in Southwest Airlines turbulence event over Gulf of Mexico.

This is original reporting and analysis by AirPro News.
The National Transportation Safety Board (NTSB) has released its final report on a severe turbulence encounter involving a Southwest Airlines Boeing 737-700, detailing how rapidly developing convective weather and air traffic control communication delays factored into an event that seriously injured two people.
The April 3, 2024, incident aboard Southwest Airlines Flight 4273 over the Gulf of Mexico highlights the operational risks when severe weather systems intersect with technical limitations at air traffic control facilities. According to the NTSB investigation, the aircraft was navigating complex weather en route from New Orleans to Orlando when the encounter occurred, resulting in serious injuries to one flight attendant and one passenger, alongside minor injuries to a second flight attendant.
Weather conditions and the turbulence encounter
Flight 4273, operated by a Boeing 737-700 (registration N567WN) with 140 passengers and five crew members on board, was traveling from Louis Armstrong New Orleans International Airport (MSY) to Orlando International Airport (MCO).
At 11:55 UTC, a Convective Significant Meteorological Information (SIGMET) advisory was issued for the region, warning of cloud tops exceeding 45,000 feet.
At approximately 08:20 Eastern Daylight Time, the aircraft encountered severe turbulence over the Gulf of Mexico. The NTSB confirmed the aircraft itself sustained no damage during the event and the flight crew was able to continue the flight.
Air traffic control workload and technical limitations
The NTSB report outlines compounding factors at the Jacksonville Air Route Traffic Control Center (JAX ARTCC) that affected the flight routing through the weather system.
During the incident, the specific JAX ARTCC sector was managing a traffic volume that exceeded its target capacity of 20 aircraft.
This high workload was exacerbated by a technical limitation involving the facility communication infrastructure. The primary VHF antenna at JAX ARTCC had been rendered inoperative following a fire in October 2023. As a result, controllers were utilizing a temporary satellite relay connection to communicate with aircraft in the sector.
The NTSB determined this satellite relay introduced a 600-millisecond round-trip transmission delay, complicating timely communication between controllers and flight crews navigating the dynamic weather environment.
AirPro News analysis
We note that the findings in this final report underscore a critical vulnerability in the National Airspace System. When primary communication infrastructure fails, the fallback systems must be robust enough to handle high-stress, time-critical scenarios like severe convective weather deviation. A 600-millisecond delay might seem negligible in routine operations, but in a saturated sector where controllers are issuing rapid heading changes to keep aircraft clear of building storm cells, that latency degrades situational awareness and increases the risk of weather encounters. The NTSB documentation of this technical shortfall will likely prompt further scrutiny of contingency communication systems at major en route centers.
Photo Credit: NTSB
-
Technology & Innovation2 days agoAirbus Vision Landing Application Enables AI Autoland
-
Route Development5 days agoDubai International Airport to Close in 2035 for Al Maktoum
-
Commercial Aviation5 days agoIATA 2026 Airline Profit Forecast Cut in Half by Fuel Costs
-
Defense & Military6 days agoWhisper Aero Launches Collaborative Logistics Aircraft for US Military
-
MRO & Manufacturing6 days agoGE Aerospace Q1 2026: LEAP Deliveries Up 60%, $170B Backlog
