FBO and airport fee data
What FBOs and airports actually charge.
Handling, ramp, facility, landing, parking and every other line, taken from real invoices. It's shared between operators who give some to get some, with no tail numbers or names attached.
Give to get
- 1
Contribute an invoice
Send an FBO or airport invoice as a PDF, or report a single fee line. The file is read, reduced to its fee lines and dropped. Only a fingerprint of it is kept.
- 2
Identifiers are stripped
Tail numbers, operators, crew and passengers never reach the database. What is stored is the airport, the FBO, the aircraft class, the fee type, the amount and the date.
- 3
Earn lookups
A validated line earns credits, with more for FBOs that have no recent data. A duplicate earns nothing. Spend credits to look up what an airport's FBOs charge.
Observed, and clearly labeled when not
Every figure from an invoice is returned as observed, with its date. Subscribers also get projected figures for FBOs and aircraft classes with no invoice yet. A projection is always labeled as one, with a confidence score and the observations it was built from.
Contributed data is not shown to anyone until the operator who contributed it has consented to share it.
Fee types
- Handling
- Ramp
- Facility
- Landing
- Terminal
- Parking
- Overnight
- GPU
- Lav service
- Potable water
- De-ice
- Hangar
- Security
- Call-out
- Navigation
- Fuel surcharge
- Other
Aircraft classes
- Piston
- Turboprop
- Light jet
- Midsize jet
- Super-midsize jet
- Heavy jet
- Airliner
Built for dispatch tools and AI agents
AvFees is an API first. Four operations cover it: report_fee, submit_invoice, lookup_fees and credit_balance. They are described in OpenAPI and exposed as MCP tools, so a quoting system or an assistant can price a stop before the invoice arrives.