Print Page | Close Window

IFD540 Certification Status

Printed From: Avidyne
Category: Avidyne General
Forum Name: IFD 5 Series & IFD 4 Series Touch Screen GPS/NAV/COM
Forum Description: Topics on Avidyne's IFD 5 Series and IFD 4 Series Touch Screen GPS/NAV/COM
URL: http://forums.avidyne.com/forum_posts.asp?TID=238
Printed Date: 28 Mar 2024 at 11:34am
Software Version: Web Wiz Forums 12.01 - http://www.webwizforums.com


Topic: IFD540 Certification Status
Posted By: AviJake
Subject: IFD540 Certification Status
Date Posted: 14 Oct 2012 at 8:45pm
I hope to use this new thread as a location to provide periodic updates on the IFD540 product and specifically on it's progress toward FAA certification.

I'd like to ask that any product specific questions on features and the like are asked in other pre-existing or newly-formed threads and we keep this particular thread focused on the cert progress.

In this thread, I'll cover hardware and software progress as well as flight test and lab test milestones reached enroute to TSO and STC approvals.  To the extent that it makes sense, I'll post target dates and readers can use this thread to independently assess progress towards certification.

At this point, we have 12 IFD540 units under test that are used in our four test aircraft, three integration test labs (ITL), and in the environmental test lab that we're renting time in.  I personally fly the units 3-5 times per week and use them in an ITL every day.    This is going to be a great product when we can get it in your airplane.


-------------
Steve Jacobson
sjacobson@avidyne.com



Replies:
Posted By: tony
Date Posted: 20 Oct 2012 at 7:28am

Steve, I appreciate your effort in being as transparent as possible without exposing too much information to your competition.  I think all of us who have invested in this development would like to share in the excitement.  Is your plan to get the hardware qualified first, so you can gear up the factory to make those initial deliveries to people like me with the software qualification to follow?  Or will both the hardware and software be certified as a unit?



Posted By: AviJake
Date Posted: 20 Oct 2012 at 9:06am
Hi Tony,

It's a little of both.  By that I mean there is no notion of FAA certification for a hardware unit without accompanying software for a product like this.

Hardware qual has two principal elements to it.  If the hardware contains what are called "Programmable Logic Devices" (ours does) or other similar types of equipment, then there is a standard that we must show compliance with (DO-254).  That is a rough analog to the software standard (called DO-178).  The second part of hardware qual is the environmental qualification.  Environmental qual is governed by a standard called DO-160.  DO-160 will drive us to various vibration, heat, cold, altitude, humidity, RF emissions and susceptibility, etc types of tests.  We are running both the DO-254 and DO-160 hardware qual efforts in parallel.  The environmental one is typically several months long (lots of tests, some with long durations) and the outcome of each is that we produce two Hardware Qual Reports that are submitted to the FAA as part of the overall compliance data package.   We'll turn those reports in before the final software and flight test reports and while the FAA will likely review and comment on them, they won't likely "sign off" on them without the accompanying software reports.

I'm also not sure how well understood the overall cert process is but we talk of it in terms of "TSO" and "STC" efforts.  Each of the TSO and STC cert efforts  have elements of hardware and software data to them but the easiest way to think of that is:

TSO - take this to mean the equipment has been shown to meet various instrument technical standards (e.g. Moving map, traffic display, lightning sensor, FMS, etc).  In the case of TSO, we have demonstrated compliance to the three hardware and software standards too (DO-254, DO-160, DO-178).

STC - this is the approval for installation in an airplane.   You can have TSO for a product but if you don't have STC, you have no approved basis to install that gear in an airplane.

I expect to report on all of those milestones in this thread (254, 160 and 178 tasks, TSO, STC and flight test milestones, etc).

So that was a long-winded way of saying that for all practical purposes, both the hardware and software get certified as a unit.  But, that doesn't mean we won't be building up a bunch of units in the factory.  We'll be sufficiently through the hardware qual far enough ahead of the software qual that even though we'll technically build up the units at risk, the risk of having to disassemble and redo some hardware element will be very low.   That way, we have a slew of built up units awaiting the final TSO and STC approval such that the day after we have those certs, we can be shipping units.

Make sense?


-------------
Steve Jacobson
sjacobson@avidyne.com


Posted By: tony
Date Posted: 21 Oct 2012 at 9:40am
Perfect sense!  Thank You.


Posted By: Victor
Date Posted: 08 Nov 2012 at 1:30pm
Steve,

Can we have an update please?  Its been almost 3 weeks.

Thanks,

Victor


Posted By: tony
Date Posted: 20 Nov 2012 at 7:48pm
you still on schedule to complete by the end of the year?


Posted By: AviJake
Date Posted: 29 Nov 2012 at 9:28pm
IFD540 Development Status (29 Nov 2012):

We've made very significant progress in the last few months but we have a few more months of work ahead of us.  Here are a few updates on our status:

  • We have about 12 units built up that are being used for various purposes to include flight test and software development and hardware environmental qualification;
  • We are flying the units in multiple aircraft.  I know I'm personally logging about 30 hours per month in-flight with the IFD540 and I'm just one of a few test pilots.  Most of our flying is based out of our Lincoln MA location and our Melbourne FL location;
  • There are 174 external, 3rd party devices the IFD540 must integrate with.   We're complete with about 115 of those devices, partially complete with another 35 or so and haven't started on the rest but we believe most to either be simple or rare in the field;
  • We are extremely happy to have retired two of my top two technical risks - we are pulling about 20% less current than we had estimated based on our design (this was one of the two risks) which means we are generating a proportionally smaller amount of wattage, which in turn means our unit is meaningfully cooler in temperature than we had anticipated (this was the other risk).   In fact, at maximum wattage (e.g. max map depiction, VHF transmitting much longer than typical, etc) still means our unit is the same as ambient temperature.  This is huge and much cooler than all surrounding units and much cooler than the G-530s that it may be replacing;
  • We begin official, for-credit environmental testing on Dec 15th.  This is the last meaningful task left on the hardware side of the product.  We have conducted in-house risk mitigation dry runs of all that testing and passed with flying colors;
  • A key member of our flight test/development team just received his DER ticket from the FAA and they (the FAA) are delegating more approval authority to Avidyne - this should help with end-game schedule control;
  • In addition to the actual software creation/functionality, FAA "certification" includes showing compliance with the DO-178B software development standard.   This has "gobs" of effort associated with it that only a true software engineer can appreciate (and in some "sick" cases, actually enjoy).   This is where the majority of the remaining work and schedule impact reside.  In other words, once we go "code complete", we still have man-weeks of process compliance/artifacts work to complete; 
  • The crew is working in a full-court press manner and we're completely heads down trying to finish the product.  We understand it is in our extreme best interest to get this done and shipping as soon as feasible.  This is an all-consuming effort so any apparent radio silence on our part is due solely to that intense focus.  I wouldn't read any more into it than that but please don't hesitate to use this forum to press for updates if you think you need to hear more.


