Frontier Plane Kills Pedestrian at LAX Takeoff

A commercial jet hit and killed a person on a runway at Denver International Airport late Friday, May 8. The plane was Frontier Airlines Flight 4345, headed to Los Angeles. It aborted takeoff after the strike, and an engine caught fire, which forced an evacuation. Everyone on board survived, but the person on the runway died. ### Wait — this was Denver, not LAX? Yes. The flight was bound for Los Angeles International Airport, which is probably why early headlines framed it as “LAX-bound.” But the collision happened in Denver during takeoff, not in Los Angeles. The airport involved was Denver International, and the reported time was about 11:19 p.m. Friday. (apnews.com) ### Who was the person on the runway? Denver airport said the person was a trespasser who had jumped a security fence and was crossing the runway when the plane hit them. As of the latest reporting, the person had not been publicly identified, and airport officials said they were not believed to be an airport employee. That detail matters because this does not look like a worker-safety incident first — it looks like a perimeter-security breach. (nbclosangeles.com) ### What happened on the plane? After the impact, the crew aborted takeoff. The strike sparked an engine fire, and passengers had to evacuate. Frontier said it was coordinating with airport and safety authorities. Denver airport said 12 people reported minor injuries during the evacuation, and five of them were taken to local hospitals. The injuries were tied to getting off the aircraft, not to the collision itself. (msn.com) ### How does something like this even happen? Runway incursions usually mean a vehicle, another aircraft, or a person ends up where they should not be. The unusual part here is not just that someone was on the airfield — it’s that they made it all the way onto an active runway during a takeoff roll. Basically, once a jet is accelerating at takeoff speed, the crew has very little time to process something unexpected ahead. That turns a security breach into an almost impossible avoidance problem. (ktla.com) The airport’s own description — fence jump, runway crossing, strike — points straight at that chain. ### Was this a normal emergency evacuation? Not really. Evacuations from a jet on a runway are controlled chaos even on a good day. Add darkness, a fire risk, and passengers who may not know what just happened, and minor injuries become common fast — sprains, scrapes, that kind of thing. That seems to be what happened here. The bigger point is that the evacuation worked. People got off the aircraft alive. (apnews.com) ### Who investigates this now? Several layers kick in. Denver International is handling the airport side. Frontier is handling the airline side. Federal safety authorities are expected to examine both the collision and the breach that let a trespasser onto the runway in the first place. The immediate questions are simple — how the person got airside, how long they were there, and whether anyone saw them before impact. Frontier has already said it is gathering information with airport and safety officials. (ktla.com) ### Why does this matter beyond one awful night? Because the aviation system is built around keeping runways sterile. If that fails, everything else gets harder in a hurry. Pilots cannot reliably dodge a person during takeoff the way a driver might swerve on a road. So this story is not just about a tragic death. It is about whether one of the country’s busiest airports had a perimeter gap big enough to put a person in front of a departing airliner. (msn.com) ### Bottom line? This was not a plane “heading to LAX” killing someone near Los Angeles. It was a Denver runway intrusion that ended in a fatal strike, an aborted takeoff, an engine fire, and an evacuation. The human tragedy is obvious. But the next phase is about security — because the hardest question is how that person got there at all. (nbclosangeles.com) (apnews.com)