Jump to content

Recommended Posts

Have a Monogram kit in 1/72 and I'm trying to find some info on the subject.

  1. Decals are for AF66051, was this plane used in Desert Storm?
  2. instructions show 36320 and 36492 as colors are these correct?
  3. What pattern would it have had?

Could it be this plane but the 6 was left off the decals?

800px-Deny_Flight_EF-111.jpg

Edited by Spectre711
Link to post
Share on other sites

Interesting...from the markings on the tail, you would think that was 66-6051, but checking Scramble and Joe Baugher's sites, that s/n doesn't exist. Both show 66-0051 as an EF-111A (converted from an F-111A) and if the kit markings show AF66 051 they are probably correct. Not sure if the aircraft in the photo is 66-0051 with some non-standard markings - I don't see any other EF-111 serial numbers that make sense. The CC on the tail indicates it was assigned to Cannon AFB, NM. From this site, the EF-111s used in Desert Storm came out of Mountain Home AFB - in fact, according to the Cannon AFB Wiki Page, Cannon didn't activate its EF-111 squadron until August 1992. Also from Wiki, that photo was taken in 1995 on a mission during Operation Deny Flight enforcing the no-fly zone over Bosnia and Herzegovina.

Link to post
Share on other sites

The kit decals has AF66051 instead of AF666051 and there is a MO instead of CC. I think all the EF-111s were converted from F-111s so I don't know how that comes into play with serial numbers.

This one shows AF66049 and MO.

800px-EF-111A_Raven.jpg

Edited by Spectre711
Link to post
Share on other sites

All EF-111s were converted from F-111s, there were no new-build EFs, and they would have retained their original serial numbers. If you look at Joe Baugher's site, he notes the ones which were converted:

http://www.joebaugher.com/usaf_serials/1966.html

As I said, I don't know what the deal with the tail number on your original shot, but the 66-0051 is a valid number, and would have typically been displayed with just the last 3 digits, as with 66-0049 in your last post. The MO tail code is from Mountain Home, and as I mentioned, they did participate in Desert Storm.

Link to post
Share on other sites

The aircraft in the picture is 66-0051.

While based at Upper Heyford (UH) and Mountain Home (MO), the EF's generally carried the last 3 digits of their serial number in large numbers on their tails.

At some point after all Ef's were consolidated in the 429 ECS at Cannon in the early 1990's, a 4 digit code appeared, with the first digit being the FY, hence the photo shows 6051. The extra zero was omitted (all EF's were had an FY number less than 100, so having all the zero's wasn't necessary).

Not sure why this occured, although given that 66-0039 and 67-0039 were both based at CC at the same time, it may have been to make identification easier from a distance.

The excellent Schiffer publication by Don Logan shows examples of both marking styles, as does www.defenseimagery.mil

At the time of Desert Storm, EF's were based at UH and MO only, but not all EF's participated in Desert Storm.

Don Logan's book contains a list of s/n which did participate - 66-0051 is not one of them.

The FS colours listed are correct, and the pattern would be same as the photo (upper surfaces 36320).

Best regards,

Phil

Link to post
Share on other sites

66-0051 didn't participate in DS, but 66-0015 did. So if you would swap the numbers on the decals, you would probably be safe, as both were Mountain Home birds.

BTW, we're having a DS group build coming up in 8 days, why not join it with your EF-111 :yahoo:

Link to post
Share on other sites

Got this from a Mountain Home site,

In early 1991, the Air Force announced that the 366th would become the Air Force's premier "air intervention" composite wing. The wing would grow from a single-squadron of EF-111As to a dynamic, five squadron wing with the ability to deploy rapidly and deliver integrated combat airpower. This resulted from General Merrill A. McPeak, then Chief of Staff of the Air Force (CSAF) and his belief that creating standing composite wings, wherein one commander would control all types of aircraft to defeat an enemy, would streamline and shorten tactical planning. General McPeak expressed that a composite wing would make "smaller mistakes because it works and trains together in peacetime...it knows the playbook...in other words, it can exploit the inherent flexibility of airpower."

The air intervention composite wing's rapid transition from concept to reality began in October of 1991 when redesignated as the 366th Wing. The wing's newly reactivated "fighter squadrons" became part of the composite wing in March 1992. The 389th Fighter began flying the dual-role F-16C Fighting Falcon, while the 391st Fighter Squadron was equipped with the new F-15E Strike Eagle. These two squadrons provide Gunfighters round-the-clock precision strike capability.

In June 1992, as part of Air Force restructuring, Strategic Air Command and Tactical Air Command merged to form Air Combat Command. A month later, the 366th also gained the 34th Bomb Squadron. Located at Castle AFB, California, the 34th flew the B-52G Stratofortress, giving the composite wing deep interdiction bombing capabilities as the only B-52 unit armed with the deadly, long-range HAVE NAP missile.

Next, in September 1992, Air Force redesignated the 390th Electronic Combat Squadron as the 390th Fighter Squadron, which began flying the Air Force's premier air superiority aircraft, the F-15C Eagle. With its internal 20-millimeter cannon and air-to-air missiles, the F-15C protects the wing's high-value assets from enemy air threats. At the same time, Air Force activated the 429th Electronic Combat Squadron, which assumed control of the wing's EF-111A aircraft as they prepared to transfer to Canon AFB, New Mexico.

During this buildup, however, the wing's Ravens remained busy flying combat missions over Iraq, both from Saudi Arabia in support of Operation Desert Calm, and from Incirlik AB, Turkey, in support of Operation Provide Comfort. In June 1993, however, the wing transferred its remaining EF-111As and the 429th ECS to Cannon AFB, ending Mountain Home's long association with the various models of the F-111 aircraft.

Link to post
Share on other sites
At the time of Desert Storm, EF's were based at UH and MO only, but not all EF's participated in Desert Storm.

Don Logan's book contains a list of s/n which did participate - 66-0051 is not one of them.

The FS colours listed are correct, and the pattern would be same as the photo (upper surfaces 36320).

66-0051 didn't participate in DS, but 66-0015 did. So if you would swap the numbers on the decals, you would probably be safe, as both were Mountain Home birds.

BTW, we're having a DS group build coming up in 8 days, why not join it with your EF-111 :D

Sounds like a plan, thanks guys!

Link to post
Share on other sites
66-0051 didn't participate in DS, but 66-0015 did. So if you would swap the numbers on the decals, you would probably be safe, as both were Mountain Home birds.
Sounds like a plan, thanks guys!

I just noticed, I made an error. 66-0015 wasn't a Mountain Home bird, it was a Upper Heyford bird assigned to the MO unit during DS. So it flew with UH tailcodes as you can see here: EF-111 66-0015. If you want, I have a pair of UH tailcodes in 1/72 for you, free of charge of course.

Link to post
Share on other sites
I just noticed, I made an error. 66-0015 wasn't a Mountain Home bird, it was a Upper Heyford bird assigned to the MO unit during DS. So it flew with UH tailcodes as you can see here: EF-111 66-0015. If you want, I have a pair of UH tailcodes in 1/72 for you, free of charge of course.

Pete,

How did you come about the UH tailcodes? I've been looking around and can't find anything with them.

ESCI maybe?

Edited by Spectre711
Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...