You can do everything real airlines can - Lower prices / temporarily change to smaller aircraft, take a loan if you are about to run out of money due to temporary problem and so on.
There's not that much airlines can do to these things IRL either.
Airlines sell tickets months in advance. If bird flu hits, they don't lose revenue as the cash is already in the bank and most tickets are nonrefundable, that is they become a credit on the books for future flights if they cancel. Thus, when events like this hit the have a significant period of time to make adjustments before it ever hits their top line with the exception of volcano eruptions.
IRL airlines can layoff staff or even offer early retirement buyouts for sustained periods of lower demand. Other players say it is the same as a fuel spike--not true. A fuel spike results in increased expenses. When you have large revenues, you can cover a lot of expenses such as a fuel spike. If demand plummets, you have no revenue, which is why it is such a problem. Furthermore, if you get hit on the CI side you end up getting penalized for months after the event is over.
Also in terms of tools, AWS is lacking when it comes to price management as the current price management tool is not nearly robust enough to effectively manage hundreds of routes when they are affected by massive events that drop demand. Temporarily switching to smaller aircraft is an option IRL because airlines, again, will sell tickets months in advance and know with high levels of confidence how many people will be on the aircraft. I was supposed to fly on the 787 Dreamliner last March, but then they got grounded. The return flight was replaced by a smaller 767, but they could only use a smaller aircraft because they knew how many seats were sold--something that can't be done in AWS.
This is a simulation and it will never perfectly reflect reality, but having events without the proper tools to react is basically telling players to bend over and take it. For example, if there is a 40% drop in demand and you fly a route 2x/daily at 900 and 1400, you don't have the ability to (without huge headaches) fly the route one day at 900 and the next at 1400 to pare back to 1 flight/day with high load factors instead of 2 flights/day with low load factors. You could then furlough part of your cabin crew etc. and fly with higher load factors, which is what most airlines would do IRL. The net result would be flying 1x/day with low profit margins on a temporary basis versus 2x/day and bleeding losses.
Since the stats available are largely backward looking, making these modifications in real time is extremely difficult, especially when the main interface values are based on a trailing 30 days--you might not know there is an issue until a month after the fact.
So while the events can suck, you can't argue that the tools are currently lacking to make temporary adjustments for events lasting only a few months, which is why so many players are frustrated and these posts keep popping up.
Taking it even a step further, since events can only happen so frequently players can prepare on the other end of the spectrum. For example, volcanoes only happen ever 20 years or something like that. We just had a volcano in GW2 in North America, which means I don't have to worry about having that big of a cash cushion because we already had our big event.
It seems the easiest solution to help mitigate the effect of events is acknowledge that many employees are not exempt (salaried). Flight attendants get paid only when the aircraft is in the air. Ground handling, security, etc. are all hourly employees, so if they don't work they don't get paid. As it stands now, all of those hourly positions are being compensated as if they are exempt/salaried and are getting paid whether they show up for work or not.