Showing posts with label Training Tips. Show all posts
Showing posts with label Training Tips. Show all posts

06 March 2013

Review: CloudAhoy

Any time I have the thought "back in my day," I like to laugh at myself as I'm neither old in age nor in pilot experience.  After having used CloudAhoy on a few flights, however, I can't help the thought.  Reviewing my training flights, or flight performance in general was all manual, based off of what my instructor and I both remembered during the flight.  In some cases, one of us would scratch something down on a piece of paper as a reminder, but the post flight analysis was based off of our recollections of the flight, regardless of how our memories were jogged.

Enter CloudAhoy.

Where I once tried to re-fly the flight in my head and pull out the noteworthy parts through memory, I now have the flight recorded and tracked in its entirety.

When I first downloaded the application and looked at the user interface, I laughed.  There are four boxes to enter your data - tail number, your name, a co-pilot or CFI, and optional remarks - two areas showing your connectivity to data (3G or wireless) and GPS (internal or external), and two large start and stop buttons.  It's as simple as that.  Press start before you start the engine, and press stop when you're done.  It also has an auto-stop feature (enabled/disabled on the settings page), which helped the one time I forgot to press stop, but I couldn't tell you what triggers it.  I'm guessing it was either the GPS getting turned off, or just that it noticed I hadn't moved in so many minutes.  In any case, the initial user interface is extremely simple, which is what drew my laugh initially.  It was only later that I picked my jaw up off of the floor because of the amount of data that hit me post flight.

After the flight is where the magic is shown.  If you think the app looks too simplistic on the flight screen, wait until the flight data is shown on the debrief screen.  Switching from the iPad to a computer yields even better results, like the ability to utilize the Google Earth browser plugin for more features.  Either way, in the app or on a computer, the left panel allows you to view the flight, broken up into segments automatically by default.  If the app detects you are taxiing, or taking off, or flying a turn around a point, or a chandelle, or landing, it will automatically section that data off so that you can analyze that part of the flight on its own.  Automation is never perfect, so it sometimes grabs items that it shouldn't, but that hasn't caused any huge issues for me so far.  As an example, on my last flight it snagged one of my laps around the pattern as a left 360 (the yellow line in the picture).  Various colors help you to see the various maneuvers.  The blue lines are normal flight, with the white and amber being approach and touch-and-go segments, respectively.  All of these segments, again, are recognized automatically.




What about the non-standard, or very specific segments, you ask?


You may remember from the flight up to Harford County that I flew the GPS approach to the airport.  The entire GPS approach was shown as blue (normal flight - pictured above), as the app saw the approach as nothing out of the ordinary.  Trying to keep up with, and set the program up for every single approach out there would be nearly impossible.  Instead, the developer created a CFI tab so that you could add your own maneuvers.  This way, you can add the maneuvers you plan on flying before the flight, and your CFI or co-pilot can simply click on the begin and end buttons for each maneuver.  This allows you to track, color and name each maneuver so that you may analyze them separately.  Additionally, you can also track your hood time by adding that as a custom segment type.

The flight marker option allows you to simply mark a specific point in the flight to remind yourself later on.  While the option isn't as specific as defining a segment, it's a lot faster for situations that happen on the fly.  The note in the program states: "in flight, when you want to mark an event, tap the event marker and optionally write a corresponding comment on a piece of paper.  The tap will result in a number marker shown on the flight path at the current location.  Each tap, increments the number.  You can later discuss these comments with your student during the debrief."  Having this tab back when I was training for my private pilot license would have really helped me out.

The last tab is a settings tab that allows you to select an auto stop feature, disable broadcasting in flight, lock the screen, and set up your CloudAhoy account.

For those of you currently in any level of training, if your instructor does not currently use CloudAhoy, I would recommend talking to him or her about adding it as a tool for your flight training analysis.  It could really have a significant impact on the way that you learn and progress through training.  After all, one of the fundamentals of instructing, and therefore learning, is critique and evaluation, which this tool would only further enhance.

The only potential negative I found with the application was that it doesn't come with a manual.  Granted, we often joke that people rarely ever actually read said manuals, but one would still be helpful for reference.  To the developer's credit, however, there are several locations with information buttons explaining what the feature is meant to do.  The above quote about flight markers came directly from one of those in-app buttons.

Overall, it's a great app and you really can't go wrong with it.  Beyond that, it's free, so you have nothing to lose.  Try it out on your next flight and see how it can help you debrief after a flight.


26 December 2012

Two Sides to Learning

As the holidays draw to a close, I'm sure that there are a good number of potential pilots who will be going up for their first flights in the coming weeks.  I definitely looked forward to the gift certificates my family got for me at my flight school around this time of year.  For those of you who are, or know someone who is about to start taking lessons soon, one of the most important things to do is make sure to get everything out of each lesson.




When you first begin flying, your flight instructor may seem to be at the pinnacle of aviation knowledge, and I'm sure many of them strive to be, but that doesn't mean you shouldn't ask for clarification when you need it.  Part of becoming an instructor is learning the Fundamentals of Instruction (FOI), which is essentially the background theory of learning. One of the points that is made is that many instructors - both in and outside of aviation - stop teaching at the application level.  What that means is that many instructors teach you how to do something, but often neglect the reasons behind the action.  Some instructors are really great at making sure this is all explained, but nobody is perfect.

Having been an instructor of the information technology sort, I can say that sometimes it's simply an issue of forgetting to mention it.  Other times, I got so excited to show someone something, that the details got lost in the process.  Going against that grain, I'll now give you the reason why I'm telling you this: your learning is both the responsibility of the instructor and of yourself.

When I began training, my first flight instructor taught me how to fly power on and power off stalls to the point where I could do them flawlessly.  While it's good that I could fly them flawlessly, it was quite some time before I made the connection that power on stalls were training for recovering from stalls on departure, and that power off stalls were to recognize full stalls and to perfect your landing flare technique.  Had I thought to ask the reasoning behind it all, I would have likely known a lot earlier.



Despite what it may seem, there's often a reason behind all of the maneuvers the FAA asks you to be able to demonstrate on the checkride.  You're flying them in training because they're on the checkride, and they're on the checkride because they show you have control of your aircraft in varying conditions.

Power on, or departure stalls: recognizing control mush and stalls on departure.
Power off stalls: recognizing proper recovery for a fully stalled condition, and perfecting your flare.
S-turns, and turns around a point: properly adjusting for wind over a set ground track (think traffic pattern).
Simulated instrument time: limited training to help you out just in case you end up in clouds.

There are likely several more, but always remember that many of the things you'll be asked to do in training have a reason behind them.  If you don't understand why you're doing something, always ask!  If you're intimidated you ask your instructor, feel free to ask here.  If I don't know it, I'll go find the answer.

Twitter: @TheMintGreenLog
(You can use the box to the right if you're already logged into your account)
Facebook: http://www.facebook.com/TheMintGreenLog