Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add autoland (yes or no) field to EFB landing distance calculator #6343

Closed
donstim opened this issue Dec 11, 2021 · 0 comments · Fixed by #6528
Closed

Add autoland (yes or no) field to EFB landing distance calculator #6343

donstim opened this issue Dec 11, 2021 · 0 comments · Fixed by #6528
Labels
EFB Request New feature or request

Comments

@donstim
Copy link
Contributor

donstim commented Dec 11, 2021

Aircraft Version

Development

Description

The landing distance calculator provides in-flight landing distance data to assist pilots in determining if they can safely land on a particular runway. It includes inputs for all of the variables that affect the in-flight landing distance computation. However, it is missing one item, and that is whether or not an autoland is being conducted.

There should be an additional input box for whether or not autoland is being used. It should have 2 choices, (1) yes or (2) no.

References (optional)

See this page from the FCOM on which the landing distance calculator is based. I have marked the missing autoland landing distance correction with a blue arrow.
Screenshot (1386)_LI

Additional info (optional)

I should have noticed this when reviewing the PR introducing the landing distance calculator, but I missed it.

Discord Username (optional)

donbikes#4084

@donstim donstim added the Request New feature or request label Dec 11, 2021
@donstim donstim mentioned this issue Jan 31, 2022
32 tasks
@derl30n derl30n added the EFB label Apr 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
EFB Request New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants