Everyone seems to agree that that FAR 43 requires a maintenance log entry
when updating the database. And everyone agrees that it is silly.

What date do you put down for the maintenance ( I know the obvious answer -
the date you did it)? If I update multiple planes this weekend with the
database that will be effective in the middle of the week (Mar 16th) because
it is more convenient to go to the airport on a weekend, is it smart to put
I updated the databases before they are effective if they have an IFR flight
before the 16th?

I understand you can legally fly an approach with an expired database if the
approach has not been modified since the last database revision. My
understanding is you couldn't verify if the approach had changed until you
wait close enough to the cycle data to get the paper charts and see if they
changed anything. If they changed it on the future cycle and it affected
your approach before the effective date (you can download 10 days ahead,
before you receive the paper) could FSDO bring enforcement?

I take the old cards home with me so I don't have to make two trips to the
airport every update cycle.

We had a courtesy safety inspection last year by FSDO and they went through
every log and found things they thought could be done better. (multiple
planes). Mostly nitpicking stuff.

Never, did they mention the absence of GPS database entries in the
maintenance log or on anyone else's plane on the field.

I think the only way around it is to leave both sets of cards and make two
trips each cycle. Now that is ridiculous!

Ron A.