Wednesday, December 29, 2010

The Coast Guard was responsible for helicopter development during World War II. One of their concerns was the rescue of the crew from a ship that had been sunk by German submarines off the U.S. east coast. Existing helicopters were too small to carry more than one or two rescuees. The Coast Guard wanted one that could carry eight in addition to a crew of two.

At the time, based on experience with autogiros, it was believed that the empty weight of a single rotor helicopter as a percentage of gross weight would increase with rotor diameter so quickly that large single rotor helicopters would have no payload capability. Frank Piasecki, a young engineer who had just flown his first helicopter, convinced the Coast Guard and the Navy that the answer was a tandem-rotor helicopter. He got a contract for a full-scale demonstrator in January 1944.

The first flight of what was designated the XHRP-X, Bureau Number (BuNo) 37968, was made in March 1945, little more than a year after go-ahead. It was powered by a 450-hp Continental R-975 radial engine and subsequently referred to as the Dogship at Piasecki. Unique features in addition to the tandem rotors were the castering wheels intended to minimize side loads in a touchdown with sideward motion; the pilot sitting aft of the front pylon (the copilot sat directly behind him); and the bottom of the forward fuselage being "skinned" with clear plexiglass panels for downward vision. Unlike subsequent tandem-rotor helicopters, the rotors did not overlap.

The XHRP-X was featured in this late 1945 newsreel as the "World's Largest Helicopter!". Following its successful development and demonstration, Piasecki received approval to build a Static-Dynamic Test Article for qualification testing of the drive and rotor systems. It did not receive a BuNo and the fuselage was never covered with fabric. It was powered by a 600-hp engine P&W R-1340 engine.

The XHRP-1, BuNo 37969, was also authorized.

Its first flight was accomplished in March 1947. It initially had a aft fuselage without as much side area as the XHRP-X, possibly to
reduce weight. Stability problems resulted in the addition of a small
horizontal stabilizer and vertical fins.

Piasecki also received a production order for 10 HRP-1s in June 1946 and another 10 in April 1947.

The first production HRP-1 flew in September 1947 and was delivered later that year. The last of the total order of 20 was delivered in 1949. These were initially used by the Marine Corps to develop tactics for vertical assault and by the Coast Guard for its ongoing helicopter search and rescue development.

Five of the HRPs initially assigned to the Marines Corps were then used by the Navy for the development of dipping sonar and airborne minesweeping. The fabric was taken off to reduce weight (testing was done off Key West, Florida) and flotation bags were added so the helicopter could be recovered if its engine quit over the water.

Eventually a portion of the small fleet was acquired by civil operators from military surplus.

The Dogship is currently stored at the Smithsonian's Paul E. Garber
Preservation, Restoration, and Storage Facility located at Silver Hill,
Maryland.

The first production HRP-1, BuNo 111809, that was at the New England Air Museum is currently being restored at Piasecki Aircraft Corporation in Essington, Pennsylvania for eventual display at the American Helicopter Museum in West Chester, Pennsylvania.

The HRP-2 utilized the same drive train and engine as the HRP-1 in an all-metal fuselage. The pilot and copilot now set side by side ahead of the front rotor mast. First flight was on 10 November 1949. Only five were produced. They were initially used by the Marines along with the HRP-1s and then all of the -2s were assigned to the Coast Guard. It was clear that they were underpowered with the same 600-hp engine installed in the HRP-1.

At least one surplus HRP-2 was procured and operated by Rick Helicopters, then the largest civil operator of rotorcraft, in the 1950s.

The Air Force and subsequently the Army recognized the value of the basic design for their emerging helicopter missions, however, and ordered modified versions of the HRP-2 as the H-21 with more powerful Wright engines with up to 1,425 horsepower.

The FJ-2 and -3 Furies had a retractable barrier pickup device located aft of the nose gear wheel well. This insured that the activated barrier cable did not fall back down before it engaged the airplane's main landing gear struts. (It was subsequently removed from at least the -3s when the angled deck eliminated the need for the Davis barrier.)

There is a similar, albeit non-retractable, device on the belly of the Grumman S2F. I had assumed that it performed the same function, but it turns out that it corrected a different problem related to the Davis barrier function.

The initial S2F Davis barrier qualification at Naval Air Material Center (NAMC) had actually been accomplished with an F7F that had been modified with tubing shaped to simulate the S2F-1 belly. Surplus F7Fs were plentiful and surplus S2Fs, not. Moreover, in the interest of minimizing cost, nose-high, off-center, and lifter strap run-down by a dual nose wheel landing gear (the F7F had a single nose wheel) were not evaluated.

In early 1954, during one of the first S2F squadron carrier qualification periods aboard Siboney (CVE-112), a pilot failed to lower his tail hook, which wasn’t noticed by anyone on the LSO platform as it should have been. This guaranteed a trip into the barriers. The airplane also engaged nose high, which didn’t help matters. Things went badly after that. The cables didn't engage the left main landing gear as they should have. The nose gear failed when the airplane pitched down and the right wing was torn off when the airplane was yanked violently around by the engagement of only one landing gear strut by the barrier cable.

S2F-1 BuNo 129146 was therefore assigned to NAMC to provide a more representative test article for a series of more comprehensive tests. It was catapulted, unmanned, into a Davis barrier at speeds from 35 to 70 knots in five-knot increments. Normal, nose-high, and nose-low engagements were made as well as at 17 feet off of centerline. A total of 129 shots were accomplished between 30 May and 23 November 1954 to develop a configuration that provided a higher likelihood of a benign barrier encounter.

