EXAMPLES Path Intrusion (Side) Example I
PATH INTRUSION EXAMPLE 1 We want to estimate the response of a motorcyclist. One may ask, “Does a motorcyclist’s response take
less time because they do not have the same leg movement as the driver of a car?” The answer would be both
yes and no. While the motorcyclist does not have to move their hands or feet very far to brake, their
search range is typically larger and their response complexity is almost always more complex.
Therefore, it is best to treat a motorcyclist as you would the driver of a car since the additional
complexity and the lack of movement time appear to cancel out.
A gray pickup drives north out of a side road and into the path of a westbound motorcyclist. The motorcyclist was traveling west at a speed of 42 fps and skidded at 10 feet before impact (.4 factor). The pick up rolled through the intersection at 5 fps and accelerated at a rate (factor) of 0.15 for the next 40.9 feet. The driver of the gray pick up looked right, then left before starting forward. The sight line was limited to 135 feet due to traffic
Using DRIVE3
After opening DRIVE3 - click on the term "DRIVE3"
Then select "Path Intrusion (Side)"
(because the intruder or "target" or "hazard" is emerging from the side of the primary driver (the supposed responder).
If DRIVE3 is not set to the unit of measure you wish, Go to "Setup"
Click on DRIVE3 and selects the unit of measure you wish to work with. In this example, feet per second.
Then click on "Accept"
Motorcyclist’s Response? Transition = 3 Anticipation = 5 Experiment type = 4 Driving = 1 Daylight (1) Urban (2) Intersection (2) Single stimuli Press Eccentricity “Compute” Primary = 134.355, Intruder = 30.7 = 12.8
Recall here that the pickup moved 40.9 feet, but the front of the pick up was only 30.7 feet left
from the supposed RESPONDER'S EYES when the intrusion began.
The left side of the screen is the entries and the right side of the screen is
the output. The Driver Response Equation (DRT) result is 1575 ms. Or 1.6 seconds based
upon the equations published by SAE in 2003 and 1407 ms or 1.4 seconds based upon the equations that are based upon
the additional data that has been collected since (and published in 2005 and in press).
Since this was a response to a vehicle, we look at the Adjustment-to-Baseline results from vehicle studies.
The average adjusted response time to studies 3, 4 and 5 is 1.411 seconds and when
we consider both the adjustment-to-Baseline and the DRT equation we have an
"Overall Average" (DRT equation and Adjustment to Baseline) is 1.4 seconds.
The Standard Precision Range in this case would be 493 ms or 0.5 seconds. This means that 70% of INDIVIDUALS
will respond within 0.9 and 1.9 seconds under the circumstances you defined.
The user must understand the difference between the accuracy with individuals and the accuracy of the equations generally.
We cannot predict the response time of someone who intentionally crashes or who exercises no care or attention.
However, when averaged, DRIVE3 has consistently (100% to date) predicted the response time for given scenarios within
0.4 seconds. The results of DRIVE3 should be used as a comparison tool after the crash has been reconstructed.
In that way the analyst may compare the actual response to the average response for a given scenario which
will allow the analyst to offer a conclusion regarding whether the response was above or below average to to what extent.
DRIVE3 will typically round down, however the actual response time is equally
likely to be anywhere within the range of plus or minus 493 ms (which has captured
68.4% of the real life responders to date). This means that 85% of all drivers will
likely respond faster than 1903 ms (1410 ms Overall + 493 ms Std Precision range).
Looking
at Example I – in the "Data to Impact" Result, it shows that the
primary vehicle was 235 feet
from impact when the side road driver last looked in his direction.
The Intruder (side road driver) was 52.9 feet from impact and this was
5.6 s. before impact. “No” means that main road driver was not within the
intruder’s sight line (based upon the entered sight line).
According
to Robinson et al, 1972, the last look phenomenon takes 1 second.
At
the decision making point (4.6 s. before impact – notice this is 1 s. later,
after the driver last looked in the opposite direction).
The primary (main road) driver (our responder) was 193 feet from impact and the
intruder was 47.9 feet from impact.
A
compilation of Research (cited in
the manual) shows that drivers need approximately 1.4 s. from when they decide
to pull out to the point their vehicle first moves.
Therefore, 1.4 s. decision time.
DRIVE3 breaks out start up time from last look time, while AASHTO's A Policy on Geometric Design for Highways and Streets recommend a rule of thumb of 2.0 seconds for start up time. If you do not know which direction the driver looked last the user may select either "Same" or "Opposite" at their
discretion (it will not change any other outputs), but by selection of "Opposite" he or she will be able to answer questions regarding that hypothetical (What if...) question later (If "Same" is selected then "Last look" results will equal "Decision Point" numbers).
4.6 s - 1.4 s = 3.2 seconds before impact.
We
are now down to 3.2 s. before impact when the intruder starts into traffic and
the main road driver is 134 feet away and is now (“Yes” under <sight
line) within the intruders sight line (but he has already made his decision to
pull out).
The
main road driver then starts to skid (or steer if that were the case) ¼
(0.2474) sec
before impact.
At
impact (t=o) the vehicles are traveling 38.81 and 20.496 fps respectively.
PATH INTRUSION EXAMPLE II We would like to estimate the response time of the white vehicle in the figure below.
A white Jeep drives east. A red car stops and then turns into the path of an eastbound
driver at NIGHT. The driver of the eastbound white car was traveling at a constant speed of 17.56 km/h
before impact. The red car was initially stopped (initial speed =0) facing the White
Jeep before turning into the intersection (.24 factor) and accelerated forward 7.62 m (25')
and laterally 5.245 m (17.21'). Drive3 assumes that the vehicle drove the arc of the curve defined by
the middle ordinate (lateral distance) and the chord (2 x the linear distance) which equals an arc
length of 11.98 m and an Approach Angle of 34.5 degrees. The sight line was limited to 150 m due to a knoll in the road.
Using DRIVE3
After opening DRIVE3 - click on the term "DRIVE3"
Then select "Path Intrusion (Front)"
(because the intruder or "target" or "hazard" is emerging from the in front of the primary driver (the supposed responder).
If DRIVE3 is not set to the unit of measure you wish, Go to "Setup"
Click on DRIVE3 and selects the unit of measure you wish to work with. In this example, feet per second.
Then click on "Accept"
Red Car Driver’s Response? Transition = 3 Anticipation = 5 Experiment type = 4 Driving = 1 Daylight (2/night) Urban (2) Intersection (2) Single stimuli Press Eccentricity “Compute” Offset Distance (Intruder) = 1.22 m (4')
Linear Distance (Primary) = 15.561 m (This is obtained from the distance of the primary at the start of the intrusion
on the right side of the screen) = 4.4 deg.
The left side of the screen is the entries and the right side of the screen is the output.
The Driver Response Equation result is 1543 ms. or 1.5 seconds. Since this was a response to a vehicle,
we look at the Adjustment-to-Baseline results from vehicle studies. The average adjusted response time
to studies 3, 4 and 5 is 1.788 seconds and when we consider both the adjustment-to-Baseline and the DRT
equation we have an estimated time of 1.666 seconds.
DRIVE3 will typically round down, however the actual response time is equally likely to be anywhere within the range of plus
or minus 583 ms (which is the Standard precision range and has captured 68.4% of the real life
responders to date). This means that 85% of all drivers will likely respond faster than 2250 ms
(1666 + 583).
The maximum time before the response is the time from when the hazard was first perceivable until the
point that the vehicle first responded (or until impact).
Tip - if the time and distance results do not show, enter a deceleration factor even if the vehicle did
not skid or change speed before impact.
We would like to estimate the response time of the eastbound red vehicle in the figure
below (assuming north is up). Another vehicle just passed a pedestrian who was stopped
at the centerline and was attempting to cross from north to south at NIGHT.
The driver of the eastbound red car (headlight height of 25 inches) was traveling at a constant speed of 40 mph (64.4 km/h) before
impact. The driver claims that his foot was on the brake pedal because he was traveling
down a steep grade. (Adjustment of ~ –400 ms). The centerline is 4'(1.21 m) to the left
of the driver’s position. The pedestrian is walking at an average speed of 3 mph(4.8 km/h).
The pedestrian was wearing dark clothing on this unlighted road.
The pedestrian did not contrast from the background very well. If this pedestrian was
not easily identifiable as an immediate hazard, then no driver response time should be
applied. It is not possible to "perceive" something as an immediate hazard if you cannot
detect it or do not know what it is (is most cases). Please read the IN CAR CREEDS acronym
under the DRIVE3 Information drop down list.

Using DRIVE3
After opening DRIVE3 - click on the term "DRIVE3"
Then select "Path Intrusion (Side)"
(because the intruder or "target" or "hazard" is emerging from the side of the primary driver (the supposed responder).
If DRIVE3 is not set to the unit of measure you wish, Go to "Setup"
Click on DRIVE3 and selects the unit of measure you wish to work with. In this example, miles per hour.
Then click on "Accept"
For the sake of this calculation however, lets assume this was a lighted road and the
pedestrian was easily identifiable as an immediate hazard (assuming that the driver
was not looking directly in that direction) and no disabling glare or adaptation problems
existed for the driver.
The pedestrian was crossing at a mid block location (not at an intersection or curve) The sight line was limited to 500 feet due to a knoll in the road (in daylight)
Red Car Driver’s Response? Transition = 3 Anticipation = 5 Experiment type = 4 Driving = 1 Daylight (2/night) Urban (2) Topography Straight (1) Single stimuli Calculate Eccentricity at the start of the intrusion by pressing “Compute” -
Intruder = 4 (1.21 m)
Enter Primary = 53.33' (16.255 m) (Start of intrusion distance from the right),
= 4.289 deg.
Adjustment –400 ms (leg hovering over brake)
The left side of the screen is the entries and the right side of the screen is the output.
The Driver Response Estimation (DRT) equation results result is 1869 ms. or 1.9 seconds.
Since this was a response to a pedestrian, we look at the Adjustment-to-Baseline results from vehicle studies.
The average adjusted response time to studies 1, 2, & 9 is 1984 ms and when we consider both the
adjustment-to-Baseline and the DRT equation we have an estimated time of 1.926 seconds.
DRIVE3 will typically round down, however the actual response time is equally likely to anywhere
within the range of plus or minus 674 ms (which has captured 68.4% of the real life responders to date).
This means that 85% of all drivers will likely respond faster than 2600 ms (1926 + 674).
In this instance, an adjustment to account for the reduction of leg movement time and vehicle latency
was entered.
Be prepared in this case to prove that the pedestrian would be EASILY identifiable as an IMMEDIATE hazard. If either is
not true, then this calculation would have no relevance. Therefore, the analyst must establish an objective threshold at which
the pedestrian could have been perceived by most drivers.
DRIVE3 offers the Twilight Distance Method to calculate the point at which the headlights will likely illuminate ahead up to
0.3 foot candles (which is the approximate ambient light at Twilight). Twilight (the end of dusk) has been recognized as the time at which outdoor
activities can no longer be performed effectively.
To utilize the Twilight Distance Calculation, click on the light blue TDM button. Enter the light threshold (0.3 fc) and the headlight height (25 inches)
You may notice that the headlights may illuminate 0.3 fc or more up to a distance of 248.42 feet according to this calculation.
If you select "Return with Sight Line Data" it will enter this number as the sight line and the Maximum Time Before Response will be
considered using this distance as the sight line. Since a headlight beam is not symmetrical, an analyst should also consider whether the
object to be perceived is within the headlight beam pattern.
If you select the blue "Graphics" button, you will get a rough idea of the headlight beam pattern. Therefore, only part of the beam
extends out to the maximum Twilight distance.
DRIVE3 should automatically calculate headway to be 3.57 s., but the user has the option
to override this entry. DRIVE3 assumes that the driver has both steering and braking as
available avoidance options (more options would cause an increase in response time).
Red Car Driver’s Response?
Using DRIVE3
After opening DRIVE3 - click on the term "DRIVE3"
Then select "Vehicle Following"
If DRIVE3 is not set to the unit of measure you wish, Go to "Setup"
Click on DRIVE3 and selects the unit of measure you wish to work with. In this example, miles per hour
Then click on "Accept"
Transition = 3 Experiment type = 4 Driving = 1 Daylight (1.5/dusk) Highway (3) Straight (1) Single stimuli
Note that headway when the relative velocity threshold [0.006 radians/sec] is met
is given to the right (3.57 sec). Note if you enter the headway manually, the word "Headway" will turn red
and indicate that there was a manual entry. If you wish to again have DRIVE3 calculate
the headway at the RSAV threshold, then clear the headway box and press enter and headway will again be automatically calculated.
To obtain the eccentricity when the Subtended angular velocity threshold is met.
Press Eccentricity “Compute” Primary (from the right side of the screen) = 314.64' (65.73 m), Intruder = 0 = 0 deg. (The bus is straight ahead)
The sight line is 2500' (762 m).
The left side of the screen is the entries and the right side of the screen is the output. The results show that half of all drivers will
perceive an immediate hazard ahead when 314.64 feet (3.57 sec) away from the rear of the lead vehicle. From that distance, the average
perception-response time is 1.9 seconds. Therefore, the average driver's vehicle will begin its maneuver 144 feet before impact (plus or minus the range).
Therefore, DRIVE3 ALLOWS FOR A DIRECT COMPARISON WITH SCENE EVIDENCE. If the driver did not begin their response
earlier than 75 feet (143.64' - 68.4') before impact, then that driver responded slower than 85 percent of all drivers in research and real life
situations that were similar to the situation entered.
Same situation as above, but this time the lead vehicle stops for an an red traffic signal
at an intersection. Therefore, change the topography to "Intersection" -
In vehicle following situations, response times increase as headway increases,
except when approaching a red traffic signal or a visual cue
that allows a following driver to see that the lead vehicle is not moving
as expected (signs and flashing lights alone may not be effective in many situations).
In these circumstances, research has shown that the headway term is no longer a variable that
is associated with changing response times and if a nominal 1.5 second headway is entered,
the average response times can be estimated very well.
Using DRIVE3
After opening DRIVE3 - click on the term "DRIVE3"
Then select "Vehicle Following"
If DRIVE3 is not set to the unit of measure you wish, Go to "Setup"
Click on DRIVE3 and selects the unit of measure you wish to work with. In this example, miles per hour
Then click on "Accept"
The left side of the screen is the entries and the right side of the screen is the output.
The Normal Response Time is 1.069 seconds (it is best to report response times to the tenths of a second, such as 1.1 seconds). DRIVE3 will typically
round down, however the actual response time is equally likely to be anywhere within the range of plus
or minus 427 ms (less than one-half second). More than 90% of the real life responders to date have fallen
within the precision range of the estimated response time.
This means that 95% of all drivers will likely respond faster than 1.5 (1.069 + 0.427) seconds in this type scenario.
We would like to estimate the response time of the red vehicle in the figure below.
A tan car is changing lanes into the path of the red car from the area
just in front of the red car driver’s “A” pillar from the driver's perspective
(approximately 20 degrees).
The collision occurred at noon. The driver of the eastbound red car was traveling at a constant speed of 96 fps
(105.33 Km/h) before impact.
The gray car slowed as it moved into the path of the red car. The driver of the red car applied the brake and skidded 10' (3.05 m)
(0.7 deceleration).
The gray car started from the left lane (one lane over).
Red Car Driver’s Response? Transition = 3 Anticipation = 5 Experiment type = 4 Driving = 1 Daylight (1) Highway (3) Straight (1) Single stimuli Eccentricity = 20 degrees
The left side of the screen is the entries and the right side of the screen is the
output. The Driver Response Equation result is 1016 ms. or 1.0 seconds. DRIVE3 will
typically round down, however the actual response time is equally likely to be anywhere
within the range of plus or minus 305 ms (0.3 s). In research, the actual response
time fell within the range more than 67.6% of the time. This means that 85% of all
drivers have responded faster than 1322 ms or 1.3 s. (1017 + 305).
Since this was a response to a vehicle, we look at the Adjustment-to-Baseline results
from vehicle studies. The average adjusted response time to studies 1, 2, & 3 is 1.0
seconds and when we consider both the adjustment-to-Baseline and the DRT equation we
have an estimated time of 1.0 seconds and a range of 0.3 second. Also note in the
time and distance calculations that the “average” driver would have started the
perception process approximately 1.1 seconds before impact (based upon these entries)
and would have been approximately 107' (32.81 m) from impact.

This module is based directly upon the research by Chang et al. (1985) who indicated that the probability of stopping, the deceleration rate and the response time to yellow traffic signals is based upon the distance to the stop line, the distance to travel through the intersection (He referred to this as the width), the speed of the vehicle and the grade of the road.
If we have a situation involving a vehicle traveling 40 mph who is 250 from the stop line when the signal changes to yellow. The vehicle is traveling up a 2 percent grade (0.02) and the (longitudinal) width is 45 feet. The sight line is the furthest that a driver can see the signal from their eye height, for our example we used 2,500 feet.
The results indicate that the likelihood of stopping under this situation is 72%. Of those who choose to stop, the average deceleration factor would be approximately 0.32 gs and the average response time would be 1.1 second.


Example X Response to an impact
Response time should be 1/2 to 1 second to respond to an impact that offers audible and tactile stimuli to the driver that is likely to be immediately identified as an impact based upon the following research.
•LIGHTS 0.86 (SD = 0.36) (prepared for)
–Cation et at, 1951; Cohen, 1987; Fambro et al, 1998; Harms, 1988, Hau et al, 2000, Lisper et al, 1967; Koppa et al, 1996; Luoma, et al, 1995; Martens et al, 2000; Olson & Sivak, 1986; Olsson, et al, 2000; Ranney & Simmons, 1992; Sayer et al, 1996; Tokunaga et al, 2000; Vercrussen et al, 1996; Warner & Mace, 1974; Yoo et al, 1999; Scott et al, 1996
•SOUNDS 0.51 (SD = .14) (prepared for)
–Wierwille et al, 1983; Tornros, 1995; Lerner, et al, 1997; Vercruyssen et al, 1996; Johansson & Rumar, 1971; Laurell & Lisper, 1978; Moss & Allen, 1925
However, if the audible or visual signal is not immediately identified, response times can be much longer.
•Otto, Otto, & Overton, 1980 (Not prepared for)
–2.9 seconds (in response to a throttle being stuck when riding a motorcycle)
To print entire page, set margins as seen below.
Select File, Page Setup
