• X-Plane
• MSFS 2020

• https://thinkaviation.net/ifr-clearance-tricks/
• https://www.vatsim.net/pilot-resource-centre/ifr-specific-lessons/ifr-clearances

Once you are connected to the appropriate Clearance Delivery Controller, all you have to do is ask for it:

“Clearance Delivery, good morning. Air Canada 301 requesting IFR Clearance to Calgary”

It is highly recommended that when you request your IFR clearance - you have a pencil in your hand and be ready to copy down the details of it. You just asked for it - so the controllers can only assume that you are ready to receive it.

CRAFT is a commonly used acronym for IFR clearances. CRAFT stands for Clearance Limit, Route, Altitude, Departure Frequency, Transponder.

• Clearance Limit - This is almost always the destination airport.
• Route of Flight - This is the route of flight you will fly. It must be checked as described below.
• Altitude - This is composed of an initial and final climb altitudes as described below.
• Departure Freqency - This is the frequency of the radar facility handling departures.
• Transponder - This is transponder beacon code assigned for your flight.

“Air Canada 301, Los Angeles Clearance Delivery. Cleared to the Calgary International Airport via the Gorman Four Departure, Shafter Transition, then as filed. Maintain 5000, Expect Flight Level Three Four Zero - five minutes after departure. Departure Frequency 124.30, Squawk 7201. Good Morning.”

Found at spadnext.com, this is a package of “drivers” which sits between devices and a Flight Simulator. It allows convenient routing and calculating of values between devices. It costs about $24.

This is an expression which helps fulfill Flight Reversing in MSFS 2020. Basically, you pull the throttle down, then push and hold the Button 7 (Labeled D on the X52 Saitek throttle controller), then push up to run the Thrust Reverser. Letting go of Button 7 returns normal operation.

This works by turning the output of Z Axis negative when Button 7 is pressed. Other numbers shown here are needed because the values to be returned to the simulator is about +/- 12K, but the Throttle axis is 0 to 100.

Letting go of Button 7 causes positive thrust to give some unwanted boost.

• On Z_Axis, add event for “Axis value changed”
• Simulator event: THROTTLE_SET

(100 - [LOCAL:JOY_0X06A30X0255_Z_AXIS])*
 (-50 - (213 * ([LOCAL:JOY_0X06A30X0255_BUTTON_7] - 1)))

Thrust Reverser interesting information: https://www.flaps2approach.com/journal/2022/9/9/reverse-thrust-procedure.html