IFD Software Release 10.2.0.0

This is simply one example that describes IFD behavior.  What if the Missed Approach hold was in a different direction than the PT where you may need different altitudes for the protected airspace due to terrain, towers, etc?  When you fly the VOR RWY 9 into RAL then the VOR into AJO, it completely deletes the Missed Approach hold.  It maintains the HILPT for the next approach, but this time it is 1500 feet lower than it is supposed to be, and the hold is on a different heading (although not by much) meaning the protected airspace is not the same.

If you have the same waypoint twice in a a row in the flight plan (but at different altitudes) what is the navigator supposed to do after you pass the waypoint the first time (at, we hope, the first altitude)?  Is there a holding pattern at that waypoint while you climb or descend to the new altitude?  In that case wouldn't a holding pattern between the waypoints make more sense than a discontinuity?  On the other hand, how does the (lateral) navigator know when you've made the right number of turns in the holding pattern and that your next pass at the holding fix is in fact the exit waypoint?

Just seems like more questions than answers to me.

In response to why this isn't an AD, I would say that if 2400' is a safe altitude for an IAF, why wouldn't it also be a safe altitude at the same location on the miss?  Sure, there could be a traffic conflict but there should not be a terrain or obstacle problem.  And if we're worried about traffic, well I'm not exactly comfortable holding at 3000' while other airplanes are flying the approach only six hundred feet below me.  Especially if you consider that 2400' is probably a MINIMUM altitude at the IAF, not a mandatory altitude.

AviJake wrote: 47. 47.  Improved Published Holds – there were some subtle uses of published holds that we did not know about operationally.  This change allows selection of the type of hold to be used when there are multiple published holds on the same database waypoint.

Indeed--thanks for the update.  Fingers crossed...

We have a bid to do the Android work that is being re-worked by the bidder.  If that comes back attractive, we'll pull the trigger.   I met with him at Oshkosh and we're both optimistic.   We'll see.

n7ifr wrote: will we be able to do our own software download & update to our X40's, or must it be accomplished at a dealer??

In between those two.

If they follow past practice, the upgrade (which is an alteration to the product) must be done by either a repair station (i.e. avionics shop/dealer) or by an A&P.

That said, an A&P has the ability/authority to supervise work, so if your A&P is comfortable with it, he might agree to supervise you doing the work and then make the required log entry for the activity.

David Bunin

... anticipating v10.2... so does anybody know - will we be able to do our own software download & update to our X40's, or must it be accomplished at a dealer??

Very excited about the WX-500 stormscope test page in 10.2.  

Right.

I see convincing evidence of activty leveraging 10.2 by third party vendors.

Well, my bird is in the shop now for the next two weeks getting 540/440/340 installed (alas without 605->605A), so it would be great if it can come along before 1st Aug. Fingers crossed!

Steve is on vacation. He will be back in a few weeks, so his response will be delayed.

But Steve did say that 10.2 would not be released before IFD550. 10.2 is first IFD550 release and they can't be certain 10.2 is finished until IFD550 is cert'd by FAA.

Vince,

Back on April 1, 10.2 was "in final company testing".

Are you guys assuming IFD100 and FF or FltPlan Go on different tablets? I sort of though that both apps would be running on the same device and any transfer could be internal, not needing wifi.

Nice David.

n7ifr wrote: We are told that the IFD100 will allow home flight planning, and easy transfer to our panel IFD's.

... expecting and hoping are different.  We are told that the IFD100 will allow home flight planning, and easy transfer to our panel IFD's.

Steve,

Whoa, there was a lot in there.

Great, thanks. Makes it a valid option for IFR Helicopters now.

I don't see Helicopter approaches on the list, was advised it was coming on 10.2, has that been relegated to 10.3?

AviJake wrote: I'll probably put the IM up a week or three prior to cert.

I would advise against that.  It's never a good idea to circulate nearly-approved data.  Just wait for that stamp and then let fly.  There is minimal benefit to the marketplace by having preliminary data now rather than approved data in a matter of days or weeks.

I am reluctant to publish a draft of the Install manual since that is FAA approved data as opposed to the Pilot Guide which is not.