FirstAlerts

Aston Martin in Hyderabad Crash Identified; Driver Tested Negative for Alcohol and Drugs

Police identify the car involved in the August 16 accident that killed a mall staffer; investigation continues.

2 reports on this incident · first at Aug 20, 2026, 4:01 p.m. ET

By AI ReporterFirst reported Aug 20, 2026, 3:42 p.m. ETWritten Aug 20, 2026, 4:05 p.m. ET
The car involved in the August 16 accident in that killed a mall staffer has been identified as an Aston Martin with registration , according to the Times of . The driver tested negative for alcohol and drugs, the outlet reported. The accident occurred in , . The Madhapur police are investigating; they said further investigation into the circumstances is under way. The cause has not been determined.

Earlier reports

  1. Aug 20, 2026, 4:01 p.m. ETFirst report

    Aston Martin Crash in Hyderabad Kills Mall Staffer; Driver's Son of Politician Booked

    A car crash in Hyderabad on August 16, 2026, killed a mall staffer, according to the Times of India. The accident involved an Aston Martin with registration TG09 G 0666, occurring around 3 pm. The driver tested negative for alcohol and drugs, the report said.

    The Madhapur police are investigating the circumstances surrounding the accident. Police said further investigation is under way. The cause of the crash has not been determined.

    The Times of India reported that the driver is the son of a Janasena MP, and that he has been booked in connection with the incident.

Was this report accurate and useful?

Reference data

From aircraft and geographic registries, not from the news sources. Registry records can be out of date, and describe the aircraft and the place only — they say nothing about what happened.

Terrain elevation
1,660 ft
Nearest aerodrome
6.4 miles S of Begumpet Airport (VOHY/BPM)

Sources

Revision history

  1. Version 120 Aug 2026, 20:05current

    First published.

  2. Version 120 Aug 2026, 20:01current

    First published.

How we work

This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.

Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.

Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.

None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.