Aviation is a hodge-podge of English, metric, dimensionless, and nautical units of measurement.
- Distance (nautical miles, nautical)
- Altitude (feet, English, and FL which is in 100’s of feet instead of thousands, very English)
- Airspeed (knots, nautical, and Mach, dimensionless related to the speed of sound)
- Temperature (centigrade, metric)
- Pressure (inches of mercury, English, and millibars, metric)
- Visibility (statute miles, English, and RVR in feet, English)
- Fuel quantity (pounds, English)
Our operational regime is initially 35 km above Venus to 60 km above Venus. Each kilometer would make for a good “flight level” and Aliens (the movie) made reference to “clicks” which is slang for kilometers.
However, as a former airline pilot, I like flying with knots indicated speed… and I am used to nautical miles for distance. So when I sat down to port over the altimeter, I took a pause… what units should it be in? Feet is unwieldy at 35 kilometers (114,829 feet aka FL 1148, whatever). Why not measure distance vertically the same that we measure it horizontally? 35 km is 18.8985 NM (60 km is 32.3974 NM) … and it gives us better resolution (the separation at tenths of NM is less than 1000 feet) so we could do a FL-type system (FL 188 to FL 324).
Doing a little research, I found that the retired space shuttle could display altitude in feet up to 400,000 depending on the phase and was also capable of showing altitude in miles from 40 to 165 (always based on static pressure).
Then again, our universe framework is metric based – it allows for faster and more accurate conversions between scales (i.e. meters to kilometers). Similarly, Rise was metric: Rise used meters and kilometers for everything – indicated speed, vertical speed, altitude, and distance.
Here is a little blast from the past for you Rise: TVP players…
I started porting over the code for the speed and altitude tapes as well as the attitude indicator and I just had to laugh. The resolution was so low and the display area so small (137×137 pixels) it is amazing we had as much information as we did.
Below is the overlay I am working with for the avionics suite. It is inspired by the EMB-195 and I am sure that the colors and spacing will change but the amount of information being added is going to blow you away!
So in addition to calculating the IAS incorrectly in Rise, the V-speeds that we were using for stall warnings, etc. were based on TAS instead of IAS! Now that I got the spreadsheet straightened out, I was able to flight prove the Vs1 and Vc speeds at both 35km and 60km.
We don’t have flaps, so there is no published Vs0 speed. We also don’t have to worry about Vr since we have no wheels, but it is interesting to note that the Vmc is so high it will likely still come into play when transitioning from VTOL.
We also have a Va speed, which I always knew as a pilot to reduce to when turbulent air penetration was anticipated – but did you know that means the wing will stall before we can exceed our positive G load limit? Genius!
So I wanted to see what would happen if I failed a flight control (neutral position). If it is either of the upper tail controls, there is some adverse yaw apparent but otherwise flies quite nice. Losing one of the lower tail controls, however, is a lot of work! You basically have to reduce the opposite engine thrust and you can then steer with pitch. Not a great situation but since we are VTOL we could reduce the airspeed quite a bit and rely on vectored thrust to steer.
However, lose an engine and we can no longer VTOL. Contrary to the Dropship from Aliens, we won’t be able to continue VTOL operations on a single engine.
Vc speed is maximum continuous thrust (MCT) in level flight (determined by the balance between total drag and total thrust). Our predicted Vc speed is 189 m/s at 35km. However, I am only getting about 146 m/s.
Looking along the longitudinal axis (Z) it turns out the flight controls (FCDRAG) are creating 24,500 pounds of drag in level flight. The rest of the airframe (AFDRAG) is only 40,500 pounds!