Pi1otguy
Pattern Altitude
I keep a picture of the F4 Phantom as my desktop at work as a reminder to consider the implications of changes we may make to software or procedures for others at my workplace. I draw parallels between the Phantom's early issues and changes/upgrades we make that could make things tough for our users.
I just wanted to sure I wasn't completely mischaractering the F4 when I explain it to coworkers (in fairly simple terms). Essentially this a small 5 min conversation about why I might be hesitant to get on board with a change right away or request extra testing time when working with other groups.
-------
The F4 (A lesson in managing systems and procedures)
Several decades ago the F4 was designed and built. It was an advanced fighter with very advanced electronics and missiles for it's time. The designers believed it would down enemies 20+ miles away and that guns were obsolete so decided not to include one.
Later on, this very advanced jet ended up in the Vietnam war but the rules from higher up the chain forced them to get close to and visually identify each enemy before taking them down. But that also wiped out their main advantage and often forced them to start fighting from a bad position since heat seeking missiles of that era had issues in certain dogfights. A few half second bursts from a gun would have made all the difference to a great many pilots.
They tried after the fact to add a gun pod on the bottom, but it wiggled in the wind so much that it was too hard to hit a target. Finally, after a few years they installed a proper gun and the Phantom went on to be great fighters of it's time and was still in use by several countries up until a few years ago. But on the way, many pilots suffered simply because someone higher up the chain slightly removed from work in the "real world" decided to remove a vital tool in the name of efficiency and such.
I just wanted to sure I wasn't completely mischaractering the F4 when I explain it to coworkers (in fairly simple terms). Essentially this a small 5 min conversation about why I might be hesitant to get on board with a change right away or request extra testing time when working with other groups.
-------
The F4 (A lesson in managing systems and procedures)
Several decades ago the F4 was designed and built. It was an advanced fighter with very advanced electronics and missiles for it's time. The designers believed it would down enemies 20+ miles away and that guns were obsolete so decided not to include one.
Later on, this very advanced jet ended up in the Vietnam war but the rules from higher up the chain forced them to get close to and visually identify each enemy before taking them down. But that also wiped out their main advantage and often forced them to start fighting from a bad position since heat seeking missiles of that era had issues in certain dogfights. A few half second bursts from a gun would have made all the difference to a great many pilots.
They tried after the fact to add a gun pod on the bottom, but it wiggled in the wind so much that it was too hard to hit a target. Finally, after a few years they installed a proper gun and the Phantom went on to be great fighters of it's time and was still in use by several countries up until a few years ago. But on the way, many pilots suffered simply because someone higher up the chain slightly removed from work in the "real world" decided to remove a vital tool in the name of efficiency and such.