X-Virus-Scanned: clean according to Sophos on Logan.com
Return-Path: <marv@lancaironline.net>
Sender: <marv@lancaironline.net>
To:  lml@lancaironline.net
Date: Thu, 21 Jul 2011 07:50:07 -0400
Message-ID: <redirect-5058967@logan.com>
X-Original-Return-Path: <rwolf99@aol.com>
Received: from imr-mb02.mx.aol.com ([64.12.207.163] verified)
  by logan.com (CommuniGate Pro SMTP 5.4.0)
  with ESMTP id 5058642 for lml@lancaironline.net; Wed, 20 Jul 2011 22:50:01 -0400
Received-SPF: pass
 receiver=logan.com; client-ip=64.12.207.163; envelope-from=rwolf99@aol.com
Received: from mtaomg-da05.r1000.mx.aol.com (mtaomg-da05.r1000.mx.aol.com [172.29.51.141])
	by imr-mb02.mx.aol.com (8.14.1/8.14.1) with ESMTP id p6L2nO0D015662
	for <lml@lancaironline.net>; Wed, 20 Jul 2011 22:49:24 -0400
Received: from core-dqb003a.r1000.mail.aol.com (core-dqb003.r1000.mail.aol.com [172.29.212.201])
	by mtaomg-da05.r1000.mx.aol.com (OMAG/Core Interface) with ESMTP id 0CF9FE00008B
	for <lml@lancaironline.net>; Wed, 20 Jul 2011 22:49:24 -0400 (EDT)
X-Original-To: lml@lancaironline.net
Subject: Re:  Flight following in SoCal
X-MB-Message-Source: WebUI
X-AOL-IP: 174.18.240.58
X-MB-Message-Type: User
MIME-Version: 1.0
From: rwolf99@aol.com
Content-Type: multipart/alternative; 
 boundary="--------MB_8CE1567EED4F905_B88_3AFDE_webmail-m004.sysops.aol.com"
X-Mailer: AOL Webmail 33972-STANDARD
Received: from 174.18.240.58 by webmail-m004.sysops.aol.com (64.12.101.87) with HTTP (WebMailUI); Wed, 20 Jul 2011 22:49:23 -0400
X-Original-Message-Id: <8CE1567EED4F905-B88-18EC0@webmail-m004.sysops.aol.com>
X-Originating-IP: [174.18.240.58]
X-Original-Date: Wed, 20 Jul 2011 22:49:23 -0400 (EDT)
x-aol-global-disposition: G
X-AOL-SCOLL-SCORE: 0:2:490882144:93952408  
X-AOL-SCOLL-URL_COUNT: 0  
x-aol-sid: 3039ac1d338d4e2793b40793

This is a multi-part message in MIME format.
----------MB_8CE1567EED4F905_B88_3AFDE_webmail-m004.sysops.aol.com
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="us-ascii"


Craig, et al --

Thanks for the suggestions.  I will try them when I next get the chance.  Y=
es, I can see how having an IFR flight plan in the system would help, even =
if you only activate it when you contact LA Center or SoCal.  And clearance=
 delivery should be able to pave the way, too.  Good ideas.

It's been about a decade since I flew in the Los Angeles basin.  I hope to =
be flying the Lancair there next year (but hey, I've said that every year..=
.)

- Rob Wolf
Tucson AZ
Ryan Airport




----------MB_8CE1567EED4F905_B88_3AFDE_webmail-m004.sysops.aol.com
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="us-ascii"

<font color=3D'black' size=3D'2' face=3D'arial'>
<div>Craig, et al --</div>


<div>&nbsp;</div>


<div>Thanks for the suggestions.&nbsp; I will try them when I next get the =
chance.&nbsp; Yes, I can see how having an IFR flight plan in the system wo=
uld help, even if you only activate it when you contact LA Center or SoCal.=
&nbsp; And clearance delivery should be able to pave the way, too.&nbsp; Go=
od ideas.</div>


<div>&nbsp;</div>


<div>It's been about a decade since I flew in the Los Angeles basin.&nbsp; =
I hope to be flying the Lancair there next year (but hey, I've said that ev=
ery year...)</div>


<div>&nbsp;</div>


<div>- Rob Wolf</div>


<div>Tucson AZ</div>


<div>Ryan Airport<br>
<br>
</div>


<div style=3D"CLEAR: both"></div>
</font>
----------MB_8CE1567EED4F905_B88_3AFDE_webmail-m004.sysops.aol.com--