An accident that could have been averted.
Xavier Mouraux
xavier.mouraux at sympatico.ca
Tue Jun 29 17:39:35 AKDT 2004
I was at the contest in Pocono and there was another pilot on my frequency.
I knew because it was announced at the pilots meeting. We were both very
aware all the time what the other one was doing.
I must say that I was very surprised to ear the story after the crash. The
second pilot should have know that the first one was on the line.
We are lucky the plane went in the tree and not in the pits or on the road.
It could have been a lot worst.
The only place I have seen a scanner used for every TX going to the impound
was in Syracuse, 3 years ago at a pattern primer run by Bob Noll. I was
surprised not to see it at the Nats or any other place. I would feel a lot
better if it was done everywhere.
I have seen a visitor pilot at my club with a radio identified with channel
16 (sticker on the futaba module) and he was saying the radio was on 26. I
forced him to block both channels and ask him to get it checked and the
steaker changed before he visits us again.
Xavier
----- Original Message -----
From: "Todd Schmidt" <tschmidt at classicnet.net>
To: <discussion at nsrca.org>
Sent: Tuesday, June 29, 2004 6:37 PM
Subject: Re: An accident that could have been averted.
> Our club has a handheld frequency scanner. Before a pilot flys at an
event
> we check his frequency to make sure its not being used, then have him turn
> on and the scanner tells us if he's transmitting on the right frequency.
> Caught a few transmitting on a different frequency before in the past.
Sure
> makes the pilots feel safe when we use it!
>
> Todd
> ----- Original Message -----
> From: "Joe Lachowski" <jlachow at hotmail.com>
> To: <discussion at nsrca.org>
> Sent: Tuesday, June 29, 2004 12:52 PM
> Subject: RE: An accident that could have been averted.
>
>
> > Mike,
> >
> > That very thing was done at this contest. I ran out the pilots list with
> > frequencies from the PASS program and just did that, ran down the list
of
> > pilots who shared frequencies and made sure each and every one
identified
> > themselves to each other.
> >
> > Another thing that creates confusion is pilots changing to another
> frequency
> > from that which they preregistered. Make sure you tell the guy running
the
> > computer that you did so if you preregistered in advance. I had 26
pilots
> > worth of info in the computer ahead of time and discovered at the pilots
> > meeting that some changes were made. Oh well, no matter what you did,
> things
> > are never always fool proof.
> >
> >
> > >From: "Dean Pappas" <d.pappas at kodeos.com>
> > >Reply-To: discussion at nsrca.org
> > >To: <discussion at nsrca.org>
> > >Subject: RE: An accident that could have been averted.
> > >Date: Tue, 29 Jun 2004 12:50:07 -0400
> > >
> > >Great idea Mike,
> > >That actually was done at this contest.
> > >Dean
> > >
> > >-----Original Message-----
> > >From: discussion-request at nsrca.org
> [mailto:discussion-request at nsrca.org]On
> > >Behalf Of mike mueller
> > >Sent: Tuesday, June 29, 2004 12:42 PM
> > >To: discussion at nsrca.org
> > >Subject: Re: An accident that could have been averted.
> > >
> > >
> > > Joe that brings up a point I would like to see made into an SOP for
all
> > >contests. During the pilots breifing before the contest it would help
if
> > >the CD would announce all the frequency conflicts and have those people
> > >talk to each other. Many times you don't even know if there's someone
> else
> > >using your frequency. It's just common sense. Mike
> > >
> > >Joe Lachowski <jlachow at hotmail.com> wrote:
> > >
> > >This past weekend at a contest, a pilot inadvertently took the wrong
pin
> > >from the pin board and shot down the pilot on the other flightline. A
few
> > >things here to ponder about when one attends a contest when this
> situation
> > >occurs.
> > >
> > >One - Double cjheck to see that you do have the correct pin.
> > >
> > >Two - You can't trust the pilots to take the right pin. Someone in the
> > >impound must directly hand the correct frequency pin to the pilot. At
> least
> > >that was resolved immediately after the incident.
> > >
> > >Three - This one requires everyone being alert of what is going on
around
> > >them and quickly reacting. In this situation the pilot with the wrong
pin
> > >could have turned his radio off when people started yelling to turn off
> ALL
> > >radios in use. This pilots plane was in the hands of the caller at that
> > >time. The pilot who lost his plane made a valiant effort to save his
> > >plane(on an FM Rx). The amount of time from interference to crashing in
> the
> > >trees was more than enough time to shut ALL radios off. There was
> > >sufficient
> > >time for that pilot to save his plane had the other pilot reacted
> quickly.
> > >
> > >Enough said.
> > >
> > >_________________________________________________________________
> > >Make the most of your family vacation with tips from the MSN Family
> Travel
> > >Guide! http://dollar.msn.com
> > >
> > >=====================================
> > ># To be removed from this list, go to
> http://www.nsrca.org/discussionA.htm
> > >and follow the instructions.
> > >
> > >
> > >
> > >
> > >
> > > _____
> > >
> > >Do you Yahoo!?
> > >Take
> >
>
><http://us.rd.yahoo.com/mail_us/taglines/mobile/*http://mobile.yahoo.com/ma
> ildemo>
> > >Yahoo! Mail with you! Get it on your mobile phone.
> > >
> >
> > _________________________________________________________________
> > Make the most of your family vacation with tips from the MSN Family
Travel
> > Guide! http://dollar.msn.com
> >
> > =====================================
> > # To be removed from this list, go to
http://www.nsrca.org/discussionA.htm
> > and follow the instructions.
> >
> >
>
>
> =====================================
> # To be removed from this list, go to http://www.nsrca.org/discussionA.htm
> and follow the instructions.
>
=====================================
# To be removed from this list, go to http://www.nsrca.org/discussionA.htm
and follow the instructions.
More information about the NSRCA-discussion
mailing list