Incident · Malfunction
Matternet medical-delivery drone operated for Swiss Post crashes into Lake Zurich
A Matternet quadcopter carrying a (non-critical) lab sample for Swiss Post went down into Lake Zurich; its parachute deployed and police divers recovered it from about 20 meters. A short circuit that cut power to the GPS unit was cited. Source: Swiss FOCA-supervised review; The Local and IEEE Spectrum reporting.
Occurred 2019-01-25 · Matternet
How to read this record
Incident records on DEPLOY are compiled from public sources (regulatory filings, news reports, and operator disclosures) and reflect what has been reported and tracked to date. They are not legal findings, determinations of fault, or safety ratings, and may be updated as new information is verified. See the sources below for the underlying references.Machine-readable surfaces
- Markdown mirror: /incidents/matternet-swiss-post-lake-zurich-crash-2019.md
- JSON-LD: embedded in this page’s head
- REST API: /v1/incidents/8d44b905-9814-4c6c-bad1-3833d5c0bdaf
- Data documentation: /data
- Query this programmatically: Deploy MCP
Sources (2)
Common questions
What happened in Matternet medical-delivery drone operated for Swiss Post crashes into Lake Zurich?
When did this incident occur?
Who was involved in Matternet medical-delivery drone operated for Swiss Post crashes into Lake Zurich?
Has anyone responded to Matternet medical-delivery drone operated for Swiss Post crashes into Lake Zurich?
What is the current status of Matternet medical-delivery drone operated for Swiss Post crashes into Lake Zurich?
Methodology: Verified · 2 sources (no primary) · last reviewed 2026-08-09
Verification posture
Verified
Low confidence
Review state
Stable
Last reviewed 2026-08-09
Sources by quality tier
- 2
- unclassified
- Unclassified source
The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.
Methodology surface for Matternet medical-delivery drone operated for Swiss Post crashes into Lake Zurich.Deploy Watch
Track this incident.
We notify you when the regulator updates the record, the remedy status changes, or a related incident surfaces.
Canonical ID 8d44b905-9814-4c6c-bad1-3833d5c0bdaf