One of the problems encountered was that on a nose gear with two wheels, a lifter strap could conceivably be caught between them, preventing the lifting of the barrier cables. The S2F also had a relatively short wheelbase and a wide tread, which meant the cable might not always rise high enough across the width of the tread in time to engage both landing gear struts. If only one strut was engaged, a violent yaw resulted as it had in the Siboney incident.

S2F changes established during the testing included the addition of four pairs of small detents on a strengthened nose wheel door so the actuator strap would not slip down, affecting the rise of the barrier cable. The nose gear strut torque arms were modified and the tow fitting between the wheels was extended forward to reduce the likelihood that a lifter strap would be trapped between the nose wheels. A slanted fairing was also added ahead of the catapult hook so there was less likelihood that the cable would be deflected downward and not engage the main gear struts.

Most importantly, a cable scoop, the “Fosdick,” was added on the bottom of the fuselage. Unlike the one on the FJ-2/3, it was not just there to keep the barrier cable up off the deck. It was primarily there to reduce the drag loads of the barrier cables on the landing gear and the violent yaw that would result if only one main landing gear was engaged by the cables, assuming that the cable scoop was engaged as well.

Here is an early S2F, flying with one engine shut down and the propeller feathered. Note that the only protuberances on the belly ahead of the retractable radar dome are two radio antennas and the catapult hook.

This is the belly of the S2F after the addition of the detents on the nose gear door, the fairing ahead of the catapult hook, and the cable scoop.

The existing main landing gear "scoops" were also modified to be more effective at diverting the cables onto the struts.

Steve Ginter is working on an S2F-1 monograph for publication in his Naval Fighters series.

Wednesday, December 8, 2010

I rediscovered an interesting report in the Vought archives this week, Notes on Comparison of Carrier and Land-based Fighter Airplanes Incorporating Folding Wingtips dated 21 March 1952 and authored by John H. Quinn Jr. I had previously copied it from the George Spangenberg collection in the National Archives but hadn't taken the time to examine it closely.

The folding wingtips aspect of it was only of passing interest to me because it was never incorporated on a produced design, at least not for the original purpose, which was to provide a high aspect ratio wing for cruise flight with the wingtips lowered and a low aspect ratio wing for combat maneuvering with the wing tips raised as shown in the following artists concept.

Vought submitted an unsolicited informal proposal to the Navy for the V-381 which incorporated the feature in September 1952. The Navy passed, having already given Douglas a contract for the A4D Skyhawk.

The report, however, addressed a more pressing issue, which was the Navy's need to achieve performance parity with land-based jet fighters. Three predesigns were accomplished for the study: a carrier-based airplane designed to the existing limitations, a land-based airplane, and a carrier-based airplane taking advantage of relaxation of the existing limitations.

"It was assumed the airplanes were powered with a single J67W-1 engine... and were designed to combat radius of 600 nautical miles, approximately." The J67 was the designation of the Curtiss-Wright license-built Bristol Aero Engines Olympus; it was projected to provide 21,500 lbs of thrust. The mission radius was, of course, selected to highlight the cruise benefit of the folding wingtip feature.

At the time, carrier airplanes had to be designed for launch from the existing hydraulic catapults and recovery using the Mk 7 arresting gear; tactical airplanes, as opposed to the big nuclear bombers, could not be any longer than 56 feet (for straight spotting on Essex-class elevators) or taller than 17 feet and more than 24.4* feet wide when folded. (The folded height and width were Essex-class hangar deck constraints.)

Although there was no dimensional restriction on the land-based airplane, it was required to operate from a 5,000-ft runway with the takeoff roll not to exceed 3,000 feet. (Sounds short, but according to the F-100A Standard Aircraft Characteristics chart, it had a ground roll of 2,970 feet at its maximum gross weight of 29,000 lbs.) It was also required to have a combat ceiling of 55,000 feet as another constraint on wing loading. (The F-100A was bit short on that and woefully short of the range, not having folding wingtips.)

Because of the lift and size limitations imposed by the existing carrier-basing ground rules, the first carrier-based design was predicted to be 200 knots slower than the land-based one at 35,000 feet, about Mach 1.7 and 2.0 respectively. Analysis indicated that only two of the carrier-basing imposed constraints, takeoff wing loading and overall length, were the cause of the difference. The newly invented steam catapult was projected to eliminate the wing loading penalty; diagonal spotting was suggested to allow for more length and provide a better fineness ratio for less drag. The result was parity of performance with land-based airplanes. (It was recognized that the longer airplane would result in fewer being accommodated aboard, a shortcoming for carrier-basing.)

Navy Length and Wing Area Constrained

Air Force Land-Based

Navy Diagonal Spotting and High Wing Loading

As it happened, the F8U-1 achieved parity (even superiority) with the F-100, also powered by the P&W J57, based on the benefit of the steam catapult alone. (It was just within the 56-foot length limit.) The F8U-3 exceeded 56 feet in length by a little less than three feet but it had Mach 2 performance in part due to the rediscovery of the area rule by Whitcomb in 1952; it too had performance parity with the land-based J75-powered fighters.

*The maximum folded width was in the process of being increased to 27.5 feet, in part perhaps to allow the Douglas A4D Skyhawk to go below without having to fold its wings.

Friday, November 19, 2010

This assessment is based almost entirely on a 1/50th scale model in the Grumman History Archives on Long Island.

