Правосуддя · Tucson crash investigation
Tucson crash speed estimated at 100–150 mph as recorder data hangs in doubt
Roadway measurements suggest 100–150 mph in the crash that killed three Salpointe students, but the estimate is preliminary and fire-damaged recorder data may be lost.
Написано 4 хв читання · 20 джерел
Доступно англійською
How much can investigators establish about a fatal crash if the car’s own electronic record is lost? In the Tucson-area collision that killed three high school students, roadway measurements now suggest the Dodge Challenger was traveling between 100 and 150 mph, with uncertainty of up to 15 mph, Pima County Sheriff Chris Nanos told the Arizona Daily Star. That preliminary estimate supports an account of extreme speed. It does not establish a precise speed at impact—and fire may have destroyed data that could help narrow the answer.1
Опитування читачів
How useful do you consider phone-app driving records in a crash investigation?
The crash happened late on November 14, 2026, near East Skyline and North Foothills drives. Alex Schneider, 18, was driving the 2014 Challenger. His passengers were Joel Slavin, 16, and Madison “Maddy” Rea, 17. All three attended Salpointe Catholic High School. Their deaths are the background to this investigative update, not a newly increased toll.113
The distinction between an estimate and a recovered measurement matters here. Nanos’s account, published by the Arizona Daily Star on November 21, rests on manual roadway measurements taken by crash investigators. It is not the result of a completed download from the vehicle’s event data recorder. Nor is 150 mph a confirmed reading: it is the upper end of the sheriff’s stated range, which carries its own uncertainty.1
The physical evidence describes a violent sequence. Nanos said the Challenger bottomed out and struck two curbs, dislodging the engine from its compartment. “The entire motor is thrown from the vehicle,” he told the Star. He described that separation as probably one of the biggest causes of the subsequent fire—a qualified investigative assessment, not a settled determination of how the fire began.1
Two speed accounts, different limits
The roadway reconstruction falls in the same broad range as a 134 mph trip maximum displayed by Life360. Maddy’s father, David Rea, supplied the screenshot described in the Star’s reporting. Nanos explicitly connected the two accounts.1
What we're seeing supports what Life360 is saying.
That agreement is meaningful, but it does not make the two sources interchangeable. One is a reconstruction from the crash scene; the other is a phone-based record of a drive. The available screenshot account does not establish where along the journey the maximum occurred, how long it lasted, or whether the Challenger was moving at that speed when it struck the curbs. A trip’s fastest recorded moment and its final moment are different questions.17
Life360’s Drive Detection analyzes phone location and activity to identify driving. It is not the Challenger’s onboard recorder. The company warns that speed accuracy depends heavily on the device and service quality, that some trip points may be missed, and that captured speeds can be inaccurate. Its supplied documentation offers no numerical error margin that can be applied to this particular 134 mph reading.42
The service also distinguishes a trip maximum from a “Speeding” event. Its rule for that event requires a vehicle to exceed 80 mph for at least 30 seconds. That does not establish that a trip maximum must last 30 seconds, and it tells investigators nothing about how long this trip’s reported maximum persisted.67
The sheriff’s department’s position is appropriately narrower than treating the screenshot as a verdict. Spokesperson Angelica Carrillo told the Star that app information can help paint a picture of what possibly happened, but is not what investigators use to determine exactly what happened. They also examine tire marks, vehicle damage and distances across the scene. The app is a piece of the reconstruction, not a replacement for it.1
The clocks still need reconciling
There is another unresolved limit in the available account: the times do not line up. The department’s initial release placed deputies’ response at approximately 11:05 p.m. The Life360 screenshot, as described by the Star, displays departure from the Rea home at 11:06 p.m. and the trip ending four minutes later, at 11:10 p.m., near the crash location.131
The available evidence does not explain that discrepancy. The initial response time was approximate, while the screenshot supplies displayed app times; neither should be silently adjusted to make a neat chronology. The four-minute trip shown by the app is not yet a fully synchronized official timeline, and it is not evidence that the car traveled at its reported maximum throughout those four minutes.
The most consequential missing evidence may be inside the damaged recorder. An event data recorder captures technical information associated with a crash or sudden impact. Nanos told the Star that investigators had removed its chip and were processing it after the device was severely damaged by fire. “It looks OK,” he said of the chip, while warning that the data might be damaged and “we may get nothing.”1
An apparently intact chip is not proof of surviving information. No usable recovered results or completion date are established in the available update. If data can be retrieved, it could help narrow the speed estimate or clarify the sequence; successful processing would not automatically guarantee a precise impact speed or resolve the mismatched clocks.1
For now, the new reconstruction gives a more concrete account of the Challenger’s speed without completing the explanation of the crash. If the chip yields nothing, investigators will still have the roadway, the wreckage and other evidence to work from. The responsible conclusion is neither that the app proves every detail nor that nothing can be known without the recorder. The evidence supports extreme speed; the final movements remain under investigation.
Джерела9
3 раніші матеріали використано для контексту.3 видання без дати:
Усі джерела за виданнями
20 джерел з 9 видань· Спочатку найцитованіші
life360.comПершим10
- Уперше повідомило
- Driving Speed & Accuracy – Life360
- Individual Driver Reports – Life360
- Drive Detection & Analysis – Life360
- Crash Detection Troubleshooting – Life360
- In-App Driving Events – Life360
- Introducing: Driving by Life360
- How Accurate Is Life360? | Life360 Location Tracking Accuracy
- Can Life360 Help You Avoid a Speeding Ticket?
- Location & Drive History – Life360
- Movement Icons – Life360
Google News last hour 2tucson.com2
Accident Newsaccidentnews.com1
- Уперше повідомило
- Three killed in car crash on East Skyline Drive in Tucson
Breaking Accident News - CrashDaily.comcrashdaily.com1
Cedar Newscedarnews.net1
- Уперше повідомило
- Speed in fatal Tucson crash reached up to 150 mph, sheriff says
KVOAkvoa.com1
People.compeople.com1
pimasheriff.org1
Як в ефірі
- The Challenger hit two curbs so hard its engine tore free.
- Three Tucson high school students died in the crash, and fire severely damaged the car's electronic recorder. Investigators now have a preliminary speed estimate, but recovering the car's own data could prove impossible.
- Can the surviving chip help investigators work out the car's final movements?
- The 2014 Dodge Challenger crashed late on November 14, 2026, near East Skyline and North Foothills drives. Pima County investigators have been measuring the roadway to reconstruct what happened before the vehicle caught fire.
- Sheriff Chris Nanos says those measurements suggest the Challenger was traveling between 100 and 150 miles an hour. He puts the uncertainty at up to 15 miles an hour. Investigators calculated that range from the crash scene.
- The upper end of that estimate is 150 miles an hour. Nanos hasn't given a precise impact speed. His investigators are working from physical evidence while they try to recover electronic information from the badly damaged car.
- Driver Alex Schneider was 18. His passengers were Joel Slavin, 16, and Madison, known as Maddy, Rea, 17. All three attended Salpointe Catholic High School. Their deaths on November 14 are the reason for this continuing crash investigation.
- Nanos says the Challenger bottomed out and struck two curbs, dislodging the entire engine from its compartment. He thinks that engine separation was probably one of the biggest causes of the fire. Investigators are still working through how the fire began.
- The roadway estimate of 100 to 150 miles an hour overlaps with a Life360 trip maximum of 134 miles an hour. Maddy's father, David Rea, supplied the screenshot. Nanos says the physical reconstruction supports what the app is showing.
- Life360 records a maximum for a drive. Investigators still have to work out how fast the Challenger was moving when it struck the curbs. Agreement between the app and roadway measurements helps them build the reconstruction without settling that final speed.
- Subscribe to this channel to follow the recorder recovery and the continuing crash investigation.
- The sheriff's department initially placed the deputies' response at about 11:05 p.m. But the screenshot displays departure from the Rea home at 11:06 p.m., and the trip ending near the crash four minutes later, at 11:10 p.m.
- Those times don't line up, and nobody has explained the difference. The screenshot provides the family's view of the trip, while investigators still need to reconcile its clock with the initial response time.
- Life360 uses phone location and activity to detect driving. GPS and phone sensors help it analyze the journey. Families can share their locations in groups and receive safety alerts, with driving information available through the service.
- Life360 warns that device quality and service quality affect speed accuracy. Some trip points can be missed, and captured speeds can be inaccurate. Its separate speeding alert requires more than 80 miles an hour for at least 30 seconds. That rule doesn't tell us how long this trip's maximum lasted.
- The sheriff's department treats app information as one piece of the investigation. Spokesperson Angelica Carrillo says it can help investigators piece together what possibly happened, but they don't use it to determine exactly what happened.
- Life360 also uses phone sensors to detect significant impacts when a vehicle is moving at least 25 miles an hour. That threshold describes when crash detection works. Investigators combine app information with tire marks, vehicle damage and distances across the scene to reconstruct a collision.
- Fire severely damaged the Challenger's event data recorder, which captures technical information around a crash. Nanos says investigators removed its chip and are processing it. He says the chip looks okay, but warns that its data may have been destroyed.
- Investigators haven't announced a completion date for that work. Usable recorder data could help narrow the speed estimate or clarify the sequence. If the chip yields nothing, they'll have to keep reconstructing the final movements from the roadway, wreckage and other evidence.
Обговорення
Дописи тут належать до сюжету «The fatal Tucson Dodge Challenger crash» і показуються в усіх його матеріалах.
Нещодавно в ефірі

Доступно англійською
Peter Fluck dies at 85: The artist who brought Spitting Image to millions

Доступно англійською
Neuralink’s reported GTA VI demo puts computer access in focus

Доступно англійською
PSG fear Doué ligament rupture, but Sunday’s scan must establish the damage

Доступно англійською
Windah’s GTA VI peak tops IShowSpeed’s—but the timing is unproven

Доступно англійською
Whitemark officer shot; residents told to expect more police
