Narrative:

Air carrier X was proceeding direct the svm VOR from near london, ontario, on this track, the aircraft would infringe on 3 sectors (dresden, flint, and windsor). Dresden sector received the handoff and subsequently handed off the aircraft to fnt sector. I relieved the dresden controller when this aircraft was about 7 mi from the flint boundary and 19 mi from the windsor sector boundary. It was believed that the aircraft would not infringe on windsor sector on its present heading due to strong southerly winds. I got busy taking handoffs and other control information from toronto center and did not see that the data block on air carrier X had timed out and dropped from my (dresden sector) display. The aircraft had apparently corrected course more to the southwest which caused an infringement of the windsor sector airspace. The windsor controller had received a handoff on cpr Y, a ptk departure requesting 17000 ft. Coordination was effected for control to climb and when this aircraft reached 16000 ft, was in conflict with air carrier X also at 16000 ft. A multitude of factors contributed to this error. Failure to pointout air carrier X to the windsor sector. This was not done because of failing to observe data block drop (drop time too short). Also, too busy with coordination which would have been accomplished automatically if toronto center was interfaced with cleveland center. Flint sector used incorrect/incomplete phraseology when approving climb on cpr Y. No reference to traffic or altitude was made. When cpr Y was issued climb to 16000 ft (stopped at 16000 ft for 17000 ft traffic), the 'T' altitude was not utilized in the data block which could have indicated to the flint controller that the windsor controller did not see the air carrier X at 16000 ft.

Related reports:

Google
 

Original NASA ASRS Text

Title: ACR X UNAUTHORIZED UNCOORDINATED PENETRATION OF ADJACENT SECTOR AIRSPACE HAD LTSS WITH CPR Y CLB TO OCCUPIED ALT. SYS ERROR.

Narrative: ACR X WAS PROCEEDING DIRECT THE SVM VOR FROM NEAR LONDON, ONTARIO, ON THIS TRACK, THE ACFT WOULD INFRINGE ON 3 SECTORS (DRESDEN, FLINT, AND WINDSOR). DRESDEN SECTOR RECEIVED THE HDOF AND SUBSEQUENTLY HANDED OFF THE ACFT TO FNT SECTOR. I RELIEVED THE DRESDEN CTLR WHEN THIS ACFT WAS ABOUT 7 MI FROM THE FLINT BOUNDARY AND 19 MI FROM THE WINDSOR SECTOR BOUNDARY. IT WAS BELIEVED THAT THE ACFT WOULD NOT INFRINGE ON WINDSOR SECTOR ON ITS PRESENT HDG DUE TO STRONG SOUTHERLY WINDS. I GOT BUSY TAKING HDOFS AND OTHER CTL INFO FROM TORONTO CTR AND DID NOT SEE THAT THE DATA BLOCK ON ACR X HAD TIMED OUT AND DROPPED FROM MY (DRESDEN SECTOR) DISPLAY. THE ACFT HAD APPARENTLY CORRECTED COURSE MORE TO THE SW WHICH CAUSED AN INFRINGEMENT OF THE WINDSOR SECTOR AIRSPACE. THE WINDSOR CTLR HAD RECEIVED A HDOF ON CPR Y, A PTK DEP REQUESTING 17000 FT. COORD WAS EFFECTED FOR CTL TO CLB AND WHEN THIS ACFT REACHED 16000 FT, WAS IN CONFLICT WITH ACR X ALSO AT 16000 FT. A MULTITUDE OF FACTORS CONTRIBUTED TO THIS ERROR. FAILURE TO POINTOUT ACR X TO THE WINDSOR SECTOR. THIS WAS NOT DONE BECAUSE OF FAILING TO OBSERVE DATA BLOCK DROP (DROP TIME TOO SHORT). ALSO, TOO BUSY WITH COORD WHICH WOULD HAVE BEEN ACCOMPLISHED AUTOMATICALLY IF TORONTO CTR WAS INTERFACED WITH CLEVELAND CTR. FLINT SECTOR USED INCORRECT/INCOMPLETE PHRASEOLOGY WHEN APPROVING CLB ON CPR Y. NO REF TO TFC OR ALT WAS MADE. WHEN CPR Y WAS ISSUED CLB TO 16000 FT (STOPPED AT 16000 FT FOR 17000 FT TFC), THE 'T' ALT WAS NOT UTILIZED IN THE DATA BLOCK WHICH COULD HAVE INDICATED TO THE FLINT CTLR THAT THE WINDSOR CTLR DID NOT SEE THE ACR X AT 16000 FT.

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.