|
From the Author
of "Accident
Scene," internationally known Accident
Reconstructionist Joseph E. Badger is providing you on these
pages his expert insights into the handling all aspects of "Accident
Reconstruction Basics." Joeseph Badger is available for
accident reconstruction consulting. That is his
business. Let him hear from you. Need an expert?
E-mail Badger at jebadger1@comcast.net .
INDEX
Joseph E. Badger is an internationally known Accident
Reconstruction Consultant and a frequent contributor to LAW and
ORDER and to NRLO. You may reach Mr. Badger by email: jebadger1@comcast.net
Be sure to check
back for more articles coming to NRLO's
eTraining Basic Education Pages : "Trailer Underride: Conspicuity,
Human Factors and Rear Bumpers" "Underride Accidents - they just
keep happening" "More Human Factors in Accident
Investigation/Reconstruction" "TIPS (Traffic Institute for Police
Services)"
Errors in Accident
Reconstruction As Seen
by Joseph E. Badger
It has recently
come to my attention that some Police academies - for whatever
reason(s) - limit their instructions regarding "accident
investigation" to a two-hour segment on how to fill out he crash
report form. Another statistic I heard was that - at least for
the aforementioned recruit school - that out of approximately 100
basic students only 14-20 take a 5-day, crash investigation
course.
Trust me on this, a 5-day
course - nay, not even a 5-week course - does not make a
qualified "accident reconstructionist." Neither does a 5-year
physics or engineering course. It takes not only training in
the mathematics and engineering priciniples involved, but also it
takes years of practical, hands-on, in-the-field
experience.
Some agenices mandate its
Officers to NOT take photographs unless there is a fatality.
Yet, we occasionally see reports of fatalities and serious bodily
injury where only the standard crash report is completed. No
photographs, no measurements.
We find that some Officers,
including those who have had no more than a couple of weeks of
reconstruction instruction, are holding themselves out as "accident
reconstruction experts," yet they make grievous blunders.
Sometimes without even realizing it.
Back to
INDEX
YAWS For instance,
just because a tire mark is curved doesn't necessarily mean it is a
yaw mark. (And while I'm on the subject, I'm forever seeing
Police reports and diagrams that mention "Yawl" marks. A Yawl
is a two-masted fore-and-aft-rigged, sailing vessel similar to a
ketch but having a smaller jigger mas stepped abaft the
rudder. Or, it's a ship's small boat, crewed by rowers.
"American Heritage Dictionary.")
A yaw, on the other hand, is a
whole other subject, described in Al Baxter's
"Accident Investigation and Reconstruciton
Terminology" as "The rotational or oscillatory
movement of an object about its vertical axis; a movement about the
z-axis of the vehicle axis system." Yaws often occur when
a driver makes a hurried steering maneuver:
(a) to avoid an object in
the road or
(b) or remain on the
pavement while entering a curve too fast, or
(c) while overcorrecting a
previous situation. "A yaw mark is that physical mark on the
roadway caused by the rotating tires of a vehicle slipping in a
direction parallel to the axle of the wheel during a maximum rate
change of direction (turn)."
Speed determinations
may indeed be made by correctly measuring genuine yaw marks;
however, if those are merely spin marks, created by one vehicle that
is impacted by another vehicle, then it is inappropriate to use
equations that assume the mark to be a real yaw. And for
heaven's sake, you don't have to measure the length of a yaw mark -
unless you simply want to know how long it is. The length has
no bearing in critical speed formulae.
For the critical speed
equation to work, the vehicle in question must be both rolling in
one direction and sliding in another; however one "expert" used a
supposed yaw mark and came up with over 90 mph, but the front tires
were both flat, and the front wheels were crushed, not allowing them
to roll.
Back to
INDEX
FLIPS, VAULTS,
AND FALLS In one respect, the yaw is
a like a vault or flip - circumstances that may befall vehicles in
certain accident scenarios. That is, a speed calculation
determined from that action is final. Whatever the vehicle
does subsequently doesn't matter. It can skid, crash into a
tree, or roll over. Once you've computed the yaw (or fail or
valut or flip) speed you must not combine the speed
following any of those events with the speed
calculated in the event. You may - and should
- use data from circumstances following the yaw, fall, or vault to
confirm the originally calculated speed. If a collision or
skid occurs prior to a yaw (etc.), then fine, speeds may be
combined.
In one case, the
reconist actually added two airborne
speeds together. Go ahead and calculate both (hopefully the
second one will be less than the first one); but don't add,
subtract, or combine them. Use the answer from the equation in
which you have the best data.
Back to
INDEX
MISINTERPRETING
EVIDENCE Be careful when taking
scene photos that you don't inadvertently create evidence that isn't
there. Watch those shadows! Likewise, be careful when
examining photographs taken at accident scenes. Shadows
created by overhead utility lines have an uncanny way of appearing
as yaws or curved tire marks on the pavement.
Back to
INDEX
COMBINING
SPEEDS Speaking of combining speeds,
there's a particular way of doing that. "Combining" doesn't
mean "adding." If a car, say, skids 50 feet on concrete, 25
feet on blacktop, then 40 feet on grass, and smashes into a
75-year-old oak tree, there's a reasonably easy way to determine how
fast the car was going when the driver first applied the
brakes. The not-so-quite-so-simple part involves first a
"crush analysis," then backing things up wherein you compute the
speed for each surface. But you don't add all those speeds
together. It's like Pythagoras Plus. Square all the speeds, add those, then take the square
root of the answer. Thay way, 36 mph and 23 mps and 24 mps and
20 mph doesn't equal 103 mph, it's 52 mph and some
change.
In a
motorcytcle case, a Ph.D. testified that a motorcyclist's speed,
based upon post-impact throw distance, was 30 to 35 mph. He
then said that the speed of the motorcycle, based upon post-impact
sliding distance, was 30 to 35. Sounds great,
right? No! He combined them and said that the speed of
the motorcycle was approximately 46 mph.
Back to
INDEX
INCORRECT
SCIENCE Acceleration rates are
interesting. Car magazines print data regarding how fast
certain cars can accelerate from 0 to 60, or the fastest speed
attainable in a quarter-mile. Be cautious using these data in
intersection collisions. There's the case where an opposing
expert used an acceleration rate for 0 to 10 mph to show how quickly
it could accelerate from 55 to 65 mph.
Back to
INDEX
DRAG
FACTORS Much of the time, assigning
a precise value for drag factor isn't necessary. In the
overall scheme of things, there isn't a lot of difference between
the speeds generated from a .65 drag factor as with a .75 drag
factor. For one reason, you end up taking a square root of the
value. As an example, if a car skids to a stop in 100 feet on
a .65 surface, the slide-to-stop speed is around 44 mph. On a
.75 surface, everything else being equal, the speed equates to about
47 mph. What's three miles an hour among
friends?
Furthermore, if you
perform a skid test (whether with a drag sled, bumper gun, or
electronic accelerometer) on the surface where the accident skidding
occurred and in the direction in the skidding happened, you should
not add or subtract the grade. The grade was "built in" when
you completed the test.
But drag factors do
make a difference when tractor-semitrailers are involved, and
especially when bob-tail units skid. ("Bob-tails," by the way,
are truck-tractors designed to pull semitrailers but which are
traveling without one.) On a roadway surface that may be .80
for a car, may be only .30 for a bob-tail tractor. And for
that same 100-foot skid, the respective speeds would be 48 mph
versus 24 mph.
Drag factors are
different for heavy trucks for a number of reasons, including weight
shift (no, not load shift; that's something else), tire pressure,
and the idiosyncrasies inherent with air brake systems.
This was an
actual case: An Officer used a 0.7 for friction,
because "all streets in the city have a 0.7." He then adjusted
for the 0.03 grade. Next, he checked the striking vehicle and
discovered that the rear brakes did not function. He
determined the speed of the striking vehicle by using momentum, then
combined the impact speed with the speed loss from pre-collison skid
marks. He used the full friction (0.73) for both pre- and
post- collision movement of both vehicles, even though he had
determined that one vehicle did not have working brakes. He
used the 0.73 for the post-impact movement of the other vehicle,
even though it was going downhill on grass, with only one wheel
locked from damage.
Similarly, there are
Officers who use the full drag factor - meaning 100% braking - for
vehicles that are free-rolling from impact to final rest.
Then there are some
who mishandle drag sleds (usually by pulling them way too slowly)
and come up with drag factors of 1.20 on level blacktop
surfaces. This may approach possiblity on some brand new
asphalt that has bits of embedded glass particles and a sled with
really soft tire material, but beware anytime you come up with a
factor of .95 or more.
Back to
INDEX
COMPUTER
PROGRAMS Beware also of accident
reconstructionists bearing software. Paraphrasing
Charles Grosvenor, former Representative from Ohio,
"Computers won't lie, but liars will
compute." I'm acquainted with two
engineers who on separate occasions used a particular program (with
which I've had years of experience and special training), one to
calculate that a vehicle was astraddle the centerline during a
collision; the other who figured how two women pushed a car up a
grade at over 10 miles an hour.
And I've seen Police
Officers who have used sophisticated mapping and measuring software
to calculate the departure angles of cars in intersection crashes
based on the center of mass of the cars at final rest, rather than
the angle at separation.
Back to
INDEX
ROUNDING
DOWN They always tell you to "give
the benefit of doubt to the violator;" but wait, you don't need to
give them the farm. Truncating the energy equation is one way
to do that. Sure, round down; but wait until you're finished,
then round down the final answer.
Back to
INDEX
MIXING
UNITS This sort of error crops up in
measuring critical speed scuffs or curved roadways. If you
measure a chord in feet, measure the middle ordinate in feet also,
not inches. Likewise, if you're dealing in feet per second,
don't use miles an hour as formula input. Imperial and metric
don't mix very well either.
Don't mix prices with
pounds. This actually happened when an engineer checked a NADA
book for the weight of a used vehicle and wrote down the retail
price of a pickup truck instead of its weight. Then he entered
that number in the momentum formula.
Back to
INDEX
BOTTOM LINE Before you hold yourself out as an "accident
reconstructionist," be sure you can back up your methodology.
Such support is not simply saying you read it someplace or some
teacher told you.
_____________________________________________________
Back to
INDEX
Joseph E.
Badger is an internationally known Accident Reconstruction
Consultant and a frequent contributor to LAW and ORDER MAGAZINE. You
may reach Mr. Badger by email: jebadger1@comcast.net.
Malfeasance of
Office Written by Joseph E.
Badger
What is
malfeasance? It's misconduct or wrongdoing, especially by a
public official (American Heritage Dictionary). A
similar word is Maleficence (Law) "The doing of an act which a
person ought not to do; evil conduct; and illegal deed. (Written
also malefeasance)" (Webster's Revised Unabridged
Dictionary).
Some Police
Departments - and some Police Officers - for some reason don't think
accident investigation is such a big deal. It evidently
doesn't matter that more people die in traffic accidents than in
suicides, homicides, and related crimes. And it apparently
doesn't matter that more property damage occurs as a result of
traffic accidents than in all the burlgaries and
robberies.
Too many Police Chiefs
and Sheriff's, and Officers working the road, feel that traffic
accidents are something best left to insurance companies.
Consequently, so many
Law Enforcement personnel do shoddy work when called to investigate
accidents - or crashes, collisions, whatever name you give
them. And this can come back to haunt you.
The good news is, most
states have laws protecting Police Officers and Police
Departments. For example, Indiana Code 34-13-3-3,
Immunity of governmental entity or employee,
states:
"A governmental
entity or an employee acting within the scope of the employee's
employment is not liable if a loss results from the following"
and it goes on to innumerate several points
including:
"(8) The
adoption and enforcement of or failure to adopt or enforce a law
(including rules and regulations), unless the act of enforcement
constitutes false arrest or false imprisonment.
"(9) An
act or omission performed in good faith and without malice under
the apparent authority of a statute which is invalid if the
employee would not have been liable had the statute been
valid.
"(10)
The act or omission of anyone other than the governmental entity
or the governmental entity's employee.
and
"(22) An act or omission performed in good faith under the
apparent authority of a court order discribed in IC 35-46-1-15.1
that is invalid, including an arrest or imprisonment related to
the enforcement of the court order, if the governmental entity
or employee would not have been liable had the court order been
valid."
That being said,
lawsuits can still be brought against Police Departments and
individual Officers for failing to do a proper
"investigation." Some Officers simply fill out a report and be
done with it. Some interview some witnesses, but not all... or
they use the information from select witnesses and ignore the
statements of others.
More good news is that
lawsuits against government entities frequently end in summary
judgements for the defense based on immunity grounds.
The bad news is, such
lawsuits still cost a bundle to defend, plus they bring untold
embarrassment to the Officer who botched the job and to the Police
agency who dropped the ball as far as "training the Officer" is
concerned.
If not malfeasance,
how about negligence? To succeed in negligence action, the
plaintiff must establish: a duty on part of defendant to
conform conduct to standard of care arising from relationship with
plaintiff; failure of defendant to conform conduct to that standard;
and injury proximately caused by breach of duty. (Westlaw 674 N.E.
2d 580, page 1.)
Does your agency have
written policies and procedures outlining what the standards are in
various situations? If not, why not? And if so, are the
Officers adhering to those standards when conducting accident
investigations?
One state case - which
will remain nameless - came about because the Highway Patrol
"....had no policy regarding how to secure an accident scene
(where to put flares, when to block the road, etc.), and the
State Patrol's lack of a policy regarding crash scene management was
negligent and put the victim in harms way."
According to one
source, some jurisdictions have laws or rules & regulations
stating that an Officer "can be removed from office for dereliction
of duty." Such things as "failure to investigate" may fall in
this category.
There is some case law
that shields Officers and Municipal agencies in certain
circumstances. For instance, Crouch v. Hall, Breen, et al.
individually and in capacity as Police Officer for the City of
Indianapolis, 534 N.E.2d 1083. While not about failure to
investigate a traffic accident, it did dealt with failure to
investigate a rape. The Indiana Court of Appeals held that
"Officers were immune from suit under discretionary function
provisions of Indiana Torts Claims Act and that Police Officers owed
no special duty to rape victim and therefore could not be held
liable for damages to rape victim's mother who claimed that rape and
death of her daughter resulted from Officers' failure to properly
investigate earlier rape."
Another case is
Boyle v. Anderson Fire Fighters Ass'n Local 1262 (1986)
Ind. App., 497 N.E. 2d 1073. This case dealt with the issue of
whether plaintiffs have a legal claim for damages against individual
striking firemen based upon their conscious refusal to fight a fire
on the plaintiffs' property.
In Indiana, the Tort
Claims Act provides numerous immunity provisions which preclude
actions against the state or its agents under certain
circumstances.
Law Clerk
Jeremy Peelle writes: "There is
also a general 'public duty' immunity which has been judicially
recognized. The courts have held that under Indiana law, there
will be no governmental liability to individuals for negligence when
the government entity owed a duty to the public at large or as a
whole. Stratmeyer v. U.S., 67 F.3d 1340 (7th Cir.
1995). The Comparative Fault Act does not apply to claims
brought under the Tort Claims Act and contributory negligence will
act as a complete bar to recovery actions. Town of
Highland v. Zerkel, 659 N.E.2d 1113 (Ind. Ct. App.
1995)."
However, individual Officers need to realize there is
a considerable price to pay even if you win or if the suit gets
dismissed. In some cases, you are liable for your own defense
costs. Your name ends up in print, often on the front
page. Your ability to function as a Police Officer can be
hampered by such publicity, whether it's warranted or not. If
the public thinks you've been direlict in your dutues in one case
they may conclude, rightly or wrongly, that you may have been
derelict in other matters.
Police agencies should
be held accountable for the negligence and/or stupidity of its
members; however, it seems gross incompetenece isn't enough.
Individual Officers should likewise be answerable to not only their
misdeeds but also to their non-deeds.
Writing for the
"Indianapolis Star" (May 23, 2003), Tom
Spalding tells readers about an Officer whose accident
reports left a lot to be desired. Though there was no mention
of the Police Department being sued, Spalding quotes the agency's
legal advisor as saying, "He had a problem doing reports
correctly, or doing them at all ... even at times when a supervisor
ordered him to." (The Officer) declined to talk about the
reports but pointed to a lack of training as the
root of the problem, according to Spalding.
This sort of thing can
come back to haunt a Police Department because, as Spalding points
out, "Police reports are critical, officials
said, because they can affect a citizen's insurance after a car
crash, or the completion of a burglary
investigation."
You may
have even been around other Officers (city, county, state) who pride
themselves on "working" traffic crashes by never even exiting their
vehicle (names and agencies withheld to protect the
incompetent). Ineptitude, lack of skill or ability, coverups,
lack of or inadequate training can all lead to lawsuits or at least
drown a Department or person in hot water.
Remember, you have a reputation to uphold. Do your
job!
____________________________________________________
Joseph E.
Badger, a nationally known Accident Reconstruction Consultant, is a
frequent contributor to NRLO. He may be reached at
jebadger1@comcast.net .
Back to
INDEX
Things Police Forget Two Weeks
Out of Recruit School by Joseph E.
Badger
For some
unknown reason, Officers forget things. I had a State Trooper
ask me one time if I would help take some measurements for a scale
diagram. The request was later changed to: "Would you make the measurements? I forgot
how." How do you
forget how to measure? The reply was a lack of an
opportunity to practice.
When I asked how many
accidents the Trooper had investigated (the answer was several minor
ones), I advised to practice with the minor fender-benders to better
prepare for the big ones that come along. It is the same thing
at crime scenes: No, you do not need a scale drawing each
time, but practice for when you do.
Practice taking latent
prints at home. Have friends over and dust their drinking
glasses after they leave. What about nighttime
photography? Unless you attended some specialized course, I
suspect many of the pictures you take at night are too dark.
Find out why. Film is cheap; and if your agency has gone
digital, shoot up a whole disk and then erase the memory
card and start over. Practice, practice, practice.
Larry Randolph, who
went through the State Police Academy with me over three decades
ago, remembers that when rookies get excited during their traffic
stops, they often forget the basics such as how to park the cruiser,
spot light placement, and their approach to the vehicle.
Part of the problem is
that many Officers do not want to bother learning the basics in the
first place. Some Officers prefer to bypass what they consider
low priority learning and jump right into the meat of drug
investigations or high-profile murder cases. Nevertheless, if
they nodded off during the session where you learn how to interview
witnesses, their investigationa suffer.
A former Officer and
long-time acquainance of mine, Aric Steve Frazier,
wrote a book a couple of years ago titled Introduction to Traffic Investigation and
Enforcement. Where many textbooks merely
tell Officers how to do things, Frazier's 16 chapters include a
dozen lessons for Officers to take self-tests to see how much they
have forgotten. You can flip through the 239 pages and find
all kinds of things you have probably forgotten how to
do.
How many of you
remember how to compute the cosine error if you are taken
to task on the witness stand in a radar speeding arrest? What
do the letters VASCAR stand for? What does your state law say
about when you can tow an abandoned vehicle? How many ways are
there to manipulate the results of an infrared
spectrophotometer? What is an infrared
spectrophotometer?
With teaching
experience at three different academies, Sergeant Barry
Walker noted, "The guys spend their
time dreaming of being the K-9, SWAT, undercover drug agent,
detective, or supervisor. They do not pay attention to the
stuff that they will have to do to get those positions.
The most common thing they forget is field sketch and
measuring techniques."
They also forget to
document the various steps they take in an investigation.
Walker said, "Officers will do the work,
track down leads that end in dead-ends, go onto other leads, talk to
neighbors, follow-up on suspects, etc., literally spending hours on
an investigation; and then they do not write it down."
That means the Criminal Investigation Section has to duplicate many
steps all over again.
George
Ogilvie, formerly with the Oregon State Police, is
concerned that many seemingly experienced Officers have forgotten
how to fill out a simple report form. "They put information in the wrong box, leave
critical boxes empty, etc. The second thing is also dealing
with report writing They should use spell check and grammar
check. Sometimes the reports are so confusing that I have no
idea what the Officer is writing about."
Granted,
a few Officers still prepare reports the old-fashioned way
(hand-written or typed on a typewriter) where spell and
grammar-checking is not as easy as a mouse click or two; however,
somebody should proofread those reports before the clerk files them
away.
Detective Gary
O'Brien (Ontario Provincial Police, Anti-Rackets Section,
Investigation Bureau) complained that Officers have evidently
forgotten everything they learned in Interviewing 101.
"Without attending advanced
interview/interrogation classes, most Officers I deal with do not
take a very good statement. The statements, in a word, are
brutal! With all my recruits, I stress the need for proper,
detailed statements. However, before I could achieve that
goal, I had to get the rookies to listen to what people were trying
to tell them. Listening skills go hand-in-hand with the
interview, but are a sadly overlooked
component."
Baltimore County Police CRASH Team Officer Rick
Esenwine came up with a half-dozen items that Officers
commonly forget:
-
How to ask all the (right)
questions needed to complete a simple report
-
How to write a report so
it is intelligible and flows with the story of what
happened
-
How to practice Officer
safety during traffic stops and contact with suspicious
persons
-
How to drive
-
How to take constructive
criticism (something not taught in the academy) from Field
Training Officers and supervisors
-
How to be assertive
without being arrogant and aggressive
Retired Alabama
Trooper William Neal expressed dismay not just with
the current state of training, but with those who do the
training. Specifically, Neal said he has serious problems with
those occasions. "When someone who has spent
only two or three years on the road is now a Sergeant teaching new
recruits Patrol procedures."
Canadian
R.W. (Bob) Rivers, prolific author and retired RCMP
Officer, noted that as far as accident reconstruction training goes,
we seem to be possessed with the issue of speed. Granted, in
nearly every traffic collision someone always asks, "How fast was he
going?" But too often training falls short in other areas of
concern. Rivers pointed to the medical profession, behavioral
science specialists, dentists, metallurgists and others who are
experts that accident investigators and reconstructionists routinely
fail to bring into their cases.
How many Police Departments
utilize the services of psychologists to really get the whole
picture of why a driver or suspect did what he did? In
addition, Rivers opined, "Just maybe there
is more to investigations and reconstructions than speed
analyses!" Perhaps it is time
that those in charge of training review their agency's training
policies and procedures.
__________________________________________________________________
Joseph E.
Badger, a nationally known "Accident Reconstruction Consultant," is
a frequent contributor to LAW and ORDER Magazine and to NRLO's
eTraining. He may be reached at jebadger1@comcast.net.
Back to
INDEX
_________________________________________________________________
Cell Phone Usage While
Driving ".......Cell phones
are not the real problem. The real underlying problem has to
do with phones period and how we are conditioned to use
them."
Submitted by Joseph E.
Badger
Written by Officer Greg Edgcombe Senior Accident
Reconstructionist Grand Rapids Police Department,
MI
Officer Greg Edgcombe,
45, has had 20+ years in Law Enforcement and is currently the Senior
Accident Reconstructionist with the Grand Rapids (Michigan) Police
Department. He is also a motor Officer and a Field Training
Officer. Greg has investigated over 1,000 accidents and
received formal accident reconstruction training through Michigan
State University. I met Greg via e-mail after reading his
article "Cell Phone Usage While Driving" in the July 2005 issue of
Reference Points, the Jouranal of the Michigan Association of
Traffic Accident Investigators (MATAI). As you know, many
motorists who use cell phones while driving become inconsiderate or
rude or turn into morons or some combination thereof.
Officer Edgcombe has figured out why. He gave me permission to
submit his article for this web site. (Joe
Badger)
I have investigated serious injury accidents
and traffic fatalities for approximately eight years now. From
time to time during an investigation, the issue of cell phone usage
arises. Because the cell phone is commonplace in vehicles,
it's become the topic of accident reconstruction training,
legislation in many states and municipalities, and the conversation
of many frustrated drivers who get slighted by the unconscious acts
of some cell phone-using drivers.
There is a reason why I describe these drivers
as "cell phone-using drivers" and not "drivers using cell
phones." A great deal of them who violate basic rules of the
road in their unconscious fashion are not primarily driving and
using a cell phone. You guessed it; they are primarily using a
cell phone and secondarily driving a 4,000-pound piece of metal that
has the potential to kill at virtually any speed given the right set
of conditions.
At times people want to tell me how others
drive because they forget that a Police Officer is not married to
his marked patrol car. We have the opportunity from time to
time to commute in our personal cars alone and with our
families. We do see how people drive when they don't know a
Police Officer is in their presence. I want to share a few
brief, but all too familiar, examples with you.
I went out with my wife and children on
Mother's Day. We finished a fantastic meal and began our trip
home. We stopped at a major intersection beside the newest
mega mall in our city. I could see a young lady around 20
years old crossing the intersection. The light turned red for
all four lanes of northbound traffic. There was a car stopped
at the front of all lanes in the intersection with the exception of
the lane on my right. This young lady continued walking,
looking straight down at the pavement in front of her feet.
Meanwhile, in the lane to the right of me, I saw a vehicle fast
approaching from behind. I said out loud, "She's gonna get
hit." The young lady walked past the front of our car and
directly into the path of the approaching car. The vehicle
swerved and locked up the brakes sliding past the pedestrian missing
her by literal inches. My family looked to the right as the
young lady in the car backed up next to us laughing nervously.
She said, "sorry" to the pedestrian she nearly hit. All of
this with her cell phone clutched in her hand up to her ear - never
breaking stride in her conversation.
I am confident that the driver of the car
neither realized that four lanes of traffic in front of her had
stopped nor that she was about to run a red light and seriously
injure a pedestrian as a bonus until it became too late to
avoid.
On a freeway in our city, a man was driving
while talking on his cell phone to a good friend. His friend
told us that the man yelled "Oh s###!" and the phone line
died. The next he heard of his friend was the day the funeral
was to be scheduled. With the investigation complete, we
discovered that his friend had been traveling at 60 miles per hour
when he rear-ended a tractor-semitrailer stopped in traffic on
the roadway directly in front of him.
I was pulling out of an area hospital
emergency room driveway after an accident follow-up.
Approaching from the north was a large box-type ambulance running
full code towards us. My partner and I heard it before we saw
it even with our windows up. The ambulance began its turn into
the emergency room drive where we held tight to give it all of the
room it needed. The ambulance suddenly slammed on the brakes
and hit the exhaust horn as it came to a complete stop after
crossing three feet over the center line. We looked to our
left, and here came a Jeep driving northbound. The driver had
a cell phone up to her ear, and we could see her talking. She
drove past as if she was on an easy-going Sunday drive. She
never looked to the left or right. The ambulance drivers both
threw their hands up in the air and had a few words to say like
"What was that?" We pulled behind the Jeep and turned our
lights on. One block later, she continued away from us.
Finally 1/2 block later with our siren and lights on, she stopped
(under a light at an intersection that fortunately turned green as
she arrived). She was absolutely oblivious to why we were
stopping her. She was so adamant that we were delusional that
she fought the ticket for "failure to yield to an emergency
vehicle." She told the judge there was no ambulance and no
lights or sirens.
Take note that people are driving around in
this "unconscious" state of mind. I completely believed
her when she told the court that as far as she was concerned, she
never saw or heard an ambulance. She was shocked when found
responsible and learned absolutely nothing from her
experience. Hopefully, it won't be a 70,000-pound fire truck
next time. An interesting note is that this was a large
ambulance within four feet of her car with lights, siren, and
exhaust horn all going as she passed by. You can see how
powerful the cell phone spell can be.
A 21-year-old family nanny was driving a
Humvee, delivering her seven-year-old client to an
appointment. She was on her cell phone leaving a message on an
answering machine with another employer. She was driving 45
miles per hour as she came to a rather large intersection. She
later told us that she never noticed that all of the other lanes of
traffic traveling with her had come to a complete stop. She
drove past all the other stopped cars never noticing that her
southbound light was solid red. She drove her Humvee directly
into the passenger door of a Suburban killing that family's
12-year-old son. She later told us she never saw the red
light. In fact, she never saw the vehicle she struck until the
collision was occurring.
In all four instances, thse otherwise good
drivers had one thing in common - the use of their cell
phones. You might think it is something common to cell phones,
but it is more simplistic than that.
I started running the entire gamut of what
could be the underlying problem of cell phone usage while
driving. I asked the question as to why a person could talk to
another person present in their car and not have the same attention
deficit they encounter while talking on a cell phone. Is it
the actual phone in their hand, the actual harness on their head,
the earpiece in their ear, or the microphone clipped on their
lapel? After all, if ever there was a society acclimated to
multi-tasking, it is the present day.
I'm an Emergency Vehicle Operation driving
instructor with my Police Department. I began making some
observations in March, 2003, during a month of high-speed,
stress-induced, and pursuit-type driving. We train our
Officers to transmit only while driving in a straight line.
Always keep your eyes moving/scanning your surroundings to overcome
the setting in of potential of tunnel vision. Tunnel vision
doesn't just mean that you begin losing peripheral vision, but it
also includes the fixation on an object directly in front of
you. This could be as simple as the roadway most directly in
front of your vehicle. Could that tunnel distance be as close
as 50 feet or less in front of your vehicle?
It would appear that accident results show it
could be. I submit to you that using a phone can create its
own version of tunnel vision. A "mental tunnel vision," if you
will, can overtake your primary function of driving a
vehicle. Think of it, drivers are striking barriers directly
in front of them. I can't tell you how many times during our
pursuit driving that the Officers overshot turns, went off road,
etc. because they were baited into communicating at inopportune
times during strenuous driving conditions. The communication
function overrode the driving function. I was able to correct
these mistakes by reminding the driver to look through the curve,
scan well ahead of your vehicle, and keep his/her eyes moving.
Of course, in pursuit driving, we talk about combat breathing and
wiggling your toes amongst other things to keep the stress down.
There's no need for that extreme in simple cell phone usage; but as
you will see, some of these principles do apply.
To answer the question of why a driver
can carry on a conversation with a passenger in his/her own vehicle
and consciously make good decisions during the trip, I began
watching people talking to each other in any and all settings
including while driving a vehicle. Watch them for yourself;
and notice how they look around, look over the person they are
talking with, look away, look in their mirror, look back at the
person, and so on. The driver's head and eyes move
constantly. Outside of a car it is rare for two people to
start talking to each other while starring into each others' eyes,
never looking away or being distracted by any external stimuli until
their conversation is over. Now you may see where I'm going
with this.
Back to the big question of how the cell phone
spell seems to come over some drivers and cause them to drive
unconsciously. I spoke earlier of the fact that the answer is
simple. In fact, cell phones are not the real problem.
The real underlying problem has to do with phones period and how we
are conditioned to use them.
Again, I began watching people. People
are creatures of habit and conditioning. The reality of it all
is that a phone is a phone no matter what kind it is. From
early age, we begin using a phone; and it's a thrill to get to talk
on it as a child. Watch a child talk on the phone. Most
will look straight ahead as they listen or talk. Many will
look down as they concentrate on the conversation. I watch my
teenagers on the phone; and most of the itme, it is much more of the
same. They look down in front of them or straight ahead as
they listen and respond. Next, I started watching the people
at work answering telephones.
Many times you will notice people will
actually freeze for a second or two as they begin talking or
listening. It's natural conditioning. Not bad in and of
itself when you're sitting in an office chair or standing in your
kitchen; it's just natural conditioning. After all, when we
are on the phone, we aren't on a sight-seeing venture. The
phone is thought of as an audio device similar to a radio and not as
a visual instrument or tool. The majority of time, most people
are using the telephone in a safe setting with little danger.
Because people are creatures of habit, we carry conditionings from
one set of circumstances to another similar set of
circumstances. Again, to people a phone is a phone is a
phone. The furthest thing in the back of most drivers'
minds is that their vehicle would ever hurt anyone. But close
to the front of a cell phone driver's mind is that they know how to
use a phone. They've been using a phone since they were three
years old when they first talked to their parent who called home
from work. What they don't see is the potential danger in
mixing the two otherwise innocuous ingredients that can create a
mental tunnel vision state of mind.
Lastly, concerning phone conditioning, you
tell me if this isn't true: No one likes to be
interrupted when on the phone. They learn to shut out external
noise and stimuli during the conversation. So when a vehicle
driver makes the phone call "primary" and driving "secondary,"
driving stimuli can get somewhat shut out as a form if distraction
or interruption to the phone call.
The way to avoid this mental tunnel vision is
to "scan." Keeping your eyes and head moving is imperative to
safe driving under these circumstances. It forces you to keep
driving as your primary function. Understand, I didn't say
eyes or head; I said eyes and head. Remember that most people
are conditioned over a lifetime to pick up a telephone and look
straight ahead as they talk. There is not much head
movement and not much eye movement.
Look back to the four examples of accidents I
gave earlier. See the similarities. Every driver missed
what was directly "in front" of their vehicle. They were "cell
phone-using drivers" not "drivers using cell phones." Prior
behaviorial conditioning of phone use dominated their prior
conditioning for driving.
Drinking alcohol and driving causes divided
attention, slowing and clouding our decision-making process.
Multi-tasking on your home computer causes the machine operation to
slow down. Much the same is cell phone use in an
automobile. In all three situations, some task is slowing the
primary process from being accomplished at 100%. I am of the
opinion that cell phones can be used safely in automobiles as long
as proper precautions are taken.
I've been in a car many times when the driver
gets a cell call. I've watched as the straight-ahead stare
sets in. They listen and talk, never moving their eyes or head
from side to side. I have at times gently reminded them of
what was coming up, as if they needed one more stimulus at that
moment. And then I receive feed back from them in the form of
"What?" which only confirmed to me that they were at maximum
attention capacity.
The safe use of cell phones in vehicles has
nothing to do with the conversation itself; it has everything to do
with overcoming previous conditioned behavior of phone use. As
a Patrol Officer, I have had many occasions to be driving, typing,
and talking on the radio at the same time. As much as I
shouldn't say it, I've had the occasion to do all that and be on the
cell phone at the same time once or twice. I have to
consciously remind myself to "keep it moving." I'm a firm
believer that if I can do it, anyone can learn to "keep it
moving." I've had a little more personal incentive to find the
cause of this dilemma because I see the affects of it. I'm
confident that keeping my eyes and head moving while I'm using a
cell phone and driving a vehicle has helped me and others in my
path, time and again.
________________________________________________________
Back to
INDEX
Author of "Cell
Phone Usage While Driving," Officer Greg Edgcombe, may be reached at
gedgcombe@yahoo.com Grand Rapids Police
Department, Grand Rapids, Michgan.
Joseph E.
Badger, a nationally known Accident Reconstruction Consultant, is a
frequent contributor to NRLO. He may be reached
at jebadger1@comcast.net.
NATIONAL RESERVE LAW
OFFICERS ASSOCIATION P.O. BOX
6505 SAN ANTONIO, TX 78209 (210)
805-8917 FAX (210)
804-2463
|