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.

FlightFactor Boeing 767 soon...

Featured Replies

Michel,

 

since apparently the ILS at TIST is well aligned, could you test an autoland with a 10 knot x-wind component ?

 

Thx!

Flying gliders since 1980

Flightsimming since 1992

AMD Ryzen 5600x, 32GB RAM, GPU Nvidia RTX 3060 Ti 8 GB, 1 TB and 500 GB nvme2 SSD drives, HP 27" 60Hz LED monitor @ 1920x1080, T16000, Hotas from old X52 Pro, Saitek Combat Rudder Pro (2010 model)

  • Replies 162
  • Views 32k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • Or you know, they could take what they learned with past products and apply it to their next release.  And we have so few developers for X-Plane that aim to make a high quality, complex aircrafts, do

  • I've been flying this for the last three days. It is the only plane that has brought those PIC / LevelD Sim 'feelings' back to this hobby of mine. While I am in love with PMDG's 777, this Flight Facto

  • Lashrathius
    Lashrathius

    I absolutely agree and thank you for bringing this out there.    Throwing my 2 cents out here -    People are saying "pass" from their past products. But ever considered the changes that went into

You know that you can change the wind in X-Plane, right? :Tounge:

 

Before you do the autoland, check the alignment of the localizer centerline on the "local map" in X-Plane. I would estimate 20% of all ILS approaches not perfectly aligned, some due to bad nav-data, but most of those because scenery artists didn´t place the runways accurately.

 

A plane doing autoland has nothing but the localizer signal to guide it laterally. So if that one isn´t running straight down the runway, the plane isn´t going to land on the centerline.

 

Jan

 

This is exactly what I said in my post above. The aircraft is perfectly align with the ILS signal, but it is the ILS signal which is not aligned with the runway in the scenery. You have to manually edit the ILS signal course on the local map and your aircraft will be on the ILS and will land on the center line of the runway.

 

Stephane

vpa055.png

Location : FMEE

Thx Stephane, and others who already mentioned the scenery alignment as being the possible cause... but...

 

but now I even more interested in finding out how the autoland logic on this 767 copes with crosswinds.  The 777 did a lousy work, even at slight x/wind components...

 

I would really like to find out how it is modeled in the FF 767 now...

Flying gliders since 1980

Flightsimming since 1992

AMD Ryzen 5600x, 32GB RAM, GPU Nvidia RTX 3060 Ti 8 GB, 1 TB and 500 GB nvme2 SSD drives, HP 27" 60Hz LED monitor @ 1920x1080, T16000, Hotas from old X52 Pro, Saitek Combat Rudder Pro (2010 model)

José then go to visit Keflavik BIKF. This is where Boeing is doing its crosswind tests ;-)

 

Stephane 

vpa055.png

Location : FMEE

I know Stephane... that where I used to take my FSX tests with ASN, PS1 and recently PSX :)

 

Airline Simulator 2 also did a great work - I miss it sometimes...

Flying gliders since 1980

Flightsimming since 1992

AMD Ryzen 5600x, 32GB RAM, GPU Nvidia RTX 3060 Ti 8 GB, 1 TB and 500 GB nvme2 SSD drives, HP 27" 60Hz LED monitor @ 1920x1080, T16000, Hotas from old X52 Pro, Saitek Combat Rudder Pro (2010 model)

  • Author

Michel,

 

since apparently the ILS at TIST is well aligned, could you test an autoland with a 10 knot x-wind component ?

 

Thx!

Ok, done. The aircraft lined up correctly and crabbed into the wind as expected. It brought me in high over the threshold and did not de-crab on landing, so rollout sent me left of the runway. TIST is a very short runway for a 767 and I ended up overshooting it.

 

I'm not certain on the correct procedure. Should I have initiated the lineup from crab myself, before touchdown?

It should all have done by the "AP" correctly, including the rollout, aligned with the rw centerline...

 