-------------
Steve Jacobson
sjacobson@avidyne.com


Posted By: edanford
Date Posted: 01 Dec 2012 at 7:14pm
How close is the Simulator to release to early adopters?


-------------
Ed


Posted By: tony
Date Posted: 05 Dec 2012 at 7:10pm

So Steve, if one was planning a cockpit upgrade around your 540 deliveries, hypothetically of course, when would be a good time to plan on taking one’s airplane being down?  Feb?  Mar? Apr?



Posted By: brou0040
Date Posted: 14 Dec 2012 at 7:42pm
When future releases with new features are certified, what is the upgrade process?  Will we have to take the plane to a dealer or can we install the update?  Will any (flight) testing be required?  Will there be any associated costs to upgrade?

Thanks,
Jayson


Posted By: AviJake
Date Posted: 15 Dec 2012 at 9:50am
Hi Jayson,

The upgrade process should be a breeze.  Every bit of software in the IFD540s are field loadable via the USB port on the front of the bezel/unit.  That means the software can be uploaded using a USB thumb drive.  We do it all the time during development and the whole process takes about 5 minutes.

This next part is not a done yet but, it is trending very nicely.   The FAA has just issued updated guidance about what types of actions the individual owner can perform on their aircraft and it appears that software updates, if using an approved Avidyne-supplied service bulletin, may (and I stress the word "may" right now) be permitted.  We are seeking clarification on that one but if that's true, that would even save the time/effort of you having to fly to an approved dealer to have that work done.  If, this new FAA-allowed owner update effort is not permitted for software updates, then it is still a simple process but involves your dealing loading, and signing off the software in accordance with the service bulletin.

The need for flight  testing before update signoff will depend on the nature of the update or functionality added.  The vast majority of the envisioned updates would not require a flight to sign off.

As for cost to upgrade, that too will depend on the nature of the new content.  Generally speaking, a bug fix load is no cost but a feature add load may have some cost associated with it.


-------------
Steve Jacobson
sjacobson@avidyne.com


Posted By: tony
Date Posted: 15 Dec 2012 at 3:19pm
Thats awesome!!!  You guys do seem to focus on customers.  Please dont stop. 
Will the 28 day nav updates be loaded using the same port?


Posted By: AviJake
Date Posted: 15 Dec 2012 at 5:50pm
Yes, the Nav, Charts and Obstacle data is all loaded through that USB port on the front of the bezel.

Why we don't encourage it at all, the system will also let you fly with expired data, it just puts an "Expired" watermark on out of date charts.


-------------
Steve Jacobson
sjacobson@avidyne.com


Posted By: tony
Date Posted: 23 Dec 2012 at 9:35pm
With only one more week left in 2012, has all the test been completed and has all the data been submitted to the FAA, such that we are only waiting on approval?


Posted By: AviJake
Date Posted: 23 Dec 2012 at 9:48pm
No.  We still have a bunch of work still to go.  That being said, we are very confident we'll have cert and be shipping in 1H 2013.

-------------
Steve Jacobson
sjacobson@avidyne.com


Posted By: tony
Date Posted: 31 Jan 2013 at 5:27am

Tomorrow is the first day of the second month of 2013; I thought this would be a good time for all of us to get a heading check. Steve would you please provide us status where we stand  in the certification process? Did we get all of our flight testing completed? Have all the reports been written and submitted?  What’s left to do?



Posted By: AviJake
Date Posted: 31 Jan 2013 at 1:59pm

IFD540 Status Update (31 Jan 2013):

We are making terrific progress but we are still a few months away from being done.   There are a lot of ways to slice this up but in general, here is a breakdown of the various efforts underway to get the IFD540 certified and installed in customer airplanes:

Hardware Qualification:

We are still undergoing the official for-credit hardware qual of the units.  This consists of three sub-categories.  We have to conduct all this testing on the fully assembled and representative units.  Accounting for potential snags, I bet we have 8ish weeks ahead of us on this effort.

1.       Environmental Qual (DO-160) – this is progressing well.  This part of testing in which the unit has be to subjected to all kinds of environmental testing to include extreme heat, and cold, altitude testing, humidity testing, RF emissions testing, RF susceptibility testing, vibration testing, salt spray, dust, dot, dot, dot.  This testing gets conducted in a special environmental test lab and the test results get submitted as part of the FAA approval process.  We’ve been in that testing since early December and have a few more weeks of that effort ahead of us.

2.       Complex Electronics Qual (DO-254) – we have conducted our own not-for-credit testing to ensure we have no problems but have not yet started the formal qual testing yet.  When we do, it should take a few weeks until completion.  For the techies in the audience, Complex Programmable Logic Devices (CPLDs) is where a lot of the embedded logic is conducted and we just have to show nothing unexpected or nefarious happens in that hardware/firmware.

3.       Minimum Operational Performance Standards (MOPS) testing – so far so good but not quite done.   The FAA specifies minimum performance requirements for hardware (e.g. GPS, VHF, etc) and each one of those standards comes with pages (and sometimes pages and pages and pages) of tests that are specified and must be run and shown to meet published pass/fail criteria.

 

Software Qualification:

I think the simplest way to think of this is a two-part effort – Development and Formal Qualification.  Both are governed by an FAA-written software process called DO-178.    This is a requirements-based process that involves all aspects of software development and cert starting with top level product definition and decomposing that into smaller and smaller and more detailed and more detailed written requirements, then the software coding to embody those requirements and then a lot of different kinds of testing designed to validate all the requirements are correct and fully embodied by the code, and conversely, the code doesn’t have anything in there that isn’t governed by the requirements.  A related type of testing is to show that every possible path the code can take results in a known or deterministic end state.  This is man-years of effort for a product of this size and complexity.   It is also an iterative process in that inputs from flight test and the FAA and sometimes the customer base, can be cause for rework and then a lot of those steps must be re-performed to re-validate the changed code.

We don’t run this in a serial manner.  In other words, we don’t wait until all the code is done before we start the validation testing.  We are well into the formal qualification of the code but some parts of the code are still changing as we fly it a lot and find things that simply must be changed.  The closer we get to the cert finish line, the higher the bar is that a potential code change must clear before we put it in.

This effort is running in parallel with the hardware qualification.   It’s all relative but flight test is still finding a number of areas that need to, or we want to, change in order to deliver a truly kick-ass product.

