X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: To: lml@lancaironline.net Date: Wed, 23 Jan 2013 08:27:55 -0500 Message-ID: X-Original-Return-Path: Received: from vms173019pub.verizon.net ([206.46.173.19] verified) by logan.com (CommuniGate Pro SMTP 6.0.1) with ESMTP id 6024820 for lml@lancaironline.net; Tue, 22 Jan 2013 21:01:15 -0500 Received-SPF: pass receiver=logan.com; client-ip=206.46.173.19; envelope-from=skipslater@verizon.net Received: from SkipPC ([unknown] [96.229.61.38]) by vms173019.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0MH2004ZJ2WY4W10@vms173019.mailsrvcs.net> for lml@lancaironline.net; Tue, 22 Jan 2013 20:00:35 -0600 (CST) X-Original-Message-id: <7D2B4E24AB4747E5B6E4D5D7EDB7653C@SkipPC> From: "Skip Slater" X-Original-To: "Lancair Mailing List" References: In-reply-to: Subject: Re: [LML] Re: WPR13FA076 X-Original-Date: Tue, 22 Jan 2013 18:00:05 -0800 MIME-version: 1.0 Content-type: multipart/alternative; boundary="----=_NextPart_000_0019_01CDF8CA.4F05E100" X-Priority: 3 X-MSMail-priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8089.726 X-MIMEOLE: Produced By Microsoft MimeOLE V14.0.8089.726 This is a multi-part message in MIME format. ------=_NextPart_000_0019_01CDF8CA.4F05E100 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Sounds like we're in complete agreement on this one Don! Skip -------------------------------------------------------------------------= -------------------------------------------------------------------------= --------------------------------------------------------- i agree that it is a common clearance but it is an instrument clearance = and IFR rules prevail. If IMC is anticipated then one needs clearance = from ATC prior to entering. The controllers assume that you are IFR = qualified, IFR current in make and model. Its only if something goes = wrong that the Feds will come calling and you better have the i's dotted = and the t's crossed. If your VFR, then you are to remain clear of clouds = at all time. When going up you are supposed to get a clearance from atc = and have to read it back. Inbound you have to ask for clearance and = readbck prior to entering IMC. If not ifr qualified then you should = advise atc that you are unable. They are providing separation from other = traffic who are anticipating a sterile pathway. ------=_NextPart_000_0019_01CDF8CA.4F05E100 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable
Sounds like we're in complete agreement = on this one=20 Don!
Skip
------------------------------------------------------------= -------------------------------------------------------------------------= ----------------------------------------------------------------------
i agree that it is a = common=20 clearance but it is an instrument clearance and IFR rules = prevail. If IMC=20 is anticipated then one needs clearance from ATC prior to entering. The=20 controllers assume that you are IFR qualified, IFR current in make and = model.=20 Its only if something goes wrong that the Feds will come calling and you = better=20 have the i's dotted and the t's crossed. If your VFR, then you are to = remain=20 clear of clouds at all time. When going up you are supposed to get a = clearance=20 from atc and have to read it back. Inbound you have to ask for clearance = and=20 readbck prior to entering IMC. If not ifr qualified then you should = advise atc=20 that you are unable. They are providing separation from other traffic = who are=20 anticipating a sterile pathway.
------=_NextPart_000_0019_01CDF8CA.4F05E100--