JetBlue pilot reports drone strike during landing at JFK

JetBlue said a pilot on Flight 948 reported striking a drone while the aircraft was landing at John F. Kennedy International Airport on June 29, in an incident that immediately raised fresh concerns about drone safety near crowded airspace.

The flight had departed Las Vegas overnight and was on final approach to JFK when the pilot told air traffic control the aircraft had collided with a drone, according to reporting cited by multiple outlets. The plane was flying at about 3,000 feet when the encounter was reported.

The jet landed safely around 7:15 a.m. ET. No one on board was reported injured, and the flight completed the approach without needing assistance.

JetBlue then removed the aircraft from service for a post-flight inspection. The airline said the check found no damage and no evidence of a collision.

The Federal Aviation Administration said the aircraft landed safely and no damage was immediately reported. The agency said it is investigating the incident.

What happened on approach

The sequence reported by JetBlue and other outlets is straightforward: the flight descended toward JFK, the crew reported a possible drone strike, and the airplane continued to a safe landing.

The precise nature of the object remains unresolved. Pilot audio and some reporting describe a drone strike, but JetBlue’s inspection did not find physical signs of impact. That leaves open whether the aircraft hit a drone, clipped an object that left no visible trace, or reported a suspected collision that proved impossible to confirm after landing.

The distinction matters because the encounter occurred during a critical phase of flight. Aircraft on approach are low enough that small unmanned aircraft can create a serious hazard even if they do not cause obvious damage.

Safety concerns near JFK

The reported incident adds to wider concern about drones near major airports, especially in the New York area. Drone activity in controlled airspace is a recurring enforcement problem because identifying operators can be difficult even when pilots or air traffic controllers report sightings.

AP reported that hours later, a helicopter had a near miss with a remote-control aircraft near the same area. That was described as a separate incident, but it reinforced the broader concern around unauthorized aircraft in the region.

The FAA has repeatedly warned about the risks posed by drones near airports, where departures and arrivals leave little room for error. Even a small object can force an airline, regulators, and investigators to reconstruct what happened from pilot reports, radar data, and post-flight inspection results.

What investigators will look for

The FAA investigation will focus on whether the JetBlue aircraft actually struck a drone, what the object may have been if one was involved, and whether an operator can be identified.

JetBlue’s inspection finding no damage narrows the physical evidence, but it does not by itself resolve the event. Investigators may still review flight recordings, crew reports, air traffic control communications, and any available surveillance or radar data from the area.

For now, the operational impact appears limited to the removal of the aircraft from service for inspection and the ongoing federal review. The flight landed safely, and the airline has not reported injuries or visible damage.

The unanswered question is whether the reported drone encounter was a confirmed strike or a suspected collision that left no trace on the plane. That distinction will likely determine how the FAA frames the incident and whether enforcement action follows.