Y90 controller described handoff to wrong sector; with data block dropped an incursion occurred.

Attributes
ACN	705188
Time
Date	200607
Local Time Of Day	0601 To 1200
Place
Locale Reference	navaid : ctr.vor
State Reference	MA
Altitude	msl single value : 8000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : y90.tracon
Operator	general aviation : personal
Make Model Name	Skyhawk 172/Cutlass 172
Operating Under FAR Part	Part 91
Flight Phase	cruise : level
Flight Plan	IFR
Person 1
Function	controller : approach
Qualification	controller : radar
Experience	controller radar : 19 controller time certified in position1 : 19
ASRS Report	705188
Person 2
Affiliation	other
Function	flight crew : single pilot
Events
Anomaly	airspace violation : entry non adherence : required legal separation
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Consequence	faa : investigated
Supplementary
Problem Areas	ATC Human Performance
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Deviation

Narrative:

I took a handoff on aircraft X from ZBW gardner sector (gdm). Aircraft was on a non-approved routing through the last sector; ZBW pauling (pwl) sector. After establishing 2-WAY communication with aircraft X; I then coordination the appropriate route with the ZBW pwl sector. I issued the route to the pilot and coordination with data to amend the route. The next thing I recall aircraft X tag was on aircraft; meaning the sector had taken the handoff. I pointed out the traffic to alb approach and switched the aircraft X to the pwl sector. I later found out that I had inadvertently directed the handoff on aircraft X to the previous (gdm) sector. That controller accepted the handoff and then dropped the data which eliminated the track for the pwl sector. The pwl sector was conducting a relief briefing when aircraft X checked frequency and nobody responded to the aircraft. The aircraft had traveled several mi into the sector before the situation was noticed.

Original NASA ASRS Text

Title: Y90 CTLR DESCRIBED HDOF TO WRONG SECTOR; WITH DATA BLOCK DROPPED AN INCURSION OCCURRED.

Narrative: I TOOK A HDOF ON ACFT X FROM ZBW GARDNER SECTOR (GDM). ACFT WAS ON A NON-APPROVED ROUTING THROUGH THE LAST SECTOR; ZBW PAULING (PWL) SECTOR. AFTER ESTABLISHING 2-WAY COM WITH ACFT X; I THEN COORD THE APPROPRIATE RTE WITH THE ZBW PWL SECTOR. I ISSUED THE RTE TO THE PLT AND COORD WITH DATA TO AMEND THE RTE. THE NEXT THING I RECALL ACFT X TAG WAS ON ACFT; MEANING THE SECTOR HAD TAKEN THE HDOF. I POINTED OUT THE TFC TO ALB APCH AND SWITCHED THE ACFT X TO THE PWL SECTOR. I LATER FOUND OUT THAT I HAD INADVERTENTLY DIRECTED THE HDOF ON ACFT X TO THE PREVIOUS (GDM) SECTOR. THAT CTLR ACCEPTED THE HDOF AND THEN DROPPED THE DATA WHICH ELIMINATED THE TRACK FOR THE PWL SECTOR. THE PWL SECTOR WAS CONDUCTING A RELIEF BRIEFING WHEN ACFT X CHKED FREQ AND NOBODY RESPONDED TO THE ACFT. THE ACFT HAD TRAVELED SEVERAL MI INTO THE SECTOR BEFORE THE SITUATION WAS NOTICED.

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