There is a paradox any flight school owner recognizes: the hard part, which is training pilots, standardizing instructors and keeping aircraft available, the school does well. What gets stuck is the part that should be trivial: proving, on paper, that all of it happened.
Instruction happens in the air. Its evidence lives in a folder. And between the flight and the folder there is a chain of small frictions that consumes administrative staff, instructors and students, and that shows up all at once at the worst possible moment: when ANAC asks to see it.
The FIP is the school's most underrated document
The training record (FIP, ficha de instrução) looks like routine bureaucracy until the day one is missing.
The classic cycle: the instructor flies the mission and fills out the FIP afterward, sometimes at the end of the day, sometimes at the end of the week. The student needs to sign, but has already left. The record goes into the "sign next time" queue. Next time is a rushed flight, and nobody remembers. Multiply by 30 active students and the result is known: a folder full of technically pending records, and someone from the office assigned to chase signatures at the hangar.
The problem is nobody's laziness. It is the design of the process. The signature depends on the student and the paper being in the same place at the same time, and flight operations are exactly the environment where that happens least.
Competency is not assessed from memory
Modern instruction, and the Supplementary Instructions of the IS 141 series that govern the CIAC, pushes training toward assessment by competencies: it is not enough to record that the mission took place, you must record how the student performed in each element, mission after mission.
On paper, this becomes a dilemma. Either the school simplifies the assessment until it fits on the form (and loses precisely the granularity the method requires), or it keeps the granularity and creates a volume of paperwork the instructor cannot sustain between two flights.
And there is the less visible side effect: with the evidence scattered across physical forms, nobody sees the student's curve. Which competency is stuck? How many more missions does this student take than the average in the same phase? The data exists, in the folder, but in a format that answers no question.
The theory exam is a process, not an event
A paper exam seems simple: print, administer, grade. The real cost is around it: generating variations for those who retake, making sure the answer key does not circulate, grading by hand, entering the grade, filing the evidence that the assessment took place, per student, per attempt.
And access control matters more than it seems: a good exam is one that assesses the right student, at the right time, released individually, not a PDF file that crosses classes over WhatsApp.
The billing that leaks
Almost every school operates some model of monthly fee with an hour allowance and overage. With manual control, overage is what leaks most: the extra hour flown that does not become a charge because the office spreadsheet and the hangar flight record close on different days. It is revenue the school has already earned, since the flight happened, and that gets lost in the gap between two controls.
What to digitize first
If the school is going to tackle one thing at a time, the order that returns the most time:
- The FIP signature. It is the bottleneck with the most direct solution: the record is born digital at the end of the mission and the student signs by link, from their phone, wherever they are. The "sign later" queue ceases to exist.
- Competency recording. Structured assessment by element, in the standard the school defined, filled out by the instructor in minutes, and turned into a progress curve that can be queried, not a pile.
- The theory exam. The school's question bank, an exam released per student, grading and score in the same place, and the answer key out of circulation.
- The flight → billing link. If the recorded mission is the same one that feeds the allowance and the overage, there is no "closing" to diverge.
How Alis handles this
Alis's schools module was built in that order, together with real CIACs, aligned with the IS 141 series that structure the operation of the training center:
- Digital FIP with signature by link: at the end of the mission, the student receives the link on WhatsApp and signs from their phone. The record stays linked to the mission, the instructor and the aircraft, and the pending signature is visible, not forgotten in a folder.
- Missions and competency-based assessment, with EBT methodology: the instructor assesses by element, and the school sees the student's progress as a curve, phase by phase.
- Theory exam with a question bank and individual release per student: automatic grading, grade entered, an answer key that never reaches the student.
- Monthly billing with allowance and overage calculated from the recorded flight, the same record that feeds the logbook and the aircraft's history.
The combined effect is what paper does not deliver: the evidence of instruction is born ready, on the spot, and the audit becomes a lookup, not a task force.
If your school also manages fleet maintenance, it is worth seeing how this connects with maintenance tracking and with the electronic logbook, and the page on schools and CIACs shows the complete module.
This article is informational and does not replace consulting the current ANAC regulations or the formal guidance applicable to your training center. Specific requirements should be confirmed in the Supplementary Instructions of the IS 141 series in force.