ForeFlight’s route on CloudAhoy

 

ForeFlightRoute

When you import a flight track from ForeFlight , we now also import and display ForeFlight’s route. This provides you with a valuable tool to debrief “planned vs. actual”. You don’t need to do anything special to get this route – it’s part of our import process.

The example above shows CloudAhoy displaying ForeFlight’s route in magenta. The actual VFR flight followed the planned route from KISQ till KNMN, then deviated from the route to go around weather, and finally joined the route from RIPON to KOSH.

The following Q+A will explain it in more details.

Q: Remind me – how do I import flight tracks recorded by ForeFlight?
A: See this.

Q: I entered a flight plan into ForeFlight before takeoff, then modified it in flight. Which will be displayed in CloudAhoy?
A: The last one. CloudAhoy imports the flight path as defined immediately before landing, i.e., the path including all the changes made in flight.

Q: How is this feature related to CloudAhoy’s Intended Flight tool?
A: When we import the route from ForeFlight, we automatically create an Intended Flight segment, colored in magenta. After the flight’s import, you can of course modify the route, change the color, or delete it altogether. And you can use the magentaEye symbol to hide or show it.

Q: I see labels with coordinates. What do they mean?FF_intendedPathS2
A: Your ForeFlight path probably did not start or end at a known fix. See the example on the right; the pilot flew for some time (the southeast section of the flight) before setting ForeFlight direct-to KRUT. As a result, the displayed magenta route starts at a coordinate where the direct-to was set.

 

As usual, please email questions or feedback to us at dev@CloudAhoy.com.

Importing flights from Garmin G3X

If your aircraft is equipped with Garmin G3X avionics, you can now debrief your flights using rich high-quality flight data captured by the G3X. It’s very similar to debriefing Garmin G1000 flights, which we described earlier.

The G3X writes flight data into an SD card. To debrief the flight you need to import that data into CloudAhoy. This blog described how to do it.G3X SD Card

Logging the flight
Important: please consult your G3X manual and/or the aircraft’s owner for details specific to your aircraft.

  1. Before turning on the avionics, insert an SD card into the SD Card slot. If you have both a PFD and an MFD, the card should typically be inserted in the master, i.e., the PFD.
  2. During flight, the G3X automatically writes the flight data into your SD card.
  3. After the flight, remove your SD card. You now have the flight data in the SD card.


Importing to CloudAhoy

  1. Insert the SD card in a card reader connected to your desktop or laptop computer. The SD card’s folder will appear on the desktop.
  2. G3X DataLogOpen the folder. It would typically contain a data_log folder, and in it the flight’s data file in CSV format.
  3. Open a web browser and login to your CloudAhoy account.
  4. G1000-SDCard-5Click the Flight Import button. Enter the flight’s pilot names, tail number and optional remarks (you can edit all these later), select the CSV file with the data, then click Import.
  5. The flight now appears in your flight list, and is ready to be debriefed.


Debriefing G3X Flights

CloudAhoy can display the rich G3X data in graphical as well as numeric forms. The screenshot below has profiles showing a specific maneuver as the aircraft is pulling 2.4G while making a 62° left turn.

CloudAhoy can display about 40 different flight profiles for flights imported from G3X, such as OAT, IAS, EGT and even transponder codes used during the flight. For more information about advanced flight profiles, see G1000 and G3X flight data with CloudAhoy profiles.

G3X G

Your plane’s V-speeds

Our new release of CloudAhoy enables you to  specify your fixed-wing plane’s V-speeds.
The main benefit of doing so is for aircraft with “unusual” characteristics, such as vintage aircraft, “one-offs”, very fast planes, etc. In those cases you can enter the V-speeds, and CloudAhoy analysis will be more accurate.

Example
Last week Rob Waring was flying four traffic patterns in his 1939 Aeronca Chief, a relatively slow tail dragger. Not knowing the plane’s V-speeds, CloudAhoy calculated them, over-estimated Vs (stall speed) by 10 knots, and labeled most of the flight as an “unknown flight op” since parts of it were below stall speed – see 1 below. By specifying the Aeronca Chief’s V-speeds, CloudAhoy provided Rob with an accurate analysis – see 2 below.

