Edge Rewrite
// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a294e8f7bf945751

Jump to content

Talk:123rd Airlift Wing

Page contents not supported in other languages.
Add topic
From Wikipedia, the free encyclopedia
Latest comment: 13 years ago by Lineagegeek in topic No lineage of 123d Fighter Bomber Wing After 1952

WikiProject Military history/Assessment/Tag & Assess 2008

[edit]

Article reassessed and graded as start class. Referencing and appropriate inline citation guidelines not met. --dashiellx (talk) 18:40, 25 April 2008 (UTC)Reply

[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.kyang.ang.af.mil/
    • In 123d Airlift Wing on 2011-05-23 02:35: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 123d Airlift Wing on 2011-06-01 03:54:59, 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) 03:56, 1 June 2011 (UTC)Reply

No lineage of 123d Fighter Bomber Wing After 1952

[edit]

Returned to state control, redesignated 123d Fighter-Interceptor Wing on 10 July 1952 and activated at Standiford Field; redesignated 123d Fighter-Bomber Wing ca. 1 July 1955, 123d Tactical Reconnaissance Wing ca. 1 July 1958; called to federal servie Apr 1968, etc. While the 123d Tactical Reconnaissance Group was inactivated on 9 December 1974, redesignated 123d Operations Group and activated ca. 1 January 1993. Lineagegeek (talk) 02:56, 12 December 2012 (UTC)Reply