ZOB controller experienced operational error at FL350 after inadvertently dropping a data block. Adjacent controller entered airspace losing separation with the untagged aircraft.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	636203
Time
Date	200410
Day	Thu
Local Time Of Day	1201 To 1800
Place
Locale Reference	navaid : cxr.vor
State Reference	OH
Altitude	msl single value : 35000
Environment
Weather Elements	Turbulence
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zob.artcc tower : cmi.tower
Operator	common carrier : air carrier
Make Model Name	DC-9 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	cruise : level
Flight Plan	IFR
Aircraft 2
Controlling Facilities	artcc : zob.artcc
Operator	general aviation : corporate
Make Model Name	Gates Learjet Corp Undifferentiated or Other Model
Operating Under FAR Part	Part 91
Flight Phase	climbout : vacating altitude climbout : intermediate altitude
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Experience	controller limited radar : 3 controller radar : 16
ASRS Report	636203
Person 2
Affiliation	government : faa
Function	controller : radar
Events
Anomaly	conflict : airborne less severe non adherence : published procedure non adherence : required legal separation
Independent Detector	atc equipment : conflict alert other controllera
Resolutory Action	controller : issued alert
Consequence	faa : investigated
Miss Distance	horizontal : 15600 vertical : 1400
Supplementary
Problem Areas	ATC Human Performance
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error

Narrative:

Problem arose when I slew-balled a slant zero on a data block and then tried to slew over another, but missed and dropped one inadvertently. Then the controller working airspace below me climbed an aircraft into my airspace, not seeing the limited data block. Conflict alert activated and then loss of separation. Procedures already written would have averted this operational error if they were followed.

Original NASA ASRS Text

Title: ZOB CTLR EXPERIENCED OPERROR AT FL350 AFTER INADVERTENTLY DROPPING A DATA BLOCK. ADJACENT CTLR ENTERED AIRSPACE LOSING SEPARATION WITH THE UNTAGGED ACFT.

Narrative: PROB AROSE WHEN I SLEW-BALLED A SLANT ZERO ON A DATA BLOCK AND THEN TRIED TO SLEW OVER ANOTHER, BUT MISSED AND DROPPED ONE INADVERTENTLY. THEN THE CTLR WORKING AIRSPACE BELOW ME CLBED AN ACFT INTO MY AIRSPACE, NOT SEEING THE LIMITED DATA BLOCK. CONFLICT ALERT ACTIVATED AND THEN LOSS OF SEPARATION. PROCS ALREADY WRITTEN WOULD HAVE AVERTED THIS OPERROR IF THEY WERE FOLLOWED.

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.