Nuff said. 😜
Connecting with the VNAV - I think you should be able to set the maximum VS that the VNAV Autopilot can go to, even if it doesn’t get to the required altitude at that waypoint. This would reduce the risk of stalling midway through flight due to a small distance between waypoints. Thoughts?
That would mean a more advanced VNAV system.
Right now it’s a very simple system.
When you set it up right, with care, the current VNAV feature will work fine.
I’d personally love a real FMC though. ;)
Nice addition!
Heheheheheheheeh to be honest i didnt… but its always worth a shot
oh my. That will be amazing and will literally make everyones life easier!!
I hope this might help and stop the amount of tail strikes I see… 😂
Thank you for the hard work and effort!
This will be awesome and I can’t wait 😊 thanks for all your hard work
Lastest iOS version on iPhone XR. Lastest IF and IF-A.
First launch it works perfectly, I even edited a Shortcut to launch IF-A than IF in one.
But if you finish flying and come back later for another flight nothing warranted to work. Weather I use my Shortcut, or launching manually apps (whatever the order), setting ON/OFF IF Connect. But if I restart my device it would be working like a charm.
Well, too complicated to stand. I’m gonna be refund from Apple for IF-A and an in-apps purchase.
I will make do without MINIMUMS, RETARD when landing etc. I hope that it would be integrated by IF team one of these days…
OK doing a first with this next release: a limited-time public beta! Share this link freely on social media if you’d like! You can take part in the beta even if you’ve never purchased In-Flight Assistant before! Unlike Google Play betas, iOS TestFlight betas are free while they last!
- Download the app “TestFlight”.
- Tap that link.
- That should install In-Flight Assistant as a beta!
Things to test for this update:
- v-speeds - enter a flight, set up your weight and flaps, then go into IF-A and tap “autofill”. It should fill in automatically calculated v-speeds.
- Please let me know if any of the speeds are off by tapping “Report error…”
- Welcome briefing now when seatbelt activated, if “pushback first” - else when starting engine.
- Safety briefing when starting engine if “pushback first” - else at pushback.
- Fixed some RAAS warnings not coming for C208.
Report any issues here, please!
I will try it out and get back to you.
I have a suggestion though. What about making a feature that can automatically retract flaps and gear on takeoff? It would fall under something kind of like the new V-speeds program. I thought it could save hassle. You could also set them to retract at a certain altitude.
Will try it out, thanks!
Love the improved safety briefing and firsts welcome idea. Will try it out
Hi the MD11F speeds are very low tried a fully loaded MD11F and the speeds were 147 152 156 flaps 28
Maybe because you’re using flaps 28?
Maybe but even at lower flaps it’s still low
Thanks! Please use the “Report Problem” button, and/or enter the data in this form: V-speed correction form
That way I have the proposed corrections in one spot.
Re C208 on iOS;
Everything IFA works perfect except Safely Briefing. It never plays, although turned on.
(Prior to IF 19 updates, it played when taxi commenced).
Thanks John.
I have submitted a report
John,
C208-iOS
“FA prepare for landing “ plays as soon as any descent from cruise is initiated. It plays again at the altitude set in IFA for that reached.
In regards to the Autofill…
It seems great! I’ve used it a bit and have a suggestion…
Often when I’m preparing a flight (getting flight plan, setting up I-FA and I-FO, etc), I’ll just be parked at my gate waiting to go until I’m ready. While I’m at the gate, I don’t have my flaps down, so when I Autofill, it tells me that it’s given me V-speeds based off of low flaps.
Could there be any way for us to tell it what flaps setting we’ll be using?
If not, that’s fine. Just wondering. I’d have to find a better time to set up the Assistant if this system will remain. 🙂
Thanks a ton! Glad to be a part of the beta.