Two Planes Came Within 500 Feet at JFK

A regional jet and a small private plane came uncomfortably close while approaching JFK on Monday, May 4. That matters because JFK runs tightly packed arrival flows all day, and when two aircraft converge near the airport, the margin for error gets very small very fast. The basic news is this: Endeavor Air Flight 5289 was on final for Runway 22L when a Cirrus SR22 crossed toward Runway 22R, and the two aircraft ended up close enough to trigger fresh alarm around JFK’s safety picture. (faa.gov) ### Which planes were involved? The commercial flight was Endeavor Air 5289, a Delta Connection regional jet. The other aircraft was a Cirrus SR22, a common single-engine personal plane. Both were approaching JFK around 5:15 p.m. local time on May 4, and both were aiming to land — just on different parallel runways. (faa.gov) ### H(faa.gov)f vertical separation at the closest point, based on preliminary Flightradar24 data cited by ABC7. The aircraft were also about half a mile apart laterally as their paths crossed. In plain English, that is not “almost touching,” but it is close enough that pilots, controllers, and regulators take it very seriously near a major airport. (abc7ny.com) ### Did the planes actually break the rules? Maybe not — and that is the key wrinkle. The FAA’s statement says air traffic control gave both pilots traffic advisories, both crews reported the other aircraft in sight, and “the required separation was maintained.” So the scary part here is less “two planes nearly collided” and more “the spacing got tight enough to look and sound bad, even if the formal minimums were still met.” (faa.gov) ### What did the pilots hear? Air traffic control audio helps explain why this turned into a story. The Endeavor crew was told the Cirrus was about 500 feet above them and crossing left to right, roughly half a mile ahead. The regional jet crew also reported getting a traffic advisory and then a resolution advisory from the onboard collision-avoidance system — though the system reportedly told(faa.gov)sts the safety nets were active, even if they did not command a dramatic maneuver. (abc7ny.com) ### Why do parallel runways make this tricky? JFK often lands planes on parallel runways at the same time. That works, but only if everybody stays precisely on the correct approach path. Think of it like two highway lanes separated by a barrier that suddenly narrows near an exit — small drift matters much more than it would in open space. A small aircraft crossing toward the neighboring runway can make a routine arrival feel dangerous in seconds. (faa.gov) ### Why does this feel bigger than one incident? Because it is the second JFK close-call story in about two weeks. In the earlier April 21 event, Republic Airways Flight 4464 and Jazz Aviation Flight 554 had to break off their approaches after one aircraft overshot toward the parallel runway’s course. Flight data in that case showed about half a mile of lateral spacing and roughly 350 feet vertically. So this latest episode lands in a pattern, not a vacuum. (patch.com) ### Has JFK had broader safety trouble before? Yes — and that context matters. The NTSB’s 2024 report on the January 2023 JFK runway incursion, when an American Airlines jet crossed in front of a departing Delta plane, led to multiple safety recommendations for the FAA. That was a ground event, not an airborne approach conflict, but it added to the sense that JFK is one of the system’s stress points. Busy airport, complex geometry, little room for sloppiness. (ntsb.gov) ### So what is the real takeaway? The good news is that nobody was hurt, the planes landed safely, and the FAA says required separation held. But the catch is that “safe enough under the rules” can still look brittle to passengers and crews when aircraft are only a few hundred feet apart near one of the country’s busiest airports. That is why these episodes keep drawing scrutiny (ntsb.gov)ople want. (faa.gov)