Part 105 · Drop zone operations
Safety reporting
Capture safety reports and hazards as durable records, each logged with who reported it and when on the platform audit trail, so a report becomes something you can review and act on instead of a message that scrolls out of a group chat. It replaces safety reports lost in texts with no record they were ever raised.
Launching the first quarter of 2027.
Illustrative — every screen reflects your own data.
Who it's for
Drop zone staff and the safety officer who need a concern to become a durable record the DZ can review and act on, rather than a message that scrolls out of a group chat.
What it replaces
Safety reports lost in a group chat or text thread, with no record they were ever raised.
What safety reporting gives you
- Safety reports and hazards as durable records
- Each logged with who reported it and when
- Something you can review and act on, not a message in a group chat
Every safety report a durable, audit-trailed record
As planned, staff would file a safety report or hazard as its own durable record, with the audit trail logging who raised it and when, so a concern becomes something the drop zone can review and act on rather than a message that scrolls out of a group chat. The intent is that each report carries its own row, so nothing is lost and there's a record it was ever raised.
- Safety reports and hazards as durable records
- Each logged with who reported it and when
- Reviewed and acted on, not lost in a group chat
A reporting-and-record layer, not an auto-rating engine
This would be a reporting-and-record layer the staff review and act on, not a prescriptive safety-rating engine. The Part 105 layer itself wouldn't add skydiving-specific auto-rating; the platform's shared SMS surface is where the rule-based risk matrix and the computed fatigue-risk score (not a prediction) live. The reports are operator-kept records — not a filing to any authority and not jumper telemetry.
- A reporting-and-record layer you review and act on
- No skydiving-specific auto-rating in the Part 105 layer
- Operator-kept records — not a filing or telemetry feed
How an operator uses this
Staff capture safety reports and hazards as durable records, each logged with who raised it and when on the platform audit trail, so a concern becomes something the drop zone can review and act on rather than a message that scrolls out of a group chat. Each report carries its own row, so nothing gets lost and there's a record that it was ever raised. It's a reporting-and-record layer, not a prescriptive safety-rating engine.
Illustrative — every screen reflects what's in your own data, nothing more.
How it works
Safety reporting, step by step
File a safety report or hazard as its own durable record.
Let the audit trail log who reported it and when, automatically.
Review open reports as a list instead of digging through a group chat.
Act on a report and keep the trail of what was raised and addressed.
Questions
Safety reporting — frequently asked
What happens to a safety report after it's filed?
It becomes a durable record on its own row, logged with who reported it and when on the platform audit trail, so it can be reviewed and acted on — not lost in texts with no record it was ever raised.
Does it score or rate hazards automatically?
Safety reports and hazards are captured as durable, audit-trailed records you review and act on. The platform's shared SMS surface includes a rule-based risk matrix and a computed fatigue-risk score (not a prediction); the Part 105 layer itself doesn't add skydiving-specific auto-rating.
Every Part 105 workspace also includes the platform-wide backbone — logbook, credentials, compliance, reporting, and audit trail.
See the backboneSee safety reporting on your operation.
It's part of the Part 105 workspace. Request a demo or join the waitlist.