Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Flysimware Chancellor released (Beta)

Featured Replies

Anyone knows how to get on their discord?

Life time flight sim enthusiast, current airplane owner 172P (past C182F). FAA CP/IR ASEL/AMEL, FI ASEL

My System: AMD Ryzen 9 9950X3D , MSI X870 GAMING PLUS, 64G RAM, ASUS RTX5090, 4T SSD

Put my hands on (pic/dual/given)

7GCAA, 8KCAB, BE24, BE76, BE35-C33, BE35, C150, C152, C172B/N/P/R/SP, 182F, M20E,M20C, M20J, AT6(SNJ4), PA28-140,PA28-151, PA28-161,PA28-181,PA28RT-201,PA28R-180/201T, PA24-250, PA32-300R, PA44, AC114, YAK-18T, YAK-52, SR22

 

  • Replies 815
  • Views 102.2k
  • Created
  • Last Reply
12 minutes ago, sd_flyer said:

Anyone knows how to get on their discord?

https://discord.gg/XFa5wqxZ

My Liveries | FAA ZMP | PPL ASEL |
| Windows 11 | MSI Z690 Tomahawk | 12700K 4.7GHz | MSI RTX 4080 | 64GB 6000 MHz DDR5 | 500GB Samsung 860 Evo SSD | 2x 2TB Samsung 970 Evo M.2 | EVGA 850W Gold | Corsair 5000X | HP G2 (VR) / LG 27" 1440p |

 

 

16 hours ago, ryanbatc said:

I would love to try VR in this sim!  I need a new video card and a VR headset.

Ryan, I just recently began using VR and regardless of all it's shortcomings it has truly been an amazing experience, for me. I'm not easily impressed but this technology is transforming and has too many uses and value in many different ways and for many different types of use cases in the future. You will feel for the first time that you are really inside of an aircraft and when you take off you'll feel as if you are really going somewhere as you are now inside and part of the game worlds, that previously, you've only been looking at on screen.

I dunno if you've already tried it but if not you're in for a treat 🙂

I'm downloading 1.3 and every copy is corrupt zip. Anyone has this problem? (Yesterday's download was fine)

Life time flight sim enthusiast, current airplane owner 172P (past C182F). FAA CP/IR ASEL/AMEL, FI ASEL

My System: AMD Ryzen 9 9950X3D , MSI X870 GAMING PLUS, 64G RAM, ASUS RTX5090, 4T SSD

Put my hands on (pic/dual/given)

7GCAA, 8KCAB, BE24, BE76, BE35-C33, BE35, C150, C152, C172B/N/P/R/SP, 182F, M20E,M20C, M20J, AT6(SNJ4), PA28-140,PA28-151, PA28-161,PA28-181,PA28RT-201,PA28R-180/201T, PA24-250, PA32-300R, PA44, AC114, YAK-18T, YAK-52, SR22

 

16 hours ago, Boeing_Driver said:

Also, I have yet to see the autopilot capture an RNAV glide path either.

I'm not able to capture the RNAV glide slope using the PMS GTN750 either...I have the latest 1.3 installation. I'm not sure of the steps though...

With all steps, I choose PROC, then the correct RNAV approach. I load and activate.

  • I tried keeping the PMS 750 on GPS, then use GPS auto pilot.
  • I tried keeping the PMS 750 on GPS, then use the APPR auto pilot.
  • I have not tried the PMS 750 with VLOC

In steps 1 & 2 above, I do not see the GLIDE SLOPE indicator. I'm not able to find any information in the 414 manuals, although it is certainly possible, I missed it.

Anyone else able to capture an RNAV approach correctly using the PMS 750?

PC: AMD 9850X3D, RAM 64GB, Geforce GTX 5090 (32GB), MSFS 2020, MSFS 2024, Pimax Super 50PPD, Quest 3

11 minutes ago, sd_flyer said:

I'm downloading 1.3 and every copy is corrupt zip. Anyone has this problem? (Yesterday's download was fine)

just downloaded and installed 1.3. No errors. haven't tried flying yet.

Edited by Romeo_Tango

Robin

Still no VS control on the autopilot.

17 minutes ago, Romeo_Tango said:

just downloaded and installed 1.3. No errors. haven't tried flying yet.

Did you try unzip it?

Here what I get. Corrupt *.exe

unknown.png

Life time flight sim enthusiast, current airplane owner 172P (past C182F). FAA CP/IR ASEL/AMEL, FI ASEL

My System: AMD Ryzen 9 9950X3D , MSI X870 GAMING PLUS, 64G RAM, ASUS RTX5090, 4T SSD

Put my hands on (pic/dual/given)

7GCAA, 8KCAB, BE24, BE76, BE35-C33, BE35, C150, C152, C172B/N/P/R/SP, 182F, M20E,M20C, M20J, AT6(SNJ4), PA28-140,PA28-151, PA28-161,PA28-181,PA28RT-201,PA28R-180/201T, PA24-250, PA32-300R, PA44, AC114, YAK-18T, YAK-52, SR22

 

33 minutes ago, sd_flyer said:

