Managing your fleet

The fleet roster is what CFIs and students pick from when scheduling lessons or checking out a plane. Each aircraft is scoped to your school workspace — moving a plane between schools requires support.

Adding an aircraft

Fleet → Add aircraft. Required fields:

• Registration (N-number for US-based schools)
• Year, make/model, category (single-engine, multi-engine, etc.)
• Hourly rate in cents, with a wet / dry flag for whether the rate includes fuel
• Status — active, maintenance, or archived

Optional but recommended:

• Nickname — what CFIs and students see in dropdowns alongside the registration
• Hobbs time and Tach time — current readings, used as defaults during aircraft checkout
• Primary location — defaults to your school's primary location if you don't set it

Status and how it surfaces in the UI

• active — bookable. Shows up in lesson-scheduling and checkout pickers.
• maintenance — still visible to admins but shown as (maintenance) and dimmed in pickers. A CFI trying to schedule against it gets a friendly block.
• archived — hidden everywhere except your historical reports. Use this for sold aircraft.

Updating an aircraft

Open any aircraft from the Fleet roster. Editable fields are the same as creation, plus:

• Document attachments — see Tracking aircraft documents.
• Reservations history — read-only timeline of past and current checkouts.

Why aircraft can't be moved between schools

An aircraft belongs to exactly one organization. Lessons, reservations, and logbook entries all reference the aircraft by ID, and we don't want a CFI at school A inadvertently logging time against a plane at school B. If a plane changes hands, support archives the old record and creates a fresh one at the new school.