CloudAhoy App release 1.7 — today

It’s in the app store as of today. This is a maintenance release, fixing three things:

– Better upload of data especially for iOS devices that are in Airplane Mode.  If you ever had a situation where flight was held in your iOS device for too long, it is now fixed.  Well, it’s fixed even if you never had the problem : )

– A recognition of Dual XGPS150 devices.  This is for display only, because even in pre-1.7 the data from Dual was used correctly.

– Devices left running for days.  This could happen in pre-1.7 when users started logging, and CloudAhoy waited patiently for them to takeoff, sometimes days.  Or it could happen if users have actually landed, but turned off auto-stop and never turned off the logging manually.

I plan to have the next app release in late April or early May.  It will have several new features, plus run in native mode on iPads.

The new Google Earth Plug-in is crashing on Macs

Sad Google

The dark side of Earth

A couple of weeks ago Google released their Google Earth version 6.2.  Unless you opted out, they upgraded your plug-in software automatically.

The previous version had several bugs that affected CloudAhoy users (and I, among many others, have reported and urged them to fix these bugs).  The bugs have been fixed, so 6.2 is good news.  But with the good news came some bad ones: the new version crashes a lot while running cockpit view animation.

I have received reports  from several users, all running on Macs.  Hey, are there Windows users out there who get this problem too?

When the problem happens, do like Google says: reload the page.  It helps… until the next crash.

I verified: this problem affects all the other camera movement applications that I tried, including Google’s own.  That’s  bad news, because if the bug were in CloudAhoy, I would have been able to fix it myself.

I found that if you get frequent crashes in one browser, switching to another is likely to help.  Today I failed to get the screenshot above while running in Safari – it worked beautifully for 15 minutes.  I switched to Firefox, and it crashed immediately.  Other days, it crashes a lot in Safari but not much in Firefox or Chrome.

I could not get the plugin to crash on Windows XP (both IE and Firefox).  Maybe because it runs a 32-bit plugin.

A bug can be both funny and annoying

Imagine yourself building a plane kit.  This is a huge endeavor in terms of the time, money and energy you devote to it.

At a certain point, the plane is ready to be tested, and you are ready to be your own plane’s test pilot.  Living in the US, you must register the plane with the FAA, which is not a trivial procedure.  After the registration process, you receive a tail number from the FAA, and anyone can type this tail number in the FAA registry and get information about the plane’s builder, namely you.

So far so good.  Now you register to CloudAhoy because you want to debrief your flights.  You enter your tail number, and CloudAhoy adds this tail number to the list of your planes, except, ooops, it lists someone else as the builder!  You have spent thousands of hours on building this plane, you registered it, and someone else is listed as the builder!  What is going on?

This happened yesterday to a CloudAhoy user.  The reason?  A bug in CloudAhoy. CloudAhoy incorrectly assumed that a given plane type is always manufactured by the same manufacturer.  For example, plane type 182R is always manufactured by Cessna, and S-76D is always manufactured by Sikorsky.   Obviously this is not the case with plane kits.  Turned out that a CloudAhoy user, call him A, entered his Lancair kit’s tail number, and CloudAhoy learned from the FAA’s registry that A is the manufacturer of that specific model of Lancair.  Then another user, B, entered his plane’s tail number, and the builder’s name was A.

Awfully sorry, B.  It will be fixed.  I can only imagine how annoying this could be to you.

Cockpit View — Released!

The Cockpit View is now released.

Select Cockpit View, click Play, and enjoy (click the “?” icon for more information).

Many thanks to all the beta users who have sent me encouraging emails, useful comments, and some “!” signs to spice the whole thing up!

A Steep Turn

A Steep Turn, Cockpit View

Cockpit View (at last!)


CloudAhoy’s cockpit view, including cockpit view animation, is now available in beta.

Be warned: it’s addictive.

To make it more fun, I now initialize the timeline’s slider to be the beginning of the takeoff roll (i.e., after the taxi to the runway).  So you can click Debrief, then set Cockpit POV (wow! you’re on the runway!), then click play, and watch the plane take off into the inviting blue horizon.

Many CloudAhoy users have asked in the past for a cockpit view.  If you are one of them, you probably received from me a polite email (recycled in part, to help save the planet) explaining why such a thing would be misleading because of all the unavoidable errors in calculating the displayed plane’s attitude.  That explanation was convincing, at least for me, and therefore I never implemented the mode.

