Talk:51st Fighter Wing
This article is rated Start-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||||||||||||||||
|
F-106's at Naha
[edit]Just a brief correction: under the "Cold War" heading it states that the 51st Wing was at Naha with F-102's. I was stationed at Naha from 1969 to 1970 and we had two F-102's and two F-106's there on standby alert at all times, not just F-102's. Those F-106's were a lot faster than the F-102's (having derived from the F-102 design). If trouble was heading our way those jets were scrambled FAST and got off our runway with full afterburners, their jet engines screeching so loud you couldn't even hear yourself scream if you happened to be on the flightline at the time. That's what interceptor aircraft were for, to intercept trouble before it got too close. That's why President George Bush took the initiative and got us into Afghanistan and Iraq, he had been an F-102 pilot in the Air National Guard, trained to react quickly. Many of us to this day think the F-106 was the best fighter jet the Air Force ever had in its inventory. It looked really good and flew really fast, some say as high as Mach 2.8! 63.192.101.175 (talk) 09:02, 26 February 2010 (UTC)Sgt. Rock
Dead link
[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'
- Start-Class military history articles
- Start-Class military aviation articles
- Military aviation task force articles
- Start-Class North American military history articles
- North American military history task force articles
- Start-Class United States military history articles
- United States military history task force articles