Return-Path: Sender: (Marvin Kaye) To: lml@lancaironline.net Date: Wed, 07 Jan 2004 11:00:47 -0500 Message-ID: X-Original-Return-Path: <5zq@cox.net> Received: from lakemtao04.cox.net ([68.1.17.241] verified) by logan.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 2921072 for lml@lancaironline.net; Wed, 07 Jan 2004 08:35:57 -0500 Received: from OFFICE ([68.110.249.147]) by lakemtao04.cox.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with SMTP id <20040107133556.BXNA19895.lakemtao04.cox.net@OFFICE> for ; Wed, 7 Jan 2004 08:35:56 -0500 X-Original-Message-ID: <020c01c3d523$2884cf70$6501a8c0@OFFICE> From: "Bill&Sue" <5zq@cox.net> X-Original-To: "Lancair Mailing List" References: Subject: Re: [LML] Hobbs and timekeeping X-Original-Date: Wed, 7 Jan 2004 08:35:47 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0209_01C3D4F9.3F88A1D0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 This is a multi-part message in MIME format. ------=_NextPart_000_0209_01C3D4F9.3F88A1D0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi guys, I hate to keep beating a dead horse, especially about a minor symantic = matter that is truly the FAA's fault for defining the way they did. = Walter and Jim just sent out posts that might add (understandably) to = the confusion about wording. Walter: " 15% difference between block to block and flight times" Jim: "That gives you flight time and total time on the engine" Here's the way I used to teach it. Look at the terms "Flight Time" and = "Time In Service". Define them in the way that a reasonable person who = understands the English language and logic would. FT would be the time = the airplane is flying, ie; off to on. Time in service would include = other things such as taxiing, ie; block to block. Now... consider who made up the official definitions. That's right, = the FAA so of course the official definitions are exactly opposite of = what the reasonable person above would conclude.=20 It also helps to remember that they are used for different purposes. = FT is what you put in your PILOT logbook. TIS is what goes in the = AIRFRAME and ENGINE logbooks.=20 Sorry about being so anal about this. They'll have me back on my = medication soon and might let me out in public so I'll have other = outlets for my ranting. Bill Harrelson 5zq@cox.net N5ZQ LNC2 Dogwood Airpark Fredericksburg, VA ------=_NextPart_000_0209_01C3D4F9.3F88A1D0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
 
Hi guys,
 
I hate to keep beating a dead horse, = especially=20 about a minor symantic matter that is truly the FAA's fault for = defining the=20 way they did. Walter and Jim just sent out posts that might add=20 (understandably) to the confusion about wording.
 
Walter:  " 15% difference = between block to=20 block and flight times"
 
Jim: "That gives you flight time and = total time=20 on the engine"
 
Here's the way I used to = teach it. Look=20 at the terms "Flight Time" and "Time In Service". Define them in the = way that=20 a reasonable person who understands the English language and logic = would. FT=20 would be the time the airplane is flying, ie; off to on. Time in = service would=20 include other things such as taxiing, ie; block to block.
 
Now... consider who made up the = official=20 definitions.  That's right, the FAA so of course the official = definitions=20 are exactly opposite of what the reasonable person above would conclude.=20
 
It also helps to remember that they are used for different = purposes. FT=20 is what you put in your PILOT logbook. TIS is what goes in the = AIRFRAME=20 and ENGINE logbooks.
 
Sorry about being so anal about this. = They'll=20 have me back on my medication soon and  might let me out in public so I'll have other outlets = for=20 my ranting.
 
Bill Harrelson
5zq@cox.net   N5ZQ =20 LNC2   Dogwood Airpark     = Fredericksburg,=20 VA 
------=_NextPart_000_0209_01C3D4F9.3F88A1D0--