Your own ops desk, from the navlog to a confirmed handling

This is the whole flow as it runs in the app today, for a trip of one or more legs.

1. 01

   Create the trip and import the plan.

   Drop a ForeFlight navlog PDF, a Garmin .fpl or a .gpx route, or enter the legs by hand.

2. 02

   Legs and stops are built.

   Each stop gets a purpose (a fuel stop when the turnaround is three hours or less, otherwise a stay), the fuel you request and a handler. The aircraft’s departure airport is a stop too, so its handler can be told when you leave.

3. 03

   Every airport is researched.

   The AI reads the web for each ICAO and fills an airport profile with sources and a confidence. You approve the fields you trust.

4. 04

   The trip is checked.

   Rules first (night, opening hours, restrictions, turnaround, fuel, handling, people), then the AI’s own warnings and questions. You answer the questions; the answers go into the mails.

5. 05

   Who do we write to?

   Per stop, ChockOps proposes recipients with a reason. Tick the ones you want and, if you like, add a line for the AI: “ask about hangar space”.

6. 06

   The mails are drafted.

   Arrival, handling and PPR requests for the stops you land at; a departure notice for the handler where the aircraft is parked. Each one is a draft in its own thread.

7. 07

   You approve and send, one by one.

   Edit the text, the recipients and the CC. Send asks for a confirmation. Nothing leaves without it.

8. 08

   Replies come back to the thread.

   Matched by mail headers, or by subject and sender when a handler’s system drops them. The AI summarises each reply and pulls out the facts.

9. 09

   Follow-up.

   Copy the booking reference and slot onto the stop, answer a question with the drafted reply, send a reminder where nobody answered, or send an update when the plan changes.

ForeFlight navlog PDF (AI structured reading), Garmin .fpl and .gpx (deterministic), or manual entry. Legs and stops are built: a stop is a fuel stop if the turnaround is three hours or less, otherwise a stay. Requested fuel and handler per stop. A fuel suggestion per leg, rounded up to 5 litres.

Per ICAO the AI searches and reads the web, from the AIP aerodrome pages to the airport’s and the handlers’ own sites, and records what it found, field by field, each with its source and a high, medium or low confidence:

• opening and ATS hours, as published and as UTC windows
• PPR rules, handling (required or not, who provides it), slot and customs / immigration requirements, with the Schengen status of the country
• fuel types, fees notes, VFR entry, frequencies, daily restrictions and training notes
• ops, handler and fuel contacts, only when a source prints them

You approve fields. Later research never overwrites an approved field; it offers a diff. Unapproved facts go into the mails as questions (“please confirm that…”), never as statements.

Deterministic rules: night from the sun position, opening hours, daily restrictions, turnaround, fuel, handling, a missing PIC or people. Then the AI adds its own warnings and questions, such as customs outside Schengen or a fuel type that may not be available.

For every stop ChockOps proposes recipients from the airport profile and says why: the handler you selected covers handling, PPR and fuel; without a handler, the airport’s ops office; at the departure airport, the handler where the aircraft is parked. Other handlers and fuel contacts are offered as alternatives, and an address that is not on a source is marked. Drafts are made only for the recipients you tick. A new mail to anyone, any time, works the same way.

• Arrival, handling and PPR request per stop: the aircraft, the flight, the ETA in UTC and local time, the persons on board, the fuel request, and numbered requests from the airport profile and your answers.
• Departure notice to the handler where the aircraft is parked: the ETD, the destination, the return if planned, the aircraft ready for departure, how to settle the invoice.
• Slots and permissions are asked for inside the arrival and handling mail, as the airport profile requires. ChockOps does not book slots through an airport’s slot system.
• Your approval on every mail: you edit the text and the recipients, and Send asks you to confirm. The mail goes out with your signature.

The trip has a mail tab like an inbox: one thread per airport or handler, grouped by stop, each with a status: draft, awaiting reply, confirmed, action needed, declined. Replies are matched by mail headers, or by subject and sender when the headers are missing; anything ambiguous waits in the inbox for you to assign. The AI classifies each reply as confirmed, quote, question or declined and pulls out the booking reference, the slot, times, prices, frequencies and the deadline. You copy them onto the stop with a click. When a verified partner asks something the trip can answer, the AI drafts the reply; you send it.

You get a notification when a reply needs you (a question, a quote, a refusal); a plain confirmation just updates the thread. The trip is readable offline.

A thread that has waited too long for an answer, or whose arrival is close, is flagged; the reminder button drafts a short, polite follow-up in the same thread. When the ETA, the people or anything else changes, “Send an update” drafts a mail that states only what changed, even after the trip is closed, for a cancellation.