Narrative:

Aircraft X was inbound to bur on the ILS and had a TCAS RA with an aircraft in the vny traffic pattern at 1800 feet east of vny. He was issued a 210 heading and 4;000 feet as he was at 3;000 feet on the final. He went around for another approach and had another TCAS RA with another aircraft in the vny traffic pattern east of vny as high as 1;900 feet. This time bur tower issued 'execute the published missed approach' and aircraft X immediately began a turn south and west back towards vny VOR instead of waiting to begin the missed approach at the missed approach point. In the mean time we were on the landline coordinating with bur tower about the missed approach and had mistakenly said to issue aircraft X a 210 heading but immediately corrected ourselves to which the tower responded he is already in the turn executing the published missed approach. Since aircraft X began his turn early at 3;000 we issued aircraft Y a turn to 180 immediately who had departed vny southeast bound on a 110 heading and was at 3;000 feet within 3 miles of aircraft X. We also had aircraft X turn to a 250 heading and climb to 5;000 to separate the traffic as much as possible.when bur issues a published missed approach as a controller I expect aircraft X to keep flying on the approach to the published missed approach point before going around giving time to correct the situation with the other aircraft that will be in the way. Also as this was aircraft X second go around there may have been confusion from the pilots point of view as he was issued a 210 heading at 4;000 on the first go around as we did not have any traffic conflicts that would be a problem. As far as I am aware this was a pilot deviation since they did not execute the publish missed approach properly.

Google
 

Original NASA ASRS Text

Title: SCT Controller describes a situation where an aircraft is issued the published missed approach at BUR and starts the turn early causing a conflict with another aircraft along with an airspace violation.

Narrative: Aircraft X was inbound to BUR on the ILS and had a TCAS RA with an aircraft in the VNY traffic pattern at 1800 feet east of VNY. He was issued a 210 heading and 4;000 feet as he was at 3;000 feet on the final. He went around for another approach and had another TCAS RA with another aircraft in the VNY traffic pattern east of VNY as high as 1;900 feet. This time BUR tower issued 'Execute the published missed approach' and Aircraft X immediately began a turn south and west back towards VNY VOR instead of waiting to begin the missed approach at the missed approach point. In the mean time we were on the landline coordinating with BUR tower about the missed approach and had mistakenly said to issue Aircraft X a 210 heading but immediately corrected ourselves to which the tower responded he is already in the turn executing the published missed approach. Since Aircraft X began his turn early at 3;000 we issued Aircraft Y a turn to 180 immediately who had departed VNY Southeast bound on a 110 heading and was at 3;000 feet within 3 miles of Aircraft X. We also had Aircraft X turn to a 250 heading and climb to 5;000 to separate the traffic as much as possible.When BUR issues a published missed approach as a controller I expect Aircraft X to keep flying on the approach to the published missed approach point before going around giving time to correct the situation with the other aircraft that will be in the way. Also as this was Aircraft X second go around there may have been confusion from the pilots point of view as he was issued a 210 heading at 4;000 on the first go around as we did not have any traffic conflicts that would be a problem. As far as I am aware this was a pilot deviation since they did not execute the publish missed approach properly.

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.