The empty weight proposed for the F-111 was even more optimistic than usual in winner-take-all paper competitions. As is customary, Grumman and General Dynamics initiated a two-pronged F-111B weight reduction study effort, the Super Weight Improvement Program and the Colossal Weight Improvement Program, even before first flight. Roughly speaking, the ground rules for the SWIP were to reduce the weight but not significantly depart from the design and mission requirements. The CWIP allowed a great deal more flexibility, basically tossing out anything imposed only by the Air Force low-altitude strike mission and preferences like the crew escape capsule.

For the CWIP configuration, Grumman engineers deleted the bomb bay and escape capsule and reduced the volume required for the main landing gear by not allowing for the large low-flotation tires required for operation from unprepared fields. That enabled them to shorten the forward fuselage by about five feet. The shorter forward fuselage presumably allowed them to delete the ventral fins, with the original vertical fin now adequate for directional stability even at high angles of attack. However, the horizontal stabilizers were slightly increased in size, presumably for improved low-speed handling qualities for the carrier approach.

All six Phoenix missiles were now carried on the fuselage, four semi-submerged and two on short pylons on the lower sides of the fuselage. This arrangement eliminated both the wing pylons and swivel mechanisms required to keep the missiles aligned when the wings were swept. I haven't yet found any information on the main landing gear configuration change required by putting two missiles on the centerline of the belly, but presumably it resembled that on either the Grumman F11F Tiger or the North American A3J Vigilante.

The center fuselage with the engine inlets and wing mounting structure were basically unchanged except for the main landing gear bay. The wings were also unchanged. The engines appear to have been moved forward by about two feet to restore the center of gravity after the nose was shortened.

Although the canopy appears to be bulged upwards, my preliminary assessment is that the visibility over the nose was no better than it was on the original F-111B, which was determined to be unsatisfactory. However, the lower weight would have resulted in a lower angle of attack for the same lift, possibly providing the same over-the-nose visibility improvement as the raised cockpit that was eventually required.

The government program team elected to incorporate most if not all of the SWIP changes in the 12th F-111A and the 4th F-111B. The CWIP specification changes stayed on the drawing board until Grumman was able to apply them to what became the F-14.

Thursday, November 4, 2010

“One if by land, and two if by sea.” That line from Longfellow’s poem commemorating Paul Revere’s famous ride in 1775 was one of the justifications used by the Navy in 1976 to select the twin-engine McDonnell F-18 over the single-engine F-16 for its VFAX program. Some viewed it as dissembling on the Navy's part since the desirability, much less necessity, for twin-engine carrier-based aircraft had not been very evident up until then. In fact, although single-engine airplanes were in the minority in the air wings at the time, that was a relatively recent change from past practice. A year earlier there was still an air wing aboard Hancock (CV-19) that was almost entirely comprised of single-engine aircraft. Now, of course, there are no single-engine airplanes in the carrier air wings.

The major benefit of twins, the capability to return to base after an engine failure, was initially problematic for a carrier-based airplane. The pilots approached power-on in level flight at the lowest safe speed and minimum altitude, cutting the engine just when the airplane would settle onto the deck. This was essentially the same technique used for a short-field landing ashore, where it assured a touchdown very close to the approach end of the runway, allowing the maximum distance for stopping.

The pilot of a twin-engine propeller-driven airplane with one engine inoperative had to take into account the minimum control speed in that situation. Since the engines were almost always placed out on the wing, when one failed the other produced a significant turning moment which had to be counteracted by the rudder. Since rudder effectiveness varied with airspeed, at some point the pilot could no longer stop the airplane from turning with the engine at full power. What’s worse, the turning generated a roll because of the difference in the lift on the wing on the outside of the turn versus the one moving slower on the inside. Since the ailerons also lost effectiveness with decreasing airspeed, a loss of control in roll would result as well if the engine power was not immediately reduced.

Unfortunately, the minimum-control speed at the power required to climb with the gear and flaps down was almost certainly higher than the required approach speed dictated by arresting gear, which made a successful wave-off an iffy proposition.

The tyranny of minimum-control speed was also imposed on an airplane taking off, but it was more draconian at sea than ashore. If the pilot taking off from a runway lost an engine while still below minimum-control speed, he would simply close the throttle on the good engine and reject the takeoff. The outcome varied with the length of the runway and if it came to that, the landscape beyond its end, but was rarely as dire as faced by the pilot of an airplane less than one hundred feet above the sea after being launched from an aircraft carrier at less than the minimum-control speed with full power on the operating engine. If he reduced power on it engine to maintain control, he almost certainly would not have enough for level flight, much less to climb or accelerate to a speed at which he could use all the power available.

Having a second engine was therefore not as good a deal for a pilot flying from an aircraft carrier as it was for one flying from an airport. Although it enabled one to divert to a land base or get back to friendly ships and ditch if an engine was lost in flight, it doubled the risk of an engine failure during a critical, albeit short, time during takeoff and landing. Twin-engine airplanes also tended to be bigger than singles whereas compactness was a virtue on an aircraft carrier.

Nevertheless, there were benefits beyond the ability to continue flight after an engine failure. The easy way to improve the performance of fighter airplanes is to incorporate more powerful engines in new or existing designs. Increasing power in piston engines basically meant adding more and/or bigger cylinders and supercharging. By the late 1930s, the engine manufacturers were beginning to approach the limits of existing technology and incremental horsepower increases were resulting in increasingly smaller increases in speed and greater engine complexity. The obvious next step was the twin-engine fighter, a doubling of power available without requiring the time and expense of a new engine development.

