By Tommy H. Thomason

Saturday, December 24, 2011

Grumman Comes from Behind to Win!

If aerospace competitions were covered on the sports page, that would have been a headline every few years for decades. As a supplier of U.S. Navy fighters, Grumman had a penchant for starting late and then catching up or winning outright, right up until they didn't. At least Northrop kept the name on the letterhead like McDonnell did for Douglas. Unlike Boeing...

Curtiss and Boeing provided all the biplane fighters for the U.S. Navy until a few years after the fledgling Grumman company spread its wings with the FF-1 in 1931. Although both kept trying, neither got a production contract for a Navy monoplane fighter, unless you count the Boeing F-18E/F, which I choose not to.
 Grumman got successive contracts for carrier-based biplane fighters up through the F3F.

Grumman was tardy about the transition to the monoplane fighter. They initially received a contract for their follow-on to the F3F as a biplane, the F4F-1, in accordance with the Navy's need for a backup to the Brewster's monoplane proposal. Grumman was subsequently allowed to change the configuration to a monoplane instead, the F4F-2, but lost the resulting fly-off to the Brewster F2A. Nevertheless, they persevered and redesigned the wings, tail, and engine installation. They then won the second round and delivered a fighter that was at least a match for the Japanese Zero early in World War II. Brewster was relegated to being a second source for Vought's Corsair.

F4F -3

Grumman also lost the fighter competition that Vought won with the Corsair. Their twin-engine F5F might have come in third instead of second if the Allison V-1710 that Bell was using in their FL-1 Aerobonita had a two-stage mechanical supercharger instead of a single stage. (For much, much more, see my XFL-1 monograph) However, Grumman got a follow-on twin-engine contract for the F7F Tigercat that did go into production (and was primarily assigned to the Marine Corps) and a contract for a Wright R-2600-powered Wildcat derivative that became a direct competitor to the F4U, delayed by development and carrier-qualification problems, when re-engined with the P&W R-2800.


Design 50 Study

Grumman was late to jets: its D-71 wasn't selected for the second round of jet fighter development that resulted in the F2H-1, FJ-1, and F6U-1 because it already had a lot of important Navy work, for one thing. They came in second to Douglas in the multi-engine night fighter competition but still got a contract for one. The F9F-1 was becoming an even more distant second so Grumman and the Navy changed the statement of work to a single-engine day fighter, the F9F-2/3 Panther. It was a success, but had to share the decks with the McDonnell Banshee.


Grumman didn't just snatch victory from the jaws of defeat with its fighters. At the end of World War II, they were developing a big propeller-driven torpedo bomber with a jet engine in the aft fuselage for extra speed during the torpedo run and withdrawal. Douglas, however, got the lion's share of the Navy's attack business with its AD Skyraider (Grumman wasn't even second: that was the Martin AM Mauler) but Grumman was able to redirect its AF to be a submarine hunter and killer.
They then repurposed a previous design for a heavily armed twin-engine torpedo bomber, the TB2F, that did not proceed past the mockup stage to be the S2F (S-2), which begat the first true COD, the TF-1 (C-1) and the AEW WF-2 (E-1B). For the history of the latter, see

Grumman was also late to swept-wing jets. The BuAer class desk officer at the time tried to get them to design the F9F-2 with a swept wing but settled for a straight-wing development and a swept-wing study. That spiraled out of control when he left and resulted in a fiasco, the variable-sweep-wing F10F Jaguar, which was cancelled after a year of flight-test disappointments of the only one completed.

However, when the Navy became so desperate for swept-wing performance that they ordered a carrier-based modification of the Air Force's F-86 Sabre, Grumman did what they should have done in the first place: took a Panther fuselage off the production line and put swept wings and a horizontal tail on it.

The resulting F9F-6 Cougar was more carrier suitable than the North American's FJ-2 Fury, which was relegated to Marine Corps. North American put a more powerful engine in the FJ-3 Fury, creating a pretty good carrier-based, albeit short-legged, day fighter but Grumman countered by putting a new wing on the F9F-8 Cougar, which had more endurance.

