A platform that already speaks your language.
Operating bases. Augments. 1099s. Cross-division manning. High ops tempo with tails spread across a continent. Customer contract lines that change monthly. You don't need another generic SaaS tool — you need software that was designed to operate on this mission from day one.
The shape of your ops, already modeled.
FOG's data model wasn't drawn from scratch. It mirrors how a contract adversary air company actually operates. If any of this sounds familiar, you're in the right place.
Dozens of operating bases
Multiple forward operating bases, each with its own DO, host-base relationship, host-specific forms, and weather picture. FOG treats location as a first-class entity, not a free-text field.
Augments & cross-division
Pilots rotate across locations and divisions weekly. FOG tracks who is augmenting where, approves cross-division requests, and keeps augments in their actual assigned location — not stuck in a generic "unassigned" bucket.
1099 contractors, W-2 employees
Two very different default-availability models. FOG handles both natively: W-2s default available, 1099s default unavailable and opt into the days they'll support. No custom fields required.
Multi-division organizations
Division-aware permissions. Division-aware manning reports. Cross-division augment flows. Executives see the whole picture; DOs see their division; locations see their own base.
Contract-tempo maintenance
Discrepancies captured from the flight log that caused them. Delayed gripes tracked to closure. MEL items with expiration dates. Work orders tied to aircraft and tail history — not just a generic ticketing queue.
Customer-ready reporting
End-of-month reports your customer will actually accept: hours by mission code, by aircraft, by location, by pilot. Export to PDF and spreadsheet without re-keying a single number.
Your world, already in the database.
No more bending the platform. FOG's entities map directly to how your ops actually run.
| What you have | What it maps to in FOG | What that means for you |
|---|---|---|
| Forward operating locations | Location with ICAO, color, host-base metadata | Division-aware, location-scoped views across every module |
| Pilot roster | User with role, division, location, 1099/W-2, qualifications | No custom-field gymnastics; your data shape is the data shape |
| Augment assignments | AugmentAssignment per week / pilot / location | Manning gantt shows who's covering what — and where they came from |
| Cross-division support | CrossDivisionRequest with approval chain | Nothing moves without the right signature, audit-logged |
| Daily GOs and sorties | ScheduleEvent → Sortie | Drag-and-drop sortie building with pilot, aircraft, mission code, fuel config |
| Fleet and maintenance | Aircraft · Discrepancy · MelItem | Live status board, writeups from the flight log, delayed-gripe tracking |
| Currency & exams | CurrencyRule · ExamSubmission | Live currency table. Missed exam = red. No more month-end surprise. |
Born inside the adversary air workflow.
FOG wasn't conceived in a conference room. It was built by a pilot flying adversary air, between GOs and briefs, to solve problems on the operation the tool-vendors never heard of. The goal has never been to become a generic aviation SaaS. It's to become the system adversary air operators reach for first.
If you run operating bases, augments, 1099 crews, and a customer that demands monthly hour reports — FOG was designed around you.
See the featuresA natural path into government flying units.
The adversary air market is where FOG cut its teeth. The ops tempo and workflow overlap with military flying units is not incidental — it's a feature. Same nouns. Same approval chains. Same currency logic.
Our roadmap includes a compliance track for DoD and federal customers: audit-logging, CUI markings in the UI, SSO via SAML/OIDC, field-level encryption for sensitive PII, and a path toward CMMC / FedRAMP alignment. We will not hand-wave this. If your authorizing official asks a hard question, we'll give you a hard answer.
Talk to the team- ·Audit logging on every mutation — already live
- ·CUI markings component set — already live
- ·SSO (SAML, OIDC) — planned
- ·Field-level encryption of sensitive PII — planned
- ·CMMC / FedRAMP alignment work — design partners welcome
Statuses are stated plainly. Nothing on this page is a claim of current certification.
See FOG on your ops.
Bring your location list, your division structure, and your current tool stack. We'll show you what the switch looks like.