37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1302249 |
Time | |
Date | 201510 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | BJC.Airport |
State Reference | CO |
Environment | |
Flight Conditions | VMC |
Light | Dusk |
Aircraft 1 | |
Make Model Name | Light Transport High Wing 2 Turboprop Eng |
Flight Phase | Final Approach |
Flight Plan | VFR |
Aircraft 2 | |
Make Model Name | Small Aircraft High Wing 1 Eng Fixed Gear |
Operating Under FAR Part | Part 91 |
Flight Phase | Final Approach |
Route In Use | Visual Approach |
Flight Plan | VFR |
Person 1 | |
Function | Local |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 6.1 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
I was working local control and recall working a trickier session than normal (perhaps it had been awhile since I had worked a busier session on this configuration). I had issued aircraft Y a clearance to land on 12L and he was entering the left base. Aircraft X was cleared touch and go on 12R and was on a right base entry. In my scan; I suddenly noticed aircraft X making a steep turn out the window; as if they were taking evasive action. I realized I had not exchanged traffic between the two aircraft; and simultaneously aircraft Y was asking about the intentions of aircraft X off his right; noting it appeared he was headed for him. I confirmed that the other aircraft was inbound on the parallel runway; and aircraft X advised they overshot the final and were making a turn back to it. Each aircraft continued without expressing further concern.I can recall there was some complexity with local pattern traffic leading up to the event; where I was having difficulty tracking a helicopter in the local pattern that was flying patterns that were higher than normal. Aircraft Y also had an issued with their transponder and this created additional workload while they were inbound. I found it challenging at times to scan some of my traffic; as I did realize upon assuming the position that some of the shades in the cab were not in a 'normal' configuration and thus some areas were darker/lighter than normal. It was obvious when traffic was lighter later and I could make adjustments - but during a busier; complex period - I could not initially understand the lighting conditions affected by the shades were making it harder to track traffic in my pattern. The temperature also seemed warmer than usual and was distracting until it was adjusted. These environmental factors are not an excuse for overlooking traffic in this scenario (and it is my responsibility to make adjustments to either correct those factors or work through them) - but they may have played a role by making it challenging to work through a higher complexity traffic situation by putting me behind issuing a traffic advisory that I normally would have covered. Exchanging traffic sooner can help the pilots perform their duties in a VFR pattern and avoid these situations. While I usually try to be proactive and issue traffic as timely as I can; I overlooked it in this instance. I believe traffic complexity and frequency congestion - in conjunction with some environmental items mentioned above - were factors that made it more challenging to keep up and contributed to this oversight. I am reminded it is important to make environmental adjustments during periods of slower activity or prior to assuming a control position (equipment settings; temperature; shades; etc.) and have other tower team members assist with these when appropriate; in order to help prevent environmental factors adding to complexity when traffic builds.
Original NASA ASRS Text
Title: A small aircraft on a left base to final for the left parallel runway with a light twin engine on a right base to final for the parallel runway. The light twin flew across their final towards the left runway arrival but corrected. ATC had not issued a traffic advisory to either aircraft. The small aircraft saw the light twin and asked the Tower what that aircrafts intentions were. ATC should have issued traffic to both aircraft.
Narrative: I was working Local Control and recall working a trickier session than normal (perhaps it had been awhile since I had worked a busier session on this configuration). I had issued Aircraft Y a clearance to land on 12L and he was entering the left base. Aircraft X was cleared touch and go on 12R and was on a right base entry. In my scan; I suddenly noticed Aircraft X making a steep turn out the window; as if they were taking evasive action. I realized I had not exchanged traffic between the two aircraft; and simultaneously Aircraft Y was asking about the intentions of Aircraft X off his right; noting it appeared he was headed for him. I confirmed that the other aircraft was inbound on the parallel runway; and Aircraft X advised they overshot the final and were making a turn back to it. Each aircraft continued without expressing further concern.I can recall there was some complexity with local pattern traffic leading up to the event; where I was having difficulty tracking a helicopter in the local pattern that was flying patterns that were higher than normal. Aircraft Y also had an issued with their transponder and this created additional workload while they were inbound. I found it challenging at times to scan some of my traffic; as I did realize upon assuming the position that some of the shades in the cab were not in a 'normal' configuration and thus some areas were darker/lighter than normal. It was obvious when traffic was lighter later and I could make adjustments - but during a busier; complex period - I could not initially understand the lighting conditions affected by the shades were making it harder to track traffic in my pattern. The temperature also seemed warmer than usual and was distracting until it was adjusted. These environmental factors are not an excuse for overlooking traffic in this scenario (and it is my responsibility to make adjustments to either correct those factors or work through them) - but they may have played a role by making it challenging to work through a higher complexity traffic situation by putting me behind issuing a traffic advisory that I normally would have covered. Exchanging traffic sooner can help the pilots perform their duties in a VFR pattern and avoid these situations. While I usually try to be proactive and issue traffic as timely as I can; I overlooked it in this instance. I believe traffic complexity and frequency congestion - in conjunction with some environmental items mentioned above - were factors that made it more challenging to keep up and contributed to this oversight. I am reminded it is important to make environmental adjustments during periods of slower activity or prior to assuming a control position (equipment settings; temperature; shades; etc.) and have other tower team members assist with these when appropriate; in order to help prevent environmental factors adding to complexity when traffic builds.
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.