Sticking with what worked and what the boss in BuAer wanted didn't always work out. The BuAer fighter class deck officer in the early 1950s led both  Grumman and North American astray, asking for a simple day fighter: small, light, maneuverable, inexpensive, and subsonic, i.e. no afterburner. Both complied and got contracts without a formal competition. Grumman at least had the sense to insist on an afterburner for what became its little F11F Tiger. Vought won the formal competition with the F8U Crusader and subsequently, the lion's share of production. The North American FJ-4 got shuffled off to the Marines Corp as a fighter (the Navy bought an attack variant as the FJ-4B to provide Douglas with an incentive to be more responsive on A4D shortcomings as perceived by BuAer engineers) and the F11F wound up performing in airshows with the Blue Angels and training budding fighter pilots.

BuAer contracted with Lockheed to modify the TV-2 (T-33) to a carrier-capable jet pilot trainer, the T2V.
Grumman sold a backup plan to the Navy, a modification to the forward fuselage of the F9F-8T to be a two-seat prototype and demonstrator of an armed (two cannon were retained), carrier-capable, two-seat jet trainer. Unfortunately for Lockheed, it took more time  to develop the SeaStar, in part due to problems with its boundary layer control system for high lift at slow speeds, than Grumman did to get the F9F-8T in front of the Navy, which wound up buying only 150 T2Vs (T-1A) as opposed to 399 F9F-8Ts (TF-9J).

Grumman finally missed the boat completely with the Navy's next fighter program, a fleet air defense fighter armed with Sparrow III missiles. McDonnell caught a break when the Fighter Class Desk hijacked his AH program. It became the F4H Phantom. Grumman immediately submitted an unsolicited proposal for a similar airplane powered by two General Electric J79s but was forced to revise it to have a single engine and compete with Vought's J75-powered derivative of the F8U Crusader. It lost to Vought and then Vought lost to McDonnell.
Note: This is not the F12F. See

Grumman did get a consolation prize at Vought's expense however. Vought won the competition for the follow-on to Grumman's WF-2 (E-1B) for AEW. From Vought's patent application:
Nevertheless, the BuAer production branch chief convinced the Chief of the Bureau of Aeronautics, Rear Admiral James S. Russell, to award the contract to Grumman instead due to industrial base considerations, i.e. Grumman needed the work. The W2F became the E-2, still in production today more than 50 years later.

Grumman got back in the fighter business as a partner to General Dynamics on the F-111 program. In my opinion, the F-111B has been unjustly maligned (see my F-111B monograph) but to be fair to those who have swallowed the Navy's PR whole and regurgitate it, the F-14 was more appropriate to the Navy's needs. Once again, Grumman made a silk purse out of the ear of a "sea pig." (I do hate that nickname.)

Their luck (and reportedly and more importantly their close working relationship with the Navy: see Inside the Iron Works) ran out when the Navy had to choose between derivatives of the F-14D and McDonnell Douglas F-18C/D. The Borg, er Boeing, then absorbed McDonnell Douglas and was finally back in the fighter business with the F-18E/F; Grumman had to sell itself to Northrop.

If Lockheed doesn't get its act together with the F-35C, Boeing may very well become the only U.S. manufacturer of carrier-based fighters.

For more on the development of U.S. Navy jet fighters through the F4H Phantom, see my book U.S. Naval Air Superiority.

Friday, December 16, 2011

A Brief History of Tailhook Design

I have been meaning to expand on my first discussion of the tailhook (HERE). The recent problems with the F-35C's brought that topic up to first on the list. More on that after a brief history of the tailhook.