Until now, that is.  I realize now that this mode is actually rather cool, and that the attitude calculation turned out to be pretty realistic (the link above explains some of the limitations of this mode).

What made me decide to do it?  I think it was a last-straw type of thing — last Friday I received yet another request to do it.  I was sitting at my computer at 2 PM, and I thought that I have a few hours to play with this before our friends come over for dinner.  Luckily Tani, my wife, was the designated cook that afternoon, so I could have several hours of hacking.  After dinner (excellant dinner BTW) I connected my laptop to the TV, and showed the hacked version to our guests, as an affordable replacement for a more robust form of entertainment such as a juggler on tightrope, or leopards jumping through rings of fire.  The guests liked it so much, that I decided to spend a week and do it right.  Soon I was doing physics on a legal pad, deriving the formulae.  Two days later I flew the Arrow, mostly for practicing Lazy Eights, but also to create a table of pitch angles in various configurations — as a way to calibrate the mathematical pitch model.

It’s still unclear to me in what ways will this mode aid in debriefing a flight.  But I am convinced that it’s as useful for debriefing as it is for just having fun.  As I was playing back some landings of mine, I did notice one from several months ago that was high above the glide slope.  I must have had four white PAPI lights in my face most of the way down on that landing. Maybe it was a case of being number 2 after a heavy military plane (my home airport is also an AFB), or maybe I was just being sloppy.  I could get the same information about the steep approach without the Cockpit POV of course.  In fact, turning the “further analysis” checkbox, CloudAhoy measures and reports the exact slope.  But I must admit that seeing the steep approach in the Cockpit POV mode gets the message deeper under one’s skin, more than the 5.7° slope number.

I kept playing back other flights, such as a flight that I flew with my son in valleys in the Rutland Vt. area, or a flight over Lake George.  It’s very entertaining, and looks pretty realistic albeit without a sound track.  One benefit of playing a flight in the cockpit’s POV is that you can click the 10x button and pretend that your humble GA plane is now a mighty F16.  Well, sort of.

I’ve had Google Earth crash on me at times when running this mode.  I think it crashed much more in Safari than in all the other browsers combined (Firefox, Chrome, IE).  Maybe it’s just my setup.

In a previous post I promised to write about Lazy Eights.  I never got to do it (and I’m not going to use the  pun that I was Lazy).  Next week we’re going on vacation, and I will be flying again in February.  Maybe I’ll write about the Lazy Eights then.

Soup University

I needed 4 instrument approaches for my IFR currency, which expired last month.  I flew three approaches last weekend, wearing foggles and with my friend Itay in the right seat.  That flight was mostly an exercise in controlling the autopilot on the 182’s G1000.  I’d give myself a B+ on my mastery of the autopilot: several times I thought that the autopilot was flying the approach, when in fact it was trying to hijack the plane, probably to Cuba, and I had to disable it.  I felt like Dave in “2001, a Space Odyssey”.

I flew three additional approaches today.  The ceiling was between 400’ to 800’, the constant pouring rain added strange sound effects, the windows were foggy, and my CFI John was in the right seat.  I wanted to take an Arrow for this flight, but it is grounded, so I flew a Warrior.

Although I had an iPad running ForeFlight with geo-referenced approach plates (and obviously running CloudAhoy as well), and although the Warrior has a Garmin 430, I decided not to use them for situational awareness, and use paper only.  There’s something pure and unspoiled about doing it that way.

Flying with John is always super educational. Flying with him, I think that on average I learn something new every 14 minutes; but in this flight the rate was even higher.  I started the engine and put it on 1000 RPM, then as I was dialing the frequencies in the radio John asked me if I looked at the engine’s RPM.  I looked, and it dropped to 900.  Ah, I said, I should use the friction lock to keep the throttle in place.  I reached out to push the throttle, but John suggested that instead I try carb heat.  I set carb heat and viola, in two seconds the RPM came back up to 1000.  I built ice in the carburetor! If I had flown the Arrow or the 182, I would not have learned this – both have fuel injection.

