Typical scenario

Gaps appear in unmanned aircraft logs after a component replacement

If error messages and missing records appear after replacing a component in an unmanned aircraft system, timing alone does not establish causation. Analysis may require comparing equipment condition, configuration versions and the origin of the logs.

What needs to be clarified

The task could be to examine which technical circumstances the available data support and which remain hypotheses.

Materials to prepare

  • Original system and controller logs with a description of how files were obtained.
  • Component documents, version details and configuration change records.
  • Repair history, condition photographs and a description of the event.

What to compare

  • Whether logs relate to the specific device and period.
  • Consistency of times, versions and message sequence.
  • Effect of data gaps on checking the proposed cause.

Possible outcome of the analysis

A possible output is a reconciled chronology of records, an account of discrepancies and a list of additional data for testing technical hypotheses.

Limits of the conclusions

Incomplete logs may prevent identification of the failure cause; the analysis does not imply an unapproved flight, establish airworthiness or replace authorisation or certification procedures.