DGCA 7-Year Flight Log Retention for Indian Drone Operators

TL;DR: Commercial drone operators in India are required to retain flight logs for seven years under the DGCA Digital Sky / NPNT framework. The retention has to be tamper-evident, include the NPNT signature and geo-fence alert trail, and be producible for audit by the DGCA, the Bureau of Civil Aviation Security, or insurance assessors. As of 2026, BVLOS operations in the three approved corridors (Ladakh minerals, Telangana pharma, Andhra Pradesh coastal) layer additional per-flight audit obligations. This post walks through what the rules actually say, what a compliant log set looks like, and how to organise retention before an audit shows up. Regulatory specifics evolve; consult the DGCA Digital Sky portal and a qualified aviation legal advisor for binding interpretation. Information current as of June 2026.

The legal frame that mandates retention

India’s drone regulatory stack has three relevant layers for log retention:

• Drone Rules 2021 — the parent regulation under the Aircraft Act. Establishes the operator-permit regime and references the Digital Sky platform.
• NPNT (No Permission, No Takeoff) — the technical compliance protocol requiring every flight to be pre-authorised by a Permission Artefact and the resulting flight log to carry a cryptographic signature.
• Digital Sky + eGCA — the DGCA platform layer. Digital Sky handles airspace permissions and NPNT authorisation; eGCA (rolled out from July 2025) handles operator registration, type certification, and Remote Pilot Certificate management.

For commercial operators (Drone Operator Permit holders), the practical retention obligation under this stack is seven years of flight logs, signed and complete, available for DGCA audit on demand.

What "a retained log" actually has to contain

A retained flight log for compliance purposes is not just the raw .bin file from the autopilot. The full record needs to include:

• The raw autopilot log (.bin for ArduPilot, .ulg for PX4, or .tlog for telemetry-only records).
• The NPNT Permission Artefact issued by Digital Sky for the flight — the pre-authorisation document.
• The signed flight log artefact as required by the NPNT compliance test suite for the specific autopilot stack.
• Geo-fence breach alerts if any — the Drone Rules require these to be retained with the flight record.
• Pilot identity — the Remote Pilot Certificate number of the operator-in-command.
• Aircraft identity — the eGCA UIN of the airframe used.

Storing only the autopilot log without the permission artefact and signature wrapper is not compliant; an auditor needs to be able to verify the flight was authorised, that the log corresponds to that authorisation, and that the file hasn’t been altered.

BVLOS corridor additions (2026)

If your operation flies in one of the three approved BVLOS corridors as of 2026 — Ladakh (minerals survey), Telangana (pharma delivery), or Andhra Pradesh (coastal monitoring) — additional per-flight records are required by the corridor-specific approval terms:

• Live UTM-2 telemetry capture for the duration of the BVLOS leg.
• Communication-link health metrics (RAD and RSSI messages on the autopilot side; ground-station telemetry quality on the GCS side).
• Failsafe trigger and resolution events with timestamps matching the corridor’s situational-awareness platform.
• Crew duty-time records aligned with the pilot of record.

Additional state-level corridors (Telangana, Uttarakhand, Gujarat for industrial delivery; West Bengal for medical delivery) follow the same general framework with state-specific procedural elements. Always check current DGCA notification before commencing operations.

Setting up a compliant retention workflow

1. One canonical store per operator. Centralise raw logs, permission artefacts, and signed wrappers in one durable storage tier (S3 with object lock, Azure Blob with immutable policies, on-prem WORM tape, or equivalent). The seven-year window starts at the flight date.
2. Index by flight ID. Every record needs to be retrievable by date, pilot, aircraft, and permission-artefact ID. An auditor will ask for "all flights by aircraft X in March 2025" or "the log for permission artefact Y"; you need to produce it within hours.
3. Tamper-evident integrity. Cryptographic hash of the raw log stored with the record. Periodic re-hash to detect bit-rot in cold storage.
4. Access control. Operators handling pilot personal information also fall under the Digital Personal Data Protection Act 2023; pilot identity records in the log retention store need access logging.
5. Annual integrity sample. Pull ten random records from the archive each year and verify they parse correctly, hash matches, and permission artefact is locatable. Catches a slow archive failure before an audit does.

Penalties and audit triggers

Under the Drone Rules 2021, an operator that cannot produce required records on demand can face penalties up to ₹1,00,000 under section 10A of the Aircraft Act framework. The Draft Civil Drone (Promotion and Regulation) Bill 2025, currently under consultation, proposes stiffer penalties including imprisonment up to three years for unregistered operation. Audits are not random — they are usually triggered by an incident report, an insurance claim, a complaint, or a periodic permit renewal check.

What the autopilot log itself contributes to compliance

Beyond the regulatory wrapper, the autopilot log carries the information that demonstrates the operation was conducted safely:

• MODE message transitions showing the flight stayed within the planned mode envelope.
• BARO.Alt, POS.Lat, POS.Lng showing the aircraft stayed within the permitted geofence.
• ERR messages showing failsafes triggered correctly when they fired.
• Battery (BAT) and motor (RCOU) traces showing the aircraft was within mechanical and power envelope.
• RAD and RSSI showing communications integrity (especially for BVLOS).

An auditor reviewing a routine record samples these fields against the permission artefact’s parameters — the geofence, altitude limit, and timing window. The signed log is what proves nothing was modified between flight and storage.

Privacy considerations under DPDP 2023

Flight logs that include identifiable pilot information or that capture personally-identifying ground content (camera frames over private property, for example) fall partially under the Digital Personal Data Protection Act 2023. Storage of these records still satisfies the seven-year DGCA mandate, but the privacy layer adds: access logging, data-subject request handling for pilot records, and a documented retention policy that explains why the records are kept and for how long. The two obligations coexist — one mandates retention, the other mandates accountable storage.

How LogHat fits

The LogHat platform stores every uploaded log in a private Azure Blob container with a unique flight identifier, generates a downloadable forensic PDF that includes the per-flight envelope summary, and surfaces the per-flight metadata (mode transitions, failsafes, geo-fence events) in a structured form suitable for retention indexing. The platform itself is operated by Technit Space and Aero Works Pvt Ltd, an Indian entity, so the data residency story for Indian operators is direct — the data sits in the AzureIndia region. We do not yet handle the NPNT permission-artefact wrapping or the cryptographic signing layer; that part of the compliance workflow continues to depend on the operator’s NPNT-compliant autopilot stack and Digital Sky integration. For end-to-end audit-ready storage, treat LogHat as the analytics and forensic layer; pair it with a dedicated NPNT compliance solution for the regulatory wrapper.

A practical checklist before next audit

1. Confirm raw logs for the last seven years are retrievable by date.
2. Confirm the NPNT permission artefact and signed wrapper for each flight are paired with the raw log.
3. Sample ten random records and verify they parse, hash, and reference an existing permission artefact.
4. Confirm pilot Remote Pilot Certificate numbers and aircraft UINs are stored with each flight.
5. Confirm geo-fence breach alerts (if any) are stored.
6. Confirm access logs to the retention store exist (DPDP 2023 layer).
7. Document the retention policy as a one-pager: what is stored, where, for how long, who has access, and the audit-response procedure. This is the document an auditor will ask for first.

When LogHat helps — and when it doesn’t

LogHat provides the analytics, the forensic PDF, the structured metadata, and Indian-region storage. We do not provide DGCA Digital Sky integration, NPNT permission artefact handling, or legal advice. For the regulatory wrapper, retain a compliance partner familiar with current DGCA practice. For technical log analysis, retention indexing, and audit-ready forensic reports, that’s what we exist to do.