X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: To: lml@lancaironline.net Date: Fri, 22 Oct 2010 11:17:48 -0400 Message-ID: X-Original-Return-Path: Received: from [70.62.14.124] (HELO ustek.com) by logan.com (CommuniGate Pro SMTP 5.3.10) with ESMTP id 4523435 for lml@lancaironline.net; Fri, 22 Oct 2010 07:53:26 -0400 Received-SPF: pass receiver=logan.com; client-ip=70.62.14.124; envelope-from=r.simon@ustek.com Subject: RE: TFR info (without political commentary) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01CB71E0.2A1BFC62" Content-class: urn:content-classes:message X-Original-Date: Fri, 22 Oct 2010 07:57:21 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 X-Original-Message-ID: In-Reply-To: X-MS-Has-Attach: yes X-MS-TNEF-Correlator: Thread-Topic: TFR info (without political commentary) Thread-Index: Actx4Ejj3Co99wPtRPmEwkOS0N+uLA== References: From: "Lancair" X-Original-Sender: "Robert Simon" X-Original-To: "Bill Kennedy" , This is a multi-part message in MIME format. ------_=_NextPart_001_01CB71E0.2A1BFC62 Content-Type: multipart/alternative; boundary="----_=_NextPart_002_01CB71E0.2A1BFC62" ------_=_NextPart_002_01CB71E0.2A1BFC62 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I flew to MD last weekend to an airport within the Washington DC TFR=20 (By now shouldn't the TFR be renamed? The "T" stands for temporary and it's been 10 years!) =20 I was rerouted a bit coming in but that was minor. Departure required a flight plan be opened, and after 5 phone calls for a void time I gave up and opened in the air over the field. Definately the way to go if it VFR. =20 =20 My return had again a small reroute out of DC but that was minor. The trip home was to have me arriving during one of the many visits by the Commander-in-Chief. Fortunately I was not based at one of the four major airports in Columbus that were within the 10 mile no-fly zone so I was able to plan an IFR flight into KDLZ that was within the 30 mile restricted zone but accessible. Had I been based at Port Columbus, OSU, Bolton, or Rickenbacker I would have had to land elsewhere and wait - although commercial flights (you remember, like the planes that are the cause for the current concern) were still allowed in and out.=20 =20 The situation is simple: the Fed wants to look like they are doing something, they dare not upset the very large constituency that flys commercial tin so instead they restrict private access to the skies. And as long as we get to and from our destinations most of the time, we grin and bear it. I do not expect that to change in my lifetime so I will not waste my time complaining 'cause it will not do any good and the stress could just cost me a medical!=20 =20 Robert M. Simon ES-P N301ES =20 ________________________________ From: Bill Kennedy [mailto:bill_kennedy_3@hotmail.com]=20 Sent: Thursday, October 21, 2010 11:10 PM To: lml@lancaironline.net Subject: TFR info (without political commentary) AOPA member services sent an update on a TFR affecting my home airfield. It included a link to TFR operations, content as follows: Requirements for flight in the outer area: * Limited to arriving or departing local airfields=20 * *Transit operations may be authorized=20 * Must be on active VFR or IFR flight plan=20 * Squawk discrete code obtained from ATC=20 * Two-way communication with ATC=20 * No loitering=20 Operations not authorized: My conclusion: It'd be pretty easy to comply with these rules if I really needed to fly today. ------_=_NextPart_002_01CB71E0.2A1BFC62 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
I flew to MD last weekend to an airport = within the=20 Washington DC TFR
(By now shouldn't the TFR be renamed? = The "T"=20 stands for temporary and it's been 10 years!)
 
I was rerouted a bit coming in but that was=20 minor.  Departure required a flight plan be opened, and after 5 = phone=20 calls for a void time I gave up and opened in the air over the = field.  Definately the way to go if it VFR.  =
 
My return had again a small reroute out of DC = but that=20 was minor.  The trip home was to have me arriving during one of the = many=20 visits by the Commander-in-Chief.  Fortunately I was not based at = one of=20 the four major airports in Columbus that were within the 10 mile no-fly = zone so=20 I was able to plan an IFR flight into KDLZ that was within the 30 mile=20 restricted zone but accessible. Had I been based at Port Columbus, OSU, = Bolton,=20 or Rickenbacker I would have had to land elsewhere and wait - although=20 commercial flights (you remember, like the planes that are the cause for = the=20 current concern) were still allowed in and out.
 
The situation is simple: the Fed wants = to look=20 like they are doing something, they dare not upset the very large = constituency=20 that flys commercial tin so instead they restrict private access to the=20 skies.  And as long as we get to and from our destinations most of = the=20 time, we grin and bear it.  I do not expect that to change in my = lifetime=20 so I will not waste my time complaining 'cause it will not do any = good=20 and the stress could just cost me a = medical! 
 
Robert M. Simon
ES-P N301ES
 

From: Bill Kennedy = [mailto:bill_kennedy_3@hotmail.com]=20
Sent: Thursday, October 21, 2010 11:10 PM
To:=20 lml@lancaironline.net
Subject: TFR info (without political=20 commentary)

AOPA member services sent an update on a TFR affecting my = home=20 airfield. It included a link to TFR operations, content as = follows:

Requirements for flight in the outer area:

  • Limited to arriving or departing local airfields=20
  • *Transit operations may be authorized=20
  • Must be on active VFR or IFR flight plan=20
  • Squawk discrete code obtained from ATC=20
  • Two-way communication with ATC=20
  • No loitering

Operations not authorized:

My conclusion: It'd be pretty easy to = comply=20 with these rules if I really needed to fly today.

------_=_NextPart_002_01CB71E0.2A1BFC62-- ------_=_NextPart_001_01CB71E0.2A1BFC62 Content-Type: text/x-vcard; name="Robert M Simon.vcf" Content-Transfer-Encoding: base64 Content-Description: Robert M Simon.vcf Content-Disposition: attachment; filename="Robert M Simon.vcf" QkVHSU46VkNBUkQNClZFUlNJT046Mi4xDQpOOlNpbW9uO1JvYmVydDtNLg0KRk46Um9iZXJ0IE0u IFNpbW9uDQpPUkc6VVNURUsgSW5jLg0KVElUTEU6UHJlc2lkZW50DQpURUw7V09SSztWT0lDRToo NjE0KSA1MzgtODAwMA0KVEVMO1dPUks7RkFYOig2MTQpIDUzOC04MDAyDQpBRFI7V09SSzo7OzQ2 NjMgRXhlY3V0aXZlIERyaXZlICMzO0NvbHVtYnVzO09IOzQzMjIwLTM2Mjc7VW5pdGVkIFN0YXRl cyBvZiBBbWVyaWNhDQpMQUJFTDtXT1JLO0VOQ09ESU5HPVFVT1RFRC1QUklOVEFCTEU6NDY2MyBF eGVjdXRpdmUgRHJpdmUgIzM9MEQ9MEFDb2x1bWJ1cywgT0ggNDMyMjAtMzYyNz0wRD0wQVVuaXRl ZCBTdGF0ZXMgb2YgQT0NCm1lcmljYQ0KVVJMO1dPUks6aHR0cDovL3d3dy51c3Rlay5jb20NCkVN QUlMO1BSRUY7SU5URVJORVQ6ci5zaW1vbkB1c3Rlay5jb20NClJFVjoyMDEwMDgxMlQxNjM5MzRa DQpFTkQ6VkNBUkQNCg== ------_=_NextPart_001_01CB71E0.2A1BFC62--