Can an A check safely be scheduled with minimum turnaround times between 2 flights?
For example, on a 707: 55 minutes after the previous flight, and 0 minutes before the next flight (since no minimum turnaround is enforced by the system at the end of an A check).
Or does this produce the same 25% delay/cancellation risk that scheduling 2 flights with the minimum turnaround time does, and so you have to pad the schedule before and/or after the A check in order to keep your punctuality up?
Minimum time only applies to beginning of maintenance.Scheduling can start the minute after it without penalty.
Quote from: exchlbg on June 22, 2012, 07:46:05 PM
Minimum time only applies to beginning of maintenance.Scheduling can start the minute after it without penalty.
So to reduce days to 1% on a 707, I should schedule A check maintenance 1 h 30 minutes after the previous flight lands?
And the same thing for B check?
As I said. System doesn´t even accept maintenance without minimum turnaround time after last landing.Scheduling system tells you the next possible departure, that´s the minimum turnaround time. It applies to A and B as well.
Add: It´s fine to schedule just minimum turnaround for maintenance start, no penalty here.
You can schedule any check after the minimum turnaround time (%25). And then you can fly the airplane the minute after. So in the scheduling page there won't be any white spots between the check and the flights.
Quote from: exchlbg on June 22, 2012, 08:12:38 PM
Add: It´s fine to schedule just minimum turnaround for maintenance start, no penalty here.
I typically schedule the minimum turnaround (55 mins for a 707) between the previous flight and the A check. But it seems that those flights have disproportionately high delays when I look at my top "most delayed routes."
Is that just a coincidence, or am I getting the 25% delay rate due to using the minimum time, which will improve if I use 90 minutes instead of 55 between the previous flight and the A check?
The flight would be delayed before that 55min turn, because checks cannot be delayed per system. Sami dixit.
Quote from: ArcherII on June 22, 2012, 08:48:40 PM
The flight would be delayed before that 55min turn, because checks cannot be delayed per system. Sami dixit.
OK thanks for clarifying that. I was also having lots of flight cancellations right before the maintenance and did not know why.
So I should treat the space between the previous flight and the A check as a normal flight turn, and schedule it for 1 h 25 / 1 h 30 or whatever I normally use between two 707 flights?
Quote from: EsquireFlyer on June 22, 2012, 09:40:29 PM
OK thanks for clarifying that. I was also having lots of flight cancellations right before the maintenance and did not know why.
So I should treat the space between the previous flight and the A check as a normal flight turn, and schedule it for 1 h 25 / 1 h 30 or whatever I normally use between two 707 flights?
No need to do that. When the flight lands and stops engines for a subsequent A check, the turn only needs to be 55min. The Check will not be delayed as the system is designed for that to not happen.
If you encounter a severe delay in that flight, it will be due to a previous flight misfortune (Mx or Wx related) or in the turn in the middle destination, not the final destination.
To put it simply, if your A check is due at 00:00 and your flight arrived with a delay at 23:50, the A check will still be performed on schedule.
Ahhhh, another mystery solved I had the same problem of canceled flights was unsure why thought I just had bad luck.