X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: To: lml@lancaironline.net Date: Mon, 24 Feb 2014 07:24:40 -0500 Message-ID: X-Original-Return-Path: <2thman1@gmail.com> Received: from mail-pd0-f181.google.com ([209.85.192.181] verified) by logan.com (CommuniGate Pro SMTP 6.0.8) with ESMTPS id 6745143 for lml@lancaironline.net; Sat, 22 Feb 2014 22:43:19 -0500 Received-SPF: pass receiver=logan.com; client-ip=209.85.192.181; envelope-from=2thman1@gmail.com Received: by mail-pd0-f181.google.com with SMTP id p10so461238pdj.26 for ; Sat, 22 Feb 2014 19:42:42 -0800 (PST) X-Received: by 10.66.27.13 with SMTP id p13mr17332104pag.76.1393126962581; Sat, 22 Feb 2014 19:42:42 -0800 (PST) X-Original-Return-Path: <2thman1@gmail.com> Received: from [192.168.1.24] ([183.182.124.72]) by mx.google.com with ESMTPSA id n6sm36109842pbj.22.2014.02.22.19.42.36 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 22 Feb 2014 19:42:41 -0800 (PST) References: In-Reply-To: Mime-Version: 1.0 (1.0) Content-Type: multipart/alternative; boundary=Apple-Mail-92737372-6098-4582-8E5C-C31F5DA0B9A8 X-Original-Message-Id: <047A1084-43BE-4541-A3CC-250B88AAC1C9@gmail.com> Content-Transfer-Encoding: 7bit X-Mailer: iPad Mail (11B554a) From: John Barrett <2thman1@gmail.com> Subject: Re: [LML] Re: Legacy Accident History Update X-Original-Date: Sun, 23 Feb 2014 10:42:35 +0700 X-Original-To: Lancair Mailing List --Apple-Mail-92737372-6098-4582-8E5C-C31F5DA0B9A8 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Had that happen years ago leaving BFI on IFR going over Cascades in my Beech= Sierra. Had alternator failure while VMC so cancelled and went back to BFI= to land. A few days later got calls from FAA wanting me to contact them. M= ade me nervous but turned out a new controller was being out through his pac= es so they were training him how to follow up on an incident. Whew! John Barrett Sent from my iPad > On Feb 23, 2014, at 3:17 AM, "Bill Bradburry" w= rote: >=20 > You never know what is going to happen when you are dealing with the FAA. = I departed a class C airport and just after departure released me, the engi= ne had a short spell of rough running. I decided to return to check it out o= n the ground even though it had already cleared. I called approach and beca= use I had just left them, I mistakenly felt it necessary to tell them why I w= as returning. When I landed 4 fire trucks followed me all the way to my han= gar. I wound up having to have a couple of half hour conversations with the= FSDO and send in all kinds of records as to what I had done to resolve the i= ssue. > =20 > B2 > =20 > From: Lancair Mailing List [mailto:lml@lancaironline.net] On Behalf Of Tho= rn, Valin B. (JSC-VA411) > Sent: Friday, February 21, 2014 1:26 PM > To: lml@lancaironline.net > Subject: [LML] Re: Legacy Accident History Update > =20 > Hello Jay, > =20 > Really glad your incident was minor after your brakes failed and regret th= at the database drawn from had incorrect data in it.=20 > =20 > The source for that listed incident was found in the Flight Safety Foundat= ion=E2=80=99s Aviation Safety Network Wiki Database =E2=80=93 ASN Occurrence= #138988 -- http://aviation-safety.net/wikibase/wiki.php?id=3D138988 . My s= ummary description drew from their narrative and it listed the airplane dama= ge as =E2=80=9CSubstantial=E2=80=9D. =20 > =20 > Narrative: > The pilot says he was attempting to land his Lancair Legacy 2000 at M. Gra= ham Clark Field/Taney County Airport (KPLK, Bransom, MO, and "bounced" whwn t= rying to land. The right side of the aircraft then went off the pavement int= o the grass, where the aircraft spun and came to a stop. > =20 > See the ASN record below. =20 > =20 > I=E2=80=99m not sure how things find their way to that data base =E2=80=93= but, there is a link you can go to and submit corrected information http://= aviation-safety.net/wikibase/web_db_edit.php?id=3D138988 . My guess is that= once the incident was properly reviewed and that facts understood that the p= reliminary data was never corrected. =46rom the revision history and cited s= ources at the bottom of the record, the editors were probably drawing from l= ocal news reporting which is typically inaccurate=E2=80=A6 > =20 > I=E2=80=99ll correct my record of it. > =20 > Thanks, > =20 > Valin > =20 > > > =20 > =20 > From: Lancair Mailing List [mailto:lml@lancaironline.net] On Behalf Of Jay= Phillips > Sent: Friday, February 21, 2014 8:02 AM > To: lml@lancaironline.net > Subject: [LML] Re: Legacy Accident History Update > =20 > #28 was me. I don=E2=80=99t know what your definition of =E2=80=9Csubstant= ial=E2=80=9D. The FAA and NTSB deemed it to be a taxi =E2=80=9Cincident=E2=80= =9D, i.e. the brakes failed during roll out. Don=E2=80=99t know where you go= t =E2=80=9Cbounce=E2=80=9D from. Makes me wonder about your other data. > =20 > Jay Phillips > =20 > From: Lancair Mailing List [mailto:lml@lancaironline.net] On Behalf Of Val= in & Allyson Thorn > Sent: Friday, February 21, 2014 6:00 AM > To: lml@lancaironline.net > Subject: [LML] Legacy Accident History Update > =20 > We hope to have the first flight of our Legacy later this year and was sur= prised so many underwriters were no longer insuring the Legacy. This motiva= ted me to relook at the accident record and update the summary table I made a= nd sent to the LML when looking at this five years ago. See the updated tab= le below. The accident record is disappointing and this probably hasn=E2=80= =99t even captured all the accidents worldwide. If anyone knows of any not s= hown here please let me know. > =20 > I found a total of 18 fatal accidents with 27 fatalities since the first (= non-fatal) accident in September 2003. So there is an average of almost 2 f= atal accidents per year since then. I estimate approximately 150 flying Lan= cair Legacy airplanes (does anyone have a confirmed number?). With that as a= basis, and just counting the years since the first accident, there=E2=80=99= s an annual probability of any particular Legacy having a fatal accident of a= bout 1 in 80.=20 > =20 > Much can be learned from looking at general aviation accident records and s= tatistics to make us safer/better pilots =E2=80=93 but, looking at the speci= fic record of the airplane you=E2=80=99re flying and/or building is most sob= ering=E2=80=A6=20 > =20 > Here are some of my take-a-ways from the Legacy=E2=80=99s accident history= =E2=80=A6 > =20 > 1. Get transition and regular refresher training from experienced Le= gacy flight instructors =E2=80=93 maintain proficiency. > 2. Install and use an angle of attack sensor for all flight phases. > 3. Install a canopy down and latched indicator =E2=80=93 simple, two= micro-switches and a light. If the canopy does open in flight, ignore the j= unk blowing around the cockpit, fly the airplane, get some good altitude, an= d workout the most stable speed to fly it back to landing. Install canopy o= pening/closing mod that doesn=E2=80=99t allow the canopy to go all the way d= own unless latched (see Don Barnes=E2=80=99 website, builder tips) > 4. Practice, practice, practice engine out failures and glides to em= ergency landings. > 5. Care for and maintain your engine like your life depends on it =E2= =80=93 since it does. > =20 > It=E2=80=99s beyond sad that so many of our pilot brothers have lost their= lives flying the Legacy. This accident history illustrates clearly higher r= isk compared to the typical personal airplane. But from the reports of vete= ran Legacy flyers, I hold on to the belief that the Legacy is an amazing, fa= st, and beautiful airplane that just demands some unique handling and discip= line beyond the typical personal airplane to fly it safely...=20 > =20 > Valin Thorn > Legacy Project > Boulder, Colorado > =20 > =20 > =20 > Lancair Legacy Accident & Incident Record > =20 > =20 > =20 > =20 > =20 > February 2014 > =20 > =20 > =20 > =20 > =20 > =20 > =20 > =20 > =20 > =20 > =20 > =20 > =20 > =20 > Accident Number > Summary Description > Event > Location > Make / Model > Regist. > Fatalities > Total Deaths to Date > Date > Number > 34 > Stall just after takeoff > 10/25/2013 > Shepparton, Australia > Lancair Legacy =20 > VH-ICZ > 2 > 27 > 33 > Stall just after takeoff > 9/18/2013 > Geraldton, Australia > Lancair Legacy =20 > VH-ALP > 1 > 25 > 32 > IMC loss of fuel pressure then smoke in cockpit, crashed 4 miles short of a= irport > 3/31/2013 > Winston-Salem, NC > Lancair Legacy =20 > =20 > 2 > 24 > 31 > Lost control on landing, broke in three pieces > 5/1/2012 > Animas Airpark,=20 > Durango, CO > Campbell Lancair Legacy > N12KX > 0 > 22 > 30 > Training flight, crashed into terrain, cause unknown > 3/10/2012 > Sao Paulo Brazil > Lancair Legacy =20 > PT-ZZR > 2 > 22 > 29 > Collision with power lines 25 ft high, 1.2 miles from departure runway in n= ight VMC. > 3/1/2012 > Belen, NM > Hemp Lancair Legacy > N273TE =20 > 2 > 20 > 28 > Bounced landing, ran off runway, substantial damage > 10/5/2011 > KPLK, Bransom, MO > Evans Lancair Legacy > N92SX > 0 > 18 > 27 > Impacted snow covered mountain at 6500 ft MSL in VMC under unknown circums= tances, 78 yr old pilot > 5/18/2011 > Pioneer, CA > Cameron Lancair Legacy > N121J > 1 > 18 > 26 > Unnecessary forced landing, crashed 3 miles short of runway. Ran left tan= k dry but right tank full of fuel, selector found in wreckage set for left t= ank. > 5/6/2011 > Richlands, NC > Peter Hebert Lancair Legacy > N23PH > 2 > 17 > 25 > Early morning night landing at Kansas City Int'l, landed in grass between t= axi ways and struck airport sign, substantial damage > 5/2/2011 > Kanasa City, MO > Prichard Lancair Legacy > N50KP > 0 > 15 > 24 > Nose gear collapse on landing, minor damage > 2/6/2011 > San Jose Airport, CA > Bereznak Lancair Legacy > N817CB > 0 > 15 > 23 > Deice sys failure, ice on aircraft, left wing dipped abruptly on landing, g= ear collapsed, substantial damage > 12/25/2010 > Oakland/Troy Airport, MI > Bowers Harbor Legacy > N384AS > 0 > 15 > 22 > Engine failure, forced landing, pax injured > 9/12/2010 > Okahandja, Namibia > Onderstall Lancair Legacy > ZU-FCY > 0 > 15 > 21 > Take off in squall conditions with 20 kt crosswind gusting to 32 kts, subs= tantial damage > 6/25/2010 > Burns, OR > Meyer Lancair Legacy > N29MM > 0 > 15 > 20 > Engine failure from oil starvation, stall crash on forced landing > 11/21/2009 > Watsonville, CA > Budd Lancair Legacy > N7JX > 1 > 15 > 19 > Pilot reports very difficult aircraft pitch control from open canopy on ta= keoff, crash landed short of runway returning to land > 2/6/2009 > Longmont, CO > Lancair Legacy =20 > N939CB > 0 > 14 > 18 > Ran off end of runway on hot/fast landing, runway 5841 ft long > 11/2/2008 =20 > Socorro, NM =20 > Hemp Lancair Legacy > N273TE =20 > 0 > 14 > 17 > Takeoff without canopy latched. Pilot likely impaired by pain med's and o= bstructive sleep apnea. > 10/18/2008 =20 > Parowan, UT =20 > Heisler Lancair Legacy =20 > N151HT =20 > 1 > 14 > 16 > Stall at low altitude on final at Oshkosh AirVenture > 7/31/2008 =20 > OSHKOSH, WI > Moser Lancair Legacy FG > N515RB =20 > 2 > 13 > 15 > Engine mechanical failure, forced landing short of runway, sheared off mai= n wheels, failed connecting rod not from engine OEM > 6/8/2008 =20 > Bend, OR =20 > Lancair Prototype Legacy 2000 =20 > N199L =20 > 0 > 11 > 14 > Fuel exhaustion during touch and go practice, stall/spin at low altitude o= n aggressive turn toward runway > 5/30/2008 =20 > Murrieta, CA =20 > Poulin L/Cullen D Lancair Legacy FG > N109DC =20 > 2 > 11 > 13 > Stall, crash on takeoff. Distracted, challenged by open canopy on take of= f > 4/13/2008 =20 > Lakeland, FL =20 > Dayon Thomas Lancair Legacy =20 > N1177M =20 > 1 > 9 > 12 > Smoke in cockpit, possible fire onboard, forced landing in rocky terrain > 4/1/2008 > Krugersdorp Game Reserve, South Africa > Lancair Legacy =20 > ZU-EFC > 1 > 8 > 11 > Aircraft veered off course after missed ILS approach crashing on road 4500= ft from approach end of runway > 2/16/2008 > Portland, OR > Legacy FG > =20 > 1 > 7 > 10 > Engine failure on first flight, possible cause mixture control attachment l= oose > 4/14/2007 =20 > Fulton, NY =20 > Romeo Lancair Legacy RG =20 > N45FR =20 > 2 > 6 > 9 > Take off with canopy unlatched, lost control, severe crash and injuries > 8/26/2005 > Ems, Austria > Hohenemser Lancair Legacy > N345MW > 0 > 4 > 8 > Stall spin, factory Legacy FG > 8/15/2005 =20 > Madras, OR =20 > Lancair Legacy FG Prototype > N359L =20 > 2 > 4 > 7 > Fuel exhaustion, forced landing, mis-calibrated fuel sensors > 8/14/2005 =20 > Groveland, CA =20 > Barnes Lancair Legacy =20 > N508DB =20 > 0 > 2 > 6 > Engine failure, cause unknown, forced landing in rocky field, landing gear= separated, post-crash fire destroyed airplane > 5/1/2005 =20 > Nacogdoches, TX =20 > Lancair Legacy =20 > N204RH =20 > 0 > 2 > 5 > Gear not extended for landing > 4/8/2005 =20 > Bend, OR =20 > Shannon Lancair Legacy > N115YP =20 > 0 > 2 > 4 > Wing skin on upper left stub wing separated in flight, landed safely, exam= ination showed poor bond > 9/12/2004 > Cambridge, OH > Lancair Legacy =20 > =20 > 0 > 2 > 3 > Engine failure with continuous warning signs months before total failure. = Super-charged engine. Engine tear down showed one piston burned through an= d other heat damage. Landing options overflown. Crashed in city. > 8/1/2004 =20 > Madison, WI =20 > Knoepflein Lancair Legacy > N98SN =20 > 1 > 2 > 2 > Flew into Level 4 & 5 thunderstorms with ATC assistance > 4/23/2004 =20 > Oakland, TN =20 > Durr Lancair Legacy =20 > N511WD =20 > 1 > 1 > 1 > Takeoff with pitot covered, takeoff aborted, ran off end of 2600 ft runway= , substantial damage > 9/19/2003 =20 > Kimberling City, MO =20 > Brice Lancair Legacy =20 > N27RM =20 > 0 > 0 > =20 > =20 > =20 > =20 > =20 > =20 > =20 --Apple-Mail-92737372-6098-4582-8E5C-C31F5DA0B9A8 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Had that happen years ago leaving BFI o= n IFR going over Cascades in my Beech Sierra.  Had alternator failure w= hile VMC so cancelled and went back to BFI to land.  A few days later g= ot calls from FAA wanting me to contact them.  Made me nervous but turn= ed out a new controller was being out through his paces so they were trainin= g him how to follow up on an incident.  Whew!

