Sender: <marv@lancaironline.net>
To: lml@lancaironline.net
Date: Sat, 17 Dec 2005 00:43:59 -0500
Message-ID: <redirect-885741@logan.com>
Received-SPF: none
 receiver=logan.com; client-ip=24.93.47.44; envelope-from=jeff@boxybutgood.com
From: Jeff Meininger <jeff@boxybutgood.com>
User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929)
MIME-Version: 1.0
Subject: Re: [LML] another Oooops!
References: <list-884806@logan.com>
In-Reply-To: <list-884806@logan.com>
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Matt Hapgood wrote:

> But hopefully not so serious.  I certainly haven't been complying with this
> reg... anyone out there have a different take on this?  This is from today's
> AOPA email newsletter.

Yeah... somebody on the Mooney list posted the relevant regs, and you do 
*NOT* have to put an entry in your aircraft logbook every time you 
update the data.  You *do* have to keep a "record", however, the same 
way you have to keep a record of VOR checks.  But the record only has to 
be of the most recent instance.  So if you update your GPS database, you 
can write the date on a sticky note and stick it to your SkyBound unit. 
  Then the next time you update, just throw that sticky note away and 
use a new one.

Here's a cut-and-paste of the regs quoted in the Mooney list post...

91.417 (b) - The owner or operator shall retain the following records 
for the periods prescribed:

(1) The records specified in paragraph (a)(1) of this section shall be 
retained until the work is repeated or superseded by other work or for 1 
year after the work is performed.

91.417 (a)(2) describes what records must be retained and tranferred 
with the airframe, engine, or other life limited parts. Avionics 
database updates isn't on that list.