Sandbox playtest: UX improvements and edge cases

Pilot conversion validation: in Sandbox 1, Atlas Globe Airways, on 19 Jul 1970 open Staff → Convert pilots at ORD. Select Boeing 727 as both the source and destination rating and enter 271 pilots. Both selections are permitted, but Convert remains disabled with only the generic “Choose the options above to see what it would do and cost.” Please prevent selecting the same rating or explain that the source and destination must differ. I cancelled without submitting.

Blank aircraft registration silently ignored: on 21 Jul 1970, open N116AG → Name and notes, clear the Registration field, and wait for the preview. It says “Nothing is paid now” and enables Save. Saving reports “Saved,” but reopening shows N116AG unchanged. A duplicate registration produces an explicit error. Please either require a registration and explain the blank value, or say that leaving it blank preserves the existing one. No other aircraft details were changed.

Duplicate fleet names: on 22 Jul 1970 in Atlas Globe Airways, Fleet → New fleet accepts the name “B721 ORD,” already used by the existing Boeing 727-100 fleet, for a new Boeing 727-100C fleet at ORD. Creation succeeds and the fleet list then shows two identically named fleets with different types. Please warn about duplicate names or distinguish fleets by type and base everywhere they are selected, particularly since the variants are not interchangeable. I deleted the new empty fleet after testing.

Empty management grant: in Sandbox 1 on 28 Jul 1970, open Atlas Globe Airways → Shares & control → Governance → Add a player. Choose an eligible player, then uncheck the default Schedules permission so that no area is selected. The completed preview says only “Nothing is paid now” and enables Grant, even though the dialog says the player acts in the areas chosen. Please require at least one permission or explain what a grant with no areas does, including whether the player receives notices. I cancelled without granting access; the submitted result was not tested.

Crew move selector suggests an ineligible hub: in Sandbox 1 on 10 Aug 1970, Atlas Globe Airways → Staff → Move crews selects cabin crew at ORD. Under To, choose Another airport and search JFK: the result is offered under “Hubs.” Select it and ORD’s spare 6; the client summary says the move makes 6 at JFK, but the completed preview rejects it with “JFK is not one of your crew bases.” Please distinguish hubs from eligible crew bases in the picker and explain how to establish a destination crew base, or prevent selecting ineligible airports. I cancelled without moving anyone.

Automatic check and aircraft location: in Sandbox 1, Atlas Globe Airways, N151AG’s page showed a C-check at ORD from 19 Jul 1970 18:23 to 3 Aug 16:41 while the aircraft was assigned AG232 ORD–SLC and AG233 SLC–ORD. AG232 departed 82 minutes late and arrived at SLC around 18:07 UTC. At 19:11 UTC, AG233 was Cancelled and N151AG was shown in its C-check on the ground at ORD; its last recorded flight had arrived at SLC, with no return or ferry shown. The check start time is not explicitly labelled with a time zone. Please reconcile automatic maintenance with the aircraft’s actual location and planned return, and show the time zone and affected flights before the check. The exact cause of the cancellation is not independently verified.

Next-check summary omits an earlier due check: on 24 Jul 1970 open N158AG. The headline says NEXT CHECK B, about 1 Sep 1970, while the checks list says A-check every month, by 10 Aug 1970, and B-check by 30 Aug 1970. The tooltip describes the headline as based on recent flying, but the A-check deadline is earlier than the displayed next check. Please show the earliest applicable date-based check as well as any usage forecast, or explain why the A-check does not count. I opened and cancelled the early-check preview; no check was scheduled.

Overdue check dialog defaults to C and hides A-check timing: on 25 Jul 1970, the notice says N152AG’s A-check is overdue (130 of 125 hours). Open N152AG → Send for check: the 11-day C-check is selected by default rather than the due A-check. Select A-check and As soon as possible: the completed preview says out of service from 25 Jul until about 25 Jul, approximately $4,057, with no start/end time, location or flight impact. At the time AG422 ORD–ORY was airborne and AG423 ORY–ORD was scheduled for 11:25 UTC. Please highlight the overdue check and show the planned time, location and any affected flights before scheduling, or explain how it fits around the existing rotation. I cancelled and did not verify an actual disruption.