The first landing of an airplane on a U.S. Navy ship, the cruiser Pennsylvania, was accomplished by a civilian pilot, Eugene Ely, on 18 January 1911—hence 2011 being the Centennial of Naval Aviation. A temporary wooden platform about 134 feet long and 32 feet wide had been added aft of the mainmast, extending aft over the after turret and past the stern of the ship. It angled upward from the fantail, the first 14-foot section at about a 30-degree angle and the remainder, less steeply but still "uphill" so as to help slow the airplane. Two low, wooden guide rails ran fore and aft on the platform about 12 feet apart to help keep the airplane on the deck. Two low canvas screens were strung across the deck about ten feet from its forward end and a high canvas screen was hung from the mast to the forward end of the platform. These foreshadowed the barriers and barricade respectively used on axial deck carriers to protect the crew forward and hopefully the pilot in the event that the airplane overran the landing area. Canvas was also slung outboard on both sides of the forward two thirds of the landing area to keep the airplane from falling into the sea if it came off the platform.

The arresting gear consisted of 22 pairs of 50-lb sandbags, each connected by a rope and placed outboard of the guide rails, which helped hold the rope above the deck. Each pair was three feet apart going up the deck. Three steel hooks were attached to the longitudinal frame of the landing gear of Ely's Curtiss pusher. These were intended to snag the ropes, with the bags then dragging the airplane to a stop. (The weight of each bag was carefully measured to insure that they were equal in order to reduce the likelihood of a bag having more drag than its partner and pulling the airplane to the side.)

The arresting system worked exactly as planned. The heritage of today's system is clearly evident.

It took a few more years of aircraft development before the U.S. Navy was ready to operate land planes from an actual aircraft carrier. The tailhook was instrumental to the success of the enterprise and a closely held innovation.

The first arresting-gear systems incorporated longitudinal wires as well as the cross-deck pendants. These were engaged by two-pronged hooks hanging down from the spreader bar between the main landing gear wheels. The purpose was to keep the airplanes from slewing off the deck or bouncing but they soon proved to be more trouble than they were worth and discarded.
A successful tailhook design was not as easy as it might seem.  The first requirement was structural: the attachment had to withstand a load two or three times greater than the weight of the airplane. Most installations were on the bottom of the aft fuselage, with the hook pivoting down from, in effect, the keel of the airplane ahead of the tail wheel.  This was mechanically and structurally simple, but meant that the retarding load of the hook ran below the aircraft center of gravity, causing the nose to pitch down during the arrestment to eliminate the resulting moment. This Grumman SF-1 tailhook is typical:
"Tail rise" with a low-mounted tailhook was a problem, as in this Bell Aircraft XFL-1 arrested landing, with the prop dangerously close to pecking the deck:

Grumman moved on to a "stinger" installation, in which the tailhook extended directly aft from the end of the tail fuselage. This was more complicated mechanically and structurally, but the retardation force was acting higher on the airframe, causing less of a pitch-down moment when the hook engaged a wire.

Vought originally utilized the stinger-type tailhook on its XF4U-1 Corsair but relocated it to the tail landing gear, still somewhat higher relative to the cg than the usual installation:
A beef up proved to be in order:

The Ryan FR-1 had a piston engine in the nose and a jet engine in the tail. Access to the jet engine was provided by removal of the aft fuselage. In order to avoid high loads on the attachment of the aft fuselage, the tail hook was attached forward  of that joint, probably as far forward as ever done.

Tail rise wasn't expected to be a problem because the airplane had a nose landing gear that protected the propeller. However, the length of the hook resulted in inflight engagements and its location, as would be expected, a nose-down pitching moment.
Loads on the nose wheel and landing gear attach structure proved to be excessive.

For more on the FR-1, en fran├žais,  see:

For its F5U, Vought designed a tailhook installation that was located above the "fuselage" (probably because one located on the belly would have resulted in excessive tail rise, although Vought engineers had a penchant for gadgetry).

 Grumman continued with the stinger tailhook through its F9F series. It continued to be satisfactory, although in one early test of the Panther, the arrestment pulled the removable aft fuselage off. This is a proof load test of the F9F-5 installation.
To simplify the installation, the Panther/Cougar hook was not retracted after landing but simply raised to the "stinger" position so the airplane could be taxied over the arresting wires, barriers, and barricade. It was then reloaded manually.

