Author Topic: Saxman (and all the other Corsair dweebs) (Read 1213 times)

Treize69 · « **Reply #15 on:** February 16, 2008, 08:45:06 AM »

The writeup and photospread in this months Warbirds Digest are great, highly reccomended.

Warbird mags are my pr0n.

Xasthur · « **Reply #16 on:** February 16, 2008, 09:04:22 AM »

Absolutely beautiful aircraft.

Imagine how horrible the forward visibility would be on take-off and landing.... That'd give the good old 109 a run for its money.

angelsandair · « **Reply #17 on:** February 16, 2008, 02:06:47 PM »

Just imagine how you could might see your six when an nme plane came up on you!!!! cuz we dont got mirrors for those planes in the game.

Shuckins · « **Reply #18 on:** February 16, 2008, 03:03:05 PM »

The F2G-1 was powered by the R-4360 "corncob" radial engine, which produced approximately 3,000hp. Projected speed at an altitude of 16,000 feet was 450 mph.

The F2G-1's cut down rear fuselage and bubble canopy had a pronounced negative effect on its lateral stability. That was something that the marginally stable Corsair design could ill afford, and is one reason why the Navy chose not to put it into production. Such a large increase in horsepower for such a small improvement in top-speed over the F4U-4 was another reason the design was allowed to languish. Finally, the F8F Bearcat offered much better vertical performance and slightly less top speed from a much smaller engine and horsepower package.

Regards, Shuckins

AquaShrimp · « **Reply #19 on:** February 16, 2008, 03:48:37 PM »

Deflection shooting would have been a pain in the butt in the F2G. Later model F4Us and P-51s actually had their noses angled downward to aid in deflection shooting.

Saxman · « **Reply #20 on:** February 16, 2008, 05:57:24 PM »

Shuckins,

Given time I'm sure Goodyear would have ironed out many of those problems. Certainly, the pilots who flew the F2G as racers certainly did.

Shuckins · « **Reply #21 on:** February 16, 2008, 10:26:06 PM »

Saxman, a dorsal fin, such as the type fitted to later models of the Mustang and Thunderbolt, would probably have alleviated the instability problem...at least to some extent.

The main problem with the F2G-1 was that, while the R-4360 produced abundant horsepower, the Corsair design was entering the area of diminishing returns. While the F4U-4 could produce speeds approaching 440 mph, the F2G-1 with 700 more horsepower bested that figure by little more than 15 mph. So, it was hardly worth the effort involved.

In any case, the advent of jet powered aircraft rendered further developement of such piston-engined fighters irrelevant.

Regards, Shuckins

bozon · « **Reply #22 on:** February 17, 2008, 06:00:12 AM »

Quote

Originally posted by Treize69
Thing would probably outshine the -4 Hog the way a P-47N does a D-11.

I'd take the D11 over the N any day, thank you.

Treize69 · « **Reply #23 on:** February 17, 2008, 07:19:56 AM »

Quote

Originally posted by Shuckins
The main problem with the F2G-1 was that, while the R-4360 produced abundant horsepower, the Corsair design was entering the area of diminishing returns. While the F4U-4 could produce speeds approaching 440 mph, the F2G-1 with 700 more horsepower bested that figure by little more than 15 mph. So, it was hardly worth the effort involved.

It wasn't meant to be drastically faster, it was designed as an interceptor against Kamikazes- high rate of climb and acceleration. Basically the lovechild of a -4 Hog and a 109K.

Saxman · « **Reply #24 on:** February 17, 2008, 09:25:24 AM »

Treize,

I've heard yes and no to that, including that the concept of the F2G dated back to before the war began, and that she was originally designed to be primarily a low-altitude fighter.

Treize69 · « **Reply #25 on:** February 17, 2008, 03:56:27 PM »

What I've read was that the concept of the engine was pre-war, its installation in the Corsair and its operational use were pure "Invasion of Japan might have beens".

Geophro · « **Reply #26 on:** February 17, 2008, 06:03:17 PM »

Picture hanger is hosed right now (says bandwidth error) but when it comes back here is a link to some of the pictures I took of it.