Jump to content

Talk:432nd Wing

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Please rename this article 432d Wing...

[edit]

...to make it consistant with USAF naming conventions and other Wikipedia Articles. --Thanks 24.210.216.14 08:04, 22 May 2007 (UTC)[reply]

The USAF currently uses "432nd Wing". Ng.j (talk) 01:06, 19 April 2011 (UTC)[reply]

Tail Codes ?

[edit]

The photos on Fox News show the UAV's carrying the Nellis tail code "WA". Is this the tail code for the 432d as well ?

Bwmoll3 23:39, 16 July 2007 (UTC)[reply]

What you learn on these pages. I did not find a list, however Globemaster has a searchable database. According to them Nellis uses:
  • LV 4450 TG
  • OT 422 TES
  • TR 37 TFW
  • WA 64 AGRS, 65 AGRS, 414 CTS, 57 FG, 57 FW, 433 WPS
Creech uses:
  • WA 11 RS, 15 RS, 17 RS
Vegaswikian 00:20, 17 July 2007 (UTC)[reply]

Requested move

[edit]
The following discussion is an archived discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. No further edits should be made to this section.

The result of the move request was: page moved. Vegaswikian (talk) 05:19, 26 April 2011 (UTC)[reply]



432d Wing432nd Wing – Per WP:COMMONNAME and USAF media recently produced. Only article move requested, Talk page exists. Ng.j (talk) 01:44, 19 April 2011 (UTC)[reply]

The above discussion is preserved as an archive of a requested move. Please do not modify it. Subsequent comments should be made in a new section on this talk page. No further edits should be made to this section.

The problem with all of this is that the United States military doesn't use this abbreviation for the numbered units. It uses the 'd', so the title now is factually incorrect. Bwmoll3 (talk) 13:00, 26 April 2011 (UTC)[reply]

Take a look a Category:Aerospace expeditionary wings of the United States Air Force. The 2009 fact sheet uses 432, no 'd' or 'nd'. However note this 2008 press release from Nellis uses nd. Vegaswikian (talk) 17:49, 26 April 2011 (UTC)[reply]

http://www.afhra.af.mil/organizationalrecords/wingsandgroups.asp All suffixes have been removed. I suggest if we are going to make these changes, we should use the correct one. Bwmoll3 (talk) 18:41, 26 April 2011 (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://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'
    • In 432d Wing on 2011-06-19 07:38:48, 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) 07:39, 19 June 2011 (UTC)[reply]

New Commander

[edit]

The article lists Col Pete Gersten as the wing commander. However, according to the USAF website, Pete Gersten is now a Brig Gen and is no longer part of the 432d Wing. I don't know who the current commander is, but this needs to be updated. reference: http://www.af.mil/information/bios/bio.asp?bioID=15276 — Preceding unsigned comment added by 24.142.68.133 (talk) 03:57, 22 July 2012 (UTC)[reply]

[edit]

Hello fellow Wikipedians,

I have just modified 3 external links on 432d 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}}).

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

  • 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) 01:42, 30 September 2016 (UTC)[reply]