Additional observed A-check example: on 30 Jul 1970, N113AG was on the ground at JFK and its next assigned AG290 was due at 11:50 UTC. The overdue A-check preview described it as “overnight” and said out of service until about 30 Jul, with no hours or affected flights. I scheduled it around 07:07 UTC; the aircraft page then showed an A-check from 07:07 until 18:09 on 30 Jul (the displayed check times did not state a time zone). AG290 and AG291 were reassigned to N155AG and still showed Scheduled, so no cancellation is established. Showing the actual duration, time zone and affected assignments before confirming would let players judge whether the work fits a ground interval.

Future checks shown as in work: in Sandbox 1 on 10 Aug 1970, Maintenance lists N118AG as Ready but its IN WORK column says “C until 29 Aug.” Open the aircraft: its C-check is scheduled from 14 Aug 07:08 to 29 Aug 06:20, yet the A, B and C rows each say “In work at ORD, 0% done,” while the aircraft is Ready and AG480 is scheduled to depart on 10 Aug. Please label future work as planned, show its start as well as its end in the maintenance table, and distinguish the check itself from the checks it will satisfy. The displayed check times do not identify a time zone.

Active check location conflicts with positioning origin: on 10 Aug 1970, N140AG’s aircraft page says it is In check, with a D-check at ORD from 3 Jun 21:16 to 14 Aug 04:57, 95% done. The same page says it is on the ground at JFK. In Flights → Position an aircraft, select N140AG and STL: the preview enables an empty flight from JFK on 14 Aug at 01:00, without explaining how the aircraft gets from the stated maintenance location to JFK. Please reconcile the aircraft location, maintenance location and planned positioning origin, or clarify if one is administrative. Times are displayed without explicit time zones in the check and preview. I cancelled without scheduling the flight; the operational result is unverified.

Frequency recommendation label: in Sandbox 1, Atlas Globe Airways, on 19 Jul 1970 select “Fewer on BOS–CHS” from the overview. The route flies three times a week at 41% full. The preset labelled “About 80% full” suggests two departures, but selecting it shows last week’s travellers would fill only 61% of the resulting seats, before allowing for lost demand. Please label the suggestion with its actual estimated load, or explain the approximation and constraints. I cancelled without changing the route.

Extreme ancillary fee: in Sandbox 1 on 20 Jul 1970, open Product & marketing and enter $999,999 for the economy bag fee. Save product reports success and the same amount persists in the summary after leaving and reopening the page, without a warning or displayed upper limit. Entering -1 instead silently becomes 0. Please show permitted boundaries and flag implausible fees before saving; also check whether extreme values can produce unintended revenue. I restored the bag fee to $0 immediately and did not verify passenger charges or economic effects.

Terminal gate input limit mismatch: in Sandbox 1 on 21 Jul 1970, open Airports & slots → Build a terminal at ORD. Enter 999 gates and leave the field: it silently changes to 120, but the completed preview says a terminal can have at most 60 gates and disables Start building. Entering 60 produces a valid cost preview. Entering 0 silently becomes 2. Please align the input and slider limits with the actual 2–60 range and communicate any adjustment. I cancelled without building.

Gate lease quantity: on 21 Jul 1970, open Airports & slots → + gates at ORD, where 89 gates are free. Enter 999 and leave the field: the input silently becomes 10 and the completed preview offers to lease 10. Please display the per-request limit and announce the adjustment, so a player does not accidentally lease fewer gates than requested. I cancelled without leasing.

Duplicate connection exceptions: in Sandbox 1 on 28 Jul 1970, open Product & marketing with Sell connecting itineraries enabled. Add BOS under Except at, then search for and add BOS again. Both entries appear; Save product reports success and both remain after leaving and reopening the page. Each Remove action removes only one entry, so a player may think an exception was cleared while the duplicate still disables connections. Please exclude or identify already-selected airports, or deduplicate on save. I removed both, saved, and confirmed the original empty exceptions list. I did not test passenger booking behavior.

