Welcome to Flightinfo.com

  • Register now and join the discussion
  • Friendliest aviation Ccmmunity on the web
  • Modern site for PC's, Phones, Tablets - no 3rd party apps required
  • Ask questions, help others, promote aviation
  • Share the passion for aviation
  • Invite everyone to Flightinfo.com and let's have fun

Question Logbook entries for avionics updates (experimental aircraft)?

Welcome to Flightinfo.com

  • Register now and join the discussion
  • Modern secure site, no 3rd party apps required
  • Invite your friends
  • Share the passion of aviation
  • Friendliest aviation community on the web

Neal

Forums Chief Pilot
Staff member
Joined
Oct 31, 1996
Posts
1,032
Type aircraft owned
Carbon Cub FX-3
Base airport
KFCI
Ratings
COMM, IFR, MEL, SEL
G3X updates for example seem quite trivial. Do people make logbook entries for avionics updates?
 
I do not make a log entry but I do record every update in my maintenance records.
 
I do not make log updates for firmware or databases
 
There are two classes of updates:
  1. “Database” updates. I think of these in the same way that the aviation regulations require me to carry onboard the latest maps (charts), procedures and airport information. For this I prefer to carry two different sources: Garmin databases in G3X and GNC; and ForeFlight on my iPad mini and not carry paper charts, etc.
  2. “Firmware” updates. These software updates to either the Garmin avionics or to the iPad (iPadOS or ForeFlight) app, I run with a “latest stable version” policy. For example, I have a separate iPad which I use with beta versions of both iPadOS and ForeFlight.
As both of these updates occur very frequently, I have not been making logbook entries unless they are as a resolution to a documented squawk. In the same way that I do not log oil top up’s, tire pressure checks, oil breather cleanings, etc.
 
Having just done the transponder and ADS-B it made me think about this. I think firmware updates are logbook worthy, database not. It can't hurt to log something, just something to think about.

I personally do log oil additions made.
 
I can ask the FAA next week at Airventure for clear direction
 
If you are asking, it would be interesting to hear their opinion on both built-in avionics (e.g. Garmin G3x, GNC, GTX) and portable avionics (e.g. Stratus, EFB).
I will have to assume that in the "certified world", both firmware and database updates are logged for all built-in avionics. As I understand it, if database and/or firmware updates have not been applied to the crew's EFBs, the plane cannot push back; thus, I believe that EFB updates (both firmware and database) are also logged, but just not in the aircraft logs.
 
My hunch is the FAA will say log everything. A little off topic of this thread but during my DAR interview he said if you're going to put camera's on, etc. log after the flight it was flight tested, etc. to cover yourself. A lot of people hang things on these planes, which I won't get started in how dangerous that is in itself, but per the DAR that should be logged.
 
Am I the only one keeping a detailed log?

I maintain a spreadsheet with separate tabs for oil, fuel, maintenance, notes, etc, etc. I have a record of everything that happened to my aircraft since I took delivery. I do it because I find it useful, not because I think there is any requirement to do so.

If you ask FAA they will likely refer you to 14 CFR part 43. You can then point out that 14 CFR Part 43 doesn't apply to experimental aircraft except to the extent called out by the Operating Limitations.

One could follow the requirement of Part 43 and the requirements of your Operating Limitations and then have no doubt that you had met any real, or imagined, requirements.
 
I do not log outside of my 3 logbooks (engine, prop, aircraft).
 

Latest resources

Back
Top