Skip to content
ATO Planner

Operations software for ATOs and general aviation

The day’s flight plan is built on one screen and published in one click.

From flight planning to evaluation forms, from weight and balance to licence currency, everything a flight school records lives in one place. No more moving between spreadsheets, WhatsApp groups and paper sheets.

Request a demo See how it works
Daily operations board 29 JUL · LTAS · Total 6:45
  • TC-AAB Landed
    ARSLAN / DEMİR E-14 08:15–09:30 1:15
  • TC-ADC Airborne
    KAYA / ÖZTÜRK N-06 09:00–10:45 1:45
  • TC-AEF Published
    YILMAZ / ŞAHİN ET-3 10:30–11:15 0:45
  • TC-AAB Published
    DOĞAN / DEMİR E-21 11:45–13:15 1:30
  • TC-AGH Draft
    ÇELİK / — PIC 14:00–15:30 1:30

You build the plan and publish the rows; instructors and students see the same list in their own panel.

Turkish and English · Data stays in Türkiye · Setup and migration included

Sound familiar

A flight school’s records scatter into five parts that never see each other.

Each part works on its own. The trouble starts between them — when an audit arrives, when a student asks how many hours they have flown, or when an instructor’s rating quietly expires.

The plan is in one file, what happened is somewhere else

The daily plan is built in a spreadsheet, then actual times go into a logbook. Reconciling the two becomes somebody’s month-end job.

Syllabus progress is on nobody’s screen

How many minutes a student has logged against each exercise is collected page by page. “Is this student ready for the skill test?” requires arithmetic.

Expiry dates live in someone’s head

Medical, class rating, IR revalidation. An expired document is usually noticed on the flight day, not while the plan is being built.

Forms sit in folders, signatures get chased

The evaluation form is printed, signed, scanned and filed. To find out which stage a form is waiting at, someone opens the folder.

From the application

Everything described here, on working screens.

These are not mock-ups made for the website; they are the application’s own screens. Personal data has been replaced with sample data.

Screenshot from the application
The daily plan screen: pick a student, the next exercise and eligible aircraft appear, and conflicts are caught before saving.
The daily plan screen: pick a student, the next exercise and eligible aircraft appear, and conflicts are caught before saving.
Screenshot from the application
The dashboard: today’s strip, pending approvals, the 30-day flight trend and fleet utilisation.
The dashboard: today’s strip, pending approvals, the 30-day flight trend and fleet utilisation.
Screenshot from the application
A student’s training card: exercise groups, logged minutes and remaining progress.
A student’s training card: exercise groups, logged minutes and remaining progress.

These are screenshots of the actual application; personal data has been replaced with sample data.

Scope

Ten modules, one database.

The modules are not separate products. They share the same aircraft, the same people and the same exercise records, so what you enter in one place is correct everywhere else.

Flight planning and daily operations

The planning screen is more than a calendar. It knows where each student left off, which aircraft is cleared for the exercise and who is actually free at that hour.

Explore

Student training records

You define the syllabus once as exercise groups. Every completed flight posts its time to the right exercise and the student’s progress card updates itself.

Explore

Weight and balance

Items, arms and envelope points are defined once per aircraft type. The instructor opening the form from a flight row only enters the load; the calculation and envelope check happen instantly.

Explore

Evaluation forms

You are not stuck with a preset template. You define the fields, options and scoring, and attach them to exercises. After that the system watches: who filled it in, who approved it, which one is still waiting.

Explore

Ground school and attendance

You define a lesson catalogue and plan lessons with instructors and student groups. Attendance is recorded on screen and feeds directly into each student’s ground exercise progress.

Explore

Fleet management

The fleet record is more than an inventory list. You define what each aircraft can be used for, and the planning screen narrows the options accordingly.

Explore

Licence and certificate tracking

Medical, class ratings and instrument rating currency sit on each person’s card with the days remaining. Anyone expired cannot be put on a plan, and reminders go out for anything about to lapse.

Explore

Reporting and analytics

Reports are not separate work — they are another view of the same data. You choose the filters, see the result on screen and export to Excel if you need to.

Explore

WhatsApp and notifications

If nobody reads email, there is no point sending notifications there. Flight plans and reminders go out over WhatsApp, with templates you write yourself.

Explore

Roles and audit trail

Permissions attach to roles rather than people, and roles are defined at screen and action level. Every change is written to the audit trail with its user and timestamp.

Explore

See all features

The life of a flight

One chain, from request to report.

These six steps run in order and each one inherits the data from the one before. You never type the same thing twice.

  1. 01

    Student request

    Students mark the days they are available from their own panel. Requests land on the planning screen.

  2. 02

    Building the plan

    Pick a student and their last flight, next exercise and the aircraft cleared for it appear. Arrival time is calculated from the exercise duration.

  3. 03

    Eligibility checks

    Before saving, the system checks: is the medical valid, is the aircraft already booked in that window, is the instructor flying elsewhere, does the currency interval still hold.

  4. 04

    Publishing

    You publish the day. Instructors and students see it in their own panel, and a WhatsApp notification goes out if you want one. Unpublished rows stay invisible.

  5. 05

    Actuals

    After the flight, actual times are entered — the fields arrive pre-filled with the planned values, so you only correct them. Weight and balance and the evaluation form open from the same row.

  6. 06

    Records and reports

    The time posts to the student’s exercise balance, the form enters its approval chain, and the flight appears in reports and Excel exports. Who changed what and when stays in the audit trail.

Who sees what

Every screen matches the job in front of it.

Permissions are defined by role; a user only sees and edits what they are authorised for.

Head of training
Fleet utilisation, student progress, overdue forms and documents about to expire, all on one panel. Everything waiting for approval sits in the action box.
Operations
Builds the daily plan, sees conflicts immediately, applies bulk status changes, publishes the day and prints it in the paper format.
Flight instructor
Today’s flights, actual time entry, weight and balance approval and the evaluation form. Their own certificate currency is on the same screen.
Student
Availability requests, published flights, exercise progress, total hours, PIC balance and the forms waiting for their signature.

Audit and data

Every record carries who changed it and when.

In flight school software the real question is not storing data, it is being able to account for it. Every change is kept with its user, timestamp and old and new values.

Full audit trail

Plans, forms, licences, student records — every change is traceable.

Role-based access

Permissions are set per screen and per action, with no per-person exceptions.

Data stays in Türkiye

Servers sit in a data centre in Türkiye, and you can export all of your data at any time.

Scheduled backups

Automatic backups are configured out of the box and can be sent to your own storage.

Resources

What we write about running a flight school

All posts

Operations 3 min read

Five common mistakes in flight school scheduling

Most scheduling mistakes come not from carelessness but from checking in the wrong place. The five we see most often in flight schools, and how each is prevented.

See it with your own data

We set up a demo account with your aircraft list and your syllabus. Build your own daily plan in it, then decide.

Request a demo See pricing

No setup fee, no commitment. We usually get back to you the same week.