  | 
				Matronics Email Lists Web Forum Interface to the Matronics Email Lists   
				 | 
			 
		 
		 
	
		| View previous topic :: View next topic   | 
	 
	
	
		| Author | 
		Message | 
	 
	
		philperry9
 
 
  Joined: 23 Nov 2011 Posts: 381
 
  | 
		
			
				 Posted: Wed Apr 26, 2017 6:05 am    Post subject: Logbook Entries | 
				     | 
			 
			
				
  | 
			 
			
				Does anyone know of a site that has sample language for logbook entries?   For example, I need to add my MT-Prop gov SB entry.  I need to show that I checked AD's for my engine.  I need to show that I've started the conditional inspection...
 
 I don't have much info on how those entries should be formatted and I'm hoping there is a site or FAA doc in existence that outlines the format for those entries.
 I'm a logbook rookie.
 Phil
 
  |  | - The Matronics RV10-List Email Forum - |  |   |  Use the List Feature Navigator to browse the many List utilities available such as the Email Subscriptions page, Archive Search & Download, 7-Day Browse, Chat, FAQ, Photoshare, and much more:
 
  http://www.matronics.com/Navigator?RV10-List |  
  |  
 
 
 
 
  | 
			 
		  | 
	 
	
		| Back to top | 
		 | 
	 
	
		  | 
	 
	
		Tim Olson
 
 
  Joined: 25 Jan 2007 Posts: 2882
 
  | 
		
			
				 Posted: Wed Apr 26, 2017 7:02 am    Post subject: Logbook Entries | 
				     | 
			 
			
				
  | 
			 
			
				I think for many of them you can just use your best common sense
 and try to provide enough detail that someone in the future
 could look and understand what was done and why.
 
 The language for the annual condition inspection is in your
 operating limitations and is pretty standard, so that one
 is easy, but I don't think there is any need to show
 that you've STARTED the inspection, just do an entry when you
 are done with it.  The start date of an inspection isn't
 the relevant date...it's the completed date that matters.
 
 That log entry usually looks like:  "I certify that this
 aircraft has been inspected on X/X/2017 in accordance with the
 scope and detail of FAR part 43, Appendix D, and was found to
 be in the condition for safe operation."
 
 I personally when doing the ACI, don't log every individual
 task, such as "repacked wheel bearings", but only list any
 that are significant for some reason.  I also log all of
 the cylinder compressions for historical reasons.
 
 Here's an example of what I did for a recent fuel pump
 log entry.  Someone like Kelly may be able to confirm
 if it's adequate.
 "Replaced fuel pump model 62B26931 s/n RC4214036826 with
 s/n RC12161697 per Lycoming SB-621B."
 
 Generally, if you are supposed to follow a procedure, you
 may want to reference it as "per XYZ" or something that
 shows where you got the guidance.  Other than that it's
 pretty much up to you.  I try to include part and serial
 numbers for anything I can, and if there was a reason why
 something needed to be done due to wear or damage, I note
 that.
 
 Here's another entry for a while ago:
 "Replaced Slick Harness M-2961 (Left) with new Aero-Lite Skytronics 
 A18-11AS-II harness (Kelly KA16014) due to loose spring on #5 wire at 
 cap end and blackening of rotor cap on old mag.  Replaced AN900-10 
 gasket on Oil temp housing plug."
 
 And another one:
 "Performed SB 14-8-29 per SB instructions, installing doubler above nose 
 gear elastomers on engine mount."
 
 An A&P like Kelly McMullen would probably have good info on
 a reference to use for examples, and maybe he can comment
 on if what I've done above is even adequate.  I personally
 don't feel they're too inadequate, but wouldn't mind a
 second opinion.
 
 The important thing is to show what parts went in and out,
 any relevant info on those parts, and what procedures were
 done and why, as far as I'm concerned.  Then you're doing
 a good job trying to provide a traceable history of the
 aircraft and engine.
 
 Tim
 
 
 On 4/26/2017 9:04 AM, Phillip Perry wrote:
  	  | Quote: | 	 		   Does anyone know of a site that has sample language for logbook entries?
    For example, I need to add my MT-Prop gov SB entry.  I need to show
  that I checked AD's for my engine.  I need to show that I've started the
  conditional inspection...
 
  I don't have much info on how those entries should be formatted and I'm
  hoping there is a site or FAA doc in existence that outlines the format
  for those entries.
 
  I'm a logbook rookie.
 
  Phil
 
 
 | 	 
 
 
  |  | - The Matronics RV10-List Email Forum - |  |   |  Use the List Feature Navigator to browse the many List utilities available such as the Email Subscriptions page, Archive Search & Download, 7-Day Browse, Chat, FAQ, Photoshare, and much more:
 
  http://www.matronics.com/Navigator?RV10-List |  
  |  
 
 
 
 
  | 
			 
		  | 
	 
	
		| Back to top | 
		 | 
	 
	
		  | 
	 
	
		Kellym
 
 
  Joined: 10 Jan 2006 Posts: 1706 Location: Sun Lakes AZ
  | 
		
			
				 Posted: Wed Apr 26, 2017 12:17 pm    Post subject: Logbook Entries | 
				     | 
			 
			
				
  | 
			 
			
				What is needed is listed in Part 43.9:
 1. description of work performed. 2 Date of completion of work
 3. Name of person performing the work (if other than the person 
 approving the work)
 4. Signature and certificate number of person approving the work.
 #3 isn't needed for OBAM. #4. no certificate number is needed for OBAM 
 aircraft, although you could put your repairman number.
 You can put total time, if you choose to track it for maintenance purposes.
 Additional guidance in AC43.9C Maintenance Records
 Note that inspection records are a little different in contents and 
 approval.
 Tim's suggestions are right on track. Including part numbers is 
 excellent. Serial numbers are not so important unless it is major item 
 that you want to track replacement..engine, prop, perhaps major 
 accessories like governor, mags, alternator, starter. It helps if say an 
 AD were to be issued on certain Skytec starters, so you don't have to go 
 find the physical serial number later.
 
 On 4/26/2017 8:02 AM, Tim Olson wrote:
  	  | Quote: | 	 		   
  
  I think for many of them you can just use your best common sense
  and try to provide enough detail that someone in the future
  could look and understand what was done and why.
  
  The language for the annual condition inspection is in your
  operating limitations and is pretty standard, so that one
  is easy, but I don't think there is any need to show
  that you've STARTED the inspection, just do an entry when you
  are done with it.  The start date of an inspection isn't
  the relevant date...it's the completed date that matters.
  
  That log entry usually looks like:  "I certify that this
  aircraft has been inspected on X/X/2017 in accordance with the
  scope and detail of FAR part 43, Appendix D, and was found to
  be in the condition for safe operation."
  
  I personally when doing the ACI, don't log every individual
  task, such as "repacked wheel bearings", but only list any
  that are significant for some reason.  I also log all of
  the cylinder compressions for historical reasons.
  
  Here's an example of what I did for a recent fuel pump
  log entry.  Someone like Kelly may be able to confirm
  if it's adequate.
  "Replaced fuel pump model 62B26931 s/n RC4214036826 with
  s/n RC12161697 per Lycoming SB-621B."
  
  Generally, if you are supposed to follow a procedure, you
  may want to reference it as "per XYZ" or something that
  shows where you got the guidance.  Other than that it's
  pretty much up to you.  I try to include part and serial
  numbers for anything I can, and if there was a reason why
  something needed to be done due to wear or damage, I note
  that.
  
  Here's another entry for a while ago:
  "Replaced Slick Harness M-2961 (Left) with new Aero-Lite Skytronics 
  A18-11AS-II harness (Kelly KA16014) due to loose spring on #5 wire at 
  cap end and blackening of rotor cap on old mag.  Replaced AN900-10 
  gasket on Oil temp housing plug."
  
  And another one:
  "Performed SB 14-8-29 per SB instructions, installing doubler above nose 
  gear elastomers on engine mount."
  
  An A&P like Kelly McMullen would probably have good info on
  a reference to use for examples, and maybe he can comment
  on if what I've done above is even adequate.  I personally
  don't feel they're too inadequate, but wouldn't mind a
  second opinion.
  
  The important thing is to show what parts went in and out,
  any relevant info on those parts, and what procedures were
  done and why, as far as I'm concerned.  Then you're doing
  a good job trying to provide a traceable history of the
  aircraft and engine.
  
  Tim
  
  
  
  
  On 4/26/2017 9:04 AM, Phillip Perry wrote:
 > Does anyone know of a site that has sample language for logbook entries?
 >   For example, I need to add my MT-Prop gov SB entry.  I need to show
 > that I checked AD's for my engine.  I need to show that I've started the
 > conditional inspection...
 >
 > I don't have much info on how those entries should be formatted and I'm
 > hoping there is a site or FAA doc in existence that outlines the format
 > for those entries.
 >
 > I'm a logbook rookie.
 >
 > Phil
 >
  
  
  
  
  | 	 
 
 
  |  | - The Matronics RV10-List Email Forum - |  |   |  Use the List Feature Navigator to browse the many List utilities available such as the Email Subscriptions page, Archive Search & Download, 7-Day Browse, Chat, FAQ, Photoshare, and much more:
 
  http://www.matronics.com/Navigator?RV10-List |  
  |  
 
 
 
 
  _________________ Kelly McMullen
 
A&P/IA, EAA Tech Counselor # 5286
 
KCHD | 
			 
		  | 
	 
	
		| Back to top | 
		 | 
	 
	
		  | 
	 
	
		 | 
	 
 
  
	 
	    
	   | 
	
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum
  | 
   
 
  
Powered by phpBB © 2001, 2005 phpBB Group
  
		 |