A person who breached the perimeter fence at Denver International Airport late Friday night was struck and killed by a Frontier Airlines jet accelerating for takeoff, forcing the pilot to abort and triggering an emergency evacuation that left 12 people hurt, U.S. Transportation Secretary Sean Duffy and airport officials said.

The trespasser jumped the fence and was on the runway within two minutes, Denver International Airport reported. By then, Frontier Airlines Flight 4345, carrying 224 passengers and seven crew members bound for Los Angeles, was already rolling at high speed down runway 17L.

The collision set off a chain of events that could have been far worse: smoke filled the cabin, a brief engine fire broke out, and all 231 souls aboard had to evacuate on the tarmac. Five of the twelve injured were taken to a hospital. The trespasser was pronounced dead. Authorities have not identified the individual and say the person was not an airport employee.

What Duffy and Denver officials described

Duffy posted his account on X shortly after the incident, which the airport said was reported at 11:19 p.m. His description was blunt:

"A trespasser breached airport security at Denver Int'l Airport, deliberately scaled a perimeter fence, and ran out onto a runway. The trespasser on the runway was then struck by Frontier Airlines Flight 4345 during takeoff at high speed."

The secretary added that the pilot halted takeoff procedures immediately. Law enforcement and firefighters responded to the scene, and the plane was evacuated.

Duffy stated that local law enforcement handles airport security and is leading the investigation, with support from the FAA and TSA. He closed with a warning that carried the weight of the night's events: "No one should EVER trespass on an airport."

Denver International Airport confirmed the timeline in its own posts on X. The airport said it inspected the fenceline after the incident and found it intact, meaning the trespasser apparently climbed over the barrier rather than cutting through it.

"DEN can confirm the pedestrian jumped the perimeter fence and was hit just two minutes later while crossing the runway. The pedestrian is deceased, and is not believed to be an employee of the airport nor have they been identified."

The airport added that the National Transportation Safety Board had been notified and that runway 17L was temporarily closed during the investigation.

A passenger's account from the wing seat

Jose Cervantes, a passenger aboard the flight, described the moment of impact to Denver station KCNC. His account matches the timeline officials laid out, the plane was already gaining speed for liftoff when the collision occurred.

"We're already taking off, right? The plane took a little bit to take off, but we were already taking off and we're going pretty fast and I felt like the plane started to tilt up when out of nowhere, it just -- we felt like a thud and heard like an explosion. And I was right on the wing, so I looked to my right and I just see, like, the right wing just on fire."

Cervantes described what followed: the aircraft dropped back down, swayed side to side, and came to a stop. The crew shut everything off. Then smoke began filling the cabin, and the evacuation began.

Frontier Airlines said in a statement that "smoke was reported in the cabin and the pilots aborted takeoff." Firefighters extinguished what the airport called "a brief engine fire."

Security incidents at major facilities have drawn renewed attention in recent months. A shooting near the White House involving Secret Service agents highlighted the persistent challenge of protecting high-value perimeters against determined intruders.

Two minutes from fence to impact

The two-minute window between the fence breach and the fatal strike raises hard questions about airport perimeter security, and about what, if anything, could have prevented the tragedy in such a compressed timeframe.

Denver International Airport is one of the largest airports in the country by land area. Its runways stretch across miles of open terrain. Perimeter fencing is the first line of defense, but as this incident shows, a fence alone does not stop someone determined to get onto active pavement.

The airport said the fence was intact after the breach, which suggests the trespasser climbed over it rather than exploiting a gap or a maintenance failure. That detail matters. It means the physical barrier did its structural job but failed to delay the intruder long enough for any response.

Whether perimeter sensors, cameras, or alarm systems detected the breach before the collision remains unknown. The investigation, led by local law enforcement with FAA, TSA, and NTSB involvement, will presumably address that question.

Evacuations under duress carry their own dangers, as Americans saw when JD Vance described a chaotic evacuation from the White House Correspondents' Dinner after a security breach at a checkpoint. When hundreds of people must exit a confined space in seconds, injuries follow.

Unanswered questions

Authorities have released no information about the trespasser's identity, age, or sex. They have not disclosed a motive. The airport said only that the individual was not believed to be an employee.

The specific injuries sustained by the twelve people hurt during the incident have not been detailed. Five were transported to a hospital; the conditions of the remaining seven are unclear.

It is also unknown whether the engine fire and cabin smoke resulted directly from the impact or from the aborted takeoff itself. Frontier's statement referenced smoke in the cabin and the pilots' decision to abort, but did not elaborate on the mechanical sequence.

Government accountability for security lapses at federal facilities has been a recurring theme. Separately, Vice President Vance has pressed for tighter oversight of federal systems that fail to track even basic information about the people they serve.

The NTSB's involvement signals that the investigation will extend beyond local law enforcement. The board typically examines aircraft incidents for systemic safety failures, not just individual culpability.

A grim week for airport safety

The Denver runway death came roughly a day after a separate incident at Orlando International Airport, where Delta Air Lines said an employee was killed Thursday night. Delta stated it was "focused on extending our full support to family and taking care of our Orlando team during this difficult time" and was working with local authorities on a full investigation.

Two deaths on airport grounds in two days, one involving a trespasser, the other an employee, underscores the hazards that exist on the operational side of every terminal wall. Passengers see the gates and the jetways. They rarely think about the high-speed, heavy-machinery environment just beyond the fence.

The loss of public figures and officials has also marked recent weeks, including the death of Georgia congressman David Scott, a reminder that sudden loss reshapes institutions overnight.

What comes next

The FAA, TSA, NTSB, and local law enforcement are all now involved in the Denver investigation. The scope of their inquiry will likely include the adequacy of perimeter detection systems, the response time between breach and alert, and whether any protocol could have stopped the trespasser before impact.

For the 231 people aboard Flight 4345, the night ended on a darkened runway surrounded by emergency vehicles instead of at a gate in Los Angeles. Twelve of them were hurt. All of them were put at risk by a single person who decided to climb a fence and walk onto an active runway.

Duffy's closing line, "No one should EVER trespass on an airport", states the obvious. The harder question is what happens when someone does, and whether two minutes is enough time for any system to stop them.

Fences keep honest people out. Security systems are supposed to handle the rest. Friday night in Denver, the rest didn't get handled in time.