37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1759113 |
Time | |
Date | 202009 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZZZ.TRACON |
State Reference | US |
Aircraft 1 | |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Route In Use | Visual Approach |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | Approach |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 2.5 |
Person 2 | |
Function | Approach |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy |
Narrative:
I had just taken the X and Y sectors from Z position during configuration #X (a configuration that we rarely use and I haven't worked in at least 8 months) and did a recorded briefing. During briefing I took point outs from Z sector on 2 aircraft. One was aircraft X who was on right downwind for runway xr. Aircraft X was yellow as a point out on my scope. I was talking to aircraft Y who was in trail of aircraft X and descended him to the MVA of XXX. I then was setting up preferences and frequencies for the sector. The Z controller was late turning base and I didn't notice. I turned base at my normal base turn not noticing that aircraft X had turned a late base. When I noticed the mistake both aircraft were at same altitude and I immediately issued traffic alert to aircraft Y and he reported responding to an RA and climbed. During that time after the loss of separation the Z controller got visual separation from aircraft X. I turned aircraft Y to the northeast and set him back up for a right base to xr. Both landed without further incident.I shouldn't have taken a point out on aircraft who was still on downwind. Also I felt a little rusty on the configuration as we rarely use it. Also with the covid staffing I have been working mostly mid shifts and hadn't adjusted the sleep patterns well enough and hadn't worked the busier traffic for a while.
Original NASA ASRS Text
Title: TRACON Controllers reported a loss of separation while working combined positions due to staffing and handoff/communication issues. The First Officer of one of the aircrafts involved also reported the conflict and made reference to the miss-communication between controllers.
Narrative: I had just taken the X and Y sectors from Z position during Configuration #X (A configuration that we rarely use and I haven't worked in at least 8 months) and did a recorded briefing. During briefing I took point outs from Z sector on 2 aircraft. One was Aircraft X who was on right downwind for Runway XR. Aircraft X was yellow as a point out on my scope. I was talking to Aircraft Y who was in trail of Aircraft X and descended him to the MVA of XXX. I then was setting up preferences and frequencies for the sector. The Z Controller was late turning base and I didn't notice. I turned base at my normal base turn not noticing that Aircraft X had turned a late base. When I noticed the mistake both aircraft were at same altitude and I immediately issued traffic alert to Aircraft Y and he reported responding to an RA and climbed. During that time after the loss of separation the Z Controller got visual separation from Aircraft X. I turned Aircraft Y to the northeast and set him back up for a right base to XR. Both landed without further incident.I shouldn't have taken a point out on aircraft who was still on downwind. Also I felt a little rusty on the configuration as we rarely use it. Also with the COVID staffing I have been working mostly mid shifts and hadn't adjusted the sleep patterns well enough and hadn't worked the busier traffic for a while.
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.