Welcome to the RA40 Excelsior, a short-haul passenger transport ideal for servicing even the smallest airfield in SimplePlanes. An older design originating from the early 1960s, this turboprop has a mostly analog cockpit setup.

This craft demonstrates a more realistic understanding of the primary systems abord an airliner: hydraulics, fuel/transfer, electrics and pneumatics. Featuring a fully functional cockpit, she delivers an immersive experience with a VR cockpit and operational checklists. She boasts a rudimentary landing assist for Wright Airport runway 36, using a coordination of distance, speed, descent rate and runway centerline tracking.

AG 7 for airstairs

ELECTRICS - The electric system is derivative of a B727 and B737. Its AC system is powered via three 120 K VA generators (one per engine and one for the APU) into a left and right AC, and an exterior 220 connection. The AC will then energize a respective DC system. To note, without DC and the battery, most cockpit instruments are useless.

FUEL - A significant leap from my previous build, fuel crossfeed is available between the two fuel tanks (only two tanks for this craft).

HYDRAULICS - Based off a Dehavilland Dash 8, the hydraulics are still quite rudimentary (see final paragraph for explanation as to why this feature was omitted). The hydraulics actuate, among other things, the rudders, landing gear and flaps. With a left and right system, she has a one-way power transfer unit (right to left) in case of loss of right AC and the number two engine.

PNEUMATICS - Based off a B737, it's a rather simple setup with not too much going on. Really, the only aspect of the pneumatics that can be enjoyed in VR are cabin pressure and the engine starters (and anti-ice for optics)

LANDING ASSIST - This is accomplished using distance, speed, descent rate, and a basic centerline guide for Wright Airport runway 36. By inputting the runway altitude into the digital display and selecting "APPLY," that altitude entered will become "0" (ground level) on the rotary altitude gauge.
Calculating landing distances is a bit more complicated. I recently taught myself how to do this and have conducted a many successful approaches of varying precision (practice makes perfect) using the 1 in 60 rule. The below link is how I got a basic understanding of this stuff.
https://www.boldmethod.com/learn-to-fly/navigation/how-the-60-to-1-rule-helps-you-plan-a-perfect-descent/

Omissions from original concept plans: Most notably, the variables menu seems to glitch after so many lines of code, which stopped me short of programming the hydraulic pressure use-reduction. An autopilot system is, for the time being, beyond my abilities in terms of developing the necessary matrices to pull that off. Cockpit lighting was also ruled out very early when designing this, as switches (as distinct from buttons) misbehave with part movement. Additionally, to save on part count, I elected not to include a master caution indicator system.

Find yourself a good chunk of time, slap on your VR headset and dive on in. Comments, feedback and funky tree questions are welcome and encouraged.

Happy flying friends