Past experience says it’s wise to be conservative on estimating the impact of these changes on schedule so I would estimate we have a few months of work still ahead of us before we declare the code to be 100% done.

 

Flight Testing:

Of course I find this to be the most enjoyable part of the effort by a long shot.   We have two dedicated airplanes for flight test and two other aircraft that we periodically use when we need to perform special tests or temporarily ramp up flight test intensity.

One thing that has slowed us down over the last 5 weeks is that one of our test airplanes has been undergoing a major modification in which a lot of sensors and 3rd party boxes that the IFD540 integrates have been installed.  We did this to ensure we had a truly representative environment for testing in case our lab configurations couldn’t adequately represent certain flight conditions or corner conditions.   We can also fly the airplane regularly “in the system” by filing IFR and flying in real airspace dealing with real flight scenarios day in and day out.   We get that airplane back this weekend and we’ll be back into full intensity flight testing.

One side note, while I would love to show off our stuff and let people take their own personal evaluation flights in these planes, we have created a self-imposed “no flights for outside people” rule and we’re staying disciplined on adhering to it until the system is “done”.  Sorry.  (I will make periodic posts of pix on my Twitter feed however)

 

FAA Involvement:

For better or worse, this one has us worried.   The crew that we work with in the FAA are all good guys trying to do a good job.   However, I’m sure no one will find it surprising to note that it is a big organization with lots of disparate parts and heavy workloads, all leading to a burdensome bureaucratic environment.   There are two specific areas that will result in real schedule uncertainty.   The first is that the STC project has been put into “sequencing”.   This is an FAA term that means the level of FAA involvement in the cert process is large enough that the regional office is not permitted to slip it in to their normal work flow.   Until it is out of sequencing, no one in the FAA can work the certification approvals and the big unknown is no one in the FAA can tell when it will pop out of sequencing, and which regional FAA office will perform the certification approval tasks.   The other event that is very disruptive to knowing with high confidence when the unit will be certified/approved is an FAA task called a Multi-Pilot System Useability Evaluation (MPSUE).   This is a FAA-run evaluation of the system in the lab and in flight in which they conduct a human factors analysis of the safety and certifiability of the unit.  For anyone following the R9 SynVis cert effort thread, you have some sense of the MPSUE saga that is likely to unfold.  And unlike in the case of SynVis which was an “abbreviated” MPSUE, the FAA has informed us that the IFD540 will receive a “full” MPSUE.   That is likely to involve at least 10 FAA flight test pilots and flight test engineers and human factors folks (and maybe more) and coordinating all those schedules and viewpoints is a non-trivial task.  It is a safe assumption to say something will need to be changed in the code as a result of that FAA input and therefore we can’t declare we’re 100% code complete until the MPSUE has been conducted and any changes implemented.  And of course, they can’t even start scheduling the MPSUE until the project comes out of sequencing.

The rest of the FAA involvement is just par-for-the-course types of tasks and are in the noise when compared to the above two challenges.

I view this area as the single biggest schedule wild card, by far.

 

Launch Readiness/Pilot Program:

Let’s try to end on a high note.   Despite all that work noted above, we are also running a parallel launch readiness effort so we’re as ready for prime time as we can be.   This has all kinds of sub-parts to it like ramping up our production line at the factory, having ship kits all ready to go, having simulators and user documentation ready to go (we don’t plan to release those until just before certification) and a lot of other typical product launch types of tasks.

One big part of our plan is to run a “Pilot Program” that will start the day after we receive TSO and STC approval/certification.  This “Pilot Program” is intended to run long enough (I’d guess 4-10 weeks) for us to be confident there aren’t any must-fix gotchas before we open the flood gates to full-rate production and installations.   I am planning on installing TSO/STC units in 20-30 customer aircraft and collecting installation and flight behavior input as required.    I have many more details on the Pilot Program that we’ll share in the coming next few weeks in which I explain the types of aircraft configurations and patterns of flying we’re looking for and seeking volunteers to participate in that program.  I wouldn’t call it a “Beta Test” program since we’ll be fully certified by that time (and by the way, we have no plans to install pre-certified gear in people’s airplanes) but it will definitely be in the veins of an early adopter kind of phase.   That explanation and solicitation for volunteers will come in the form of an email to all those customers who have already signed up for one or more IFD540s but if you want to get a headstart on throwing your name into that hat, don’t hesitate to send an email to sjacobson@avidyne.com.



-------------
Steve Jacobson
sjacobson@avidyne.com


Posted By: tony
Date Posted: 31 Jan 2013 at 7:46pm
Steve, thank you.


Posted By: oskrypuch
Date Posted: 31 Jan 2013 at 9:00pm
Wow, thanks much for the update.

* Orest



Posted By: tony
Date Posted: 01 Feb 2013 at 5:59am
Could sequestration effect the amount of support from the FAA causing this effort to just fall off the FAA's to do list? or do you think this program is big enough in the eyes of the FAA to continue staffing it?


Posted By: AviJake
Date Posted: 02 Feb 2013 at 7:54am
That's a good question and one I don't know the answer to.  I asked the explicit question to our local FAA certification office and wait to hear back the response.  Will post update when I get it.

-------------
Steve Jacobson
sjacobson@avidyne.com


Posted By: AviJake
Date Posted: 16 Feb 2013 at 2:02pm
Just wanted to follow up on the Sequestration question.

I asked about sequestration and the effects it may be having on the FAA now.  As you may recall, the current date for sequestration is 1 March.  The official FAA policy right now is 30 days prior to that, changes start happening so we’re already in that window.

As of 1 March, all non mission critical FAA employees are to be furloughed.  There seems to be some confusion on what this even means but I believe the current plan of record is that every member of the FAA, at least in the offices that we deal with, may be affected several days per month.  I don't understand this to be a full-time furlough.  Still ugly but not as ugly as it might have been.

30 days prior, all non mission critical travel is cancelled and employees are encouraged to clear as much work off their to-do lists as feasible.

We surely don't want sequestration to come to pass but it seems like some impacts are already being realized.



-------------
Steve Jacobson
sjacobson@avidyne.com


Posted By: SB Jim
Date Posted: 06 Mar 2013 at 7:59pm
Any news?


Posted By: AviJake
Date Posted: 07 Mar 2013 at 7:48pm

IFD540 Status Update (7 Mar 2013):

We've moved 6 weeks closer to cert since the last big update.   I'll use the same way to slice this up as the late Jan update, albeit in an abbreviated manner:

Hardware Qualification:

We are still undergoing the official for-credit hardware qual of the units.  We had one glitch with the VHF performance at low voltage testing and have subsequently tweaked the design to address that problem and are back in qual - that put a few week dent in the hardware qual schedule. 

