Return-Path: Sender: (Marvin Kaye) To: lml Date: Mon, 02 Dec 2002 12:17:58 -0500 Message-ID: X-Original-Return-Path: Received: from [198.36.178.141] (HELO stoel.com) by logan.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 1892782 for lml@lancaironline.net; Mon, 02 Dec 2002 12:00:44 -0500 Received: from pdx-smtp.stoel.com ([172.16.1.137]) by gateway1.stoel.com with ESMTP id <119312>; Mon, 2 Dec 2002 08:59:53 -0800 Received: from PDX-MX1.stoel.com ([172.16.1.172]) by pdx-smtp.stoel.com with Microsoft SMTPSVC(5.0.2195.5329); Mon, 2 Dec 2002 09:00:29 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: Re: Direct Routings X-Original-Date: Mon, 2 Dec 2002 09:00:24 -0800 X-Original-Message-ID: <5458ED2469307644B8BA64EDE0FD441753845E@PDX-MX1.stoel.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: Direct Routings Thread-Index: AcKaJE25qTluJgYTEdeKmQAQS/k/NQ== From: "Halle, John" X-Original-To: X-Original-Return-Path: JJHALLE@stoel.com X-OriginalArrivalTime: 02 Dec 2002 17:00:29.0089 (UTC) FILETIME=[51284910:01C29A24] Actually the subject is getting more interesting. My autopilot = (TruTrak) uses gps as its primary data source. As a result, in the = GPS-S or Track Modes, under normal circumstances, it flies a track = rather than a heading. The other mode is coupled to a VOR or LOC, in = which case, of course, it flies the selected radial. TruTrak is working = on a coupler to a HSI or DG that would permit it to fly a heading but = has not completed it and does not anticipate that it will be widely = used. In its present configuration, the only way I can fly a heading on = autopilot (as, for example, when I get a vector from ATC) is to select a = track on the autopilot that I think will work and then keep adjusting it = so as to maintain a heading as indicated on my HSI. Here is what the people I have called have to say about the subject: EAA: Never heard of the issue and have no knowledge of any FAA plan to = give track vectors AOPA: Ditto FAA: Do not give track vectors and have no plan to do so. TruTrak: Don't worry about it. Unless you have a hellacious crosswind, = the difference won't matter. None of these answers is particularly satisfying. It would be nice if = the FAA had some interest in joining the rest of us in the 21st century.