Uncoord penetration of airspace by air carrier X. Operational deviation.

Attributes
ACN	122123
Time
Date	198909
Day	Sat
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : rdu
State Reference	NC
Altitude	msl bound lower : 27000 msl bound upper : 27000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport, Low Wing, 2 Turbojet Eng
Flight Phase	cruise other
Route In Use	enroute : direct
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Experience	controller non radar : 2 controller radar : 8
ASRS Report	122123
Person 2
Affiliation	government : faa
Function	controller : handoff position
Qualification	controller : radar
Experience	controller military : 4 controller non radar : 6 controller radar : 22
ASRS Report	122784
Events
Anomaly	non adherence : published procedure other anomaly other
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Consequence	Other
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Deviation Intra Facility Coordination Failure

Narrative:

I was working rdu hi (R-36) radar position with training being conducted on the left position. Traffic during this period was heavy and complex. Medium large transport at FL270 was descended to FL250 and not being a like type, would allow the string of iad arrs behind to pass overhead. Not until medium large transport was approaching 5 mi of the boundary, was I told that bkt int was refusing to take the handoff. I instructed medium large transport to make a right 360 (there was not a convenient place at this time to put medium large transport). Also, there were 2 additional iad arrs at FL330 crossing with an air carrier going to jfk at FL330, an mlt climbing to FL310 wbound (eliminating the option to descend the crossing traffic to FL310), and 2 aircraft at FL370 crossing north of sdz VORTAC. With all this going on and no place to easily place medium large transport (which I did with a great deal of hard vectoring and speed control), apparently air carrier X was allowed to cross the bkt int boundary. By the time my scanning brought me back to my northern boundary, I saw that several aircraft needed to be switched to bkt int as well as hpw hi. I don't recall, but air carrier X must have been in that group.

Original NASA ASRS Text

Title: UNCOORD PENETRATION OF AIRSPACE BY ACR X. OPERATIONAL DEVIATION.

Narrative: I WAS WORKING RDU HI (R-36) RADAR POSITION WITH TRAINING BEING CONDUCTED ON THE L POSITION. TFC DURING THIS PERIOD WAS HEAVY AND COMPLEX. MLG AT FL270 WAS DESCENDED TO FL250 AND NOT BEING A LIKE TYPE, WOULD ALLOW THE STRING OF IAD ARRS BEHIND TO PASS OVERHEAD. NOT UNTIL MLG WAS APCHING 5 MI OF THE BOUNDARY, WAS I TOLD THAT BKT INT WAS REFUSING TO TAKE THE HANDOFF. I INSTRUCTED MLG TO MAKE A RIGHT 360 (THERE WAS NOT A CONVENIENT PLACE AT THIS TIME TO PUT MLG). ALSO, THERE WERE 2 ADDITIONAL IAD ARRS AT FL330 XING WITH AN ACR GOING TO JFK AT FL330, AN MLT CLIMBING TO FL310 WBOUND (ELIMINATING THE OPTION TO DSND THE XING TFC TO FL310), AND 2 ACFT AT FL370 XING N OF SDZ VORTAC. WITH ALL THIS GOING ON AND NO PLACE TO EASILY PLACE MLG (WHICH I DID WITH A GREAT DEAL OF HARD VECTORING AND SPEED CONTROL), APPARENTLY ACR X WAS ALLOWED TO CROSS THE BKT INT BOUNDARY. BY THE TIME MY SCANNING BROUGHT ME BACK TO MY NORTHERN BOUNDARY, I SAW THAT SEVERAL ACFT NEEDED TO BE SWITCHED TO BKT INT AS WELL AS HPW HI. I DON'T RECALL, BUT ACR X MUST HAVE BEEN IN THAT GROUP.

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.