1.       Environmental Qual (DO-160) – I didn't really mention this in the late Jan update but we front end loaded the tougher and riskier tests so we minimize the likelihood of late-in-the-game surprises.  As I noted above, the tests uncovered a design issue that we found and fixed and are back at it now.  I'd be willing to bet we have more of those ahead of us this spring.

2.       Complex Electronics Qual (DO-254) – we have conducted our own not-for-credit testing to ensure we have no problems but have still not yet started the formal qual testing.  When we do, it should take a few weeks until completion.  For the techies in the audience, Complex Programmable Logic Devices (CPLDs) is where a lot of the embedded logic is conducted and we just have to show nothing unexpected or nefarious happens in that hardware/firmware.

3.       Minimum Operational Performance Standards (MOPS) testing – so far so good still but not quite done.   The FAA specifies minimum performance requirements for hardware (e.g. GPS, VHF, etc) and each one of those standards comes with pages (and sometimes pages and pages and pages) of tests that are specified and must be run and shown to meet published pass/fail criteria.

 

Software Qualification:

We have a very specific punch list of items and we're systematically checking them off one-by-one.  The pace is definitely accelerating but there is still a small mountain of work ahead of us.  No show stoppers and we've hired up to augment our software testing crew.  Many of the formal software tests are written and more are done every day (there are almost one thousand tests to create/review/run/document).

I left this paragraph in from the Jan update since it's still relevant - Past experience says it’s wise to be conservative on estimating the impact of these changes on schedule so I would estimate we have a few months of work still ahead of us before we declare the code to be 100% done.

 

Flight Testing:

The airplane that I'm principally flying is a workhorse.  We upgraded it last week to ops test more of the systems we interface to in a real world situation.  The result is that the plane has a crazy antenna farm on the roof and I feel like Lily Tomlin in front of her switchboard as I change connections real-time in flight.  

I do have a minor fuel leak in a wing root which will require me to put the plane down for a little bit but aside from that, it's a reliable steed.

The FL-based test aircraft is equally as busy and that gets flown all the time by our Chief Pilot and our CEO.   We're bringing another test bird up in FL shortly.

 

FAA Involvement:

For better or worse, this one still has us worried.   We are still in sequencing and it's still not clear how the sequester-generated periodic FAA furloughs will impact the program.

 

Launch Readiness/Pilot Program:

I had a huge response in the solicitation email to all the pre-buy customers a few weeks back asking for volunteers to participate.  I haven't spent enough time pouring through all the data yet to down-select the best configured airplanes operated by eager to help owners.   I bet there are still a few weeks before that settles out.



-------------
Steve Jacobson
sjacobson@avidyne.com


Posted By: tony
Date Posted: 07 Mar 2013 at 8:06pm

Steve, Thank you for the update....

So now I'm going to put on my program manager hat. What are the estimated completion dates for the above tasks? In other words, when are you going to be done with your effort? I know you can't predict the FAA's support, given all the furlough notices today, but when will your development team be finished?

 

.


Posted By: AviJake
Date Posted: 07 Mar 2013 at 8:15pm
June or July.

-------------
Steve Jacobson
sjacobson@avidyne.com


Posted By: SB Jim
Date Posted: 05 Apr 2013 at 12:03pm
Jake,
 
Time flies when you're having fun. Another month has passed.
 
How goes it?


Posted By: AviJake
Date Posted: 07 Apr 2013 at 8:39am
It's going well (IFD540 development that is).  I'm currently on a 6-day XC to exercise the dual IFD540 aircraft "in the system" and will provide a more detailed post when I return.  Our rate of closure to the finish line hasn't slipped at all in the last month so that's encouraging.

The FAA, despite the effects of sequester and the fact that the IFD540 cert program is still in sequencing, is pressing ahead with scheduling the MPSUE (Multi-Pilot System Usability Evaluation) human factors evaluation and flight test in May. 


-------------
Steve Jacobson
sjacobson@avidyne.com


Posted By: oskrypuch
Date Posted: 07 Apr 2013 at 10:47am
Bravo.

* Orest



Posted By: SB Jim
Date Posted: 09 Apr 2013 at 11:15am
Jake,
 
Good news.
 
Plus they pay you to go flying? What a horrible job! <g>


Posted By: Paul
Date Posted: 09 Apr 2013 at 1:18pm
It isn't perfect.  They pay him to go flying, but on the ground he has to put up with us.


Posted By: glassanza
Date Posted: 11 Apr 2013 at 3:33pm
Got to turn knobs as well as pinch and poke a 540 at S&F yesterday....Super Impressed. I feel the finish line is in sight and its goning to be well worth the wait. Special thanks to Jonathan Pelletier for showing me some of the functionality.

-------------
GDC25


Posted By: AviJake
Date Posted: 11 Apr 2013 at 5:04pm
Good to hear about the demo at SnF.

One more piece of encouraging news - the FAA has officially pulled the program out of sequencing and we had an extensive meeting with them this past Monday with respect to planning the details of the FAA participation in the cert program.

I also happened to bump into one of the principal FAA test pilots who will be part of the MPSUE while on my XC and we got to do some good familiarization training on the real gear in the aircraft on Tuesday.

I'm sure it'll go slower than we all want but it's all coming together nicely.

When I get a few minutes, I'll type up some of the highlights of my 5 day XC trip with the gear.  Put about 29 flight hours on the gear during those 5 days.


-------------
Steve Jacobson
sjacobson@avidyne.com


Posted By: oskrypuch
Date Posted: 11 Apr 2013 at 5:08pm
Very, very good to hear.

* Orest



Posted By: jperryfly
Date Posted: 15 Apr 2013 at 11:18pm
Hi Steve,
So the 440 should be ready about this time next year?  Any hopes for earlier than that?
I would be installing it in place of a 430w in an experimental would that get me an earlier date?
John 


-------------
John Perry


Posted By: AviJake
Date Posted: 16 Apr 2013 at 8:06am
Hi John,

For planning purposes, you should expect the IFD440 to come out 6 months after the IFD540.  But, yes, there is some reason to hope that it will be faster.  We already have the hardware and the software is virtually identical to the IFD540 and the FAA is aware of both.

That being said, I'm afraid that it'll be done when it's done and that having an Experimental category airplane won't help speed up delivery for you.  Frustrating I'm sure, but it's our reality.

Steve


-------------
Steve Jacobson
sjacobson@avidyne.com


Posted By: wsh
Date Posted: 16 Apr 2013 at 4:47pm
what is the schedule for the 540?


Posted By: AviJake
Date Posted: 16 Apr 2013 at 5:42pm
Not clear.  Here's what I do know:

