What’s the procedure in a case like the guy who was sucked into that Frontier a321 engine, and who is responsible for the engine cleanup?

Frontier Airlines Flight 4345, an Airbus A321 registered N607FR, executed a rejected takeoff on Runway 17L at Denver International Airport on the night of May 8, 2026, after the aircraft struck an unauthorized pedestrian on the runway during the takeoff roll. The crew aborted the departure — reportedly calling out "we're stopping… we just hit somebody, engine fire" on ATC frequencies — and initiated emergency evacuation of 231 passengers and crew via slides. Denver Fire Department extinguished a brief engine fire, and the aircraft was grounded for investigation. The NTSB assumed lead investigative authority, with TSA and FAA runway security elements also implicated given the nature of the runway breach. The victim's access to an active runway at a Class B airport during nighttime departure operations represents a critical security and airside access failure that will draw scrutiny well beyond the airworthiness investigation itself.

From a procedural standpoint, the crew's actions align precisely with the Airbus A321 QRH and standard 14 CFR Part 121 rejected takeoff protocol. An RTO initiated below V1 — the decision speed, typically 130–140 knots for an A321 at or near max takeoff weight — is always the correct call when engine fire, severe FOD ingestion, or an unsafe condition is confirmed. Once stopped, the QRH engine fire checklist drives the fire handle pull sequence, which simultaneously closes the fuel shutoff valve, isolates hydraulics, and enables Halon fire agent discharge. Smoke in the cabin elevates the situation to an evacuation threshold, which the crew correctly executed. Aircraft Rescue and Firefighting (ARFF) units respond under FAA Advisory Circular 150/5210-6D and are pre-positioned during all departures and arrivals at certificated airports — their rapid containment of the fire was textbook. Nothing in the crew's decision chain appears improvised; every step follows a well-rehearsed pathway precisely designed for catastrophic FOD events.

Engine cleanup after human ingestion is classified as both a severe mechanical event and a biohazard operation, and responsibility falls squarely on the airline as the aircraft operator. Frontier will contract an MRO provider — potentially AAR Corp, which maintains facilities at DEN — to remove the affected engine, disassemble it, and perform ultrasonic and hot-wash procedures to clear biological material from compressor stages, blades, and nacelle structures. Human tissue introduces biohazard protocols governed by OSHA's 29 CFR 1910.1030 (bloodborne pathogen standards) and EPA medical waste disposal requirements, meaning the process is not simply a mechanical teardown but a regulated hazmat operation. Blade sets are individually inspected and likely replaced given the severity of ingestion; the engine itself may be sent for full teardown rather than on-wing repair. Cost estimates for this level of remediation run $500,000 to over $2 million per engine before the aircraft can be returned to airworthiness certification under FAA oversight. Denver International's operations authority holds independent responsibility for runway FOD sweep and debris clearance under FAA AC 150/5210-24 post-incident protocols, but the engine itself is entirely the airline's liability.

The broader operational lesson for flight crews and directors of operations across Part 121, 135, and Part 91K operations is that the FOD and runway incursion threat does not originate solely from hardware or wildlife — human intrusion onto movement areas, while statistically rare, has produced analogous events including the 2022 DFW ground worker ingestion incident involving a Southwest aircraft. That incident prompted renewed OSHA and FAA scrutiny of ground crew positioning during active operations; this Denver event will likely generate new TSA-driven review of perimeter access controls and airside credentialing at major hub airports. For flight crews, the takeaway is procedural discipline under extreme psychological stress: the instinct to assess an ambiguous situation before committing to an RTO must always yield to the established V1 abort criteria, and in this case the crew's rapid, correct execution of those criteria almost certainly prevented a far worse outcome for the passengers aboard. Security teams, ground handlers, and airport operations personnel should treat this event as a forcing function for re-examining the layered controls that are supposed to prevent any unauthorized person from reaching an active runway at a commercial service airport.