37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1152887 |
Time | |
Date | 201402 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | ZNY.ARTCC |
State Reference | NY |
Aircraft 1 | |
Make Model Name | B737-700 |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Route In Use | Vectors |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | B737 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Person 2 | |
Function | First Officer |
Experience | Flight Crew Last 90 Days 330 Flight Crew Type 6500 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy |
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.
Original NASA ASRS Text
Title: A ZNY Controller and one of the plots involved describe a three way TCAS event that may have resulted in collisions without TCAS intervention.
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.
Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.