 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZAB controller described an airspace incursion event when failing to properly identify an IFR departure that was experiencing transponder problems.
| Attributes | |
| ACN | 978851 |
| Time | |
| Date | 201111 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZAB.ARTCC |
| State Reference | NM |
| Aircraft 1 | |
| Make Model Name | PA-28 Cherokee/Archer/Dakota/Pillan/Warrior |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Developmental |
| Person 2 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Airspace Violation All Types |
Narrative:
I sat down and received a briefing from the r-side on D45 at which time the controller mentioned that a PA28 was cleared off of flg and was not radar identified yet. As soon as the briefing was over the r-side asked the pilot his altitude and his beacon code; pilot said he was on the right beacon code we still did not have him in radar so we told the pilot we would get him in radar soon. After this; I was on and off line with other coordination for the next 20 or 30 minutes. About 45 minutes after the conversation with the pilot; an airplane asked if we wanted him to talk to phx approach. We could not hear his full call sign and when the r-side asked was the pilot was he was 30 miles north of pxr so we asked him to contact phx approach. Since he was in their airspace; I then found out that the airplane was the PA28 which we never radar identified or shipped to phx approach. I believe what would have helped in this situation was if we were able to get the pilot in radar coverage and if we were able to hear the aircraft.
Original NASA ASRS Text
Title: ZAB Controller described an airspace incursion event when failing to properly identify an IFR departure that was experiencing transponder problems.
Narrative: I sat down and received a briefing from the R-Side on D45 at which time the Controller mentioned that a PA28 was cleared off of FLG and was not RADAR identified yet. As soon as the briefing was over the R-Side asked the pilot his altitude and his beacon code; pilot said he was on the right beacon code we still did not have him in RADAR so we told the pilot we would get him in RADAR soon. After this; I was on and off line with other coordination for the next 20 or 30 minutes. About 45 minutes after the conversation with the pilot; an airplane asked if we wanted him to talk to PHX Approach. We could not hear his full call sign and when the R-Side asked was the pilot was he was 30 miles north of PXR so we asked him to contact PHX Approach. Since he was in their airspace; I then found out that the airplane was the PA28 which we never RADAR identified or shipped to PHX Approach. I believe what would have helped in this situation was if we were able to get the pilot in RADAR coverage and if we were able to hear the aircraft.
Data retrieved from NASA's ASRS site as of April 2012 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.