First-day route readiness: in Sandbox 1 on 20 Jul 1970, plan BOS–MKC on B721 ORD once weekly, first available. The completed preview says “All 1 in its free time,” “Ready to plan,” starts 20 Jul and needs 9 of 9 aircraft; the expanded 27 Jul fleet preview also shows 9 of 9. After saving route 304, the first outbound AG540 was delayed 163 minutes. At 21:56 UTC, the aircraft assigned to it, N116AG, showed AG110 ORD–BOS scheduled 19:25 UTC and airborne, followed by AG540 BOS–MKC scheduled 19:35 UTC, before the incoming flight could arrive. A separate N103AG had been ferried ORD–MKC for the return AG541. Please show first-day positioning and any initial flight conflicts in the launch preview, or explain that its fleet fit is a representative future week rather than a guarantee for the start day. I have not established whether an operational disruption caused the reassignment or delay.

Route page confuses start date with first flight: on 27 Jul 1970, plan BOS–SYR on HS748 ORD once weekly, fitted on Sundays, with First available. The preview says starts 3 Aug and shows Sunday 16:15. After creating route 308, its page says “Its first flights are on 3 Aug 1970,” but the first listed outbound and return flights are on Sunday 9 Aug; 3 Aug is Monday. Please distinguish the effective start date from the actual first scheduled departure, particularly for less-than-daily routes. The first flight has not yet operated.

Frequency change preview conflicts with selected plan: in Sandbox 1, Atlas Globe Airways, on 22 Jul 1970 open BOS–CLT (route 306) → Change frequency and select Once daily (7). The selected “How it fits” option says “6 a week now” and lists six days, while the completed What happens preview says “7 a week from 22 Jul 1970” and enables Change frequency. The alternative “All 7 with another Boeing 727-100” reports that 10 aircraft would be needed but only 9 are available. Please make the summary and confirmation reflect the selected six-departure plan, or explain why seven will actually fly. I cancelled without submitting, so the committed outcome has not been verified.

Wet-lease preview overlooks future fleet use: in Sandbox 1 on 23 Jul 1970, Atlas Globe Airways → Fleet shows B732 ORD needs 3 of 3 aircraft from the week of 10 Aug. In Charters & wet leases → Offer a wet lease, select that fleet and another airline, select Every spare one (3), and leave the proposed 6 Aug–4 Nov dates. The dialog calls all three spare now and enables Send the offer with a three-month payment preview, without showing the scheduled August flying or its effect. Please check and display availability across the entire proposed period, including future routes, before sending. I cancelled; I did not send an offer or verify what would happen if accepted. The timetable explicitly says the fleet starts 50 flights a week on 10 Aug, needing all three aircraft.

First available can postpone a planned start: on 23 Jul 1970 open the 13 Aug start date for JFK–MKE (route 271), then choose Starting → First available. The preview proposes 19 Aug “once its crews are trained,” with 852 passengers rebooked, 114 refunded and $6,958 in disruption costs, despite the existing earlier planned start. Staff shows B737 pilot hires arriving 13–19 Aug. Please explain that First available may delay an already scheduled service and clearly contrast the old and proposed start dates and crew readiness. It is unclear whether the original 13 Aug start can actually operate with the available crew. I left the route unchanged.

Conflicting aircraft shortage counts: on 23 Jul 1970 plan BOS–SFO for one weekly departure with B704 ORD and First available. The fleet selector says 6 usable and 1 short. Once fitted, the suggestion says “All 1 with 3 more Boeing 707-420” and “needs 3 more aircraft,” while the blocking message directly below says it “would need 8 aircraft but has 7 available.” These numbers imply different shortages, with no explanation of the time or maintenance assumptions. Please reconcile the counts or label the dates and available-versus-total assumptions. I did not create the route.

Batch hides the blocking details: on 24 Jul 1970, plan BOS–SFO once weekly on B720 ORD for 23 Aug. The preview explains that the route needs two aircraft but only one is available. Click Add to batch: the destination clears, the detailed reason disappears, and Submit 1 plan is disabled. A generic “Get another Boeing 720” link remains, but the batch row only shows BOS–SFO and 1×, with no displayed start date, fleet, specific conflict or edit action. Please retain each plan’s details and validation reason in the batch and let the player edit it. I removed the test item without submitting.

