HomeNewsArticle Display

460th OSS inches by 566th IOS, 6-0

By By Senior Airman Jacque Lickteig , 460th Space Wing Public Affairs / Published September 29, 2006

Josh Mills, quarterback for the 566th Information Operations Squadron's intramural flag football team, smacks into 460th Operation Supports Squadron's Jason Banda during a game Tuesday afternoon. 460th OSS won, 6-0. (U.S. Air Force photo by Senior Airman Jacque Lickteig)
PHOTO DETAILS  /   DOWNLOAD HI-RES 1 of 2

Josh Mills, quarterback for the 566th Information Operations Squadron's intramural flag football team, smacks into 460th Operation Supports Squadron's Jason Banda during a game Tuesday afternoon. 460th OSS won, 6-0. (U.S. Air Force photo by Senior Airman Jacque Lickteig)

Josh Mills, quarterback for the 566th Information Operations Squadron's intramural flag football team, runs the ball during Tuesday's game. (U.S. Air Force photo by Senior Airman Jacque Lickteig)
PHOTO DETAILS  /   DOWNLOAD HI-RES 2 of 2

Josh Mills, quarterback for the 566th Information Operations Squadron's intramural flag football team, runs the ball during Tuesday's game. (U.S. Air Force photo by Senior Airman Jacque Lickteig)

PRINT | E-MAIL
BUCKLEY AIR FORCE BASE, Colo. -- The defending champs, the 460th Operations Support Squadron/2nd Space Warning System intramural flag football team, hushed the 566th Information Operations Squadron team, 6-0, on the new football field Tuesday afternoon, even after losing center Steven Dakus to a shoulder injury during the game.

The teams held each other back defensively most of the game, but the 460th OSS wide receiver Jason Banda gained 40 yards out of the second half chute to help his team score the only touchdown of the game.

On the 460th OSS's mid-field possession toward the beginning of the game, 566th IOS linebacker Jimmy Buczek intercepted quarterback Kevin Scott's throw.

566th IOS wide receiver Brett Wallace gained first and goal. Buczek gained another eight yards, but Banda cut their advances by five by blitzing quarterback Josh Mills.

The 460th OSS's Jared Smith pulled 566th IOS's Brett Barkacs's flag five yards short of the goal, and 460th OSS's Sean Garrick blocked Mills' throw to stop the touchdown.

On the 460th OSS's following possession, Scott threw a 50-yard pass to Garrick for a 60-yard gain, the longest completed pass of the game. But, he couldn't complete another pass in that possession to score.

The 566th IOS gained only five yards in their next possession to give the 460th OSS first down on the 35 yard line. After two penalties that put 460th OSS third and 30 to the 20 yard line, Barkacs intercepted a throw before the halftime whistle blew.

The 460th OSS started the second half out strong with Banda's 40 yard gain. Jared Smith ran for five, and Dexter Bennett caught the touchdown pass for a 6-0 lead. The 460th OSS couldn't connect on the next play for the extra point.

Barkacs racked up 25 yards for the 566th IOS during their following possession, but Garrick stopped them in their tracks with an interception.

On the 460th OSS's next two plays, they were penalized 20 yards for guarding the flag. A call on illegal blocking against 460th OSS forced the turnover.

The 566th IOS's Mills charged 20 yards to put his team on the opposite 35 yard line. A throw to Wallace gained another five yards, and an unnecessary roughness call put the 566th IOS at first and goal.

A quick pass to Wallace left them five yards short of a touchdown with 2:30 left in the game. Mills dropped the hike, so they fell 11 short of the goal. With two minutes to play, 460th OSS charged offsides, so the 566th gained four yards off the penalty. On the fourth down, Banda intercepted the throw in the end zone.
USAF Comments Policy
If you wish to comment, use the text box below. AF reserves the right to modify this policy at any time.

This is a moderated forum. That means all comments will be reviewed before posting. In addition, we expect that participants will treat each other, as well as our agency and our employees, with respect. We will not post comments that contain abusive or vulgar language, spam, hate speech, personal attacks, violate EEO policy, are offensive to other or similar content. We will not post comments that are spam, are clearly "off topic", promote services or products, infringe copyright protected material, or contain any links that don't contribute to the discussion. Comments that make unsupported accusations will also not be posted. The AF and the AF alone will make a determination as to which comments will be posted. Any references to commercial entities, products, services, or other non-governmental organizations or individuals that remain on the site are provided solely for the information of individuals using this page. These references are not intended to reflect the opinion of the AF, DoD, the United States, or its officers or employees concerning the significance, priority, or importance to be given the referenced entity, product, service, or organization. Such references are not an official or personal endorsement of any product, person, or service, and may not be quoted or reproduced for the purpose of stating or implying AF endorsement or approval of any product, person, or service.

Any comments that report criminal activity including: suicidal behaviour or sexual assault will be reported to appropriate authorities including OSI. This forum is not:

  • This forum is not to be used to report criminal activity. If you have information for law enforcement, please contact OSI or your local police agency.
  • Do not submit unsolicited proposals, or other business ideas or inquiries to this forum. This site is not to be used for contracting or commercial business.
  • This forum may not be used for the submission of any claim, demand, informal or formal complaint, or any other form of legal and/or administrative notice or process, or for the exhaustion of any legal and/or administrative remedy.

AF does not guarantee or warrant that any information posted by individuals on this forum is correct, and disclaims any liability for any loss or damage resulting from reliance on any such information. AF may not be able to verify, does not warrant or guarantee, and assumes no liability for anything posted on this website by any other person. AF does not endorse, support or otherwise promote any private or commercial entity or the information, products or services contained on those websites that may be reached through links on our website.

Members of the media are asked to send questions to the public affairs through their normal channels and to refrain from submitting questions here as comments. Reporter questions will not be posted. We recognize that the Web is a 24/7 medium, and your comments are welcome at any time. However, given the need to manage federal resources, moderating and posting of comments will occur during regular business hours Monday through Friday. Comments submitted after hours or on weekends will be read and posted as early as possible; in most cases, this means the next business day.

For the benefit of robust discussion, we ask that comments remain "on-topic." This means that comments will be posted only as it relates to the topic that is being discussed within the blog post. The views expressed on the site by non-federal commentators do not necessarily reflect the official views of the AF or the Federal Government.

To protect your own privacy and the privacy of others, please do not include personally identifiable information, such as name, Social Security number, DoD ID number, OSI Case number, phone numbers or email addresses in the body of your comment. If you do voluntarily include personally identifiable information in your comment, such as your name, that comment may or may not be posted on the page. If your comment is posted, your name will not be redacted or removed. In no circumstances will comments be posted that contain Social Security numbers, DoD ID numbers, OSI case numbers, addresses, email address or phone numbers. The default for the posting of comments is "anonymous", but if you opt not to, any information, including your login name, may be displayed on our site.

Thank you for taking the time to read this comment policy. We encourage your participation in our discussion and look forward to an active exchange of ideas.