Flytebook Fleet · flight schools, charter, clubs, aerial work

Every aircraft, every crew, on one desk.

Live flight-following, dispatch and debrief for small operators, from the phones your crews already carry. No trackers to fit, no hardware to buy.

7 days · 5 seats · No card · Observers free

Demo · KMRY

AIRBORNE2

  • N4521K1430–1615ZAIRBORNEC172Lesson 4 · pattern workALT 1,539 ft
  • N7291R1330–1500ZAIRBORNEC182Lesson 9 · night cross-countryALT 4,539 ft

RELEASED1

  • N812CF1500–1620ZRELEASEDP28AFerry · KMRY–KSNS · annual

SCHEDULED1

  • N33TE1600–1730ZSCHEDULEDDA40Lesson 2 · slow flight

LANDED1

  • N5108Q1300–1400ZLANDEDC172Solo · patternLanded 1352Z

Two aircraft reporting, one released, one scheduled — every strip from the crews’ phones.

Three questions every desk asks.

A flight school, a charter certificate, a club, an ag outfit — the desk asks the same three questions all day. Fleet answers them from the phones your crews already carry.

Dispatch

Where is 7291R right now?

Today it is a whiteboard, a group text, and “call me when you land.” The desk finds out an aircraft is late when somebody notices the gap.

  • Positions come from the crew’s phone and rack as strips by phase: scheduled, released, airborne, landed.
  • STALE after 120 seconds without a fix, with the age of the last one on the strip.
  • OVERDUE past the planned return plus a grace period you set — 15 minutes by default.
  • Alerts you can act on: past planned return, contact lost, pilot phone battery low, off the planned route. Every acknowledgement is audited.
Alerts · open
  • N7291RPast planned returnTF26011 · Park / Ito · planned 1500Z · 12 min overOpen
  • N812CFConnection staleFP26003 · Diaz · last fix 2 min agoOpen
  • N33TEMission not started by the grace timeTF26015 · Nguyen / Ito · scheduled 1600ZOpen
  • N4521KPilot phone battery lowTF26014 · Cole / Park · 14 % · acknowledged 1447Z by dispatchAcknowledged

Chief instructor

Who’s in the 172 at three?

The schedule lives in a spreadsheet, the change lives in a text thread, and the student who never saw it turns up for an aircraft that has already gone.

  • Missions from templates: a dual training flight carries the lesson, the syllabus stage and the maneuvers.
  • A double-booking check before you save, with an audited override — dispatchers double-book on purpose: standbys, swaps.
  • Crew assignment with accept or decline, and release: crews start organization flights only on a released mission.
  • A briefing package per leg — METAR/TAF, NOTAMs, TFRs, winds — with staleness tags and crew acknowledgement, plus a mission channel with read receipts and updates that require a response.
Missions · new
Aircraft
N4521K
Crew
Nguyen / Ito
Lesson
3 · Stage pre-solo
Window
1445–1630Z

N4521K is already booked 1430–1615Z on TF26014 (Cole / Park).

Change the aircraft or the window, or book anyway — the override is recorded with your name.

Briefing packageMETAR / TAF freshNOTAMs 40 minTFRs freshWinds 3 h stale

Safety

What happened out there?

The debrief is from memory, the track is a GPX file emailed around, and the paperwork for the insurer starts from a blank page.

  • Replay with planned versus actual, cross-track error, and the readouts: ALT, GS, TRK, VS, XTK.
  • Archived cockpit audio on the same timeline, when the crew shared it.
  • Markers for notes, deviations, training items and hazards; the instructor’s sign-off freezes the record.
  • GPX and CSV export, with every access recorded before a link is signed.
Archive · replay
0:310:386,0004,0002,000
ALT
2,350 ft
GS
104 kt
TRK
287 °
VS
−450 fpm
XTK
0.3 NM L
T+
0:42:17
Deviation · 0:31Training item · 0:38Signed · Park, CFI · 1612Z

Built for how you operate

Same desk, your vocabulary.

Every dual and solo flight on the desk, from release to debrief.

Instructors release the lesson, students fly it with the app they already carry, and the chief instructor sees the whole day on one rack. After landing, the replay and the sign-off live with the student’s record.

Template that ships
Dual training flight TF
Lesson · Stage (pre-solo, solo, cross-country, checkride prep) · Maneuvers
Seeded for every new organization, with instructor and student seats on the crew.
Roles that matter
Chief instructorInstructorStudentDispatcher
Alerts
Overdue after a 15-minute grace by default; students only see their own flights in the archive.
A mission ref looks like
TF26014

How it works

From sign-up to the first strip in an afternoon.

  1. Create your organization

    Two minutes: a name, a home base, how you fly. The 7-day trial starts at once, with four mission templates already on the desk.

  2. Add aircraft, invite your team

    Registration, type and base per aircraft. A link per person with one of twelve roles — observers watch for free.

  3. Crews fly with the app

    On any plan, including free Solo. Before sharing, the pilot reads your consent declaration verbatim. Location is required by default; cockpit audio is optional.

  4. Your desk sees every flight

    Live strips and alerts while it is airborne, the replay and debrief when it lands, the audit trail throughout.

Your crews’ data, your rules

Sharing a position is a decision. It stays one.

Consent
Your consent declaration is shown to the pilot verbatim before any sharing starts. You write it; the app displays it.
Sharing rules
Location required by default, cockpit audio optional, release required — each one a policy you set for your organization.
Retention
Live track points, flight tracks, cockpit audio, messages, briefings and audit each keep their own retention window. Scheduled sweeps enforce it.
Roles
Twelve roles from owner to observer over thirty-four permissions, with per-person overrides that expire. Students see their own archive.
Revisions
Mission plans are immutable revisions. When two people edit, the second to save sees the conflict and the diff — never a silent overwrite.
Access audit
Every archive download and export is recorded before a link is signed, so who saw what is as complete a record as the flight itself.

Pricing

Start on the full desk.

After the trial

Seat-based plans — Fleet Starter, Fleet and Fleet Pro — follow the trial. We set yours up with you before it ends, sized to your seats and bases, and nothing is charged until you say so.

Your crews’ own Flytebook plans are separate and stay theirs. Solo is free forever.

Questions operators ask

Before you start.

Do my pilots need a paid Flytebook plan?

No. Crews fly organization missions on any Flytebook plan, including the free Solo plan. Your organization’s seat is what admits them to the desk.

What hardware do I need?

None. Positions and, if you switch it on, cockpit audio come from the Flytebook app on the crew’s phone. There is nothing to fit to the aircraft.

What happens when a phone loses signal?

The strip reads STALE after 120 seconds without a fix and the desk sees the age of the last one. Past the planned return plus your grace period it moves to OVERDUE and raises an alert. Nothing ever says “landed” without a fix.

Can students see other people’s flights?

Only what their role allows. Students read their own flights in the archive; instructors, dispatchers and safety roles see the organization’s. Twelve roles cover the usual desks, and permissions can be adjusted per person.

We fly from more than one field. Does that work?

Yes. Organizations are split into bases, teams and units, each with a home airport, and people can be scoped to the ones they belong to.

Is the trial limited?

It is the full desk for 7 days with 5 seats. Observers don’t use a seat. No card is needed to start.

How do invitations work?

You create an invitation with a role from the People page. Give an address and Flytebook emails it; either way you get a link you can send yourself.

Set up your desk this afternoon.

Create your organization, add the aircraft, send your crews a link. The first strip appears the moment the first crew starts a flight.

7 days · 5 seats · No card