A quick primer on how WingbookHQ organises maintenance data for your organisation.
See an overview of any upcoming or overdue items, and whether or not these are grounding. You can also see open defects and a summary of any recent maintenance work. This page will show maintenance related to all aircraft in the organisation you have selected.
Example: Before releasing G-ABCD, open the dashboard to confirm no grounding items exist and spot that the 50-hour check is due in 3 hours, so you can schedule it before dispatch.
The tech log is now updated automatically every time a new flight is added, and the hours remaining until the next 50 hour check is automatically calculated and displayed (always based on flight time). You can use the “Reset 50 hours” button to start a new 50-hour cycle, and you can decide whether to display flight, brakes and/or tacho time in your organisation settings.
Example: Your aircraft has just completed its 50 hour check, so pressing the “Reset 50 hours” button starts a new section and resets the timer to 50 hours.
Create a library of tasks across your club—capture each inspection, AD, or checklist item once here, then assign the same task to multiple aircraft or schedules later. Store references, tolerances, and notes so engineers always see the same instructions.
Example: Build a “PA28 50‑hour check” task once with every step listed; when you add a new PA28 to the fleet the task is ready to assign without retyping anything.
Bundle library tasks into recurring schedules to match your CAMO or club programme. Each line can track against hours, cycles, landings, or calendar time, and Wingbook automatically forecasts when the next hit will occur.
Example: Assign the 50-hour task to each aircraft; once engineers log the event, Wingbook resets the schedule and will flag the task as the 50 hour mark approaches again.
Add components and set time or usage limits on them for tracking. Each component can monitor tacho hours, brakes hours, flight hours, landings, or calendar limits, and you can set warning thresholds so upcoming replacements surface on the dashboard.
Example: Add the ELT battery as a component with a 24-month interval so the system warns you a month before it expires.
Log maintenance work and tie it to any defects, recurring schedules, or components. Each event captures readings, engineer notes, CRS references, and documents, and you can reset the hours on any tied components while you save.
Example: When engineers complete the 50-hour check, add a maintenance event, link the 50-hour schedule, reset the hours on the propeller component, and include the CRS reference so everything updates together.
Raise and track defects, and set whether or not these are minor (advisory) or grounding items. Defects raised in tech log entries are automatically added here, and you can link them to maintenance events to capture the fix and close them out.
Example: If a tech log entry reports “Starboard NAV light inop,” it appears here as a defect—mark it as advisory and once the bulb is replaced in a maintenance event the defect closes automatically.