GoFBO

GoFBO for Part 135

Fly charter by the book, without a second system.

GoFBO adds Part 135 to the scheduling, crew, briefings and flight logs you already run: each leg flown 91 or 135, duty and rest checked while you build the trip, signed releases with the load manifest, flight locating, and records an inspector can follow. License only the tails you fly under 135.

A GoFBO Part 135 flight release with weather, alternate and runway checks
New · Safety management system

Your Part 5 SMS is due May 28, 2027. GoFBO has it built in.

Every Part 135 operator needs a safety management system and a declaration of compliance with the FAA by May 28, 2027. GoFBO runs yours where the flying already is: a high FRAT, a duty exceedance, an overdue flight or an MEL deferral starts a safety report in one click, and every step is kept in records that can't be quietly changed. When you're ready, GoFBO checks you against Part 5 and writes the declaration letter. Included with Part 135.

A safety policy in GoFBO, signed by the accountable executive

Safety policy

Written from a starting draft, signed by your accountable executive in GoFBO, read by everyone.

Risk management

A hazard register on a 5×5 matrix, rated before and after controls, and changes reviewed before they start.

Safety assurance

Confidential reports, investigations, internal audits and safety objectives you can measure.

Safety promotion

SMS training records with recurrent due dates, and safety bulletins everyone marks read.

AI Trip Builder

A charter request comes in by text. Forward it, and the trip is built.

“Bill and Joe want to go to the next Bears game.” That's the whole request. Forward the customer's text to GoFBO, forward the email, or paste it in. GoFBO looks up the game, picks the airport, works out when to land and when to leave, adds the fuel stop, asks the one thing nobody said, and has a Requested trip waiting for you.

Your GoFBO texting number [email protected]
GoFBOText message
Bill and Joe want to go to the next Bears game.
Trip SAW-1047 started: N350SA KBOI → KPIR → KMDW Sun Oct 25, landing 2:20 PM for the 3:25 PM kickoff at Soldier Field. When do Bill and Joe want to fly home?
Monday morning around 9
Done: home Mon Oct 26, wheels up KMDW 9:00 AM via KPIR. SAW-1047 is waiting for you to schedule.
RequestedSAW-1047KBOI → KMDWFinish the trip

One sentence in. A whole trip out.

“Bill and Joe want to go to the next Bears game.”

  1. Reads the request

    "Bill and Joe" is two passengers. "The next Bears game" is an event it has to look up.

    2 passengers · event: the next Bears game
  2. Finds the game

    It searches the web for the Bears' next game: the date, the kickoff and the stadium. An away game sends it to that stadium instead.

    Sun, Oct 25 · 3:25 PM kickoff · Soldier Field, Chicago
  3. Picks the airport

    Every airport within 45 nm of Soldier Field is checked for the runway this aircraft needs, the drive to the stadium and FBOs you already use.

    KMDW Midway · 35 min drive · 6,522 ft runway
  4. Sets the arrival

    Kickoff, less the drive, less 30 minutes at the FBO to unload and find the car.

    Land KMDW by 2:20 PM CDT
  5. Chooses the aircraft and the departure

    The aircraft free that weekend, with flight times from its own cruise speed, worked back to a departure time in Boise's time zone.

    N350SA · wheels up KBOI 8:05 AM MDT
  6. Adds the fuel stop

    Boise to Midway is 1,255 nm and the King Air is planned at 1,000 nm, so it stops near halfway, at an airport with the runway and an FBO, your fuel program's first.

    Fuel stop KPIR Pierre · 45 min on the ground
  7. Asks what it can't know

    Nobody said when they're coming home, so GoFBO asks by text or email. The answer plans the return.

    "Monday morning around 9" → home Mon, Oct 26 via KPIR
  8. Hands it to a person

    A Requested trip lands on the dashboard and every scheduler is told. Add the crew, check the times, click Schedule. Nothing is scheduled by itself.

    SAW-1047 · Requested · waiting for you

From the text to the schedule in three steps.

  1. Forward it, or paste it.

    Text it to your GoFBO number, forward the email to [email protected], or paste it into AI Trip Builder on the dashboard.

  2. GoFBO plans it.

    The event, the airport, the times, the fuel stops, and the aircraft when only one fits. Anything a trip can't be booked without (the day, how many are going, when they fly home) is asked by text or email, and the answer updates the trip.

  3. A person schedules it.

    It lands on the dashboard as a Requested trip and every scheduler is told. Add crew, check the times, click Schedule. Duty, rest and the release still apply before it flies.

More about AI Trip Builder

AI Trip Builder's plan for the Bears trip: the legs, the fuel stop at Pierre, and what GoFBO assumed

Only your people, and nothing scheduled by itself. Requests are accepted only from people in your GoFBO account who can create or request trips: email has to pass SPF or DKIM, and texts have to come from a phone number that person has agreed to use with GoFBO. Every trip waits as Requested until a scheduler schedules it. Part of the AI add-on, with potential delay detection and crew destination research.

Flight release · 135.77

Release the flight with the checks done for you.

The METAR and TAF for departure, destination and alternate are kept with the release. Alternate minimums under 135.223 and the 60% runway rule are checked, and the release is signed by a named person with release authority.

How it works

A Part 135 flight release with METAR, TAF, alternate and runway checks
Load manifest · 135.63(c)

Weight and balance on the envelope.

