A routine Friday night departure from Denver International Airport turned into a scene of chaos and tragedy when a Frontier Airlines aircraft struck and killed a pedestrian on the runway during its takeoff roll.
The incident, which occurred at approximately 11:19 p.m., triggered an immediate emergency response, including an engine fire and the evacuation of 231 people from the aircraft. Airport officials confirmed that the pedestrian, whose identity has not yet been released, had jumped a perimeter fence and was struck just two minutes after entering the airfield.
The collision forced the pilots of Frontier Flight 4345, bound for Los Angeles International Airport (LAX), to abort the takeoff. The sudden stop and subsequent reports of smoke in the cabin led to a full emergency evacuation via the aircraft’s slides, leaving passengers and crew stranded on the runway as emergency crews rushed to the scene.
A Timeline of the Collision
The sequence of events was captured in real-time through air traffic control (ATC) transmissions, painting a picture of the sudden transition from a standard departure to a crisis. According to records from ATC.com, the pilot alerted the control tower almost immediately after the impact.
“We’re stopping on the runway,” the pilot reported. “We just hit somebody. We have an engine fire.”
The urgency of the situation escalated quickly. The pilot informed controllers that there were “231 souls” on board—comprising 224 passengers and seven crew members—and noted that an “individual was walking across the runway.” As the air traffic controller confirmed that emergency vehicles were “rolling the trucks,” the pilot reported smoke inside the aircraft and declared the intent to evacuate the passengers directly onto the runway.
| Detail | Information |
|---|---|
| Flight Number | Frontier Flight 4345 |
| Route | Denver (DEN) to Los Angeles (LAX) |
| Time of Incident | Friday, approx. 11:19 p.m. |
| Location | Runway 17L, Denver International Airport |
| Total Onboard | 231 (224 passengers, 7 crew) |
Security Breach and Perimeter Failures
The death has raised immediate questions regarding the security of the airfield. An airport spokesperson stated that the pedestrian was not an employee and had gained access to the restricted area by jumping a perimeter fence. Most concerning to investigators is the timeline: the individual was struck only two minutes after entering the airport grounds.
This narrow window suggests a significant gap between the breach of the perimeter and the ability of security personnel or surveillance systems to intercept the intruder before they reached an active runway. The National Transportation Safety Board (NTSB) has been notified and is coordinating with airport and airline authorities to determine how the breach occurred and why the individual was not detected in time.
Passenger Impact and Evacuation
For the 224 passengers on board, the flight ended in a harrowing evacuation. While Frontier Airlines confirmed that the pilots aborted the takeoff due to the collision and reports of smoke in the cabin, it remains unclear whether the smoke was a direct result of the impact with the pedestrian or a secondary mechanical failure caused by the engine fire.
Passengers were forced to exit the plane via emergency slides, a process that often causes minor injuries. Airport officials reported that 12 passengers suffered minor injuries during the ordeal, with five requiring transport to local hospitals for further evaluation. Once cleared from the aircraft, the remaining passengers were bused back to the terminal.
A Concerning Trend in Airport Fatalities
The tragedy in Denver comes at a time of heightened sensitivity regarding airport safety. Only one day prior, a Delta Air Lines employee was killed while on the job at Orlando International Airport. While the circumstances of the Orlando death differ—involving an employee rather than a trespasser—the back-to-back fatalities have put a spotlight on the inherent dangers of the airfield environment.
In a statement, Delta Air Lines expressed its focus on supporting the family of the deceased employee and working with local authorities to determine the cause of that incident.
Note: If you or a loved one have been affected by a traumatic event, resources are available through the National Crisis Lifeline at 988.
Runway 17L remained closed following the incident to allow investigators to process the scene and gather evidence. The NTSB’s investigation will likely focus on the flight data recorder, ATC communications and airport surveillance footage to reconstruct the final moments before the collision.
The next confirmed step in the process will be the release of the preliminary NTSB factual report, which typically outlines the technical causes of the accident and the sequence of security failures.
Do you have information regarding this incident or a similar experience with airport security? Share your thoughts in the comments or contact our newsroom.
