The one seventy two was booked solid through Sunday. It is not flying today.
Aircraft on ground. Every idle hour is revenue you will never recover, and the logbook does not care how busy the weekend was.
Torgix flags it the moment the squawk lands. The issue, the work order, the part, and the paperwork, one record, audit ready.
And it prices the downtime in the only currency that matters: the bookings that did not fly.
You cannot stop machines from breaking. You can stop losing track of what it costs. Torgix.
Aircraft on ground differs from most equipment downtime in two ways, and both raise the stakes.
The first is that the revenue does not come back. A loader that misses Thursday can often work Saturday. A booked aircraft that does not fly on Saturday has lost that slot permanently, because the customer flew with somebody else or did not fly at all. Utilization is the whole economic model, so idle hours are not an inconvenience, they are the product not being sold.
The second is that the paperwork is not optional. Maintenance on an aircraft has to be recorded to a standard that survives inspection, which means the record of what was done, by whom, against which component and at what time in service is part of the job rather than an afterthought. A faster turnaround that leaves the logbook incomplete is not faster, it is a deferred problem.
What the video shows is those two requirements handled in the same pass. The squawk lands, the issue and work order open against the specific aircraft, the part is matched, and the documentation is produced as a by-product of the work rather than reconstructed later from memory.
The costing runs alongside it. Time in service, maintenance cost and idle hours attach to the tail number, so the question of which aircraft is actually earning has an answer that does not depend on anybody's recollection of the season.