I'm downloading 1.3 and every copy is corrupt zip. Anyone has this problem? (Yesterday's download was fine)

Also recently downloaded and all fine.

AMD Ryzen 7 5800x3d, MSI X570 Pro, 32 gb DDR4 3600 ram, Gigabyte 6800 16gb GPU, 1x 2tb Samsung  NvMe , 1x 2tb Sabrent NvME, 1x Crucial 4tb Nvme M2 Drive

1 minute ago, Car147 said:

Also recently downloaded and all fine.

OK thanks. I'll try different browser then

Life time flight sim enthusiast, current airplane owner 172P (past C182F). FAA CP/IR ASEL/AMEL, FI ASEL

My System: AMD Ryzen 9 9950X3D , MSI X870 GAMING PLUS, 64G RAM, ASUS RTX5090, 4T SSD

Put my hands on (pic/dual/given)

7GCAA, 8KCAB, BE24, BE76, BE35-C33, BE35, C150, C152, C172B/N/P/R/SP, 182F, M20E,M20C, M20J, AT6(SNJ4), PA28-140,PA28-151, PA28-161,PA28-181,PA28RT-201,PA28R-180/201T, PA24-250, PA32-300R, PA44, AC114, YAK-18T, YAK-52, SR22

 

35 minutes ago, sd_flyer said:

I'm downloading 1.3 and every copy is corrupt zip. Anyone has this problem? (Yesterday's download was fine)

I started the download and then fired up MSFS as it was downloading, and spent the morning shooting RNAZ approaches at KSBA on autopilot, writing up the procedure to post here for those asking for help,.    Just finished the session, and my download completed and is fine.  

So I'd suggest kicking it off again and coming back after a while. 

"That's what" - She

21 minutes ago, dbw1 said:

Still no VS control on the autopilot.

Is this the TDS, PMS or classic (GNS530) panel?

If TDS or PMS panel, I'd recommend first selecting an altitude below the HSI, then arming it (tiny white circle immediately to the right).  The press FD on the AP panel.  Then press VS and change it with the wheel.  Then press AP after trimming the plane to engage AP.

If it's classic panel... it may have changed.  But it used to be ARM altitude in selector, press ALT on AP panel, then use the thumb wheel to control pitch.  Don't forget to actually turn on the AP master rocker switch to the right of the thumb wheel.

Edited by ryanbatc

My Liveries | FAA ZMP | PPL ASEL |
| Windows 11 | MSI Z690 Tomahawk | 12700K 4.7GHz | MSI RTX 4080 | 64GB 6000 MHz DDR5 | 500GB Samsung 860 Evo SSD | 2x 2TB Samsung 970 Evo M.2 | EVGA 850W Gold | Corsair 5000X | HP G2 (VR) / LG 27" 1440p |

 

 

21 minutes ago, Stoopy said:

shooting RNAV approaches at KSBA on autopilot, writing up the procedure to post here for those asking for help,

Sounds GOOD! Looking forward to it!

PC: AMD 9850X3D, RAM 64GB, Geforce GTX 5090 (32GB), MSFS 2020, MSFS 2024, Pimax Super 50PPD, Quest 3

The below is longer than it needs to be only because I try to be very thorough. Also please excuse any technical or terminology errors, as I am only a self-taught sim pilot and not the real thing (although I have had a mustache since the age of 13),  But this is what works for me to do RNAV approaches with this bird,  