2 flights1

I had a lot of fun debriefing Rob’s flight, since he had embedded in it a nice cockpit video. If you have a few minutes, click this, turn on the audio, and enjoy :)

Background: V-speeds and CloudAhoy
For safe flying, every pilot of a fixed-wing aircraft needs to know the plane’s V-speeds. Likewise, to analyze and evaluate the flight, CloudAhoy needs to know the V-speeds.

Until now, CloudAhoy estimated the V-speeds automatically from the flight envelop. This works well most of the time, but there are end-cases, such as very slow or very fast planes, in which CloudAhoy’s estimates might be off. The new feature enables you to increase CloudAhoy’s accuracy by explicitly providing the V-speeds.

“System” V-speeds
CloudAhoy has a “system” V-speed defined for several common aircraft types. If you fly a US or a Canadian aircraft, CloudAhoy will look up the tail number in the registry, determine the type and apply the “system” V-speeds if known rather than estimate the V-speeds. Over time CloudAhoy will have system V-speeds defined for more and more aircrafts types. vspeeds2

How to enter the V-speeds
You can enter your plane’s V-speeds in the “My Aircraft” section of the Account tab. The example below shows how a user is overriding Vr.vspeedsForm

Should you enter V-speed numbers?
In most cases, you don’t need to enter V-speeds – although it never hurts.

If you don’t enter V-speed numbers, CloudAhoy will typically analyze your flights correctly by either estimating the V-speeds, or by using the “system” V-speeds for your aircraft type.

There are two cases in which CloudAhoy’s analysis will benefit from your entering the V-speeds:

  • There are no “system” V-speeds available for your make/type aircraft, and it seems that CloudAhoy has made some errors in analyzing the flight – for example, it incorrectly labeled a section of the flight as “stall”.
  • There are “system” V-speeds for your make/type aircraft, but they do not reflect the numbers which you use. For example, you may prefer to rotate 5 knots above the aircraft’s “system” Vr. Or perhaps your specific aircraft has some modifications which lower the normal Vso

You can override any of the “system” V-speeds. Note that entering V-speeds affects only the analysis of your flights. It does not affect other pilots, even if they fly the same identical plane.

Let us know about your V-Speeds
If your plane type does not have a “system” V-speeds and you have entered standard V-speeds for it, please send us an email (dev@cloudahoy.com). It would help other pilots flying the same make/type.

As always, we welcome your feedback.

G1000 and G3X flight data with CloudAhoy profiles

For pilots flying a Garmin G1000 or Garmin G3X-equipped aircraft – we have just released a significant addition to your debriefing arsenal: extended G1000 or G3X data displayed as CloudAhoy profiles. It allows you to focus on such things as your power settings, engine information, and navigation accuracy.

See also Importing flights from Garmin G1000 and Importing flights from Garmin G3X.

In what follows I describe G1000 profiles. G3X profiles are very similar.

I  used the G1000 data of a VFR flight which I recently flew from KPWM to KBED on a DA 40. The flight itself was uneventful, but still it’s interesting to view the rich data.
In this post I am going to share with you:
Examples of debriefing G1000 data
“How to” – viewing G1000 data

Examples of debriefing G1000 data

Example – Navigation, horizontal CDI:  this was a VFR flight and on the approach to landing I had to follow a Citation on the right base. Even though it was a visual approach, I loaded the ILS-29 approach into the G1000. The horizontal CDI profile shows the CDI deflection as I was approaching the localizer’s center beam, then overshooting it (oops) before intercepting the center line from the other side.

G1000ProfilesAppr3

 


Example – Engine Data: I plotted the altitude, manifold pressure, RPM and CHT3 for the entire flight. Note the RPM=2000 during run-up, then set to max during the initial climb and during the final approach.G1000Profiles4P

 


Example – Radio: in some cases it might be interesting to debrief the radio usage. The following screenshot shows my aircraft about 5 miles from Boston’s mode-C veil when I switched to Boston Approach 124.4 on the active COM1. COM2 at the time was tuned to KBED’s ATIS, 124.6.
Soon after, I switched COM2 to KBED’s tower 118.5, then after landing to KBED ground 121.7, and finally after I parked I called for fuel on 130.8.G1000ProfilesFreqA

 


