FileFlo vs. Avantext:
Avantext Distributes the OEM Technical Publications.
FileFlo Holds the Compliance Evidence Binder.
Avantext is an aviation document management platform built specifically for the storage, distribution, and revision tracking of OEM technical publications — maintenance manuals, illustrated parts catalogs, structural repair manuals, component maintenance manuals, wiring diagrams, and service bulletins — for Part 145 repair stations and Part 91 corporate flight departments. Avantext is the technical-pub library a mechanic searches every time a work order opens to find the current-revision procedure. FileFlo is a different layer — the compliance document evidence platform the FAA Principal Maintenance Inspector (PMI) pulls during Part 145 surveillance under FAA Order 8900.1 Volume 6: AI-classifying 600+ document types, holding the §145.211 Quality Control Manual file with version history, the §145.109 housing/facility records, the §145.219 work order + parts traceability binder, the §43.13 performance compliance evidence, the §43.9 maintenance entries, the §43.7 RTS sign-offs, and Form 8130-3 attachments as the one-click FAA-PMI-ready audit binder. Together, not versus. Here is the honest side-by-side at a flat $299/mo.
Almost every Part 145 repair station accountable manager and Part 91 corporate flight department maintenance director I have spoken with in the last twelve months has had some version of this conversation: "Avantext distributes our OEM technical publications — every mechanic searches the current-revision IPC, the current-revision maintenance manual, the current-revision component manual every time a work order opens. The Avantext tech-pub library is real, the OEM revision pipeline is genuinely integrated, and we are not going to switch off it. But during our last FAA PMI surveillance under 8900.1 Volume 6, the inspector asked for our §145.211 QCM revision history with FAA-acknowledgment correspondence going back five years, the §145.109 housing/facility tooling calibration records, and the §145.219 work order + parts traceability records reconciled against §43.9 maintenance entries and §43.7 RTS sign-offs. Avantext supplies the OEM manual the §43.13 entry cites — but it does not hold the signed §43.13 evidence, the §43.9 entry, the §43.7 sign-off, or the Form 8130-3 attachment for the installed part. Is there a software tool that closes the compliance evidence binder gap without replacing what Avantext already does well?" Avantext is the aviation technical publications distribution platform where the Part 145 mechanic and the Part 91 corp flight department maintenance director access the current-revision OEM data required under 14 CFR §43.13 for performance compliance — the methods, techniques, and practices prescribed in the current OEM maintenance manual or Instructions for Continued Airworthiness. That technical-pub workflow is the real-time mechanic surface — it runs every time a work order opens, it integrates with the OEM service-bulletin pipeline, and it is the single pane of glass the Part 145 quality control inspector uses to verify the work was performed against the current-rev data. FileFlo does not attempt to replace any of that — that is OEM technical-pub data, that is the daily mechanic workflow, and Avantext is built specifically for the aviation document management use case. What FileFlo does is the next layer: the compliance document evidence binder under 14 CFR §145.211, 14 CFR §145.109, 14 CFR §43.13, and (for Part 91 corp flight departments) 14 CFR §91.7 — the document evidence file the FAA PMI/POI pulls during a Part 145 or Part 91 surveillance event. Avantext supplies the OEM manual the §43.13 entry cites; FileFlo holds the signed §43.13 entry, the §43.9 record, the §43.7 sign-off, and the Form 8130-3 behind it.
This page is not a takedown of Avantext. The Avantext aviation document management workflow is built specifically for the OEM technical publications distribution use case — the revision-tracked maintenance manual the mechanic references for §43.13 performance compliance, the IPC the inspector uses to verify the correct part number, the service-bulletin pipeline that delivers OEM revisions as they issue — and that is genuinely the right tech-pub surface for the daily Part 145 mechanic and the Part 91 corp flight department maintenance director. Operators who rely on Avantext for daily OEM technical-pub access should keep Avantext. The honest question is whether Avantext is also the right tool for the compliance document evidence binder the FAA PMI/POI pulls during an FAA Order 8900.1 Volume 6 (or Volume 3) surveillance event — and the answer for most Part 145 stations and Part 91 corp flight departments is that the compliance-evidence side of the workflow is out of scope for Avantext (because Avantext is built for OEM tech-pub distribution, not the signed regulatory-compliance archive) and is the specific gap FileFlo closes. The right operating model for most Part 145 + Part 91 operators is Avantext for the OEM technical publications library + 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 PMI surveillance (8900.1 Vol 6)
- 14 CFR §145.211 QCM file with version history + FAA-ack correspondence
- 14 CFR §145.109 housing/facility records + tooling calibration evidence
- 14 CFR §145.219 work order + parts traceability records (2-yr retention)
- 14 CFR §43.13 signed performance compliance evidence citing manual rev
- 14 CFR §43.9 + §43.7 maintenance entry + RTS sign-off storage
- Form 8130-3 Authorized Release Certificate attachments per component
- Part 91 corp flight dept §91.7 / §91.417 / §91.403 airworthiness binder
- AI document classification across 600+ aviation compliance document types
- Flat $299/mo unlimited aircraft types — no per-OEM-library inflation
- 5-day self-serve trial — live in minutes, no implementation
- OEM aviation technical publications distribution library
- Maintenance manuals + IPCs + SRMs + CMMs + wiring diagrams
- OEM revision pipeline + service bulletin distribution
- Multi-aircraft-type technical-pub access for mechanics
- Current-revision OEM data sourcing for §43.13 compliance
- Searchable technical-pub library across OEM document corpus
- Tech-pub user access control for mechanic + inspector roles
The honest answer for most Part 145 / Part 91 operators on Avantext: keep Avantext for the OEM technical publications library mechanics search every day + add FileFlo at $299/mo for the compliance document evidence layer the FAA PMI pulls. The two products are complements — Avantext supplies the manual rev the §43.13 entry cites, FileFlo holds the signed §43.13 entry + §43.9 record + §43.7 sign-off + Form 8130-3 behind it.
Feature-by-Feature Comparison
Based on publicly available Avantext aviation document management materials, customer reports, and FileFlo product as of May 2026.
| Feature | FileFlo$299/mo · unlimited aircraft | AvantextEnterprise custom quote · OEM-library tiered |
|---|---|---|
| OEM technical publications library (maintenance manuals, IPCs, SRMs, CMMs, wiring diagrams) | Not in scope — holds the resulting compliance records, not OEM tech pubs | Core competency — aviation technical-pub distribution platform |
| OEM revision tracking + service bulletin distribution | Not in scope — relies on Avantext as upstream tech-pub source | OEM revision pipeline integration + bulletin distribution |
| Compliance document evidence platform (AI-classified binder) | 600+ doc types AI-classified per article + work order + tail | Technical-pub library — not signed-record document evidence storage |
| 14 CFR §145.211 Quality Control Manual (QCM) version control + PMI binder | Holds + version-tracks QCM revisions + FAA-acknowledgment correspondence | Does not hold §145.211 QCM document or revision history |
| 14 CFR §145.109 housing, facility, equipment + tooling records | Holds §145.109 facility records + tooling calibration evidence | Not in scope — OEM tech-pub library only |
| 14 CFR §145.219 work order + parts traceability recordkeeping (2-yr retention) | §145.219 binder organized by article + work order + tail | Technical-pub access only — does not hold §145.219 records |
| 14 CFR §43.13 performance compliance evidence (work performed per current-rev manual) | Holds signed §43.13 evidence citing Avantext-supplied manual revision | Supplies the manual — does not hold the signed compliance evidence |
| 14 CFR §43.9 maintenance record entries + §43.7 RTS sign-offs | Holds signed §43.9 + §43.7 documents per article + tail | Tech-pub source for the entry — not the signed entry itself |
| Form 8130-3 Authorized Release Certificate attachments | Holds Form 8130-3 per installed component, AI-classified | Not in scope — tech-pub library only |
| 14 CFR §91.7 / §91.417 Part 91 corp flight dept airworthiness records | Holds §91.7 / §91.417 / §91.403 / Part 39 AD binder per tail | OEM tech-pub access — not §91.7 airworthiness records storage |
| FAA PMI / POI surveillance binder (8900.1 Vol 6 / Vol 3) one-click PDF | PMI/POI-ready binder organized by CFR section + article + work order | Operator must export + assemble compliance binder manually |
| Multi-regulation coverage (FAA + DOT + OSHA + EPA for hangar ops) | 14 CFR + 49 CFR + 29 CFR + 40 CFR all in one platform | Aviation technical publications only — single-domain scope |
| Pricing model | $299/mo flat, unlimited aircraft types + users | Enterprise custom quote (~$8K-$80K+/yr by OEM library count) |
| Free trial (no sales call) | 5-day full access, no card | Demo + custom quote + OEM library + onboarding process |
| Implementation timeline | Self-serve · live in 30-60 minutes | Multi-week onboarding + OEM library provisioning + user setup |
| Use case fit | Part 145 / Part 91 PMI / POI compliance evidence binder for surveillance | Part 145 / Part 91 OEM technical publications library for mechanics |
Avantext prices on an enterprise custom-quote model that varies by aircraft type count, OEM publication library scope, user count, and integration tier. Range cited from public sources and operator reports — verify directly with Avantext for an exact quote.
Where Each Tool Sits Inside 14 CFR §145.211, §145.109, §145.219, §43.13, and §91.7
The Part 145 + Part 91 recordkeeping regulations map cleanly onto the right operating model. Here is who does what.
14 CFR §145.211 — Quality Control Manual
§145.211 requires every Part 145 certificated repair station to prepare, keep current, and follow a Quality Control Manual (QCM) acceptable to the FAA. The QCM must contain the inspection procedures, the calibration procedures for tools and test equipment, the receiving inspection procedures under §145.103, the housing / facility procedures under §145.109, the return-to-service procedures under §43.7, the maintenance record procedures under §43.9, and the personnel training procedures under §145.163. The QCM must be revised whenever any procedure changes, must be made available to all personnel performing maintenance, and must be made available to the FAA PMI on request. FAA Order 8900.1 Volume 6 governs PMI surveillance of Part 145 repair stations. Avantext is the OEM technical-pub library — it does not hold the §145.211 QCM document itself, it does not version-track QCM revisions, and it does not hold the FAA-acknowledgment correspondence chain. FileFlo wins here cleanly for §145.211: holds the QCM file with full version history, AI-classifies every revision against the referenced cross-procedures, links FAA acknowledgments to the revision chain, and produces the §145.211 PMI-surveillance-ready binder in one click.
14 CFR §145.109 — Equipment, Materials, and Data Requirements
§145.109 requires every Part 145 repair station to have the equipment, tools, and materials necessary to perform the maintenance, preventive maintenance, or alteration for which the station is rated; to have the technical data necessary to perform the work (acceptable to the Administrator, including the OEM maintenance manuals, ICAs, and applicable Airworthiness Directives); and to ensure all measuring and test equipment is calibrated at intervals acceptable to the FAA. The PMI surveillance checklist under FAA Order 8900.1 Volume 6 specifically pulls §145.109 tooling calibration records, technical data currency evidence, and facility documentation. Avantext covers the technical data side of §145.109 — the current-revision OEM maintenance manual is a real §145.109 acceptable-data source. Avantext does NOT hold the tooling calibration records, the housing / facility documentation, or the §145.109 evidence binder. FileFlo wins here for §145.109 evidence: holds the tooling calibration records, the facility documentation, the cross-references to the Avantext-supplied current-revision OEM data, and produces the §145.109 PMI-ready binder in one click.
14 CFR §43.13 — Performance Rules (General)
§43.13 requires every person performing maintenance, preventive maintenance, or alteration on an aircraft, airframe, engine, propeller, or component to perform the work using the methods, techniques, and practices prescribed in the current manufacturer's maintenance manual or Instructions for Continued Airworthiness (ICA) acceptable to the FAA, or other methods, techniques, and practices acceptable to the Administrator. §43.13 also requires the work be performed in a manner that ensures the aircraft is at least equal to its original or properly altered condition. Avantext is the upstream tech-pub source — the current-revision OEM maintenance manual a mechanic references is the §43.13 acceptable-data source. Avantext does NOT hold the signed evidence that the work was performed using that current-revision data: the §43.9 maintenance entry citing the manual revision and date, the §43.7 RTS sign-off, the inspector signature, the work order documentation under §145.219. The signed records are the document evidence the PMI pulls during Part 145 surveillance. FileFlo wins here for §43.13 evidence: holds the signed §43.13 compliance evidence, AI-links the §43.9 entry to the Avantext-supplied manual revision, holds the §43.7 RTS sign-off and inspector signature, and produces the one-click §43.13 binder reconciled to the §145.219 work order record.
14 CFR §145.219 — Recordkeeping
§145.219 requires every Part 145 certificated repair station to retain the records of maintenance, preventive maintenance, or alteration performed on each article worked under the certificate. The records must be retained for at least 2 years (with longer retention for life-limited parts under §91.417 and Part 39 Airworthiness Directives), must include the work order number, the article serial number, the inspection records, the §43.9 maintenance entry, the §43.7 RTS sign-off, the parts traceability records under §145.103, and (where applicable) the Form 8130-3 Authorized Release Certificate for installed components. The records must be made available to the FAA PMI on request during Part 145 surveillance. Avantext is the OEM technical-pub library — it does not hold the §145.219 work order records, the parts traceability documentation, or the Form 8130-3 attachments. FileFlo wins here for §145.219 retention: organizes records by article + work order + tail, AI- classified, retention-tracked through the §145.219 2-year window (and longer for life-limited parts and AD compliance), and produced as the one-click §145.219 binder for PMI surveillance organized to match the FAA Order 8900.1 Volume 6 inspector checklist.
14 CFR §91.7 — Civil Aircraft Airworthiness (Part 91 Corp Flight Dept Use Case)
§91.7 requires every person operating an aircraft to determine the aircraft is in an airworthy condition before each flight. The determination is supported by the §91.417 maintenance record retention requirement — the airframe, engine, propeller, appliance, and component records must be retained until the work is repeated or superseded (plus 1 year for §91.417(a)(1) records and 90 days after the work is approved for return to service for §91.417(a)(2) records). Part 91 corporate flight departments running multiple aircraft tails use Avantext to access the current-revision OEM maintenance manuals — the technical-pub source the contract Part 145 station references when performing maintenance under §43.13. Avantext does NOT hold the §91.417 retention file, the §43.9 entries from the contract Part 145 station, the §43.7 RTS sign-offs, the §91.403 maintenance accountability records, or the Airworthiness Directive compliance evidence under Part 39 / §91.403. FileFlo wins here for §91.7 + §91.417 evidence: holds the §91.7 / §91.417 / §91.403 / Part 39 binder per aircraft tail, AI-classified, retention-tracked through the §91.417 retention windows, and produced as the one-click §91.7 airworthiness binder for FAA surveillance or insurance underwriter due diligence. Civil-penalty exposure under 49 U.S.C. § 46301 runs up to $37,377 per violation per day for 2026 — a Part 145 surveillance event with §145.211 + §145.109 + §145.219 + §43.13 findings (or a Part 91 §91.7 + §91.417 + §91.403 + Part 39 finding compound) can escalate to a six-figure civil penalty exposure for the certificate holder or operator.
Real Pricing Comparison
FileFlo is one flat price for the compliance document evidence layer regardless of aircraft type count or OEM library scope. Avantext prices on an enterprise custom-quote model tiered by OEM publication libraries, aircraft type count, user count, and integration scope. The math escalates with every additional OEM library + every additional user.
* Pricing range based on public sources and operator reports across Avantext OEM-library tiers. Avantext does not publish pricing — contact Avantext for an exact quote based on aircraft type count, OEM publication library scope, user count, and integration tier.
The pricing comparison is not apples-to-apples. Avantext is an OEM aviation technical publications platform; FileFlo is a compliance document evidence platform. The right operating model is “Avantext for the OEM technical publications library + FileFlo for the §145.211 / §145.109 / §145.219 / §43.13 / §91.7 audit binder” — combined cost typically lower than enterprise aviation compliance platforms alone.
When to Use Each (and When to Use Both)
Add FileFlo if you...
- Are a Part 145 repair station whose PMI surveillance pulls §145.211 QCM revisions and FAA-ack correspondence
- Need the signed §43.13 performance compliance evidence — not just Avantext supplying the manual revision
- Need the §43.9 maintenance entry + §43.7 RTS sign-off reconciled with §145.219 work order records
- Need the §145.109 housing/facility records and tooling calibration evidence binder
- Need the §145.219 parts traceability + Form 8130-3 attachments binder organized by article
- Are a Part 91 corp flight department needing §91.7 / §91.417 / §91.403 / Part 39 airworthiness binder
- Want AI to auto-classify 600+ aviation compliance documents — no manual filing
- Need cross-regulation coverage — FAA + DOT + OSHA + EPA for hangar ground ops
- Need a one-click FAA-ready audit binder for PMI / POI surveillance events
- Want unlimited aircraft types + users without per-OEM-library enterprise inflation
Keep Avantext if you...
- Need the OEM aviation technical publications distribution library
- Need current-revision maintenance manuals + IPCs + SRMs + CMMs for mechanics
- Need the OEM revision pipeline integrated with service bulletin distribution
- Need multi-aircraft-type technical-pub access across Cessna / Gulfstream / Bombardier / Embraer / Dassault fleets
- Need searchable OEM document corpus for mechanic + QC inspector workflow
- Need the current-revision OEM data source for §43.13 performance compliance
- Need tech-pub user access control for differing mechanic + inspector roles
"We Added FileFlo to Avantext Because..."
Real workflows Part 145 accountable managers and Part 91 corporate flight department maintenance directors describe after pairing FileFlo with Avantext.
"I'm accountable manager at a Part 145 repair station with airframe + powerplant ratings on three Cessna Citation types. Avantext is our OEM tech-pub library — every mechanic searches the current-revision IPC and maintenance manual every time a work order opens. The tech-pub revision pipeline is genuinely good engineering and we are not switching off it. When the FAA PMI showed up for surveillance under 8900.1 Volume 6, the first request was our §145.211 QCM revision history with FAA-ack correspondence going back five years, and the second request was §145.219 work order records for a specific article serial number reconciled against the §43.9 entry, §43.7 RTS sign-off, and Form 8130-3 for the installed component. Avantext supplied the manual revision the §43.13 entry cited — but it does not hold the signed §43.13 evidence or the work order chain. We added FileFlo at $299/mo for the compliance evidence binder. PMI surveillance now closes in 90 minutes instead of three days, and our last surveillance had zero §145.211 or §145.219 findings."
"We're a mid-size Part 145 station running Avantext for OEM tech-pubs across four aircraft types — Gulfstream, Bombardier, Embraer, and Dassault. Avantext costs us about $35K a year for the OEM library access and it is the right tool for daily mechanic workflow; we are not switching off it. But our last PMI surveillance pulled §145.109 tooling calibration records, §145.219 work order records with parts traceability for life-limited components going back 7 years for §91.417 retention, and §43.13 performance compliance evidence reconciled across all four aircraft types. Avantext supplies the OEM data the §43.13 entry references — but it does not hold the signed evidence, the calibration records, or the work order binder. We added FileFlo for the compliance document evidence layer. Combined Avantext + FileFlo annual spend is still less than the enterprise aviation compliance platforms quoted us, and we kept the OEM tech-pub workflow that runs daily mechanic operations."
"I'm maintenance director at a Part 91 corporate flight department with three tails — a Gulfstream G650, a Bombardier Global 7500, and a Cessna Citation Latitude. We use Avantext for the OEM tech-pub library that our contract Part 145 station references when performing maintenance under §43.13. Avantext is the right tool for tech-pub access — multi-aircraft-type, revision-tracked, integrated with the service-bulletin pipeline. But the §91.7 airworthiness determination before each flight and the §91.417 retention file across all three tails — including the contract Part 145 station §43.9 entries, the §43.7 RTS sign-offs, the §91.403 maintenance accountability records, and the AD compliance evidence under Part 39 — is not what Avantext holds. We added FileFlo for the §91.7 / §91.417 / §91.403 / Part 39 binder per tail. The insurance underwriter due-diligence request that used to take two weeks now takes under an hour, and our last underwriter renewal closed without a single open §91.7 documentation request."
Frequently Asked Questions
What is Avantext, and who is it built for in 2026?
Avantext is an aviation document management platform built specifically for the storage, distribution, and retrieval of aviation technical publications — maintenance manuals, illustrated parts catalogs (IPCs), structural repair manuals (SRMs), wiring diagrams, component maintenance manuals (CMMs), service bulletins, and OEM technical data — for Part 145 repair stations and Part 91 corporate flight departments. Avantext has historically focused on the technical publications pain point of a Part 145 repair station mechanic who needs to look up the current-revision IPC for a Cessna Citation CJ3 wing assembly, or a Part 91 corporate flight department maintenance director who needs the latest-revision maintenance manual for a Gulfstream G650 engine controller across multiple aircraft tails. Avantext distributes OEM technical publications, version-tracks revisions as OEM service bulletins issue, and provides search across the technical document library. Avantext competes against aviation technical publications platforms like Aerodata, ATP Aviation Hub (the technical-pub side, distinct from ATP CTS training), and OEM-direct publication portals. Avantext is NOT a compliance evidence platform competing against CAMP Systems for §43.9 maintenance entries or against ATP CTS for §135.293 crew records — its document scope is OEM technical publications, not the signed compliance records the FAA POI/PMI pulls during surveillance. Avantext is the technical-pubs library the mechanic uses to find the right procedure; FileFlo is the compliance document evidence binder the FAA Principal Maintenance Inspector (PMI) pulls during Part 145 surveillance under FAA Order 8900.1 Volume 6 — the §145.211 QC Manual file, the §145.109 housing/facility records, the §43.13 performance compliance evidence, and the §145.219 recordkeeping binder organized by article + work order.
How much does Avantext cost vs FileFlo?
Avantext prices on an enterprise subscription model tailored to aviation document management scope — number of aircraft types in the publication library, number of OEM publication subscriptions (Cessna, Gulfstream, Bombardier, Embraer, Dassault, etc.), number of users with technical-pub access, and the integration tier (basic search vs full mechanic workflow integration). Public pricing is not posted; Avantext sells through a custom-quote sales process. Industry reporting and Part 145 repair station operator disclosures suggest Avantext annual contracts run from roughly $8,000-$15,000 per year for a small Part 145 station with a single OEM publication library (e.g., one Cessna Citation type) up to $40,000-$80,000+ per year for a multi-fleet Part 91 corporate flight department or larger Part 145 station with 4-6 OEM publication libraries, multi-user technical-pub access, and integration to the maintenance tracking platform. FileFlo is a flat $299 per month or $2,990 per year — unlimited aircraft types, unlimited users, all compliance features. The pricing comparison is NOT a substitution comparison. Avantext sells aviation technical publications + revision distribution; FileFlo sells the compliance document evidence binder the FAA POI/PMI pulls during surveillance. The right operating model for most Part 145 repair stations and Part 91 corporate flight departments is keep Avantext for the OEM technical publications library that mechanics search every day AND add FileFlo for the §145.211 / §145.109 / §145.219 / §43.13 / §91.7 compliance document evidence binder. Verify Avantext pricing directly during the Avantext sales process; FileFlo pricing is locked at getfileflo.com/pricing.
Does FileFlo replace the OEM technical publications library Avantext distributes?
No — and the Part 145 repair station and Part 91 corporate flight department pairing is exactly the use case where this distinction matters most. Avantext is the OEM technical publications distribution platform where the mechanic searches for the current-revision IPC for a wing assembly, the maintenance director pulls the latest-revision Component Maintenance Manual (CMM) for an engine controller, and the inspector references the structural repair manual (SRM) section for a specific damage classification. That technical-pub workflow is the daily mechanic + maintenance director surface — it runs every time a work order opens, it integrates with the OEM revision pipeline as service bulletins issue, and it is the single pane of glass the Part 145 quality control inspector uses to verify the work was performed against the current-revision OEM data. FileFlo does NOT attempt to replace that workflow. FileFlo is the destination for the completed compliance documents — the §145.211 QC Manual revision file with FAA-acknowledgment correspondence, the §145.109 housing/facility records, the signed §43.13 performance compliance evidence, the §43.9 maintenance record entries showing the work performed against the Avantext-supplied current-revision OEM data, the §43.7 return-to-service sign-off, the §145.219 work order + parts traceability records, and the Form 8130-3 Authorized Release Certificates for installed components. The combined operating model is: Avantext for the OEM technical publications library the mechanic searches every day + FileFlo for the compliance document evidence binder the PMI pulls during Part 145 surveillance.
Can FileFlo hold the 14 CFR §145.211 Quality Control Manual file the PMI pulls during Part 145 surveillance?
Yes — and this is FileFlo's strongest use case for Avantext-running Part 145 repair stations. 14 CFR §145.211 requires every Part 145 certificated repair station to prepare, keep current, and follow a Quality Control Manual (QCM) acceptable to the FAA Administrator. The QCM must contain the procedures, instructions, and information necessary to operate the Part 145 repair station — the inspection procedures, the calibration procedures for tools and test equipment, the procedures for receiving inspection of incoming parts under §145.103 and §145.109 housing/facility, the procedures for return-to-service under §43.7, the procedures for maintenance records under §43.9, and the procedures for personnel training under §145.163. The QCM must be revised whenever any procedure changes, must be made available to all personnel performing maintenance, and must be made available to the FAA PMI on request during surveillance. FAA Order 8900.1 Volume 6 governs PMI surveillance of Part 145 repair stations. Avantext distributes OEM technical publications — it does not hold the §145.211 QCM document itself, it does not version-track QCM revisions, and it does not hold the FAA-acknowledgment correspondence chain. The Part 145 station that walks into PMI surveillance with Avantext-supplied current-revision OEM data but cannot produce the current-revision §145.211 QCM with version history, revision dates, and FAA-acknowledged revision letters is the station that picks up a §145.211 finding. FileFlo holds the §145.211 QCM file, version-tracks every revision, holds the FAA-acknowledgment correspondence, and produces the FAA-ready §145.211 binder in one click — with the cross-references to §145.103 receiving inspection procedures, §145.109 housing/facility records, and §145.163 personnel training records readable to the PMI.
Does FileFlo hold the §145.219 recordkeeping and §43.13 performance compliance records the PMI pulls during a Part 145 surveillance event?
Yes — and this is where the Avantext + FileFlo pairing closes the most operational risk. 14 CFR §145.219 requires every Part 145 certificated repair station to retain the records of maintenance, preventive maintenance, or alteration performed on each article worked under the certificate. The records must be retained for at least 2 years (with longer retention for life-limited parts under §91.417 and Part 39 Airworthiness Directives), must include the work order number, the article serial number, the inspection records, the §43.9 maintenance entry, the §43.7 RTS sign-off, the parts traceability records under §145.103, and (where applicable) the Form 8130-3 Authorized Release Certificate. 14 CFR §43.13 separately requires every person performing maintenance, preventive maintenance, or alteration on an aircraft, airframe, engine, propeller, or component to perform the work using the methods, techniques, and practices prescribed in the current manufacturer's maintenance manual or Instructions for Continued Airworthiness (ICA) acceptable to the FAA, or other methods, techniques, and practices acceptable to the Administrator. Avantext supplies the current-revision OEM maintenance manual the mechanic references for §43.13 compliance — that is the technical-pub source. Avantext does NOT hold the signed evidence that the work was performed using that current-revision data: the §43.9 maintenance entry citing the manual revision, the §43.7 RTS sign-off, the inspector signature, the work order + parts traceability records under §145.219. The signed records are the document evidence the PMI pulls during Part 145 surveillance. The Part 145 station that has the Avantext-supplied current-revision OEM data but cannot produce the signed §43.13 compliance evidence is the station that picks up a §43.13 finding and (in repeat-finding cases) the §145.55 certificate enforcement action. FileFlo holds the §145.219 work order binder, the §43.9 entries citing the Avantext-supplied manual revision, the §43.7 RTS sign-offs, the parts traceability records under §145.103, and the Form 8130-3 attachments — organized by article + work order + tail, AI-classified, retention-tracked, and produced as the one-click §145.219 + §43.13 binder for PMI surveillance.
What about Part 91 corporate flight department use under §91.7 airworthiness records?
Same pairing logic applies for Part 91 corporate flight departments running Avantext. 14 CFR §91.7 requires every person operating an aircraft to determine the aircraft is in an airworthy condition before each flight — and the determination is supported by the §91.417 maintenance record retention requirement (the airframe, engine, propeller, appliance, and component records must be retained until the work is repeated or superseded, plus 1 year for §91.417(a)(1) records and 90 days after the work is approved for return to service for §91.417(a)(2) records). Part 91 corporate flight departments running multiple aircraft tails (e.g., a Gulfstream G650, a Bombardier Global 7500, a Cessna Citation Latitude) use Avantext to access the current-revision maintenance manuals for each aircraft type — the technical-pub source the contract Part 145 station references when performing maintenance under §43.13. Avantext does NOT hold the §91.417 retention file itself, the §43.9 entries from the contract Part 145 station, the §43.7 RTS sign-offs, the §91.403 maintenance accountability records, or the Airworthiness Directive compliance evidence under Part 39 / §91.403. FileFlo holds the §91.7 / §91.417 / §91.403 / Part 39 binder per aircraft tail, AI-classified, retention-tracked through the §91.417 retention windows, and produced as the one-click §91.7 airworthiness binder for FAA surveillance or insurance underwriter due diligence. Civil-penalty exposure under 49 U.S.C. §46301 runs up to $37,377 per violation per day for 2026 — a §91.7 + §91.403 + Part 39 finding compound is a six-figure exposure for the corporate flight department. Avantext for the OEM technical publications library; FileFlo for the §91.7 airworthiness records binder.
Authored by Chad Griffith, Founder of FileFlo. Last reviewed 2026-05-31. Software perspective — comparing Avantext (aviation OEM technical publications distribution) and FileFlo as compliance software products. References: 14 CFR §145.211, 14 CFR §145.109, 14 CFR §145.219, 14 CFR §43.13, 14 CFR §135.21, 14 CFR §91.7, 49 U.S.C. § 46301.
Add the FAA Part 145 + Part 91 Compliance Document Binder — At Flat $299/mo
5-day free trial. No credit card. No sales call. No multi-month OEM-library provisioning. Build your first 14 CFR §145.211 or §145.219 or §91.7 audit binder today — at a fraction of enterprise aviation compliance platform pricing.
$299/mo · Unlimited aircraft types · Cancel anytime · No implementation fees