37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 394028 |
Time | |
Date | 199802 |
Day | Wed |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | atc facility : sli |
State Reference | CA |
Altitude | msl bound lower : 15000 msl bound upper : 15000 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Controlling Facilities | artcc : zla tracon : sna |
Operator | common carrier : air carrier |
Make Model Name | Brasilia EMB-120 All Series |
Operating Under FAR Part | Part 121 |
Flight Phase | cruise other |
Flight Plan | IFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : departure |
Qualification | controller : radar |
Experience | controller radar : 10 |
ASRS Report | 394028 |
Person 2 | |
Affiliation | government : faa |
Function | controller : approach |
Qualification | controller : radar |
Events | |
Anomaly | non adherence : published procedure other anomaly other other anomaly other |
Independent Detector | other controllera |
Resolutory Action | other |
Consequence | Other |
Supplementary | |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Operational Deviation |
Narrative:
I was working the newr position at the time of this incident. Due to a problem with the alphanumeric radar tracking system, the manr position was unable to complete an automated handoff to me on air carrier X, an E120. When manr coordinated with me, my display showed air carrier X on a 'C' position symbol. This normally indicates that ZLA has accepted an automated handoff from my sector. I subsequently assigned air carrier X 15000 ft, per SOP for aircraft entering ZLA sector 21 airspace. However, sector 21 had not actually accepted an automated handoff from me, and the aircraft entered sector 21's airspace unbeknownst to that controller. Although no other aircraft was involved, the potential for conflict with sector 21 traffic did exist. This event was caused by the ARTS system displaying a 'C' (center) position symbol, causing me to mistake the aircraft's handoff status. This equipment should be carefully evaluated before it contributes to a more serious incident.
Original NASA ASRS Text
Title: A TRACON CTLR RECEIVED AN INTRAFAC HDOF ON AN IFR E120 WITH A 'C' SYMBOL IN THE DATA BLOCK THAT WOULD EVENTUALLY BE ENTERING ZLA AIRSPACE. THE CTLR THOUGHT THAT A HDOF HAD ALREADY BEEN ACCEPTED BY THE CTR BECAUSE OF THE 'C' SYMBOL AND CHANGED THE ACFT TO THE CTR FREQ. THE ACFT ENTERED CTR AIRSPACE WITHOUT A HDOF.
Narrative: I WAS WORKING THE NEWR POS AT THE TIME OF THIS INCIDENT. DUE TO A PROB WITH THE ALPHANUMERIC RADAR TRACKING SYS, THE MANR POS WAS UNABLE TO COMPLETE AN AUTOMATED HDOF TO ME ON ACR X, AN E120. WHEN MANR COORDINATED WITH ME, MY DISPLAY SHOWED ACR X ON A 'C' POS SYMBOL. THIS NORMALLY INDICATES THAT ZLA HAS ACCEPTED AN AUTOMATED HDOF FROM MY SECTOR. I SUBSEQUENTLY ASSIGNED ACR X 15000 FT, PER SOP FOR ACFT ENTERING ZLA SECTOR 21 AIRSPACE. HOWEVER, SECTOR 21 HAD NOT ACTUALLY ACCEPTED AN AUTOMATED HDOF FROM ME, AND THE ACFT ENTERED SECTOR 21'S AIRSPACE UNBEKNOWNST TO THAT CTLR. ALTHOUGH NO OTHER ACFT WAS INVOLVED, THE POTENTIAL FOR CONFLICT WITH SECTOR 21 TFC DID EXIST. THIS EVENT WAS CAUSED BY THE ARTS SYS DISPLAYING A 'C' (CTR) POS SYMBOL, CAUSING ME TO MISTAKE THE ACFT'S HDOF STATUS. THIS EQUIP SHOULD BE CAREFULLY EVALUATED BEFORE IT CONTRIBUTES TO A MORE SERIOUS INCIDENT.
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.