Hi everyone / devs,
I recently started playing and bought a used Boeing 737-200 (PH-ZAN) with A, B, C, and D checks all overdue. After booking a refit at AMS (18 Sep 1988 – 29 Sep 1988), I noticed something odd with how the automatic maintenance forecasts are scheduling the overdue checks.
As shown in the attached screenshot, the automatic review predicts the following sequence after the refit finishes:
- Predicted A-check: 1988-09-30 (9h 36m)
- Predicted B-check: 1988-10-01 to 1988-10-02 (1d 9h)
- Predicted C-check: 1988-10-03 to 1988-10-18 (15d 10h)
- Predicted D-check: 1988-10-19 to 1988-12-21 (63d 21h)
In real-world aviation—and according to the game's own UI at the bottom of the window—a D-check "Covers 4 overdue requirements" and "The default covers all overdue requirements when a common covering check exists."
However, instead of scheduling a single D-check to clear all four overdue requirements at once, the automatic review seems to be queuing A, B, C, and D checks back-to-back, probably triggered in chronological order of their overdue dates (since the A-check has the earliest deadline of 7 Jan 1985). This adds about 17 days of redundant downtime and maintenance costs before the D-check even starts.
Is this just a visual quirk in the "Predicted" text showing hypothetical dates for each individual check, or will the automatic 02:00 UTC review actually execute them one by one from A to D unless I manually intervene and book the D-check myself? If it actually runs all four sequentially, shouldn't the auto-scheduler prioritize the single covering D-check?
Thanks!