= John Barrett

Sent from my iPad


On Feb 23= , 2014, at 3:17 AM, "Bill Bradburry" <bbradburry@bellsouth.net> wrote:

=

You never know what is going to happen when you are dealing with the FAA.  I departed a class C airport and ju= st after departure released me, the engine had a short spell of rough running.  I= decided to return to check it out on the ground even though it had already cleared.  I called approach and because I had just left them, I mistake= nly felt it necessary to tell them why I was returning.  When I landed 4 fi= re trucks followed me all the way to my hangar.  I wound up having to have= a couple of half hour conversations with the FSDO and send in all kinds of records as to what I had done to resolve the issue.=

 

B2

 


From: Lancair Mailing List [mailto:lml@lancaironline.net] On Behalf Of Thorn, Valin B. (JSC-VA411)
Sent: Friday, February 21, 20= 14 1:26 PM
To: lml@lancaironline.net
Subject: [LML] Re: Legacy Acc= ident History Update

 

Hello Jay,

 

Really glad your incident was minor after your brakes failed and regret that the databas= e drawn from had incorrect data in it. 

 

The source for that listed incident was found in the Flight Safety Foundation=E2=80=99s= Aviation Safety Network Wiki Database =E2=80=93 ASN Occurrence #138988 -- http://av= iation-safety.net/wikibase/wiki.php?id=3D138988 .  My summary description drew from their narrative and it listed the airplane damage as =E2=80=9CSubstantial=E2=80=9D.  

 

