Back to zip content
List of Fixed Items.

FMA not completely disengaging when ADF frequency changed from 666 or 777. This has been fixed. I tested every function and FMA remained completely disengaged.

Flap retraction from 20 degrees went stright to 5 and skipped 10 degrees. This has been fixed as well as the flap speeds have been slightly adjusted.

In certain situations the flaps would try to retract while descending for your destination and would be expecting them to extend. This has been fixed with a definitive border between the phase of flight that requires retraction and the phase that requires extension.

At high altitude cruise in rare situations automatic flap extension was possible and may occur. Fixed.

The HDG read out mode to display distance remaining to the Top Of Descent has been made to function in Alpha air space only to furthur assist in not getting in the way when HDG mode might be desired.

When leveling off below M0.82 FMA will now command the autopilot to maintain 310 KIAS replacing the old command of 300 KIAS.

After leveling off upon receiving clearance to climb again, FMA required an altitude input in the MCP greater than 900 ft above current indicated altitude to reinitiate. This has been changed to 1900 ft. This helps with control to climb 1000 ft or so. Also ATC would never issue a clearance to climb only 1000 ft, unless you were suddenly heading the other direction. Basically while flying westward you fly even thousand altitudes and odd while flying eastward.

FMA waits till a radio height of 120 ft instead of 80 ft to begin the automation. I did this to give the pilot a tiny bit more time to get the plane fully rotated.

 The automation of the landing lights in some cases were getting a little confused. Sometimes they would be turned off before landing. This has been Fixed.

While climbing if you pass into the descent phase FMA has calculated, FMA would set up the MCP but not actually activate it. Fixed.

     I just want to apologize to anyone who downloaded version 1.0. Some of these bugs were pretty major and could have caused some of you major frustration. Some of them were mental notes I was aware of but simply forgot because this project got a lot more complicated than I thought it would. Others I found while fixing the known issues. OK then, well I hope I corrected most everything. 

3rett.

END OF FIXED ITEMS*************************************************




































A Small Disclaimer. 

1. I, the author, am not responsible for any problems this add-on may cause you or your computer.
 
2. I, the author, am not required to offer any support of any kind.

3. This add-on is offered "AS IS" only.

4. No one not even I the author is allowed to sell this add-on for any type of monetary gain including but not limited to trades.

5. You ARE allowed to redistribute this add-on assuming it is in it's original and unaltered form and FREE of charge as defined in section 4.

6. I am asking that you don't try to modify this add-on. However doing so would ultimately render this add-on to a non-redistributable status.

7. You are required to have fun with this add-on!!!!!

















For FSX Only.


















Here is the most basic information on FMA to get you going............



First program a flight plan into the GPS. At the very least it should have one waypoint in between the departure and destination airports. This "final" waypoint must be between 20 and 30 nautical miles from and, directly inline with the intended ILS equipped landing runway. The heading TO the final waypoint should not exceed 35 degrees plus or minus the direction of the intended landing runway. There can be any number of waypoints between the departure airport and the final waypoint. Lastly give the plane enough room to climb and descend. Flight plans shorter than 240 nautical miles climbing higher than FL350 might not be able to complete their climb. Use common sense flight planning.

Get the ILS frequency for the intended landing runway and dial it in your NAV1 radio then transfer it to the active window.

Calculate and add the fuel needed for your flight.

Set up the MCP. Completely disable the autopilot including the auto throttle arm switch. Now dial your V2+15 into the IAS window. If you don't know what it is you can refer to the detailed instructions or use 165 which seems to be somewhat universal. The HDG window will display the total miles remaining before FMA's calculated point of descent. It will only display this information when over 13k MSL, within 360 NM of the top of descent, and when the HDG button is NOT illuminated. HDG mode can be used anytime for navigation as desired. The "Vert SPD" window is now used for selecting take-off thrust up to 10k MSL. 0000 is full thrust while +0100, 0200, and 0300 are all reduced thrust settings +0300 being the least amount of thrust. Finally enter your intended cruise altitude in the "ALT" window.

Now select GPS on the main panel to guide the autopilot's "LNAV" and dial 0666.0 into the ADF to activate FMA.

When lined up on the runway trim the plane to 8.5-9.0, make sure your flaps are at least 10 and all the lights are on. Now turn on the auto throttle arm and the flight director toggle switches ONLY. Do not turn on the autopilot or push one of the speed selectors. Just arm the AT and activate the FD.

Finally when the plane reaches an IAS of V2+15-25 (165-25=140 for example) evenly rotate to 10 degrees like normal. After the plane leaves the ground pull up to about 15 degrees to hold your V2+15 then when you're 120 feet above the ground (which happens quick) let go and enjoy the ride to your destination airfield.