First college game of 2009

9/5/09 was the first game of the college season, and no, this was not week zero; however, the same ten out of eleven week thing applies.

Once again I was at the field where they treat the officials like crap (see http://pigskinref.blogspot.com/2007/10/this-is-college-football.html). Game administration was a moderately better than previous seasons, but not much. The chain crew was late, the game clock did not run when it should, the play clock (25 second clock) often sat idle, and the ball boys were lame. We did not have our escort to the locker room, they did not supply any water, and we had to wait for the doors to be open at halftime and after the game. In all we still managed to compete the game within 2:51 minutes.

I mention this because each week we get a bulletin from the 'bosses' about game length. This weeks statement goes like this, "Average length of game was right at 3 hours, with the shortest game at 2:35 and longest at 3:41. We averaged 21 fouls, and an average of 10 fouls per game would be of the “coachable” classification."

"Coachable" fouls mean brain-fart fouls such as false starts or illegal formation. These are non-judgement, no subjectivity, no 'when in question do this' type of stuff. Easy, no questions asked fouls. Even your mother would recognize these as fouls. It's the other 11 fouls (using the 21 fouls mentioned above) my bosses care about. These depend upon our rule knowledge and making judgment decisions. This is often very difficult to do.

Contrarily to common myth officials do not want to throw flags. It delays the game and we get monitored on how many flags we throw. I actually spend more energy focusing on what NOT to flag as a foul. But my duty to the players and the game is to make it safe and fair, but to also not influence the game. Safety and fairness should always trump any other motivation. It still is not easy.

For example, during the game I threw flag for a Chop Block against the visitors. A Chop Block is when two players (typically offensive players) attack an opponent with a combination of a High-Low block. Often the first man goes low to take out the knees and the second hits the victim high. Or the first man engages high and the second guy takes his knees out. Visualize what happens to the guys - it's like he gets chopped in half.

Here is the official description: A Chop block is a high-low or low-high combination block by any two players against an opponent anywhere on the field, with or without delay between blocks; the "low" component is at the opponent's thigh or below.

This uses the term block several times. So, what does blocking mean? The official description is: obstructing an opponent by contacting him with any part of the blocker's body.

Does 'contact' mean I brush by a guy with my fingernail and I blocked him?

So, you should be asking some 'what if' questions. What if a guy was on the ground and the defender trips over him while engaged with another guy up high? I mean, hell we have 22 people and over the friggin place and people are falling over left and right. By reading the descriptions above, would this be a chop block?

I was watching the Center and Guard from the visitors all night getting very close to chop blocking the defender. The guard would go low and the center would attempt to contact the defender high. He often would touch the defender, maybe with a hand or shoulder, but he never really 'blocked' they guy enough to make it 'bad'. Eventually, they succeeded and took the guy out, which I promptly flagged. This is a 15 yard penalty.

This is what my bosses are looking for. Using judgment. Technically, there may have been 10 chop block fouls if we were being absolutely anal. Is this what anybody really wants?

This is why I like working int the middle. They are big fouls and player safety is in my hands. I know I'm wrong sometimes and I do miss making the call. I hate it when I miss it. But I catch it more often now than I used to.

More games tomorrow. Stay tuned.

Being 'kinda' Right is not an Option - Part II

Being Kinda Right in College

Last Saturday I worked two College games. One was great. The other was a complete disaster.

First Game
The first game started at 1:00PM ended in 2:50 minutes in spite of a score of 38-22 and nine timeouts being called. I'm still loving this new timing rule. The game ran smoothly and the game was easy to manage. We only had a total of thirteen fouls.

I did throw an Illegal Helmet contact on a tackler. That was easy. I also threw a Personal Foul when #55 drive both this hands into the chest of opponent. I could have tossed him for fighting, but told the White Hat I did not want to eject him. I didn't need to. You could hear his coach screaming across the field "I told you never to retaliate!". He's right. We always catch the second guy. Otherwise a simple game. Then came the second game.

Second Game
The second game began at 7:00PM. By 8:00 I wish I was somewhere else.

The White Hat and I worked the 1:00 game and we also were working the 7:00 game. The first game ended at 3:50, but by the time we completed the game report, took a shower and drove to the 7:00pm game, we did not arrive until 5:30pm. We were rushed.

Being rushed didn't help as this was a difficult game to officiate. There were several personal fouls, and an Unnecessary Roughness when the a defender threw the QB out of bounds and then the QB retaliated. I think there were four flags on the ground.

I threw a flag on an open field Chop Block. The 'low' part of this block needs to be at the thigh or below. I wish I could see the film to confirm the low block. At worst we was at the thigh, but on film it will look pretty dramatic. The defender went head-over-heals folowing the block.

In all there were twenty-six fouls during the game.

I nearly had an Inadvertent Whistle when a receiver muffed a pass, it falls towards the ground, hits a defender on the foot, springs into the air and is finally intercepted. I had moved the whistle into my mouth when the receiver muffed anticipating the incomplete pass. By the time the third player was going after the ball, I had taken it out. That was a close one.

I was involved in two controversial calls, one of which I'm still feeling the sting about. I learned a lot during this game.

Lesson Learned #1

The first was on a pass to the flats to my right. The QB put a lot of heat on the pass so I had to turn quickly to help with coverage. The ball was behind the receiver and thrown short. A defender stretches for the ball and it does a shoe-string catch. I instantly signal incomplete. I know I heard the ball hit the ground and from my angle the ground assisted the receiver with the catch. The wing official did not protest my call, but later said he felt his hand was under the ball. I still felt the ground assisted.

What complicates my call is the interception occurred right in front of the wing official. No, he was trailing the guy who intercepted the pass where I was observing from the front. This is why I turn to assist on these type of passes, because I have a better angle. After the game I asked one of the deep officials who is a former Umpire what his opinion was. Did I go fishing is someone else's pond?

He felt it is OK for an umpire to make that call, but it's one of those things you have to be 100% positive about. The question is -- was I in the best position to make that call? He felt I was still in the process of moving. I had not planted my feet and I was not in the best position to make the call, right or wrong.

In hindsight, I still believe my call was correct, but when this situation occurs again I will add to my mental checklist "am I positioned to make this call." If I'm not positioned properly, how can I really make a call like that even if I am right?

Lesson Learned #2, is a big, painful, humbling lesson I'll describe in the next post.

New Timing Rule is Awesome

Saturday's game was hot. Frickin hot. And then on top of that it was hot.

The field itself (grass) was in okay shape, we had a twenty-five second clock that actually worked, the chain-crew actually did a good job. The home team provided water and sports drink, towels and soap for showers. Nothing to gripe about.

The new NCAA timing rules seem to be working. Our game finish in exactly three hours. This was with twenty-five penalities, eleven time-outs, and final score of 38-16, so there were plenty of times where the clock stopped. Last season the average was something like 3:15. I'm loving the new clock mechanic.

In simple terms the clock is now only stopping on incomplete passes. For plays going out of bounds (could be a run, completed pass, fumble out of bounds, backward pass, etc.) the clock will start on the Ready. Once I put the ball down the White Hat starts the clock. The clock will still be start on the snap on change of possession and and will be stoped to move the chains as ususl. The twist is within two minutes in the 2nd and 4th quarters we fall back to the previous timing rules. But for 56 minutes, it is pure bliss.

The game started on a strange note. During the opening kickoff, the 25-second clock expired way before the kickers were even close to kicking the ball. When I say expired, I mean it was '00' for five seconds. I threw a flag for delay of game. As umpire, this is not my call, but no one seemed to be paying attention. I heard the coach say "that was ticky-tack". Well, ya, it was, but why bother having the rule if we aren't going to follow them. We keep getting preasured to speed the games up, so what the hell. And you damn well know if it was the the other team he'd be screaming. Nonetheless, I won't do that again.

We had an unusual Illegal Batting by the offense following a blocked scrimmage kick. Batting, in case you are not familiar, is intentionally striking or intentionally changing the balls direction with the hands or arms. So, in this case, the blocking of the scrimmage kick (punt) is technically batting, but that touching is ignored. What is not ignored is after the kick is blocked a player from the kicking team leaps in the air and intentionally strikes the ball so it goes forward. Batting is complicated because sometimes you can and sometimes you can't. I'll do a post just on batting soon. Luckily, batting does not occur often, but when it does it is a 15-yard, loss of down penalty. But there are exceptions to this also.

I threw flags for Chop Block, False Start, Ineligible Receiver Downfield, and a Defensive Holding.

The new Chop Block rule is also great. More on this next time.

There we also several defensive holding fouls during pass plays.