Today's Message Index:
----------------------
1. 10:11 AM - RV-10 on ice (Dawson-Townsend,Timothy)
2. 10:31 AM - Re: RV-10 on ice (Alan Mekler)
3. 06:09 PM - Re: RV-10 down (Jim)
4. 06:25 PM - Re: Re: RV-10 down (Seano)
5. 06:25 PM - Re: Re: RV-10 down (Seano)
6. 06:25 PM - Re: Re: RV-10 down (Seano)
Message 1
| INDEX | Back to Main INDEX |
| NEXT | Skip to NEXT Message |
| LIST | Reply to LIST Regarding this Message |
| SENDER | Reply to SENDER Regarding this Message |
|
Are we the first RV-10 to land on the ice runway at Alton Bay, NH? The ice
runway season for the last two years has been cut short by unpredictable w
eather, but this year's earlier cold snap got a nice base of the hard stuff
.
Just pick a day with minimal crosswind and it's not too tricky . .. .
On Flickr: http://www.flickr.com/x/t/0094009/photos/93596491@N08/850343468
7/
Tim Dawson-Townsend
N52KS
Message 2
| INDEX | Back to Main INDEX |
| PREVIOUS | Skip to PREVIOUS Message |
| NEXT | Skip to NEXT Message |
| LIST | Reply to LIST Regarding this Message |
| SENDER | Reply to SENDER Regarding this Message |
|
| Subject: | Re: RV-10 on ice |
Tim,
I'm based close by at KLCI.
Over the years there have been lots of mishaps at Alton Bay so I haven't lan
ded my 10 there. I worry about the differential breaking for steering on ice
. I have flown a 172 in there. With snow banks I worry about the low wing o
n the 10.
Friday was a nice day- light winds.
Did you stop at Shibley's for lunch?
Alan
N668G
Sent from my iPad
On Feb 24, 2013, at 1:09 PM, "Dawson-Townsend,Timothy" <tdawson-townsend@aur
ora.aero> wrote:
> Are we the first RV-10 to land on the ice runway at Alton Bay, NH? The ic
e runway season for the last two years has been cut short by unpredictable w
eather, but this year's earlier cold snap got a nice base of the hard stuff.
>
> Just pick a day with minimal crosswind and it's not too tricky . .. .
>
> On Flickr: http://www.flickr.com/x/t/0094009/photos/93596491@N08/85034346
87/
>
> Tim Dawson-Townsend
> N52KS
>
>
==========================
=========
==========================
=========
==========================
=========
==========================
=========
>
Message 3
| INDEX | Back to Main INDEX |
| PREVIOUS | Skip to PREVIOUS Message |
| NEXT | Skip to NEXT Message |
| LIST | Reply to LIST Regarding this Message |
| SENDER | Reply to SENDER Regarding this Message |
|
>From a BeechTalk post...
I got the cliff notes of the story from Frank this morning I may not have this
completely correct but here's the gist of what happened. What was most scary
about hearing him tell this to me is I could see getting sucked in to the same
kind of situation. Just like they always tell us, accidents are usually caused
by what seems (at the time) like a a chain of minor events and if you can break
the chain then it doesn't happen. If you don't break it, you look up just
in time to hit the side of a mountain.
Frank told his friends he didn't want to land at night but he knew they were calling
it close. He got two weather briefings via AOPA & Foreflight and also called
FAA for an update on the way to the airport, he also called the airport for
a first hand report he said he was mostly thinking about ice. They got off
on time but fought a 47 kt headwinds and so they got there later than planned
(surprise 1) . He picked up an IFR clearance for the GPS approach. While shooting
the approach he got a visual on the airport (when looking down, he said it
looked like daylight down there) so he canceled (or got cleared for the visual
I'm not sure I've got this part correct). He dropped down below the clouds
and it was much darker than above (surprise 2), he clicked the airport lights
and they wouldn't come on (turns out they have been having troubles with them
but there were no notams) (surprise 3), at the same time one of his the big EFIS
displays wouldn't dim (surprise 4). Frank said he thought he spent maybe 20-30
seconds trying to rectify these problems rather than going missed. He did
decide to go missed but hit the side of the mountain as he was executing and hitting
buttons.
in retrospect Frank said he should have gone missed with ANY problem but these
other factors sucked him into thinking he could quickly fix them and land. In
another friend's words "that's why they call it an "accident" rather than an
"on purpose"".
Franks said it is a miracle to be alive, they hiked to the crash site today and
he said it really hit him how lucky they were. A cut finger, a bruised face and
frostbite is the worst of the physical injuries. He feels terrible about putting
his friends in harms way and it's gonna take some time for him to forgive
himself.
Sent from my iPad
==
Message 4
| INDEX | Back to Main INDEX |
| PREVIOUS | Skip to PREVIOUS Message |
| NEXT | Skip to NEXT Message |
| LIST | Reply to LIST Regarding this Message |
| SENDER | Reply to SENDER Regarding this Message |
|
Accidents happen. Glad they are ok.
Interested to see if terrain aural warnings were on during IFR and/or
synthetic vision.
----- Original Message -----
From: "Jim" <fehdxlbb@gmail.com>
Sent: Sunday, February 24, 2013 7:04 PM
Subject: RV10-List: Re: RV-10 down
>
>>From a BeechTalk post...
>
> I got the cliff notes of the story from Frank this morning I may not
> have this completely correct but here's the gist of what happened. What
> was most scary about hearing him tell this to me is I could see getting
> sucked in to the same kind of situation. Just like they always tell us,
> accidents are usually caused by what seems (at the time) like a a chain of
> minor events and if you can break the chain then it doesn't happen. If you
> don't break it, you look up just in time to hit the side of a mountain.
>
> Frank told his friends he didn't want to land at night but he knew they
> were calling it close. He got two weather briefings via AOPA & Foreflight
> and also called FAA for an update on the way to the airport, he also
> called the airport for a first hand report he said he was mostly
> thinking about ice. They got off on time but fought a 47 kt headwinds and
> so they got there later than planned (surprise 1) . He picked up an IFR
> clearance for the GPS approach. While shooting the approach he got a
> visual on the airport (when looking down, he said it looked like daylight
> down there) so he canceled (or got cleared for the visual I'm not sure
> I've got this part correct). He dropped down below the clouds and it was
> much darker than above (surprise 2), he clicked the airport lights and
> they wouldn't come on (turns out they have been having troubles with them
> but there were no notams) (surprise 3), at the same time one of his the
> big EFIS displays wouldn't dim (surprise 4). Frank said!
> he thought he spent maybe 20-30 seconds trying to rectify these problems
> rather than going missed. He did decide to go missed but hit the side of
> the mountain as he was executing and hitting buttons.
>
> in retrospect Frank said he should have gone missed with ANY problem but
> these other factors sucked him into thinking he could quickly fix them and
> land. In another friend's words "that's why they call it an "accident"
> rather than an "on purpose"".
>
> Franks said it is a miracle to be alive, they hiked to the crash site
> today and he said it really hit him how lucky they were. A cut finger, a
> bruised face and frostbite is the worst of the physical injuries. He feels
> terrible about putting his friends in harms way and it's gonna take some
> time for him to forgive himself.
>
> Sent from my iPad
> ==
>
>
>
Message 5
| INDEX | Back to Main INDEX |
| PREVIOUS | Skip to PREVIOUS Message |
| NEXT | Skip to NEXT Message |
| LIST | Reply to LIST Regarding this Message |
| SENDER | Reply to SENDER Regarding this Message |
|
Accidents happen. Glad they are ok.
Interested to see if terrain aural warnings were on during IFR and/or
synthetic vision.
----- Original Message -----
From: "Jim" <fehdxlbb@gmail.com>
Sent: Sunday, February 24, 2013 7:04 PM
Subject: RV10-List: Re: RV-10 down
>
>>From a BeechTalk post...
>
> I got the cliff notes of the story from Frank this morning I may not
> have this completely correct but here's the gist of what happened. What
> was most scary about hearing him tell this to me is I could see getting
> sucked in to the same kind of situation. Just like they always tell us,
> accidents are usually caused by what seems (at the time) like a a chain of
> minor events and if you can break the chain then it doesn't happen. If you
> don't break it, you look up just in time to hit the side of a mountain.
>
> Frank told his friends he didn't want to land at night but he knew they
> were calling it close. He got two weather briefings via AOPA & Foreflight
> and also called FAA for an update on the way to the airport, he also
> called the airport for a first hand report he said he was mostly
> thinking about ice. They got off on time but fought a 47 kt headwinds and
> so they got there later than planned (surprise 1) . He picked up an IFR
> clearance for the GPS approach. While shooting the approach he got a
> visual on the airport (when looking down, he said it looked like daylight
> down there) so he canceled (or got cleared for the visual I'm not sure
> I've got this part correct). He dropped down below the clouds and it was
> much darker than above (surprise 2), he clicked the airport lights and
> they wouldn't come on (turns out they have been having troubles with them
> but there were no notams) (surprise 3), at the same time one of his the
> big EFIS displays wouldn't dim (surprise 4). Frank said!
> he thought he spent maybe 20-30 seconds trying to rectify these problems
> rather than going missed. He did decide to go missed but hit the side of
> the mountain as he was executing and hitting buttons.
>
> in retrospect Frank said he should have gone missed with ANY problem but
> these other factors sucked him into thinking he could quickly fix them and
> land. In another friend's words "that's why they call it an "accident"
> rather than an "on purpose"".
>
> Franks said it is a miracle to be alive, they hiked to the crash site
> today and he said it really hit him how lucky they were. A cut finger, a
> bruised face and frostbite is the worst of the physical injuries. He feels
> terrible about putting his friends in harms way and it's gonna take some
> time for him to forgive himself.
>
> Sent from my iPad
> ==
>
>
>
Message 6
| INDEX | Back to Main INDEX |
| PREVIOUS | Skip to PREVIOUS Message |
| NEXT | Skip to NEXT Message |
| LIST | Reply to LIST Regarding this Message |
| SENDER | Reply to SENDER Regarding this Message |
|
Accidents happen. Glad they are ok.
Interested to see if terrain aural warnings were on during IFR and/or
synthetic vision.
----- Original Message -----
From: "Jim" <fehdxlbb@gmail.com>
Sent: Sunday, February 24, 2013 7:04 PM
Subject: RV10-List: Re: RV-10 down
>
>>From a BeechTalk post...
>
> I got the cliff notes of the story from Frank this morning I may not
> have this completely correct but here's the gist of what happened. What
> was most scary about hearing him tell this to me is I could see getting
> sucked in to the same kind of situation. Just like they always tell us,
> accidents are usually caused by what seems (at the time) like a a chain of
> minor events and if you can break the chain then it doesn't happen. If you
> don't break it, you look up just in time to hit the side of a mountain.
>
> Frank told his friends he didn't want to land at night but he knew they
> were calling it close. He got two weather briefings via AOPA & Foreflight
> and also called FAA for an update on the way to the airport, he also
> called the airport for a first hand report he said he was mostly
> thinking about ice. They got off on time but fought a 47 kt headwinds and
> so they got there later than planned (surprise 1) . He picked up an IFR
> clearance for the GPS approach. While shooting the approach he got a
> visual on the airport (when looking down, he said it looked like daylight
> down there) so he canceled (or got cleared for the visual I'm not sure
> I've got this part correct). He dropped down below the clouds and it was
> much darker than above (surprise 2), he clicked the airport lights and
> they wouldn't come on (turns out they have been having troubles with them
> but there were no notams) (surprise 3), at the same time one of his the
> big EFIS displays wouldn't dim (surprise 4). Frank said!
> he thought he spent maybe 20-30 seconds trying to rectify these problems
> rather than going missed. He did decide to go missed but hit the side of
> the mountain as he was executing and hitting buttons.
>
> in retrospect Frank said he should have gone missed with ANY problem but
> these other factors sucked him into thinking he could quickly fix them and
> land. In another friend's words "that's why they call it an "accident"
> rather than an "on purpose"".
>
> Franks said it is a miracle to be alive, they hiked to the crash site
> today and he said it really hit him how lucky they were. A cut finger, a
> bruised face and frostbite is the worst of the physical injuries. He feels
> terrible about putting his friends in harms way and it's gonna take some
> time for him to forgive himself.
>
> Sent from my iPad
> ==
>
>
>
Other Matronics Email List Services
These Email List Services are sponsored solely by Matronics and through the generous Contributions of its members.
-- Please support this service by making your Contribution today! --
|