Definitely a weird case, this works (in both cases) on the premium search endpoint, but not on standard where it seems to fail on uppercase. However, as a workaround, I added the @ character to the query:
https://api.twitter.com/1.1/search/tweets.json?q=to%3A%40ILCUK
This appears to work as expected.