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.

A few questions about JS41

Featured Replies

1. This works fine with me.. don't know why it doesn't work properly.2. Make sure spoilers are armed and RPM is at 100% before landing. They also only come up while in reverse thrust.

Regards.
Matthias Hanel
 

MilViz Beta Team

  • Replies 33
  • Views 4.3k
  • Created
  • Last Reply

Top Posters In This Topic

  • Author

1. Hm, is it possible that crosswind causes that behaviour? (I landed on rwy 11 and wind from 190) ..but I quess not..2. I had 98% RPM, and speed .. hm, speed should be lower then Vref .. I don't remember. Spoilers were armed before takeoff - no doubt :)

Lukasz Trzaskowski

1. ILS approach- I have landed on APP mode twice and every time I was a little left drift from localizer (GS works fine). As a result I had to turn AP off earlier and handly correct horizontal path stright to the runway. What is wrong? ..what I did wrong? ..or is it a bug?
I have confirmed this issue, I'll make some screenshots later to show the scale of this "drift". I let the AP fly to 200" AGL and it made my landing really, really hard.
  • Commercial Member
I have landed on APP mode twice
You two aren't using the APP mode all the way down to touchdown are you? It's not rated for that and not meant to do that.Too many people confuse this. ILS is not autoland. ILS assists you in lining up with the runway with the addition of glideslope information, that is it. CAT-II offers lower minima. CAT-III, along with the appropriately rated crew and aircraft offers the option (requirement) of an approach ending in an autoland. Because of limitations in FS, however, there are no differentiations between CATs I/II/III as far as programming and settings go within the scenery, so all are treated as CAT-III (you may see CATs specified in the nane, but they are representations in name only).What was your intercept angle? Was the CRS set properly? What were the winds?Kyle

Kyle Rodgers

I think we're assuming he was using the tutorial flight when he had the problem with the localizer. Thre are some localizers in the game that are just wrong. If you have add on scenery that might also cause a problem. As for the wind idea, if its the tutorial, winds are pretty light there. And even so, the bird should automatically set the heading to stay centered and/or make corrections when it gets off line. As for John, do you have FS SP2 or acceleration installed? That's been the source of many problems.

PMDGAirbus.gif

Doug Orvis

PP-ASEL-IA (USA), Based at KHEF

 

Picture courtesy of Kyle Rodgers

You two aren't using the APP mode all the way down to touchdown are you? It's not rated for that and not meant to do that.
No we don't. At this moment I suspect ASE for causing a deviation on the final stage of approach, we will test it a little more with Lukas today.
As for John, do you have FS SP2 or acceleration installed? That's been the source of many problems.
I think that not having SP2/Accel installed is source of problems wink.gif
I think that not having SP2/Accel installed is source of problems wink.gif
Once again, I'm in total agreement with Grzegorz on this. What problems exactly come from SP2/Accel?

i9 10920x @ 4.8 ~ MSI Creator x299 ~ 256 Gb 3600 G.Skill Trident Z Royal ~ EVGA RTX 3090ti ~ Sim drive = M.2  2-TB ~ OS drive = M.2 is 512-gb ~ 5 other Samsung Pro/Evo mix SSD's ~ EVGA 1600w ~ Win 10 Pro

Dan Prunier

  • Author
What was your intercept angle? Was the CRS set properly? What were the winds?
1. At LOWW and EPWA, there are STARs/transitions which leads stright to the runways. Within these procedures I had NAV mode active (FMC was properly programmed). When I received localizer signal and I was on final of transition procedure (stright to the rwy), I engaged APP mod. Then, aircraft makes smooth corrections to capture localizer, but the needle isn't centered (a little left drift) and stays in that state all the time until reached 200' AGL. Then I disengaged AP and I have to handly make quite tidy corrections to be centered of the rwy.PS. I didn't try intercept localizer at c.a. 30 deg. angle.2. Yes. CRS was set properly, but... I set CRS which is included on approach chart.. and I have installed (freeware) addons scenery of airports (from AVSIM or Flightsim.com). Anyway, Grzegorz says, that he has the same issue although he has deafault sceneries (am I right, Grzegorz?)3. I don't remember what wind were at LOWW. At EPWA wind was 190/6-7kts and approach on rwy 11.PS. I also have ASE.Lucas

Lukasz Trzaskowski

Try the registry repair tool if LOC tracking is misbehaving. This is free from Flight1, and be sure to run as admin if you have Vista/W7.

Dan Downs KCRP

  • Author

Ok, I will check it and will reply what is result.Thanks!

Lukasz Trzaskowski

I have "applied" FS_Registry_Repair and I'm going to test it right now, if "drift" will occur I'll try to catch it on screenshot.

  • Author

Ok.. I have also 'applied' "Registry Repair". Now it looks quite good.. (approach for rwy 33, EPWA)..but there is a different between CRS from charts (324) and CRS from FSX (328). Although I have dedicated freeware AFCAD for EPWA for FSX, it looks like the FSX course (328) is properly.I don't know now -> my AFCAD for EPWA is broken or the course from FSX is always properly, independently of addon scenery..?CRS 324:eff562f9.jpgCRS 328:2ec59340.jpg

Lukasz Trzaskowski

Confirmed, my first landing after applying Registry Repair was perfect, even with the wind direction shift on the final. I'll test it more tomorrow, but so far so good.Thanks Dan!

Create an account or sign in to comment

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.