Sct controller assumes 'nats (non-ARTS track status)' on aircraft data tag is a VFR aircraft, when actually IFR, and is involved in operational error with another opposite direction IFR aircraft.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	523602
Time
Date	200108
Day	Wed
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : sct.tracon
State Reference	CA
Altitude	msl single value : 6000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : sct.tracon artcc : zob.artcc
Operator	general aviation : personal
Make Model Name	Bonanza 35
Operating Under FAR Part	Part 91
Flight Phase	descent : intermediate altitude
Route In Use	enroute airway : v23.airway
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tracon : sct.tracon
Operator	general aviation : personal
Make Model Name	Cessna 120
Operating Under FAR Part	Part 91
Flight Phase	cruise : level
Route In Use	enroute airway : v23.airway
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar controller : developmental
Experience	controller radar : 22 flight time total : 300
ASRS Report	523602
Person 2
Affiliation	government : faa
Function	controller : approach
Events
Anomaly	conflict : airborne critical non adherence : published procedure non adherence : required legal separation
Independent Detector	atc equipment : conflict alert other controllera other flight crewa
Resolutory Action	none taken : detected after the fact
Consequence	faa : investigated
Miss Distance	horizontal : 6000 vertical : 100
Supplementary
Problem Areas	ATC Human Performance
Primary Problem	ATC Human Performance
Air Traffic Incident	Intra Facility Coordination Failure Operational Error

Narrative:

BE35 descending from 9000-5000 ft sebound V23. C210 level at 6000 ft, nwbound V23 in handoff status from another sector. This aircraft was in 'nats' status on my scope. ARTS IIIE does not display whether aircraft is VFR or IFR under these conditions. This is a typical scenario for this sector however 99.99% of these aircraft that go 'nats' are VFR at 4500 ft or below. The cessna was about to enter my airspace without a handoff. I called the other sector and advised them the cessna was in 'nats' status and that he was approved to enter (assuming that this aircraft was VFR). The bonanza was in handoff to this controller. The other controller answered with 'roger.' after the aircraft passed each other the computer 'saw' the cessna and gave me a firm data block. The other controller accepted the handoff on the bonanza. The bonanza pilot told me that he had seen the cessna go by.

Original NASA ASRS Text

Title: SCT CTLR ASSUMES 'NATS (NON-ARTS TRACK STATUS)' ON ACFT DATA TAG IS A VFR ACFT, WHEN ACTUALLY IFR, AND IS INVOLVED IN OPERROR WITH ANOTHER OPPOSITE DIRECTION IFR ACFT.

Narrative: BE35 DSNDING FROM 9000-5000 FT SEBOUND V23. C210 LEVEL AT 6000 FT, NWBOUND V23 IN HDOF STATUS FROM ANOTHER SECTOR. THIS ACFT WAS IN 'NATS' STATUS ON MY SCOPE. ARTS IIIE DOES NOT DISPLAY WHETHER ACFT IS VFR OR IFR UNDER THESE CONDITIONS. THIS IS A TYPICAL SCENARIO FOR THIS SECTOR HOWEVER 99.99% OF THESE ACFT THAT GO 'NATS' ARE VFR AT 4500 FT OR BELOW. THE CESSNA WAS ABOUT TO ENTER MY AIRSPACE WITHOUT A HDOF. I CALLED THE OTHER SECTOR AND ADVISED THEM THE CESSNA WAS IN 'NATS' STATUS AND THAT HE WAS APPROVED TO ENTER (ASSUMING THAT THIS ACFT WAS VFR). THE BONANZA WAS IN HDOF TO THIS CTLR. THE OTHER CTLR ANSWERED WITH 'ROGER.' AFTER THE ACFT PASSED EACH OTHER THE COMPUTER 'SAW' THE CESSNA AND GAVE ME A FIRM DATA BLOCK. THE OTHER CTLR ACCEPTED THE HDOF ON THE BONANZA. THE BONANZA PLT TOLD ME THAT HE HAD SEEN THE CESSNA GO BY.

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.