LAX-Bound Plane Hits Pedestrian at Takeoff

A Frontier Airlines flight headed to Los Angeles turned into a runway disaster late Friday night at Denver International Airport. Flight 4345, an Airbus A321, hit and killed a person while accelerating for takeoff on Runway 17L. The collision sparked a brief engine fire, filled the cabin with smoke, and forced an evacuation of all 224 passengers and seven crew members. Twelve people reported minor injuries, and five were taken to hospitals. ### What exactly happened? The plane was departing Denver for LAX shortly after 11 p.m. local time on May 8 when the crew reported striking a person on the runway and aborted takeoff. Air traffic audio and witness accounts line up on the basic sequence — a loud impact, the aircraft stopping hard, then smoke and fire around one engine. Passengers were evacuated and later bused back to the terminal. (cnbc.com) ### Who was on the runway? Turns out this was not an airport worker or someone in an authorized area. Denver airport officials said the person had jumped the airport’s perimeter fence and was hit about two minutes later while crossing the runway. Transportation Secretary Sean Duffy said the person had breached airport security and run onto the airfield before being struck at high speed. The person had not been publicly identified in the reports available Saturday. (abcnews.com) ### Why did the plane catch fire? The key detail is the engine. Officials told ABC News the victim was at least partly pulled into one of the engines, which caused a brief engine fire. Frontier also said smoke was reported in the cabin after the impact. That helps explain why this became more than a rejected takeoff — it became a full evacuation event, with passengers getting off onto the runway itself. (cnbc.com) ### How bad were the injuries onboard? No one on the aircraft was reported killed, but the evacuation was not injury-free. Denver airport said 12 people reported minor injuries and five were transported to local hospitals. In a case like this, those injuries can come from the sudden stop, panic in the cabin, or the evacuation itself — even when the fire is brief. ### Was the runway shut down? (abcnews.com) Yes. Runway 17L was closed during the initial investigation, then reopened by 10:55 a.m. local time on Saturday after the scene was cleared. The National Transportation Safety Board was notified, and the FAA and TSA were also involved alongside local law enforcement. So this is now both an accident investigation and a security investigation. ### How unusual is this? (cnbc.com) Very. Aircraft hit wildlife more often than people, and runway incursions usually involve vehicles or other aircraft, not a pedestrian breaching the perimeter of a major airport. That is what makes this story land so hard — the aviation part is horrifying, but the security lapse is just as important. A person got from outside the fence to an active runway fast enough to intersect a departing jet. ### What questions matter now? The big one is simple: how did someone get onto the airfield and reach Runway 17L so quickly? Denver said it examined the fence line and found it intact, which suggests the breach may have been more about access and response time than obvious physical damage. Investigators will also look at the crew’s rejected takeoff, the engine damage, the evacuation, and whether anything about surveillance or patrol patterns failed. (cnbc.com) ### Bottom line This was not just a freak runway collision. It was a fatal security breach at one of the country’s busiest airports that also triggered an onboard emergency. The plane stopped. The passengers got out. But the harder question is how the person got there at all. (cnbc.com)