 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A controller experienced a tag drop on an IFR BE55 at 6000 ft. The controller asked the center if they could see the BE55 on their radar and the center advised they could. The reporter claims that data tags dropping are a continuing problem.
| Attributes | |
| ACN | 415201 |
| Time | |
| Date | 199809 |
| Day | Tue |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | atc facility : abi |
| State Reference | TX |
| Altitude | msl bound lower : 6000 msl bound upper : 6000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : abi |
| Operator | general aviation : personal |
| Make Model Name | Baron 55/Cochise |
| Operating Under FAR Part | Part 91 |
| Flight Phase | cruise other |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : approach |
| Qualification | controller : radar pilot : private pilot : instrument |
| Experience | controller non radar : 8 controller radar : 6 flight time total : 225 |
| ASRS Report | 415201 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Qualification | controller : radar |
| Events | |
| Anomaly | other anomaly other |
| Independent Detector | other controllera |
| Resolutory Action | none taken : unable |
| Consequence | Other |
| Supplementary | |
| Primary Problem | Navigational Facility |
| Air Traffic Incident | other |
| Situations | |
| Navigational Aid | Unspecified |
Narrative:
While assigned to the radar position I had an aircraft data tag drop. This aircraft was operating direct maf from south of abi. The pilot requested a rerte to direct eip. I requested the data person to amend the flight plan. I continued with my other duties, and upon completing a scan of my strips the aircraft was no longer on my scope. I verified the aircraft was on frequency and I asked ZFW if they had radar (they did not). I returned to the aircraft and advised radar contact lost. I inspected my drop/suspend list and the aircraft's identify was not present. ZFW then advised they had radar on the aircraft. Based on the aircraft's last known position, type aircraft, and speed, it was determined that the aircraft had not left our airspace. Data tags dropping is a continuing problem.
Original NASA ASRS Text
Title: A CTLR EXPERIENCED A TAG DROP ON AN IFR BE55 AT 6000 FT. THE CTLR ASKED THE CTR IF THEY COULD SEE THE BE55 ON THEIR RADAR AND THE CTR ADVISED THEY COULD. THE RPTR CLAIMS THAT DATA TAGS DROPPING ARE A CONTINUING PROB.
Narrative: WHILE ASSIGNED TO THE RADAR POS I HAD AN ACFT DATA TAG DROP. THIS ACFT WAS OPERATING DIRECT MAF FROM S OF ABI. THE PLT REQUESTED A RERTE TO DIRECT EIP. I REQUESTED THE DATA PERSON TO AMEND THE FLT PLAN. I CONTINUED WITH MY OTHER DUTIES, AND UPON COMPLETING A SCAN OF MY STRIPS THE ACFT WAS NO LONGER ON MY SCOPE. I VERIFIED THE ACFT WAS ON FREQ AND I ASKED ZFW IF THEY HAD RADAR (THEY DID NOT). I RETURNED TO THE ACFT AND ADVISED RADAR CONTACT LOST. I INSPECTED MY DROP/SUSPEND LIST AND THE ACFT'S IDENT WAS NOT PRESENT. ZFW THEN ADVISED THEY HAD RADAR ON THE ACFT. BASED ON THE ACFT'S LAST KNOWN POS, TYPE ACFT, AND SPD, IT WAS DETERMINED THAT THE ACFT HAD NOT LEFT OUR AIRSPACE. DATA TAGS DROPPING IS A CONTINUING PROB.
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.