Narrative:

Aircraft X was inbound on an ILS approach to [runway] 16R; on short final he unexpectedly went around. Our procedure with a go around on an ILS approach is to do the published missed approach. I called the valley sector at socal approach and they concurred. The local controller told him to execute the published missed approach and the plane appeared to be doing so. He turned southeast bound and was given the departure frequency; and the frequency change. Shortly after the valley sector yelled on the line that they need to talk to aircraft X so I said we'll try again and the controller switched him again. At this point we observed the plane flying through burbank's class C at 2;500 MSL; flying northbound towards whiteman airport and elevated terrain. Valley calls over again and we switch him again; this time the pilot responds to the change but then calls back a second later asking again for the frequency. At this point I tell the controller to give him 120.4 the filmore frequency which is the tag he was listed under on the radar scope. I called filmore to ask if they had him as he was flying at 2;500 ft seemingly into a mountain; they said no; I asked valley and they did have him. I told them they need to climb him; they did and re-sequenced aircraft X with traffic. On his next approach he transmitted that he had issues with his flaps; that's why he went around.the published missed approach isn't really helpful; in most cases it makes the situation worse. He flew right into burbank's airspace and then into whiteman's airspace barely missing traffic. In most cases aircraft are visual approaches and thus we don't have this problem but there has to be a better missed approach procedure then to turn them into another tower's airspace.

Related reports:

Google
 

Original NASA ASRS Text

Title: VNY Tower Controller reports of a missed approach that doesn't get on the correct frequency quickly; which causes the aircraft to violate a Class Charlie and fly towards mountainous terrain.

Narrative: Aircraft X was inbound on an ILS approach to [Runway] 16R; on short final he unexpectedly went around. Our procedure with a go around on an ILS approach is to do the published missed approach. I called the Valley Sector at SoCal Approach and they concurred. The Local Controller told him to execute the published missed approach and the plane appeared to be doing so. He turned southeast bound and was given the Departure frequency; and the frequency change. Shortly after the Valley Sector yelled on the line that they need to talk to Aircraft X so I said we'll try again and the Controller switched him again. At this point we observed the plane flying through Burbank's Class C at 2;500 MSL; flying northbound towards Whiteman airport and elevated terrain. Valley calls over again and we switch him again; this time the pilot responds to the change but then calls back a second later asking again for the frequency. At this point I tell the Controller to give him 120.4 the Filmore frequency which is the tag he was listed under on the radar scope. I called Filmore to ask if they had him as he was flying at 2;500 FT seemingly into a mountain; they said no; I asked Valley and they did have him. I told them they need to climb him; they did and re-sequenced Aircraft X with traffic. On his next approach he transmitted that he had issues with his flaps; that's why he went around.The published missed approach isn't really helpful; in most cases it makes the situation worse. He flew right into Burbank's airspace and then into Whiteman's airspace barely missing traffic. In most cases aircraft are visual approaches and thus we don't have this problem but there has to be a better missed approach procedure then to turn them into another Tower's airspace.

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.