Example – Altitude vs. OAT: Here I plotted the Altitude and the Outside Air Temperature profiles of the departure climb from KPWM to my cruise altitude of 3000′. Turned out the temperature dropped at a rate of 2.7°C per 1000′.

G1000ProfilesClimb

“How to” – viewing G1000 data

The combination of the rich flight data from the G1000’s avionics with the flexible profile display of CloudAhoy provides a powerful debriefing environment. You can display any number of profiles simultaneously and move their timelines in sync, or watch them change during animation.

QprofilesMenu9uick reminder:

To display a profile, click (or tap) the profiles profilesMenuIcon menu icon in the Flight Profiles bar. You can select a standard profile (like altitude) as well as a G1000 profile.

We organized the data into groups. Read the list like you read classified ads in a newspaper: top to bottom and left to right.

As always, please let us know how this works for you. We would love to receive examples of your own debriefs using the G1000 or G3X.

Importing Garmin VIRB’s flight data to CloudAhoy

VIRBGarmin’s VIRB video camera is gaining popularity among pilots. VIRB also captures the flight’s GPS data, and that data can be imported to CloudAhoy for further debrief.

James Papafagos is using VIRB with CloudAhoy, and he was kind enough to write the bulk of today’s post. The stage is yours, James:

Uploading a .gpx file from your Garmin VIRB to CloudAhoy.

Connect your VIRB to your PC / MAC via USB and open the USB drive that should now be available.

Open the “Garmin” directory then open the “GPX” folder. You will see file named “Track_2014-9-23 145854.gpx” (for example)

It helps to have the directory view that shows the date modified so you can locate your specific flight if you have many recorded.

You can upload this file to CloudAhoy now by clicking “flight import”.

But… you probably have a flight longer than 20 min or so and have 2, 3 ,4 video clips and for each clip.. the VIRB created a new .GPX file. NOW WHAT?

If using a MAC, download the light version of Adze form http://kobotsw.com
You will use this to import your multiple .gpx files into one, and then upload that combines file to CloudAhoy.

Run Adze, just drag and drop all the .GPX files for your flight

VIRB 1

Select all the tracks by clicking on the first track, hold down shift and click on the last track

VIRB 2Detail

With theses tracks selected, click on the “glue” icon (or press “command – M”)

VIRB 3Detail

VIRB 4Detail

You will now have ONE track that contains all the data from the multiple tracks you started out with.

Now, go to File, Save As.  to save the new file.  This file can now be uploaded to CloudAhoy!

Thank you James!

As always, any feedback is most welcomed.

Improvements in flight profiles display

We enhanced the flight profile display in the Debrief tab; it is now possible to:
– undock a profile, move it and resize it,
– drag the crosshair to move the timeline.profilesOvrS

profilesMenu

 

To display a profile, click (or tap) the profilesMenuIcon menu icon
in the Flight Profiles bar, and select the profile from the list.

 

Profiles: undock and dock
Initially a profile is displayed in the Flight Profiles section. This is called docked state. You can undock a profile by clicking the undocking icon profileDockIcon.

Once undocked, a profile can be moved and resized – see the illustration below. You can also dock it back in the Flight Profiles by clicking the docking icon profilesDockprofilesDragAreas350

To close a profile, click its X icon on the upper right, or unselect it from the menu.

Drag the crosshair to move the timeline
Each profile has a vertical line to show the current time. You can drag the line to move the current time, which is exactly equivalent to moving the timeline’s slider – but allows for better accuracy.

Persistence
If you are the flight’s owner (i.e., one of the pilots), each profile’s size and location is saved, and will be restored the next time you debrief the flight.
BTW, we now also save segment information windows segInfoIcon, and the PIP window.

Example
The screenshot on top was obtained by analyzing the flight in XC mode (click the XCMode button in the Flight Segments bar), selecting only the Approach and Final segments (see here about segments isolation) and displaying airspeed in docked state and altitude in undocked. Such a display can help in debriefing how stabilized the approach was.