Drivers trusted the turn-by-turn voice into 59 waters, 25 deserts and 19 cliff edges

Asked:

“Map every documented case of a driver following GPS into a lake, desert, or cliff — 'death by GPS' incidents”

A live-web scan on 31 August 2026 surfaced 103 distinct reported incidents after semantic filtering and incident-level deduplication, spanning 2003–2026 across at least 20 countries. “Death by GPS” is the established umbrella term: the census includes fatal events, survivals, rescues and near-disasters. This is a documented-web census, not an exhaustive global registry.

Where navigation led drivers astray

water (59)desert (25)cliff / precipice (19)circle size = incidents at that spot · dark ring = at least one death reported

Positions are approximate, placed from the published location text (town, park, road or country level); precise coordinates were not published in the source data. One incident (“a dam”, location unstated) cannot be placed and is omitted from the map.

The record thickens after 2021 — and it is mostly water

waterdesertcliff

85 incidents carry a usable year; 18 more were reported only with relative or partial wording (“Friday”, “last year”) and are held out of the timeline rather than placed falsely.

What the record says, beyond the map

Water dominates: 59 of 103 incidents (57%) end in a lake, river, harbour or canal — from a BMW driven down a ferry ramp into the Havel river in Germany in 2005 tapesearch.com to a car in a Thai irrigation canal in 2025 theglobeandmail.com.

The deadliest single case in the set: a mother followed her GPS onto a gravel road in Death Valley in August 2009; her son died before rescue — the most heavily corroborated incident here, with 48 independent pages thetimes.com.

Utah's Grand Staircase–Escalante is a repeat trap: the same monument roads appear in incidents from 2003, 2007, 2008 and 2017, stranding everyone from couples to a 26-person convoy automotive-fleet.com.

The first legal precedent: in 2009 a UK driver whose satnav left his BMW teetering over a 100-ft drop in Todmorden became the first person convicted for blindly following satnav directions dailymail.com.

Evidence is thin for much of the tail: 45 of 103 incidents rest on a single accessible page, while the average incident is corroborated by 5 pages — the ledger below shows each count as a confidence cue.

Incident ledger — all 103 rows

Date	Location	Category	People & outcome	Navigation-linked outcome detail	Pages	Source

Rows outlined in crimson at the left edge report at least one death. Blank cells mean the source did not state the value; nothing is guessed. Relative dates (“Friday”, “last year”) are shown as published, unresolved.

Method: documented-web census compiled by a broad live scan on 2026-08-31 across water, desert and cliff searches over multiple source types; hundreds of candidate reports were semantically filtered and deduplicated to 103 distinct incidents (59 water, 25 desert, 19 cliff). One row per incident with date, location text, category, people, navigation role, outcome, fatalities where extractable, and corroborating-page count (mean 5, max 48; 45 incidents have a single source). News coverage is uneven; some dates are month/year or relative wording and are left unresolved; precise coordinates were not published, so map positions are approximate; some incidents rest on one accessible source. “Death by GPS” is an umbrella term — the set includes rescues, survivals and near-misses as well as 23 incidents whose outcome text reports at least one death.

This report was generated automatically by Keenable SELECT at a user's request, from publicly available web sources linked herein. Keenable does not review, verify, or endorse its contents and makes no representation as to accuracy, completeness, or timeliness; AI-based extraction may contain errors. Nothing in this report is investment, legal, financial, or other professional advice. All trademarks and referenced content remain the property of their respective owners; no affiliation or endorsement is implied. To report an error, rights concern, or request removal: legal@keenable.ai.