Start up normally from cold & dark, including avionics master

  1. I use the first PMS 750 for map, the second for flight plan
  2. In (second) PMS 750 Flight Plan menu, set Origin and Destination on PMS 750 (in this case, KSBA to KSBA)
  3. In PMS 750 Proc menu, select Approach, choose RNAV 7, set Transition to GOLET intersection (or whichever you prefer, doesn't matter, but the below example will use GOLET) then select Load Approach
  4. Note the altitudes shown for the various waypoints in the approach.  The initial approach fix of GOLET shows ground altitude so we can disregard and be at any height we like there, but the next waypoint LOBER is 4000ft, the final approach fix (faf) at NAPPS is 1800 feet. So we should plan to be at those altitudes when we reach those waypoints, and certainly for the iaf we need to be NO MORE than 1800ft - 1700ft might be a safer bet.  Otherwise we will be above the glideslope and the Autopilot will never latch on to it.  Better to sneak up on the glideslope from underneath it. 
  5. Now that we have a target altitude, in the Flight Plan menu, use the MENU button on the second PMS 750 to set the cruising altitude - in this case we'll just go with 4,000 feet.  Set Altitude Alerter (below HSI) to same altitude and arm it by pressing the ARM button (should get a yellow light to confirm).
  6. I also like to set my HSI Nav1 course (yellow arrow) to the heading of the destination runway, as a visual aid in flying the approach. Heading bug can be set as desired (in this case I set it to the direct track for the first waypoint, the iaf GOLET).
  7. On the Garmin autopilot panel, turn on the Flight Director (FD) button
  8. Press CDI on the first PMS 750 to select GPS mode instead of VLOC
  9. On Garmin the autopilot, put it in NAV mode and press ALT to set your desired altitude control mode (ft/min or pitch) but of course do not yet engage the A/P

Before taking off, review the plan:

  1. Take off, clean up the plane and head towards the iaf of GOLET, ideally at no more than 4000ft to make life easy for ourselves. For controlling the vertical speed, IAS mode seems to work best for climbout right now. 
  2. We'll engage autopilot in NAV mode as soon as we stabilize the climbout and set altitude for 4,000
  3. PRIOR to reaching the iaf of GOLET, we are going to activate the approach on the second PMS 750 by clicking on the large tile at the top of the approach that says "Approach - KSBA RNAV 7" and select "Activate approach".  If we wait too long it may turn the plane back to the prior waypoint of KSBA and overfly it, if that happens select "activate Approach" on the PMS 750 again
  4. We will also need to descend to the target altitude (or below) for each waypoint in the approach, with the goal of being below 1800ft by the time we reach the faf NAPPS
  5. Prior to reaching the NAPPS iaf, but after passing through the previous waypoint of ECEVA. we will put the autopilot in approach (APPR) mode.  

Pre-Takeoff settings:

  1. IAS set to desired climb speed (110 kts or so)
  2. Altitude Alerter set to 4000ft, and Armed (yellow light)
  3. Autopilot set to NAV mode
  4. Flight Director on, Autopilot off

Takeoff and Climbout:

  1. Clean up the plane, stabilize your climb and engage Autopilot
  2. IAS of 110 gets pretty close to best rate of climb, monitor the altitude and if it overruns and fails to level out at 4000 fpm, press ALT and dial in -500 fpm, then ARM the altitude selector again if not already still armed.
  3. Reduce manifold pressure to 25" or so when when leveled out, reducing to 22 or 20 as you get closer to the faf

Steps for ascending/descending to desired altitude with Garmin A/P and Altitude Alerter from level flight:

  1. Set the desired new altitude on the Altitude Alerter, but do not ARM it yet (you probably won't be able to)
  2. Press ALT on the Garmin Autopilot so that the "VS" mode shows up
  3. Use the Garmin Autopilot NoseWheel dial to dial in the ascent/descent rate
  4. As the Ascent/Descent begins, press ARM on the Altitude Alerter to queue the Altitude Selection (ALTS) in the Garmin Autopilot diplay window

Approach:  Using the above procedure you can either dial in the new altitude setting for each point in the approach (4000, 2800 for ECEVA then 1800 for this appraoch), then activating by pressing ALT to dial in the descent rate of -500 fpm or whatever followed by ARMing the Altitude Alerter, or just dial in the faf altitude of 1800 (in this case) then activating by pressing ALT, dialing in the descent rate of -500 fpm or whatever, and ARMing the Altitude Alerter.
 So after GOLET, set Altitude Alerter to target altitude of either 2800 for ECEVA, or 1800 for NAPPS iaf if you just want to cut to the chase.

  1. Upon reaching LOBER at 4000ft, use VS mode on autopilot to initiate -300 to -500fpm descent rate.  Adjust as you like to reach target altitudes (or below) at subsequent waypoints until reaching the faf
  2. When reaching target altitude of 1800 or whatever for our iaf, the A/P should level out if Altitude Alerter was armed, if not press ALT on the Garmin A/P to level out. Then place A/P in Approach mode by pressing APR button. Autopilot shoud respond by showing "GP" on bottom of display, indicating GlidePath mode is armed and the A/P is looking to capture it
  3. At or just prior to reaching the faf of NAPPS, the autopilot should capture the glide path and nose you down to a -500fpm descent.  You did get the plane slowed up ready to drop gear and flaps, right?  IF not this is the time to do so!
  4. Seatbacks raised and tray tables put away.
  5. The yellow Glideslope indicator on the left side of the Attitude Indicator, above the HSI, should confirm you are on the glideslope, and the directional arrow on the HSI should verify you are on the localizer 
  6. If you find yourself going below or above the glideslope, check your airspeed. I start out with MP at the bottom of the green arc, gear and full flaps down, and keep it around 100 knots or so, then 92 or thereabouts over the fence.  I haven't looked up the official V speeds but this seems pretty close.

Will add some screenshots later,  Professional pilots and other experts please feel free to pick the above apart and point out corrections or other tips & advice.  Happy Landings.

 

Edited by Stoopy

"That's what" - She

Thanks Stoopy,

The take away I get from the above is:

  • Arrive at FAF at correct FAF altitude
  • PMS GTN750 is still set to GPS mode
  • Press APR mode on A/P

Pretty sure I tried all this, but I did use the 1st GTN to setup and initiate the RNAV approach. I will use the second as you describe above.

I know I must be missing something, but while I do see the "GP" show up after pressing APR, I did not see the Yellow Glideslope indicator on the left side of the Attitude indicator.

Thank you very much for taking the time to document your process!

PC: AMD 9850X3D, RAM 64GB, Geforce GTX 5090 (32GB), MSFS 2020, MSFS 2024, Pimax Super 50PPD, Quest 3

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.