X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: To: lml@lancaironline.net Date: Fri, 21 Nov 2008 18:27:54 -0500 Message-ID: X-Original-Return-Path: Received: from bay0-omc1-s8.bay0.hotmail.com ([65.54.246.80] verified) by logan.com (CommuniGate Pro SMTP 5.2.10) with ESMTP id 3311312 for lml@lancaironline.net; Fri, 21 Nov 2008 15:32:47 -0500 Received-SPF: pass receiver=logan.com; client-ip=65.54.246.80; envelope-from=gt_phantom@hotmail.com Received: from hotmail.com ([10.12.232.171]) by bay0-omc1-s8.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 21 Nov 2008 12:32:11 -0800 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 21 Nov 2008 12:32:11 -0800 X-Original-Message-ID: Received: from 24.248.74.254 by COL0-DAV33.phx.gbl with DAV; Fri, 21 Nov 2008 20:32:10 +0000 X-Originating-IP: [24.248.74.254] X-Originating-Email: [gt_phantom@hotmail.com] X-Sender: gt_phantom@hotmail.com From: "GT-Phantom" X-Original-To: Subject: Aircraft FAA Designators X-Original-Date: Fri, 21 Nov 2008 15:32:10 -0500 X-Original-Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_007A_01C94BEE.5211AEC0" X-Mailer: Microsoft Office Outlook 11 Thread-Index: AclMGDrGIc4PpFWDRP2Y+c0waLMN2w== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 X-OriginalArrivalTime: 21 Nov 2008 20:32:11.0616 (UTC) FILETIME=[3B64D600:01C94C18] X-Original-Return-Path: gt_phantom@hotmail.com This is a multi-part message in MIME format. ------=_NextPart_000_007A_01C94BEE.5211AEC0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I mistakenly insisted to someone the other day that LNC2 was a Lancair 235 and therefore a 320/360 must be LNC3. I was wrong, and being the sort to own up to my mistakes I thought I'd send this out (due to a bad case of CRS syndrom, I can't recall who it was...) just in case anyone besides me hadn't gotten the word. I can't imagine why the 320/360 do not have their own identifiers as they are a different airframe than the 2 series, but there go your tax dollars at work. If anything, I would have thought that the ES and 4 would have shared an identifier - but again logic is eschewed. Apparently they haven't gotten around to the new Evolution yet. From the AOPA site: AOPA has compiled the type designators for Lancair kitplanes: Identifier Aircraft Type(s) LEG2 Lancair Legacy 2000 LNC2 Lancair, Neico, Padc, Pai Lancair 200/235/320/360 LNC4 Lancair, Neico, Padc, Pai Lancair 4 LNCE Lancair Lancair Es TGRS Lancair Tigress Cheers, Bill ------=_NextPart_000_007A_01C94BEE.5211AEC0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I = mistakenly=20 insisted to someone the other day that LNC2 was a Lancair 235 and = therefore a=20 320/360 must be LNC3.

I was = wrong, and=20 being the sort to own up to my mistakes I thought I'd send this out (due = to a=20 bad case of CRS syndrom, I can't recall who it was...) just in case = anyone=20 besides me hadn't gotten the word.

I = can't imagine why=20 the 320/360 do not have their own identifiers as they are a different = airframe=20 than the 2 series, but there go your tax dollars at work. If = anything, I=20 would have thought that the ES and 4 would have shared an identifier - = but again=20 logic is eschewed.

Apparently they=20 haven't gotten around to the new Evolution yet.

From = the AOPA=20 site:

AOPA has compiled the type designators for Lancair = kitplanes:

Identifier	Aircraft Type(s)
LEG2	Lancair Legacy 2000
LNC2	Lancair, Neico, Padc, Pai Lancair 200/235/320/360
LNC4	Lancair, Neico, Padc, Pai Lancair 4
LNCE	Lancair Lancair Es
TGRS	Lancair Tigress

Cheers,

Bill

------=_NextPart_000_007A_01C94BEE.5211AEC0--