Narrative:

Working wr/rcic with moderate traffic; a combination of TRSA arrivals/departures and one practice approach. Training on local control at the time of the incident. Helicopter X was executing an ILS runway 2L practice approach VFR. When the aircraft advised they were executing their missed approach I radar identified the aircraft and initiated a turn to the east and gave appropriate altitude instructions to set the aircraft up for their next request. Immediately following this; the ojti (on job training instructor) on local control called via the shout line to question what the helicopter was doing; advise me that the aircraft never checked on their frequency; and inform me of traffic in the pattern; reference the turning helicopter. I provided local control with what instructions had been issued. Following the shout line coordination I immediately informed the helicopter of the traffic and requested the aircraft climb at best rate to the assigned altitude; which I knew would de-conflict the aircraft with the traffic pattern altitude. The aircraft never reported the traffic in sight; but the targets diverged and I informed the aircraft the traffic was no factor. Following this I asked the aircraft if they had ever checked on with the tower and they indicated they had not been switched to the tower frequency. The helicopter continued their flight without any further incidents. I see three main problems (and associated solutions) with this event: 1) I was unable to recall if I actually switched the aircraft to the tower frequency before it entered the class-D airspace. While I would like to believe that I had instructed the aircraft to change frequencies; I would have to review the voice recording to determine if I accomplished that duty or not. Obviously; I will increase my diligence to ensure I switch aircraft to the tower frequency in an appropriate and timely fashion. 2) I believe the training on local control negatively affected the tower's situation awareness regarding an inbound aircraft not on their frequency. Subsequent conversation with the ojti determined that he was aware they were not talking to the helicopter and was monitoring the situation appropriately. I do not know why no attempt was made prior to the aircraft's missed approach to determine if the aircraft was still on my frequency; but my guess is that the ojti was waiting for the developmental to address the situation and just let it go too far. Had local control communicated with me via any available means that they were not talking to the helicopter it would have immediately identified and remedied the problem before the potential for conflict with their pattern traffic existed. 3) I cannot explain why an aircraft executing an approach inbound to a runway would not question still being on the approach control frequency inside the class-D airspace. If the aircraft had questioned whether they should be talking to the tower; the problem would have immediately been identified and remedied before the potential for conflict with the pattern traffic existed.

Related reports:

Google
 

Original NASA ASRS Text

Title: FAI TRACON Controller described airspace incursion event when failing to coordinate a helicopter conducting an ILS 2L practice approach to the tower resulting in a near conflict event.

Narrative: Working WR/RCIC with moderate traffic; a combination of TRSA arrivals/departures and one practice approach. Training on Local Control at the time of the incident. Helicopter X was executing an ILS Runway 2L practice approach VFR. When the aircraft advised they were executing their missed approach I RADAR identified the aircraft and initiated a turn to the east and gave appropriate altitude instructions to set the aircraft up for their next request. Immediately following this; the OJTI (on job training instructor) on Local Control called via the shout line to question what the helicopter was doing; advise me that the aircraft never checked on their frequency; and inform me of traffic in the pattern; reference the turning helicopter. I provided Local Control with what instructions had been issued. Following the shout line coordination I immediately informed the helicopter of the traffic and requested the aircraft climb at best rate to the assigned altitude; which I knew would de-conflict the aircraft with the traffic pattern altitude. The aircraft never reported the traffic in sight; but the targets diverged and I informed the aircraft the traffic was no factor. Following this I asked the aircraft if they had ever checked on with the Tower and they indicated they had not been switched to the Tower frequency. The helicopter continued their flight without any further incidents. I see three main problems (and associated solutions) with this event: 1) I was unable to recall if I actually switched the aircraft to the Tower frequency before it entered the Class-D airspace. While I would like to believe that I had instructed the aircraft to change frequencies; I would have to review the voice recording to determine if I accomplished that duty or not. Obviously; I will increase my diligence to ensure I switch aircraft to the Tower frequency in an appropriate and timely fashion. 2) I believe the training on Local Control negatively affected the Tower's situation awareness regarding an inbound aircraft not on their frequency. Subsequent conversation with the OJTI determined that he was aware they were not talking to the helicopter and was monitoring the situation appropriately. I do not know why no attempt was made prior to the aircraft's missed approach to determine if the aircraft was still on my frequency; but my guess is that the OJTI was waiting for the Developmental to address the situation and just let it go too far. Had Local Control communicated with me via any available means that they were not talking to the helicopter it would have immediately identified and remedied the problem before the potential for conflict with their pattern traffic existed. 3) I cannot explain why an aircraft executing an approach inbound to a runway would not question still being on the Approach Control frequency inside the Class-D airspace. If the aircraft had questioned whether they should be talking to the Tower; the problem would have immediately been identified and remedied before the potential for conflict with the pattern traffic existed.

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.