Narrative:

An E170 departed phl; routed over ditch intersection; and was going to the center structure. Almost immediately the data tag went into (if) inter facility failure; so I knew this might be a manual hand-off to dixie sector in ZNY. After numerous tries for an automated hand-off failed; I then tried to contact dixie for a manual hand-off between 15-20 miles from the border. There was no reply. My sector started to become complex as more departures routed over ditch went airborne. I stopped all south departures to deal with not be able to get in contact with dixie sector. I tried numerous times to coordinate a hand-off on the (4114) line for dixie sector with no reply. My only option in my mind is to get the E170 back in my airspace; so I descended and turned the aircraft back into my airspace to prevent any further problems that may have occurred. This is a problem because we enter ZNY airspace on a narrow corridor which leaves no option to turn right or left to stay in our own airspace. I attempted to contact ZDC for a point-out anticipating I was going to have to hold the E170; the reply indicating that ZDC didn't own airspace that far north. We at phl don't have a center breakdown of airspace between ZNY and ZDC which would have been helpful. Eventually the supervisor was able to get a hold of dixie sector to begin coordinating hand-offs. Apparently the dixie sector was very busy at the time and was unable to answer the land line; which turned out to be a huge problem for me as I had no outs. Dixie sector said there was an automation problem because there were two flight plans in the system under the same call sign. As it turned out we had taken a hand-off on the E170 from spuds intersection to our north from ZNY. This is why the hand-off would not automate. Part of the problem is the airline scheduled a departure and an arrival during the same arrival/departure bank; which causes automation issues with the center. The scheduling overlap should be widened to 6 hours in my opinion to allow for delays caused by south.west.a.P. Luckily there were aircraft separation issues and dixie sector was not negatively impacted by the od (operator deviation); however the fact remains; how do we deal with our departures in the future when the center decides they can't take a hand-off. My suggestions are as follows: 1. We need a center structure breakdown of the sectors above phl airspace; both ZNY and ZDC. This would have given me a better opportunity to talk to the right controller for a point-out so as to not abuse any one's airspace. 2. There needs to be better coordination between ATC and the airlines about coordinating call sign changes with aircraft that are going the share the call sign. I had no idea there was another same call signs flight from our north until after the fact. I'm aware that this is a nationwide problem; but this time resulted into a snowball that took one of my options of coordinating a hand-off away. 3. If ATC and the airlines can't find a way to deal with call sign issues; the equipment automation needs to address situations when the same call sign is used; that will still allow us to make an automated hand-offs. 4. With airspace redesign in effect; it would be helpful if that area of the airspace was ours 12;000 ft and below to allow such an out should it happen more frequently. This was a known event in which I had to get the supervisor to get in contact with dixie sector. Given the same situation; I don't know of anything else that could have been done to prevent this from happening again. Although this is not a norm; it does happen from time to time which deserves attention; so I; and the rest of my team; don't get caught with no options to protect ourselves. Keep in mind I started manual hand-offs well in advance anticipating a potential problem.

Related reports:

Google
 

Original NASA ASRS Text

Title: PHL TRACON controller described failed hand off attempt to ZNY resulting in an airspace infraction; the reporter listing automated hand off limitations; lack of Center airspace descriptions; and airspace redesign/s as possible solutions similar events.

Narrative: An E170 departed PHL; routed over Ditch Intersection; and was going to the Center structure. Almost immediately the data tag went into (IF) inter facility failure; so I knew this might be a manual hand-off to Dixie Sector in ZNY. After numerous tries for an automated hand-off failed; I then tried to contact Dixie for a manual hand-off between 15-20 miles from the border. There was no reply. My sector started to become complex as more departures routed over Ditch went airborne. I stopped all South departures to deal with not be able to get in contact with Dixie Sector. I tried numerous times to coordinate a hand-off on the (4114) line for Dixie Sector with no reply. My only option in my mind is to get the E170 back in my airspace; so I descended and turned the aircraft back into my airspace to prevent any further problems that may have occurred. This is a problem because we enter ZNY airspace on a narrow corridor which leaves no option to turn right or left to stay in our own airspace. I attempted to contact ZDC for a point-out anticipating I was going to have to hold the E170; the reply indicating that ZDC didn't own airspace that far North. We at PHL don't have a Center breakdown of airspace between ZNY and ZDC which would have been helpful. Eventually the Supervisor was able to get a hold of Dixie Sector to begin coordinating hand-offs. Apparently the Dixie Sector was very busy at the time and was unable to answer the land line; which turned out to be a huge problem for me as I had no outs. Dixie Sector said there was an automation problem because there were two flight plans in the system under the same call sign. As it turned out we had taken a hand-off on the E170 from SPUDS Intersection to our north from ZNY. This is why the hand-off would not automate. Part of the problem is the airline scheduled a departure and an arrival during the same arrival/departure bank; which causes automation issues with the Center. The scheduling overlap should be widened to 6 hours in my opinion to allow for delays caused by S.W.A.P. Luckily there were aircraft separation issues and Dixie Sector was not negatively impacted by the OD (operator deviation); however the fact remains; how do we deal with our departures in the future when the Center decides they can't take a hand-off. My suggestions are as follows: 1. We need a Center structure breakdown of the sectors above PHL airspace; both ZNY and ZDC. This would have given me a better opportunity to talk to the right controller for a point-out so as to not abuse any one's airspace. 2. There needs to be better coordination between ATC and the Airlines about coordinating call sign changes with aircraft that are going the share the call sign. I had no idea there was another same call signs flight from our north until after the fact. I'm aware that this is a nationwide problem; but this time resulted into a snowball that took one of my options of coordinating a hand-off away. 3. If ATC and the airlines can't find a way to deal with call sign issues; the equipment automation needs to address situations when the same call sign is used; that will still allow us to make an automated hand-offs. 4. With airspace redesign in effect; it would be helpful if that area of the airspace was ours 12;000 ft and below to allow such an out should it happen more frequently. This was a known event in which I had to get the Supervisor to get in contact with Dixie Sector. Given the same situation; I don't know of anything else that could have been done to prevent this from happening again. Although this is not a norm; it does happen from time to time which deserves attention; so I; and the rest of my team; don't get caught with no options to protect ourselves. Keep in mind I started manual hand-offs well in advance anticipating a potential problem.

Data retrieved from NASA's ASRS site as of April 2012 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.