 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
TRACON controller reported a departure did not tag up on the radar display and was not detected until flying 40 to 50 miles.
| Attributes | |
| ACN | 1560395 |
| Time | |
| Date | 201807 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | PBI.TRACON |
| State Reference | FL |
| Aircraft 1 | |
| Make Model Name | Regional Jet CL65 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Climb |
| Flight Plan | IFR |
| Person 1 | |
| Function | Approach Departure |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 7 |
| Events | |
| Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy |
Narrative:
I had just taken the position. I was briefed on a departure which I climbed and switched to ZMA. I was only on position a few minutes when I was relieved from the position to move over and split off the position. This was done by a supervisor and a trainee as the trainee was certified on the departure sector but not the arrival one. After opening the arrival position and working for a few minutes I overheard the departure controller asking the position of an aircraft. This aircraft ended up being a regional jet that had departed and tagged up approximately 40-50 miles north of the airport. The departure controller asked if I talked to the aircraft before the sector split. I stated that I had not talked to the aircraft and had no idea they took off. I did not observe a data tag or an untagged secondary target at any time. I do not recall ever hearing the aircraft check-in and as a result never radar identified it. I did have other aircraft on my frequency that required my attention away from the departure side of the airport as well as weather beginning to build in the airspace. I never received a 'no tag' call from the tower on departure.[I recommend] a reminder to the workforce that the pbi standard operating procedure requires the tower to notify the TRACON within 3 miles of any departures that have not tagged. Do not switch aircraft to departure control from local control until an acquired tag is observed. Do not continue to have a departure SID level off at an altitude that is in direct conflict with an arrival descent procedure.in light of this; I do accept responsibility in that I should have observed the primary target in my airspace and questioned it. Also; the tower did scan the departure strip but I did not check the printer for it. While not required; this is a practice I normally do workload permitting and will make sure my focus always stays sharp in the future with regard to this.
Original NASA ASRS Text
Title: TRACON Controller reported a departure did not tag up on the radar display and was not detected until flying 40 to 50 miles.
Narrative: I had just taken the position. I was briefed on a departure which I climbed and switched to ZMA. I was only on position a few minutes when I was relieved from the position to move over and split off the position. This was done by a supervisor and a trainee as the trainee was certified on the departure sector but not the arrival one. After opening the Arrival position and working for a few minutes I overheard the Departure Controller asking the position of an aircraft. This aircraft ended up being a regional jet that had departed and tagged up approximately 40-50 miles north of the airport. The Departure Controller asked if I talked to the aircraft before the sector split. I stated that I had not talked to the aircraft and had no idea they took off. I did not observe a data tag or an untagged secondary target at any time. I do not recall ever hearing the aircraft check-in and as a result never radar identified it. I did have other aircraft on my frequency that required my attention away from the departure side of the airport as well as weather beginning to build in the airspace. I never received a 'no tag' call from the Tower on departure.[I recommend] a reminder to the workforce that the PBI Standard Operating Procedure requires the Tower to notify the TRACON within 3 miles of any departures that have not tagged. Do not switch aircraft to departure control from local control until an acquired tag is observed. Do not continue to have a departure SID level off at an altitude that is in direct conflict with an arrival descent procedure.In light of this; I do accept responsibility in that I should have observed the primary target in my airspace and questioned it. Also; the tower did scan the departure strip but I did not check the printer for it. While not required; this is a practice I normally do workload permitting and will make sure my focus always stays sharp in the future with regard to this.
Data retrieved from NASA's ASRS site 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.