A Frontier Airlines plane was forced to abort its takeoff and evacuate passengers after fatally striking a pedestrian on the runway at Denver International Airport on Friday night. The incident occurred as the Airbus A321 was departing for Los Angeles with 224 passengers and seven crew members on board.
According to CBS News, the collision took place at approximately 11:19 p.m. when the individual, who had jumped the Colorado airport perimeter fence just two minutes earlier, crossed the path of the aircraft. The situation quickly escalated into a major emergency. Radio traffic captured the pilot informing air traffic controllers, “We just hit somebody. We have an engine fire.”
The impact caused significant damage, and passengers reported hearing a loud boom followed by the sight of fire and sparks coming from the engine and wing area. The cabin soon filled with thick smoke as the pilots successfully aborted takeoff and brought the plane to a halt. Given the situation, the crew initiated an emergency evacuation using the plane’s slides.
I am a frequent flier, and I can’t even imagine the situation
According to NBC News, passenger Nikil Thalanki described the immediate aftermath inside the aircraft. “Smoke filled the cabin completely — it was super hard to breathe,” he said. “And then we were sitting there, what they told us to wait there, just remain seated for like, two three minutes, maybe four minutes, and then they opened up the exits.”
Other passengers echoed the intensity of the scene. Mohamed Hassan, another passenger, recounted his experience, stating, “Honestly it was the scariest experience of my life,” and added, “I was on the flight and I looked to my right and I just saw a fire, I heard a loud boom, people started screaming.”
Passengers were instructed to leave their belongings behind as they exited the aircraft onto the runway. From there, buses transported them back to the terminal. While the airline confirmed that no major injuries were reported among the passengers and crew, the airport stated that 12 people reported minor injuries, with five requiring transport to local hospitals for further care.
The identity of the pedestrian remains unknown, and officials have confirmed that the individual is not believed to be an airport employee. The perimeter fence around the facility remains intact, and the event has sparked a multi-agency investigation.
The National Transportation Safety Board and the Federal Aviation Administration are both involved in determining the exact cause of the collision and the subsequent engine fire. Runway 17L, where the incident occurred, was closed for the investigation.
Transportation Secretary Sean Duffy addressed the incident on X, confirming the details surrounding the breach. He also emphasized the severity of such actions by stating, “No one should EVER trespass on an airport.” Local law enforcement is also participating in the ongoing investigation into how the individual gained access to such a restricted area.
For those on the flight, the incident left a lasting impression. While many passengers were eventually able to continue their journey to Los Angeles on a replacement flight provided by the airline, some found the experience too overwhelming to travel immediately. Hassan, for instance, declined the offer for a new flight on Saturday morning.
The Association of Flight Attendants-CWA issued a statement following the event. They noted that they “commend the quick and professional actions of the pilots and the firefighter first responders who ensured the fire did not spread as everyone onboard was ushered to safety.” The airport has expressed its sympathies to everyone involved in the incident as they work to finalize their review of the emergency response.
This isn’t the first flight that has had to abort takeoff in the past few months. A lot of them tied back to belligerent passengers; there was even a case of a mysterious leak. However, none of them had such a horrifying reason, and my heart goes out to the passengers and the crew.
Published: May 11, 2026 05:58 am