The paper techlog, replaced. Not reinvented.

Your paper techlog has a row. So does ChockOps, with the same fields:

• Departure and arrival ICAO
• BLOCK OFF, TAKE-OFF, LANDING, BLOCK ON, in UTC
• Landings
• Hour-meter reading (G1000 counter today; see the type library below for Hobbs and tach)
• Flight rules V / I / Y / Z (V is the default)
• Fuel at departure, fuel used, fuel at arrival, plus uplift in litres and US gallons
• Oil added, TKS (level, status, refill), O2 (pressure, status, refill)
• PIC, second crew member, passengers, remarks

Two ways to enter it. Open the flight before departure and close it after landing, or enter the whole row at once. An aircraft has at most one open flight.

The new row starts with the previous arrival as departure, fuel at departure as the previous arrival plus this row’s uplift (recalculated as you type), the same oil text, flight rules and you as PIC. TKS and O2 show the previous value greyed out and must be touched at closing. An unread value cannot slip through. Carried fields are marked “from previous”.

Blocking errors

Times out of order, fuel above tank capacity, a counter that goes backwards, missing required fields at closing.

Warnings you must confirm

• Hour meter vs time. The hour-meter delta does not match block, flight or engine time by more than 0.2 h.
• Fuel. Fuel used, the tank difference and the fuel-flow record disagree by more than 2 USG.
• Positioning. Departure is not the last arrival. (“Unlogged positioning flight?”)

Refuel detection. If fuel at departure is more than 2 USG above the previous arrival, the app proposes the missing uplift and flags “full tanks”.

The G1000 shows total time in service to 0.1 h. ChockOps models the hidden fraction from your past readings and tells you what the meter should read after this flight, with a probability. If the meter jumped (a maintenance run, a reset), it says so.

• TTAF
• Total landings
• Engine hours, separate from flight time, from an offset or from engine-run minutes
• Prop hours, with an offset after a prop change

Every maintenance item draws on these.

Open a flight and ChockOps checks: open defects, deferred defects you have not acknowledged, overdue maintenance, expired certificates, expired deferrals. Anything found is a red full-screen warning. You can still fly (the app does not ground your aircraft; your CAMO and your judgement do), but you must acknowledge. The acknowledgement is audited and the owner and maintenance role are notified.

• You can edit your own row for 24 hours after closing. Then it locks.
• Only an admin can change a locked row, and a reason is mandatory.
• Nothing is deleted. A voided row keeps its sequence number and drops out of the counters.
• Every change goes to the audit log with a before/after diff.

Close the row and the techlog sheet goes out by email as a PDF that looks like the paper one: A4 landscape, the same columns, a “Next inspection TTAF / NOT LATER THAN” header. The old house rule “send a photo of the sheet to the group” is retired. A report variant adds totals, the due list and open defects. English or Hungarian.

ChockOps installs as an app. Writes go into an outbox and sync when you are back online. If someone closed a row while you were offline, you get a rebase flow with the carry-forward recalculated, and version conflicts are shown side by side. Your G1000 track draws on a map on the entry.