 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Local controller described a conflict event where an air carrier on final requested a 360 for altitude loss and eventually conflicted with following traffic on downwind; the reporter acknowledging a loss of situational awareness.
| Attributes | |
| ACN | 1017377 |
| Time | |
| Date | 201206 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Aircraft 1 | |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Final Approach |
| Route In Use | Visual Approach |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Citation III VI VII (C650) |
| Flight Phase | Final Approach |
| Route In Use | Visual Approach |
| Flight Plan | IFR |
| Person 1 | |
| Function | Local |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Conflict Airborne Conflict |
Narrative:
Air carrier X was on final for runway xxr and was too high. He asked for 'south' turns which were approved and then asked to make a 360. The next traffic for runway xxr was still on downwind; so there was plenty of room for the 360. There was traffic; aircraft Y for runway xxl on a visual approach. I estimated that air carrier X would complete his turn to final for xxr well ahead of air carrier Y; I was wrong. I did not get aircraft Y to get air carrier X in sight or even issue the traffic to him. I got distracted by departure aircraft that were at runway xxl and not ready to go. The next time I looked up; air carrier X had blown through the xxr final and was just slightly ahead of aircraft Y and I had not pointed out the traffic. I had aircraft Y get him in sight and have him maintain visual for the wake turbulence separation (large and small). This was all my fault; things were going smoothly and I was lulled into a sense of security. I should have been more aware of what air carrier X was doing/his location and issued the traffic.
Original NASA ASRS Text
Title: Local Controller described a conflict event where an Air Carrier on final requested a 360 for altitude loss and eventually conflicted with following traffic on downwind; the reporter acknowledging a loss of situational awareness.
Narrative: Air Carrier X was on final for Runway XXR and was too high. He asked for 'S' turns which were approved and then asked to make a 360. The next traffic for Runway XXR was still on downwind; so there was plenty of room for the 360. There was traffic; aircraft Y for Runway XXL on a Visual Approach. I estimated that Air Carrier X would complete his turn to final for XXR well ahead of Air Carrier Y; I was wrong. I did not get aircraft Y to get Air Carrier X in sight or even issue the traffic to him. I got distracted by departure aircraft that were at Runway XXL and not ready to go. The next time I looked up; Air Carrier X had blown through the XXR final and was just slightly ahead of aircraft Y and I had not pointed out the traffic. I had aircraft Y get him in sight and have him maintain visual for the wake turbulence separation (Large and Small). This was all my fault; things were going smoothly and I was lulled into a sense of security. I should have been more aware of what Air Carrier X was doing/his location and issued the traffic.
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.