Delta Flight Aborts Takeoff at JFK After Flames Seen

Follow us on Google

Passengers on a Delta Air Lines flight departing New York’s John F. Kennedy International Airport experienced a tense takeoff attempt when the aircraft abruptly braked on the runway after what witnesses described as flames coming from one of the engines, prompting a temporary runway closure and widespread delays.

Aborted Takeoff Triggers Runway Shutdown

According to flight tracking data and contemporaneous accounts shared on aviation forums and social media, the incident involved Delta Air Lines Flight 28, which was preparing for departure from JFK on Tuesday. As the aircraft accelerated for takeoff, the crew rejected the takeoff roll, bringing the jet to a rapid stop on the runway.

Multiple passengers posting online reported seeing bursts of flame from one of the engines, followed by the smell of fuel and a sudden deceleration. Others described emergency vehicles quickly surrounding the aircraft as it remained on the runway. Publicly available information indicates that the jet did not leave the pavement and there were no immediate reports of injuries.

Airport operations information and passenger accounts indicate that the runway used for the attempted departure was temporarily taken out of service while personnel inspected the surface for debris, leaked fuel or damage. Departures and arrivals were rerouted to other runways, causing delays and a growing queue of aircraft waiting to depart JFK.

Reports from travelers at the airport describe aircraft taxiing in a slow “parade” pattern toward alternative runways while crews and ground teams managed the disruption caused by the closure.

Onboard Passengers Describe Flames and Sudden Stop

Passengers aboard the Delta flight recounted a routine taxi and lineup before the takeoff roll began to feel unusual. Several travelers posting in real time said they saw what looked like flames or a flash from the left side of the aircraft just as the jet was gaining speed, followed almost immediately by heavy braking.

Others described a strong smell of fuel and the sound of the engines throttling down as the plane slowed. Cabin crew instructed passengers to remain seated while emergency vehicles approached, according to these public accounts. Some travelers reported that they initially believed they were already airborne due to the intensity of the braking before realizing the aircraft was still on the ground.

Publicly available information suggests that passengers ultimately remained on board while the aircraft was assessed, before being moved back to a gate. Several individuals posting online reported that they were later rebooked or transferred to another aircraft for their onward travel, though exact timelines varied depending on their connecting flights and destinations.

Despite the dramatic nature of the rejected takeoff and the visible flames reported by passengers, there were no immediate indications of injuries among those on board, based on available public reporting.

Operational Impact Across a Busy Evening at JFK

The aborted takeoff occurred during an already active period at JFK, one of the busiest international gateways in the United States. With one runway closed for inspection and cleanup, air traffic was funneled onto remaining surfaces, compounding delays for both departing and arriving flights.

Travelers and aviation enthusiasts monitoring real-time flight data observed a line of aircraft taxiing toward alternate runways as departure times slipped. Some passengers on unrelated flights reported being held in extended taxi patterns or waiting at gates as controllers sequenced traffic and airport crews completed work on the affected runway.

Based on publicly available flight-tracking information and passenger commentary, the disruption lasted long enough to cause knock-on effects for later departures, with some flights pushed back significantly from their scheduled times. However, once the runway inspection was complete and any potential debris or fuel was cleared, normal operations gradually resumed.

JFK has experienced similar operational snarls after previous runway incidents, and the latest episode again highlighted how a single disabled aircraft or precautionary closure can reverberate across a complex hub schedule.

Rejected Takeoffs and Safety Protocols

Abruptly stopping a takeoff, known in aviation as a rejected takeoff, is a well-established safety procedure used when crews detect a potential problem before the aircraft leaves the ground. Publicly available safety analyses describe it as a conservative measure taken in response to engine anomalies, system warnings, or external hazards on the runway.

In this case, reports from passengers and online aviation communities suggest that the crew responded quickly to signs of an engine issue, including visible flames and a possible fuel leak. Modern airliners are designed to withstand high-energy rejected takeoffs, and pilots train extensively in simulators for precisely these scenarios, including heavy braking and coordination with emergency services.

Published safety data and previous incident reports show that while rejected takeoffs can be alarming for those on board, they often prevent more serious outcomes by keeping an aircraft on the runway rather than allowing it to become airborne with a developing mechanical problem. Ground crews, firefighters and maintenance teams then work together to secure the aircraft, assess any damage and inspect the runway for hazards.

In the wake of the Delta Flight 28 incident at JFK, publicly available information indicates that standard protocols were followed: the takeoff was halted, emergency services responded, the runway was closed for inspection, and the aircraft was held until it was considered safe to move. Further details about any underlying mechanical issues are expected to emerge from subsequent technical evaluations and regulatory reporting.