Grumman greatly simplified the mechanics and structure of the aft mounted hook in the F11F. It was stowed upside down and backwards so it simply dropped down from the extreme aft end of the fuselage.

After landing, the pilot raised it to the stinger position like the F9F's:
(The sailor was out there to pull the arresting cable off the hook if it did not fall off of its own accord.)

The F11F hook was double-jointed so it could be reloaded after the airplane had taxied forward and parked.This installation was innovative* but not imitated. For one thing, if when making a field landing the pilot decided after touchdown to drop the hook to engage the emergency arresting gear, it probably wouldn't rotate into position behind the aircraft.

Concerned with the nose-down pitching moment of even a stinger location of the tailhook for the F7U-1, Vought created a double-jointed installation in which the hook was attached at the top of the fuselage:
The design proved to be overly complicated and heavy (it also had a device that ejected the cross-deck pendant from the throat of the hook), so Vought reverted to a conventional belly mounting for the F7U-3. For more on the F7U-1 tail hook, click HERE.

Tail rise problems caused by low-hook attach points were dealt with by beefing up what broke, for example the F8U nose wheel.

In addition to structural and pitching moment concerns dealt with during predesign, the engineers also had to fine tune hook design and operation during development test and Navy evaluation. Hook damping was a cut and try process. Too little damping and the hook would skip, sometimes missing all the wires. Too much was hard on the aircraft structure, not to mention the deck. Hook length might also require experimentation in conjunction with damping changes. Too short a hook and long touchdowns risked missing all the wires; too long and an inflight engagement and overly hard landing might result. Trail angle was another; after problems were encountered in field and at-sea trials, the F4H tailhook operation was modified so that the trail angle decreased after main gear touchdown.

Which brings us to the F-35C. The first roll-in arrestment attempts at Lakehurst in early 2011 were disappointing to say the least: zero traps in eight tries. According to the recently published Quick Look Review of the Joint Strike Fighter Program:

"Root cause analysis identified three key AHS (Arresting Hook System) design issues: (1) the aircraft geometry has a relatively short distance between the aircraft’s main landing gear tires and tailhook point (when lowered), (2) tailhook point design was overemphasized for cable shredding (n.b. the tendency for the hook point to dig into and damage the cable) features versus ability to scoop low positioned cables, and (3) tailhook hold-down damper performance is ineffective to support damping of small bounces relative to runway/deck surface profiles."

This picture provides an approximation of the height of the hook above the deck relative to the main landing gear with the oleos fully extended with the F-35C at my guess at its angle of attack on approach. Note that the hook point is not below the wheels as it is on most other carrier-based airplanes and much closer to the wheels horizontally.

Contrast this hook-point position relative to the wheels both vertically and longitudinally with that of an F-18F Super Hornet's:
My guess is that the relative shortness of the hook is related to its closeness to the wheels, since an inflight engagement of a hook located so far forward relative to the wheels would generate a greater nose-down pitching moment than a hook located farther aft. Inflight engagement incidents would be minimized by having a short hook. However, the hook point's closeness to the wheels longitudinally appears to have resulted in an unanticipated problem that can be best understood by looking at this excellent summary of what happens when the wheels tramp down the arresting wire, also known as the cross-deck pendant:

Basically, the landing gear wheels mash down (trample is the term of art used in the report) the cross-deck pendant and it doesn't rebound high enough and quickly enough so that the current hook point (which was based on the proven F-18 design) can get under it. The proposed fixes are to revise the shape of the hook point and modify the damping of the hook so that it is less likely to skip over all the wires.
These changes will probably be sufficient so that more onerous changes to the hook installation are not required. (For a June 2014 update, see; the redesign was subsequently successfully qualified at sea). However, it once again illustrates the degree of difficulty in achieving the desired result on the first try and the necessity to plan time for redesign and retest of even the most basic and well known requirement.

