About

Skyborne Flight Briefing is designed to organise flight preparation, source material, calculations, and notes in one structured workflow.

Briefing data is saved locally in your browser when using the normal Save button. Optional Cloud Sync can be used separately when you want to transfer or back up a briefing temporarily across devices.

This tool is a briefing aid only. It does not replace official Skyborne procedures, aircraft documents, instructor guidance, or pilot-in-command judgement.

Skyborne Flight Briefing was designed and built from the ground up as a custom web application. The interface, workflow, and briefing logic were developed iteratively with assistance from GPT-5.5 and Codex.

The application is built with a modern React / Next.js stack, managed with npm, and deployed through Vercel. The live production site is served from the custom domain preflightbriefing.co.uk, with the original Vercel domain retained as a redirect for older links.

The app uses a local-first storage model. Normal Save stores briefing data in the user’s browser so a briefing can be resumed on the same device without requiring a login. This keeps the core workflow fast, simple, and independent of an account system.

Optional accountless Cloud Sync is provided for cross-device use. A user can generate a secure sync link or QR code, save the active briefing to cloud storage, and then load it on another device. This is designed for the practical briefing workflow of preparing on a laptop and continuing on an iPad or another device.

Cloud Sync uses Supabase for temporary briefing storage. Briefing data is stored as structured JSON, while supported uploaded files are stored separately in Supabase Storage. This avoids embedding large PDFs or images directly inside the briefing data.

Supported synced files include the NOTAM PIB PDF, F215/F214 weather chart images, Mass & Balance images, Flight Performance images, and Climb Gradient Calculations images. Local browser storage remains available, and Cloud Sync does not replace the normal Save button.

The sync system is accountless by design. Instead of usernames and passwords, access is controlled by a secure sync link/token. Anyone with the valid link can access that temporary cloud copy, so users should treat the link as sensitive. Cloud copies are temporary, can be manually deleted, and are intended as a short-lived handover mechanism rather than long-term document storage.

The application also includes QR-code handoff, optional email delivery of sync links through Resend, custom sender-domain authentication, and a private Supabase Storage bucket for supported synced uploads.

The project was created to combine a traditional pre-flight briefing workflow with modern web tooling, keeping the focus on structure, speed, and operational clarity.

Designed and developed by Caleb Ellis.