1.  FAA has officially cleared the way to work the program;
2.  We have scheduled FAA fam flights for week of 29 April;
3.  We are working toward a week of 20 May FAA Human Factors review - we're ready, just waiting on the FAA to coordinate the schedules of all their participants;
4.  Our development team will be done by June or July.

From there, there are too many variables to declare a release date - clarity will be much more likely as #4 approaches.   The team here can't be working any harder on this project than we are and we are extremely motivated to get it done as soon as feasible.


-------------
Steve Jacobson
sjacobson@avidyne.com


Posted By: wsh
Date Posted: 16 Apr 2013 at 6:29pm
Tx

may we conclude august at the earliest?

P.s. we definitely appreciate all the hard work and opennes. We just want to understand where we are approximately


Posted By: AviJake
Date Posted: 16 Apr 2013 at 6:58pm
Yes, I think August is the earliest based the June/July completion by the development team.  It *may* not be much later than that.

-------------
Steve Jacobson
sjacobson@avidyne.com


Posted By: tony
Date Posted: 16 Apr 2013 at 8:15pm

Steve, I'm not sure I share your optimism but it doesn’t matter;  it’s going to be what it’s going to be and its out of our control.  I know how its ilmost impossible to predict how long the FAA will take.  What I would be interested in hearing is the feedback from the “pilot program”.  Let’s call it a quick look from a customer’s point of view.  Would that be possible?



Posted By: Victor
Date Posted: 17 Apr 2013 at 5:26am
Wouldn't it be fantastic if the release date was announced in time for Oshkosh.


Posted By: AviJake
Date Posted: 17 Apr 2013 at 7:28am
Tony,

Yes, I'll publish results of the Pilot Program but we won't start that until we have a certified product.  We anticipate the Pilot Program to run between 3 and 6 weeks after we receive certification.

Victor,

Yes, that would be fantastic to have cert by Oshkosh and while there is some chance of that happening, it does not look likely based on the various back-and-forth tasks that have to be accomplished once the development team is done.  I expect that at Oshkosh, assuming we do not have cert, we'll have a much better idea on when it may be (perhaps that's what you were suggesting).


-------------
Steve Jacobson
sjacobson@avidyne.com


Posted By: wsh
Date Posted: 30 Apr 2013 at 4:48am
Hi

@Aero Friedrichshafen people apparently were told that delivery is now expected for december??

I may hope, especially now that you are out of sequencing and the FAA is ack from the furloughs, that we may expect that it rather be july/august?



Posted By: MysticCobra
Date Posted: 30 Apr 2013 at 7:50am
I don't think "the FAA is back from the furloughs".  FAA flight controllers are back from furloughs, but it's not clear to me where the money came from.  I've seen some reports that it came from other FAA projects like airport improvements.  There could still be sequester impacts to non-flight control FAA functions.


Posted By: chflyer
Date Posted: 30 Apr 2013 at 8:17am
Steve's note above indicates to me that first customer deliveries (outside of the pilot program) could be expected in Q4. Anything earlier would be wishful thinking.

Earliest possible certification August plus pilot program brings us to mid-end September. I expect customer deliveries will be in the sequence of pre-order, and not all will be filled on day 1. Avidyne won't likely start mass production until the end of the pilot program to ensure any easy fixes are included in the first shipments.


-------------
Vince


Posted By: phkmn
Date Posted: 30 Apr 2013 at 4:53pm
"2.  We have scheduled FAA fam flights for week of 29 April;"

So... is this happening as planned?


-------------
PH


Posted By: AviJake
Date Posted: 30 Apr 2013 at 7:18pm
This serves me right for spending all day flying the IFD540 - come back and there are a bunch of questions posted......

The FAA did indeed stop the furloughing of some employees but that was only the Air Traffic Controllers.  The guys who do aircraft and avionics certifications (i.e. the crew we deal with) are still affected by the sequester-induced furloughs.  They are forced to take one day every two weeks off without pay.   It is having some, but so far not too much impact on what we're seeing.

Yes, we are still flying with the FAA this week for their first look/fam flights.  I'm specifically flying with two of the guys on Thursday and they are expecting about a 2 hour (120 min) sortie.  We're ready.  They have also gotten their evaluation pilots all signed up for the week of 27 May for the official evaluations.  They are being very creative in funding that effort - I don't ask questions on how they are pulling that off.....just really happy they are.

The development team does remain on track to complete all development in June or July.  We have a very specific punch list of remaining items and it gets smaller every day.  Nothing on the remaining list looks like it has any meaningful likelihood or potential to result in a miss of that June/July milestone.

Aside from the May FAA evals, we are still in negotiation with how much of the other cert tasks they will delegate to us.  The results of those negotiations will directly affect the duration of the cert end-game.

And yes, as soon as TSO/STC is issued by the FAA, we absolutely still plan to run that pilot program to ensure we don't have (or quickly eliminate) any introduction-to-service types of issues.  I still expect the duration to be at least 3-4 weeks long and may be longer depending on the intensity of the flying during the pilot program and if any issues pop up.


-------------
Steve Jacobson
sjacobson@avidyne.com


Posted By: oskrypuch
Date Posted: 30 Apr 2013 at 8:47pm
Very good, keep it rollling.

* Orest



Posted By: AviJake
Date Posted: 02 May 2013 at 4:47pm
(IFD540 Status Update - 2 May 2013):

Flew the IFD540 with FAA today.  I would characterize the flight as going well to very well.   This was the first real familiarization the FAA has had with the unit and they did a comprehensive evaluation of the system using our test 182 equipped with dual IFD540s.   While all aspects of the system were looked at, the emphasis was on touch screen operations.  To be clear, this was not a for-credit evaluation of the system by the FAA, it was just a fam flight and a dry running of the MPSUE profile they will fly later this month.  That being said, they did identify two specific areas that likely would produce a cert problem.  I think they were right and we will address both issues prior to the official MPSUE later this month.

One other side note - the FAA cert group that we work with were informed that they too are no longer on furloughs as of this week so that should help with keeping the ball rolling on IFD540 cert.


-------------
Steve Jacobson
sjacobson@avidyne.com


Posted By: oskrypuch
Date Posted: 02 May 2013 at 7:38pm
Quote  That being said, they did identify two specific areas that likely would produce a cert problem.  I think they were right and we will address both issues prior

What kind of thing(s) was that, if you can say?

* Orest



Posted By: AviJake
Date Posted: 02 May 2013 at 7:54pm
Sure.

Issue #1: When we are panning the map to a location not co-located with the ownship position, we effectively froze the map so the pilot can see a steady and non-moving map when reaching that pan position. If however, the aircraft heading was changing while in the panned state, the heading box at the top of the temporarily frozen map would not update.   The change will be to always keep the heading box at the top of the map representative of actual aircraft heading.  There are some subtle nuances to that summary but close enough to get the idea.

