Narrative:

While working the radar associate position we had an airspace deviation involving commuter airplane and an approach control. The traffic was moderate with complex situations. I was busy doing various radar associate duties, ie, coordinating estimates with canada and other adjacent sectors. I was also posting my flight progress strips, as well as helping the radar controller with pointouts, handoffs and the moving of data blocks to prevent overlap. During this time period I looked at the radar, and I noticed 1 of the aircraft we're working was inside the approach controls airspace west/O a manual, or automated handoff. I then immediately asked the radar controller if he had made a manual handoff in which he said no. I then called the approach control and made a manual handoff in which they accepted. The point where the deviation occurred, is right at the parameter where we or the computer can initiate an automated handoff and have it 'flash' west/O 'failing'. 90 percent of the time we do need to make a manual handoff along this route. Supplemental information from acn 152736. I was the radar controller at combined sectors spanning over 100 NM, involved with military operating areas, air refueling rtes, ir rtes, montreal and btv arrs and departures. Air carrier X on V322 was allowed to enter manchester approach airspace west/O a handoff. Automated handoffs on this airway 'fail' until they are within 5 NM of the boundary. This requires undivided attention to aircraft on V322. I was too busy to provide this. The parameters for automated handoffs should be increased.

Google
 

Original NASA ASRS Text

Title: ACR ENTERED ADJACENT FAC AIRSPACE WITHOUT HANDOFF.

Narrative: WHILE WORKING THE RADAR ASSOCIATE POS WE HAD AN AIRSPACE DEV INVOLVING COMMUTER AIRPLANE AND AN APCH CTL. THE TFC WAS MODERATE WITH COMPLEX SITUATIONS. I WAS BUSY DOING VARIOUS RADAR ASSOCIATE DUTIES, IE, COORDINATING ESTIMATES WITH CANADA AND OTHER ADJACENT SECTORS. I WAS ALSO POSTING MY FLT PROGRESS STRIPS, AS WELL AS HELPING THE RADAR CTLR WITH POINTOUTS, HDOFS AND THE MOVING OF DATA BLOCKS TO PREVENT OVERLAP. DURING THIS TIME PERIOD I LOOKED AT THE RADAR, AND I NOTICED 1 OF THE ACFT WE'RE WORKING WAS INSIDE THE APCH CTLS AIRSPACE W/O A MANUAL, OR AUTOMATED HDOF. I THEN IMMEDIATELY ASKED THE RADAR CTLR IF HE HAD MADE A MANUAL HDOF IN WHICH HE SAID NO. I THEN CALLED THE APCH CTL AND MADE A MANUAL HDOF IN WHICH THEY ACCEPTED. THE POINT WHERE THE DEV OCCURRED, IS R AT THE PARAMETER WHERE WE OR THE COMPUTER CAN INITIATE AN AUTOMATED HDOF AND HAVE IT 'FLASH' W/O 'FAILING'. 90 PERCENT OF THE TIME WE DO NEED TO MAKE A MANUAL HDOF ALONG THIS RTE. SUPPLEMENTAL INFO FROM ACN 152736. I WAS THE RADAR CTLR AT COMBINED SECTORS SPANNING OVER 100 NM, INVOLVED WITH MIL OPERATING AREAS, AIR REFUELING RTES, IR RTES, MONTREAL AND BTV ARRS AND DEPS. ACR X ON V322 WAS ALLOWED TO ENTER MANCHESTER APCH AIRSPACE W/O A HDOF. AUTOMATED HDOFS ON THIS AIRWAY 'FAIL' UNTIL THEY ARE WITHIN 5 NM OF THE BOUNDARY. THIS REQUIRES UNDIVIDED ATTN TO ACFT ON V322. I WAS TOO BUSY TO PROVIDE THIS. THE PARAMETERS FOR AUTOMATED HDOFS SHOULD BE INCREASED.

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