Brady Quinn entered the field inside Arrowhead Stadium after a smattering of fans cheered his predecessor's head injury. Now, he has left the field under similar circumstances, just without the crowd's approval.
Quinn was forced out of the game after taking a nasty hit during a sack. The early diagnosis is a head injury.
Matt Cassel returned and quickly hooked up with Dwayne Bowe for a long gain. Fans still don't seem overly excited to see him, though.
So, what does the latest Kansas City Chiefs quarterback injury mean? Let's check it out.
For the Chiefs
All due to respect to the gentlemen in red, but this doesn't mean much of anything in the long run. Kansas City couldn't have expected Quinn to be the answer at quarterback.
Especially after his first quarter in which he amassed one yard.
That isn't a typo. In the yards column on the box score, he is listed as having thrown for a single yard.
In reality, this injury might result in a few more wins for the Chiefs this year. Cassel is not a great quarterback, but he has a much more solid track record than the journeyman Quinn.
For Your Fantasy Team
If you had Quinn as your starting quarterback at any point this season, I'll assume it was only as a bye replacement that you had neglected until the last minute.
If you had him as your starting quarterback on a more permanent basis, your team has got to be struggling.
Regardless of the reason, his impact going forward will be non-existent. Romeo Crennel needed a legitimate reason to go back to Cassel, and he got it when Quinn went down.
There aren't any scenarios under which you should expect Quinn to return to the field that don't involve another Cassel injury. And even then, I wouldn't be surprised if the Chiefs turned to somebody else.
I wonder what Tim Tebow is doing.