The U.S. Navy solicited proposals for a twin-engine carrier-based fighter in 1937 but none of the submittals were deemed to be acceptable. In 1938, the Navy had Lockheed modify an Electra Junior to have a fixed tricycle landing gear and tail hook. It was designated XJO-3 and delivered in October 1938. On 30 August 1939, Navy pilots made 11 takeoffs and landings from Lexington (CV-2) to evaluate it from both twin engine and tricycle landing gear standpoints.

In parallel with this research program, the 1938 competition for a new fighter was opened to both single and twin-engine designs. This time, the Grumman design number G-34 was considered worthy of evaluation by the Navy as the XF5F along with single-engine designs from Vought, the XF4U-1 powered by the big new P&W R-2800; and Bell, offering a derivative of the Army Air Forces P-39, the XFL-1.

The XF5F, probably in consideration of the one-engine-inoperative requirement, had the engines mounted as far inboard as possible and twin vertical fins, one in each engine’s slipstream. One-engine-inoperative wave offs were evaluated at altitude: "(A wave-off) might be accomplished (on one engine) provided the airspeed is about 80 knots or more and no more the 1/2 power on the operative engine were used." The "proper" approach speed based on stall speed, however, was defined as about 74 knots.

In spite of having as much or a little more installed horsepower than the XF4U, the XF5F was slower and couldn’t climb as high although its rate of climb through 20,000 feet was essentially the same. As a result, the Navy elected to proceed with the F4U for development and production. Nevertheless, the Bureau of Aeronautics continued to be interested in a twin-engine carrier-based fighter. On 30 June 1941, Grumman received a contract for the two XF6Fs and two XF7Fs. The F7F program suffered from the priority on F6F Hellcat development but the prototype Tigercat finally flew for the first time on 3 November 1943.

As soon as Grumman test pilots flew the XF7F-1, they realized that it did not have a big enough fin and rudder for an acceptable minimum control speed in the event of an engine failure on takeoff or a wave-off. Design of a bigger fin and rudder was initiated and introduced on the F7F-3. Although all models of the F7F were carrier qualified, the likelihood of and/or concern about a successful single-engine wave-off must have been low as there was no description of the technique for a single-engine carrier landing in the flight manual. In any event, the Tigercat never deployed with an air group on a carrier, probably due to its size as much as anything else.

One of the Navy’s first carrier-based jets, the McDonnell FD-1 Phantom was a twin, mainly because the Westinghouse-provided engine wasn’t very big. It grew to become the F2H Banshee, the first twin-engine airplane to regularly deploy on carriers. Two of its contemporaries, the Douglas F3D Skyknight and the North American AJ Savage, were also multi-engined. The AJ had three engines, two turning propellers and a jet. Like the F7F Tigercat, the Skynight was primarily operated by the Marines and made very few deployments. The Savage did deploy because of its critical mission of long-range nuclear strike, but because of its size, it generally was held in readiness at nearby Naval air stations during a carrier’s deployment. These jets were less limited from a minimum control speed standpoint in the event of a one-engine-inoperative situation than previous twin-engine propeller-driven airplanes because the engines were located close to the centerline; the AJs were slightly better off if one of its piston engines failed because the jet engine was located on its centerline.

However, North American was concerned about minimum control speed as evidenced by the size of the AJ’s original fin and rudder, made even bigger because carrier basing necessitated a fairly short airplane. Unfortunately, the rudder proved to be too big for high speed flight and resulted in a fatal accident when it broke the tail off in a flight test maneuver. The empennage was redesigned to increase the size of the fin, reduce the size of the rudder, and delete the dihedral in the horizontal stabilizer.

The lack of U.S. Navy concern about engine failures in the late 1940s was evident by the initiation of single-engine airplane programs, the Douglas F4D Skyray and the McDonnell F3H Demon, to replace the twin-engine all-weather Banshee. It was still true in 1958, when the Navy had to choose between the single-engine Vought F8U-3 and the twin-engine McDonnell F4H. The safety record of twin versus single-engine airplanes was examined and determined to not be a deciding factor. In fact, the only twin-engine airplane in the deployed carrier air groups at the time was the Douglas A3D Skywarrior, which had two engines because it was too big to be powered by only one. The F4H was selected because it had a dedicated radar operator, not because it had two engines.

The Navy did regularly deploy one twin-engine propeller-driven airplane at sea for more than two decades beginning in the mid-1950s on axial deck carriers, in part because Grumman had learned a lot about operating twin-engine airplanes from aircraft carriers with the F7F program. Its S2F (S-2) was as short-coupled as carrier airplanes get, so in order to size the rudder both for the single engine takeoff and wave-off condition and—relatively speaking—high-speed flight, it had a two-piece rudder. Up and away, the forward portion of the rudder was just used for directional trim and only the aft portion of the rudder moved with the rudder pedals. For takeoffs and landings, the forward and aft portions of the rudder could be selected to move as a unit, doubling the width of the rudder and reducing the S2F's minimum control speed to one suitable for carrier launches and wave-offs.

The introduction of steam catapults, angled decks, and descending, constant angle of attack approaches also reduced the degree of difficulty of one-engine-inoperative takeoffs and landings.

By the time Grumman engineers designed the F-14, they felt confident enough in their handling qualities analysis to widely separate its engines to provide a "tunnel" where two of the big Phoenix missiles could be carried side-by-side.

However, minimum control speed would still prove fatal to the unwary: Hultgreen Crash

Finally, click HERE for a great tale of how a second engine and a naval aviator saved an airplane...

