Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/45/d96268876/htdocs/elmundo/wp-includes/classes.php on line 576

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/45/d96268876/htdocs/elmundo/wp-includes/classes.php on line 576

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /homepages/45/d96268876/htdocs/elmundo/wp-includes/classes.php on line 576

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /homepages/45/d96268876/htdocs/elmundo/wp-includes/classes.php on line 576

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/45/d96268876/htdocs/elmundo/wp-includes/classes.php on line 593

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/45/d96268876/htdocs/elmundo/wp-includes/classes.php on line 687

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/45/d96268876/htdocs/elmundo/wp-includes/classes.php on line 687

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /homepages/45/d96268876/htdocs/elmundo/wp-includes/classes.php on line 687

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /homepages/45/d96268876/htdocs/elmundo/wp-includes/classes.php on line 687

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/45/d96268876/htdocs/elmundo/wp-includes/classes.php on line 710

Strict Standards: Redefining already defined constructor for class wpdb in /homepages/45/d96268876/htdocs/elmundo/wp-includes/wp-db.php on line 58

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d96268876/htdocs/elmundo/wp-includes/cache.php on line 99

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/45/d96268876/htdocs/elmundo/wp-includes/cache.php on line 404

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d96268876/htdocs/elmundo/wp-includes/query.php on line 21

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d96268876/htdocs/elmundo/wp-includes/theme.php on line 576

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d96268876/htdocs/elmundo/wp-content/plugins/exec-php/exec-php.php on line 22

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d96268876/htdocs/elmundo/wp-content/plugins/exec-php/includes/manager.php on line 34

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d96268876/htdocs/elmundo/wp-content/plugins/exec-php/includes/manager.php on line 35

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d96268876/htdocs/elmundo/wp-content/plugins/exec-php/includes/manager.php on line 36

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d96268876/htdocs/elmundo/wp-content/plugins/exec-php/includes/admin.php on line 42

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d96268876/htdocs/elmundo/wp-content/plugins/exec-php/includes/admin.php on line 51

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d96268876/htdocs/elmundo/wp-content/plugins/exec-php/includes/admin.php on line 52

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d96268876/htdocs/elmundo/wp-content/plugins/exec-php/includes/admin.php on line 53

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d96268876/htdocs/elmundo/wp-content/plugins/exec-php/includes/ajax.php on line 63

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d96268876/htdocs/elmundo/wp-content/plugins/exec-php/includes/cache.php on line 33

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d96268876/htdocs/elmundo/wp-content/plugins/exec-php/includes/cache.php on line 42

Warning: Cannot modify header information - headers already sent by (output started at /homepages/45/d96268876/htdocs/elmundo/wp-includes/classes.php:576) in /homepages/45/d96268876/htdocs/elmundo/wp-content/plugins/langswitch.php on line 662

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d96268876/htdocs/elmundo/wp-content/plugins/wp-forum/bbcode.php on line 173

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d96268876/htdocs/elmundo/wp-content/plugins/wp-forum/bbcode.php on line 962

Warning: Cannot modify header information - headers already sent by (output started at /homepages/45/d96268876/htdocs/elmundo/wp-includes/classes.php:576) in /homepages/45/d96268876/htdocs/elmundo/wp-content/plugins/wp-forum/cookie.php on line 21

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GoogleSitemapGeneratorLoader::Enable() should not be called statically in /homepages/45/d96268876/htdocs/elmundo/wp-includes/plugin.php on line 311
2008 June | El Mundo Sports

Archive for
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 19

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 28

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 32

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 33

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 19

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 28

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 32

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 33
30 June 2008


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 19

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 28

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 32

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 33

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 19

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 28

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 32

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 33

A Spanish Futbol Dream Come True


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 19

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 28

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 32

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 33

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 19

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 28

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 32

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 33
30 June 2008

There are few adjectives to describe the atmosphere in Vienna on the afternoon of June 29, 2008. For most soccer fans, it’s a dream to go to a World Cup Final or a UEFA Euro Final. Although I wasn’t able to be there in person, I couldn’t help but feel the passion of the game and the nervousness of the players and fans alike. In the tunnel before kickoff, players usually are congratulating each other and slapping high-fives with the opposition.

Not today.

As they walked down the tunnel toward the carnival that is the Euro 2008 Final, there were no glances of admiration, no smiles of joy, and no emotions whatsoever. Looks of businessmen brokering a deal that their livelihood depended on were scattered across the players’ faces. The enormity of this event and the importance of national pride seemed to have a hold on each and every athlete as they entered the field to enormous ovations.