* The reversed F11F tailhook was, however, not the first such installation. The Brits put a tailhook on an Airacobra I to evaluate arrestment of an airplane with a nose landing gear. It pivoted from a fitting just in front of the tail post and was manually stowed upside down and backwards. I'm not sure whether this unusual installation was because of the need to find a solid piece of structure to attach the hook to or to minimize the nose-down pitch on engagement. Maybe both. Captain Eric Brown made an unauthorized deck landing with it on Pretoria Castle on 4 April 1945 at the conclusion of a series of hook-up passes to evaluate flexible-deck approaches. By his own admission, he declared an emergency without cause in order to be get permission to land aboard and make the first landing of a tricycle aircraft on a British aircraft carrier. (The U.S. Navy had already done so, one of the few times that the Brits came in second on aircraft carrier milestones.)
The hook had to be relatively long because of the tricycle landing gear (see the FR-1 example above).

Sunday, November 13, 2011

Scooter! Stuff

My latest book, Scooter!, has yet to get many reviews on line or in periodicals (actually only one so far, from an on-line friend) but what I really appreciate are the complimentary and congratulatory emails from individuals, particularly those who bring something more to the story.

For example, Larry Blumenthal provided the following, scanned from FDR's 1960 cruise book picture of tied-down A4D-2s with protective covers in place, including specially created GSE for the Tinkertoy:

T.J. (Jeff) Brown provided a summary assessment of the A-4 versus the A-7 for the book, but he had more to add:

There is one thing that I forgot to mention in my submission that you might include, should you ever do a reprint. The A-4F nose struts that included the nosewheel steering (NWS) feature did not hold up well under the punishment of repeated carrier landings and leaked hydraulic fluid profusely. When a strut failed, there was no indication to the pilot except his repeated pushes on the stick button were doing nothing, and this detraction with his head down in the cockpit sometimes caused late brake applications when exiting the arresting gear. This caused great concern to all who might be in charge of flight operations, namely the Air Boss and the Skipper, especially if foul-deck waveoffs resulted. The nosewheel steering was also not accurate enough to keep from sliding off the side of the "turtle back" on the catapult (that held the bridle) that the airplane had to go up and over, either, and this operation had to be done with a Blue Shirt on the deck with a nosewheel tiller bar. This was dangerous for the Blue Shirt if the a/c had an operative nosewheel steering, since if it were engaged with the tiller bar connected, it could cause anything from broken bones to his being tossed over the side. For these reasons, most A-4F squadrons (as we did in Air Wing 21) replaced the Foxtrot nose struts with Echo struts. Problem solved, and we operated as had A-4 units since time immemorial: take the trap at 100%; on the pullback, simultaneously pull the power to idle, retract the speedbrakes, raise the flaps and hit the left brake, causing the aircraft to cock to the right since it was being pulled aft by the arresting cable; then smartly taxi out of the gear, pleasing all hands.

In the Training Command, it would not have been practical to do this with the T-birds, since carrier landings were few and some of the students needed all the help they could get anyway. Instead, the LSOs just put the Fear of God into them NOT to touch the NWS while on the ship and the tiller bar was connected (hand signal: index finger placed alongside the nose, and clearly acknowledged by the pilot).

Us Old Salts endured the inconvenience of not having NWS on the beach, since it would be a major job for Maintenance to change the struts all out and back on a short turnaround, which we usually had. All this taken into account, the A-7 always had NWS, since there was no turtle-back on the nose-tow cat system, and the NWS was much more accurate and easy to steer onto the nose-tow box. This is my story and I'm stickin' to it! :-)

Jack Anderson provided more color as well from his experience:

Reading (Scooter!) brought back a lot of memories that had been dormant about flying the the first A4D-1's. We were so pleased with them after flying F7U-3s that we just enjoyed the simplicity, reliability and the performance of them. I had forgotten about the engine problems and the mandatory safety inspections. One of those occurred while we were at sea doing our first carquals.

