Talk:153d Command and Control Squadron

From Wikipedia, the free encyclopedia
Jump to: navigation, search
WikiProject United States / Wyoming (Rated Start-class, Low-importance)
WikiProject icon This article is within the scope of WikiProject United States, a collaborative effort to improve the coverage of topics relating to the United States of America on Wikipedia. If you would like to participate, please visit the project page, where you can join the ongoing discussions.
Start-Class article Start  This article has been rated as Start-Class on the project's quality scale.
 Low  This article has been rated as Low-importance on the project's importance scale.
Taskforce icon
This article is supported by WikiProject Wyoming.
 
WikiProject Military history (Rated Start-Class)
MILHIST This article is within the scope of the Military history WikiProject. If you would like to participate, please visit the project page, where you can join the project and see a list of open tasks. To use this banner, please see the full instructions.
Start This article has been rated as Start-Class on the quality assessment scale.

Sources of information[edit]

The information obtained about the 153d CACS was public information from many different sources: Air Force Historical Research Agency, Air Force Space Command, 90th Missile Wing FOIA office to name a few(arren). The information specifically asked for was: Air Force Form 35, Request for Authorization for Assumption of/Appointment to Command (these have commander's names and unit activation dates), lineage and heraldry for 4 CACS, 721 MCCS, and other units which were kludged into the 153d (the logo and bits of the history). Oh, and Air Force Space Command general orders when bestowing Air Force Outstanding Unit Awards - those are sometimes good for unit designations and locations. TDRSS (talk) 17:31, 3 September 2009 (UTC)

Dead link[edit]

During several automated bot runs the following external link was found to be unavailable. Please check if the link is in fact down and fix or remove it in that case!

  • http://www.wychey.ang.af.mil/main.asp
    • In 153d Command and Control Squadron on 2011-05-23 03:35:08, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'
    • In 153d Command and Control Squadron on 2011-06-01 16:25:58, Socket Error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'

--JeffGBot (talk) 16:26, 1 June 2011 (UTC)