Flight Logs & Compliance

Capture Flight Records in Colony Core

Colony Core supports structured flight logging tied to jobs and equipment records:

1. Open your flight log after the mission from mobile or desktop
2. Record the operational details that matter:
   • Flight duration and location
   • Aircraft, pilot, and battery used
   • Operational notes, incidents, or conditions
   • Linked job or site reference
   • Attachments or supporting documentation as needed
3. Link the record to the correct job and equipment history
4. Export in standard formats such as PDF or CSV when needed

Manual Flight Log Entry

Manual entry remains the primary beta workflow for flight logging:

1. Click "+ New Flight Log"
2. Fill in:
   • Date and time
   • Duration (minutes)
   • Pilot and crew members
   • Drone used (serial number)
   • Location (takeoff point)
   • Altitude and distance
   • Weather conditions
   • Linked job (required for compliance)
3. Save. Can be exported in standard formats such as PDF or CSV.

FAA Compliance (Part 107)

Colony Core structures the fields operators commonly need for Part 107 documentation:

• Pilot certification: Copy of Part 107 cert on file
• Flight duration: Logged in a consistent record format
• Airspace: Notes and authorizations can be attached to flight records
• Crew members: Visual observer, ground crew logged
• Conditions: Weather, visibility, or safety notes can be recorded when needed
• Incident reports: Near-miss or accident documentation

Export Flight Logs for Audits

When the FAA asks for records:

1. Go to Flights → Export
2. Choose:
   • Date range (e.g., last 30 days)
   • Format: PDF or CSV
   • Filter by pilot, drone, or job type
3. Export the format that best fits your review, audit, or insurance workflow
4. Share exported records with clients, insurers, or regulators as needed

Maintenance & Battery Tracking

Linked logs support equipment and maintenance tracking:

• Battery cycle count: Tracked through linked equipment records
• Total flight hours: Summed across logged usage
• Maintenance due: Alerts can be based on configured service intervals
• Replacement history: Log when batteries/props are replaced