DEDICATED RISK REVIEW 04 · SWITZERLAND · HISTORICAL CASE
Swiss grid inspection in 2020–2021: protecting flights, data and continuity
An operation can work well technically. Its complete data chain still needs evidence of its own.
2026-10-01 · v1.0.0
Historical case · 2020–2021. Neither transaction price nor price advantage is established. No reviewed source establishes a data leak in this case. Risk scenarios are our explicitly conditional analysis.
Frame your own requirement01 · What the historical record actually says
On 6 November 2020, BRACK described Bouygues E&S EnerTrans AG using a Matrice 300 RTK with Zenmuse H20T. The operator interview discusses power-line inspection and a move from an M210 V1. It also acknowledges that drones are not more economical for every task. This is operator experience published by a retailer, not an independent cost study. [S1]
DJI subsequently covered the case. Its English page is dated 20 February 2021 and its German page 22 December 2021. Those are publication dates, not evidence of three separate purchases. Both manufacturer pages belong to the same source family. [S2][S3]
02 · Three different meanings of safety and security
Our engineering interpretation: a low purchase price becomes meaningful only after the required output and remaining risks are defined. No actual price advantage has been established for this case.
| Area | The real question | Relevant evidence |
|---|---|---|
| Work and flight safety | Is the mission acceptable within its defined conditions? | Approved operating conditions, staff qualifications and test records |
| Data security | Who can read or change originals, locations and reports? | Data flows, access rights, change history and tested transfer paths |
| Continuity | Can the job continue if a device or service fails? | Restore tests, fallback procedures and documented dependencies |
Weather resistance does not establish data security. A claim about encryption on one radio link does not establish protection of every subsequent copy. One successful mission does not establish that its records can be recovered.
03 · The historical configuration is incomplete
| Component | Historical evidence | Unanswered question |
|---|---|---|
| Aircraft / payload | M300 RTK / H20T [S1] | Individual units, hardware and firmware revisions |
| Control | Smartcontroller in the retailer account [S1] | App version, user roles and local storage |
| Analysis and delivery | No complete system inventory in the reviewed sources | Analysis software, export format, recipients and deletion periods |
| Purchase and maintenance | No invoice or complete contract obtained | Price, scope, replacement equipment and response time |
Historical company names are retained to identify the sources. They do not establish present ownership, fleet composition or supply availability.
04 · What could be lost in a credible worst case
The following are our conditional scenarios for a comparable job, not allegations of an EnerTrans incident. Red identifies a potentially serious condition, not a calculated probability.
| Required condition | Possible consequence | Check before operational use |
|---|---|---|
| High impact: inspection data reaches an unapproved recipient | Asset images and findings require an investigation and a review of sharing permissions. | Trace every export and sharing step using synthetic data. |
| High impact: reports can no longer be matched to originals | An incorrect finding could affect a maintenance decision. A grid outage would require further errors and failure of additional safeguards. | Sample the chain from asset ID through capture, editing and approval. |
| High impact: the only copy becomes unavailable | Some or all inspection work must be repeated; access, weather and staffing may extend the delay. | Demonstrate restoration on a separate system. |
| High impact: access survives the end of a contract | A former project account can still read or alter records. | Check roles, expiry dates and permission withdrawal. |
These conditions are not nationality-specific. The reviewed case reports establish neither data theft nor the absence of all risk.
05 · Keep later warnings in their own time frame
The January 2024 CISA/FBI publication addresses general risks from Chinese-manufactured UAS to critical infrastructure, including data transfers, updates and connected components. It does not investigate this Swiss case. [S4]
Here it provides a later review lens, not evidence of an incident in 2020 or a Swiss procurement determination. Likewise, present-day privacy features cannot substitute for checking the historical software configuration.
06 · The missing numbers behind a cost comparison
A technical testimonial does not replace an invoice. For this project, the transaction price, actual labor per inspection and any quantified security loss have not been established. All remain UNKNOWN.
| Cost block | Records needed | Decision supported |
|---|---|---|
| Acquisition | Contract covering camera, software, training and maintenance | Compare like-for-like scope |
| Routine work | Preparation, travel, capture, analysis and sign-off | Cost per accepted result rather than per flight minute |
| Rework | Cause, extra hours and remobilization | Separate quality problems from security incidents |
| Dependencies | Export options, fallback process and recovery time | Estimate switching and interruption costs |
Our proposed calculation is: cost per accepted inspection = (allocated acquisition cost + operations + validation + actual rework) / number of accepted inspections. Hypothetical damage belongs in separate stress cases. Without defensible probabilities, do not compute an expected loss.
07 · Who should supply which evidence
This is our proposed responsibility map for a comparable engagement, not a description of the historical contracts.
| Role | Evidence to provide | Acceptance point |
|---|---|---|
| Asset owner | Data classification, sharing rules and technical criteria | A sample finding is technically traceable and understandable. |
| Flight provider / integrator | Approved configuration and capture process | A representative dataset meets the agreed quality criteria. |
| IT / security specialist | Checked storage, access and transfer paths | Test data can be traced from receipt through deletion. |
| Maintenance provider | Device replacement and media-handling procedures | Residual data is checked before a device leaves custody. |
One supplier may perform several roles, but the evidence remains distinct. Replacing a motor or enclosure alone does not answer questions about the analysis workstation, accounts or onward sharing.
08 · Start with model, task and problem
An initial inquiry needs the existing model, known versions, task and a specific problem such as uncertain data destinations, missing originals or an untested recovery process. Do not initially send asset coordinates, flight logs, credentials or confidential imagery.
Open the existing inquiry form
Reference: UAV-RISK-CH-GRID-004. The link does not automatically fill context. A German form version and acceptance by a specialist are not confirmed. Naming a company implies neither a partnership nor direct delivery of an inquiry to that company.
Current purchase prices and supply terms belong in a separate, not-yet-published article. This historical review is not a present-day purchase recommendation.
Sources and limits
S1 is a retailer interview. S2 and S3 are related manufacturer accounts with different publication dates, not independent test reports. S4 is later general US guidance. Checked 2026-10-01. We did not test the aircraft or its historical data flows.
Related research
Japan power-line inspection · 2021 · English · Brazil solar inspection · English