It was old world football against the new regime. Experience against youth. Work ethic against talent. Whatever phrase could be used to analyze this matchup, the only thing that could be sure was that either Germany or Spain was going home champions of Europe.

Both team captains, Germany’s Michael Ballack and Spain’s Iker Casillas, joined the referees at midfield for the coin toss. As the two captains shook hands, with barely more than a quick glance at each other, I knew we were in for something special.

And special it was.

As expected, Spain controlled possession for the first 10 minutes, although both teams looked a little nervous. An errant back-pass from Sergio Ramos gifted Germany striker Miroslav Klose a great chance, but he couldn’t control the ball. The Germans seemed to think the right side of Spain’s lineup was a weakness, and they tried to exploit it at every opportunity. Sergio Ramos stepped up his game and quickly shut down the offensive attack by the German wingers.

Spain took the game to the Germans around the 20th minute as Fernando Torres headed a great cross from the right side of midfield off the post. It was almost 1-0 for Spain except for the bad-luck bounce for Torres. But he didn’t have to wait much longer to put Spain in front.

Torres made his run up the middle, in the 33rd minute, and was fed a great through ball from central midfield. Germany defender Phillip Lahm had good position, but Torres just wanted the ball more. He blew by Lahm as if the defender was standing still and chipped the ball over goalkeeper Jens Lehman to put Spain in front. The Spanish contingent yelled cheers of joy, as chants of El Nino (Torres’ nickname in Spain) could be heard throughout the stadium.

Classy finish from a world-class player.

Right before halftime, Ballack clashed heads with Spanish midfielder Marcos Senna. Ballack, battered and bloodied, ran off the field twice for treatment before the cut over his eye could be shut. As he re-entered the game, his team seemed rejuvenated. Seeing their captain beaten up, but returning to battle, gave the Germans new life. Germany, never known for giving up, pushed on and created several chances before halftime, but they couldn’t find the net as Ballack missed a volley wide.

As the second half began, Spain again took control of the ball possession and wouldn’t let the Germans get it back. Pressing for a second goal, Spanish midfielder Xavi Hernandez sent a laser on goal that Lehman batted away to safety. A few seconds later, Spanish midfielder David Silva sent in a left-footed rocket that went just wide. The Germans were breathing a bit easier as they just averted what would have surely put the game out of reach.

In the 65th minute, things got a bit heated as German midfielder Lukas Padolski got in the face of David Silva. Silva pushed his head toward Padolski as if to head-butt him, but he missed. The two had to be separated as the intensity level kicked up a notch.

A few minutes later, Sergio Ramos dove to head a cross toward goal, but Lehman was there to make the save. What a great chance for Spain to put the game away, and I’m sure Sergio Ramos wished he had that one over again.

In the 82nd minute, Spain winger Santi Cazorla sent in a cross that Danny Guiza headed over to Senna who missed an empty net! Another rued chance for Spain as they tried to bury the Germans, not allowing them to get the ball back. With only second left to play, and Spain leading 1-0, the Germans became desperate, fouling the Spaniards every chance they got in obvious frustration. Germany can do nothing but watch Spain melt the clock with their quick passing and ball control.

As the clock strikes 0:00, the Spanish players, coaches, and fans jump for joy. They have done it. Spain’s first major championship in 44 years. The long wait for silverware is over.

Fernando Torres is the hero of a nation in waiting, but they are not waiting any more.

“Viva España!!!“ was all that could be heard as the Red Fury joined the fans in celebration.

In the middle of the field, Michael Ballack stood stoically and watched Spain celebrating their well-deserved victory. His look was one of astonishment. Ballack had obviously dreamed of this moment his whole life. He looked on as if wanting to change places with the Spanish players celebrating in front of him. But his head was still held high. As it should be.

The officials took a stroll toward the awards podium, and the players clapped for their efforts. The Germans then made their way past the Spanish to receive their second-place medals.

The Spanish applauded them out of respect as well. The Germans, always the sportsmen, accepted their medals with dignity. Although understandably disappointed, the country still stands united in their praise for their team.

The Spaniards then walked up to the podium to receive their winning medals. The last to make his way was the Spanish captain, Iker Casillas. He accepts his medal, walks in front of the players, and steps on top of the podium alongside the Euro Cup Trophy. Casillas raises the trophy high above his head as his fellow teammates join him in celebration.

Spain are champions of Europe.

Viva España!

