Manchester City manager Manuel Pellegrini criticised referee Mark Clattenburg for the penalty awarded against Raheem Sterling after his side's 2-1 defeat to Tottenham on Sunday.
City lost further ground in the Premier League title race with the costly defeat at the Etihad Stadium - their seventh of the league campaign.
Harry Kane opened the scoring with the controversial penalty early in the second half after Danny Rose's cross had deflected off Sterling's back and onto his elbow, with Clattenburg pointing to the spot.
City substitute Kelechi Iheanacho looked to have salvaged a point, but Christian Eriksen's winner seven minutes from time proved decisive and Pellegrini was left to rue the penalty decision.
"Before that [penalty] we had more clear chances. There were not too many in such a close game but the penalty was very important," he told Sky Sports.
"Unfortunately it is the same referee who in the first game against Tottenham [earlier this season] gave two offside goals. It's an unbelievable penalty that decides the game.
"The shot hits the back of Sterling then his elbow slightly. I don't think the referee can decide the game in that way. That action in such a close game was absolutely decisive.
"We are very unlucky with this referee, we have nothing more to do than to complain about that action."
City are now six points off the pace in fourth following two defeats to Spurs along with losses to title rivals Arsenal and Leicester this season.
Asked about his side's fading title chances, Pellegrini added: "We responded well but I feel it was more important to win the three points.
"We are not going to give up, losing twice here against Leicester and Tottenham is too much but we have to continue working with the players.
"The spirit of the team was very good, we need to improve our football but we are going to carry on fighting as far as we can."
Get the best features, fun and footballing frolics straight to your inbox every week.
Thank you for signing up to Four Four Two. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.