Status Update on A6M2 Rei Shiki Sentoki Ni Ichi Gata.
(or a Tale of Two Zeros)
A week ago, I thought the A6M2 Zero was very close to done. It was missing a proper control panel, but the Hurricane panel wasn't too far off.
Since then....
I noticed that the engine output didn't drop even when the RPM was reduced by 150 or so.
I figured I had a pretty good idea what was causing this so went ahead to change it.
The change was to level out the Engine Efficiency to RPM curve which needed a corresponding change to the Torque Friction Loss per Cylinder to RPM curve. (Records 508 and 509.)
In playing with this, I found that although the power up to the critical altitude (12,500 feet) remained the same, the power at altitude was significantly reduced.
This was unacceptable because the absolute ceiling was already too low and less power would reduce the ceiling even further. The testing of the Aleutian Zero gave a ceiling of 38500 feet. I was getting more like 36,000 in testing.
The solution wasn't very difficult. It was basically to reduce the Engine efficiency and to also reduce the Friction loss. This needed a couple hours of testing to get an acceptable level of power at each altitude.
My original Zero was the A6M5 which I built and released about 10 years ago. Testing and research back then was much less than I do today. One of the things I have found since then was that the sea level speed of the Zero in most models was very close to 300 mph. The earlier flight model was limited to 270 mph at 500 feet.
One of the issues with the actual Japanese Zero was that its maximum speed in a dive was limited by structural strength. The maximum diving speed never exceeded 460 mph. We can't reproduce structural failures due to aerodynamic loads in CFS, so there needs to be something else to discourage excessive speed.
At the time, I found that I could control the directional and longitudinal oscillations of the aircraft quite easily and predictably and set the vibrations to start at around 285 mph TAS at 500 feet. This is only accurate to around 5-10 mph, so sometimes the vibration might start at 280 mph.
Since the new flight model was capable of around 290-295 mph at 500 feet, the vibrations needed to be tuned again. This needed a fair amount of looking around to find the notes I had used earlier. (Most recent use was around 2008.) To test this, I needed a way to push the aeroplane a bit faster. The A6M2 normally does not have WEP but for this test, gained about 10 inches extra boost and about 275 more horsepower to confirm that the new values I entered would not cause a vibration until 308 mph. This didn't seem to be enough so the next change put the speed limit up at 315 mph again at 500 feet. Under normal use, the virtual pilot should never see that this limit even exists.
The other speed limiting change which I now do for all new aircraft is to adjust the Mach Drag curve to put a "wall" just under Mach 1 which tapers back to adjust drag upwards at lower speeds to limit the maximum speed in a full power vertical dive. For this Zero, the speed limit is around 550 mph True Air Speed in a vertical dive from 30,000 feet. I didn't bother trying to convert this to Indicated Air Speed because I was lazy.
My protocol for testing level speeds is to run at full power with autopilot controlling altitude and heading.
As soon as 15 seconds pass without an increase, I note the current reading as maximum speed.
This may be 2-3 mph below where it finally stabilises, but is consistent and also compensates for an autopilot being able to hold much steadier than a human pilot.
Please respond with methods you all use to do this.
Speed @ 500 ft = 294 mph
Speed @ 12500 ft = 336 mph
Speed @ 15000 ft = 331 mph
I believe at this point, this makes a pretty good starting point for a flight model.
- Ivan.
(or a Tale of Two Zeros)
A week ago, I thought the A6M2 Zero was very close to done. It was missing a proper control panel, but the Hurricane panel wasn't too far off.
Since then....
I noticed that the engine output didn't drop even when the RPM was reduced by 150 or so.
I figured I had a pretty good idea what was causing this so went ahead to change it.
The change was to level out the Engine Efficiency to RPM curve which needed a corresponding change to the Torque Friction Loss per Cylinder to RPM curve. (Records 508 and 509.)
In playing with this, I found that although the power up to the critical altitude (12,500 feet) remained the same, the power at altitude was significantly reduced.
This was unacceptable because the absolute ceiling was already too low and less power would reduce the ceiling even further. The testing of the Aleutian Zero gave a ceiling of 38500 feet. I was getting more like 36,000 in testing.
The solution wasn't very difficult. It was basically to reduce the Engine efficiency and to also reduce the Friction loss. This needed a couple hours of testing to get an acceptable level of power at each altitude.
My original Zero was the A6M5 which I built and released about 10 years ago. Testing and research back then was much less than I do today. One of the things I have found since then was that the sea level speed of the Zero in most models was very close to 300 mph. The earlier flight model was limited to 270 mph at 500 feet.
One of the issues with the actual Japanese Zero was that its maximum speed in a dive was limited by structural strength. The maximum diving speed never exceeded 460 mph. We can't reproduce structural failures due to aerodynamic loads in CFS, so there needs to be something else to discourage excessive speed.
At the time, I found that I could control the directional and longitudinal oscillations of the aircraft quite easily and predictably and set the vibrations to start at around 285 mph TAS at 500 feet. This is only accurate to around 5-10 mph, so sometimes the vibration might start at 280 mph.
Since the new flight model was capable of around 290-295 mph at 500 feet, the vibrations needed to be tuned again. This needed a fair amount of looking around to find the notes I had used earlier. (Most recent use was around 2008.) To test this, I needed a way to push the aeroplane a bit faster. The A6M2 normally does not have WEP but for this test, gained about 10 inches extra boost and about 275 more horsepower to confirm that the new values I entered would not cause a vibration until 308 mph. This didn't seem to be enough so the next change put the speed limit up at 315 mph again at 500 feet. Under normal use, the virtual pilot should never see that this limit even exists.
The other speed limiting change which I now do for all new aircraft is to adjust the Mach Drag curve to put a "wall" just under Mach 1 which tapers back to adjust drag upwards at lower speeds to limit the maximum speed in a full power vertical dive. For this Zero, the speed limit is around 550 mph True Air Speed in a vertical dive from 30,000 feet. I didn't bother trying to convert this to Indicated Air Speed because I was lazy.
My protocol for testing level speeds is to run at full power with autopilot controlling altitude and heading.
As soon as 15 seconds pass without an increase, I note the current reading as maximum speed.
This may be 2-3 mph below where it finally stabilises, but is consistent and also compensates for an autopilot being able to hold much steadier than a human pilot.
Please respond with methods you all use to do this.
Speed @ 500 ft = 294 mph
Speed @ 12500 ft = 336 mph
Speed @ 15000 ft = 331 mph
I believe at this point, this makes a pretty good starting point for a flight model.
- Ivan.
Last edited: