This article is rated Start-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects:

Military history: Aviation / Intelligence / North America / United States C‑class 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.Military historyWikipedia:WikiProject Military historyTemplate:WikiProject Military historymilitary history articles C This article has been rated as C-class on the project's quality scale. This article has been checked against the following criteria for B-class status: Referencing and citation: criterion not met Coverage and accuracy: criterion met Structure: criterion met Grammar and style: criterion met Supporting materials: criterion met Associated task forces: /  Military aviation task force Intelligence task force North American military history task force United States military history task force

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'

--JeffGBot (talk) 05:49, 19 June 2011 (UTC)[reply]

These two units do not share a lineage (even by temporary bestowal). Temporary bestowal is ruled out because both were active simultaneously during WW II.

The most current designation for the wing is 26th Network Operations Group26th Network Warfare Wing --Lineagegeek (talk) 15:30, 11 April 2016 (UTC)[reply]

The most current designation for the group is 350th Electronic Systems Wing]

The article needs to be split.--Lineagegeek (talk) 20:06, 13 May 2013 (UTC)[reply]

Text and/or other creative content from 26th Tactical Reconnaissance Wing was copied or moved into 350th Electronic Systems Wing on May 22, 2013. The former page's history now serves to provide attribution for that content in the latter page, and it must not be deleted as long as the latter page exists.

Well? Tabletop (talk) 08:57, 1 June 2013 (UTC)[reply]

Usage in official USAF documents is 2d and 3d rather than 2nd and 3rd for ordinal designations of units through the level of division [1] unless it is omitted entirely [2]. (Third for the numbered air force and III back when there were numbered commands). This has risen to the level of edit wars elsewhere, and there are a couple of redirects where both endings have been used for a Wikipedia article on a USAF unit. I wouldn't make an edit to change this alone, but I'd change it along the way if I were editing a section for other reasons.--Lineagegeek (talk) 19:22, 1 June 2013 (UTC)[reply]