Talk:86th Airlift Wing

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://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:29, 19 June 2011 (UTC)

86th Fighter Wing

This wing spent 33 years as the 86th Fighter Wing, 86th Fighter-Bomber Wing, 86th Fighter-Interceptor Wing and 86th Tactical Fighter Wing. For another 8 years it directed all fighter interceptor units in USAFE. It is also currently active under a different designation. It has earned one Air Force Outstanding Unit Award with Combat V device, and 13 other Air Force Outstanding Unit Awards. Four of these were earned while carrying a "Fighter" designation.

The 86th Fighter Wing (Air National Guard) was active for seven years and has been disbanded. Its only decoration is a Philippine Republic Presidential Unit Citation that was awarded to all US units that participated in the liberation of the Philippines in 1945.

It seems clear that this wing is not only the more notable wing to hold the designation 86th Fighter Wing, but the most likely unit someone would be searching for when using 86th Fighter Wing as their search term. If that were not so, there would be no need for the disambiguator on the National Guard wing. --Lineagegeek (talk) 15:00, 4 March 2015 (UTC)

External links modified

Hello fellow Wikipedians,

I have just modified one external link on 86th Airlift 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:

• Added archive https://web.archive.org/web/20100122091735/http://home.att.net/~jbaugher/usafserials.html to http://home.att.net/~jbaugher/usafserials.html

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

Y 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. --Lineagegeek (talk) 22:57, 15 October 2016 (UTC)

Cheers.—InternetArchiveBot (Report bug) 13:30, 30 September 2016 (UTC)