X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: To: lml@lancaironline.net Date: Mon, 23 Apr 2012 00:53:08 -0400 Message-ID: X-Original-Return-Path: Received: from st11p01mm-asmtpout002.mac.com ([17.172.204.237] verified) by logan.com (CommuniGate Pro SMTP 5.4.4) with ESMTP id 5501180 for lml@lancaironline.net; Sun, 22 Apr 2012 18:32:52 -0400 Received-SPF: pass receiver=logan.com; client-ip=17.172.204.237; envelope-from=alcornl@me.com MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_OdHgLBbmukEf5Bfmk6UNgw)" Received: from st11p01mm-spool002.mac.com ([17.172.204.247]) by st11p01mm-asmtp002.mac.com (Oracle Communications Messaging Server 7u4-23.01(7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0M2W000O0JXHFSA0@st11p01mm-asmtp002.mac.com> for lml@lancaironline.net; Sun, 22 Apr 2012 22:32:08 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.6.7580,1.0.260,0.0.0000 definitions=2012-04-22_07:2012-04-21,2012-04-22,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=1 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1012030000 definitions=main-1204220309 Received: from localhost ([17.172.204.222]) by st11p01mm-spool002.mac.com (Oracle Communications Messaging Server 7u4-23.01(7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0M2W00KDVJXIX530@st11p01mm-spool002.mac.com> for lml@lancaironline.net; Sun, 22 Apr 2012 22:32:06 +0000 (GMT) X-Original-To: lml@lancaironline.net From: Luke Alcorn Subject: Re: [LML] Re: ensure your transponder works X-Original-Date: Sun, 22 Apr 2012 22:32:04 +0000 (GMT) X-Mailer: MobileMe Mail (1I09.7849) X-Originating-IP: [75.148.66.66] X-Original-Message-id: <207010b7-64a0-4ce1-b0fc-b0e248daaf21@me.com> --Boundary_(ID_OdHgLBbmukEf5Bfmk6UNgw) Content-type: text/plain; charset=utf-8; format=flowed Content-transfer-encoding: quoted-printable Since the Northwest overflight of MSP a couple of years ago, the FAA is ho= t and heavy on NORDO's, i.e. lost comms. They make us hunt down aircraft = like crazy. Since Jan, 2012, the FAA has implemented a new quality contro= l system and before a nordo was handled in each atc facility. Now we just= report the aircraft nordo and a report is filed as to how long they were = out of comms. Those reports for straight to the regional quality assuranc= e office and they determine whether or not to file a pilot deviation. The= new standard is 20 minutes. If it is longer than 20 minutes, the regiona= l QA sends the pilot deviation report to FSDO. Not much we can do about i= t anymore, other than tell everyone, make sure your talking to atc every 2= 0 minutes. =20 Luke Alcorn NATCA ZJX Safety Rep=EF=BB=BF --Boundary_(ID_OdHgLBbmukEf5Bfmk6UNgw) Content-type: multipart/related; boundary="Boundary_(ID_GODrFaDgAg1L1TLh4+Lr6w)"; type="text/html" --Boundary_(ID_GODrFaDgAg1L1TLh4+Lr6w) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: 7BIT

Since the Northwest overflight of MSP a couple of years ago, the FAA is hot and heavy on NORDO's, i.e. lost comms. They make us hunt down aircraft like crazy. Since Jan, 2012, the FAA has implemented a new quality control system and before a nordo was handled in each atc facility. Now we just report the aircraft nordo and a report is filed as to how long they were out of comms. Those reports for straight to the regional quality assurance office and they determine whether or not to file a pilot deviation. The new standard is 20 minutes. If it is longer than 20 minutes, the regional QA sends the pilot deviation report to FSDO. Not much we can do about it anymore, other than tell everyone, make sure your talking to atc every 20 minutes.

Luke Alcorn
NATCA ZJX Safety Rep

--Boundary_(ID_GODrFaDgAg1L1TLh4+Lr6w)-- --Boundary_(ID_OdHgLBbmukEf5Bfmk6UNgw)--