Issue #2:  The IFD540 has Forward Looking Terrain Alerting (FLTA) as part of the baseline product.  This is a subset of certified TAWS and will alert the pilot via a message and an aural alert if it projects an imminent impact with terrain (approximately 60 and 30 seconds from projected impact).  It is suppressed around airfields or if the pilot manually toggles it off.  We annunciate the inhibit state but that wasn't a permanent display of the inhibit state.  The FAA noted that may be a cert issue so we intend to make that a permanent display when it is inhibited (in other words, no pilot action is required to display it but conversely, if the state is active, then the annunciation of it can not be removed).


-------------
Steve Jacobson
sjacobson@avidyne.com


Posted By: oskrypuch
Date Posted: 02 May 2013 at 10:28pm
Interesting, thanks, appreciate the insight. Fine details, but they could be issues.

* Orest





Posted By: Victor
Date Posted: 03 May 2013 at 5:39am
Steve,

I can't thank you enough for keeping us in the loop the way you have been.  To get on here the same day you flew with the FAA and keep us advised of the result is so very much appreciated.

Victor


Posted By: tony
Date Posted: 03 May 2013 at 1:34pm

Steve, I think you will avoid issues down the road (hazardous misleading data) if you just remove the heading all together when you pan the map.  Then once you leave the pan mode and the ship's solution is centered on the display, put it back.  I'm assuming the CDI still indicates cross track error in pan mode and that’s what the pilot should be flying anyway.  Everything else is situational awareness.

Just my opinion



Posted By: AviJake
Date Posted: 17 May 2013 at 8:22pm
(IFD540 Status Update - 17 May 2013):

Flew the IFD540 with the FAA again this week (Thursday).  I would characterize the flight as also going well to very well.   This was the second familiarization the FAA has had with the unit and they ran through the intended full MPSUE flight profile and evaluation test events in our test 182 equipped with dual IFD540s.   The going-in objective of the flight was for the local FAA to dry run the MPSUE flight profile and tweak the run cards as required in support of the full MPSUE that starts in two weeks.   But, during post-flight, the FAA pilot decided he's seen enough of the system and will consider that his for-credit MPSUE flight evaluation.  He had a number of observations but no CIs (Certification Issues), PCIs (Potential Certification Issues) or RSEs (Recommended System Enhancements) which was great news.

As always happens with these things, the FAA has made some meaningful changes to the way they intend to run the MPSUE.   They have added several more (4) pilots to the evaluation team and their availability schedules are such that we actually start the MPSUE next week (technically this week since the Thursday flight will count) and run through the end of the week of 3 June, expecting the last flight to be on/about 7 June.

Of course, the more exposure the system has to evaluation pilots the greater the risk but we feel very confident going into this - we're ready.


-------------
Steve Jacobson
sjacobson@avidyne.com


Posted By: AzAv8r
Date Posted: 17 May 2013 at 8:26pm
Fabulous!  Thanks for the update.
Jon



Posted By: tony
Date Posted: 19 May 2013 at 8:55pm
Is the MPSUE tests you speak of, where you give the platform over to the FAA and they operate it by themselves without Avidyne involvement?


Posted By: AviJake
Date Posted: 20 May 2013 at 9:00am
For the MPSUE, the typical protocol is that the FAA evaluator pilot flies in left seat as the flying pilot, the Avidyne pilot sits in the right seat and serves as PIC but does not operate the system, fly the airplane or talk on the radio unless needed to for safety or asked to by the FAA, and a FAA Flight Test Engineer sits in the back seat and directs the run cards and records the FAA evaluator pilot comments and takes other notes.

We then debrief the flight afterwards and the FAA spends 1-3 weeks compiling all the FAA notes and the publishes an official FAA position on their findings.  They score each finding using a scale:

CI - Certification Issue;
PCI - Potential Certification Issue;
RSE - Recommended System Enhancement
Comment/Note/Observation - Self evident

Then the negotiation begins and we'll formally respond in writing as to the company position.  The general rule is that all CIs must be resolved before certification and PCIs are usually in the same boat while the rest are all negotiated.


-------------
Steve Jacobson
sjacobson@avidyne.com


Posted By: tony
Date Posted: 21 May 2013 at 6:08am
So if I'm reading this right, am I correct to assume that all the software qualification tests have been completed in the lab, and the last formal testing will be completed in about a month?  Have all the hardware qualification issues resolved?


Posted By: AviJake
Date Posted: 21 May 2013 at 10:00am
No, I wish that were a correct read but it's not quite right.

We try to time the MPSUE to happen when a number of factors are right.  The principal considerations are:

1.  The system is representative of the final product such that all evaluations are against the design we intend to certify;
2.  The system is not so close to certification that any changes induced by the FAA evaluation would have significant and difficult to deal with schedule implications;
3.  The FAA evaluator pilots schedules permit the time.

We hit #1 a few weeks ago but couldn't schedule #3 until now.   For better or worse, we don't think we've added too much risk to #2.

We won't even consider starting the formal software testing until the look & feel and usability evaluations by the FAA are complete and closed out.    This is done because the software testing is so time consuming - dozens of engineers running tests almost around the clock for weeks and weeks.

We also are going to go back into formal hardware testing starting in about a week or so.   All the hardware and environmental testing we've been conducting for months has led to a number of good design updates/improvements and the last of those redesigned hardware components arrive in a few days.   We're looking at the last few months of hardware testing as terrific risk mitigation and design improvement and formal testing dress rehearsals and now go into the retest phase with high confidence.


-------------
Steve Jacobson
sjacobson@avidyne.com


Posted By: tony
Date Posted: 21 May 2013 at 6:25pm
Steve, Thank you.  I have a pretty good idea now where you are.  I'm going to guess there are about 250 KSLOC in your image.  For the formal software testing are most of the tests manual?


Posted By: AviJake
Date Posted: 22 May 2013 at 9:34am
Our SLOC count is actually 4-5 times that size.  We've got approximately 1.2 MSLOC which is clearly a daunting task. 

On the good news front, about 450 KSLOC is the OS which comes as a Reusable Software Certification (RSC) package which means we don't have to review it or write/run tests for it - that has already been done.

Of the remaining 680K of Application flight code, about half is unchanged legacy code from R9 so the previous code reviews and test generation are complete and we can take cert credit for it.

Of the now remaining 340K of "new" code, about 1/3 is Level D which obviates the need for DO-178 style code review.

That leaves us with approximately 220K SLOC that need code review and test generation/running.  We started on that about 6 months ago and have been sliding more and more engineers to those tasks as they complete their pure development tasks.

