Ad: This forum contains affiliate links to products on Amazon and eBay. More information in Terms and rules
One man's "set in concrete" is another mans "started getting a little heavy".I have always been of the same opinion that you are describing here. There are some people however who take some of the pilot reports literally rather than figuratively. I have heard arguments that when the pilot described the stick as feeling like it was "set in concrete", that is literally what he meant. Concrete, immovable.... When these kinds of comments start getting posted, it is time to find something else to do.
When you have an aircraft whose controls stiffened up at fairly moderate airspeeds, even a small change in direction for a simple tracking shot may require high effort on the controls.I suspect that the problem of pulling Gs and handling the throttle trigger at the same time, and/or that the requirement to do both at the same time, is being overstated.
When in a maneuvering fight the pilot will have to be able to handle both the throttle and stick, to one degree or another at the same time, whether the trigger is on the throttle or stick. Otherwise, when turning at significant Gs, the pilot will not be able to push the throttle forward to gain/maintain energy, or chop the throttle in order to prevent overshooting the target aircraft. Yes, I am sure there would be some instance where this might not be possible, but that would (I think) be the exception.
The A6M had problems with the controls stiffening up at high speeds (over 300 mph per the US evaluations) but not at normal maneuver speeds (which were usually in the 150-250 mph range). The aircraft was considered by the Japanese pilots to be very responsive at these speeds, with acceptable control forces, and this was backed up by the Allied evaluations.
And (though I may be thinking about this wrong) when turning at any rate over around 3 Gs the pilot in a typical WWII fighter will not be able to see the target aircraft (at effective firing range) anyway, as it will be hidden below the nose of the firing aircraft. Pulling around 3 Gs would not require particularly high stick forces in the fighters of the time (including the A6M), and even 4-5 Gs normally did not require particularly high stick forces. When we add that (from what I have read) most effective shooting occurred when the attacking pilot was able to relax on the Gs after gaining the necessary lead angle for the shot. Or the shot could be taken without having to pull high Gs in the first place (ie 80% or more of the shoot downs occurred without the victim being aware that the attacking aircraft was in a position to take the shot). I have only seen a relatively small number (easily less than 100) of shoot downs caught on camera, but in most of them neither the attacker or the attacked appeared to be pulling high Gs at the time of the kill shots.
Make sense?
DO IT. Trust me. Go fly a sailplane. You'll like it, a lot.agree on rudder but I have never been in let alone flown a sailplane so cannot comment on that.
I'm pretty sure you would have noticed the ground approaching and would have adjusted your trajectory to prevent such catastrophe from happening. Hopefully, there was no Zero on your tail ...To be honest, I find that circle-jerk to be BS.
Years ago, we were over the Mojave with our Cherokee Warrior and started a series of tight turns to port.
We started at about 10K AGL and after about five consecutive turns, realized we had dropped about 4K and bled off enough airspeed that we were about to enter a serious stall.
We levelled out at about 5K AGL or so and decided that was enough shenanigans for one day.
Found out later that the Air Density for that area was up and we had actually ended up been much lower than we thought.
Had we tried 75 or 100, we'd have been digging holes with our chins...
I'm not sure you are right above. There is a trigger on the stick. The throttle has an armament selector switch that allows the pilot to select cannons, MG, or both to shoot when the trigger is pulled. It might be depending on model, too.I figure this is the natural tendency to use two hands as stick forces get higher.
This brings up one of the features of the A6M series that I have always found curious and non-optimal:
The trigger for the armament is on the throttle.
If you need both hands on the stick in order to pull enough angle to get a shot, how do you take a shot when the trigger is on the throttle?
When you have an aircraft whose controls stiffened up at fairly moderate airspeeds, even a small change in direction for a simple tracking shot may require high effort on the controls.
andI think the trigger on the throttle was much more widespread and simultaneously more disliked. It WOULD make it harder to be offensive at higher speeds when two hands were needed on the stick.
It has also been mentioned that some pilots did not like this and had the trigger moved to the control stick . . .
re
and
It would be nice if there were any mention, in any reports written by Japanese pilots, to the effect that the position of the trigger was a problem. There are a limited number of such (test or combat) reports that have been translated into english, and I am sure that I have read only a relative few of them, but none of the ones I have read mention any such problem. I have only read a couple of books either written by former Japanese A6M pilots or as biographies written with the help of others, and there was no mention of such a problem.
Does anyone have any such references available?
Great post!I'm not too sure it was a "problem" as much as possibly annoying at higher speeds when you might need both hands to make a hard roll or pull. If you were using both hands, then it was hard to shoot. I'm not too sure when it happened, but many just-post-war American fighters had a turning handle on the throttle. It was sort of like a motorcycle throttle.
You get on the tail of the enemy and start closing. As you do, you twist the throttle handle one way or the other (toward you or away from you) and adjust the gunsight reticle (which was a circle of about 12 - 16 light spots on the windscreen) until it matched the wingspan of the target. When it did, you were in range and could shoot with some degree of certainty of a hit if your aiming point (a light circle in the middle of the reticle) was in the right place. If you were leading him with a deflection shot, it would be in front of the target along his line of travel. If you were in trail, it would be when the aiming point was on him.
Sounds complicated, but was and IS actually simple in actual use. I'm pretty sure most of the members in here have seen or tried this technique, at least on a simulator.
I have tried it in inside a hangar sitting in the front seat of a MiG-15 UTI 2-seat trainer. The gunsight is EASY to operate and we had fun using it to set the reticle so it just matched the wingspan of a Corsair picture taped to the wall in front of the MiG right in front of the gunsight. This was at Deer Valley airport, Arizona. I had a friend who had a MiG-15 UTI and we got it running about 1994 or so. We managed to start it an taxi it, but he passed away before he flew it. Last I heard, it was donated to a Museum in Boise, Idaho, though I'm not too sure if it ever got there. This particular guy also had an AT-6G and a mint-condition Cessna 180 with the rear seats removed so the dog (big, friendly German Sheppard) could ride. It was a kick to fly from short gravel patches around the Phoenix area. We landed once on a friend's driveway (gravel) and taxied up to the farm house. I'd have sworn we could not get in there but my friend, Curt Earl, landed there frequently and was very familiar with the approach. Interesting, to say the least.
Anyway, throttle-mounted stuff for gunsights and other functions have been a staple. Why not a trigger?
Great post!
I was not planning to post anything more here because we had reached a deadlock when it comes to if US trial data was representative or not.
But having thought some more about this I realized that there is another approach to the problem:
There is actually one data point which all seem to agree on: That the Zero did 316 mph at the so-called normal power setting with +50 mm boost and 2350 rpms.
So I added this power setting to my A6M2 Zero model in C++, and was happy to see that it was almost spot on as it was. I actually had to increase the value of the Cdo a few percent but it was really close.
And with the model now tuned to the 316 mph with the +50 mm at 2350 rpm, I again tried the power setting in the US trial, i.e. US 35" at 2575-2600 rpms, and the result was 334.5 mph. So basically spot on with the US trials.
Thus satisfied with the model, I now tried with the Sakae 12's "WEP" +250 mm boost 2550 rpm setting, and the speed was increased to 337.8 mph.
So why does the speed not go up higher with so much more added boost? Like to the vaunted 345 mph figure?
Well because at the same time as the power goes up, this extra power is generated at a lower altitude. And what this means in practice, is that while going from +50 to +250 mm and increasing the rpms certainly gives a much higher power, it at the same lowers the FTH to a lower altitude. And at lower altitudes, the air is denser, and the aircraft therefore experiences much more drag thus "eating" up the gain in power.
And this is why I have been posting the Spitfire MkI speed chart: The Spitfire's Merlin produces circa 1050 hp at +6.25 boost at around 5 km, and with +12 boost about 1310 hp, but this is at an altitude which is a bit below 3 km. And pushing the aircraft through the dense air down below 3 km eats up most of the added power. And that is what the chart shows: While the speed for the Spitfire at lower altitudes is greatly increased, the absolute top speed number at the FTH is not. And the effect is just the same for the Zero and the Sakae 12. And this is incidentally why you need simulations: Because if you assume that the added power is available at the "old" FTH, then 345 mph is most certainly possible. But this is simply wrong. This is not how physics works.
So in summary: With a C++ model replicating both the Japanese 316 mph with +50 mm, and the US test data at 35", the top speed of the A6M2 Zero at the +250 mm 2550 rpm setting can be expected to be in the order of 337-338 mph.
I think the account of Sakai running down the Cobra was in Samurai , I've read it more than once, but the last time about 20 years ago.This is part of what I wonder about. Just about every report has notes and explanations as to why the performance obtained with the Akutan A6M2 may not be representative of an operational aircraft and yet you ignore those notes that are in the actual report.
25-45 degrees happens to be the correct pitch range for A6M2.
29-49 degrees happens to be the pitch range for early A6M5. Later aircraft seemed to have a wider pitch range.
If accounts of aerial battles are to be believed, there is at least one Airacobra pilot who is probably convinced he could not outrun a A6M2 at low altitude.
Mr. Sakai tells of chasing one down and Airacobra are not particularly slow at low altitude.
I am curious as to what horsepower reading you got from your simulation at "Normal" power and at what altitude.
What altitude did you use for the US speed run trial and which test case did you see which showed an RPM over 2550?
What altitude did you use for the Japanese speed run trial? What speed did the simulator hit before use of Overboost?
I am fairly convinced that the supercharger on Sakae 12 had more capacity at its rated altitude.
If engine starts putting out black smoke, it is a pretty good indication that they are running a super rich mixture and a noticeable burst of speed is probably non-trivial.
So far we have been working on the assumption that Overboost was the same as Takeoff power but do we really know this was the case?
I do not believe the Spitfire is a good analog to the A6M2 with a Sakae 12 engine.
The Sakae 12 made more horsepower at rated power at its critical altitude of 4200 Meters than it did with Takeoff power at Sealevel.
Its supercharger was tuned specifically for "higher altitudes". The Sakae 11 apparently made about 30 more HP but down at 3000 Meters.
To be honest, I am not entirely convinced 345 MPH is entirely correct either which is why I have never gone back to revise my own simulator model.