Uncoord penetration of airspace. Operational deviation. Anonymous report.

Attributes
ACN	122523
Time
Date	198909
Day	Tue
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : rdu
State Reference	NC
Altitude	msl bound lower : 25000 msl bound upper : 27000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zdc
Operator	common carrier : air carrier
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	cruise other
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : handoff position
Qualification	controller : radar
ASRS Report	122523
Person 2
Affiliation	government : faa
Function	controller : handoff position
Qualification	controller : developmental
Events
Anomaly	non adherence : published procedure other anomaly other
Independent Detector	other controllera
Resolutory Action	none taken : anomaly accepted
Consequence	Other
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Intra Facility Coordination Failure Operational Deviation

Narrative:

As the afternoon traffic buildup approached, the supervisor put 2 more controllers on the sector. Since the developmental had never worked the 'left' position only, he was moved there and an fpl put on the 'right' position. Traffic complexity increased rapidly. A string of dulles inbnds was coming through with the slowest aircraft in the lead! The plan was to put the slow aircraft at FL250 and all the faster overtaking traffic at FL270. The altitudes were coordinated. At handoff time the next sector refused to take the slow aircraft because he was underneath another inbound. We turned him around and vectored the other inbnds for extra spacing. This created extra coordination and workload. One of the other aircraft apparently crossed the boundary without being handed off. I was concerned that we have had to turn other aircraft around, so I warned the 'right' controller and tried to watch the data blocks as closely as possible to insure handoffs were made. I do not recall anyone crossing the boundary without being handed off. The aircraft were separated at all times. The airplane that crossed the boundary was changed to the next frequency and the controller saw the target.

Original NASA ASRS Text

Title: UNCOORD PENETRATION OF AIRSPACE. OPERATIONAL DEVIATION. ANONYMOUS REPORT.

Narrative: AS THE AFTERNOON TFC BUILDUP APCHED, THE SUPVR PUT 2 MORE CTLRS ON THE SECTOR. SINCE THE DEVELOPMENTAL HAD NEVER WORKED THE 'L' POSITION ONLY, HE WAS MOVED THERE AND AN FPL PUT ON THE 'R' POSITION. TFC COMPLEXITY INCREASED RAPIDLY. A STRING OF DULLES INBNDS WAS COMING THROUGH WITH THE SLOWEST ACFT IN THE LEAD! THE PLAN WAS TO PUT THE SLOW ACFT AT FL250 AND ALL THE FASTER OVERTAKING TFC AT FL270. THE ALTS WERE COORDINATED. AT HANDOFF TIME THE NEXT SECTOR REFUSED TO TAKE THE SLOW ACFT BECAUSE HE WAS UNDERNEATH ANOTHER INBND. WE TURNED HIM AROUND AND VECTORED THE OTHER INBNDS FOR EXTRA SPACING. THIS CREATED EXTRA COORD AND WORKLOAD. ONE OF THE OTHER ACFT APPARENTLY CROSSED THE BOUNDARY WITHOUT BEING HANDED OFF. I WAS CONCERNED THAT WE HAVE HAD TO TURN OTHER ACFT AROUND, SO I WARNED THE 'R' CTLR AND TRIED TO WATCH THE DATA BLOCKS AS CLOSELY AS POSSIBLE TO INSURE HANDOFFS WERE MADE. I DO NOT RECALL ANYONE XING THE BOUNDARY WITHOUT BEING HANDED OFF. THE ACFT WERE SEPARATED AT ALL TIMES. THE AIRPLANE THAT CROSSED THE BOUNDARY WAS CHANGED TO THE NEXT FREQ AND THE CTLR SAW THE TARGET.

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.