As for the tests, a great deal are automatic in that once you write and dry run and review them, they can be automatically run and the test results are auto compiled.  There are still a lot of tests that are more manual than automatic due to the nature of setting up a specific configuration of avionics and having to verify visual behavior on the display.  For example, needing to see a flight plan leg turn magenta when it becomes the active leg is still a manual exercise for us.


-------------
Steve Jacobson
sjacobson@avidyne.com


Posted By: oskrypuch
Date Posted: 22 May 2013 at 4:51pm
I'm fascinated with all the detail we're seeing here, and it helps with the wait.  ;-)

Thanks.

* Orest



Posted By: tony
Date Posted: 22 May 2013 at 8:58pm
Steve,  thank you for the transparency.  Yes it's much clearer now.  From your response you must be using the OS from the guys in FL.  Its a stable product and we always have gotten great support from them.  I am impressed with the size of your OFP.  Please don't run out of room......


Posted By: AviJake
Date Posted: 22 May 2013 at 9:42pm
We're using the identical OS we use in R9 - it's called LynxOS-178 and is provided by Linuxworks with the RSC.  I know that at least Rockwell Collins and Avidyne use it in our avionics applications. 

We also layer on top of that an ARINC653 partitioned architecture that essentially creates brick walls between the virtual machines running code at different design assurance levels (DAL).  In other words, a Level D application (e.g. Checklist) can not adversely affect a higher Level C (e.g FMS) or Level B (LPV guidance/deviation) application.  Each DAL runs in its own virtual machine - we segment the processor into several semi-autonomous virtual processors.   It's a pretty neat, sophisticated and highly effective architecture for this type of rigorous aviation application.


-------------
Steve Jacobson
sjacobson@avidyne.com


Posted By: AviJake
Date Posted: 29 May 2013 at 5:03pm
(IFD540 Status Update - 29 May 2013):

We're hot and heavy in the midst of the MPSUE.  We've put 6 FAA reps through ground training, ground eval and flight eval so far with about 5 or 6 more still to go.    We don't have any results yet - will make a post when we have something interesting to talk about on this front.


-------------
Steve Jacobson
sjacobson@avidyne.com


Posted By: AviJake
Date Posted: 04 Jun 2013 at 7:42am
(IFD540 Status Update - 4 June 2013):

Still in the middle of IFD540 MPSUE and it just got extended.  Due to scheduling challenges on the part of the FAA, we are now scheduled to conclude FAA flights on Friday 14 June.

On a side note, we are showing the FAA the IFD440 at the same time so we can hopefully avoid any new human factors/system usability evaluation with that product.


-------------
Steve Jacobson
sjacobson@avidyne.com


Posted By: oskrypuch
Date Posted: 04 Jun 2013 at 9:01am
Well, not a biggie.

* Orest


Posted By: jperryfly
Date Posted: 13 Jun 2013 at 2:09pm
Steve, 
Ref your comment on the 440 on 04Jun.
Does that change the target date for the 440?  I would just like to get a jump on selling my 430W so I can pay for the 440.  
Thanks,
John in Fl


-------------
John Perry


Posted By: AviJake
Date Posted: 13 Jun 2013 at 6:31pm
Hi John,

Reference your question about IFD440 timing, we don't know but we hope so.   We'll be able to give a pretty good heads up on 440 cert when we're within 2-3 months of it's expected cert.  Might be wise to wait until then just in case.


-------------
Steve Jacobson
sjacobson@avidyne.com


Posted By: tony
Date Posted: 17 Jun 2013 at 3:57pm
Originally posted by AviJake AviJake wrote:

(IFD540 Status Update - 4 June 2013):

Still in the middle of IFD540 MPSUE and it just got extended.  Due to scheduling challenges on the part of the FAA, we are now scheduled to conclude FAA flights on Friday 14 June.

 
I hate to be a nag, but did this complete?


Posted By: oskrypuch
Date Posted: 17 Jun 2013 at 4:27pm
Originally posted by tony tony wrote:

 
I hate to be a nag, but did this complete?

Boy, what a NAG!

* Orest



Posted By: AviJake
Date Posted: 17 Jun 2013 at 8:10pm
It wasn't but it is now.   The FAA had to weather cancel last week and rescheduled the two make-up flights today.

I am pleased to declare the MPSUE is now complete - at least all the FAA evaluation flights.  It took almost 5 weeks instead of the 1 they had intended - all due to FAA availability and weather challenges.

The next phase is to wait until they publish their Issues List.  I fear we'll have to wait another painful duration for that to get into our hands since the principal FAA rep that is responsible for creating and issuing the list is about to head out on vacation and he's unable/unwilling to delegate that list creation to anyone else.

In the meantime, we'll keep plugging away on the certification artifacts. We'll focus on the ones least likely to be affected by any FAA input from the MPSUE.


-------------
Steve Jacobson
sjacobson@avidyne.com


Posted By: oskrypuch
Date Posted: 17 Jun 2013 at 11:33pm
Well, maybe he'll be in a really good mood when he returns, and give you a Gold Star.

* Orest



Posted By: Victor
Date Posted: 18 Jun 2013 at 5:36am
Did he indicate how long he will be absent?

Victor


Posted By: AviJake
Date Posted: 18 Jun 2013 at 7:50am
The FAA rep responsible for the Issues List is busy with other applicants this week and is out all week next week.  He returns on 1 July.

-------------
Steve Jacobson
sjacobson@avidyne.com


Posted By: tony
Date Posted: 18 Jun 2013 at 3:14pm
Did we get the redesigned hardware through environmemtal qual yet?


Posted By: AviJake
Date Posted: 18 Jun 2013 at 6:45pm
Not quite.  I think we're 2-3 weeks away from being done.  We decided to re-run a number of tests with the new display glass.  No show stoppers so far and none anticipated.

-------------
Steve Jacobson
sjacobson@avidyne.com


Posted By: tony
Date Posted: 18 Jun 2013 at 8:06pm
after you receive your stc, how long will you allow the pilots program to run before you ship to the rest of us?


Posted By: AviJake
Date Posted: 29 Jun 2013 at 11:29am
Pilot program should run between 3 weeks (enough time to determine if all is going swimmingly well) and 5 weeks (enough time if some installs are slow out of the gate or if feedback is slow to come in). 

Based on how that pilot program goes, we'd either open up full-rate shipping at that point or fix any entry-to-service issue that was discovered during the pilot program.


-------------
Steve Jacobson
sjacobson@avidyne.com


Posted By: oskrypuch
Date Posted: 29 Jun 2013 at 7:53pm
Well, I'm standing by. I'm ready to get going right away, on that new baby