In a clean configuration we could exceed Mach one in a 30-degree dive. It performed well up to 35,000 ft. As it passed through 40,000 ft it was getting very sensitive. I once nursed one to 49,500 ft but it took a lot of work and required a step climb from about 43,000 ft. One my squadron mates said he made it to 50,000 ft by doing the same technique. We could out dogfight anything at Cecil Field except the F8U-1. The roll rate was spectacular and the throttle response was very good. The aerodynamic slats could flip you upside down in a high-altitude dogfight especially above 40,000 ft if you pulled too hard in the turn. I don't remember too much trouble with fuel shift in the wings on the dash 1, probably because of our nuke delivery mission and the requirement for a lot of low level nav practice.

Walt Fink, another contributor to Scooter!, and a long-time acquaintance, had his memory jogged as well:

The photo of the EPI on page 63 brought back a couple memories. The little windows for fuel pressure and oil pressure were flip-flop things with two readings (when powered), NORM and OUT, or something like that. We discovered, after a couple of unnecessary aborts by some of our more senior aviators, that the oil pressure flip-flop would show OUT when in reality the oil pressure was high. Apparently the circuitry inside it just recognized the normal range and anything above or below it defaulted to OUT. Since the J-65 was built around an oil leak anyhow, that did result in a couple moments of panic and high pucker factor.

That little quirk caused the Navy to retrofit the airplanes with what we called a "nickel gauge" for direct oil pressure reading. So-called because it was the tiniest little gauge in the airplane, only about the size of a nickel.

Jim Rotramel, my go-to guy for external stores and F-111 stuff, took the time to go through the book and provide corrections and additions to the captions for pictures that I hadn't shown him before going to press:

Pg 130: Mk 81/Mk 14 Snake Eyes, not Mk 82s. The Scooter was so small that Mk 82s looked enormous on it. The key thing to look for was that you couldn't carry a fully loaded MER/TER of Mk 82s, while you could with Mk 81s.

Pg 137: Small photo is not an M117 (wrong shape/fin). Outboard appears to be Mk 82/Mk 15 SE, inboard is probably AN-M65 1,000-lb bomb. (Large photo is Mk 81/Mk 14 Snake Eyes again.)

Pg 140: Bottom photo is CBU-55 FAE, not Napalm.

Pg 141: Mk 81/Mk 14 Snake Eye

Pg 145: No "-" in M118 (or any other M series bomb, just M and the number with no space or dash).

Pg 150: the outboard pylons aren't loaded with CBU (no fins, no fuzes). They appear to be 19-tube rocket pods, probably LAU-61s, which were 10 in. longer than LAU-3s.

Pg 151: 221 has Mk 81/Mk 14Snake Eyes. 227 probably has an AGM-12E Standoff Cluster Missile loaded with BLU-62 and 63s.

Pg 169: Nearest A-4 carrying a TP Mk 82 and NTP Mk 83

Pg 175: Nice shot of a Mk 83 LGB.

Pablo Calcaterra sent me this picture of an Argentine pilot attacking HMS Glasgow on 12 May 1982. The picture was taken from the deck of HMS Brilliant and is indicative of the height of the A-4 on the run-in:

A better reproduction of Captain Carballo's and Lt Rinke's attack on Broadsword on 25 May and a painting by Carlos A. Garcia are provided here:

Tuesday, October 25, 2011

Douglas F6D Missileer

One of the Navy's ongoing concerns is defense of its ships from attacks by aircraft and/or missiles. The Chinese anti-ship missile threat is only the latest. In the 1950s, it was long-range, high-performance missiles launched from Soviet bombers. The first solution was the Sparrow air-to-air missile carried by fighters whose development had begun in the late 1940s. The F4H Phantom was the first Navy fighter specifically designed for the mission and was also armed with the Sparrow. However, the Navy continued to fret about a combination of faster bombers and longer range air-to-surface missiles that the Phantom/Sparrow approach was not capable of adequately addressing.

