The address was not really able to spend any inputs prior to it receiving an input. If you look closely you will see that, according to blockchain.info it spent an input two seconds prior to it receiving the input that it spent. This was likely the result of the 1st received transaction being propagated by a node and then the spending transaction being propagated prior to the 1st transaction being fully propagated. Blockchain.info's node likely "saw" the 2nd transaction first
Ah, sounds reasonable then. I guess whoever controlled that address decided to move the coins only a second or two after receiving them while the receiving transaction was still unconfirmed. That sending transaction reached Blockchain.info first before the recieving transaction was able to reach it.
I've found that transactions tend to be visible (albeit unconfirmed) almost instantaneously after being broadcast so whoever controlled that address must have been in quite a hurry.