Positioning flight lacks a cost estimate: on 24 Jul 1970, Flights → Position an aircraft, select N158AG at ORD and JFK. The preview says it will pay fuel and fees and “Nothing is paid now,” but gives no estimate of the later charge before enabling Fly it there. Please show an estimated total and its components, or explain why no estimate is available. I submitted this positioning flight (AG9726), which arrived at JFK for the fleet’s planned services.

Aircraft removal previews omit future schedule impact: on 24 Jul 1970, B732 ORD’s timetable says its 50 weekly flights start 10 Aug and need all three aircraft. Open N158AG → Move to fleet: No fleet is selected by default and the completed preview says only “Nothing is paid now,” enabling Move without showing the future shortfall. Store likewise enables Store and explains rent and a 10-day return to service, but does not mention the upcoming flying. Please flag affected future schedules and the number of aircraft still needed before confirming. I cancelled both previews; the operational outcome was not tested.

Idle fleet recommendation ignores upcoming commitments: on 30 Jul 1970, Atlas Globe Airways → Overview says B732 ORD flies its three aircraft 0.0 hours a day each and suggests another route or more departures to earn on idle time. The same page’s fleet table says 50 flights a week start from 10 Aug and require all three aircraft, with none spare. On 29 Jul, attempting PHL–BDL once weekly with that fleet and First available says it would need four aircraft, has three, and no start date fits planned deliveries and other flying. Please distinguish temporary idle time before planned services from sustainable spare capacity, and show the upcoming start or offer a time-limited option if the game supports one. The trial route was not created.

Monthly cash-flow closing balances do not carry forward: in Sandbox 1, Atlas Globe Airways → Finance → Statements → Months, inspect Statement of cash flows. May 1970 is marked closed and shows cash at close $163,924,425; June cash at start is $164,496,832, a $572,407 difference. April closes at $121,063,802 but May starts at $120,433,934, a $629,868 difference. June closes at $201,276,467 but July starts at $201,260,372, a $16,095 difference. Within May, start cash plus the displayed net change equals the stated close; the discontinuity is between periods. Please reconcile adjacent periods or show any boundary adjustment explicitly. This is a statement-display/reconciliation observation; I have not established whether underlying cash transactions are wrong.

Historical profit differs between statements: in the same company and month view, income statement net profit is -$521,549 for March, $8,717,567 for April and $19,068,117 for May: cumulative $27,264,135. The May month-end balance sheet instead shows Profit this year $26,535,555, a $728,580 difference. The annual statement’s current year-to-date net profit does equal the sum of the displayed monthly amounts. Please reconcile the historical balance-sheet figure with the closed income periods, or identify any adjustment and its effective date.

Fuel supply savings preview assumes the commitment without making that clear: on 26 Jul 1970, open Finance → Fuel → Sign a contract at BOS. The dialog shows recent usage of about 3,790 tonnes a month. Enter 999,999,999 tonnes and leave the field; it silently changes to 11,370. Select 3 years and wait for the completed preview: it shows 8.0% off and “SAVES ABOUT $31,775 a month,” with market price $0.035/kg, while warning only generally that buying below 90% of the commitment incurs a 15% shortfall charge. The savings figure is approximately 8% of the committed 11,370 tonnes at the shown price, about three times the discount on recent usage, and does not show the shortfall cost at that usage. Please label the volume assumption, estimate savings and penalties using recent usage, and show the input limit when clamping. I cancelled; I did not sign this contract or test actual charges.

Hedge “Most allowed” preset can be invalid: on 26 Jul 1970, with Atlas Globe Airways already hedging 5% through 16 Oct, open Finance → Fuel → Hedge fuel and select the preset “Most allowed 80%” for a one-year term. The completed preview rejects it: “at most 80% of fuel can be hedged; 5% already is during that term.” Entering 75% instead produces an enabled hedge preview. Please calculate the preset and slider maximum from overlapping hedges for the selected term, or label 80% as the total limit rather than the amount available to add. I cancelled without taking a new hedge.

Loan selection remains after repayment: in Sandbox 1 on 29 Jul 1970, Finance → Loans & bonds, select all 17 aircraft loans and repay them in full. The result says “Repaid,” debt becomes $0, and the table says “No loans,” but the toolbar still says “17 selected” and leaves Repay in full enabled. Clicking it opens a $0 preview that says “Not possible: choose the loans to repay,” with confirmation disabled. Clear removes the stale selection. Please clear repaid loans from the selection automatically when the transaction succeeds. The initial repayment was real; the second preview did not submit.

Maximum margin investment preset is rejected: in Sandbox 1 on 11 Aug 1970, open Atlas Globe Airways → Shares & control → Invest your capital → On margin. The dialog says up to $4.4M more can be borrowed, and offers “All you can borrow $8.8M.” Select it: the completed preview disables Invest and says the investment needs $8.8M more equity than the $4.4M available over the $94.5M needed for existing positions. Selecting “All you have $4.4M” instead enables Invest and shows a cash-funded payment of $4,399,996. Please calculate the maximum preset using the actual post-investment margin requirement, or explain the conflicting amounts before selection. I cancelled without investing.

Dividend minimum silently raises entered amount: in Sandbox 1 on 11 Aug 1970, Atlas Globe Airways → Shares & control → Pay a dividend, enter $0.001 per share and leave the field; it silently changes to $0.01. Entering $0 likewise changes to $0.01. With 15 million shares, the completed preview enables Pay for $150,000 and shows a $100,000 payment to the player. Please state the one-cent minimum and reject or explicitly announce an upward adjustment, particularly when zero was entered. I cancelled without paying a dividend.

Timetable optimizer gives contradictory fleet counts: in Sandbox 1 on 25 Jul 1970, open the B703B ORD shortage notice and let Improve schedules search for Fewer aircraft. The fleet has 11 aircraft, with 10 usable while one is in a check. The suggestion for the week of 27 Jul says AIRCRAFT NEEDED 11 → 11 and “11 of 11 aircraft needed,” but also says “That needs all 10 of the fleet’s aircraft, leaving none spare.” The page underneath says “Fits from the week of 27 Jul,” while the suggestion itself does not reduce the 11-aircraft requirement. Please distinguish total, usable now, and projected availability on the effective date, and avoid implying that 10 aircraft can cover a requirement of 11. I did not apply the suggestion.

Optimizer result and confirmation disagree: on 26 Jul 1970, open Timetable → HS748 ORD → Improve schedules → Fewer aircraft. The completed full suggestion for the week of 27 Jul reports AIRCRAFT NEEDED 10 → 9, with all five proposed route changes selected and “That needs all 9 of the fleet’s aircraft.” After the booking-impact preview completes, it instead says “10 of 9 aircraft needed from the week of 27 Jul 1970,” yet enables Apply 5 route changes. The selected changes were ORD–MEM, ORD–BNA, BOS–PHL, BOS–PIT and BOS–MSY. Please reconcile the search result with the final selected-change validation, explain any differing assumptions, and flag a remaining shortfall before applying. I did not apply it; the resulting schedule has not been verified.

Timetable calls a continuing route ended: on 26 Jul 1970, in HS748 ORD timetable choose the suggestion to reduce BOS–STL from 14 to 6 weekly departures, set From to 3 Aug, and apply it. Routes shows “Changes 3 Aug 1970” and “14 → 6,” with a new timetable taking over. However, select BOS–STL on the timetable chart and its route card reads “Ends 3 Aug 1970,” without saying that six weekly departures continue. Please distinguish the end of the current timetable from the end of the route and show the replacement frequency. The future schedule is shown in Routes; I have not yet observed the service after that date.

Cancellation notice links to a different count: on 29 Jul 1970 around 00:44 UTC, Notices says “6 flights cancelled on 28 Jul,” with 214 flown and six cancelled for no aircraft. Following that notice opens Flights for 28 Jul with Cancelled selected, but the page lists only two cancellations (AG232 and AG233), and says 157 flown. It labels the date as local departure date and still shows 24 upcoming flights, so differing day boundaries or an unfinished local day may explain the discrepancy; the notice does not explain its own period. Please make the linked list cover the notice’s exact period, or label both time bases and offer a way to inspect all six. I have not established which calculation is incorrect.

Fare ladder saves duplicate booking thresholds: in Sandbox 1 on 26 Jul 1970, open Fares & pricing → Booking ladder. The existing steps are 30 days / 90% and 0 days / 110%. Add a step (initially 21 days / 85%), change its days to 30 and leave the field. Both 30-day rows show “Same days as another step,” but Save ladder remains enabled and returns “Ladder saved.” Switching away and back shows three saved steps, including the duplicate. The help says the step with the most days not above the days left applies but does not explain which of two tied steps wins. Please block saving duplicate thresholds or define and display the tie rule. I removed the added step and saved again; the original two-step ladder was restored. I did not verify the prices actually charged during the brief test.

Fare ladder does not explain uncovered days: in the same ladder, remove the 0-day / 110% step, leaving only 30 days / 90%, then save. The page says “Ladder saved” and reopening shows one step. Its explanation says the step with the most days not above the days left applies, but no step meets that condition for bookings 0–29 days ahead and no fallback is described. Please explain the fallback fare in both the editor and chart, or require a day-zero step. I did not verify actual ticket prices; I restored the original 0-day / 110% step and confirmed the two-step ladder.

Fare percentage entry changes typed values: with the 0-day step at 110%, select its percentage text, type 125, and tab away. It displays 105 instead, without an explanation. Similarly, entering 110 into a newly added 0-day step produced 100; the + button could reach 110. Please allow intermediate input while typing and validate after editing so the value entered is preserved or an adjustment is explained. I reloaded without saving the 125 test and confirmed the original 110% remains saved.

Pricing rule accepts reversed distance bounds: in Sandbox 1 on 30 Jul 1970, add a pricing rule and select HND under touching (the preview says it reaches none of our 150 markets). Set distance from 2,000 km to 1,000 km and valid fare bounds of 150–200%. Save pricing reports success; switching tabs and back shows the seventh rule still has 2,000 to 1,000 km, without a warning. By contrast, a 150% floor and 50% ceiling is rejected with a clear error. Please reject or explain reversed distance ranges so a rule does not silently match no routes. I removed the test rule and saved, restoring the six existing rules; actual fare effects were not tested.

Cargo bid eligibility needs clearer status: in Sandbox 1 on 27 Jul 1970 open London Electronics (London–San Juan, 5,000 kg/week, 85% reliability required). The completed bid preview shows 175 kg scheduled in seven days, a 3,000 kg minimum, and 71% reliability. It says capacity and reliability must improve before the tender closes, yet enables Place bid. Submitting $1.04/kg reports “Bid placed” and the offer shows the bid with a Withdraw button. If bids may be placed conditionally and eligibility is checked at closing, please say so explicitly and label the bid as currently unqualified; otherwise prevent or reject the bid. I withdrew it immediately and verified the offer again shows no bid. I did not test award behavior.

Incomplete market rate silently ignored: on 28 Jul 1970 in Atlas Globe Airways → Cargo → Set rates, keep the existing 120% default, choose A different rate for one market, then Another market. Leave both From and To blank and the $0 field unchanged. The completed preview says “Nothing is paid now” and enables Save; submitting reports “Rates saved,” but Rates still shows zero market rates. Please require both airports before saving the chosen override, or explicitly say that only the default rate will be saved. The default remained 120%; no market override was created.

Market research reports no airlines on a heavily served route: in Sandbox 1, Atlas Globe Airways on 27 Jul 1970, commission Chicago–Los Angeles research for $1,215. The completed report says schedules of 3 Aug, AIRLINES 0 and “No airline sells journeys in this market on the day studied,” although the Markets table shows three airlines and 6,580 seats a week, and our ORD–LAX route 99 operates 21 weekly departures each way, including three on Mondays (3 Aug is a Monday). The report also shows 7,640 passengers each way flown last week. Please reconcile the report with the recurring timetable, or explain if the studied date is outside the generated booking horizon and prevent an empty result from being presented as no service. I have not established the underlying cause.

Repeat test on 30 Jul: commissioning the same Chicago–Los Angeles report for another $1,215 returned schedules of 6 Aug with AIRLINES 0 again, despite the market table still showing three airlines and 6,580 weekly seats. The updated report shows 6,930 flown last week. The report list now has only one Chicago–Los Angeles entry, dated 30 Jul; the earlier 27 Jul report is no longer visible. The page says reports are kept for 30 days, but the commission preview did not say a new report would replace an existing one. Please preserve prior reports for the stated period or clearly warn that a new report replaces the old one.

Wet-lease quantity input and cost preview disagree with fleet size: in Sandbox 1 on 29 Jul 1970, open Atlas Globe Airways → Charters & wet leases → Offer a wet lease and select B720 ORD, which the dialog says contains 1 aircraft. Enter 999 in How many aircraft: it silently changes to 2, and the per-aircraft dry-rent estimate falls from $37.9k/month to $19.4k/month; the suggested fair rent also drops from $99k to $78k. Select an airline and the completed preview correctly says the fleet has 1 aircraft and cannot lease out 2, with Send disabled. Please constrain and label the quantity to the fleet’s actual availability, and avoid presenting a per-aircraft cost derived from an invalid quantity. I cancelled without sending an offer.

Campaign duration limit mismatch: in Sandbox 1 on 29 Jul 1970, open Atlas Globe Airways → Product & marketing → New campaign, choose Airline-wide, and enter a zero weekly budget. The completed validation says a campaign needs a weekly budget and 1 to 104 weeks. Enter a positive budget, then type 104 weeks and leave the field: it silently changes to 52, with the end date and total calculated for 52 weeks. Entering 9999 also becomes 52. Please align the control with the actual supported limit and show any adjustment. I cancelled without starting a campaign; I did not test whether 104 weeks is accepted by the server.

Follow-up on BOS–STL timetable change: on 9 Aug 1970, route 307 confirms the replacement version runs from 3 Aug with six weekly departures each way, and AG342/343 operated on 7–9 Aug. However, the Flights tab continues to list the removed AG344/345 departures as “Cancelled” on every future date shown through 30 Aug, and also marks the non-operating Monday AG342/343 departures cancelled. Please distinguish flights removed by a planned timetable revision or non-operating days from operational cancellations, and filter superseded instances by default or explain their status. It is not established whether these entries affect cancellation statistics.

Slot-offer grid lacks accessible controls: in Sandbox 1 on 10 Aug 1970, open Atlas Globe Airways → Airports & slots → Slots → JFK → Offer to an airline. The outlined grid cells are clickable with a pointer (for example, Tuesday 14:00 selects one slot), but the accessibility tree exposes only the day and hour text, with no named controls for the cells. From the Price field, Shift+Tab moves directly to the airline field, skipping the grid. Please expose each selectable slot with its day, local time, available quantity and selection state, and support keyboard selection. I cancelled without sending an offer.

Slot offer price silently changes: in that same dialog choose an airline, enter -999 as the price, then select an available slot. The field changes to $0 without an explanation and the completed preview enables a free offer. Please reject negative prices with a clear message or announce the adjustment, so the player does not accidentally offer slots for nothing. I did not send the offer.

Marketing slider exposes a misleading accessible value: on 10 Aug 1970, open Atlas Globe Airways → Product & marketing → Marketing budget. At the saved Light setting, the text field and summary say $120,000 a week, but the accessibility tree exposes the “Marketing a week” slider value as 11,924,304. Select Steady: the field says $250,000 while the slider exposes 24,842,300. Please expose the actual dollar amount and units to assistive technology (for example with an appropriate value text), so the slider agrees with its visible budget. I returned the selection to Light without saving a change.

Another slider example: on 11 Aug 1970, Finance → Cash policy → Keep a cash floor defaults to one month of costs, displayed as $40,300,000. The accessibility tree exposes the Cash floor slider value as 4,000,000,000. Please check the shared slider value semantics across money controls. I returned to the original Borrow to cover it selection without saving.