For over a year now I have been running SD on an original iPad and enjoying the benefits of such a good piece of software.

However, I'm now using the latest version of the iPad SD (late Dec release) on the same iPad with iOS 5.1.1 and have found that the SD software constantly crashes out on me. I've tried this on the ground and in air, only to find the same results. Whether I'm in plan mode or GPS navigation mode, it just keeps on happening!

I've restarted the iPad, shutdown all other apps -- all to no avail. On today's flight in MVFR the longest that I managed to keep SD running in Navigation Mode was about 5 minutes and the shortest time was 15 seconds. According to the logs I have about 20 flights logged in the space of 90 minutes, mainly from "unknown to "unknown" , as I tried to restart SD in mid flight.

SD is a fantastic piece of software but I'm not able to rely on this latest iPad release whereas in the previous version I may have experienced a crash on the odd occasion and was happy to live with that.

I've be thinking about purchasing the iPad mini but will be putting that on hold and returning to the Navsgo as my main SD device. What a shame as SD and iPad ae made for each other.

Is anybody else experiencing the same problems?





Biggles -- EGKB

I've been researching this problem and have tried a number of sledge hammer approaches.

I decided to remove SD completely, install it afresh from iTunes and only use the chart data for UK. Everything else remained "as supplied (default) via the download"

What I have found so far is that when SD crashes it appear to be attempting to update the screen and that I can solve the problem of "crash after crash" by RESETTING LOCATION WARNINGS in the iPad SETTINGS GENERAL RESET menu which subsequently, on loading SD again, forces SD to open a new LOCATION SERVICES session.

Don't yet understand why this sequence seems to solve the problem but I have run SIMULATIONS & GROUND TESTS satisfactory after completing this sequence of recovery and remained error free for well over 5 hours.

Have yet to work out what sequence reintroduces the problem. Will keep you posted.

Would welcome a knowledge pool from anyone else who is experiencing these issues.

Biggles -- EGKB