X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: To: lml@lancaironline.net Date: Wed, 04 Mar 2009 08:13:24 -0500 Message-ID: X-Original-Return-Path: Received: from bosmailout17.eigbox.net ([66.96.189.17] verified) by logan.com (CommuniGate Pro SMTP 5.2.12) with ESMTP id 3526006 for lml@lancaironline.net; Tue, 03 Mar 2009 18:40:45 -0500 Received-SPF: pass receiver=logan.com; client-ip=66.96.189.17; envelope-from=SRS0=eRDRq+=7C=mwheli.com=bjburr@eigbox.net Received: from bosmailscan23.eigbox.net ([10.20.15.23]) by bosmailout17.eigbox.net with esmtp (Exim) id 1LeeDZ-0000g1-MU for lml@lancaironline.net; Tue, 03 Mar 2009 18:40:09 -0500 Received: from bosimpout01.eigbox.net ([10.20.55.1]) by bosmailscan23.eigbox.net with esmtp (Exim) id 1LeeDZ-0004Lb-F3 for lml@lancaironline.net; Tue, 03 Mar 2009 18:40:09 -0500 Received: from bosauthsmtp07.eigbox.net ([10.20.18.7]) by bosimpout01.eigbox.net with NO UCE id NjHz1b004099BUA0000000; Tue, 03 Mar 2009 14:17:59 -0500 X-EN-OrigOutIP: 10.20.18.7 X-EN-IMPSID: NjHz1b004099BUA0000000 Received: from c-67-177-32-58.hsd1.ut.comcast.net ([67.177.32.58] helo=[192.168.0.7]) by bosauthsmtp07.eigbox.net with esmtpa (Exim) id 1LeeDY-0004r3-GG for lml@lancaironline.net; Tue, 03 Mar 2009 18:40:08 -0500 X-Original-Message-Id: <1D86498C-01A4-43CD-90BD-1B80832D1BAF@mwheli.com> From: Burr Bryan X-Original-To: List Lancair Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Subject: H.A.I. Response TSA 1542-04-08F X-Original-Date: Tue, 3 Mar 2009 16:40:06 -0700 X-Mailer: Apple Mail (2.930.3) X-EN-UserInfo: afb066d8b4230608b04b264cad72a5d8:59efd05c4346593dae8a30875e4d072b X-EN-AuthUser: bjburr@mwheli.com X-Original-Sender: Burr Bryan X-EN-OrigIP: 67.177.32.58 X-EN-OrigHost: c-67-177-32-58.hsd1.ut.comcast.net Here is Ann Carroll's (from the Helicopter Association International) response to the TSA SD 1542-04-8F. Bryan Burr Lancair Super ES I read thru your email. TSA has been extremely vague with the GA industry regarding implementation of this directive and what the actual requirements are. See additional information put out last week on this issue. We certainly intend to continue pursuing this with TSA along with the large aircraft rule. Let me know if there is anything else I can provide in the way of information or if you have any additional questions or comments. Ann 2/25/2009 The Transportation Security Administration (TSA) yesterday released the following notice to airport operators and tenants on the status of Security Directive (SD) 1542-04-8F. The general aviation industry associations have been working closely with the TSA to minimize the impact this SD has on the general aviation community since its release late last year. The compliance date for SD 1542-04-8F, which requires personnel who have access to the secure areas of commercial airports to undergo Security Threat Assessments and to be badged, has now been extended to June 1, 2009. Operators affected by this SD should work closely with their Federal Security Directors (FSDs) and airport management to ensure they are in compliance by this new deadline. Many members have reported that FSDs and airports are working to identify alternative means of compliance, as provided within the SD, for general aviation entities affected by the SD, as appropriate. For Immediate Dissemination: TO: Airport Operators & Airport Tenants FR: Douglas Hofsass, TSA General Manager For Commercial Aviation As you know, TSA has been working closely with AAAE and ACI on the implementation of SD 1542-04-8F. AAAE and ACI have been providing feedback and suggestions on your behalf since inception. Although TSA provided a fairly large lead time for section II.C, and while we understand that a number of airports have already indicated "compliance" with this section, we are also hearing that a large number of airports need additional time to reach compliance. Many of the airports requesting an extension have been working hard on this requirement for the past 4-6 weeks, but due to the size of the incremental population, reaching compliance by the current deadline is not feasible. Rather than having a large number of individual airports go through their respective FSD's and TSA Headquarters for individual extensions, we have made the decision that we will extend the compliance date for section II.C until June 1, 2009. This means that the current deadline for Cat X's and Cat 1's (which is currently March 1, 2009) and the current deadline for Cat 2's, Cat 3's, and Cat 4's (which is currently April 30, 2009) will be extended until June 1, 2009. As a reminder, section II.C is the section which requires all employees who have unescorted access to the SIDA, Secure, and AOA areas of the airport to have an airport issued ID with an accompanying STA. TSA encourages airports to comply with section II.C sooner than June 1, 2009 if practicable. TSA is committed to providing permanent relief (under section II.M) to those airports who can establish compliance prior to June 1, 2009. As a reminder, TSA recently issued SD 1542-01-10G, which provides "name variance relief" for no-fly comparisons until June 1, 2009. The extension for section II.C is not an extension for the entire SD. TSA will be issuing SD 1542-04-8G in the coming days, which will codify the new compliance dates for section II.C. As a reminder, TSA previously issued guidance exempting US Military and TSA Personnel from the STA requirement, which will also be codified in SD 1542-04-8G. Ann O'Hara Carroll Vice President, Legislative Affairs Helicopter Association International (HAI) 1635 Prince Street Alexandria, Virginia 22314 Bryan Burr President Mountain West Helicopters bjburr@mwheli.com 497 N. Quail Hollow Dr. Alpine, UT 84004 Phone 801-216-4001 Fax 801-216-4004