Jump to content

Talk:96th Test Wing

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
(Redirected from Talk:96th Air Base Wing)
[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://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 483d Composite Wing on 2011-06-19 14:01: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 51st Fighter Wing on 2011-06-19 20:05:22, 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 86th Airlift Wing on 2011-06-19 21:28:49, 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) 21:52, 19 June 2011 (UTC)[reply]

[edit]

Hello fellow Wikipedians,

I have just modified one external link on 96th Test Wing. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at {{Sourcecheck}}).

checkY An editor has reviewed this edit and fixed any errors that were found.

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 15:41, 30 September 2016 (UTC)[reply]

Edits by IP editor

[edit]

Partly reverted the following:

Date of emblem approval. Supported by cited reference.
Removal of capitalization in Air Force reserve. Although there was an organization named Air Force Reserve, it did not exist in 1947, so "reserve" in this context is not a proper noun and should not be capitalized.
Restoration of capitalization in Air Force Materiel Command Restructuring. This was the formal name of the command's reorganization to reduce the number of intermediate headquarters and is a proper noun. --Lineagegeek (talk) 22:44, 25 February 2017 (UTC)[reply]
Concur completely with your reversion of my capitalization. I try to be a stickler about such things and am grateful to learn from a master! Re: the date the emblem was approved, I've moved that info to a note in hopes of decluttering the infobox a bit. I've also moved the current unit emblem to the "image" field of the infobox in conformity with the infobox template which calls for "An image of the unit insignia". Ocalafla (talk) 17:22, 26 February 2017 (UTC)[reply]