Jump to content

Archived

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

zachlog

Role of "Minimums" in Autoland/LAND 3

Recommended Posts

If the minimums are not set or not set properly (RA or BARO), will it cause the cancelation of "Autoland" and force a manual landing ? I understand that the "Minimums" callout will not be heard. Thanks,Zach


Zachary Kapsiotis

Share this post


Link to post
Share on other sites

As long as the minima are set up they should be heard. What I observe however, is very often after a go-around the callouts that were played on the first approach won't play on the second one. Not sure if they set some sort of "played" flag to the sounds, I don't know. The panel state files suggest something like that, but it's pure speculation on my part. Also, depending on how 'close' the minimum is to a 'usual' callout altitude (e. g. 100), the one might play but the other not. Other than that, it has nothing to do with autoland. Minima apply for every approach, no matter how they are performed (excluding CAT IIIB approaches without DH obviously) and you need to adhere to them no matter if you fly, the guy on the right seat or George. sig.gif

Share this post


Link to post
Share on other sites
As long as the minima are set up they should be heard. What I observe however, is very often after a go-around the callouts that were played on the first approach won't play on the second one. Not sure if they set some sort of "played" flag to the sounds, I don't know. The panel state files suggest something like that, but it's pure speculation on my part. Also, depending on how 'close' the minimum is to a 'usual' callout altitude (e. g. 100), the one might play but the other not. Other than that, it has nothing to do with autoland. Minima apply for every approach, no matter how they are performed (excluding CAT IIIB approaches without DH obviously) and you need to adhere to them no matter if you fly, the guy on the right seat or George. sig.gif
Etienne, Thanks for the reply. I understand the significance of "Minimums". The reason for my question was that I am still getting "No Autoland" so I am looking for candidate problem areas so I thought this might be one of them. Both radios tuned to the ILS Freq., Localizer, G/S, CMD B, Flaps at VREF, SPEED set to VREF+5....all are working fine except that right at the end, Autoland cuts out. There must be something I am missing. Thanks,Zach

Zachary Kapsiotis

Share this post


Link to post
Share on other sites

Zach,did you set both course selectors? Regards from EDDMPeter


Peter

Win10/64/32,0GB, i9-9900KS@4.00GHz, Gigabyte 1080ti, P3Dv5.1

Share this post


Link to post
Share on other sites
Zach,did you set both course selectors? Regards from EDDMPeter
Hmmm....I think I did but not 100% certain. I will retry and report back as soon as I have the opportunity. Thanks again,Zach

Zachary Kapsiotis

Share this post


Link to post
Share on other sites

Ahh, you were that, with the NO AUTOLAND issue. Forgot about that. Anything else, did you enable random failures? All failures checked and cleared? Everything set up, also on the overhead, electrical power distribution, both generators online? In case of fail-op equipment, ISFD aligned and operating? Two IRSs? No flags or other indications? Maybe you could post a large screenshot showing your entire panel when you get the message. Or maybe two more, of the overhead and the aft electronics panel too. Plus your location and intended runway of course. Maybe we can figure it out after all. sig.gif

Share this post


Link to post
Share on other sites
Ahh, you were that, with the NO AUTOLAND issue. Forgot about that. Anything else, did you enable random failures? All failures checked and cleared? Everything set up, also on the overhead, electrical power distribution, both generators online? In case of fail-op equipment, ISFD aligned and operating? Two IRSs? No flags or other indications? Maybe you could post a large screenshot showing your entire panel when you get the message. Or maybe two more, of the overhead and the aft electronics panel too. Plus your location and intended runway of course. Maybe we can figure it out after all. sig.gif
Etienne, When I confirm the setting of both CRSs (a couple of posts up), if I still get the "NO AUTOLAND", I will post a few screeshots. One question- Can you provide additional information on this one. >> ISFD aligned and operating? Thanks again,Zach

Zachary Kapsiotis

Share this post


Link to post
Share on other sites
Etienne, Thanks for the reply. I understand the significance of "Minimums". The reason for my question was that I am still getting "No Autoland" so I am looking for candidate problem areas so I thought this might be one of them. Both radios tuned to the ILS Freq., Localizer, G/S, CMD B, Flaps at VREF, SPEED set to VREF+5....all are working fine except that right at the end, Autoland cuts out. There must be something I am missing. Thanks,Zach
I had same problem , i was used for my preference to change the "instrument transfer swithches" position. It MUST be all in CENTER position otherwise AIII do not arm.I was getting crazy but finally i coght the solution.Hope this help you.Paolo bozzetti

