Database updates, logging

[danb35]

New rule published by the FAA a couple of days ago:

§ 43.3 Persons authorized to perform maintenance, preventive maintenance, rebuilding, and alterations.

* * * * *

(k) Updates of databases in installed avionics meeting the conditions of this paragraph are not considered maintenance and may be performed by pilots provided:

(1) The database upload is:

(i) Initiated from the flight deck;

(ii) Performed without disassembling the avionics unit; and

(iii) Performed without the use of tools and/or special equipment.

(2) The pilot must comply with the certificate holder’s procedures or the manufacturer’s instructions.

(3) The holder of operating certificates must make available written procedures consistent with manufacturer’s instructions to the pilot that describe how to:

(i) Perform the database update; and

(ii) Determine the status of the data upload.

Not maintenance any more, no more need to log them.

Final rule on pilot database updating.pdf

[M016576]

It's about time!

[Cruiser]

What?????????

I don't see any change to the part 91 operators in this rule.

This rule amends 43.3 by adding paragraph (k).

43.3 applies to PERSONS AUTHORIZED TO PERFORM MAINTENANCE, PERVENTIVE MAINTENANCE, REBUILDING, AND ALTERATIONS.

All of these actions require logging.

[1964-M20E]

Well my thoughts are that the GPS itself tells you what database is installed and therfore complies with the database version being loged regardless of what rule you want to use. Myself I plug the DB in and go. It is either current or not.

[danb35]

All of these actions require logging.

"Updates of databases in installed avionics meeting the conditions of this paragraph are not considered maintenance"

[Marauder]

"Updates of databases in installed avionics meeting the conditions of this paragraph are not considered maintenance"

I think the big advantage of this change is for those Aspen owners out there. I was informed that firmware updates required a trip to the avionics shop for the update. If I am reading this correctly, as long as I know the procedure for the update verification, I can do this activity myself.

[Marauder]

Provided they consider an operating unit's firmware update a database...

[danb35]

Well my thoughts are that the GPS itself tells you what database is installed and therfore complies with the database version being loged regardless of what rule you want to use. Myself I plug the DB in and go. It is either current or not.

Unfortunately, your thoughts on the matter don't appear to match the previous regulations. The previous rule identified database updates as preventative maintenance, which can legally be done by the owner or operator of an aircraft. So far, so good. However, FAR 43.9 requires that after maintenance or preventative maintenance is performed, and before the aircraft is returned to service, a maintenance record entry be made. That entry must contain (1) the date the work was done, (2) a description of the work done, and (3) the name, certificate number, and signature of the person performing the work or approving the return to service. As applied to database updates, it's a stupid rule, for exactly the reasons you cite, but it's still the rule--or was until a couple of days ago. Surprisingly enough, the FAA seems to have realized that the times, they are a-changin'.

[1964-M20E]

Like many things in life common sense and what works do not always follow the rules to the letter but rather fufill the intent.

[fantom]

Thank The Lord.......many of us can finally update our very antiquated DBs ;-)