FBO One Email Integration
BCC your FBO One handling confirmations to AirPlx and trips appear on your schedule within a minute. No double entry, no typos.
How it works
FBO One Handling email AirPlx Parses email Trip
System -------------------> Inbox -----------------> Created
(BCC / forward) (within ~1 min)FBO One sends a handling confirmation. You have a copy BCC’d to your AirPlx ingestion address. AirPlx pulls the tail number, aircraft type, operator, and ETA/ETD out of the email and creates the trip automatically.
Setup
Three steps. Expect 5 minutes end-to-end.
Configure AirPlx
Go to Settings → Configuration and do all four of these in one sitting:
- Enable Email Ingestion (toggle on).
- Copy your ingestion address — it looks like
ingest+{your-slug}@airplx.com. You’ll paste this into FBO One in the next step. - Select
FBO Onefrom the FBO System dropdown. - Set your Timezone to your FBO’s local time (e.g.,
Australia/Sydney,America/New_York).
Timezone is not optional. FBO One sends times in local time — if AirPlx doesn’t know your timezone, every arrival and departure silently defaults to UTC and will be hours off.
Optional: set a Default Location (hangar or ramp) if most email-ingested trips go to the same spot. You can always reassign after the fact.
BCC the ingestion address from FBO One
BCC in FBO One (recommended)
In FBO One, open Administration → Email Message Settings for handling confirmations and add your ingest+{slug}@airplx.com address as a BCC recipient. Save.
If you can’t find the setting, your FBO One admin or FBO One support can help — the exact path depends on your FBO One configuration.
Deliverability: FBO One sends through Amazon SES. If nothing arrives, ask your FBO One admin to check their SPF/DKIM DNS records — see Setting Up FBO One For Sending Email .
Send a test
Trigger a handling confirmation in FBO One (or ask your admin to send a test), wait about 60 seconds, and check your AirPlx schedule. The trip should appear with a blue Email source chip. If it doesn’t, check Operations Inbox — it may have been queued for review.
What gets imported
| Field | From the email | Example |
|---|---|---|
| Tail Number | First line after “Dear Duty Manager,” or REGISTRATION: | N930GL, VHVKX, G-LUXE |
| Aircraft Type | AC Type: | GL6000, E55P, FA7X |
| Operator | Operator: | CARGILL INC, Elevate Jet |
| ETA | ETA: (local time, converted to UTC) | 16-Jan-26 08:20 |
| ETD | ETD: (local time, converted to UTC) | 17-Jan-26 10:00 |
| Reference | REF number: | BDU-1769 |
Unknown ETA or ETD can be written as -, TBD, TBA, or N/A — AirPlx creates the trip with an open-ended arrival or departure.
When a trip doesn’t appear
If AirPlx receives an email it can’t fully process — usually because the aircraft isn’t in your database yet — it lands in Operations → Inbox instead of creating a trip. Open the item, resolve what’s flagged (e.g., add the missing aircraft), and process it.
Email format reference
AirPlx handles the four common FBO One scenarios.
Arrival + departure
The standard case — aircraft arriving and departing on known dates.
REF number: BDU-1769
ATTN: AirPLX Hailey
Dear Duty Manager,
N930GL
AC Type: GL6000
Operator: CARGILL INC
ETA: 16-Jan-26 08:20 (LT)
ETD: 17-Jan-26 10:00 (LT)International registrations work out of the box: N-numbers (US), VH (Australia), G- (UK), D- (Germany), C- (Canada), and other ICAO formats.
Edge cases
- Cancellations are not processed. If FBO One cancels a trip, remove it from AirPlx manually. Cancellation support is on the roadmap.
- Amendments may create a second trip. If FBO One re-sends with new times and the dates no longer overlap the original, you’ll get a duplicate. Remove the stale one.
- Exact duplicates are deduped. The same email processed twice won’t produce two trips — AirPlx tracks each email by its unique ID.
Troubleshooting
All times look wrong by the same offset. Your timezone is unset or wrong. Fix it in Settings → Configuration — this is the cause roughly every time.
Nothing is arriving. Verify the ingestion address has no typos (a wrong slug fails silently — there’s no bounce). Then ask your FBO One admin to confirm the email is being sent, and wait a full 60 seconds.
Trip didn’t appear but the email was sent. Check Operations → Inbox. Common cause: the aircraft isn’t in your AirPlx database yet.
FAQ
How fast do trips appear? Typically 1–2 minutes. AirPlx polls for new mail every 60 seconds.
Does AirPlx read any other email?
No. Only mail sent to your specific ingest+{slug}@airplx.com address is processed.
Where does a default location come in? If set, every email-ingested trip is assigned there on creation. You can move it afterward like any other trip.
My FBO uses something other than FBO One. See X1 FBO Email, or email support@airplx.com — we can usually add a parser for common formats.