Date: 201402
Local time of day: 0001-0600
Location: ZNY.ARTCC, NY
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Descent
Airspace: Class A ZNY
ATC / advisory: Center ZNY
Second aircraft: B737 Undifferentiated or Other Model
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown
Second reporter function: First Officer
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Aircraft RA; Person Air Traffic Control
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Procedure; Human Factors; Airspace Structure
Primary problem: Ambiguous

Narrative: Aircraft X; an ISP arrival northeast bound routed on preferential routing to ISP was high; descending to FL210. Aircraft Y; an ISP departure was opposite direction level at FL280 and Aircraft Z; a JFK departure was climbing to FL270 underneath Aircraft Y; a couple miles off his right and converging. Aircraft X's descent rate was not enough to descend under Y (or Z) and apparently the Washington Center Controller didn't recognize the situation. We (the 2 controllers at N66) tried calling to find out what was happening; but were not answered. At approximately 12 o'clock and 5 miles X was at 28;500 descending to 21;000 through both Y (level at 28;000) and Z (25;700 climbing to 27;000). After being relieved and going to observe a replay on the FALCON system it appears that at 12 o'clock and 2 miles the altitudes were 28;200 and 28;000 with a 900 KT closure. The next hit showed X having climbed to 28;500 and Y having descended to 27;200 (800 FT in 12 seconds) and also Z reversed on that one hit from having climbed on the previous hit; to having descended. I believe all 3 planes received TCAS warnings and instructions; without which there would have been a collision. There is no excuse for the fact that this section of airspace has preferential departure routes and preferential arrival routes in both directions on the same airway; or on 2 airways not laterally separated from each other. The involved routes are J174/J121/V139. On these routes we have JFK departures climbing south westbound; ISP and Connecticut airport departures climbing south westbound; PHL arrivals descending south westbound; ISP and Connecticut arrivals descending north eastbound and PHL departures climbing north eastbound (though for the most part; these are kept west of this airspace). They are all on the same airway; always in conflict. The rest of ZNY; and; I would assume; the country; use one way airways for departure and arrival routes. It is ridiculously unsafe to have this one section of airspace DESIGNED to have aircraft head on descending and climbing through each other all on the same airway. Something needs to be done about this; today we came 6 seconds and 3(!) TCAS resolutions from 1 if not 2 midair collisions. Collisions that would not have happened if the routes those aircraft were assigned were not designed to create this situation over and over again on a daily basis.


Second narrative: On vector with New York Center near BRIGS Intersection; ATC requested an expedited descent from FL390 to FL210. Vertical Speed was approximately 3;000 FPM. As we approached FL290; ATC told someone to maintain FL290; call sign unclear. I immediately asked; 'Who was that for?' ATC did not repeat the instruction or ask anyone for confirmation. Shortly thereafter; we and two other aircraft got RA's. We climbed from about FL280 to about 288; lots of confusion on ATC's part. After the incident; we proceeded uneventfully to destination.


Synopsis: A ZNY Controller and one of the plots involved describe a three way TCAS event that may have resulted in collisions without TCAS intervention.