Help Center

IOPS is a web platform for managing flight service requests between aircraft operators and ground handlers. It replaces the email threads, phone calls, and spreadsheets used to arrange handling, fuel, customs, permits, and transport for a trip.

An FSR is a single trip record: the aircraft, the itinerary, crew and passengers, and every ground service requested. Operators and handlers work from the same record, so status, changes, and messages stay in one place.

Aircraft operators who request services, handlers and FBOs who confirm and fulfill them, and the ground agents on a handler's team who carry out the work at the airport.

No. A handler can create and manage a trip in IOPS for an operator who still sends requests by email or phone. Travelers never need an account: passport details are collected through a secure one-time link.

No. IOPS runs in the browser on desktop and on your phone.

When a trip includes a Mexican airport, IOPS checks the aircraft against your blanket permits and tells you whether the trip is covered or a permit is needed. It also alerts you before a blanket permit expires.

IOPS builds the eAPIS manifest in ARINCDirect-compatible format from the crew and passenger data already on the trip, and checks that required fields are complete. You submit it through your ARINCDirect account.

Yes. Edits to a confirmed trip are recorded field by field, the handler is notified, and the handler acknowledges the change. Every edit is kept in the trip's log.

Passport numbers are encrypted with AES-256 in the database, passport photos are served only through time-limited links, and access is limited to the organizations working the trip.

A handler admin adds agents to their team, sets what each person can see, and assigns them to trips. Agents see only the trips assigned to them.