|37000 Feet||Browse and search NASA's
Aviation Safety Reporting System
|Local Time Of Day||1201 To 1800|
|Locale Reference||atc facility : bwz|
|Altitude||msl bound lower : 7000|
msl bound upper : 7000
|Operator||general aviation : corporate|
|Make Model Name||Small Transport, Low Wing, 2 Turbojet Eng|
|Flight Phase||cruise other|
|Route In Use||arrival other|
enroute airway : n90
|Affiliation||government : faa|
|Function||controller : radar|
|Qualification||controller : radar|
|Experience||controller military : 3|
controller non radar : 3
controller radar : 19
|Function||flight crew : captain|
oversight : pic
|Qualification||pilot : atp|
|Anomaly||non adherence : published procedure|
other anomaly other
|Independent Detector||other controllera|
|Resolutory Action||controller : issued new clearance|
|Consequence||faa : investigated|
|Primary Problem||ATC Human Performance|
|Air Traffic Incident||Intra Facility Coordination Failure|
I was working the bwz sector at ZNY. At approximately XX30 local, I accepted a handoff on small transport. I instructed the transferring controller to assign a heading of 030 degrees for traffic. After the communications transfer was made, I instructed the aircraft to proceed direct to bwz. I initiated a computer handoff to the ny TRACON. The aircraft was getting close to the TRACON boundary and they had not accepted the handoff. I called approach control twice on the handoff phone line, informed my supervisor of the problem and instructed the aircraft to make a 360 degree turn. My supervisor called the supervisor involved at the TRACON and was told that the handoff was flashing at the wrong sector (which I have no control over) and that there was 'no problem,' even though the aircraft had crossed the boundary while making the 360 degree turn. Immediately, the controller at the TRACON called and said that there was 'no problem.' the aircraft was never in conflict with another aircraft. When I reported for my next assigned shift, I was informed that the TRACON had reported that I had allowed an aircraft to violate their airspace and that my radar rating was suspended and I was to report to the training department.
Original NASA ASRS Text
Title: ACFT PENETRATED ADJACENT AIRSPACE WITHOUT AUTHORIZATION.
Narrative: I WAS WORKING THE BWZ SECTOR AT ZNY. AT APPROX XX30 LCL, I ACCEPTED A HDOF ON SMT. I INSTRUCTED THE TRANSFERRING CTLR TO ASSIGN A HDG OF 030 DEGS FOR TFC. AFTER THE COMS TRANSFER WAS MADE, I INSTRUCTED THE ACFT TO PROCEED DIRECT TO BWZ. I INITIATED A COMPUTER HDOF TO THE NY TRACON. THE ACFT WAS GETTING CLOSE TO THE TRACON BOUNDARY AND THEY HAD NOT ACCEPTED THE HDOF. I CALLED APCH CTL TWICE ON THE HDOF PHONE LINE, INFORMED MY SUPVR OF THE PROB AND INSTRUCTED THE ACFT TO MAKE A 360 DEG TURN. MY SUPVR CALLED THE SUPVR INVOLVED AT THE TRACON AND WAS TOLD THAT THE HDOF WAS FLASHING AT THE WRONG SECTOR (WHICH I HAVE NO CONTROL OVER) AND THAT THERE WAS 'NO PROB,' EVEN THOUGH THE ACFT HAD CROSSED THE BOUNDARY WHILE MAKING THE 360 DEG TURN. IMMEDIATELY, THE CTLR AT THE TRACON CALLED AND SAID THAT THERE WAS 'NO PROB.' THE ACFT WAS NEVER IN CONFLICT WITH ANOTHER ACFT. WHEN I RPTED FOR MY NEXT ASSIGNED SHIFT, I WAS INFORMED THAT THE TRACON HAD RPTED THAT I HAD ALLOWED AN ACFT TO VIOLATE THEIR AIRSPACE AND THAT MY RADAR RATING WAS SUSPENDED AND I WAS TO RPT TO THE TRNING DEPT.
Data retrieved from NASA's ASRS site as of August 2007 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.