Narrative:
The pilot says he was attempting to land his Lancair Legacy 2000 at M. Graha= m Clark Field/Taney County Airport (KPLK, Bransom, MO, and "bounced" whwn trying to land. The right side of the aircraft then went off the pavement in= to the grass, where the aircraft spun and came to a stop.

 

See the ASN record below.  

 

I=E2=80=99m not sure how things find their way to that data base =E2=80=93 but, there is= a link you can go to and submit corrected information http://aviation-safety.n= et/wikibase/web_db_edit.php?id=3D138988 .  My guess is that once the incident was properly reviewed and that fa= cts understood that the preliminary data was never corrected.  =46rom the revision history and cited sources at the bottom of the record, the editors were probably drawing from local news reporting which is typically inaccurate=E2=80=A6

 

I=E2=80=99ll correct my record of it.

 

Thanks,

 

Valin

 

<image001.jpg&= gt;=

<image002.jpg&= gt;=

 

 

From: Lancair Mailing List [mailto:lml@lancaironline.net] On Behalf Of Jay Phillips
Sent: Friday, February 21, 20= 14 8:02 AM
To: lml@lancaironline.net
Subject: [LML] Re: Legacy Acc= ident History Update

 

<= span style=3D"font-size:11.0pt;color:#1F497D">#28 was me. I don=E2=80=99t kn= ow what your definition of =E2=80=9Csubstantial=E2=80=9D. The FAA and NTSB deemed it to b= e a taxi =E2=80=9Cincident=E2=80=9D, i.e. the brakes failed during roll out. Don=E2=80=99t know where you got =E2=80=9Cbounce=E2=80=9D from. Makes me won= der about your other data.

<= span style=3D"font-size:11.0pt;color:#1F497D"> 

<= span style=3D"font-size:11.0pt;color:#1F497D">Jay Phillips=

<= span style=3D"font-size:11.0pt;color:#1F497D"> 

From: Lancair Mailing List [mailto:lml@lancaironline.net] On Behalf Of Valin & Allyson Thorn
Sent: Friday, February 21, 20= 14 6:00 AM
To: lml@lancaironline.net
Subject: [LML] Legacy Acciden= t History Update

 

We hope to have the first flight of our Legacy later this year and was surprised so man= y underwriters were no longer insuring the Legacy.  This motivated me to relook at the accident record and update the summary table I made and sent t= o the LML when looking at this five years ago.  See the updated table below.   The accident record is disappointing and this probably hasn=E2=80=99t even captured all the accidents worldwide.  If anyone kn= ows of any not shown here please let me know.

 

I found a total of 18 fatal accidents with 27 fatalities since the first (non-fatal) accident in September 2003.  So there is an average of almost 2 fatal accidents per year since then.  I estimate approximately 150 flying Lancair Legacy airplanes (does anyone have a confirmed number?).  With that as a basis, and just counting the years since the first accident, there=E2=80=99s an annual probability of any particular Legacy having a fata= l accident of about 1 in 80. 

 

Much can be learned from looking at general aviation accident records and statistics to make us safer/better pilots =E2=80=93 but, looking at the specific record of= the airplane you=E2=80=99re flying and/or building is most sobering=E2=80=A6&nbs= p;

 

Here are some of my take-a-ways from the Legacy=E2=80=99s accident history=E2=80=A6

 

1.       Get transition and regular refresher training from experience= d Legacy flight instructors =E2=80=93 maintain proficiency.<= /font>

2.       Install and use an angle of attack sensor for all flight phas= es.

3.       Install a canopy down and latched indicator =E2=80=93 simple,= two micro-switches and a light.  If the canopy does open in flight, ignore t= he junk blowing around the cockpit, fly the airplane, get some good altitude, a= nd workout the most stable speed to fly it back to landing.  Install canop= y opening/closing mod that doesn=E2=80=99t allow the canopy to go all the way d= own unless latched (see Don Barnes=E2=80=99 website, builder tips)

4.       Practice, practice, practice engine out failures and glides t= o emergency landings.

5.       Care for and maintain your engine like your life depends on i= t =E2=80=93 since it does.

 

It=E2=80=99s beyond sad that so many of our pilot brothers have lost their lives flying t= he Legacy.  This accident history illustrates clearly higher risk compared= to the typical personal airplane.  But from the reports of veteran Legacy flyers, I hold on to the belief that the Legacy is an amazing, fast, and beautiful airplane that just demands some unique handling and discipline bey= ond the typical personal airplane to fly it safely... 

 

Valin Thorn

Legacy Project

Boulder, Colorado

 

 

 

Lancair Lega= cy Accident & Incident Record

 

 

 

 

 

February 201= 4

 

 

 

 

 

 

 <= /o:p>

 <= /o:p>

 <= /o:p>

 <= /o:p>

 <= /o:p>

 <= /o:p>

 <= /o:p>

 <= /o:p>

Accident Number

Summary Description

Event

Location

Make / Model

Regist.

Fatalities

Total Deaths to Date

Date

Number

34

<= span style=3D"font-size:11.0pt;color:black">Stall just after takeoff

10/25/2013

Shepparton, Australia

Lancair Legacy  

VH-ICZ

2

27

33

<= span style=3D"font-size:11.0pt;color:black">Stall just after takeoff

9/18/2013

Geraldton, Australia

Lancair Legacy  

VH-ALP

1

25

32

<= span style=3D"font-size:11.0pt;color:black">IMC loss of fuel pressure then s= moke in cockpit, crashed 4 miles short of airport

3/31/2013

Winston-Salem, NC<= /font>

Lancair Legacy  

 

2

24

31

<= span style=3D"font-size:11.0pt;color:black">Lost control on landing, broke i= n three pieces

5/1/2012

Animas Airpark,
Durango, CO

Campbell Lancair Legacy=

N12KX

0

22

30

<= span style=3D"font-size:11.0pt;color:black">Training flight, crashed into te= rrain, cause unknown

3/10/2012

Sao Paulo Brazil

Lancair Legacy  

PT-ZZR

2

22

29

<= span style=3D"font-size:11.0pt;color:black">Collision with power lines 25 ft= high, 1.2 miles from departure runway in night VMC.

=

3/1/2012

Belen, NM

Hemp Lancair Legacy

N273TE  

2

20

28

<= span style=3D"font-size:11.0pt;color:black">Bounced landing, ran off runway,= substantial damage

10/5/2011

KPLK, Bransom, MO

Evans Lancair Legacy

N92SX

0

18

27

<= span style=3D"font-size:11.0pt;color:black">Impacted snow covered mountain a= t 6500 ft MSL in VMC under unknown circumstances, 78 yr old pilot

5/18/2011

Pioneer, CA

Cameron Lancair Legacy

N121J

1

18

26

<= span style=3D"font-size:11.0pt;color:black">Unnecessary forced landing, cras= hed 3 miles short of runway.  Ran left tank dry but right tank full of fuel= , selector found in wreckage set for left tank.

=

5/6/2011

Richlands, NC<= /span>

Peter Hebert Lancair Legacy

N23PH

2

17

25

<= span style=3D"font-size:11.0pt;color:black">Early morning night landing at K= ansas City Int'l, landed in grass between taxi ways and struck airport sign, substantial damage

5/2/2011

Kanasa City<= span style=3D"color:black">, MO

Prichard Lancair Legacy=

N50KP

0

15

24

<= span style=3D"font-size:11.0pt;color:black">Nose gear collapse on landing, m= inor damage

2/6/2011

San Jose Airport, CA=

Bereznak Lancair Legacy

N817CB

0

15

23

<= span style=3D"font-size:11.0pt;color:black">Deice sys failure, ice on aircra= ft, left wing dipped abruptly on landing, gear collapsed, substantial damage

12/25/2010

Oakland/Troy Airport, MI

Bowers<= span style=3D"color:black"> Harbor Legacy

N384AS

0

15

22

<= span style=3D"font-size:11.0pt;color:black">Engine failure, forced landing, p= ax injured

9/12/2010

Okahandja, Namibia

Onderstall Lancair Legacy

ZU-FCY

0

15

21

<= span style=3D"font-size:11.0pt;color:black">Take off in squall conditions wi= th 20 kt crosswind gusting to 32 kts, substantial damage

6/25/2010

Burns, OR

Meyer Lancair Legacy

N29MM

0

15

20

<= span style=3D"font-size:11.0pt;color:black">Engine failure from oil starvati= on, stall crash on forced landing

11/21/2009

Watsonville<= span style=3D"color:black">, CA

Budd Lancair Legacy

N7JX

1

15

19

<= span style=3D"font-size:11.0pt;color:black">Pilot reports very difficult air= craft pitch control from open canopy on takeoff, crash landed short of runway returning to land

2/6/2009

Longmont, CO

Lancair Legacy  

N939CB

0

14

18

<= span style=3D"font-size:11.0pt;color:black">Ran off end of runway on hot/fas= t landing, runway 5841 ft long

11/2/2008  

Socorro, NM=  

Hemp Lancair Legacy

N273TE  

0

14

17

<= span style=3D"font-size:11.0pt;color:black">Takeoff without canopy latched.&= nbsp; Pilot likely impaired by pain med's and obstructive sleep apnea.

10/18/2008  

Parowan, UT=  

Heisler Lancair Legacy  

N151HT  

1

14

16

<= span style=3D"font-size:11.0pt;color:black">Stall at low altitude on final a= t Oshkosh AirVenture

7/31/2008  

OSHKOSH, WI=

Moser Lancair Legacy FG

N515RB  

2

13

15

<= span style=3D"font-size:11.0pt;color:black">Engine mechanical failure, force= d landing short of runway, sheared off main wheels, failed connecting rod no= t from engine OEM

6/8/2008  

Bend, OR  

Lancair Prototype Legacy 2000  

N199L  

0

11

14

<= span style=3D"font-size:11.0pt;color:black">Fuel exhaustion during touch and= go practice, stall/spin at low altitude on aggressive turn toward runway=

5/30/2008  

Murrieta, CA  <= /o:p>

Poulin L/Cullen D Lancair Legacy  FG

N109DC  

2

11

13

<= span style=3D"font-size:11.0pt;color:black">Stall, crash on takeoff.  D= istracted, challenged by open canopy on take off

4/13/2008  

Lakeland, FL  <= /o:p>

Dayon Thomas Lancair Legacy  

N1177M  

1

9

12

<= span style=3D"font-size:11.0pt;color:black">Smoke in cockpit, possible fire o= nboard, forced landing in rocky terrain

4/1/2008

Krugersdorp Game Reserve, South Africa

Lancair Legacy  

ZU-EFC

1

8

11

<= span style=3D"font-size:11.0pt;color:black">Aircraft veered off course after= missed ILS approach crashing on road 4500 ft from approach end of runway

2/16/2008

Portland, OR

Legacy FG

 

1

7

10

<= span style=3D"font-size:11.0pt;color:black">Engine failure on first flight, p= ossible cause mixture control attachment loose

4/14/2007  

Fulton, NY  

Romeo Lancair Legacy RG  

N45FR  

2

6

9

<= span style=3D"font-size:11.0pt;color:black">Take off with canopy unlatched, l= ost control, severe crash and injuries

8/26/2005

Ems, Austria

Hohenemser Lancair Legacy

N345MW

0

4

8

<= span style=3D"font-size:11.0pt;color:black">Stall spin, factory Legacy FG

8/15/2005  

Madras, OR  

Lancair Legacy FG Prototype

N359L  

2

4

7

<= span style=3D"font-size:11.0pt;color:black">Fuel exhaustion, forced landing,= mis-calibrated fuel sensors

8/14/2005  

Groveland, CA  =

Barnes Lancair Legacy  

N508DB  

0

2

6

<= span style=3D"font-size:11.0pt;color:black">Engine failure, cause unknown, f= orced landing in rocky field, landing gear separated, post-crash fire destroyed airplane

5/1/2005  

Nacogdoches<= span style=3D"color:black">, TX  

Lancair Legacy  

N204RH  

0

2

5

<= span style=3D"font-size:11.0pt;color:black">Gear not extended for landing

4/8/2005  

Bend, OR  

Shannon Lancair Legacy

N115YP  

0

2

4

<= span style=3D"font-size:11.0pt;color:black">Wing skin on upper left stub win= g separated in flight, landed safely, examination showed poor bond

9/12/2004

Cambridge, OH<= /span>

Lancair Legacy  

 

0

2

3

<= span style=3D"font-size:11.0pt;color:black">Engine failure with continuous w= arning signs months before total failure.  Super-charged engine.  Engin= e tear down showed one piston burned through and other heat damage.  Landing options overflown. Crashed in city.

8/1/2004  

Madison, WI=  

Knoepflein Lancair Legacy

N98SN  

1

2

2

<= span style=3D"font-size:11.0pt;color:black">Flew into Level 4 & 5 thunde= rstorms with ATC assistance

4/23/2004  

Oakland, TN=  

Durr Lancair Legacy  

N511WD  

1

1

1

<= span style=3D"font-size:11.0pt;color:black">Takeoff with pitot covered, take= off aborted, ran off end of 2600 ft runway, substantial damage

9/19/2003  

Kimberling City, MO  = ;

Brice Lancair Legacy  

N27RM  

0

0

 

 

 

 

 

 

 

= --Apple-Mail-92737372-6098-4582-8E5C-C31F5DA0B9A8--