ZMA associate controller conducting OJT experienced operational deviation citing new uret equipment ...

Attributes
ACN	717387
Time
Date	200611
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : zma.artcc
State Reference	FL
Altitude	msl single value : 12000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zma.artcc
Operator	common carrier : air taxi
Make Model Name	Super King Air 200 HDC
Operating Under FAR Part	Part 135
Flight Phase	cruise : level
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : flight data instruction : instructor
Qualification	controller : non radar controller : radar
Experience	controller time certified in position1 : 20 controller time certified in position2 : 6
ASRS Report	717387
Person 2
Affiliation	company : air taxi
Function	flight crew : captain oversight : pic
Events
Anomaly	airspace violation : entry non adherence : required legal separation
Independent Detector	other controllera
Resolutory Action	none taken : anomaly accepted
Consequence	faa : investigated
Supplementary
Problem Areas	ATC Human Performance
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Deviation

Narrative:

I was conducting OJT on the associate position; I inadvertently removed an active flight plan that I thought was a duplicate. I believe that the use of the uret prevented the detection of this incident by removing the previous redundant controls. By this I mean; prior to the use of the uret system; when a controller received a message generated by the host computer system; the controller needed to acknowledge the message and take action. During the use of uret; the system does not require the controller to acknowledge any message or take any action prompted by said message. We have become dependent on the automation. Before uret if a controller received a remove flight plan message they would verify that the aircraft indeed was not going to enter their airspace. During uret operation; most messages go unanswered as the machine updates most of the information. Removal of flight plan information messages go unanswered and in most cases are disregarded.

Original NASA ASRS Text

Title: ZMA ASSOCIATE CTLR CONDUCTING OJT EXPERIENCED OPDEV CITING NEW URET EQUIP AS CAUSAL FACTOR.

Narrative: I WAS CONDUCTING OJT ON THE ASSOCIATE POS; I INADVERTENTLY REMOVED AN ACTIVE FLT PLAN THAT I THOUGHT WAS A DUPLICATE. I BELIEVE THAT THE USE OF THE URET PREVENTED THE DETECTION OF THIS INCIDENT BY REMOVING THE PREVIOUS REDUNDANT CTLS. BY THIS I MEAN; PRIOR TO THE USE OF THE URET SYS; WHEN A CTLR RECEIVED A MESSAGE GENERATED BY THE HOST COMPUTER SYS; THE CTLR NEEDED TO ACKNOWLEDGE THE MESSAGE AND TAKE ACTION. DURING THE USE OF URET; THE SYS DOES NOT REQUIRE THE CTLR TO ACKNOWLEDGE ANY MESSAGE OR TAKE ANY ACTION PROMPTED BY SAID MESSAGE. WE HAVE BECOME DEPENDENT ON THE AUTOMATION. BEFORE URET IF A CTLR RECEIVED A REMOVE FLT PLAN MESSAGE THEY WOULD VERIFY THAT THE ACFT INDEED WAS NOT GOING TO ENTER THEIR AIRSPACE. DURING URET OP; MOST MESSAGES GO UNANSWERED AS THE MACHINE UPDATES MOST OF THE INFO. REMOVAL OF FLT PLAN INFO MESSAGES GO UNANSWERED AND IN MOST CASES ARE DISREGARDED.

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.

ZMA associate controller conducting OJT experienced operational deviation citing new uret equipment as causal factor.