ZSE controller experienced operational error at approximately 8000 alleging absent data block and confused coordination as causal factors.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	735597
Time
Date	200704
Local Time Of Day	0601 To 1200
Place
Locale Reference	navaid : ubg.vor
State Reference	OR
Altitude	msl bound lower : 7000 msl bound upper : 8000
Environment
Flight Conditions	Mixed
Weather Elements	Rain
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zse.artcc
Operator	general aviation : personal
Make Model Name	Citation II S2/Bravo
Operating Under FAR Part	Part 91
Flight Phase	cruise : level
Flight Plan	IFR
Aircraft 2
Controlling Facilities	artcc : zse.artcc
Operator	general aviation : personal
Make Model Name	PA-34-200 Seneca I
Operating Under FAR Part	Part 91
Flight Phase	cruise : enroute altitude change
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Experience	controller radar : 4
ASRS Report	735597
Events
Anomaly	conflict : airborne critical non adherence : required legal separation
Independent Detector	atc equipment : conflict alert other controllera
Resolutory Action	controller : issued alert controller : issued new clearance
Consequence	faa : investigated
Miss Distance	horizontal : 9840 vertical : 200
Supplementary
Problem Areas	ATC Human Performance
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error

Narrative:

On apr/xa/07 at XA01 I had an operational error. Below I will describe the error. At XG55Z; I called portland approach control (pdx) to appreq an aircraft (C550) at 8000 ft. At the same time during this coordination; pdx told me that another aircraft was going to be at 6000 ft. I was confused because I didn't have a data block on this aircraft yet; so I called back to confirm the call sign. During this session my d-side had taken several calls from pdx. This led to heightened complexity to the sector at that time. At approximately XG56 my d-side released an aircraft off of salem; or; to an altitude that put him in conflict with several others sbound. My d-side did; however; correct himself/herself in a laughing manner to the correct altitude. 2 aircraft including the PA34 were requesting different altitudes when the aircraft off of salem was called. At this time; I had already shipped the C550 to pdx. At XG58 I climbed the PA34 to 9000 ft and he was in conflict with the C550 at 8000 ft. I descended the PA34 to 7000 ft. I did not avoid an operational error.

Original NASA ASRS Text

Title: ZSE CTLR EXPERIENCED OPERROR AT APPROX 8000 ALLEGING ABSENT DATA BLOCK AND CONFUSED COORD AS CAUSAL FACTORS.

Narrative: ON APR/XA/07 AT XA01 I HAD AN OPERROR. BELOW I WILL DESCRIBE THE ERROR. AT XG55Z; I CALLED PORTLAND APCH CTL (PDX) TO APPREQ AN ACFT (C550) AT 8000 FT. AT THE SAME TIME DURING THIS COORD; PDX TOLD ME THAT ANOTHER ACFT WAS GOING TO BE AT 6000 FT. I WAS CONFUSED BECAUSE I DIDN'T HAVE A DATA BLOCK ON THIS ACFT YET; SO I CALLED BACK TO CONFIRM THE CALL SIGN. DURING THIS SESSION MY D-SIDE HAD TAKEN SEVERAL CALLS FROM PDX. THIS LED TO HEIGHTENED COMPLEXITY TO THE SECTOR AT THAT TIME. AT APPROX XG56 MY D-SIDE RELEASED AN ACFT OFF OF SALEM; OR; TO AN ALT THAT PUT HIM IN CONFLICT WITH SEVERAL OTHERS SBOUND. MY D-SIDE DID; HOWEVER; CORRECT HIMSELF/HERSELF IN A LAUGHING MANNER TO THE CORRECT ALT. 2 ACFT INCLUDING THE PA34 WERE REQUESTING DIFFERENT ALTS WHEN THE ACFT OFF OF SALEM WAS CALLED. AT THIS TIME; I HAD ALREADY SHIPPED THE C550 TO PDX. AT XG58 I CLBED THE PA34 TO 9000 FT AND HE WAS IN CONFLICT WITH THE C550 AT 8000 FT. I DSNDED THE PA34 TO 7000 FT. I DID NOT AVOID AN OPERROR.

Data retrieved from NASA's ASRS site as of January 2009 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.