Volaris Jet Declares Mayday Over Las Vegas After Bird Strike Ignites Right Engine

A Volaris flight bound for Guadalajara, Mexico, turned back to Las Vegas's Harry Reid International Airport on the evening of Monday, September 14, 2026, after its crew declared an in-flight emergency when the right engine caught fire moments after departure. Volaris Flight 1741 landed safely roughly forty minutes after the mayday call, and airport officials confirmed no injuries among passengers or crew.
Ground-level video that circulated widely this week — first aired publicly on Friday, September 18 — shows short, bright bursts of flame shooting from the aircraft's right engine as it climbed out over the Las Vegas valley shortly after sunset. In audio recorded from the cockpit-to-tower exchange, a pilot can be heard telling air traffic control: "Mayday, mayday, mayday. Engine two failure." Passengers described hearing a loud bang resembling an explosion during the initial climb, which triggered visible alarm inside the cabin before the crew calmed travelers and began preparations to return to the airport.
What happened
According to Volaris's own account of the incident, the aircraft's turbine ingested a bird during the takeoff roll, an event commonly known in the industry as a bird strike. Wildlife ingestion into a jet engine can bend or shred internal fan blades and compressor stages, and in some cases ignite residual fuel or hydraulic fluid inside the engine casing, producing the visible flame bursts caught on camera. Volaris said in its statement that the crew followed standard emergency procedures after detecting the engine problem, shut down the affected engine, and used the aircraft's remaining engine to fly back toward Harry Reid International rather than continuing toward Mexico.
Flight 1741 remained airborne for close to forty minutes after the initial bang before touching down, a window during which the crew would have worked through checklist procedures for a single-engine approach, coordinated with air traffic control to sequence a priority landing, and likely burned down fuel or repositioned to a suitable approach path. Airport authorities in Las Vegas said there were no visible signs of smoke or fire on the aircraft by the time it landed and taxied clear of the runway, and emergency crews that staged for the arrival were not needed for any injuries.
Local outlet Fox5 Vegas and national broadcasters including CNN and NBC News carried footage and passenger accounts of the incident in the days following, while Yucatan Magazine and other Mexico-focused outlets noted the flight's cancelled onward routing to Guadalajara, a market Volaris serves heavily from several U.S. gateway cities as part of its low-cost, cross-border network.
The regulatory picture
The Federal Aviation Administration confirmed it is investigating the incident, in line with the agency's standard practice for any engine-related emergency declaration involving a U.S. airport. As of this writing, no preliminary report has been published, and the FAA has not released a timeline for when findings might be public. Consistent with international investigative norms under ICAO Annex 13 — the framework member states use for probing aviation occurrences — this article makes no claims about contributing causes beyond what Volaris and the FAA have themselves stated: a bird strike is understood to be the trigger event, but a full accounting of the engine's internal damage, whether any additional mechanical factors were present, and the specific sequence that produced visible external flame has not yet been made public.
Bird strikes are among the most common wildlife hazards in commercial aviation and are rarely fatal to an aircraft's outcome, largely because jet engines are certified to withstand a defined level of bird ingestion without catastrophic failure, and because modern twin-engine airliners are designed and crewed to fly, maneuver, and land safely on a single engine. The FAA's Wildlife Strike Database has logged tens of thousands of reported strikes across U.S. airports in recent years, the vast majority causing no injury and only minor aircraft damage. Visible flame during a bird-strike-related engine failure — as opposed to smoke alone — is less common but not unprecedented, and it is typically the product of ingested debris disrupting the engine's internal airflow and igniting unburned fuel inside the combustor or turbine section before the crew shuts the engine down.
The aircraft and the airline
Volaris is one of Mexico's largest low-cost carriers, operating an all-Airbus narrowbody fleet drawn from the A320 family across an extensive network linking the United States and Mexico, along with routes into Central America. Las Vegas–Guadalajara is one of several U.S.–Mexico leisure and visiting-friends-and-relatives routes the carrier operates using its single-aisle jets, typically flown by two pilots supported by cabin crew sized to the aircraft's seating capacity. Neither Volaris's statement nor the news coverage reviewed for this article specified the exact aircraft variant or registration involved, and that detail — along with the extent of physical damage to the engine — is expected to emerge as any FAA or manufacturer-level inspection proceeds.
Las Vegas's Harry Reid International sits close to open desert on its eastern approaches but is also near enough to the Las Vegas Strip and surrounding neighborhoods that a low-altitude climb-out with visible flame is likely to be seen and filmed by people on the ground, which is almost certainly how footage of Monday evening's incident began circulating so widely: not from onboard passengers, but from bystanders below who caught the aircraft's initial ascent on their phones before word of the mayday call itself became public days later. That gap between the incident occurring on September 14 and video surfacing publicly on September 18 is itself a reminder of how modern aviation incidents are often pieced together well after the fact, as separate video sources, passenger accounts, and official statements converge into a fuller public record.
How single-engine returns work
Commercial twin-engine jets, including the Airbus A320-family aircraft Volaris flies, are certified under strict international standards that require them to take off, climb, maneuver, and land safely with only one engine operating, a standard that exists precisely to cover scenarios like a bird strike disabling one engine shortly after departure. In practice, that means a crew facing an engine failure or fire on climb-out follows a memorized and checklist-driven sequence: identify which engine has failed, retard or shut down its thrust lever, discharge a fire suppression bottle into the engine nacelle if fire indications persist, and reconfigure the aircraft's flight controls and systems to compensate for asymmetric thrust from the remaining engine. Air traffic controllers, once notified of an emergency squawk or a verbal mayday call, typically clear surrounding traffic and offer the crew a direct routing back to the departure airport or the nearest suitable field, prioritizing the aircraft ahead of the normal arrival sequence.
The nearly forty minutes Flight 1741 spent airborne before landing is consistent with a crew working through such a checklist at a deliberate pace rather than rushing: burning down fuel to reach a safe landing weight, verifying system status, briefing the cabin crew and, where needed, passengers on the situation, and coordinating approach details with air traffic control — all before committing to final approach and landing. That the aircraft landed with no visible smoke or fire and needed no emergency-response intervention on the runway is, by the account given so far, evidence that the crew's engine shutdown and fire-suppression response worked as designed.
What happens next
Airlines and manufacturers typically follow a bird-strike-related engine event with a borescope inspection — a fiber-optic camera examination of the engine's internal blades and combustion chamber — to catalog damage before any decision is made about repair, part replacement, or, in more severe cases, full engine removal for teardown. Given that Volaris has already attributed the event to a bird strike and that the aircraft landed without further incident, the file is likely to proceed as a routine, if visually dramatic, engine-ingestion investigation rather than trigger any broader fleet action. There is no indication at this stage of a manufacturer safety bulletin or a wider FAA order tied to this specific aircraft type as a result of the Las Vegas event; nothing in reporting so far points beyond the single bird encounter as a contributing factor.
Airport wildlife management programs — required at U.S. commercial airports under federal regulation — typically respond to a strike report like this one by reviewing recent bird activity near the runway involved, checking whether any mitigation measures such as habitat modification, noise deterrents, or netting near drainage areas might reduce the odds of a repeat encounter. Whether Harry Reid International's wildlife hazard management team identified any contributing local factors, such as a particular bird species or a nearby attractant like standing water, has not been disclosed publicly as of this writing.
For passengers, the episode is a reminder of how airline crews are trained to respond when jet engines take in wildlife: rapid diagnosis, an engine shutdown to prevent further damage, and reliance on redundant systems built into every twin-engine commercial jet to bring the aircraft back safely on one engine. Federal investigators will ultimately determine whether any additional factors — beyond the bird strike Volaris has already disclosed — played a role, but that determination has not yet been published, and this article will not speculate about findings the FAA has not yet issued.