Theoretically you shouldn't have been forced to intervene, under than to set thrust reverse...

 

Well, I'll wait for iXEG....

 

Thx for the test!

 

P.S.: 

 

* The Boeing AFM low visibility autoland crosswind limitation is 25 knots. To both initiate and land, Delta Ops Specs further restricts CAT II and CAT III low visibility operations to a 15 knot crosswind limit. For CAT I or higher visibility, the autolnd crosswind limit is 29 knots...

 

The 767s autoland crosswind capability is 25kts, except on a contaminated runway, where it is 12kts, or very low visibility (<1200m/<600m) where it is lower (15kts/10kts respectively).

The autopilot will still attempt the autoland if wind speeds exceed these limits, but Mr. Boeing cannot guarantee that it will be successful. Once the runway alignment process takes place the autopilot will go to the limits of yaw and roll to try maintain localiser, if the wind is stronger than it allows for then the aircraft will fly out of tolerance and a go-around would have to be initiated. The same applies on the runway, however a wet runway could allow the aircraft to slide off the side, thus the lower limit.
The go-around is initiated if below Cat 1 minima and the aircraft is outside tolerance, normally autocoupled. If at or above Cat 1 minima and the crew becomes visual the autopilot may be disengaged and the approach flown manually. This is known as reversion and allows up to 33kts (+5kt gusts) of crosswind.
Depending on the airline's procedures use of the go around switch is required for a missed approach to apply thrust to GA limits and provide pitch and roll guidance to the flight directors. Not activating the TOGA switches was cited as one of the causes for the QF1 accident at Bangkok: 

Flying gliders since 1980

Flightsimming since 1992

AMD Ryzen 5600x, 32GB RAM, GPU Nvidia RTX 3060 Ti 8 GB, 1 TB and 500 GB nvme2 SSD drives, HP 27" 60Hz LED monitor @ 1920x1080, T16000, Hotas from old X52 Pro, Saitek Combat Rudder Pro (2010 model)

  • Author

Also noted upon LOC capture, when I subsequently pushed the APP button, the remaining 2 CMD autopilots were not automatically selected. I had to manually add them in. I think this is wrong and does not mimic the correct logic. Anyone care to comment on the correct behavior?

 

I'll add that the LAND 3 annunciator lit up at the correct RA of 1500 feet.

  • Commercial Member

I always believed that you had to manually select the other 2 CMDs when doing a LAND3...? It's like the PMDG NGX - you have to manually select the other CMDs.

3HSAJHT.png

TFDi Design

  • Commercial Member

Did you watch the video I posted? The real thing does it automatically.

Paul Grubich 2017 - Professional texture artist painting virtual aircraft I love.
Be sure to check out my aged cockpits for the A2A B-377, B-17 and Connie at Flightsim.com and Avsim library

i-5vbvgq6-S.png

  • Author

Did you watch the video I posted? The real thing does it automatically.

Hi Paul,

 

Yup, in the video, they clearly come on automatically as soon as the First Officer presses the APP button.

Yep,

 

perfectly seen in this video too: around 0:45

 

 

The 1st officer engages LAND mode, and soon after the three AP lights are "up"...

 

and... also in this video of the GREAT LevelD 767... around 3:31

 

Flying gliders since 1980

Flightsimming since 1992

AMD Ryzen 5600x, 32GB RAM, GPU Nvidia RTX 3060 Ti 8 GB, 1 TB and 500 GB nvme2 SSD drives, HP 27" 60Hz LED monitor @ 1920x1080, T16000, Hotas from old X52 Pro, Saitek Combat Rudder Pro (2010 model)

  • Commercial Member

I stand corrected. Thanks gents! I'll send a ticket in for a fix.

 

Cheers,

3HSAJHT.png

TFDi Design

  • Author

I can highly recommend these series of video training packs, this chapter deals with Autoland

 

 

Thanks Will, these will certainly come in handy.

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.