Monday, October 4, 2010

I recently read an excellent history of a carrier-based airplane but noted that the author, in the captions, did not bother to differentiate between barriers and barricades. It is a minor quibble, but the nomenclature is specific and illustrates a two-step set of changes to carrier-deck equipment forced by the introduction of jet airplanes, one element of which was retained on angled-deck carriers.

Barrier

Davis Barrier

The configuration of the Davis barrier changed over time but the principal remained the same.

Barricade

The original barrier was introduced at the very beginning of carrier operations to stop an airplane when its tail hook had missed all the arresting wires. First one steel cable and then two were strung across the deck about three feet high at each barrier station. They were attached to stanchions which could be folded down to place the cables on the deck so airplanes could taxi past the barriers. An operator was stationed at each barrier to raise and lower it.

The steel cable barriers were very effective.

Unfortunately, the original barriers were not safe to use to stop airplanes with nose landing gears and to some extent, with twin-engine airplanes. The steel cables would wipe out the nose landing gear, raising the potential for the cables on the next barrier forward to slice the canopy off the airplane, and with it the pilot's head.

There was also the potential on a twin-engine propeller-driven airplane for the nose gear to pull the cable forward, allowing a propeller to hit it an angle and cut it, rather than skip off of it and past it. A tightly stretched steel cable when cut could wreak all kinds of havoc, not to mention not stopping the airplane.

The Davis barrier solved those problems by having the cables laying flat on the deck. A canvas strap was strung across the deck about three feet up using the same stanchions used for the original barrier. When the airplane's nose gear (or a "retractable barrier guard" in front of the windscreen if the nose gear had collapsed) hit the horizontal strap, vertical straps between it and the cables pulled them up off the deck to engage the main landing gear, thereby stopping the airplane. There were about six or so barriers on a carrier, so some were rigged for props and some for jets. They could also be reconfigured or replaced fairly quickly. Four barriers are shown in the following picture, two prop (lying on the deck) and two jet/AJ, i.e. Davis, one that has been activated but didn't snag the main landing gear because the jet had hooked a late wire so was going too slowly (barrier operators were cautioned not to drop their barriers too quickly) and the other in the ready position.

The Davis barrier worked acceptably after some development, although it was recognized that if the airplane were going too fast when it hit the Davis barrier, the cables might not be pulled up high enough, fast enough so they didn't get above the main landing gear tires and snag the landing gear struts before the main landing gear had passed by. There was also a problem with the steel cables being cut by airplane appendages at the higher landing speed of jets as well as pilots defeating the purpose of the barrier with a late and unsuccessful wave off as pictured above. After a few incidents in the fleet with jets not being stopped by the Davis barrier, a really big canvas net hung from scaled-up barrier stanchions was introduced as the last-chance layer of protection for the men and aircraft forward of the landing area. This was the barricade.

With the advent of the angled deck, barriers were no longer required. However, the barricade was still necessary if a jet had a landing gear or tail hook problem and couldn't land ashore. It is only rigged when required and the deck crews periodically practice erecting it on short notice and in only a few minutes.

Wednesday, September 29, 2010

Today I read an article in an English modeling magazine by a well-known aviation history author who repeated the error that the F2H-2 fuselage was longer than the F2H-1's, whereas the length increase actually occurred between the XF2D-1 and the F2D-1 (F2H-1). I decided to fix that on Wikipedia as a public service. In the process of doing so, I also fact-checked statements about the fuel capacities of the three airplanes. That's when I discovered that I had only resolved part of the length error that continues to be promulgated.

At the time of the XF2D-1 mockup review, its Standard Aircraft Characteristics (SAC) chart dated 1 May 1945 lists the fuel capacity as 510 gallons internal plus a 345 gallon external tank. Unfortunately, there were no drawings on this SAC chart. However, the length was given as 38' 9.5". The external tank was probably similar to the one provided for the FD-1 (FH-1) as shown here in November 1948.

A month later, an addendum page was added providing the "effect of mock-up changes on XF2D-1 preliminary data sheets dated 1 May 1945": "Subsequent to the distribution of the XF2D-1 data sheets, mock-up board recommendations revised the fuel system to eliminate the external droppable tank and provide instead an increase in internal protected fuel capacity from 510 to 847 gallons."

The XF2D-1 SAC chart dated 1 June 1946 shows an overall length of 38' 11.5", an increase of only two inches. The total internal-fuel capacity shown is the required 848 gallons, including the two tanks in the stub wings that presumably was 90 gallons of the more than 300-gallon increase required. I would guess that the fuselage was deepened from the mock-up configuration to provide most of the rest.

Note that there are three large fuselage tanks, again similar to the FD/FH fuel system configuration.

According to the SAC charts, the F2H-1 internal fuel capacity was increased by only 29 gallons over that of the XF2D-1. What's a little confusing is that the 1 April 1948 F2H-1 SAC chart page for Armament & Tanks is identical to the one above for the XF2D, almost certainly an error in compiling the SAC chart since the correct fuel quantity of 877 gallons is listed on its Page 1. (Each tank has a small but different capacity, with the largest difference being the aft tank at 223 gallons instead of 198.) Another oddity is that this SAC chart lists 200-gallon tip tanks for the F2H-1, whereas it's clear from the Pilot's Handbook for the F2H-1 dated 1 October 1949 and the F2H-2 SAC dated 1 November 1949 that the F2H-1 did not have provisions for tip tanks. Note that the F2H-2 SAC page for Armament & Tanks once again uses the XF2D artwork although it has been updated to show the -2 tip tanks and label each fuselage fuel tank with its correct volume without changing the size or shape of the tanks from the original XF2D illustration.

