 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Apa tower controller reported that they did not issue traffic advisory after a delayed heading change to avoid conflicts.
| Attributes | |
| ACN | 1669799 |
| Time | |
| Date | 201907 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | APA.Airport |
| State Reference | CO |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Small Transport |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Initial Climb |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Small Aircraft |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Cruise |
| Route In Use | VFR Route |
| Person 1 | |
| Function | Local |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 2 |
| Events | |
| Anomaly | ATC Issue All Types Airspace Violation All Types Conflict NMAC Deviation - Procedural Published Material / Policy |
Narrative:
Aircraft Z was a departure to the southwest. Aircraft X was an IFR departure initially cleared for takeoff with runway heading to protect for aircraft Z. The incorrect squawk code on the radar tag up was a distraction. I issued a turn to heading 300 about 3 miles south of the airport and switched aircraft X to departure control. I should have issued the traffic; aircraft Z and aircraft Y that were to the south/southwest at close to 8;000 ft. Aircraft Y was a fast VFR aircraft that was inbound but not talking to ATC and violated the class D. Aircraft X had a TCAS/RA for the two VFR aircraft. Aircraft X also did a very slow turn to the 300 heading which further caused him to be over the VFR traffic. [My recommendation is to] give the turn earlier; when I issued the squawk code. Also; I should have issued the traffic prior to switching frequencies. I should have ensured all conflicts were resolved.
Original NASA ASRS Text
Title: APA Tower Controller reported that they did not issue traffic advisory after a delayed heading change to avoid conflicts.
Narrative: Aircraft Z was a departure to the southwest. Aircraft X was an IFR departure initially cleared for takeoff with runway heading to protect for Aircraft Z. The incorrect squawk code on the radar tag up was a distraction. I issued a turn to heading 300 about 3 miles south of the airport and switched Aircraft X to Departure Control. I should have issued the traffic; Aircraft Z and Aircraft Y that were to the south/southwest at close to 8;000 ft. Aircraft Y was a fast VFR aircraft that was inbound but not talking to ATC and violated the Class D. Aircraft X had a TCAS/RA for the two VFR aircraft. Aircraft X also did a very slow turn to the 300 heading which further caused him to be over the VFR traffic. [My recommendation is to] give the turn earlier; when I issued the squawk code. Also; I should have issued the traffic prior to switching frequencies. I should have ensured all conflicts were resolved.
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.