Questions? Feedback? powered by Olark live chat software
Powered by Jitbit .Net Forum free trial version.

iFlightPlanner

 

...

Forum

Recent Posts recent posts - RSS

19 days ago
Topic:
Please add Top of Climb and Top of Descent

John Burnside
John Burnside
Posts: 215
Thanks for your post and the additional detailed info! Unfortunately, top of climb and top of descent is not provided by the underlying flight planning engine, so inserting it into the navigation log would be a rough guess. We will continue to work with our technology partners to try and make this possible!

We know that isn't the answer you're looking for (or that we'd like to give), but we do appreciate your feedback and will continue to work to make this possible!
26 days ago
Topic:
Please add Top of Climb and Top of Descent

sjk2@njit.edu
sjk2@njit.edu
Posts: 1
Hello,

Is there an update on this feature?

top of climb can be found here: https://en.wikipedia.org/wiki/Top_of_climb

Basically, it is a way for you to establish that your climb and weather are correct, and to check to ensure that your calculations are correct.
It would be nice for the program to put a way point on the map while planning to indicate where the top of climb and top of decent are. This can be done automatically, through a setting or via an option while planning the route.

I think the easiest way to do this would be to calculate the distance you would travel from departure and arrival based on your ground speed and climb/decent performance. For example, I climb at 500 ft/minute, I know that I want to cruise at 4500 MSL and the airport is 500 ft above sea level. It would take me 8 minutes to climb. If my ground speed is 90 knots, I know that in 8 minutes I will have traversed 12 nautical miles from my starting point. The program will then put a way point on my course 12 miles from my departure airport. The same process would hold true for the top of decent.

Please let me know if there is anything I can do to help with this feature.

Thanks!
1/13/2020
Topic:
iPad Waypoint Deletion

John Burnside
John Burnside
Posts: 215
Yes, indeed. Just an oversight on our part!

We much prefer to fix the root issue ASAP rather than provide workarounds, especially those that are a bit clunky. That is much easier done on the web (iFlightPlanner.com) where we can deploy individual changes like this. However, for apps, an entire new version has to be deployed and approved through Apple, so it takes a bit longer. In the meantime, we at least want to provide an option to remedy.
edited by John Burnside on 1/13/2020
1/13/2020
Topic:
iPad Waypoint Deletion

ssharpe83713
ssharpe83713
Posts: 3
Thanks, John. Logically, I would think that since the developers decided to allow the creation of temporary locations in the free version, they would provide a means to get rid of them, short of killing the app each time. Thanks again!
1/13/2020
Topic:
iPad Waypoint Deletion

John Burnside
John Burnside
Posts: 215
Ah, yes. For iFlightPlanner Free members, iFlightPlanner for iPad is "view only." You may plan and modify flights at iFlightPlanner.com, then sync the info into iFlightPlanner for iPad, but only view it there for reference. This is because our Free membership level is supported by ads on the web, but we don't show any ads in iFlightPlanner for iPad.

We will review the temporary waypoints issue in the Free version and plan to add an easy method to remove those. As a workaround for now, if you double tap the Home button on your iPad and close out iFlightPlanner for iPad completely, then re-open the app, they will be removed.

Let us know if we can help further in the meantime!
1/13/2020
Topic:
iPad Waypoint Deletion

ssharpe83713
ssharpe83713
Posts: 3
Thanks for your quick and detailed response, John. However, it appears that the free version does not behave that way. Flight planning is not functional on the free version, so I don't get those associated options. There is no "Save As" in the upper left corner of the popup menu. If I plan a flight from the website, that flight is visible after the iPad sync, but it can't be modified in the free version. No matter which past flight I select, the map continues to show the scattered waypoints that were previously created by a long press from the map screen. It sure would be nice to have a delete capability for temporary locations created on the map in the free version.
1/12/2020
Topic:
iPad Waypoint Deletion

John Burnside
John Burnside
Posts: 215
Thanks for your post! We're always happy to help.

There are a few key touch interactions available with the map in iFlightPlanner for iPad:

1. If you simply tap anywhere on the map, as you did, and select a location it will add that location to the route of your current flight. Tap "Planner" at the top, then "Plan Flight" in the black planner console that drops down to generate a new navigation log including the new point.

2. To create a "Custom Waypoint" that is permanent and may be used in future routes, tap anywhere on the map, then tap "Save As" in the upper left corner of the popup menu.

3. Once you have planned a flight and see the route on the map, you may long press on the route line to insert a new waypoint into the route.

4. For any waypoint in your route, you may single tap it to see the waypoint info and a button to remove it from the route. You may also long press and drag the waypoint to perform route-rubberbanding.

If ultimately, you're just trying to get rid of one or more temporary locations on the map created by option 1, just tap the back button to return to your Flights list, then tap New Flight and they'll be cleared.

Let us know if we can help further!
1/12/2020
Topic:
iPad Waypoint Deletion

ssharpe83713
ssharpe83713
Posts: 3
I'm evaluating the free version on iPad. From the Flights/View Charts/Map screen, I can long press on the map to generate the Location pop-up menu and select a location, which appears on the map in a small blue circle, but I can't figure out how to delete the locations that I place on the map???
1/6/2020
Topic:
Leg altitude

John Burnside
John Burnside
Posts: 215
Thanks for clarifying! Unfortunately, the flight planning engine does not support varying cruise altitudes within a single flight, but your example and the other possible scenarios, especially involving mountain flying, are scenarios that definitely happen in real-world flying.

I wish we had a better answer for you at this moment, but we have noted your feedback in our list of feature requests to review for coming development. As always, our development is prioritized based on member input and request volume for a specific feature, so we greatly appreciate you sharing your question here!
1/3/2020
Topic:
Leg altitude

ultrissa
ultrissa
Posts: 2
Thanks John for your reply. By 'leg' I mean the section between two waypoints. I thought of this problem the other day when I was planning a flight between Mount Pocono, PA (KMPO) and Essex County, NJ (KCDW). I wanted to fly via Blairstown (1N7) and Andover (12N) at 5500 ft altitude but KCDW is under Newark's B airspace external 'cake', which has a 3000 ft base. This means that somewhere between Andover and the border of Newark's airspace, you must descend below 3000 ft. Ideal would be to add a waypoint (WP) near the airspace border where you want to be sure to be at, say, 2800 ft and have the software re-calculate and define TOD (5500 ft) and BOD (2800 ft) in the 'leg' Andover-WP, after which you proceed to KCDW at a safe 2800 ft. (Marking TODs on the route would be also very useful). Of course, in this particular circumstance, this is not really critical since KCDW is close enough to the airspace border for me to descend and proceed by dead reckoning, but think of the many other situations (crossing a mountain crest for example or having to transition under or over an airspace) in which changing temporarily altitude and maybe also speed might be critical. I don't mean just editing the speed in the NavLog but re-calculating everything: winds change direction at different altitudes.

Thanks for your attention


Carl Salustri
1/2/2020
Topic:
Leg altitude

John Burnside
John Burnside
Posts: 215
Hi Carl,

Thanks for your post! We're always interested in feedback from our members.

We do provide the ability to set the altitude on a per-flight basis. To clarify, by "leg" do you mean a flight between two airports or a segment within a flight, such as between two waypoints?

I ask because people sometimes use "leg" interchangeably and we want to make sure we're answering your question as accurately as possible.
1/2/2020
Topic:
Leg altitude

ultrissa
ultrissa
Posts: 2
iFlightPlanner is a GREAT tool, for which I thank you very much. The only serious flaw that I found in it is the impossibility to set a cruise altitude for each leg (I don't mean just editing, but recalculating winds, heading etc. in the Nav Log). This is a serious detail when flying in mountain regions or in the vicinity of air spaces. PLEASE, consider this issue.
THANK YOU.

Carl
Private Pilot
12/15/2019
Topic:
Stratus 3??

John Burnside
John Burnside
Posts: 215
Definitely a matter of months, not a year! Also, if you'd be up for it, we can provide you a beta version to help us test out the new integrations and other features. Let us know if you're interested and we'll reach out by e-mail to get your device info!
12/13/2019
Topic:
Stratus 3??

clocklin
clocklin
Posts: 14
Any hints on when version 4.0 might be out? If it's a year away, I'd like to get my ADS-B In working again sooner and may go with the Dual. If it's a couple months, I'll wait. (Unless I can get my FlightBox fixed and then it won't matter.)
12/13/2019
Topic:
Stratus 3??

John Burnside
John Burnside
Posts: 215
Cal,

There is a plan! In fact, the Stratus 3 and 3i have already been integrated into the next version of iFlightPlanner for iPad, which will also include iFlightPlanner for iPhone. You'll receive an e-mail when that is released (version 4.0).

We do also already support the Dual devices in the current version of iFlightPlanner for iPad!
12/12/2019
Topic:
Stratus 3??

clocklin
clocklin
Posts: 14
Just wondering if there is any plan to support the Stratus 3 - at least for traffic and weather? (I'm having trouble with my Stratux and getting no response from FlightBox so I'm thinking about getting something else and the only other viable portable option seems to be the Dual XPS.)
11/21/2019
Topic:
Disconnect between METAR & NAVLOG winds

John Burnside
John Burnside
Posts: 215
Thanks for your post! We're always happy to answer questions.

The wind data used depends on the date/time of your flight. The National Weather Service produces wind forecasts at many different altitudes in six hour forecast increments and updates these forecasts four times per day. When producing a navigation log, the flight planning engine determines the best wind forecast to use for each part of your route. When your scheduled departure date is outside the timeframe of current wind forecasts, historical wind data will be used.

For example, if you perform initial planning for a flight five days from now, historical winds would be used. As you get closer to the flight day/time, we recommend generating a new nav log to utilize currently forecasted winds.

METARs are not used in generating nav logs because the wind data in a METAR is an observation from the past (typically within the last hour) rather than a forecast looking ahead to the actual time of your flight. TAFs would be more helpful as a forecast mechanism but don't include winds aloft data.

We're happy to investigate odd scenarios like the one you described in your post if you can provide further details, especially the departure, destination, route, departure date, and cruise airspeed. It can sometimes be difficult to reconstruct the result, though, as the forecasts may have changed.
11/21/2019
Topic:
Disconnect between METAR & NAVLOG winds

Flyhound
Flyhound
Posts: 2
I love flight planning with iFlightPlanner overall. My biggest problem is a big disconnect between the METAR data shown on the graphic map for my flight, and the winds in the NAVLOG. Just this morning, I'm planning a flight to KAWO and the METAR data on the chart shows the winds at KAWO to be 020 degrees at 5 knots. The NAVLOG produces for my flight shows the winds at KAWO to be 104 degrees at 14 knots. That's a BIG difference. It can't be explained by altitude because my flight is just at 1500' and the winds aloft shows the winds at KAWO to only be 149 degrees at 4 knots at 3,000'. So, where does the wind data for the NAVLOG come from?
10/18/2019
Topic:
A few questions from a new user.

randalforbes
randalforbes
Posts: 7
Thanks, I will prob fly this weekend, and check out the instructions.
Will advise on any issues.
Regards,
Randy
(take the rest of the day off... You've earned it. In fact.. You can have the whole weekend off. )
10/18/2019
Topic:
A few questions from a new user.

John Burnside
John Burnside
Posts: 215
No problem!

3) To show the waypoint popup info, use just a single light tap on the waypoint icon ("V" for VOR, "X" for a fix, etc.). If you hold down on the icon, it will jump up 1/2 inch to allow you to perform route rubberbanding. It jumps up by design so the icon is not directly under your finger, but rather above your finger to help see where you are moving the waypoint. Once you let go, the popup menu allows you to a) "Save As" - save the new location as a custom waypoint or b) leave the waypoint as a custom lat/lon location in the route or c) snap to a known waypoint from the list. If you unintentionally activate the rubberbanding feature, tap "Cancel" at the top right of the popup menu to snap back to your original waypoint. You can also tap and hold anywhere on a route line to insert an entirely new waypoint.

Now, the "Direct To" behavior changes depending on which route segment is currently activated, as indicated by the route segment highlighted in magenta. On the map (or in the nav log) tap on any segment to activate that segment. As you pass waypoints, the app will automatically activate the next segment. The active segment determines the instrument data, such "Distance to Next Waypoint", etc.

When the current segment is activated and you "Direct To" the next waypoint, it will insert a lat/lon waypoint for your current location, then create and activate a route segment to your next waypoint. I believe this is the behavior you were after. I believe you likely didn't have the current route segment activated. When you "Direct To" a previous route segment, it will change the flight destination as it assumes it is a diversion entirely from your intended route and destination.

4) Let us know if the "track up" mode, via the arrow icon on the left side of the map, achieves the desired behavior on your next flight!

We'll hold you to that promise on months! smile