Aircraft entered adjacent sector's airspace without a handoff.

Attributes
ACN	106717
Time
Date	198903
Day	Sat
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : dls
State Reference	OR
Altitude	msl bound lower : 16000 msl bound upper : 16000
Environment
Flight Conditions	IMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zse
Operator	common carrier : air carrier
Make Model Name	Small Transport
Flight Phase	cruise other
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : flight data
Qualification	controller : radar
ASRS Report	106717
Person 2
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
ASRS Report	106714
Events
Anomaly	non adherence : published procedure other anomaly other other anomaly other
Independent Detector	other controllera
Resolutory Action	other
Consequence	Other
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Deviation Inter Facility Coordination Failure
Situations
ATC Facility	procedure or policy : unspecified

Narrative:

I was working the d-side of sector 09 at sea ARTCC. Sector 05 called to ask if I knew anything about air carrier X. I replied affirmative, he had departed pasco for pdx. The sector 05 controller asked if the uncorrelated beacon 20 mi south of mount adams (which is in sector 05 airspace) could be him. I replied that it could be and I would find out. I told the r-side controller. He idented the aircraft and verified the mode C. It was indeed the target in question. I did a flight plan readout on the aircraft and the flight plan was not stored. I entered a new flight plan. The r-side started track, handed off the data block and shipped the aircraft to sector 05. Computer data shows that I had removed strips on the aircraft. The only thing I could think of is that I had accidentally 'rs' (removed strip) the aircraft by mistake when pasco tower called an arrival time on a pasco arrival. The way the pasco strip posting is handled, a pasco to pdx flight is only posted with the departure strip in the pasco bay. This strip is always right next to the first aircraft in the pasco arrival sequence. If a blank strip holder was kept between the arrs and departures in the pasco bay it would provide some physical sep between these strips and possibly decrease the odds of this happening again.

Original NASA ASRS Text

Title: ACFT ENTERED ADJACENT SECTOR'S AIRSPACE WITHOUT A HANDOFF.

Narrative: I WAS WORKING THE D-SIDE OF SECTOR 09 AT SEA ARTCC. SECTOR 05 CALLED TO ASK IF I KNEW ANYTHING ABOUT ACR X. I REPLIED AFFIRMATIVE, HE HAD DEPARTED PASCO FOR PDX. THE SECTOR 05 CTLR ASKED IF THE UNCORRELATED BEACON 20 MI S OF MOUNT ADAMS (WHICH IS IN SECTOR 05 AIRSPACE) COULD BE HIM. I REPLIED THAT IT COULD BE AND I WOULD FIND OUT. I TOLD THE R-SIDE CTLR. HE IDENTED THE ACFT AND VERIFIED THE MODE C. IT WAS INDEED THE TARGET IN QUESTION. I DID A FLT PLAN READOUT ON THE ACFT AND THE FLT PLAN WAS NOT STORED. I ENTERED A NEW FLT PLAN. THE R-SIDE STARTED TRACK, HANDED OFF THE DATA BLOCK AND SHIPPED THE ACFT TO SECTOR 05. COMPUTER DATA SHOWS THAT I HAD REMOVED STRIPS ON THE ACFT. THE ONLY THING I COULD THINK OF IS THAT I HAD ACCIDENTALLY 'RS' (REMOVED STRIP) THE ACFT BY MISTAKE WHEN PASCO TWR CALLED AN ARR TIME ON A PASCO ARR. THE WAY THE PASCO STRIP POSTING IS HANDLED, A PASCO TO PDX FLT IS ONLY POSTED WITH THE DEP STRIP IN THE PASCO BAY. THIS STRIP IS ALWAYS RIGHT NEXT TO THE FIRST ACFT IN THE PASCO ARR SEQUENCE. IF A BLANK STRIP HOLDER WAS KEPT BTWN THE ARRS AND DEPS IN THE PASCO BAY IT WOULD PROVIDE SOME PHYSICAL SEP BTWN THESE STRIPS AND POSSIBLY DECREASE THE ODDS OF THIS HAPPENING AGAIN.

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.