This is a multi-part message in MIME format.
--------------BEC7EE09FE87A71858788230
--------------BEC7EE09FE87A71858788230
Content-Disposition: inline
X-Mozilla-Status2: 00000000
Message-ID: <37DFF3F4.1FA4F1D7@p-d-g.com>
Date: Wed, 15 Sep 1999 12:31:01 -0700
From: Craig Wright <craig@p-d-g.com>
Organization: Product Design Group
X-Mailer: Mozilla 4.61 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Nick England <nick@cs.unc.edu>
Subject: Re: Reflections on a racing incident
References: <199909151817.OAA15419@altair.cs.unc.edu>
This thread reminds me of the speech airline flight attendants give before
take off. Every airline says exactly the same thing as dictated by the FAA.
Those of us who fly often would probably have no disagreement on safety
procedures in case of an accident. Repetition and constancy leads to strong
habits. Sanctioning bodies should emulate the airlines and reiterate the
basic flag rules at EVERY meeting.
My 2 cents,
Craig Wright
Nick England wrote:
> Well it is now perfectly clear that there are two conflicting "standard
> red flag procedures". One says "stop now (safely)", the other says "quit
> racing, slow down, and return to the pits".
>
> Which is why I really hate those short drivers meetings that take the
> attitude that "everyone knows what the flags mean so we don't want to
> insult any big shots by taking 30 seconds to remind you what procedure
> this particular association has decided to use at this particular
> track on this particular day."
>
> Organizing bodies should be more responsible and professional than
> that!
>
> Here's a suggestion - and I'll start using it too. Always ASK
> at the Driver's meeting what the red flag procedure of the day is.
> I'd much rather be embarrased at being a novice than:
> a) run over some poor corner worker who expected me to stop.
> b) get run into by some poor racer who didn't expect me to stop.
>
> Best Regards & Have Fun,
> Nick England
> http://www.cs.unc.edu/~nick/racing.html
--------------BEC7EE09FE87A71858788230--
|