Not withstanding all that, the revelation to me is that the increase in fuel system capacity does not account for all or even most of the fuselage length increase ahead of the engine inlets between the prototype XF2D and the production F2D (F2H). A net increase of 31 gallons in the three fuselage tanks (the wing stub tanks were reduced in capacity by one gallon each) requires a net increase in length of the tanks of only about five inches, not 12. The remainder may have resulted from the need for additional interior volume for equipment and/or the desire to increase the fineness ratio of the fuselage and canopy to reduce drag. A center-of-gravity correction can't be ruled out, either.

Tuesday, September 28, 2010

The Supreme Court has agreed to hear part of the A-12 appeal by Boeing and General Dynamics. (See here, here, and here for the background; the case status is provided here.) Note that they are limiting their review to the Fifth Amendment issues and not reviewing the termination for default issue.

Sep 28 2010 Petition GRANTED limited to Question 2 presented by the petition. The petition for a writ of certiorari in No. 09-1298 is granted limited to Question 1 presented by the petition. The cases are consolidated and a total of one hour is allotted for oral argument.

09-1302 BOEING COMPANY V. UNITED STATES
DECISION BELOW: 567 F.3d 1340
LOWER COURT CASE NUMBER: 2007-5111, 2007-5131
QUESTION PRESENTED:
1. Whether the Due Process Clause of the Fifth Amendment permits an appellate court to adopt a new legal rule, inconsistent with its own prior ruling in the same case, and then apply it retroactively to the record established in the trial court pursuant to the prior ruling, without remanding to afford the parties the opportunity to prove their case under the new rule. 2. Whether the Due Process Clause of the Fifth Amendment permits the Government to maintain a claim while simultaneously asserting the state secrets privilege to bar presentation of a prima facie valid defense to that claim. 3. Whether the Government may terminate a government contract for default on the ground that a contractor has failed to make adequate progress toward timely completion of that contract where the Government has not set a valid deadline for completing the contract.
CONSOLIDATED WITH 09-1298 FOR ONE HOUR ORAL ARGUMENT
09-1298 LIMITED TO QUESTION 1
09-1302 LIMITED TO QUESTION 2
CERT. GRANTED 9/28/2010

Sunday, September 5, 2010

Some ship guys who know a lot about aircraft carriers don’t know all that much about carrier-based airplanes. Similarly, some carrier-based airplane enthusiasts are likely to be equally ignorant about aircraft carriers in spite of their best efforts, as in my case.

For example, I have sometimes referred to any angled-deck Essex/Ticonderoga-class* carrier as a 27 Charlie. The nickname comes from the SCB (ShipCharacteristic Board) design number for a set of Essex-class carrier modifications that began to be defined in the late 1940s, when the Navy realized that a major upgrade program was needed to allow them to operate jets, which had to be launched and recovered at higher speeds, and larger attack aircraft.

While doing some fact checking for my Skyhawk book for Specialty Press, including trying to figure out why a hangar-deck illustration appeared to show two starboard deck edge elevators on an Essex-class carrier (see here), I discovered that I was in error. As it turns out, the SCB 27 modifications added more powerful catapults and arresting gear, a reinforced flight deck, larger centerline elevators with additional lift capability, a new island, and an increase in the aviation gasoline storage capacity, among other things, but not the angled deck or starboard deck edge elevator. The first nine modified were 27As with the new H-8 hydraulic catapult and the final six were 27Cs (hence the Charley nickname) with the even newer and more powerful C-11 steam catapult, the most significant difference between the two upgrades. The nine 27As and three of the six 27Cs were completed and placed into service as axial deck carriers; the addition of the angled deck was accomplished in a subsequent overhaul period. (Only one SCB 27 carrier, Lake Champlain, did not eventually receive the angled deck.)

Not, strictly speaking, a 27 Charlie (Kearsarge)

A 27 Charlie (Ticonderoga)

(Note that the shape of the forward elevator and the aft location of the starboard elevator mark it as a 27 Charlie but an Essex-class carrier with a rectangular forward elevator and the starboard elevator located more forward might also be one of the 27 Charlies.)

The last three (Intrepid, Ticonderoga, and Hancock) of the six 27Cs modification were completed with the angled flight deck, so-called hurricane bow, and a starboard deck edge elevator replacing the aft centerline elevator. These modifications were the major part of SCB 125, which was then applied all but two of the carriers updated by SCB 27A and 27C. (These three were also unique in that the starboard deck edge elevator was located farther aft than on the other three 27Cs or any of the 27As subsequently modified in accordance with SCB 125, hence the hangar deck illustration mentioned above showing two locations for that elevator.)

The 27 Charlies are also distinguished by a 70-foot long forward elevator. However, the three modified at Puget Sound (Lexington, Hancock, and Shangri La) were originally completed with the standard SCB 27 54-foot forward elevator for some reason, with the 70-foot version being retrofitted at some point.

More than half of the angled-deck Essex-class carriers were therefore 27 Alphas plus the SCB 125 changes. One, Antietam (CVA-36), was neither a 27A or C but it was modified with an angled deck for an evaluation, which resulted in SCB 125. The starboard deck edge elevator was not incorporated. Antietam was eventually relegated to a training role.

