Since you chose not to fly and some other guy continued to fly, I suppose you can show us the NTSB report of the in-flight Wong separation that you avoided, by eliminating your personal risk.
Yes, I can, with five different aircraft. Two of them resulted in actual separations, killing everyone. The other three did not, but developed cracks that grounded the aircraft. Four different operators, entirely unrelated. In the case of a fifth operator that developed such cracks making the sixth and seventh aircraft, I refused to fly at all for the operator. NTSB reports, therefore, exist for two mishaps of that group, and both are well documented, albeit with very incorrect public perceptions Not my first rodeo.
Doug you're a professional pilot, you've filled out a risk assessment yes?
No. We don't do that.
I have several examples in files at home. I don't use them, and no operator for whom I've flown does. The closest was one operation in Iraq to whom I was attached, that used a computer-based fatigue-management system. Their program didn't accept fatigue, but did set flight and duty limits based on certain factors. If they found we were flying too much, according to the program, we'd get flagged with a notice to take time off. You could say it was a risk assessment, but it wasn't. It was a simple algorithm that spelled out a pre-determined amount of flight and duty. Because of the nature of our operation, I regularly timed out and ended up being stood down for a day until the program dictated that I could fly again.
The program for which I'm operating presently has no duty or time limits, and prescribes no days off. Each operation, each company, each organization, each agency, etc, is a little different. Different policies, different regulations, different contracts. I work for several different employers, and wear several different hats; some simultaneously (double dipping, if you will), sometimes. Others are seasonal, and sometimes it's just one employer. Some assignments come and go. Sometimes I need to balance one against the other. For certain kinds of flying, for example, the FAA dictates that any and all commercial flying is cumulative to flight time limits. If I fly 121, for example, I must also count other commercial flying such as ag or firefighting, toward my cumulative limits, but only when considering my limits for 121. Firefighting doesn't care, but contractually has it's own limits applicable to the fire operations. No risk assessment is filled out in either case.
My job (HEMS), has some of the riskiest flying you can do, but I accept it and embrace it.
I flew medevac, air ambulance, organ transport, and other duties for a number of years, for several different operations. I never considered it risky (any more than the firefighting I'm doing right now), and never had a problem refusing a flight, dictating we use a different time, location, routing, or take a delay) in the interest of safety. I still don't. In the last two days I've stated we won't use a particular airport, for example, do to crosswinds, in the interest of safety. Two days ago I refused a drop requested by an air attack, to support a dozer near the head of an active fire. I counter-offered another drop that I could do safely, and we did that. Nobody wants to see us put an aircraft in the ground; not me, not the air tactical group supervisor, not the incident commander, not the dozer operator, and not the reporters following the event on the ground or in the air. We're there to do a job and do it safely, and we don't help anyone if we can't do that.
I've flown firefighting operations for many years. I don't embrace risk as part of that operation, but I do engage in a steady, unrelenting systematic process of risk elimination. There will never be a time when this process is done, before, during, or after a flight. We don't use a matrix or risk assessment, but we do consider the operation on a segmented and holistic basis as needed.