CrewSheet captures the panel at engine shutdown, extracts the flight data, validates it against the prior leg, and ships a signed aircraft log sheet, a ForeFlight Logbook CSV, and a CAMP Systems update. Built for Part 91 corporate flight departments and Part 135 charter operators with modern glass-cockpit turbine fleets.
As the crew secures the aircraft, the pilot monitoring lifts an iPad and frames the panel. CrewSheet accepts the post-flight panel image, an optional pre-flight reference, and the Hobbs meter. Shot through bright sun on a Pilatus PC-24 ramp, captured through cockpit glare on a winter morning — the adapter is trained for it.
Claude Sonnet 4.5 reads the photograph on AWS Bedrock with a panel-specific prompt cached at one-hour TTL. It returns flight time, fuel quantities, Hobbs, cycles, and engine N1 with a confidence number. The validation engine then runs eight rules across Hobbs continuity, fuel balance, time-in-service drift, and crew assignment before any data is committed.
The PIC signs. CrewSheet renders the aircraft log sheet to PDF, generates a ForeFlight Logbook CSV (one row per pilot-flight pair), and prepares a CAMP Systems update with airframe and engine totals rolled forward. The audit log records every state change with attribution — ready for the next FAA records review.
CrewSheet runs on a single-tenant AWS account dedicated to the operator. No shared databases, no third-party SaaS for the regulatory record. Compute is AWS Fargate behind CloudFront, vision is Claude Sonnet 4.5 on Bedrock, storage is KMS-encrypted S3, and the audit log is immutable.
“The first day we used it, the captain shut down, snapped the panel, and the log was signed before the lineman finished chocking the nosewheel. That has never happened before.”
Every output references the same finalized flight log, signed by the PIC. Amendments produce versioned successors; the audit log records who, when, and what changed.
Printable single-page sheet covering aircraft identity, route, times, fuel, crew, validations. Part 135 legs receive the 135.63(c) load-manifest block. Stored versioned in S3.
Conforms to the public Aircraft + Flights two-section template. One row per pilot-flight pair so multi-crew legs produce multiple rows. Imports cleanly into ForeFlight Web.
Airframe and engine totals rolled forward, cycles incremented, ready for the maintenance team's CAMP intake. Phase 2 will add a direct API push.
14 CFR 91.417 — Part 91 maintenance records: total time in service, life-limited parts, AD compliance.
14 CFR 135.63 — Part 135 recordkeeping: pilot records (12 months), load manifest (30 days).
14 CFR 135.439 — Part 135 maintenance records.
14 CFR 1.1 — Time in service: wheels-up to wheels-down. Not Hobbs. Not block time. CrewSheet keeps all three.
We're onboarding a small number of Part 91 and Part 135 operators flying the Pilatus PC-24 as Phase 1 design partners. Pilot pricing through the first 60 days.