FileFlo vs. WingX:
WingX Runs the Part 135 Charter Operations Surface.
FileFlo Holds the Compliance Document Evidence.
WingX is the charter-operations management platform built specifically for Part 135 on-demand charter operators, fractional providers, and air taxi operators — the daily operator surface that combines aircraft scheduling, crew duty time tracking, dispatch release under §135.83 and §135.85, trip quoting, flight following, and the maintenance status visibility that determines whether a tail number is releasable for the next dispatch. WingX is the single pane of glass the Part 135 director of operations and chief pilot use for daily charter control. FileFlo is a different layer — the compliance document evidence platform the FAA Principal Operations Inspector (POI) pulls during Part 135 surveillance under FAA Order 8900.1 Volume 3: AI-classifying 600+ document types, holding the §135.21 General Operations Manual file with version history, the §135.63 records of work, the §135.293 + §135.297 crew competency records, and the §135.443 airworthiness check records as the one-click FAA-POI-ready audit binder. Together, not versus. Here is the honest side-by-side at a flat $299/mo.
Almost every Part 135 charter director of operations and chief pilot I have spoken with in the last twelve months has had some version of this conversation: "WingX runs our entire daily charter operation — scheduling, dispatch release, crew duty time, trip quoting, the chief pilot looks at WingX dashboards twenty times a day to know which tail and which crew are releasable for the next flight. The WingX charter-ops workflow is real and we are not going to switch off it. But during our last FAA POI surveillance under FAA Order 8900.1 Volume 3, the inspector asked for our §135.21 GOM revision history, the signed §135.293 competency check records for every pilot, and the §135.443 airworthiness check records reconciled against §43.9 maintenance entries — and none of that is really what WingX holds. WingX shows currency status as a green dot or red dot; the POI wants the signed record. Is there a software tool that closes the document binder gap without replacing what WingX already does well?" WingX is the Part 135 charter-specific operator control surface where the director of operations and the chief pilot run daily flight scheduling, crew assignment, duty time and rest tracking under 14 CFR Part 135, dispatch release, 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 14 CFR §135.293, and it is the single pane of glass the Part 135 charter director uses for daily control. FileFlo does not attempt to replace any of that — that is operator-surface tracking data, that is the daily dispatch workflow, and WingX is built specifically for the Part 135 charter use case. What FileFlo does is the next layer: the compliance document evidence binder under 14 CFR §135.21, 14 CFR §135.63, 14 CFR §135.443, and 14 CFR §43.9 — the document evidence file the FAA POI pulls during a Part 135 surveillance event. WingX shows the green dot; FileFlo holds the signed record behind it.
This page is not a takedown of WingX. The WingX Part 135 charter-operations workflow is built specifically for the on-demand charter use case — the trip quoting, the crewmember assignment against §135.293 currency, the dispatch release decision against §135.443 airworthiness status, the duty time + rest tracking that prevents a §135.267 flight-time-limitation finding — and that is genuinely the right operator surface for the daily Part 135 charter director. Operators who rely on WingX for daily scheduling, dispatch release, trip quoting, and crew duty time tracking should keep WingX. The honest question is whether WingX is also the right tool for the compliance document evidence binder the FAA POI pulls during an FAA Order 8900.1 Volume 3 surveillance event — and the answer for most Part 135 charter operators is that the document binder side of the workflow is underbuilt in WingX (because WingX is built for the operator surface, not the document archive) and is the specific gap FileFlo closes. The right operating model for most Part 135 charter operators is WingX for the charter-ops + scheduling + dispatch + crew duty time surface + FileFlo at $299/mo for the compliance document evidence layer. The two products are complements, not substitutes, and the combined operating cost is dramatically lower than the enterprise aviation compliance platform alternatives.
Quick Verdict
- 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
- 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
The honest answer for most Part 135 charter operators on WingX: keep WingX for the daily charter-ops + scheduling + dispatch + crew duty time control surface + add FileFlo at $299/mo for the compliance document evidence layer the FAA POI pulls. The two products are complements — WingX shows the green dot for dispatch, FileFlo holds the signed record behind it.
Feature-by-Feature Comparison
Based on publicly available WingX charter-ops materials, customer reports, and FileFlo product as of May 2026.
| Feature | FileFlo$299/mo · unlimited aircraft | WingX~$50-$250/aircraft/mo · per-module quote |
|---|---|---|
| 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 (scheduling, dispatch, crew currency, trip quoting, flight following, maintenance integration), and operator tier. Range cited from public sources and operator reports — verify directly with WingX for an exact quote.
Where Each Tool Sits Inside 14 CFR §135.21, §135.63, §135.293, §135.443, and §43.9
The Part 135 charter recordkeeping regulations map cleanly onto the right operating model. Here is who does what.
14 CFR §135.21 — Manual Requirements (GOM/GMM)
§135.21 requires every Part 135 certificate holder (except those qualifying for the §135.21(b) basic-list / single-pilot exception) to prepare and keep current a General Operations Manual (GOM) and (where applicable) a General Maintenance Manual (GMM) containing the procedures and instructions necessary to operate the Part 135 certificate. The GOM must reflect the OpSpecs issued under §135.5, must be revised whenever any procedure changes, must be carried aboard the aircraft or be accessible, and must be made available to the FAA POI on request. FAA Order 8900.1 Volume 3 Chapter 18 governs POI surveillance of OpSpecs and GOM currency. WingX is the daily operator surface — it does not hold the GOM document itself, it does not version-track GOM revisions, and it does not hold the POI-acknowledgment correspondence chain. FileFlo wins here cleanly for §135.21: holds the GOM file with full version history, AI-classifies every revision against the OpSpecs authorization referenced, links POI acknowledgments to the revision chain, and produces the §135.21 POI-surveillance-ready binder in one click.
14 CFR §135.293 — Pilot Initial and Recurrent Tests + Competency Checks
§135.293(a) 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. §135.293(b) requires a competency check in the aircraft (or approved simulator) within the preceding 12 calendar months. The chief pilot or POI surveillance event needs to see the signed record — name of the check airman, date of the check, aircraft type tested, items tested, satisfactory or unsatisfactory results, and signature. WingX shows the dispatcher and chief pilot a green dot or red dot derived from operator-entered currency dates — but the signed §135.293 record itself is the document evidence the POI pulls. FileFlo wins here cleanly for §135.293: holds the signed record per crewmember and aircraft type, AI-classified, expiration-tracked at 12 months, and produced as the one-click §135.293 binder for POI surveillance. The same logic applies to §135.297 instrument proficiency checks (6-month currency), §135.299 line checks, and §135.351 recurrent training.
14 CFR §135.63 — Recordkeeping Requirements
§135.63 requires every Part 135 certificate holder to keep at its principal business office (or other approved location) the records of: each flight, including the names of the crewmembers and their duty assignments; the load manifest for each flight under §135.63(c) showing aircraft identification, trip number, departure point, weight, names of passengers, and crewmembers; the airworthiness release or pilot certification of airworthy condition under §135.443; and the records of the duty time and flight time for each crewmember required to comply with §135.267. The records must be retained for the periods specified in §135.63(b) and made available to the FAA on request. WingX captures the live operational data — the trip number, the crew assignment, the duty time clock — but Part 135 recordkeeping requires the records to be retained as document evidence, not just live operator-surface state. FileFlo wins here for §135.63 retention: organizes records by crewmember, by aircraft tail, by date range, and by CFR section, AI-classified, and produced as the one-click §135.63 binder for POI surveillance organized to match the FAA Order 8900.1 Volume 3 inspector checklist.
14 CFR §135.443 — Airworthiness Check
§135.443 requires every Part 135 certificate holder to ensure no person operates an aircraft under Part 135 unless the aircraft has had an airworthiness check performed and signed off as required by §135.419 (approved aircraft inspection program) or — for operators not on an approved program — by the inspections required under 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 or red dot the dispatcher uses to release N-number 123AB for the next flight. That operator visibility is real and is the right place for the dispatch decision. WingX does NOT hold the signed §135.443 airworthiness check record itself, the underlying §43.9 maintenance record entry, the §43.7 return-to-service sign-off, or the Form 8130-3 Authorized Release Certificate for any replacement part installed. FileFlo wins here for §135.443 evidence: holds the signed §135.443 record, the §43.9 maintenance entry, the §43.7 RTS sign-off, and the Form 8130-3 attachment, AI-classified per aircraft tail, and produced as the one-click §135.443 binder for FAA Principal Maintenance Inspector (PMI) surveillance under FAA Order 8900.1 Volume 6. WingX for the dispatch-status visibility; FileFlo for the PMI document binder.
14 CFR §43.9 — Content, Form, and Disposition of Maintenance Records
§43.9 requires every person who performs maintenance, preventive maintenance, rebuilding, or alteration on an aircraft, airframe, engine, propeller, appliance, or component part to make an entry in the maintenance record containing: a description of the work performed, the date of completion, the name of the person performing the work, and (if maintenance is performed by a Part 145 repair station) the signature, certificate number, and kind of certificate held by the person approving the aircraft for return to service under §43.7. For a Part 135 charter operator that uses a Part 145 repair station for maintenance under contract, the §43.9 entry is the document evidence the FAA POI / PMI pulls during surveillance to reconcile against the §135.443 airworthiness check and the WingX dispatch status. WingX surfaces the maintenance status as live operator-visibility data; FileFlo holds the underlying §43.9 records, the §43.7 RTS sign-off, and (where applicable) the Form 8130-3 attachment — all AI-classified and produced as the one-click §43.9 binder for FAA surveillance. Civil-penalty exposure under 49 U.S.C. § 46301 runs up to $37,377 per violation per day for 2026 — a Part 135 surveillance event with §135.21 + §135.293 + §135.443 + §43.9 findings can compound into a six-figure civil penalty exposure for the certificate holder.
Real Pricing Comparison
FileFlo is one flat price for the compliance document evidence layer regardless of aircraft count. WingX prices per-aircraft, per-module across the scheduling, dispatch, crew currency, and trip quoting tiers. The math escalates with every aircraft + every WingX module the operator adds.
* Pricing range based on public WingX sales materials and operator reports across charter-ops tiers. 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 + FileFlo for the §135.21 / §135.63 / §135.293 / §135.443 audit binder” — combined cost typically lower than enterprise Part 135 compliance platforms alone.
When to Use Each (and When to Use Both)
Add FileFlo if you...
- Are a Part 135 charter operator whose POI surveillance pulls §135.21 GOM revisions and POI correspondence
- Need the signed §135.293 + §135.297 + §135.299 + §135.351 crew competency records — not just WingX currency status
- Need the §135.63 records of work binder organized by crewmember + tail + date for POI surveillance
- Need the §135.443 airworthiness check record + §43.9 entries + §43.7 RTS sign-offs reconciled for PMI surveillance
- Want AI to auto-classify 600+ aviation compliance documents — no manual filing
- Need cross-regulation coverage — FAA + DOT + OSHA + EPA for ground operations
- Need a one-click FAA-ready audit binder for POI / PMI / OPSS surveillance events
- Want unlimited aircraft seats without per-aircraft enterprise inflation
Keep WingX if you...
- Need the daily Part 135 charter operations control surface
- Need aircraft scheduling + crew assignment + dispatch release workflow
- Need crew duty time + rest tracking under §135.267 flight-time limitations
- Need trip quoting + customer dispatch release workflow
- Need real-time currency status visibility (green/red dot) for the chief pilot
- Need flight following + real-time aircraft status during charter ops
- Need maintenance status integration for dispatch release decisions
"We Added FileFlo to WingX Because..."
Real workflows Part 135 charter directors of operations and chief pilots describe after pairing FileFlo with WingX.
"I'm a director of operations at a 6-aircraft Part 135 on-demand charter operation. WingX runs our entire daily workflow — scheduling, dispatch release, crew duty time, trip quoting. The chief pilot looks at the WingX board twenty times a day. When the FAA POI showed up for surveillance under 8900.1 Volume 3, the first request was §135.21 GOM revision history with POI-acknowledgment correspondence going back two years, and the second request was the signed §135.293 competency check records for every PIC. WingX shows the green dot for currency status — that is genuinely useful for daily dispatch — but it does not hold the signed competency check record itself. We added FileFlo at $299/mo for the document binder. POI surveillance now closes in 90 minutes instead of three days, and our last surveillance had zero §135.21 or §135.293 findings."
"We're a 12-aircraft Part 135 charter operator on WingX with the full ops module — scheduling, dispatch, crew currency, trip quoting, flight following. WingX costs us about $18K a year for the Part 135 control surface and it is the right tool for daily ops; we are not switching off it. But our last POI surveillance pulled §135.63 records of work for every crewmember over a 24-month period, plus §135.443 airworthiness check records reconciled against §43.9 entries from our contract Part 145 repair station. WingX shows the live dispatch status — green or red — but it does not hold the §43.9 record from the repair station or the signed §135.443 check. We added FileFlo for the document evidence binder. Combined WingX + FileFlo annual spend is still less than the enterprise Part 135 compliance platforms quoted us, and we kept the operator-surface workflow that runs daily charter ops."
"I'm chief pilot at a Part 135 fractional operator. We use WingX for the operator surface because the trip quoting + crew assignment + duty time integration is genuinely good engineering for fractional charter ops. But the FAA POI surveillance is increasingly focused on §135.21 GOM currency + §135.293 competency check records + §135.297 instrument proficiency check records as the document evidence, and WingX is not built to hold the signed record. We added FileFlo for the §135.21 + §135.293 + §135.297 binder. Every signed check is AI-classified, organized by crewmember + aircraft type, expiration-tracked at 6 months for §135.297 and 12 months for §135.293. When the POI asks for a five-year-old §135.293 record for a specific PIC, I produce it in under 30 seconds. WingX runs the daily operator surface; FileFlo holds the proof the crew was current."
Frequently Asked Questions
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, 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.
Authored by Chad Griffith, Founder of FileFlo. Last reviewed 2026-05-31. Software perspective — comparing WingX (Part 135 charter operations control surface) and FileFlo as compliance software products. References: 14 CFR §135.21, 14 CFR §135.63, 14 CFR §135.293, 14 CFR §135.443, 14 CFR §43.9, 49 U.S.C. § 46301.
Add the FAA Part 135 Compliance Document Binder — At Flat $299/mo
5-day free trial. No credit card. No sales call. No multi-month onboarding. Build your first 14 CFR §135.21 or §135.293 or §135.443 audit binder today — at a fraction of enterprise Part 135 compliance platform pricing.
$299/mo · Unlimited aircraft · Cancel anytime · No implementation fees