X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: To: lml@lancaironline.net Date: Sat, 13 May 2006 14:47:30 -0400 Message-ID: X-Original-Return-Path: Received: from imo-m27.mx.aol.com ([64.12.137.8] verified) by logan.com (CommuniGate Pro SMTP 5.0.9) with ESMTP id 1111914 for lml@lancaironline.net; Sat, 13 May 2006 11:06:56 -0400 Received-SPF: pass receiver=logan.com; client-ip=64.12.137.8; envelope-from=Sky2high@aol.com Received: from Sky2high@aol.com by imo-m27.mx.aol.com (mail_out_v38_r7.5.) id q.405.1db8c10 (65098) for ; Sat, 13 May 2006 11:06:07 -0400 (EDT) From: Sky2high@aol.com X-Original-Message-ID: <405.1db8c10.31974fdf@aol.com> X-Original-Date: Sat, 13 May 2006 11:06:07 EDT Subject: Re: [LML] Re: IVP Crash X-Original-To: lml@lancaironline.net MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-----------------------------1147532767" X-Mailer: 9.0 Security Edition for Windows sub 5300 X-Spam-Flag: NO -------------------------------1147532767 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In a message dated 5/13/2006 9:02:07 A.M. Central Standard Time, RicArgente@cs.com writes: So far all we know is that the engine sputtered on takeoff, YES. An attempt was made to turn back to the airport--MAYBE NOT! This is NOT a definite. Grease, Fine. I do want to know more about the sputtering engine. Did it reach full power on the take off run? Was there a contaminant that reached the engine just at rotation? In other words, what was the physical failure that led to the rest? Should the takeoff been aborted? Indeed, David may have been maneuvering to avoid buildings (thus people) on the ground. We all know that these things stop flying when they go too slow. Below is a photo of runway 6/24 at Somerset (Airnav, 2G9) taken from the 24 end (opposite the takeoff direction). The road to the right (281) is somewhat parallel to the runway (4600 feet, 2272 MSL) and could have been a potential set down target after lift off from 06. Yes, it was a sad, sad day............ Grayhawk PS the satellite view of the region was too fuzzy. Try zillow.com and look about 2 mi NE of Somerset, PA. -------------------------------1147532767 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

In a message dated 5/13/2006 9:02:07 A.M. Central Standard Time,=20 RicArgente@cs.com writes:

<= FONT=20 style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000 size= =3D2>So far=20 all we know is that the engine sputtered on takeoff, YES. An attempt= was=20 made to turn back to the airport--MAYBE NOT! This is NOT a=20 definite.

Grease,

Fine. I do want to know more about the sputtering engine.&nb= sp;=20 Did it reach full power on the take off run? Was there a contaminant t= hat=20 reached the engine just at rotation? In other words, what was the phys= ical=20 failure that led to the rest? Should the takeoff been aborted?

Indeed, David may have been maneuvering to avoid buildings (thus people= ) on=20 the ground. We all know that these things stop flying when they go too= =20 slow.

Below is a photo of runway 6/24 at Somerset (Airnav, 2G9) taken from th= e 24=20 end (opposite the takeoff direction). The road to the right (281)=20 is somewhat parallel to the runway (4600 feet, 2272 MSL) and could have= =20 been a potential set down target after lift off from 06.

Yes, it was a sad, sad day............

Grayhawk

PS the satellite view of the region was too fuzzy. Try zillow.com= and=20 look about 2 mi NE of Somerset, PA.

-------------------------------1147532767--