* Orest




Posted By: ddgates
Date Posted: 29 Jun 2013 at 9:08pm
Do these developments bear any relation to the IFD 440 vert?

-------------
David Gates


Posted By: AviJake
Date Posted: 30 Jun 2013 at 10:15am
With respect to David's question about 440 cert, the short answer is "yes".   The tougher answer is in providing substantiating detail.

We still expect the 440 to be a "fast follow" cert behind the 540.  That may mean 2 months, that may mean 6 months.   We're flying 440s at the same time as the 540 in our test aircraft and we showed the FAA during the recent 540 human factors evaluation (MPSUE) that it's the "same, only smaller" version of the 540 so any considerations they have on the 440 *should* be resolved by any thing we do in the 540.

That being said, whenever we hit a resource crunch or an attention needing effort, the 540 will always win out over the 440.    That's an important statement in order to resist the temptation to cert both at the same time.  We don't want to accept the potential of delaying 540 by pulling in the 440.  We do ask ourselves nearly every day something like "will doing that with the 440 delay the 540 time to market by even a day and if so, is it really, really worth it?"  It's rare to hear a "yes" to that question.


-------------
Steve Jacobson
sjacobson@avidyne.com


Posted By: ddgates
Date Posted: 30 Jun 2013 at 2:18pm
Makes sense, Steve.

Maybe they will hand you an unsolicited "gift"...


-------------
David Gates


Posted By: wsh
Date Posted: 30 Jun 2013 at 5:15pm
so what is the expectation for the 540.August or Octobre?


Posted By: AviJake
Date Posted: 01 Jul 2013 at 8:50am
Definitely not August for IFD540 Cert.  Instead of providing a date, I'll say that we have a few major milestones to get through before we can spike the ball.  You should consider measuring us against these remaining milestones to get a sense of the higher and higher confidence date.  Those remaining big milestones are:

1.  Receive, and react accordingly to, the FAA-generated MPSUE assessment of the unit.  This will likely drive some code changes but we won't know the magnitude until we get the official list from the FAA;

2.  Achieve 100% DO-178B Code Complete status.   This is well beyond "feature complete".  DO-178B "Code Complete" means we've finished all the code review and requirement tracing of the code per the FAA-recognized software standard.   We can't finish this until we know the code is done changing.  Note that we're done with all the changes on our end, we're just reacting now to any mandated changes;

3.  Officially declare DO-160 Hardware Qual testing to be complete;

4.  Achieve "Red Label" status on the combined hardware/software system.  This means that all formal for-credit software and hardware testing have been completed.  In other words, this is a submittable-for-cert system;

5.  Complete official company "for-credit" flight testing of the final submittable system;

6.  Complete FAA TIA (Type Inspection Authorization) testing.  This is the FAA's final exam of the complete system before they sign off on cert.

7.  Make our final submissions to the FAA of 100% of the certification artifacts.

We do consider this to be end-game of the program.  Some of those activities typically last only a matter of a few days (e.g. 5, 6, 7) and some take several weeks to get through (e.g. 2, 4).


-------------
Steve Jacobson
sjacobson@avidyne.com


Posted By: Leonard
Date Posted: 01 Jul 2013 at 12:36pm
Can I save on freight and just have Santa bring and install it?


Posted By: AviJake
Date Posted: 01 Jul 2013 at 12:59pm
Gosh, I sure hope so.   I might even come down and hand-deliver it......

-------------
Steve Jacobson
sjacobson@avidyne.com


Posted By: wsh
Date Posted: 01 Jul 2013 at 5:44pm
dear Steve

I do appreciate your candor in the matter. It however does seem that everytime new .. or unannounced ... issues come up ..

I seriously hope and count on Avidyne delivering this year .. and have it certified by october.

It is about time that we start concentrating on the real important stuff ... like getting the MLX working on it..

Other than that I truly look forward to getting rid of the Garmins and getting a much more intuitive system.


Posted By: AviJake
Date Posted: 01 Jul 2013 at 7:09pm
Understood.

-------------
Steve Jacobson
sjacobson@avidyne.com


Posted By: jkturner
Date Posted: 02 Jul 2013 at 9:03pm

Are we seriously looking at October as the likely date for certification?  i was told when i purchased that the unit should be certified by June, I know that you've had to deal with the effects of sequestration but how has that caused a delay of 4 months?  I sold my Garmin 530W while I could still get something for it and am now renting one from a local avionics shop to use until the IFD 540 is available.  Any news on who or when the pilot program people will be selected and potentially have radios?   Thank you for your support!



-------------
JT


Posted By: AviJake
Date Posted: 04 Jul 2013 at 9:26am
I will report on the FAA MPSUE findings and the Code Complete milestones noted above (#1, 2) and at that point, will focus on the pilot program selection and date estimates since at that point, we have a much more deterministic schedule.

We're working weekends and holidays to get this done.


-------------
Steve Jacobson
sjacobson@avidyne.com


Posted By: jkturner
Date Posted: 04 Jul 2013 at 10:58am
Thank you for the information!

-------------
JT


Posted By: Leonard
Date Posted: 04 Jul 2013 at 11:11pm
WELL It is what it is!
While others Can't wait to get a new untried unit.  I'd much rather wait a little longer  just to unsure that I will not having to send it back because of XYZ  problems.
 
My thoughts are, do not be pressured by us customers. When Avidyne is ready. We'll be ready.
 
Leonard


Posted By: tony
Date Posted: 17 Jul 2013 at 4:57pm
Did you get any FAA MPSUE findings reported yet?


Posted By: AviJake
Date Posted: 17 Jul 2013 at 7:38pm
No, afraid not.    Here is an exact cut and paste from an email I got this morning from the FAA on the topic:

"We are about 75% through. We are having another meeting on Friday to finish this up, so Friday, maybe next Monday."

This is a big enough milestone that you can be sure I'll report the status/findings as soon as I get them and what our course of action will be based on those findings.


-------------
Steve Jacobson
sjacobson@avidyne.com


Posted By: oskrypuch
Date Posted: 18 Jul 2013 at 9:11am
Fingers crossed that there are no biggies.

* Orest



Posted By: Paul
Date Posted: 22 Jul 2013 at 7:36pm
The rest of the world waits to find about about Kate's baby.  We wait to hear what the FAA said.  They (or we) should get a life...


Posted By: oskrypuch
Date Posted: 22 Jul 2013 at 8:48pm
You know what, I kind of LIKE the life I already have!  ;-)

* Orest




Print Page | Close Window

Forum Software by Web Wiz Forums® version 12.01 - http://www.webwizforums.com
Copyright ©2001-2018 Web Wiz Ltd. - https://www.webwiz.net