CPU i7 7700 3,6 ghz @ 4,5 stable config.
32 gigs DDR4 3200 MHz ram  Geforce GTX 1080 Ti 11 Gbyte DDR 5 
windows 10 PRO 64 Bits build 2004  - Hotas Wharthog throttle - joystick + Rudder Pedals + Trackir 5 and Oculus Rift S
480 gbyte SSD Corsair .- 240 Gb SSD kingstone  - 10.000 rpm HD 1TB

 

Share this post


Link to post
Share on other sites
When I confirm the setting of both CRSs (a couple of posts up), if I still get the "NO AUTOLAND", I will post a few screeshots. One question- Can you provide additional information on this one.
Probably bad wording on my part, but for fail-op operation you obviously need the ISFD to be working as your third "inertial source", although that's a bit of a joke, also the ISFD uses heading info from one of the IRSs so it's not truely a standalone source if you ask me. Anyways, if you simulated a failure of it and cleared the failure, it needs 90 seconds to align again. For a full fail-op landing it needs to be operational. If it's not working you should definitely see some sort of message, at least NO LAND 3. sig.gif BTW Does anyone know what would be correct in the following scenario: Fail-op equipment, perform autoland. Anytime below 1500R, at least with LAND3 announced, fail the ISFD. NO LAND 3 appears on EICAS, other than that LAND3 remains enabled. Is this how it should be?

Share this post


Link to post
Share on other sites
I had same problem , i was used for my preference to change the "instrument transfer swithches" position. It MUST be all in CENTER position otherwise AIII do not arm. I was getting crazy but finally i coght the solution. Hope this help you. Paolo bozzetti
Paolo, Thanks for the suggestions but I don't know what this is referring to ==> "instrument transfer swithches" ? Zach

Zachary Kapsiotis

Share this post


Link to post
Share on other sites

They are on the overhead. If e. g. an IRS or DEU fails you can set all instruments on the remaining device, as usually for instance IRS L drives CM1's DUs while IRS R drives CM2's DUs. sig.gif

Share this post


Link to post
Share on other sites
BTW Does anyone know what would be correct in the following scenario: Fail-op equipment, perform autoland. Anytime below 1500R, at least with LAND3 announced, fail the ISFD. NO LAND 3 appears on EICAS, other than that LAND3 remains enabled. Is this how it should be?
Just below 1500 ft and while the localizer and glideslope are flashing amber ( performing a self test )........If you RESET the ISFD at this exact moment you will see Land 2 announced instead of land 3.Land 2 still has rollout and flare and is a full autoland. Fred.

Frederic Steiner.

B7382.jpg

Share this post


Link to post
Share on other sites

Well, I know that. But I talked about what should happen if the ISFD fails after the self test, with LAND3 already announced. What it does on the NGX, as indicated above, is I get a NO LAND 3 annunciation, but other than that LAND3 stays enabled. I was wondering if a NO LAND 3 indication at that time would downgrade the active LAND3 to LAND2 for example, or if LAND3 is 'locked' by that time, apart from severe malfunctions obviously like an IRS failure or so. sig.gif

Share this post


Link to post
Share on other sites
Ahh, you were that, with the NO AUTOLAND issue. Forgot about that. Anything else, did you enable random failures? All failures checked and cleared? Everything set up, also on the overhead, electrical power distribution, both generators online? In case of fail-op equipment, ISFD aligned and operating? Two IRSs? No flags or other indications? Maybe you could post a large screenshot showing your entire panel when you get the message. Or maybe two more, of the overhead and the aft electronics panel too. Plus your location and intended runway of course. Maybe we can figure it out after all. sig.gif
Etienne, LAND 3 finally worked for me and apparently I was not doing anything incorrectly. I was practicing my landing skills over and over at KDTW Rwy 22R/ILS 111.95. There must be a problem with this rwy because when I switched to rwy 22L/ILS 110.7 next to it, and did not change anything else, LAND 3 worked like a charm. Thanks for all your feedback (and the rest of the people in this thread),Zach

Zachary Kapsiotis

Share this post


Link to post
Share on other sites

Yeah maybe something's wrong with the AFCAD here and there. Freqs tend to change every once in a while... maybe you might check the data for that particular runway. sig.gif

Share this post


Link to post
Share on other sites

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
  • Donation Goals

    AVSIM's 2020 Fundraising Goal

    Donate to our annual general fundraising goal. This donation keeps our doors open and providing you service 24 x 7 x 365. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. We reset this goal every new year for the following year's goal.


    43%
    $10,910.00 of $25,000.00 Donate Now
×
×
  • Create New...