Fair Fare
FairFare
The DOT cash-refund navigator — turn a cancellation or schedule change into the cash the airline actually owes you, not a 60-day voucher.
Date: 2026-05-14 Form factor: Web app (single-page; mobile-friendly) Status: Prototype
What it is
FairFare is a single-page workspace that walks an airline passenger through the DOT Automatic Refund Rule (14 CFR §259.5) the moment their flight gets cancelled or significantly delayed. It produces a refund verdict, a side-by-side decode of the airline's voucher offer vs. the cash refund the law allows, an auto-generated demand letter addressed to the carrier's refunds inbox, and a 7-business-day deadline tracker that escalates to a DOT consumer complaint if the airline misses the clock.
The prototype demonstrates the end-to-end flow on five sample disruptions (Frontier, Delta, Spirit, United, American) covering the four most common refund-eligibility patterns: a domestic delay over the threshold, an international delay just under it, an outright cancellation routed to a Future Travel Voucher, the flight-number-only swap that's currently inside the DOT enforcement carve-out, and a multi-segment cancellation rebooked overnight.
Who it serves
Any US-departing or US-arriving traveler who just got the dreaded "your flight has been changed" email — but specifically the audiences who are most often steered into vouchers:
- Leisure travelers booked on ultra-low-cost carriers (Frontier, Spirit, Allegiant). The Feb 2026 FlyersRights audit found these carriers were still routing a majority of cancellation customers to Future Travel Vouchers by default, despite the rule. (Altitudes Magazine, 2026-04-18)
- Business travelers with non-refundable tickets purchased through an OTA. They tend to assume "non-refundable" means "I'm out of luck" — DOT's automatic-refund obligation overrides the fare class.
- Anyone with $50–$200 in ancillary fees (seat selection, bags, priority boarding) sitting on a cancelled flight. Those fees are refundable as part of the same claim and most travelers never ask.
- Travelers whose flight was "merely renumbered" in May/June 2026 — they should know the rule is paused for them until 2026-06-30 so they don't waste a complaint cycle.
The pain is concrete and recurring. Airlines have made over 12,000 schedule changes per month so far in 2026, and a CFPB analysis of consumer chargeback data showed travel-industry chargebacks rose 28% YoY after the DOT rule took effect — meaning the gap between what travelers are entitled to and what they actually receive is large enough to drive payment-rail disputes.
Why it could be profitable
Monetization is freemium with a one-time-fee Pro tier and a B2B white-label:
- Free: refund verdict + demand letter for one disruption per session. No account.
- Pro ($9 one-time per claim): chargeback-letter template, EU261/UK261 cross-jurisdictional letter, deadline reminders by email, and DOT-complaint pre-fill. Scales with the user's actual recovery — a $400 ticket recovery is a 45× return on the $9 fee.
- B2B white-label ($199/mo flat): corporate-travel desks, premium-card concierge teams (Amex Platinum, Chase Reserve), and travel agencies embed FairFare into their post-disruption flow. They already pay junior staff to chase refunds; FairFare cuts the labor.
Demand math: 862M US enplanements per year × 4–6% disruption rate × $300 avg refundable value × 30% of disrupted travelers who would actually use a tool = **$3.1B/yr in recoverable refunds passing through the funnel**. A $9 Pro conversion on 0.5% of disrupted travelers would clear $1.6M ARR before any B2B revenue.
The regulatory tailwind is unusually strong: DOT just entered full enforcement in April 2026, FlyersRights is publishing a quarterly compliance score, and the Refund III rulemaking due 2026-06-30 will expand the rule (likely closing the flight-number-change loophole). Each of those events is a free PR moment for a tool sitting on top of the rule. (DOT, 2025-12-05, Altitudes Magazine, 2026-04-18)
Form factor & scope
Single-page web app, sized for mobile and desktop. The prototype is scope-locked to the post-disruption refund workflow — it does not search, book, or rebook flights, and it is not a chargeback service. The minimum viable scope demonstrated here is:
- Pick a disruption (sample or your own).
- Get a verdict on cash-refund eligibility.
- See the airline's voucher offer decoded next to what the rule actually allows.
- Get a personalized, citation-ready demand letter addressed to the carrier's published refunds inbox.
- Watch the 7-business-day refund deadline; if the airline misses it, escalate to DOT.
How to run it
- Open
index.htmlin any modern browser (Chrome, Firefox, Edge, Safari). - Pick any disruption from the left rail. The verdict, voucher decoder, demand letter, and deadline tracker update together.
- Optionally edit your name in the right-hand controls, toggle ancillary-fee inclusion, or add the chargeback escalation paragraph.
- Copy letter copies the demand letter to the clipboard. Download .txt saves it as a file you can attach to the airline's refund webform.
No build step, no API keys, no accounts. The sample data is inlined inside index.html as a <script type="application/json"> block, so the page works directly from file://.
What's in this prototype
- Refund engine that applies the DOT thresholds (3hr domestic / 6hr international / cancellation = automatic) and identifies the active carve-out for flight-number-only changes through 2026-06-30.
- Five fully-modeled disruptions spanning ULCC, legacy, and international itineraries.
- Carrier intelligence panel with a 9-airline compliance scoreboard derived from the Feb 2026 FlyersRights audit, the carrier's published refunds inbox, and the most common voucher-trick observed for each.
- Letter generator that cites 14 CFR §259.5(b) and §259.5(c), enumerates ancillary fees, and computes the credit-card refund deadline (today + 7 business days).
- Deadline panel that shows the credit-card and other-payment refund deadlines and the DOT-complaint URL to escalate.
Roadmap
- Add EU261 / UK261 cross-jurisdictional refund logic (compensation tiers up to €600).
- Connect to credit-card chargeback APIs (Visa, Mastercard, Amex) for one-click "Reg Z dispute" filing on the 8th business day.
- Add a passive disruption monitor: paste a confirmation number and FairFare polls airline schedule data overnight, firing the workflow automatically when a "significant change" is detected.
- B2B white-label: brandable header, multi-claim dashboard, audit log for corporate compliance.
- Reciprocal-trust integration with travel-insurance carriers (Allianz, Berkshire) so the demand letter doubles as a claim-supporting document.
Sources
- DOT, Airline Refunds and Other Consumer Protections, 90 FR 96891 (2025-12-05) — text of the December 2025 enforcement update and the carve-out for flight-number-only changes through 2026-06-30.
- Altitudes Magazine, DOT Airline Refund and Fee Transparency Rules Enter Full Enforcement Phase (2026-04-18) — context for the April 2026 enforcement transition and the FlyersRights audit findings.
- DOT, Refunds (Aviation Consumer Protection) — official passenger-facing summary used to validate the in-app citations and the secure.dot.gov complaint URL.
- DOT, Final Rule Requiring Automatic Refunds of Airline Tickets and Ancillary Service Fees (2024-04-24) — the underlying 2024 rule (89 FR 32760) FairFare cites in every demand letter.
Requirements
FairFare — Requirements
Goals
- Help a non-expert traveler convert a cancelled or schedule-changed flight into the cash refund DOT requires within 30 minutes of the disruption notice.
- Make the rule itself legible: every verdict cites the specific regulation, deadline, and carve-out so a determined airline rep can't bluff a refusal.
- Produce a portable, copy-pasteable demand letter that an airline's refund team has to acknowledge — no plain English of "I'm upset", just the rule plus the math.
- Track the 7-business-day refund clock and turn missed deadlines into a one-click DOT consumer complaint.
Primary user
A US-based leisure or business traveler who has just received a disruption notice (cancellation, retiming, or "we've rebooked you on…" email). They are typically:
- 25–55 years old, mobile-first, opening the link from a phone in an airport lounge or a hotel lobby.
- Aware that "DOT changed the refund rules" but unsure whether their specific situation qualifies.
- Comfortable copying a generated letter and emailing it from their personal address.
- Not willing to pay $150 to a refund-recovery service that takes 30% of the recovered amount.
The job-to-be-done is: "In the next 5 minutes, tell me whether I'm owed a cash refund, draft me the email that gets it, and tell me what to do if it doesn't show up."
Functional requirements
- FR1: Render a left-rail picker of pre-loaded sample disruptions, each with carrier, route, and the headline that triggered the user's confusion.
- FR2: For each disruption, surface a persona/itinerary card with passenger, ticket number, paid amount, payment method, and purchase date.
- FR3: Compute a refund verdict using the DOT thresholds (3hr domestic, 6hr international, cancellation = automatic) and label it as Qualifies / Does-not-qualify / Carve-out.
- FR4: Display the cited regulation (14 CFR §259.5) and the relevant subsection alongside the verdict so the rule is auditable.
- FR5: Compute the dollar amount owed = base ticket + (optional) ancillary fees. Toggle ancillaries in/out and recompute live.
- FR6: For each carrier, surface a 0–100 compliance score, the carrier's published refunds-team email address, and a one-line note on the carrier's most common voucher-trick observed in the audit.
- FR7: Generate three letter variants: (a) cash-refund demand for qualifying disruptions, (b) amenities request for sub-threshold delays, (c) carve-out inquiry for paused flight-number-only changes.
- FR8: Allow the user to override the passenger name and toggle a chargeback + state-AG escalation paragraph.
- FR9: Provide Copy-to-Clipboard (with
document.execCommandfallback forfile://) and Download-as-.txtfor the letter. - FR10: Compute and display the credit-card refund deadline (today + 7 business days, skipping weekends) and the other-payment deadline (today + 20 calendar days).
- FR11: Display a fallback panel pointing to the DOT consumer complaint URL with a one-line explanation of typical resolution time.
- FR12: Surface a top-bar "estimated refund owed" pill that updates with every scenario change.
- FR13: Run from
file://with no remote scripts, no API keys, and no build step. Inline the sample data insideindex.htmlto avoid thefetchCORS restriction on local files.
User stories
- As a Frontier passenger whose flight was delayed 4 hours, I want to know whether I qualify for a cash refund so I can refuse the $50 voucher and demand the full $251.40.
- As a Spirit passenger whose flight was cancelled and offered a 60-day Future Travel Voucher, I want a citation-ready letter that demands the cash refund of my full ticket plus the bag and seat fees.
- As a Delta international passenger whose flight was delayed 5h 30m, I want to be told plainly that I am NOT entitled to a mandatory cash refund, so I focus my time on amenities (meal vouchers, hotel) instead.
- As a United passenger whose flight number was changed without any time change, I want to know that DOT has paused this category of refund until 2026-06-30, so I don't waste a complaint cycle.
- As an American passenger who was rebooked overnight after a cancellation, I want to know that accepting the rebook does NOT waive my cash-refund right, so I can still elect cash if the new itinerary is unworkable.
- As a passenger who emailed the airline and got no response, I want a deadline-tracked escalation path that ends with a DOT complaint.
- As a corporate-travel-desk admin handling 30 disruptions a week, I want to copy a pre-filled letter for any traveler in under 60 seconds without needing to open a refund SOP wiki.
- As a passenger who cares about privacy, I want all of my booking details to stay client-side and never touch a server.
Non-functional requirements
- Performance: First paint < 1s on a 4G connection; total bundle (HTML + CSS + JS + inlined data) < 80 KB gzipped.
- Privacy: No analytics, no third-party fonts, no remote scripts. Booking details never leave the browser.
- Accessibility: Semantic HTML5 (
header,main,aside,article,footer); WCAG 2.2 AA contrast on dark theme; all interactive controls reachable via keyboard. - Resilience: Clipboard write falls back to
document.execCommand('copy')whennavigator.clipboardis unavailable (which happens forfile://in some browsers). - Responsiveness: Three breakpoints — desktop (>1100px), tablet (600–1100px), phone (<600px). Single-column collapse below 1100px.
- Data integrity: All thresholds, deadlines, and citations live in
sample-data.json::rule_summaryso the rule can be updated in one place when DOT publishes Refund III on 2026-06-30.
Out of scope (for the prototype)
- Live integration with airline reservation APIs (Sabre, Amadeus, Travelport) to detect disruptions automatically.
- Real chargeback filing with Visa / Mastercard / Amex.
- Multi-claim dashboards or accounts.
- Non-US carriers and non-US-departing itineraries (EU261/UK261 logic is roadmap, not in this build).
- Hotel/rental-car refund logic.
Open questions
- Should the demand-letter Pro tier include a follow-up cadence (Day 8 reminder, Day 14 escalation) over email — and if so, do we need to host a transactional email service to make that work?
- Will Refund III (due 2026-06-30) close the flight-number-change carve-out, or codify it? The carve-out scenario in this prototype assumes the carve-out remains in force until that date.
- Is there appetite from premium-card concierges (Amex, Chase, Capital One) to white-label this, or do they prefer to keep it in-house with their existing claim-support staff?
- For B2B corporate-travel buyers, do we need single-sign-on and audit log compliance from day one, or can a per-claim PDF export carry that load?