Strictly speaking, it is not even correct that all angle-deck carriers with steam catapults were 27 Charlies. The first carrier to be modified in accordance with SCB 27A, Oriskany (CVA-34), had its hydraulic catapults replaced with steam catapults in the late 1950s when the angled deck was finally added to it. This was the unique SCB 125A configuration. From a capability standpoint, it was equivalent to the other 27 Charlies.

For much, much more on the subject of the development and description of U.S. Navy aircraft carriers, I recommend Dr. Norman Friedman's excellent U.S. Aircraft Carriers: An Illustrated Design History, Naval Institute Press, 1983, ISBN 0-87021-739-9.

* The most significant difference between the so-called Essex and Ticonderoga classes, if I understand correctly, is that the Ticonderoga-class had the upper part of the bow extended slightly to accommodate a second quad 40 mm cannon emplacement just in front of and below the flight deck. This gives rise to the categorization of short hull (Essex) versus long hull (Ticonderoga) ships; they were the same length at the waterline and the flight decks were essentially the same size.

Wednesday, August 11, 2010

Not too bold a claim, since as far as I know, it's the only one. However, it's got a lot of stuff in it on the F8U-3 and the Grumman D-118 that I'm sure you've not seen as well as coverage of the fly-off between the F8U-3 and the F4H. You can order it from Steve Ginter here or from Sprue Brothers here.

No matter how long I procrastinate before turning in a manuscript and illustrations, something always shows up after it's too late to include. In this case, the go-to guy for F3D stuff, Paul Bless, sent me an email with the following additional information:

I believe that the heads-up display in the F8U-3 was one of the first in a combat aircraft. It was developed by the Autonetics Division of North American Aviation and test flown in F3D-2M BuNo 127028, which was assigned to the Dallas BAR (Bureau of Aeronautic Representative) in 1956 through about 1960 when it was transferred back to Point Mugu.

Friday, July 23, 2010

The history of Navy VX development/evaluation squadrons is complicated and inadequately documented but I've attempted to summarize it. An example of complication is VX-3. In its first (and brief) incarnation, it existed to evaluate helicopters and develop operational procedures for them.

The aircraft evaluated by the second VX-3 couldn't have been more different, although it even used the same tail code initially.

VX-3 was one of four new air development squadrons (VX) that the Navy formed in 1946 to develop and evaluate aircraft tactics and techniques as directed by a command that was a consolidation of fleet units doing development work. (In December 1947 this command was designated the Operational Development Force.) Other squadrons were subsequently added. In 1969, the surviving Air Development Squadrons became Air Test and Evaluation Squadrons.

The first VX squadrons had two-letter tail codes with the first letter being X. In 1957, the first letter of the east-coast-based VX squadrons was changed from X to J.

VX-1 (XA/JA) Anti-Submarine Warfare: VX-1 was originally an Aircraft Experimental and Development Squadron established at NAS Anacostia in Washington D.C. on 13 August 1942. A detachment for aircraft antisubmarine warfare development was established at NAS Quonset Point, Rhode Island on 1 April 1943. This detachment was the basis for the next VX-1, which was commissioned on 15 March 1946 and moved to Boca Chica Field, NAS Key West, Florida. VX-1 relocated to NAS Patuxent River in September 1973 and is the only one of the original four VX squadrons still in existence.

VX-2 (XB/JB) Drone Controller/Guided Missile Development: VX-2 was formed on 15 March 1946 from VJ-20, which existed for only a week having previously been XVJ-25, which was established on 16 June 1945 at NAS Brunswick, Maine to support XVF-200, an Experimental Development Squadron formed at the same time to evaluate and test Kamikaze defenses. VX-2 was based at NAS Chincoteague, Virginia until it was disestablished circa 1958.

VX-3 (XC) Helicopter Development: Established at NAS New York on 1 July 1946 and moved to NAS Lakehurst. It apparently didn't take long to sort things out because the first VX-3 was disestablished on 1 April 1948. Its personnel and aircraft were assigned to one of two utility helicopter squadrons HU-1 (UP) and HU-2 (UR) located on the west coast and east coast respectively.

VX-3 (XC/JC) was reincarnated in November 1948 at NAS Atlantic City to accomplish development and evaluation of jet fighter tactics and procedures. It was formed by merging VF-1L and VA-1L of Light Carrier Air Group 1L. VX-3 was relocated to NAS Oceana, Virginia before NAS Atlantic City was decommissioned in July 1958. It was disestablished on 1 March 1960.

VX-4 (XD) Airborne Early Warning Development was established with the personnel and aircraft of VPB-101 on 15 May 1946 at Floyd Bennett Field, New York, flying PB-1Ws (B-17Gs with APS-20 air search radar installed in place of the bomb bay). The squadron made the first hurricane surveillance flight using radar in September 1946. It relocated to NAS Quonset Point, Rhode Island, in September 1946. It subsequently moved to NAS Patuxent River in July 1948 and was reportedly redesignated as Airborne Early Warning Squadron 2 (VW-2) in June 1952.

VX-4 (XF) Air-Launched Guided-Missile Development: Established 15 September 1952 at Point Mugu, California. It was disestablished on 30 September 1994 as part of the consolidation with VX-5 to form VX-9.

VX-5 (XE) was commissioned on 18 June 1951 at NAS Moffett Field, California. The squadron was initially assigned the development and evaluation of aircraft tactics and techniques for delivery of special weapons (nukes) from AD Skyraiders in all-weather conditions. In July 1956 VX-5 moved to the Naval Air Facility, China Lake, CA, since much of their test effort had involved use of the ranges and instrumentation facilities there. Semi-permanent detachments were located at several other bases Over the years, VX-5 maintained detachments at other Navy bases, e.g. at NAS Whidbey Island, WA to monitor EA-6B developments. VX-5 was formally disestablished on 29 April 1994 as part of the consolidation with VX-4 to form VX-9.

