GPS database updates.... pilot or maintenance item?

Patrick

Well-Known Member
Under Part 91, 135, or 121?

For further clarification, in this instance, we are not referring to FMS type units, but something along the lines of a GNS530 or G1000, and also not something like a KLN-94.

CFR 14, Appendix A to part 43 would seem to make this pretty clear that it is a maintenance item.

Further, if 121 or 135, as far as I can tell, there would need to be something in the Op Specs giving authority to a pilot to perform this function.

Virtually all 135's that I'm aware of consider this a maintenance item, just like many 135's require that adding a quart of oil to a turbine engine be done by maintenance personnel.

Discuss....
 
Personally, I don't believe it is a maintenance item. If it was, wouldn't it require a maintenance logbook entry every time it is updated? Seems a little ridiculous.
 
Personally, I don't believe it is a maintenance item. If it was, wouldn't it require a maintenance logbook entry every time it is updated? Seems a little ridiculous.

It is, it does, and it is.

Speaking only for Part 91 operations...it's a preventative maintenance item.

14 CFR 43 Appendix A
(32) Updating self-contained, front instrument panel-mounted Air Traffic Control (ATC) navigational software data bases (excluding those of automatic flight control systems, transponders, and microwave frequency distance measuring equipment (DME)) provided no disassembly of the unit is required and pertinent instructions are provided. Prior to the unit's intended use, an operational check must be performed in accordance with applicable sections of part 91 of this chapter.

14 CFR 43.9
(1) A description (or reference to data acceptable to the Administrator) of work performed.

(2) The date of completion of the work performed.

(3) The name of the person performing the work if other than the person specified in paragraph (a)(4) of this section.

(4) If the work performed on the aircraft, airframe, aircraft engine, propeller, appliance, or component part has been performed satisfactorily, the signature, certificate number, and kind of certificate held by the person approving the work. The signature constitutes the approval for return to service only for the work performed.
 
It is, it does, and it is.

Speaking only for Part 91 operations...it's a preventative maintenance item.

14 CFR 43 Appendix A
(32) Updating self-contained, front instrument panel-mounted Air Traffic Control (ATC) navigational software data bases (excluding those of automatic flight control systems, transponders, and microwave frequency distance measuring equipment (DME)) provided no disassembly of the unit is required and pertinent instructions are provided. Prior to the unit's intended use, an operational check must be performed in accordance with applicable sections of part 91 of this chapter.

14 CFR 43.9
(1) A description (or reference to data acceptable to the Administrator) of work performed.

(2) The date of completion of the work performed.

(3) The name of the person performing the work if other than the person specified in paragraph (a)(4) of this section.

(4) If the work performed on the aircraft, airframe, aircraft engine, propeller, appliance, or component part has been performed satisfactorily, the signature, certificate number, and kind of certificate held by the person approving the work. The signature constitutes the approval for return to service only for the work performed.

This is exactly what I'm looking at. If 135, this automatically becomes a maintenance item. I can't sign it off, because I'm not an A&P.
 
I've always seen it as a pilots responsibility but that may be different because my company maintains a part 91 status. We are also in remote locations for most of our work trips. I've always been the one having to update it otherwise I can't fly.
 
Under 135, it is definitely a mx item. Even as a pilot/a&p you can't update it unless you are part of the companies mx program.
 
Preventative maintenance under part 43, pilot performable if your particular operation allows it.


Sent from 1865 by telegraph....
 
We do, it's kinda ridiculous, we came up with a little 8 to a page form that you just fill in and sign.


Sent from 1865 by telegraph....
 
On CMP it's tracked on a 28 day cycle (funny coincidence, but that's when the databases expire). Has to be performed and signed off by MX, along with EGPWS updates.
 
There is a big ol checklist for it. Yes. For something as simple as a GPS update.

We can all agree that this is 100% ridiculous. However, as with many things, the FAA frequently does not make simple things simple when it comes to the legality of such.

In this specific instance, at my current 135 operator, our Chief Pilot, and to make matters worse, POI, seem to be of the opinion that this is something that can be done by the pilot, whereas, anyone and everyone else seem to understand that it's a maintenance item (as ridiculous as that is). While I'm happy to go burn duty time to go update the thing, there's no way for me to legally log the update, therefore, I'm just not going to do it.

While the FAA seems to be moving in the direction of making this a pilot duty, until the FAA makes it crystal clear that this is a) a pilot duty, and b) provides for a procedure to make it legal, I'm not doing it.
 
Ya we have a checklist to follow. Which ultimately leads to an entry in the AML saying that we completed a GPS database update.
 
I saw, once upon a time, a gps update that came with a sticker. Inserting the sticker in the log book satisfied corrective action write ups.

Put card in, update, put sticker in log, sin and date, call it good ...
 
Back
Top