'Done' - Birmingham City 'complete' signing in blow to League One rivals


Charlton Athletic striker Alfie May is reportedly set to sign for Birmingham City imminently in a blow to League One rivals Huddersfield Town.
Transfer specialist Darren Witcoop claims May’s move to Blues is “done” despite Huddersfield initially believing the attacker was joining them instead.
Advertisement
Hide AdAdvertisement
Hide AdIt’s a significant deal as Birmingham seek to guarantee goals in the English third tier following their relegation from the Sky Bet Championship. Centre-forward was a position of immediate concern after the exits of Jay Stansfield and Scott Hogan but signing May will ease those worries.
May, who is formerly of Billericay, Corinthian, Chatham, Bromley, Erith & Belvede, Farnborough and Hythe, was quite the late bloomer having emerged from non-league. The now 30-year-old has flourished at a higher level in recent seasons, though, as he has netted over 20 goals in three successive League One campaigns.
Charlton, if they do indeed lose May to Blues, will have enjoyed just one season of the attacker leading the line at The Valley. In total, May has scored 73 goals in 204 League One appearances. He’s also netted 17 in 72 League Two games, as well as 11 in 21 FA Cup fixtures.
Birmingham could secure two strikers in one day
May completing a move on July 1 would mean Blues tying down two attackers in the same day. It was confirmed earlier on Monday morning that popular striker Lukas Jutkiewicz had put pen to paper on a new one-year contract.
Advertisement
Hide AdAdvertisement
Hide Ad

The 35-year-old continues as Birmingham’s longest-serving player, eager to help his side return to the Championship at the first time of asking. May’s arrival will definitely reduce Juktiewicz’s game time but he’s bound to feature more often than he did last campaign.
Comment Guidelines
National World encourages reader discussion on our stories. User feedback, insights and back-and-forth exchanges add a rich layer of context to reporting. Please review our Community Guidelines before commenting.