Part 137 · Operations & fleet
Ops board
A daily ops board tracks the day's work across the ag fleet — which aircraft is flying, who's assigned, and what's scheduled — so the operation runs from one shared screen instead of a clipboard that resets every morning. Every entry is captured with an actor and timestamp on the platform audit trail, which matters when an operation has to show what it flew and when. It's an operations record, not a crop-mapping or target-spraying tool.
Launching the first quarter of 2027.
Illustrative — every screen reflects your own data.
Who it's for
Ag aviation operators and chief pilots who run the day's work across the fleet and need one shared board — which aircraft is flying, who's assigned, what's scheduled — instead of a clipboard rebuilt from memory each morning.
What it replaces
The daily clipboard that resets every morning and the operations record kept by hand, neither of which leaves an actor-and-timestamp trail of what flew and when.
What ops board gives you
- Daily ops board across the ag fleet — flying, assigned, scheduled
- Every entry captured with an actor and timestamp
- An operations record, not a crop-mapping or target-spraying tool
One shared board for the ag fleet's day
As planned, the day's work across the ag fleet would run off one shared board — which aircraft is flying, who's assigned, and what's scheduled — so the operation reads from a single screen instead of a clipboard that gets wiped and rebuilt from memory each morning. The intent is that an aircraft and crew are assigned to a job and posted to the board, and state is updated as work progresses, so the whole operation sees the same picture.
- Daily ops board across the ag fleet — flying, assigned, scheduled
- One shared screen instead of a clipboard rebuilt each morning
- State updated as work progresses, read by the whole operation
An auditable operations record — not a mapping tool
This is built as an operations record: every entry on the board would be captured with an actor and timestamp on the platform audit trail, so when an operation has to show what it flew and when, the answer is on the record rather than reconstructed from clipboards. It is deliberately not a crop-mapping or target-spraying tool, and it does not produce as-applied or as-covered application maps.
- Every entry captured with an actor and timestamp
- Show what flew and when without rebuilding from clipboards
- An operations record, not a crop-mapping or target-spraying tool
How an operator uses this
An ag operator runs the day off one shared board — which aircraft is flying, who's assigned, and what's scheduled — instead of a clipboard that gets wiped and rebuilt from memory each morning. Every entry is captured with an actor and timestamp on the platform audit trail, so when the operation has to show what it flew and when, the answer is on the record. It tracks the operation; it does not produce as-applied or as-covered application maps.
Illustrative — every screen reflects what's in your own data, nothing more.
How it works
Ops board, step by step
Open the ops board to see the ag fleet's day — flying, assigned, and scheduled.
Assign an aircraft and crew to a job and post it to the shared board.
Update state as work progresses so the whole operation reads from one screen.
Rely on the actor + timestamp audit trail to show what flew and when.
Questions
Ops board — frequently asked
Does the ops board produce application maps?
No. It's an operations record — which aircraft flew, who was assigned, and when — not an as-applied or as-covered application-mapping tool. Deep agronomic analytics and grower-handoff maps are out of scope.
Is the day's activity auditable?
Yes. Every entry on the board is captured with an actor and timestamp on the platform audit trail, so an operation can show what it flew and when without reconstructing it from clipboards.
Every Part 137 workspace also includes the platform-wide backbone — logbook, credentials, compliance, reporting, and audit trail.
See the backboneSee ops board on your operation.
It's part of the Part 137 workspace. Request a demo or join the waitlist.