[tccrockets] Re: Club cards/Lanyards - was Re: Re: 2012 Tripoli Rule Revisions - lanyard idea

  • From: James Dougherty <jafrado@xxxxxxxxx>
  • To: tccrockets@xxxxxxxxxxxxx
  • Date: Thu, 9 Feb 2012 14:44:48 -0800

yes, good point, we all have those already - no more $$$.

But then we would have to have a rule that you wear the card around
your neck (RSO wouldn't be able to call out - hey, are you TRA/NAR certified)?

So, maybe you could do this if it was around your neck :-)


On 2/9/12, Steve Ainsworth <sainsworth@xxxxxxxxxx> wrote:
> Or could we just use our TRA cards for display?
>
> Steve A
>
> -----Original Message-----
> From: tccrockets-bounce@xxxxxxxxxxxxx
> [mailto:tccrockets-bounce@xxxxxxxxxxxxx] On Behalf Of James Dougherty
> Sent: Thursday, February 09, 2012 2:37 PM
> To: tccrockets@xxxxxxxxxxxxx
> Subject: [tccrockets] Club cards/Lanyards - was Re: Re: 2012 Tripoli Rule
> Revisions - lanyard idea
>
> :-)
>
> That's funny. Well, we can get all the club members cards, but it will
> cost probably $5-10 per person to make them. What do people think
> about club cards? Would people be willing to pay $10 for a nice
> plastic card (like the ROC style cards).
>
>
> On 2/9/12, Steve Ainsworth <sainsworth@xxxxxxxxxx> wrote:
>> Oh…. I thought it was the “Non-TRA Guest” that was to be kept on the
>> lanyard
>>  ☺
>>
>> Steve A
>>
>> From: tccrockets-bounce@xxxxxxxxxxxxx
>> [mailto:tccrockets-bounce@xxxxxxxxxxxxx] On Behalf Of James Dougherty
>> Sent: Wednesday, February 08, 2012 6:27 PM
>> To: tccrockets@xxxxxxxxxxxxx
>> Cc: <tccrockets@xxxxxxxxxxxxx>
>> Subject: [tccrockets] Re: 2012 Tripoli Rule Revisions
>>
>> Club cards on a detachable
>> Lanyard :-)
>>
>> Sent from my iPhone
>>
>> On Feb 8, 2012, at 5:18 PM, "AiRobert"
>> <airobert@xxxxxxxxxxxxx<mailto:airobert@xxxxxxxxxxxxx>> wrote:
>> I’ll put it next to my yellow star….
>> I don’t like it, but it’s probably good-ish.
>> RZ
>>
>>
>> ________________________________
>> From:
>> tccrockets-bounce@xxxxxxxxxxxxx<mailto:tccrockets-bounce@xxxxxxxxxxxxx>
>> [mailto:tccrockets-bounce@xxxxxxxxxxxxx] On Behalf Of JACK GARIBALDI
>> Sent: Wednesday, February 08, 2012 5:06 PM
>> To: tccrockets@xxxxxxxxxxxxx<mailto:tccrockets@xxxxxxxxxxxxx>
>> Cc: TCC Chat
>> Subject: [tccrockets] Re: 2012 Tripoli Rule Revisions
>>
>> I like the lanyard Idea
>> Jack
>>
>> Sent from my Mil Spec IPhone 4S
>>
>> On Feb 8, 2012, at 4:31 PM,
>> gary-walker@xxxxxxxxxxx<mailto:gary-walker@xxxxxxxxxxx> wrote:
>>
>> My 2 cents as well...
>>
>>
>>
>> It appears that there are 2 main points of interest in the rules
>> revisions...so far.
>>
>>
>>
>> 1. Motor ignition methods - As Jack and others have said, pretty cut and
>> dry
>> as I understand it.  That said, yes, it appears that some existing
>> electronics that require break/pull wires may need to be phased out.
>>
>>
>>
>> 2. Non-HPR (i.e. uninsured persons) on the range/launch area.  -  Perhaps
>> we
>> could have all HPR fliers openly display their membership cards (TRA or
>> NAR)
>> at all times on a lanyard or clipped to their short/jacket. Also, we
>> might
>> designate a Pad Manager or additional RSO's, as we've had at times in the
>> past, to oversee the actual pad area. This would help clarify just who is
>> in
>> the area while charges and electronics are being armed.
>>
>>
>>
>>  I think we have been pretty fortunate to have not had any serious
>> incidents
>> at TCC launches, at least in my memory.  Most times, we have plenty of
>> help
>> at LCO and RSO and I thank those who do it on a regular and occasional
>> basis, but as the discussions over the new rules imply, we can always use
>> more "eyes on" what's happening around us.
>>
>>
>>
>> Of course these issues will continue to be discussed at future launches
>> and
>> here on the chat so that all of us are on the same page and understand
>> what
>> is "OK" and what is not.
>>
>>
>>
>> See you at the next launch!
>>
>> Gary Walker
>>
>> Prefect - TCC
>>
>> No virus found in this incoming message.
>> Checked by AVG - www.avg.com<http://www.avg.com>
>> Version: 8.5.455 / Virus Database: 271.1.1/4195 - Release Date: 02/07/12
>> 20:17:00
>>
>
>

Other related posts: