Record accurately
Users are responsible for entering and reviewing accurate information appropriate to their operation.
Flight Records & Compliance Boundaries
Colony Core can keep structured field history associated with the work it supported. This public page intentionally does not publish the complete field set, validation behavior, filters, exports, or record-management controls.
What to understand
Keep operational history connected to the work.
The record model is intended to support consistent organizational history. It is not represented as automatic proof of regulatory compliance.
Keep context connected
Where enabled, keep the field record associated with relevant job and equipment context so later review is easier.
Know the compliance boundary
The remote pilot and organization determine current regulatory requirements, retention needs, and what evidence is legally sufficient.
Protected implementation
Detailed record instructions belong inside authenticated product support.
The public site does not publish the full record schema, exact entry procedure, filtering model, export configuration, validation rules, status logic, or equipment-derived calculations. Those details can vary and provide unnecessary implementation disclosure.
Signed-in users should use their account support path or contact Colony Core for the current workflow.