An Airbus A320, flown as JetBlue Flight 94 from Orlando, FL [KMCO] to White Plains, NY [KHPN], reportedly took evasive actions during the arrival, to avoid a collision with a small plane. The news story was widely reported four days later.
Below is arrival portion of the route of flight, from FlightAware. Note the flight-planned crossing of the midsection of Long Island and the box-shaped route over the Sound, apparently to transition through the flows in/out of KLGA and/or KJFK.
If reports are accurate and the JetBlue crew did in fact take last-second evasive actions, this was most likely a controller error. And this does happen; controllers get bored or distracted. Or, they may be coming to work with deprived sleep, due to bad workshift planning, with compressed work schedules (though, many controllers ‘benefit’ from this type of schedule, by having what feels like a 3-day weekend every week).
In any event, if there is any possible ATC involvement, NATCA and FAA will both encourage the controller to file an ATSAP report. Doing so grants that controller immunity for his/her error, meaning less re-training and less discipline. More importantly (to FAA and NATCA), filing the ATSAP report means the Public will likely learn nothing more about what happened here.
Why not? Because in May 2014, FAA Administrator Huerta signed off on a new administrative rule that declared all ATSAP report data ‘fully exempt’ from release under FOIA laws. Now, not even the courts will compel release of ATSAP data. This change makes ATSAP effectively a ‘black hole’ for U.S. aviation safety data. Thus, no matter how diligently the media investigates this incident, FAA will refuse to release the real details, as reported by the controller.
If it helps to sweeten your bitter, just give it a fuzzy new name and catch-phrase: