Thirteen killed in Aerodiana sightseeing plane crash over Peru's Nazca Lines
Outlets report no survivors among 11 foreign tourists and two crew after the aircraft went down on August 1, 2026; the cause has not been determined, and reporting has not advanced since August 2.
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
- 12,497 ft
- Nearest aerodrome
- 8.7 miles SSW of Air Force Colonel Alfredo Mendivil Duarte Airport (SPHO/AYP)
Sources
- 13 killed in tourist plane crash in Perudw.com
- 13 dead after small tourist plane crashes in Peruvanguardngr.com
- Tourist plane on sightseeing flight in Peru crashes into a fielddailymail.com
- Thirteen dead in Peruvian tourist plane crash over Nazca Linesaljazeera.com
- Plane crash in Peru kills 13 people on tourist flight abc.net.au
- 13 tourists killed in plane crash near Peru's famed Nazca Lines during viewing flightnypost.com
- Thirteen people dead after small tourist plane crashes in Peruthejournal.ie
- Peruvian plane crash kills 13, including European tourists - Al Jazeera - Slashdotslashdot.org
- 13 killed in small tourist plane crash in Peruvanguardngr.com
- 13 die in Peru tourist plane crashpunchng.com
- Tourist plane crashes near Nazca Lines in Peru, killing 13 - AeroTimeaerotime.aero
Revision history
- Version 77 Aug 2026, 15:22current
Removed the sentence declaring the event "still developing" and replaced it with a dated statement that the reporting rests on August 2, 2026 coverage and has not advanced since; added a matching note to the dek. Expanded the crash-time paragraph to print each outlet's wording exactly ("shortly after 1:00 pm", "shortly after 1pm", "about 1:00pm local time", "shortly after 1:00 p.m.") rather than collapsing them into one phrase. All other facts, attributions, conflicts and figures — including the 12,497 feet elevation — are unchanged.
- Version 64 Aug 2026, 23:40
Added headline and dek, credited Slashdot in the fatality attribution, noted the operator's use of Cessna Grand Caravan aircraft, and stated that the 2022 and 2010 accidents bear on nothing about this cause.
- Version 54 Aug 2026, 23:28
Added headline and dek, and clarified that no registration appears in the material so the airframe remains unidentified; attribution otherwise unchanged.
- Version 44 Aug 2026, 23:23
Removed the claim that the tail number is unknowable, adding Pisco to the conflicting crash-site list, and added a headline and dek.
- Version 34 Aug 2026, 20:09
Added a statement that the aircraft's registration is unidentified and why, and folded the location reference data into the closing paragraph.
- Version 24 Aug 2026, 20:09
Added multi-outlet sourcing, conflicting aircraft type, crash location and time figures, victim ages and nationalities, crash-site details, Fujimori's airport suspension remarks, prior Nazca wind suspension and Aerodiana's 14 years of operations.
- Version 14 Aug 2026, 20:09
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.