Clear about what works.

FlytFlow is an initial working web platform. It is not yet a complete production flight-school system.

Working in this release

• Email/password school signup and login; tenant-scoped records, owner-managed team logins, linked instructor/student permissions, and role checks.
• Isolated fictional school with 12 aircraft, 15 instructors, and 75 students.
• Visual aircraft and instructor availability in local time, touch/drag time selection, and reservations with aircraft, instructor, and student conflict prevention.
• Entered grounding and currency checks; human-approved dispatch.
• Flight return with meter updates and invoice generation.
• Training evaluations, discrepancies, grounding reports, leads, CSV exports, and audit records.
• Responsive web workspace and Vector: an animated copilot with authorized record search and backend OpenAI integration (requires an active API connection).

Not connected or not yet implemented

• Square merchant activation and live payment acceptance testing remain pending. Platform membership checkout and admin access controls are implemented; student billing profiles, custom account payments, partial invoice payments and verified payment history are implemented. Each school must connect its own Square merchant. Refund reconciliation is supported; issuing refunds and accounting sync are not implemented.
• Live weather/NOTAM ingestion, notifications, calendar sync.
• Signed native iOS/Android app builds, device acceptance testing, TestFlight/store distribution, push notifications, and offline training synchronization. Native client source is implemented.
• Email invitations, email verification/recovery, advanced account administration and SaaS tenant support actions.
• Recurring/multi-aircraft reservations, drag-and-drop editing, waitlists, automatic rescheduling, and optimization.
• Validated Part 61/141 syllabi and regulatory record retention, digital signatures, endorsements, AD applicability, signed maintenance release, parts and work-order management.
• Backups/recovery drills, load testing, security audit, and operational acceptance by a flight school.

Demo transactions are simulated. Software record checks are not official weather briefings, airworthiness determinations, or operational approvals.