WingX shows the green dot. FileFlo holds the signed record.
This isn't FileFlo versus WingX. Keep WingX as your Part 135 charter operations surface: scheduling, dispatch release, crew duty time, trip quoting, and the currency status the chief pilot reads before every leg. FileFlo is a different layer, the compliance document evidence binder the FAA Principal Operations Inspector pulls during Part 135 surveillance: the §135.21 GOM file, the signed §135.293 / §135.297 competency records, the §135.63 records of work, and the §135.443 airworthiness records behind it. WingX shows the green dot. FileFlo holds the signed record behind it.
$299/mo flat · Unlimited aircraft · No sales call
One runs the dispatch. One survives the surveillance.
WingX is the charter operations surface
It runs daily scheduling, crew assignment, duty time and rest tracking, dispatch release, trip quoting, and flight following, and shows the chief pilot whether a tail and crew are releasable. It is genuinely good at this. Keep using it.
FileFlo is the compliance evidence layer
It is the destination for the completed documents: the §135.21 GOM with version history, the signed §135.293 / §135.297 competency records, the §135.63 records of work, and the §135.443 airworthiness records, all AI-classified per crewmember and tail, retention-tracked, and produced as the one-click POI-ready binder.
Who wins for what.
The honest answer for most Part 135 charter operators: keep WingX for the daily charter-ops + scheduling + dispatch + crew duty time control surface, and add FileFlo for the compliance document evidence layer the FAA POI pulls.
FileFlo wins for
- Compliance document evidence binder for FAA POI surveillance (8900.1 Vol 3)
- 14 CFR §135.21 GOM file with version history + POI correspondence
- 14 CFR §135.293 signed pilot competency check records per crewmember
- 14 CFR §135.297 instrument proficiency check records (6-month currency)
- 14 CFR §135.63 records of work binder (crewmember + tail + date range)
- 14 CFR §135.443 airworthiness check records + §43.9 entries
- AI document classification across 600+ aviation document types
- Flat $299/mo unlimited aircraft, no per-aircraft inflation
- 5-day self-serve trial, live in minutes, no implementation
WingX wins for
- Part 135 charter daily operations control surface
- Aircraft scheduling + crew assignment + dispatch release
- Crew duty time + rest tracking under §135.267 flight-time limits
- Trip quoting + customer dispatch release workflow
- Currency status visibility: green/red dot for chief pilot
- Flight following + real-time aircraft status
- Maintenance status integration for dispatch release decision
FileFlo vs. WingX, feature by feature.
Based on publicly available WingX charter-ops materials, customer reports, and FileFlo product as of June 4, 2026.
| Feature | FileFlo$299/mo · unlimited aircraft | WingX~$50-$250/aircraft/mo |
|---|---|---|
Part 135 charter dispatch + scheduling + crew duty time | Not in scope; holds the resulting compliance records | Core competency: daily Part 135 operator control surface |
Compliance document evidence platform (AI-classified binder) | 600+ doc types AI-classified per crewmember + tail | Operator-surface tracking, not document evidence storage |
14 CFR §135.21 General Operations Manual (GOM) version control + POI binder | Holds + version-tracks GOM revisions + POI correspondence | Does not hold GOM document or revision history |
14 CFR §135.293 pilot competency check records (signed record-of-work) | Holds signed §135.293 record per crewmember + aircraft type | Shows currency status; does not hold the signed record |
14 CFR §135.297 instrument proficiency check records | Holds signed §135.297 record + 6-month currency tracking | Shows currency status; does not hold the signed record |
14 CFR §135.63 records of work (crewmember + aircraft + training) | §135.63 binder organized by crewmember + tail + date range | Operational records only; does not hold §135.63 binder |
14 CFR §135.443 airworthiness check record (signed) | Holds signed §135.443 inspection record + RTS sign-off | Shows next-due airworthiness as dispatch status (visibility) |
14 CFR §43.9 maintenance record entries + §43.7 RTS sign-offs | Holds signed §43.9 + §43.7 documents per tail | Operator-surface visibility, not document storage |
Part 135 trip quoting + customer dispatch release | Not in scope: operational quoting + customer-facing | Charter-specific trip quoting + customer dispatch workflow |
FAA POI surveillance binder (8900.1 Vol 3) one-click PDF | POI-ready binder organized by CFR section + crewmember | Operator must export + assemble binder manually |
Multi-regulation coverage (FAA + DOT + OSHA + EPA ground ops) | 14 CFR + 49 CFR + 29 CFR + 40 CFR all in one platform | Part 135 charter ops only: single regulation focus |
Pricing model | $299/mo flat, unlimited aircraft + users | ~$50-$250/aircraft/mo (per-aircraft + per-module quote) |
Free trial (no sales call) | 5-day full access, no card | Demo + custom quote + onboarding process |
Implementation timeline | Self-serve · live in 30-60 minutes | Multi-week onboarding + Part 135 cert + crew data migration |
Use case fit | Part 135 POI/PMI document evidence binder for surveillance | Part 135 daily charter ops + dispatch + crew currency surface |
WingX prices on a per-aircraft, per-module subscription model that varies by Part 135 fleet size, module selection, and operator tier. Range cited from public sources and operator reports; verify directly with WingX for an exact quote.
One flat price. No per-aircraft math.
FileFlo is one flat price for the compliance document evidence layer regardless of aircraft count. WingX prices per-aircraft, per-module; the math escalates with every aircraft and every module the operator adds.
Contact WingX for an exact per-aircraft quote based on Part 135 fleet size, module selection, and operator tier.
The pricing comparison is not apples-to-apples. WingX is a Part 135 charter operations control surface; FileFlo is a compliance document evidence platform. The right operating model is WingX for the charter-ops + scheduling + dispatch surface, and FileFlo for the §135.21 / §135.63 / §135.293 / §135.443 audit binder, with a combined cost typically lower than enterprise Part 135 compliance platforms alone.
Platform definition.
FileFlo is a compliance document intelligence platform that operates as an evidence layer alongside a Part 135 charter operations system such as WingX. It does not schedule aircraft, assign crews, track duty time, or release dispatch; those are operational-control functions WingX performs well. Instead, FileFlo receives the completed compliance documents a Part 135 charter operator generates (the 14 CFR §135.21 General Operations Manual and its revision chain, the signed §135.293 competency check records, the §135.297 instrument proficiency check records, the §135.63 records of work, the §135.443 airworthiness check records, and the §43.9 maintenance entries from the contract Part 145 station), classifies each against its governing CFR section, tracks retention, and generates an inspector-format audit binder on demand for FAA Principal Operations Inspector (POI) surveillance.
The distinction matters because WingX is an operational-control surface: it is optimized for the real-time dispatch decision: which tail and which crew are releasable for the next leg, reading currency dates against the calendar and surfacing them as a green or red dot. WingX can tell the dispatcher a pilot is current; what the certificate holder must also produce, under §135.21 and §135.63, is the document evidence: the signed competency check record, the GOM revision the POI acknowledged, the records of work. FileFlo adds that compliance-evidence layer without disturbing the operations surface beside it.
Why a green dot isn't a signed record.
Federal Part 135 rules do not ask whether the dispatch board showed a pilot current; they ask whether the certificate holder kept the required manual current and can produce the signed record on demand. Under 14 CFR §135.21, every certificate holder (outside the §135.21(b) basic-list and single-pilot exceptions) must maintain a current General Operations Manual reflecting the OpSpecs issued under §135.5, revised whenever a procedure changes, accessible to crewmembers, and available to the FAA Principal Operations Inspector on request during surveillance governed by FAA Order 8900.1 Volume 3 Chapter 18. Under §135.293, each pilot in command must pass a written or oral test and a competency check within the preceding 12 calendar months; under §135.297, an instrument proficiency check within the preceding 6 calendar months. An operations surface can render a perfect green dot from operator-entered dates and still leave the operator exposed, because a dispatch-board status has no concept of a signed record-of-work bearing the check airman's name, the date, the items tested, and the result.
The recordkeeping and airworthiness rules complete the picture. Under §135.63, the certificate holder must retain records of each flight, the load manifest, the airworthiness release, and the duty and flight time required to comply with §135.267, retained for the periods specified and produced to the FAA on request. Under §135.443, no aircraft may be operated unless it has had a §135.419 approved-program inspection within the preceding limits or, off-program, the Part 91 inspections including §91.409 annual or 100-hour, applicable Airworthiness Directives under Part 39, and life-limited part status under §91.417. WingX surfaces the next-due airworthiness item as a dispatch status; the signed §135.443 record, the §43.9 maintenance entry, and the §43.7 return-to-service sign-off from the contract Part 145 station are the document evidence the FAA Principal Maintenance Inspector pulls during a Volume 6 surveillance event.
This is the gap FileFlo closes. Rather than ask an operator to abandon the operations surface that runs daily charter dispatch, FileFlo receives the completed documents, maps each to the CFR section it satisfies, version-tracks the §135.21 GOM, tracks retention against §135.63 windows, and assembles the POI surveillance binder in the format the agency expects. WingX shows the green dot; FileFlo holds the signed record behind it. Civil-penalty exposure under 49 U.S.C. §46301 runs up to $37,377 per violation per day for 2026, which is why the document binder, not the dispatch board, determines how a surveillance event ends.
Built by an operator, against the rules themselves.
Chad Griffith, Founder & CEO of FileFlo, built FileFlo's rule packs against the actual surveyor, inspector, and safety-investigator protocols, not against a generic "compliance" abstraction. Each regulator's taxonomy maps documents to the exact CFR section that demands them, which is why FileFlo can sit alongside a charter operations system like WingX and still speak the language a Part 135 POI uses. FileFlo's connectors are read-only by design: the platform reads what you already have and never becomes a place your team has to migrate into.
Quick answers.
Last reviewed June 4, 2026.
What is WingX, and who is it built for in 2026?
WingX is the charter-operations management platform built specifically for Part 135 on-demand charter operators, fractional operators, and air taxi providers: the operator surface that combines aircraft scheduling, crew duty time tracking, dispatch, trip quoting, flight following, and maintenance status into one Part 135 operational control workflow. WingX has historically focused on the Part 135 charter operator pain point of running a multi-aircraft, multi-crew, multi-base charter operation where every flight needs FAA Part 135 dispatch release, the chief pilot needs to know every crewmember currency status under §135.293 and §135.297, and the director of operations needs the aircraft maintenance status under §135.443 reconciled against the next dispatch. WingX competes against industry charter-ops platforms like Avianis, Leon, BART, and other Part 135 charter-specific operators surfaces. WingX is NOT a maintenance tracking platform competing against CAMP Systems or Veryon; its Part 135 maintenance status integration is operator-visibility-oriented, not airworthiness-engineering depth. WingX is the dispatch + scheduling + crew currency operator surface where the Part 135 charter director runs daily operations. FileFlo is a different layer entirely: the compliance document evidence binder the FAA Principal Operations Inspector (POI) pulls during Part 135 surveillance under FAA Order 8900.1 Volume 3: the §135.21 manual currency file, the §135.63 records of work, the §135.293 competency check records, and the §135.443 airworthiness check records as document evidence, not operator-surface tracking data.
How much does WingX cost vs FileFlo?
WingX prices on a per-aircraft subscription model tailored to Part 135 charter operator fleet size and module scope. Public industry reporting and operator-side disclosures put WingX pricing at roughly $50-$250 per aircraft per month depending on aircraft count, module selection (basic scheduling, full dispatch + crew currency, trip quoting, flight following, maintenance integration), and whether the Part 135 certificate holder is a single-aircraft on-demand operator or a 15+ aircraft fractional / managed-fleet provider. A 3-aircraft Part 135 charter operator on a mid-tier WingX configuration typically pays $150-$200 per aircraft per month ($5,400-$7,200 per year for the 3-aircraft fleet). A 10-aircraft Part 135 charter operator on full WingX dispatch + crew + trip quoting typically pays $100-$175 per aircraft per month ($12,000-$21,000 per year). A 20-aircraft fractional operator running WingX as the operator control center typically pays $75-$150 per aircraft per month ($18,000-$36,000 per year). FileFlo is a flat $299 per month or $2,990 per year: unlimited aircraft, unlimited users, all compliance features. The pricing comparison is NOT a substitution comparison. WingX sells the Part 135 charter operator scheduling + dispatch + crew currency control surface; FileFlo sells the Part 135 compliance document evidence binder the FAA POI pulls. The right operating model is keep WingX for the charter ops + scheduling + dispatch workflow AND add FileFlo for the §135.21 / §135.63 / §135.293 / §135.443 document binder. Verify WingX pricing directly during the WingX sales process; FileFlo pricing is locked at getfileflo.com/pricing.
Does FileFlo replace the Part 135 dispatch + crew scheduling workflow WingX runs every day?
No, and the Part 135 charter operator pairing is exactly the use case where this distinction matters most. WingX is the charter operations control surface where the director of operations and chief pilot run daily flight scheduling, crew assignment, duty time and rest tracking, dispatch release under §135.83 and §135.85, trip quoting, flight following, and the maintenance status visibility that determines whether N-number 123AB can be released for the next dispatch. That operational workflow is the real-time operator surface: it runs hot all day, it integrates with crew currency under §135.293 and §135.297, and it is the single pane of glass the Part 135 charter director uses for daily control. FileFlo does NOT attempt to replace that workflow. FileFlo is the destination for the completed compliance documents: the signed §135.293 competency check record, the §135.297 instrument proficiency check record, the §135.21 manual currency stamp, the §135.63 crewmember records of work, and the §135.443 airworthiness check record, all AI-classified, retention-tracked, and produced as the one-click FAA-POI-ready binder during a Part 135 surveillance event. The combined operating model is: WingX for the Part 135 daily operations + dispatch + crew currency control surface + FileFlo for the compliance document evidence binder the POI pulls during surveillance.
Can FileFlo hold the §135.21 General Operations Manual (GOM) currency file the WingX director of ops needs at FAA renewal?
Yes, and this is FileFlo's strongest use case for WingX-running Part 135 charter operators. 14 CFR §135.21 requires every Part 135 certificate holder (except those single-pilot operators and basic-list operators meeting the §135.21(b) exception criteria) to maintain a current GOM containing the procedures, instructions, and information necessary to operate the Part 135 certificate. The GOM must reflect the OpSpecs the FAA issues under §135.5, must be revised whenever any policy, procedure, or operational program changes, must be carried aboard the aircraft (or accessible) and made available to crewmembers, and must be available to the FAA Principal Operations Inspector (POI) on request during surveillance. FAA Order 8900.1 Volume 3 Chapter 18 governs POI surveillance of OpSpecs and GOM currency. WingX is an operator-surface platform: it does not hold the GOM document itself, it does not version-track GOM revisions, and it does not hold the §135.21 revision history the POI asks for during a surveillance event. The Part 135 charter operator who walks into surveillance with the WingX dispatch logs but cannot produce the current-revision GOM with version history, revision dates, and POI-acknowledged revision letters is the operator who picks up a §135.21 finding. FileFlo holds the §135.21 GOM file, version-tracks every revision, holds the POI-acknowledgment correspondence, and produces the FAA-ready §135.21 binder in one click, with the OpSpecs cross-referenced, the OpSpecs A013/A014/A025/etc. authorization status linked, and the revision chain readable to the POI.
Does FileFlo hold the §135.293 crew currency records the chief pilot needs to dispatch a WingX-scheduled flight?
Yes, and this is where the WingX + FileFlo pairing closes the most operational risk. 14 CFR §135.293 requires every Part 135 certificate holder to ensure each pilot in command has passed a written or oral test on FAR Part 91 and Part 135 regulations, on the aircraft type, on the operating limitations, on the emergency procedures, and on the relevant systems within the preceding 12 calendar months under §135.293(a), and a competency check in the aircraft (or approved simulator) within the preceding 12 calendar months under §135.293(b). 14 CFR §135.297 separately requires the pilot in command of an IFR flight to have passed an instrument proficiency check within the preceding 6 calendar months. WingX shows the chief pilot whether a crewmember is current (green dot, red dot) by reading the operator-entered currency dates against the calendar. WingX does NOT hold the signed §135.293 competency check record itself. The signed record-of-work is the document the POI pulls during a §135.293 surveillance event under FAA Order 8900.1 Volume 3. The Part 135 charter operator who has the WingX green dot but cannot produce the signed §135.293 record (name of check airman, date of check, aircraft type tested, items tested, satisfactory/unsatisfactory results, signature) is the operator who picks up a §135.293 finding and (in repeat-finding cases) the §135.5 certificate enforcement action. FileFlo holds the §135.293 competency check record itself, organized by crewmember and aircraft type, AI-classified, expiration-tracked, and produced as the one-click §135.293 binder for POI surveillance. The same logic applies to §135.297 instrument proficiency checks, §135.299 line checks, and §135.351 recurrent training records.
What about the §135.443 airworthiness check records WingX shows as a dispatch status?
Same pairing logic applies. 14 CFR §135.443 requires every Part 135 certificate holder to ensure no person operates an aircraft under Part 135 unless that aircraft has had a §135.419 approved aircraft inspection program inspection accomplished within the preceding time limits, or (for operators not on an approved program) the inspections required by Part 91, including §91.409 annual or 100-hour inspection, applicable Airworthiness Directives under Part 39, and life-limited part status under §91.417. WingX displays the next-due airworthiness items as a dispatch status: the green dot means N-number 123AB is releasable for the next flight, the red dot means it is grounded pending an inspection or AD. That operator visibility is real and it is the right place for the dispatcher to make a dispatch decision. WingX does NOT hold the signed §135.443 airworthiness check record itself, the §43.9 maintenance record entry establishing the inspection completion, the §43.7 return-to-service sign-off, or the Form 8130-3 Authorized Release Certificate for the installed replacement part. The signed records are document evidence the FAA Principal Maintenance Inspector (PMI) pulls during Part 135 maintenance surveillance under FAA Order 8900.1 Volume 6. FileFlo holds the §135.443 record file, the §43.9 maintenance record entries, the §43.7 RTS sign-offs, and the Form 8130-3 attachments, organized by aircraft tail, AI-classified, retention-tracked, and produced as the one-click §135.443 + §43.9 + §43.7 binder for PMI surveillance. WingX for the daily dispatch status; FileFlo for the FAA-investigator-ready document binder.
Keep WingX. Add the binder.
Build your first 14 CFR §135.21, §135.293, or §135.443 audit binder today, at a flat $299/mo, unlimited aircraft. 5-day free trial, no card, no sales call.
$299/mo · Unlimited aircraft · Cancel anytime