The first ILS approach was uneventful.  Not my best, nor my worst ever.  We broke out at 600’, and I could see the runway lights straight ahead although the runway was still in the mist.  Breaking out from a cloud base and seeing the runway lights straight ahead is probably the most rewarding price in aviation!  John asked me not to look outside and fly the remaining 200’ to the Decision Altitude looking only at the panel.  I flew the missed, and immediately got sucked back into the soup.  I sometimes wonder whether the term “soup” was coined in Boston, where the locals eat Clam Chowduh (myself, I don’t care much for this local delicacy).

On the second approach, which was a Localizer approach, John asked me if I ever flew partial panel in IMC.  No I didn’t, and today was therefore my first time.  John covered both the AI and the heading indicator, and my flight started to look like a drunken pilot’s.  John suggested that I use the 430’s compass-like display, and I did.  As I was trying to manage the situation, John kept asking me questions.  For example, if I wanted to use the magnetic compass, what type of errors should I be more concerned about: turning errors, or acceleration errors?  I figured that since I am not accelerating much in this flight, the correct answer would be turning errors.  No, said John.  He took the yoke and showed me what happens to the compass when the plane’s airspeed changes as it climbs or descends a mere 50’.  If you want to fly in IMC using the magnetic compass, said John, you better train for it.

I kept flying while John kept asking me a never-ending stream of questions.  What would be the next heading from ATC?  Where are we now relative to TAYUB?  What’s your primary gauge for pitch right now?  I think that in addition to teaching me, John was trying to saturate my brain, the way it would be in a real partial panel flight in IMC. Obviously, if you really lose your vacuum while in the soup, it’s a good enough reason to declare an emergency.

The third and last approach was ILS, still with the two gyros covered, and John suggested that I ask ATC for a no-gyro approach.  I have read about it once, but never practiced it, certainly not in IMC.  It was the coolest thing.  The controller acted in a very un-Bostonian manner, and worked with me with a lot of patience.  As I was flying, I said to John that the controller must be frustrated having to do this extra work, but John calmed me by saying that the controller probably appreciates the opportunity to practice this as well.  The idea in a no-gyro emergency is that instead of giving you vectors, the controller tells you when to start to turn and when to stop turning.  Looking at the CloudAhoy track above (with the published ILS approach overlay), indeed both of us learned during this approach.  Both he and I improved as the flight went on.

John then taught me another thing (I lost track of how many new things I learned).  Bend my leg so that the knee is higher and almost touches the yoke, rest my hand on my knee, and then fly the plane with my thumb and pointing finger.  This is so relaxing (assuming that the plane is well trimmed).  And is very precise as well, exactly the extra precision that the situation required.  I also used the pedals a lot for fine heading changes.

After intercepting the localizer, I started to chase the needles.  “Chasing the needles” is obviously a bad thing, something to be frown upon, but I think that without the vacuum instruments this is essentially what one does.  Looking at CloudAhoy’s altitude and course profiles below, it’s obvious that my chasing of the needles could have been done much better.

All in all, I was pretty happy with my performance, given the rust level and the workload.  CloudAhoy’s segments list, above on the left, shows that on my first ILS approach the missed was taken at 426’ (the minimums are 383’), and the missed on my LOC approach was taken at 721’ (the minimums are 720’).  The chasing of the needles on the third approach is shown in CloudAhoy’s profiles on the right.  While flying it, it did not feel as dramatic as it looks in the profiles, or as it looks in the ground track.  It’s one case where CloudAhoy has a sobering effect.  The two things that I am taking from this segment of the approach, thanks to CloudAhoy, are: (1) don’t turn more than 1/2 standard rate, (2) have patience: turn a little, stop the turn and see where the needle is going.

The rapid rate of teaching me new things did not end while taxing back to the ramp.  As I cleared the active, I pushed the VFR button on the transponder to set it to code 1200.  John asked me: supposed you pushed it by mistake, what’s the best way to put in the previous transponder code?  I did not know of a quick way but there is one (on that specific transponder): you long-click the button, and the old code comes up.  John said that it’s the same on the G1000.  Good to know!

But an even more important educational moment was 10 minutes earlier, when I was established on the localizer and Boston handed me over to the Bedford tower.  I repeated the instruction “6 November Delta, to tower”.  Before I clicked the frequency flip-flop to talk to the tower, John keyed the mike and said in his quite voice: thank you very much for your help.  The way he said it, it was clear that he actually meant it and was not only polite.  The controller said in a cheerful voice, you’re welcome sir.