One owner, one calendar, three aircraft, and a rotating cast of 1099 remote pilots is a business until Friday afternoon—then it is five spreadsheets arguing about who was PIC, whose COI expired, and which job still needs a payout. Drone team seats are not a vanity feature. They are how a multi-pilot shop keeps the week assignable without turning every dispatch into a group text.
This is a Pilot Ledger Field Work post about ops for shops that hire contractors and employees side by side. It is not tax advice, employment-law advice, or a waitlist pitch. Soft CTA only: run jobs and crew in one place at Pilot Ledger.
The real problem is not “more pilots”
Solo Part 107 work fails gracefully. You know who was PIC because it was you. The second you add a second remote pilot—especially a 1099 contractor who also flies for someone else—the failure mode changes. The client asks for the certificate number of the person who flew Thursday. The insurer asks whether that person was named on the policy. Payroll (or accounts payable) asks whether the hours match the invoice. Nobody can answer from memory at scale.
Spreadsheet chaos usually looks like this:
- A Google Sheet for “available this week”
- A shared drive folder of COIs with filenames like `final_v3.pdf`
- A group chat where job assignments live and die
- A separate payout sheet that never matches the job board
- A calendar that shows the site but not the PIC
That stack works until two pilots claim the same pad, a contractor’s certificate renews mid-month, or a client wants the named PIC on the deliverable package. Then you rebuild the week from texts.
1099 contractors vs W-2 seats (ops view, not legal theater)
Shops mix labor models. Treat the labels as ops roles, not as a substitute for counsel.
1099 contractors often bring their own aircraft, their own schedule friction, and a shorter relationship. You still need them on the job record: name, certificate number, aircraft if they fly theirs, insurance if your contract requires it, and a clear PIC assignment for every sortie. Do not pretend a contractor is “just a camera operator” on a Part 107 job. Someone is remote PIC. Write the name.
W-2 seats (employees or long-term crew on your payroll) usually mean your aircraft, your maintenance board, and your recurring schedule. Seats still need the same flight packet fields: who flew, which serial, which authorization, which client job. The difference is continuity—seats show up on next week’s roster without a new SOW—and liability language your counsel already negotiated.
Either way, the shop’s system of record should not care about the tax form first. It should care about assignment: this job, this date, this PIC, this aircraft, this insurance state, this payout status. The 1099 vs W-2 distinction matters for contracting and payroll. It should not create two incompatible calendars.
Shared calendar that names a PIC
A shared calendar that only shows “Site A — Thursday” is a rumor. A useful multi-pilot calendar shows:
- Client / job name and address or pin
- Window (not just “AM”) and weather/access notes
- Assigned remote PIC (human name, not “crew”)
- Aircraft / payload planned
- Status: proposed, accepted, flown, scrubbed, invoiced
When a contractor accepts a seat on a job, acceptance should update the same board the owner uses. Side DMs are how double-books happen. If two people can edit the sheet, you do not have a source of truth—you have a race condition.
PIC is not optional decoration. Under Part 107, the remote pilot in command is a specific person for the operation. If your board cannot answer “who was PIC on the Tuesday roof,” you do not have team ops. You have a hope that someone remembers.
Insurance certs as a gate, not a folder
Multi-pilot shops bleed time chasing certificates of insurance. Put the gate on assignment, not on Friday panic:
- Required COI on file for contractors who fly under your contract terms
- Named insured / additional insured language your client requires, if any
- Expiration date visible on the pilot’s seat record
- Block or warn on assignment when the cert is missing or expired
You are not the underwriter. You are the dispatcher. The goal is to stop sending a pilot whose paperwork you cannot show if the GC asks at the gate. Store the PDF against the person (or the company entity), not in a folder named `insurance_new`.
Aircraft liability, payload riders, and “own aircraft vs company aircraft” belong in the same conversation. A 1099 who flies their own airframe may need different paper than a W-2 seat on your serial. Capture the rule once; apply it every time you assign.
Job assignment without the group-chat shuffle
Good assignment is boring:
- Job created with scope, deliverables, and site constraints
- Pilot seat offered with date, rate or payout rule, and PIC expectation
- Pilot accepts or declines in the system
- Prep packet attached (access, airspace notes, client contacts)
- Flight logged against the same job
- Deliverables and payout tied to the same ID
Skip any of those and you recreate spreadsheet archaeology. Especially skip “we’ll figure payout later.” Later is when the contractor has three other gigs and your AP queue is a mystery novel.
For shops that mix mapping, inspection, and photo work, tag the job type on assignment. A thermal roof PIC is not automatically the right seat for a stockpile volume day. Skill tags on seats beat tribal knowledge in the owner’s head.
Payouts that match the job, not the vibe
Contractors get paid when the shop can prove the work. Tie payout to the job record: accepted assignment, flown status, deliverable checklist, and any holdbacks you already wrote into the SOW. Do not invent a second “hours” sheet that disagrees with the calendar.
Clear fields help:
- Agreed rate (day, job, or acre—whatever you contracted)
- Expenses if allowed
- Status: pending flight, pending deliverable, ready to pay, paid
- Payment reference once sent
W-2 seats still need job costing even when payroll is separate. If you cannot see which jobs ate which crew hours, your profitable week is a guess.
What “team seats” should mean in software
When you evaluate ops software for a multi-pilot shop, ignore vanity dashboards. Ask whether drone team seats give you:
- People records with certificate numbers, roles (1099 / W-2), and document expirations
- A shared job calendar with named PIC assignment
- Acceptance workflow so owners are not the only people who can schedule
- Job packets that survive a handoff between pilots
- Payout or cost tracking keyed to the same job ID
- Export when you leave—because a seat system you cannot leave is another trap
Pilot Ledger is aimed at commercial drone shops that have outgrown a solo inbox and a color-coded Sheet. Start from Pilot Ledger or pricing when the roster, the jobs, and the payouts should stop living in parallel universes.
Practical checklist for this week
Before the next contractor:
- One roster with name, certificate number, labor type, and COI expiration
- One calendar where every booked job has a named PIC
- One acceptance path that does not require a phone call
- One payout status per job
- One place for scrub notes so weather days do not orphan deposits
Spreadsheet chaos is what happens when the people model and the job model never meet. Put them in the same system, name the PIC every time, and the Friday argument gets shorter.