Talk:32d Air Operations Group

Dead link

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://afhra.maxwell.af.mil/rso/rso_index.html
  • In Hamilton Air Force Base on 2011-03-22 19:58:15, 404 Not Found
  • In Hamilton Air Force Base on 2011-04-18 04:46:30, 404 Not Found
  • In 13th Bomb Squadron on 2011-05-23 02:58:17, 404 Not Found
  • In 17th Training Wing on 2011-05-25 02:00:51, 404 Not Found
  • In 1st Troop Carrier Group on 2011-05-25 06:54:14, 404 Not Found
  • In 13th Bomb Squadron on 2011-06-01 15:07:57, 404 Not Found
  • In 17th Training Wing on 2011-06-01 22:26:07, 404 Not Found
  • In 18th Operations Group on 2011-06-02 00:26:19, 404 Not Found
  • In 1st Troop Carrier Group on 2011-06-10 04:31:19, 404 Not Found
  • In 22d Air Refueling Wing on 2011-06-19 05:30:26, 404 Not Found
  • In 32d Air Operations Group on 2011-06-19 06:34:59, 404 Not Found

--JeffGBot (talk) 06:35, 19 June 2011 (UTC)

Dead link 2

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://home.att.net/~jbaugher/usafserials.html
  • In Davis–Monthan Air Force Base on 2011-03-17 00:06:04, 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 Don Muang Royal Thai Air Force Base on 2011-03-17 13:51:38, 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 Dreux-Louvilliers Air Base on 2011-03-17 16:15:45, 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 Duxford Aerodrome on 2011-03-17 18:06:35, 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 Earls Colne Airfield on 2011-03-17 19:49:46, 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 Eglin Air Force Base on 2011-03-18 00:53:53, 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 England Air Force Base on 2011-03-18 05:59: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 Erding Air Base on 2011-03-18 07:24:53, 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 Fürstenfeldbruck Air Base on 2011-03-19 16:19:40, 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 George Air Force Base on 2011-03-19 21:10:42, 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 Hahn Air Base on 2011-03-22 19:02:46, 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 Homestead Joint Air Reserve Base on 2011-04-10 04:18:17, 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 Hahn Air Base on 2011-04-13 04:40:55, 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 Hamilton Air Force Base on 2011-04-18 04:46:50, 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 Hahn Air Base on 2011-04-22 04:10:23, 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 100th Air Refueling Wing on 2011-05-23 01:59:13, 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 14th Flying Training Wing on 2011-05-23 03:30:43, 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 100th Air Refueling Wing on 2011-05-31 21:25:06, 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 10th Air Base Wing on 2011-06-01 01:46:02, 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 14th Flying Training Wing on 2011-06-01 15:59:10, 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 20th Fighter Wing on 2011-06-19 05:22:14, 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 301st Fighter Wing on 2011-06-19 06:25:11, 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) 06:38, 19 June 2011 (UTC)

Redirect

Article a/o 8 Apr 2012 uses an outdated designation for this unit, which is currently the 32d Air Expeditionary Group. Created article for current designation and moved all material in this article as of that date to 32d Air Expeditionary Group article and converted this page to a redirect. Lineagegeek (talk) 20:08, 8 April 2012 (UTC)