DEDICATED RISK REVIEW 03 · JAPAN · HISTORICAL CASE / 2021

Power-line inspection across a strait.
A successful flight does not establish data security.

Before comparing aircraft prices, ask whether the inspection record can be trusted.

Published 2026-10-01 · v1.0.0 · Original case publication: 2021

This article revisits a historical demonstration. Present-day models, prices and supply terms belong in a separate article. We have not established that this equipment was bought cheaply or that this demonstration suffered a leak or compromise. The worst-case scenarios below are our conditional engineering analysis.

Frame your own requirement

01 · What the historical record establishes

DJI’s October 2021 account describes an Omishima branch-line demonstration involving Enecom, Chugoku Electric Power Transmission & Distribution and DJI JAPAN, using Matrice 300 RTK, Zenmuse H20T and DJI Terra. Chugoku refers here to a Japanese company. The manufacturer reports shorter working time; we do not treat that as independently verified performance. [S1][S2]

Enecom’s case page also describes power-line and tower imaging and route preparation. It is not a complete configuration record or security audit of this demonstration. [S3]

02 · A model name is not a reproducible configuration

Item	Evidence available here	Missing record
Aircraft, payload, software	M300 RTK / H20T / Terra in the historical account [S2]	Individual aircraft, hardware revision, firmware and software versions
Control and positioning	No complete configuration inventory obtained	Controller, app, RTK correction path and permissions
Storage and transfer	The case article does not establish the complete flow	Storage locations, external transfers, service copies and deletion records
Purchase terms	No historical invoice or transaction price obtained	Aircraft, payload, software, training and maintenance line items

Unknown does not mean absent, compromised or safe. Present-day product features must not be retroactively attributed to this 2021 configuration.

03 · The asset is more than the photograph

This is a checklist for a comparable workflow, not a reconstruction of the demonstration’s actual transfers. Check the aircraft, controller, analysis computer, recipients and maintenance providers individually.

Asset	Information that may remain	Question for the owner
Original imagery	Equipment appearance, location and capture time	Who can read it? Are originals separated from publication copies?
Routes and survey outputs	Flight paths and spatial relationships	Where are they stored, exported and versioned?
Analysis and reports	Suspected defects, decisions and reinspection targets	Can each finding be traced to the equipment ID and original? Who approved it?
Repair and disposal	Job data left on devices or media	Are outbound copies and returned devices checked?

04 · Worst cases require explicit conditions

Red identifies conditions with potentially serious consequences. It is not a probability forecast or a finding that a particular model was compromised.

Necessary condition	Credible worst-case consequence	Evidence to check first
High-impact condition: sensitive files reach an unapproved destination	Equipment information or defect locations reach an unintended recipient, requiring investigation, sharing suspension and reclassification	Destinations, sharing permissions, access records and data classification
High-impact condition: report changes cannot be checked against originals	A defect could be missed or unnecessary work ordered. Equipment failure would require additional conditions, including incorrect decisions and failures in maintenance safeguards	Originals, versions, change history and approvals
High-impact condition: only one device holds the job record	Failure, loss or compromise requires another survey, with weather and scheduling delaying recovery	Restore tests, separately held backups and an alternative work plan
High-impact condition: unverified changes enter operational use	Routes or analysis outputs cannot be revalidated, forcing a mission pause or deliverable review	Change approval, validation records and recovery procedures

These pathways are not exclusive to Chinese-made equipment. Nationality alone cannot establish whether a specific compromise occurred.

05 · A 2024 warning is not evidence of a 2021 incident

The 2024 CISA/FBI document is a general warning about Chinese-manufactured UAS and critical infrastructure. It discusses transfers, updates and connected equipment. It is neither an investigation of this Japanese demonstration nor a determination of Japanese procurement eligibility. [S4]

Our proposed check uses anonymized test data across capture, analysis, delivery and servicing. Turning off communications during a flight does not establish that later copying or sharing is prevented.

06 · The numbers missing from a claim of cheapness

The public material reviewed here does not establish the original purchase-price advantage, a breach loss or a quantified return on investment. A present-day used price would not substitute for the historical contract.

Cost category	Actual inputs required	Without records
Acquisition	Contract price, training, analysis environment, service agreement	UNKNOWN
Each job	Preparation, capture, analysis and review labor; subcontracting	UNKNOWN
Interruption and rework	Remobilization, repeat capture, restoration and additional review	UNKNOWN
Migration	Export, retraining, compatibility checks and old-media handling	UNKNOWN

Decision model: total cost = acquisition + routine operation + validation and administration + actual interruption and rework + migration. Keep hypothetical incident losses in a separate conditional stress case. Without defensible event probabilities, do not calculate an expected loss.

07 · Where the engineering barriers sit

Our engineering interpretation is that value lies in repeatable mission paths, interpretable images, traceable reports and procedures that survive changes, as well as aircraft assembly. Each needs a separate acceptance check.

Responsibility	Deliverable to request	Example acceptance check
Flight and integration	Mission conditions and approved configuration	Review test results within conditions set by the safety lead
Imaging and analysis	Image-quality criteria and sample report	Trace equipment IDs to originals and review interpretability
Information management	Data-flow map and access inventory	Trace synthetic data through storage, sharing and deletion
Maintenance and continuity	Configuration history and recovery procedure	Restore required records on another workstation

This is not a finding that the historical participants lacked these capabilities. It is a way to define responsibilities for a separate engagement.

08 · Start with your model, mission and problem

For an initial inquiry, state the model and known versions, the mission such as power-line inspection, and the problem—for example, unknown sharing destinations or untraceable originals. Do not initially send precise infrastructure coordinates, flight logs, credentials or sensitive imagery.

Open the existing inquiry form

This links to the existing form; article details are not automatically filled. Japanese form support and specialist acceptance have not been confirmed. Include reference “UAV-RISK-JP-POWER-003” if useful. This does not imply a partnership with, or direct delivery to, any company named in the article.

A separate current-procurement article is not yet published. Do not use this historical page as a current purchase recommendation.

Sources and limits

S1 and S2 are accounts of the same demonstration from the same manufacturer, not two independent validations. S3 is operator-authored case material. S4 is later general US government guidance. Checked 2026-10-01. This article is not a full republication, product certification or hands-on test.

Related research

Latest UAV public research · Sites

Japan rail inspection · Brazil solar inspection · English