Air carrier X unauthorized penetration of airspace. Operational deviation.

Attributes
ACN	151425
Time
Date	199007
Day	Tue
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : yul
State Reference	PQ
Altitude	msl bound lower : 7000 msl bound upper : 7000
Environment
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : yul tracon : btv
Operator	common carrier : air carrier
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	cruise other
Route In Use	enroute : direct
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar
Experience	controller radar : 8
ASRS Report	151425
Person 2
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar
Events
Anomaly	non adherence : published procedure other anomaly other
Independent Detector	other flight crewa
Resolutory Action	none taken : detected after the fact
Consequence	Other
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Deviation

Narrative:

I was assigned the radar approach control position. I accepted an automated handoff on air carrier X, an overflt through our area, northbound to montreal (yul) at 7000' MSL. I received a radio call from air carrier X and issued him an altimeter setting. Because our computer is not interfaced with montreal terminal (approach control) I contacted them to forward an estimate for the flight over plattsburgh VOR. I estimated air carrier X would cross plb VOR at xx:yz. I issued instructions to another aircraft assigned 7000 and remember checking air carrier X position relative to the second aircraft. Air carrier X had, to the best of my recollection, a full data block (ARTS ii a). My relief showed up and I gave her a briefing. I did not mention air carrier X during the briefing. The flight progress strip was not in with the active traffic. It was next to the landline buttons and inactive strips, from my previous coordination call (per the relieving controller). Air carrier X contacted my relief and questioned whether he was on the right frequency and beacon code. (He knew something was wrong). My relief knew nothing about the flight. Air carrier X contacted montreal on his own. Montreal controllers idented the flight near montreal. The controller that relieved me advised me of the situation...I do not know why the data block disappeared on air carrier X... But that is irrelevant. I forgot him.

Original NASA ASRS Text

Title: ACR X UNAUTH PENETRATION OF AIRSPACE. OPDEV.

Narrative: I WAS ASSIGNED THE RADAR APCH CTL POS. I ACCEPTED AN AUTOMATED HDOF ON ACR X, AN OVERFLT THROUGH OUR AREA, NBND TO MONTREAL (YUL) AT 7000' MSL. I RECEIVED A RADIO CALL FROM ACR X AND ISSUED HIM AN ALTIMETER SETTING. BECAUSE OUR COMPUTER IS NOT INTERFACED WITH MONTREAL TERMINAL (APCH CTL) I CONTACTED THEM TO FORWARD AN ESTIMATE FOR THE FLT OVER PLATTSBURGH VOR. I ESTIMATED ACR X WOULD CROSS PLB VOR AT XX:YZ. I ISSUED INSTRUCTIONS TO ANOTHER ACFT ASSIGNED 7000 AND REMEMBER CHKING ACR X POS RELATIVE TO THE SECOND ACFT. ACR X HAD, TO THE BEST OF MY RECOLLECTION, A FULL DATA BLOCK (ARTS II A). MY RELIEF SHOWED UP AND I GAVE HER A BRIEFING. I DID NOT MENTION ACR X DURING THE BRIEFING. THE FLT PROGRESS STRIP WAS NOT IN WITH THE ACTIVE TFC. IT WAS NEXT TO THE LANDLINE BUTTONS AND INACTIVE STRIPS, FROM MY PREVIOUS COORD CALL (PER THE RELIEVING CTLR). ACR X CONTACTED MY RELIEF AND QUESTIONED WHETHER HE WAS ON THE R FREQ AND BEACON CODE. (HE KNEW SOMETHING WAS WRONG). MY RELIEF KNEW NOTHING ABOUT THE FLT. ACR X CONTACTED MONTREAL ON HIS OWN. MONTREAL CTLRS IDENTED THE FLT NEAR MONTREAL. THE CTLR THAT RELIEVED ME ADVISED ME OF THE SITUATION...I DO NOT KNOW WHY THE DATA BLOCK DISAPPEARED ON ACR X... BUT THAT IS IRRELEVANT. I FORGOT HIM.

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.