VX-6 (XD/JD) Antarctic Program Support: Established at NAS Patuxent River, Maryland on 17 January 1955 and subsequently relocated to NAS Quonset Point from which it deployed to the Antarctic from October to February each year. It was redesignated as VXE-6 in January 1969. Before Quonset Point was closed in 1974, the squadron was relocated to Naval Air Weapons Stations Point Mugu, California, where it was disestablished on 27 March 1999. (At some point, possibly associated with the move to the west coast, the tail code became XD again.)

VX-7 I haven't found anything on a squadron operating as VX-7.

VX-8 (JB) The Oceanographic Airborne Survey Unit was established on 1 July 1965 at NAS Patuxent River. It was redesignated VX-8 on 1 July 1967 and became the Oceanographic Development Squadron, VXN-8, on 1 January 1969. It was disestablished on 1 October 1993.

VX-9 (XE) was formed at China Lake from the consolidation of VX-4 and VX-5 directed by the CNO in June 1993 as a cost reduction measure. It was established on 30 September 1994. It evaluates strike warfare airplanes, weapons, and tactics, to include electronic countermeasures, from an operational standpoint.

HMX-1 was established in on 1 December 1947 at MCAS Quantico, Virginia for the development of amphibious assault via vertical envelopment. In September 1957, it acquired the additional role of presidential transportation via helicopter.

In early 2002, only three "X" squadrons remained: VX-1, VX-9, and HMX-1. Five more were added on 1 May 2002 as a result of redesignations of existing units:

The aircraft test and evaluation squadrons at Patuxent River were redesignated as VX squadrons;

Tuesday, July 20, 2010

In addition to its descriptive designation system for operational aircraft, the Navy had one for research aircraft, at least following World War II. It evolved to be the combination of the Navy’s letter for the manufacturer and the manufacturer’s internal design number for the project.

One of the first Navy research aircraft was the concept demonstrator for the Vought F5U program. The Navy designated it V-173, the Vought model number, and it was so marked along with the assigned Bureau Number (BuNo). The V-173 apparently predated the formal adoption of the research aircraft designation convention because U was the Navy’s letter for Vought, not V.

The Navy's next research aircraft program was initiated in 1945 with Douglas for high-speed research aircraft. This was intended to be a three-phase effort, with the first phase being design, manufacture. and flight test of a set of transonic jet airplanes; the second, modification of two of the six Phase 1 airplanes with auxiliary rocket engines for higher speed; and the third, a mockup of an operational jet fighter. Early on, Douglas and the Navy tore up the original plan. The first phase resulted in three D-558-1 identical straight-wing Skystreaks. The second phase was an all-new swept-wing aircraft. It received the designation D-558-2 and a different popular name, Skyrocket. Note that its Douglas model number was almost certainly not 558. The third phase of the contract was cancelled.*

The next Navy research aircraft program resulted in two Bell P-63s modified with swept wings in early 1946. These were designated L-39-1 and L-39-2, with L being the Navy’s letter for Bell and 39 in this case being the Bell design number for the proposal. (Design numbers were assigned by Bell engineering independently of model numbers, which were assigned by management). As it happened, Bell never assigned a model number to the Navy’s L-39. However, at least one of Bell’s L-39 flight test reports began with 33, which was the model number of the early P-63s.

The Navy bought three of the Kaman synchropter model 225s for evaluation in 1950, assigned them BuNos, and gave them the designation K-225, which also was the Kaman designation.

In January 1951, Convair received a contract for two experimental jet fighter seaplanes, which the Navy designated Y2-2. This is the cleanest example of the convention, since Y was the Navy’s letter for Convair and 2-2 was Convair’s model number. These were redesignated XF2Y-1 later that year.

The Navy contracted with Kaman for a tiltwing STOL ground test article (half of the wing, one engine, nacelle, and prop) as the K-16 in 1956. In January 1958, this contract was amended to add the design and manufacture of the K-16B, which consisted of the K-16 wing and a Grumman JRF fuselage. It never flew but was tested in the NASA Ames 40X80 wind tunnel in late 1962. A K-16C proposal with a Kaman HU2K helicopter uselage and fixed wing aircraft empennage did not result in a contract.

The Goodyear Inflatoplane was evaluated at NATC circa 1959/1960 in an Office of Naval Research Program. Five Goodyear GA-468s were reportedly acquired by the Navy for test but I don’t know if it ever got a BuNo or a Navy designation.

* The cancellation of the third phase of the Navy/Douglas high-speed research program did not preclude the uninformed from subsequently applying the designation D-558-3 to a follow-on study accomplished by Douglas for the Navy, the Models 671, as well as to its proposal for the Air Force/NASA/Navy X-15 program, the Model 684. It was, in effect, a retroactive nickname, one not used by Douglas at the time, much less the Navy.

My Latest Book

For More About My Books and Monographs:

About Me

In 1956, at age 12, I lived on NAS Sangley Point in the Philippine Islands. Always enamored with airplanes, I imprinted on the Cougars, Banshees, and Skyraiders then being deployed. Not able to be a Naval Aviator because I was nearsighted, I instead became an aeronautical engineer and general aviation pilot. Now retired, I write books and monographs on U.S. Navy aircraft.