The solution from operational analyses was the Missileer concept. The Operational Requirement was issued on 11 July 1955. The "fighter" would simply be a subsonic platform that loitered out on a station on the threat axis,  lugging a huge, long-range radar and up to eight very long-range air-to-air  missiles. The missile's range requirement necessitated that it be provided with its own radar for terminal guidance. That and fuel required range that it was a very big missile indeed. It was to be called Eagle.

Work on the missile and engine design definition began first, because they would take much more time to develop and qualify than the airframe. The Bendix Corporation was selected as the prime contractor for the Eagle, including the airborne radar and missile control system, in December 1958. Grumman (airframe and flight test), Westinghouse (aircraft radar), Litton (tactical computer), Sanders (missile active pulse doppler seeker), and Aerojet (propulsion) were subcontractors.

 The missile with its booster was 16-feet long. Together, they weighed 1,288 lbs, including the missile's on-board radar and 110-lb warhead. The maximum range from launch to intercept was 100 nautical miles against a bomber flying at 60,000 feet and Mach 2.

The Pratt & Whitney TF30 engine was one of the first turbofan-type engines, desired for its benefit on endurance. It was based on an engine that Pratt was developing for airlines.

The invitation to bid on the aircraft wasn't requested until 11 December 1959. Bids were received at the end of February from Chance Vought, Douglas, Grumman, McDonnell, and North America. Douglas was selected. The decision was announced on 21 July 1960.

The Navy's press release was explicit about the F6D's role: "The EAGLE-MISSILEER weapon system employs the concept of building long range and high performance into the missile, rather than into the launching aircraft." The 50,000-lb takeoff-gross-weight airplane was to be capable of operating from Essex-class carriers and loiter on station for four hours at 35,000 feet.

The bulbous nose was necessary to accommodate the Westinghouse AN/APQ-81 radar dish, which was five feet in diameter. (Big as the radar was, the missile's maximum range could only be utilized with the Bendix home-on-jam option.) The two-man crew sat side-by-side, surrounded by avionics. The normal missile load was six, all carried under the wings. Two additional missiles could be carried under the fuselage, increasing the takeoff gross weight by 4,800 lbs.

Unfortunately, the incoming Secretary of Defense, Robert McNamara, decided that it would be cost effective to combine two nascent "fighter" programs, the Navy's carrier-based, subsonic, 35,000-ft loiter Missileer and the Air Force's land-based, supersonic, tree-top ingress, nuclear-strike TFX. Strictly speaking, neither was a fighter and what's worse, two more different tactical airplane requirements would be difficult to imagine. The F6D program was formally terminated in April 1961 (it had been on hold since December 1960 awaiting the Kennedy administration's DoD programs review); Hughes took over the development of the radar/missile program, which was appropriately renamed Phoenix.

The F-111 train wreck, particularly given the Navy's outrage at being subservient to Air Force program management and subsequent passive-aggressive cooperation, was inevitable. For more on the F-111B program history, buy my F-111B monograph HERE.

Saturday, October 15, 2011

A Designation Story

The Grumman WF-2 (E-1B) is an interesting example of the Navy designation system and a little known false start for an iconic Navy airplane, the "Stoof with a roof". For starters, what was the WF-1? And why is there no E-1A?

The basic designation was W for Airborne Early Warning (AEW) and F for Grumman. Up until then, W was a suffix, not a prime mission designation, as in TBM-3W. It indicated that an existing airplane type, the third modification (3) of the first Torpedo Bomber (TB) to be built by Eastern Aircraft (M), had been modified for the AEW mission (W) by substituting a large radar and its cover for the bomb bay. (The 3 actually reflected that it was the third modification of the TBF, since the airplane was originally designed, developed, and produced by Grumman as its first torpedo bomber, with Eastern Aircraft, a division of General Motors, taking over its production from Grumman.)

The TBF-3W was followed by a series of AD Skyraiders, like the AD-3W shown here, modified similarly to carry the APS-20 radar aloft.

