37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1071941 |
Time | |
Date | 201303 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | JFK.Airport |
State Reference | NY |
Aircraft 1 | |
Make Model Name | A320 |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Climb |
Flight Plan | IFR |
Person 1 | |
Function | Approach Departure |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
Jfk was on a 4 left/right operation with southwest traffic departing 31L; along with doing the white/wavey route swap. There was a large volume of traffic off runway 31L going to the next sector. Due to volume; they stopped traffic going to that sector. I called jfk local controller and verbally stopped all departures off runway 31L. Unknown to me; jfk tower and new york TRACON traffic management unit (tmu) were discussing southwest departures off jfk and the volume/in-trail. Someone either in new york TRACON tmu or jfk tower believed that meant that southwest bound traffic was released and started to depart runway 31L without my approval on jfk departure radar position or without coordination/approval from the jfk sector sequencer. This caused an airspace deviation into my sector. Traffic was stopped and should have not resumed. Jfk tower should be mandated to get release on all departure stops from the jfk area/departure controller. Even if there is a fix stop by tmu. The reason is that if there is either a stop from the departure controller or the tmu; the sector may use that airspace for other reasons that the tower or tmu are not aware of. The tower or tmu just releasing traffic into a sector without the sectors knowledge is very dangerous.
Original NASA ASRS Text
Title: N90 Controller expressed concern regarding the release procedures used for JFK Tower and the interaction of the TMU vs. the departure sectors.
Narrative: JFK was on a 4 L/R operation with southwest traffic departing 31L; along with doing the WHITE/WAVEY route swap. There was a large volume of traffic off Runway 31L going to the next sector. Due to volume; they stopped traffic going to that sector. I called JFK Local Controller and verbally stopped all departures off Runway 31L. Unknown to me; JFK Tower and New York TRACON Traffic Management Unit (TMU) were discussing southwest departures off JFK and the volume/in-trail. Someone either in New York TRACON TMU or JFK Tower believed that meant that southwest bound traffic was released and started to depart Runway 31L without my approval on JFK departure RADAR position or without coordination/approval from the JFK Sector sequencer. This caused an airspace deviation into my sector. Traffic was stopped and should have NOT resumed. JFK Tower should be mandated to get release on all departure stops from the JFK area/Departure Controller. Even if there is a fix stop by TMU. The reason is that if there is either a stop from the Departure Controller or the TMU; the sector may use that airspace for other reasons that the Tower or TMU are not aware of. The Tower or TMU just releasing traffic into a sector without the sectors knowledge is very dangerous.
Data retrieved from NASA's ASRS site as of July 2013 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.