Share/Save


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 19

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 28

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 32

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 33

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 19

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 28

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 32

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 33

Wranglers Tied for First


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 19

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 28

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 32

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 33

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 19

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 28

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 32

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/45/d96268876/htdocs/elmundo/wp-includes/functions.php on line 33
29 June 2008

Pretty aqua pants, but they didn’t help the Texas Copperheads put any points on the board early in their 38-41 loss to our own Austin Wranglers. Three and out is not a way to start the game.

After the first drive stalled, a fan got to come out on the field and take a few field goal kicks. An Arena League game always has events lined up during time outs, and this game was no different. He lined up, took a step toward the ball, the follow through, and it hit the backside of a Copperhead player! The other players and fans had a nice laugh. I think the holder, who happened to be a Hooters girl, distracted him. 

The referees at Wranglers’ games take their job seriously, but they like to have fun. There is one ref who takes his job a little too seriously. When he needs to move the chains or grab a football for the other refs, he runs as if he just committed a crime and is being chased by the police. He could also be seen doing push-ups before the opening kick off. Take it easy guy, you’re going to hurt yourself.

With the Wranglers up 7-0, the Copperheads had the ball at Austin’s 10 yard line. “Rush situation,” yelled the Wranglers’ head coach. “Don’t be offside!” The ball was snapped, and Texas’ quarterback dropped back to pass. He threw a laser for a touchdown, then ran over to the Copperhead receiver to celebrate. “Woo hoo,” he screamed. “Great catch, baby!”

On the next drive, Andy Hall found Mel Long over the middle for a touchdown. It was a nice move by Long to get separation from the defender. “He’s grabbing my arms, ref!” a defender yelled in frustration. “He can’t do that!” Are the players now coaches? I guess so.

Wranglers’ special teams have been solid all year with one exception. They have given up good field position on kick returns too often. As was the case on the next return, only the Wranglers’ kicker was able to save the touchdown. But it didn’t do much good as the Copperheads scored on their next play to tie the game at 14.

Interesting side note, the kicker for Texas has a heck of a right leg, but no right arm. I was chatting with the Copperheads general manager, Michael Aradillas, and he told me the ir kicker was born with only one arm, but he’s widely considered the best kicker in the league. “These guys are playing for the love of the game,” stated Aradillas. “They only get paid a couple hundred bucks a game and some do have aspirations to play in AFL1 or even the NFL. Our team is pretty much all rookies. It’ll take some time to improve, but they love the game.”

On the next drive for the Wranglers, Hall drops back and shoots a missile over to LeJuan Edwards, who leans against the wall. A defender strips him before he goes down and runs the ball back into the end zone for a score. The fans are stunned.

Every few games, the Wranglers have two sumo wrestlers come out onto the field and try to score a touchdown before the mascot, Trigger, can stop them. This time, the sumo wrestlers decided to take it into their own hands. They ganged up on Trigger, using wrestling moves that would have made the WWF happy. At halftime, I caught up with Trigger to see how he was doing. “You OK, buddy?” I asked. “Those guys didn’t hurt you too badly did they?” He replied, “No, not too badly.” I think his pride was more hurt than his body.

The Wranglers locked down the Copperheads in the third quarter and didn’t allow a single point. Demetrie McCray was flying all over the field as he batted away several passes and made seemingly every tackle to frustrate the Copperhead offense. He seemed to be playing the best game of his season until he got beat deep by a Texas receiver to make the score 35-31 in favor of the Wranglers.

Austin’s offense stalled, giving Texas life, and they took full advantage. The Copperheads ran the ball down the Wranglers throats, eventually putting the ball into the end zone and taking a 38-35 lead with two minutes left.

You could see the desperation as the Wranglers didn’t want to lose this game and fall below .500 again. A sense of urgency was needed, and the fans chanted and encouraged the players, giving them hope. After several successful passing plays, Kamau Jackson flattened the Copperhead defenders, running into the end zone for the winning score.

Wranglers win again!

I caught up with Coach Ben Bennett after the game to see what he thought of the performance:

Austin Chronicle: Good season coach. A bit up and down, but a great turnaround wouldn’t you say?

Coach Bennett: Well, think about the terrible start we had [0-3], and what we have done since [7-6 overall]. We are improving. We’re still tied for first place [in the division] even after that bad start.

AC: That’s all that counts.

CB: Well, we got three more games to win the division, so we’ll see what happens.

Yes coach, we will see what happens. But after this amazing turnaround, no one is considering you a failure.

Share/Save