As an aside, the similarly configured Grumman AF-2W was used for AntiSubmarine Warfare (ASW), not AEW, with the radar being used to detect a surfaced submarine or more likely, its snorkel. It was paired as a hunter with the AF-2S, the killer half of an ASW team, which was equipped and armed to localize and sink the submarine.

Grumman was in the process of replacing the AF-2W and AF-2S with the S2F, a twin-engine airplane that combined the mission equipment and armament of those two airplanes into one. The S for ASW was now a prefix as W would be for AEW.

The S2F's small radar that was housed in a retractable "dustbin" dome under the aft fuselage was optimized for surface surveillance, not AEW. Grumman therefore proposed a minimally modified S2F airframe for the AEW role, with the APS-20 radar and dome mounted above the cockpit rather than under the fuselage, which would have required a much longer landing gear and therefore required a folding vertical fin/rudder to meet the hangar-height limitation. The forward location of the radome meant that the existing S2F wing-fold system that overlapped the fuselage could be retained. The only change required to the airframe therefore was a slightly deeper fuselage with an aft cabin door and the addition of finlets to the horizontal stabilizer to compensate for the sail area forward that was added by the radar dome.

The Navy ordered two prototypes as the WF-1 and assigned them BuNos 133043 and 133044. Grumman accomplished wind tunnel tests and a fuselage mockup before the WF-1 effort was terminated, probably due to budget priorities and the availability of the AD-5W.
Vought got a contract for the WU-1 and two Bureau Numbers were assigned, 133780/1, but it was also cancelled. (Note the wing-fold arrangement used to accommodate the radar dome.)

Eventually, however, the Navy felt the need to use a bigger, better radar for the AEW mission. The existence of and commonality with the TF-1 Carrier on Board Delivery (COD) variant of the S2F, which had been proposed at the same time as the WF-1, was no doubt one of the deciding factors in the decision to award the program to Grumman.

Incidentally, the COD version of the S2F was designated as T for Trainer rather that something like S2F-1R like the TBM-3R because the majority of the missions it was originally intended to be used for were training. See

The resulting WF-2 bore only a family resemblance to the S2F and TF, however. The radar was now mounted above the fuselage, which required the substitution of an H-tail and a reversion to the sto-wing fold system that was a Grumman invention. The capacious TF-1 fuselage was lengthened ahead of the wing, probably to maintain the required center of gravity. Because of uncertainty about the aerodynamic implications of the huge radome, TF BuNo 136792 was modified, except for the fuselage extension and sto-wing, for initial flight test with the radome. (Note the feathered engine.)

In the following picture, the aerodynamic prototype is flying in formation with a production WF-2. Note the different location of the propeller strip versus the pilot's side window, which indicates where the forward fuselage was extended forward.

The sto-wing necessitated the use of a free-swiveling tail wheel because of the aft shift in the center of gravity when the wings were folded.

I can't confirm that the prototype was designated the XTF-1W as Wikipedia currently states. It doesn't seem likely and Larry Webster confirmed that its history card only states TF-1 and C-1A. A very early (but not dated) Grumman S2F brochure describes the AEW and the COD versions as the WF-1and TF-1 respectively. I've also read that the aerodynamic prototype was designated WF-1, with the production airplane therefore being the WF-2. That's definitely bogus.

After Grumman flight test of the aerodynamic prototype, the radome was removed, the TF/C-1 interior installed, and the aircraft utilized as a transport by NAS Quonset Point, RI.

According to Angelo Romano, there were three other topless Tracers that were used for pilot training since field carrier landings and real carrier landings, not to mention catapult launches, were hard on the electronics, not to mention that the radar and guys in back were unnecessary for that requirement.

When Navy aircraft designations were changed in 1962 to be consistent with the Air Force system, the WF-2 became the E-1B. Although it could have been argued that there was no need to reflect a universe in which the WF-1 had not been cancelled, the group in charge of redesignation chose to do so.

For a multi-part history of U.S. Navy AEW by a naval aviator, Steeljaw Scribe, who has forgotten more about the subject than I will ever know, see: