 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Tpa controller describes a loss of separation due to data tag overlap and amount of traffic during the session.
| Attributes | |
| ACN | 1232772 |
| Time | |
| Date | 201501 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | TPA.TRACON |
| State Reference | FL |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Small Aircraft |
| Flight Phase | Cruise |
| Flight Plan | VFR |
| Aircraft 2 | |
| Make Model Name | Small Aircraft |
| Flight Phase | Cruise |
| Route In Use | Vectors |
| Flight Plan | VFR |
| Person 1 | |
| Function | Departure Approach |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 3.5 |
| Events | |
| Anomaly | ATC Issue All Types Conflict NMAC |
Narrative:
Working satellite and departure combined in the midst of busy season; middle of the day; good VFR weather. At the time of the event I had 19 airplanes; which is quite busy for this sector and typically would permit a handoff; which I did not have until I asked for one; after it was too late. Aircraft X departed vnc requesting northbound along the coast. I assigned aob 3000 VFR. Aircraft Y departed srq VFR. I issued climb to 5500; but then amended to 3000 for traffic at 4000 IFR; and additional traffic at 3500 VFR. I then assigned 3000 to aircraft X for traffic at 2000 opposite direction. In the area where the event occurred; there were 5 data blocks overlying each other. I became distracted with other traffic and missed the ca [conflict alert] until after it had happened; at which point aircraft Y informed me an aircraft just passed by what he assumed to be 500 feet laterally at the same altitude. I don't have a recommendation because during the busy season handoff is often staffed on this sector; but this time the supervisor just didn't realize how busy I'd become.
Original NASA ASRS Text
Title: TPA Controller describes a loss of separation due to data tag overlap and amount of traffic during the session.
Narrative: Working satellite and departure combined in the midst of busy season; middle of the day; good VFR weather. At the time of the event I had 19 airplanes; which is quite busy for this sector and typically would permit a handoff; which I did not have until I asked for one; after it was too late. Aircraft X departed VNC requesting northbound along the coast. I assigned AOB 3000 VFR. Aircraft Y departed SRQ VFR. I issued climb to 5500; but then amended to 3000 for traffic at 4000 IFR; and additional traffic at 3500 VFR. I then assigned 3000 to Aircraft X for traffic at 2000 opposite direction. In the area where the event occurred; there were 5 data blocks overlying each other. I became distracted with other traffic and missed the CA [Conflict Alert] until after it had happened; at which point Aircraft Y informed me an aircraft just passed by what he assumed to be 500 feet laterally at the same altitude. I don't have a recommendation because during the busy season handoff is often staffed on this sector; but this time the supervisor just didn't realize how busy I'd become.
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.