Crew, passengers, bags and fuel become the load manifest. Zero fuel, takeoff and landing are plotted on the aircraft's own CG envelope, and anything outside it is flagged in red before anyone signs.

How it works

Weight and balance on the release: zero fuel, ramp, takeoff and landing, and the chart inside the CG envelope
Duty and rest · 135.267

Duty and rest checked while you schedule.

Flight time, duty and rest for every pilot, quarter, two quarters and year, including their Part 91 flying, with anything over a limit called out and printable for the inspector.

How it works

135.267 flight time, duty and rest by pilot, with findings
Flight locating · 135.79

Know where every flight is.

Crew tap Departed and Arrived from their phone. Released, airborne and arrived flights are on one board, and an overdue flight emails everyone with release authority.

How it works

Flight locating: released, airborne, arrived and overdue flights

Built for Part 135.

Each one tied to the regulation it helps you meet. Pick one for a short walkthrough.

Also built in

Per tail

Part 91 or 135 on every leg

License only the tails you fly under 135. Owner legs and positioning stay Part 91 on the same trip, and still count toward duty.

119.65, 135.77

135 positions and release authority

Director of Operations, Chief Pilot, Director of Maintenance and the rest, each with the access their job needs. Release authority goes to named people, not a role.

135.63

Records that can't be quietly changed

Flight logs, duty, the certificate profile and your settings keep every version. Nothing in the compliance history can be edited or deleted.

135.63, 135.65, 135.267

Reports an inspector expects

Flight time, duty and rest; pilot records and checks; the aircraft list; flights flown with crew and block times; releases and manifests; flight locating; mechanical irregularities.

91.203

Aircraft documents and insurance

Registration, airworthiness and insurance with expiry dates and scans, and the insurer's pilot minimums checked against every pilot you assign.

Stricter than 135.267

Your own duty rules

Longest duty day, rest before duty, flight time and legs per duty, and days off in a rolling window. Warn or block each one, for Part 135 trips or all flying.

119.5, 119.7

Your certificate in one place

Certificate number, kind of operation, FSDO, your principal inspectors and DOT registration, kept with the rest of your records.

Warn, or stop the trip.

Every operator draws the line in a different place. Choose whether a duty, rest or qualification problem shows as a warning for the scheduler to weigh, or stops a Part 135 trip from being scheduled until it's fixed. Either way the reason and the regulation are spelled out on the trip, and the choice is kept in your compliance history.

  • One-pilot and two-pilot aircraft, set per tail
  • Duty planned from your own report and release times
  • A request can always be saved; only scheduling is held
GF-1062 · N123AB · BOI → SUN → BOI
Can't be scheduled under Part 135 until fixedSecond in command not assigned 135.99Captain: 7.5 h of rest in the 24 before duty ends 135.267(d)
Check before savingFirst officer: 1 landing in the C25B in 90 days 135.247

Coming next.

In the order operators have asked for them. Tell us what you need next and it moves up the list.

Coming next

Charter quotes and contracts

Quotes priced from your rates, contracts with your DOT registration, and invoices that flow from the trip.

Try our fuel planner for yourself.Your legs, your burns, your FBO prices: see where to buy and where to tanker, and download the report. Free, no sign-in.Plan a trip

Your Part 91 flying lives here too.

Most charter operators also fly owner trips, positioning legs and maintenance ferries. GoFBO keeps all of it on one calendar with one crew list, so a Part 91 leg yesterday still counts toward a pilot's duty and rest today, and nobody keeps a second spreadsheet to find out.

Pricing.

Part 135 is an add-on to any GoFBO plan, licensed per tail. See the plans.

Add-on for any plan

Flying charter? Add Part 135 operations.

Add Part 135 to any package and license only the tails you fly under 135. The rest of your fleet stays Part 91, and each trip leg on a 135 aircraft can still be flown under Part 91 for owner or positioning flights.

$35per Part 135 tail
per month
  • Part 91 or 135 on every leg, on the tails you license
  • Director of Operations, Chief Pilot and other 135 positions, with release authority
  • Certificate profile with your FSDO and principal inspectors
  • Block times and crew duty in every flight log
  • 135.267 flight, duty and rest report, pilot checks (135.293, .297, .299), aircraft list and mechanical irregularities
  • Compliance history that can't be edited or deleted
Built in the left seat

We were tired of finding out where we were flying at the last second.

As pilots, we kept two paper logs and four Excel spreadsheets for the same flights. Trips were planned in group texts we weren't even on. Our flight coordinator was overwhelmed, and so were we: we often didn't know how many passengers were coming, let alone who they were, when we were leaving, or sometimes even where the customer wanted to go, until the very last second.

One place for the whole trip, so the crew knows what the office knows, when the office knows it.

The pilots behind GoFBO · Boise, Idaho

The way it wasWhat we built

Two paper logs and four Excel spreadsheets for the same flights.

One flight log. Photograph the Hobbs and the fuel; totals, reports and maintenance update themselves.

The trip lives in a group text you're not even on.

Every crew member sees the trip, who's flying and every change, on their own phone, as it happens.

A flight coordinator buried in calls, texts and spreadsheets.

One schedule everyone works from. Crew are asked and confirmed for them, so they can coordinate.

No passenger count, let alone a manifest.

Passengers on the trip, with the manifest and their preferences in the trip sheet before every leg.

Not knowing when you leave, or even where they want to go, until the last second.

A request becomes a trip the moment it arrives. Forward the email; every change reaches the crew live.