The Smart Marty Sky Dispatch
Frontier Airlines jet strikes person on runway at Denver International Airport: Officials
Pilots reported an engine fire and smoke inside the aircraft after the incident.
A Frontier Airlines jet struck a person on a runway at Denver International Airport, according to officials, with the incident involving a person on the runway during taxi or takeoff operations. Initial reporting described an engine fire and smoke inside the aircraft as part of the events, though the material does not specify whether those conditions were confirmed as actual fires or smoke within the cockpit or cabin. Frontier Airlines was the airline associated with the aircraft involved, and officials provided updates as the situation developed on the airport campus.
CBS News Colorado reported a nationwide FAA-ordered ground stop tied to the event, indicating that outbound departures were halted across the United States while aircraft already in flight continued under existing clearances. The stoppage was described as extraordinary and safety-related, part of efforts to investigate underlying causes affecting air-traffic-control operations. Coverage noted that several outlets described the disruption as an effort to sterilize the airspace while investigators pursued the root issues, though no end date was disclosed in the initial advisory.
At Denver International Airport, the ground stop affected passenger movement with flights held on the tarmac and at gates, and overall airport operations slowed, according to CBS News Colorado. The reporting emphasized the disruption to travelers and airport operations, but did not specify flight numbers or the precise impact on individual departures or arrivals. Airport officials and airline staff were described as coordinating with passengers to manage the halt and provide information and support during the disruption.
The nationwide scope of the FAA ground stop was reinforced by national coverage, with FOX 13 Seattle and WZTV noting that departures nationwide were impacted and that there was no immediate end-date announced in the initial advisory. WXYZ Channel 7 tracked the ground stop as lasting more than four hours—beginning shortly before 4 p.m. Eastern and ending around 8:15 p.m. Eastern—while citing a telecommunications outage as a trigger and reporting reassurances from Transportation Secretary Sean Duffy and Homeland Security Secretary Markwayne Mullin that there was no evidence of a cyberattack and that the public remained in no danger. The reports highlighted thousands of cancellations and broad travel disruption as people attempted to reach destinations after the halt.
O’Hare International Airport in Chicago was described in the material as experiencing a mid-afternoon ground stop due to thunderstorms, with departures held from about 1:00 p.m. to 2:15 p.m. local time, and weather conditions potentially extending the pause, though no direct connection to the Denver incident was established in the shared material. The broader narrative ties the Denver event to wider air-traffic-system disruptions affecting multiple major hubs and the nationwide air-network, with various outlets offering parallel coverage of the same overall incident window.
Aviation Pros’ briefing for SmartMarty Sky summarized one recurring aviation datum linked to the period: at O’Hare, the year-to-date average taxi time from runway touchdown to gate for arriving flights was about 20 minutes over January through August, reflecting general operational congestion rather than specifics tied to the Denver incident. The briefing also incorporated context from other outlets describing related disruptions tied to aging ATC technology and a broader national halt in traffic flows, though it did not provide detailed causal connections to the Denver event itself.
In related coverage from Castanet and Yahoo Finance, broader aviation-disruption themes included security-related interruptions and other airport operations in the United States, including a Saturday evening brief closure of Dallas Love Field following an FAA alert—attributed to a security issue later described as unfounded—along with reports of a nationwide ground stop connected to aging air-traffic-control technology, which airlines had to navigate as operations began to normalize. The material notes these as part of the larger ecosystem of disruptions surrounding the Denver incident but does not specify direct causal links, flight numbers, or Times for the Denver event.