37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1084911 |
Time | |
Date | 201304 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | TUS.Airport |
State Reference | AZ |
Aircraft 1 | |
Make Model Name | PA-46 Malibu Meridian |
Operating Under FAR Part | Part 91 |
Flight Phase | Final Approach |
Flight Plan | IFR |
Person 1 | |
Function | Local |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types |
Narrative:
A cvlt was doing VFR pattern work in the rectangular pattern for runway 29R. An IFR PA46 reported on a GPS approach to runway 21. The pilot did not state how far he was from the airport. I expanded the scope to 22 miles and still did not see the PA46. I then asked the pilot his location and he replied that he was 2 1/2 mile final. There was no tag; data-block; primary target; etc on the scope and I could not see the PA46 out the window. The PA46 stated that he could maintain 040. I told him to maintain 040 and instructed the cvlt to make left traffic with and early crosswind and stopped him at 035. The data-block and other associated information for the PA46 reappeared when the aircraft was midfield. I ensured that the PA46 was VFR at that point and instructed him to turn right on course to phoenix and he departed my airspace without incident. I don't know what the fix is for this. After reviewing the radar tapes I found that the PA46 flew approximately 4.5 miles with no data block or primary tag.
Original NASA ASRS Text
Title: TUS Controller described a target loss event when both the primary and secondary indications were absent near the airport.
Narrative: A CVLT was doing VFR pattern work in the rectangular pattern for Runway 29R. An IFR PA46 reported on a GPS approach to Runway 21. The pilot did not state how far he was from the airport. I expanded the scope to 22 miles and still did not see the PA46. I then asked the pilot his location and he replied that he was 2 1/2 mile final. There was no tag; data-block; primary target; etc on the scope and I could not see the PA46 out the window. The PA46 stated that he could maintain 040. I told him to maintain 040 and instructed the CVLT to make left traffic with and early crosswind and stopped him at 035. The data-block and other associated information for the PA46 reappeared when the aircraft was midfield. I ensured that the PA46 was VFR at that point and instructed him to turn right on course to Phoenix and he departed my airspace without incident. I don't know what the fix is for this. After reviewing the RADAR tapes I found that the PA46 flew approximately 4.5 miles with no data block or primary tag.
Data retrieved from NASA's ASRS site as of July 2013 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.