Narrative:

I was training on the west arrival at dtw with weather in area. This was a complex session with trying to run visuals between the weather cells and then going to ILS approaches as the weather started to impact the final. I had to take the frequency from the developmental a couple of times and even though I had communicated that I wanted the involved aircraft to do an ILS; the developmental turned him in for a visual approach. I told developmental to correct the vector as the aircraft was requesting an additional vector for weather that put him closer to traffic on other localizer. The weather vector was approved and I told him to watch the situation developing. We slowed aircraft and turned onto localizer; but before the aircraft was established; I realized that compression was not going to allow approach to continue. I turned the aircraft right immediately; but was told later I had a possible proximity error. I take full responsibility; but do feel as if some things contributed; 1.) even thought there is an unused scope next to where training was taking place; we are not able to use it. We have to only look at the scope that the trainee is using. This makes if difficult for two reasons; 1. The trainer has to look at the trainees preferential sets on the scope. I find it uncomfortable to look at some of the trainees scopes because they look at such a close range. What might look like 3 miles on my scope does not look like 3 miles on their scope. 2. We were using a distance measuring aid (*T); but as a trainer having to look from an extra foot or two away makes it tough. In the above situation I thought it said 3.83 but it must have said 3.33 because the next hit showed like 3.21 and I took action; but too late. We used to be able to be able to use adjacent scopes with our own preferential and bring up 'J-rings' and other aids that we saw fit for monitoring a developing situation. It also allowed us to sit straight to the scope at a good distance; instead of off to side and farther back. Note: they put the same scope rule into effect to eliminate a trainer from missing a flashing point out that the trainee might take. We used to tell trainee to tell us before taking a point out so we knew what to watch. 2.) as is usual in these situations with weather and unusual situations developing; we had too many people trying to make decisions. During the course of this session; even though we had a coordinator we were approached by tmu; feeder H/O and another supervisor to coordinate things. I had to take too much attention away from training to answer questions. We needed one focal for everything.

Related reports:

Google
 

Original NASA ASRS Text

Title: D21 Controller providing OJT described a loss of separation event when the developmental was late in issuing OJTI directed instructions. The reporter claimed limited radar display visibility and distracting questions were causal factor in this instance.

Narrative: I was training on the West Arrival at DTW with weather in area. This was a complex session with trying to run visuals between the weather cells and then going to ILS approaches as the weather started to impact the final. I had to take the frequency from the developmental a couple of times and even though I had communicated that I wanted the involved aircraft to do an ILS; the developmental turned him in for a visual approach. I told developmental to correct the vector as the aircraft was requesting an additional vector for weather that put him closer to traffic on other localizer. The weather vector was approved and I told him to watch the situation developing. We slowed aircraft and turned onto localizer; but before the aircraft was established; I realized that compression was not going to allow approach to continue. I turned the aircraft right immediately; but was told later I had a possible Proximity Error. I take full responsibility; but do feel as if some things contributed; 1.) Even thought there is an unused scope next to where training was taking place; we are not able to use it. We have to only look at the scope that the trainee is using. This makes if difficult for two reasons; 1. The trainer has to look at the trainees preferential sets on the scope. I find it uncomfortable to look at some of the trainees scopes because they look at such a close range. What might look like 3 miles on my scope does not look like 3 miles on their scope. 2. We were using a distance measuring aid (*T); but as a trainer having to look from an extra foot or two away makes it tough. In the above situation I thought it said 3.83 but it must have said 3.33 because the next hit showed like 3.21 and I took action; but too late. We used to be able to be able to use adjacent scopes with our own preferential and bring up 'J-rings' and other aids that we saw fit for monitoring a developing situation. It also allowed us to sit straight to the scope at a good distance; instead of off to side and farther back. Note: They put the same scope rule into effect to eliminate a trainer from missing a flashing point out that the trainee might take. We used to tell trainee to tell us before taking a point out so we knew what to watch. 2.) As is usual in these situations with weather and unusual situations developing; we had too many people trying to make decisions. During the course of this session; even though we had a coordinator we were approached by TMU; Feeder H/O and another supervisor to coordinate things. I had to take too much attention away from training to answer questions. We needed one focal for everything.

Data retrieved from NASA's ASRS site as of April 2012 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.