Flying breakdown
Launch methods
Uses the same date range as Flying breakdown.
Flight logbook
| Date | Time | Aircraft | Role | Other pilot | Duration | Launch | Notes / review |
|---|
Launch failure types
Confirmed classifications only · stacked P1 and P2 counts
Flights awaiting review
SPL exercises taught
Flights recorded as instructional PIC with selected SPL syllabus exercises. Each bar is split into non-overlapping periods: most recent 1 year, 1–3 years ago and 3–9 years ago. All periods are relative to today.
Aircraft register
Register aircraft, seat count and trigraph. Aircraft are listed as My glider(s), Club, then Privately owned. Changing ownership never reclassifies existing flights.
Add or update aircraft
Import weekly CSV
Upload a CSV in the same format as your club's weekly flight summary. Only rows containing your configured name are imported. Previewing or importing never changes the original file.
Pilot name variations (optional)
Add common misspellings or alternative names used in club CSVs. One name per line. These names will match your flights but will not rewrite the original P1/P2 names.
Restore or reset
Google Drive automatic backup
Connect your personal Google account to store logbook snapshots in a visible MyFlights Backups folder in My Drive. Google authorisation requires a hosted HTTPS site and a Google OAuth web client ID; it cannot work from a downloaded file opened locally.
On connection, saves trigger a debounced cloud backup. The app keeps a current snapshot, plus one snapshot per day and per month. Attachments are not included yet. The app retries pending changes when reopened and connected; Android cannot guarantee background uploads after the browser closes.
CAA recency
Evidence date checks (not compliance decisions)
Planned modules
SFCL.155 launch-method recency · SFCL.160 SPL and TMG recency · SFCL.360 FI(S) recency.
CAA Evidence Register
Record medical documents, refresher training, flights with examiners and other evidence. Choose a photograph, take one with your Android camera, or attach a document. Completion dates and evidence types can later be interrogated against CAA requirements.
For the prototype, files stay in this browser's device storage (not Google Drive). A JSON backup exports evidence details but not the attached file contents. Keep your originals safe.
Evidence history
| Date completed (event) | Category | Activity | Person / issuer | Attachment | Actions |
|---|
Archived instructor-flight evidence
Historical evidence and attachments are retained; linked flights stay in the logbook.
| Date completed | Activity | Instructor | Attachment | Actions |
|---|
Prototype v1.4 · Live records remain browser-local. Google Drive backup requires configuration and does not synchronise live records. Export a manual backup before changing browsers or clearing site data. Do not use as your sole official logbook.