Good afternoon! I wanted to update you on our priority items on the FlyQ Web flight planner. This message below was also posted on AOPA's forums.
Also, wanted to address the comments on the temporary interruption of fuel prices on the AOPA Airports pages. AOPA simply transferred to a new service provider for fuel prices and it took us a couple of days to make the transition. They are back up and available as they were previously.
Please let me know if you have any other questions,
Katie Pribyl
--------------------------------------------------------------
I want to provide all of you an update on our efforts to get the FlyQ Web planner up to the high standard you expect from AOPA. We launched this service too early. That is my responsibility and for that, I apologize.
We are working seven days a week to get the flight planner fixed and I thought you may appreciate some insight on how we are attacking the problem and our order of priority in addressing issues and releasing features. Our first priority is to repair malfunctions and provide better directions for users. Therefore we are currently concentrating on the following:
1. The FAA flight plan form. The problem is that you cannot edit the fields that the planner has produced. We are making each field in this form editable to allow users to refine the form before submission. We expect this to be released soon.
2. Nav Log. The Nav Log was not in kneeboard format and had a number of inaccuracies. As an interim fix, we have provided a Nav Log that is in knee board format and we have fixed all of the inaccuracies. I understand that this Nav Log is not as convenient as the AIFP version, so we are working to duplicate the Nav Log that we produced In AIFP. We expect to release the new Nav Log soon.
3. Help documentation. We are producing three types of help documentation - a user guide, contextual help, and video tutorials.
4. Restoring saved AIFP flight plans. We have recovered copies of stored routes for all members who logged into AIFP in 2011 and/or 2012. We are working to format this data and then import it into FlyQ Web. When successful, these routes will appear in the “Recent” tab in a box called “Favorites”. We expect this to be released soon.
5. Ability to edit a flight plan after it is created. This will allow users to change fields - like routing and altitudes - during the creation of a flight plan without starting completely over with a new flight plan.
After these areas are successfully addressed, we will continue to fix reported bugs and look to further enhancements.
Addressing a few that have been mentioned here on the forums:
1. User defined maps. I too miss the ability top start with a topographical base map, and add layers like navaids, airspace, roads, and state boundaries. This is functionality that we need to develop and will take longer than the issues above.
2. User defined waypoints. The FlyQ Web system does not currently allow the creation of User Defined Waypoints. We will work to develop this functionality. User Defined Waypoints used in an AIFP stored route will work when those plans are restored.
3. TFRs. TFRs are designed into the current system. We have witnessed a bug based on reports found on this forum. We are working to fix this bug immediately.
Many of you have been very helpful in alerting us to bugs and deficiencies in the FlyQ Web flight planner. We appreciate your help and input. The most efficient way for you to continue to communicate this information with us is via email at
flyqhelp@aopa.org.
Again, I apologize for the inconvenience and frustration that we have caused with our move to the FlyQ Web flight planer. We will continue to work to provide you with a great flight planning tool.
Chris Ward