What happens next
Airlines and manufacturers typically follow a bird-strike-related engine event with a borescope inspection — a fiber-optic camera examination of the engine's internal blades and combustion chamber — to catalog damage before any decision is made about repair, part replacement, or, in more severe cases, full engine removal for teardown. Given that Volaris has already attributed the event to a bird strike and that the aircraft landed without further incident, the file is likely to proceed as a routine, if visually dramatic, engine-ingestion investigation rather than trigger any broader fleet action. There is no indication at this stage of a manufacturer safety bulletin or a wider FAA order tied to this specific aircraft type as a result of the Las Vegas event; nothing in reporting so far points beyond the single bird encounter as a contributing factor.
For passengers, the episode is a reminder of how airline crews are trained to respond when jet engines take in wildlife: rapid diagnosis, an engine shutdown to prevent further damage, and reliance on redundant systems built into every twin-engine commercial jet to bring the aircraft back safely on one engine. Federal investigators will ultimately determine whether any additional factors — beyond the bird strike Volaris has already disclosed — played a role, but that determination has not yet been published.
Sources
- Fox5 Vegas: Volaris flight lands safely following mid-air engine fire alert in Las Vegas
- Yahoo News / weather.com: Pilot Declares 'Mayday, Mayday' After Flames Are Seen Shooting from Volaris Plane's Engine
- CNN: Flames from airplane engine seen over Las Vegas
- KTNV: Video shows Volaris flight landing in Las Vegas after reported engine fire
- Yucatan Magazine: Fire Breaks Out on Volaris Vegas Flight to Guadalajara
- NBC News: Takeoff scare for Mexico bound flight