Building a pilot-ops layer on phpVMS 7 (Confluence Air dev diary)

I run Confluence Air (CFE), a regional feeder out of KSUS. We’re on phpVMS 7, and for the last couple of months I’ve been building a custom module that sits in front of the stock pilot pages. We call it CFEnet. Sharing progress because some of you are solving the same problems.

The problem. Stock phpVMS treats a bid as the plan and a PIREP as the record, and nothing ties the two together over time. Pilots end up with stale bids, flights they meant to fly sitting next to flights they already flew, and no clean “here’s my week.”

What the module does so far (on our staging site):

  • Assignments. A pilot takes a flight for a specific date and a specific tail. That becomes a duty on their schedule. The module still creates the normal bid, so SimBrief and ACARS work as usual.
  • Find a Flight. Search returns only flights the pilot is eligible for, using core’s subfleet rules. Browsing and taking are separate steps, so nobody grabs a flight by accident.
  • Tail picker. Lists active aircraft in the eligible subfleets, hides any tail already on another duty that day, and shows each one’s last known position.
  • Automatic closure. When a PIREP is accepted, the module matches it to the duty and closes it. It matches on the flight’s business details, not the flight ID, because manual PIREPs don’t always carry one. If the PIREP is later rejected, the duty reopens. Every change is written to an append-only audit table.
  • Relinquish. A pilot can hand a flight back. It removes the bid and any unflown OFP in one step.
  • My Schedule and History. Current flight, next flight, upcoming list, and a history view with PIREP links.

Design rules I’ve held to. The module writes only to its own tables plus the standard bid. It doesn’t touch core tables or recreate anything phpVMS already does. Everything runs in UTC, with the pilot’s local time shown alongside.

Next up is a flight workspace: one page per flight with the summary, aircraft, dispatch/OFP through SimBrief, weather, and documents.

It isn’t on our production site yet. It goes there when the workspace is done and tested. Happy to answer questions on the approach.