Human Factors

Tiger teams have been long used for problem-solving and or responding to opportunities (Laakso et al., 1999). Tiger teams are not just another form of a team with a set of resources. They are formed differently, used for episodic actions, and then released when the task is complete. In most cases, tiger teams are used for solving difficult problems in a timely way. Given this reason. these teams are formed with a purpose and bring specific skills (Pavlak, 2004). They are also created to self-sufficient and complete in terms of skills and capacity.

As a manager researching flight management system (FMS) issues, I would bring a group of resources with the required skill sets and more importantly experience. The skills needed would include, hardware, software programming, testing, and automation. I would also include subject matter experts from flight control, navigation, avionics, navigation data, and computational expertise. The team will also comprise resources from external partners for hardware, the operating system, and any other sub-components that were externally sourced. I would also ensure that escalation paths are clearly identified within each of the external organizations in case, such escalations were required to ensure priority and timeliness in those organizations.

Once the team has been formed, interaction cadence is important. When and where will they meet, how often and who leads the team – becomes important. Establishing a team leader helps with this process. Setting up a ‘war room’ will be essential to collate all the necessary design artifacts and incident reports. that will help troubleshoot the issue. A flight management system simulator will be required and set up. The simulator will help in reproducing the navigation guidance issue(s).

Robust system design “ensures that future systems continue to meet user expectations despite rising levels of underlying disturbances” (Mitra, 2010). The intent of the robust design is to allow a system to function reliably, perhaps with reduced capability, despite errors in input or computation. Systems are designed to accommodate a vast range of operating conditions and inputs. Despite that, every system has its limits where outside of that operating envelope, the system does not have the intelligence to handle the situation (Atkins et al., 2006). In the given FMS situation, without more detail, it’s hard to conclude that the system is either robust or not. Regardless of how holistic and intelligent a system is, once outside of its programmed boundary, the system would not know how to handle a specific problem. In 2008, Qantas flight 72 suffered an uncommanded loss in altitude now associated with a bit being flipped in the flight management system caused by ionization radiation (See Baraniuk, 2022 for more information on computer bit flips due to solar radiation associated solar flares). This is an example of ‘yet to be known’ factors that could impact the robustness of a system.

Typically redundancy is used as a mitigation for safety-critical systems. Having backup systems is an effective strategy for dealing with insufficient robustness (Mitra, 2010). Multiple of input sensors allow for differentiation models to detect differences and when supplemented with a tertiary sensor, allow for triangulation and therefore detection of an impending problem (Bijjahalli et al., 2020). In the case of software systems, where complex logic can be the cause for errors, exhaustive testing of all code branches and automated testing of multiple-programmatic paths is typically used to prevent an isolated line of code to cause an error (Huhns, & Holderfield, 2002). Data is another cause for the lack of robust behavior because systems are as precise as the data provided. Data verification and validation are the mitigation for this cause.

Ideally, it is best to build systems such that if it’s unable to compute an answer within its defined operating envelope, it must signal such failure to the crew and allow them to resolve the situation. That said, differential input computations led to the autopilot on Air France 447 disconnecting at 35000 feet over the Atlantic leaving the plane in the crew’s hands (Admiral Cloudberg, 2021). In the final analysis, the crew stalled the airplane and all data indicates that the controls were held in high pitch position all the way to its final impact. This indicates that using reverting to manual control as a means of robust design may also not be the best answer for all situations.

Human input is a common problem and protecting a system from erroneous input is perhaps the most significant challenge for designers (Atkins et al., 2006). To anticipate the various inputs that numerous users of a system could potentially input into a system is an extraordinary challenge for any designer. American Airlines flight 965 to Cali, Colombia impacted terrain from an erroneous input into the FMS (Ladkin, 1996). Rushing through an approach at an airport without operational radar, accepting a different approach than earlier planned and programmed, clearing the programming from the FMS to execute a visual approach, and rushing through FMS waypoint entry without verification with associated charts are reported to be the most probably causes (Pérez-Chávez & Psenka, 2001). There are more causes that came together as explained in Reason’s Swiss cheese model that contributed to the crash (Reason et al., 2006). Other factors included a single letter identification for a navaid 150 miles away which with some diligence and attention, could have been easily detected if the crew was not rushing. A single letter – R – indicating two different navaids ROMEO and ROZO – caused the airplane to make a sharp left turn and head straight into the terrain. Preventing error input is typically used to maintain the operational boundaries of a system. However, this could prove limiting in itself.

The first task for the team will be to reduce the errors as much as possible. This allows for a close study of the problem. Documenting the causes in fishbone diagrams allows for listing all causes that could have led to the issues. Taking each case individually to further resolve them would lead to resolution of the issue. The benefit of using a tiger team for this purpose is to have undistracted bandwidth to focus on the issues on hand.
There is no perfect answer to designing robust behavior. It is as much art as it is a science to build a complex, comprehensive design. Achieving perfect design is an ongoing challenge and it is worthy of mention that automation and human factors issues remain a serious concern for the aviation industry even today.

References:
Admiral Cloudberg. (2021, October 9). The Long Way Down: The crash of Air France flight 447. Medium; Medium. https://admiralcloudberg.medium.com/the-long-way-down-the-crash-of-air-france-flight-447-8a7678c37982Links to an external site.
Atkins, E. M., Portillo, I. A., & Strube, M. J. (2006). Emergency Flight Planning Applied to Total Loss of Thrust. Journal of Aircraft, 43(4), 1205–1216. https://doi.org/10.2514/1.18816Links to an external site.
Baraniuk, C. (2022, October 12). The computer errors from outer space. Bbc.comLinks to an external site.; BBC. https://www.bbc.com/future/article/20221011-how-space-weather-causes-computer-errorsLinks to an external site.
Bijjahalli, S., Sabatini, R., & Gardi, A. (2020). Advances in intelligent and autonomous navigation systems for small UAS. Progress in Aerospace Sciences, 115, 100617.
Huhns, M. N., & Holderfield, V. T. (2002). Robust software. IEEE Internet Computing, 6(2), 80-82.
Ladkin, P. (1996). AA965 Cali accident report. University of Bielefeld.
Laakso, M., Takanen, A., & Röning, J. (1999, June). The Vulnerability Process: a tiger team approach to resolving vulnerability cases. In Proc. 11th FIRST Conf. Computer Security Incident Handling and Response.
Mitra, S. (2010). Robust System Design. 2010 23rd International Conference on VLSI Design, 434–439. IEEE. https://doi.org/10.1109/VLSI.Design.2010.77Links to an external site.
Pavlak, A. (2004). MODERN TIGER TEAMS.
Pérez-Chávez, A., & Psenka, C. (2001). Systems accidents and epistemological limitations: The case of American airlines’ flight 965 in Cali, Colombia. Practicing anthropology, 23(4), 33-38.
Reason, J., Hollnagel, E., & Paries, J. (2006). Revisiting the Swiss cheese model of accidents. Journal of Clinical Engineering, 27(4), 110-115.
Pavlak, A. (2004). Modern TIger Teams.

Notes on Instructing and Learning

What comes to mind when you think of ‘good instruction?’
Instruction basically means to direct or help acquire a skill or help ‘do’ something.

Good instruction is about providing steps on ‘how to do’ something in the simplest but most effective manner. Ultimately the test of good instruction is how quickly a learner can acquire the skill being taught and how effectively that Individual can demonstrate gained proficiency.

What were your most profound (positive or negative) learning experiences?
The one experience that comes to my mind is my flight training experience.

My instructor was an individual who learned to fly in Hawaii, in times when flying was not as regulated or complicated. Making learning a fun experience was his primary goal. He deeply believed that when you enjoy something, you learn faster. He also grew up in aircraft that were basic. Hence his stick and rudder skills were so much more effective. He was a natural at flying. More than all the theory he provided me (which I got from my textbooks also), his attitude towards flying and instructing struck me as most powerful. I went from zero to solo in 20 days. He would wake up early so that I could fly early mornings before I got to work. We flew every morning at 5:30a or 6a. He would demonstrate how every runway, however short, was long enough if the proper technique was applied.

I got my PPL. However, I took away more about attitude and instruction from him, than simply flying skills.

How does it feel to teach someone how to do something?
I have always had a passion to explain concepts, events, machines, and weather phenomena to those interested in it. I have a natural ‘coaching’ style when it comes to building teams at work. I have had the privilege of running 300-400 person teams and my instinctive style is to coach and allow individuals the latitude to express themselves. I run a flight simulation venture that I started out of a deep passion for simulator technology combined with a passion for teaching/instructing. I began teaching at a university in Chicago over a decade ago only because I wanted to ‘pay it forward’. Shaping minds, and creating the next generation of professionals give me immense pleasure. One-half of my 30-year career has been in building and operating technology platforms for Higher Education. In that context, I was privileged to develop algorithms for adaptive learning and competency-based learning models. I used it as an opportunity to deploy my learning as a student and an instructor into new models for learning and instructional design. To me, teaching and/or instructing a learner is a profoundly rewarding experience. This is also the reason why I took an adjunct role at ERAU.

When teaching someone how to do something, what strategies do you use?
Modeling elements from the ‘real environment’ is essential. Creating an environment that mirrors the environment in which the knowledge or skill will be applied is essential for the effective transmittal of knowledge or skill. Hence I try to recreate elements from the ‘real environment’ in the teaching process.

I also enable a student as many learning aids as possible.

Different learners learn differently. Hence teaching style has to adapt and I adapt as needed. For some, visual aids are effective, others learn better by listening and some do well by ‘doing’. I use any or all of these channels.

Explaining underlying theory to the extent needed substantiates learning. Mixing theory with practice is another strategy for the effective transmission of knowledge. The learner must feel the joy of learning something. Being able ‘to do’ something, and being able to apply the knowledge or skill is very effective in reinforcing learning. There are times when I create a phenomenon and I ask the student to explain why it’s occurring.

Chunking learning into smaller segments is another strategy. Especially when learning is ‘chunked’ into segments that collectively and cohesively aggregate to a larger whole, knowledge or skill is transmitted effectively.

Current-day technology allows for several techniques to ‘gamify’ learning and bring a sense of challenge into the learning process. The human psyche likes a challenge – however, care must be exercised to ensure that it is not perpetually overwhelming where it can introduce a sense of “I can never win this’. Hence adaptive learning is powerful. Using Machine Learning techniques, the system can be engineered to adapt to skills/success levels and introduce the challenge in a controlled manner where the learner is challenged, but a little bit at a time, and knowledge or skill is built over time.

How do you know if a learning experience was successful?
Measured assimilation is the true test of success in learning. Can the learner explain a concept effectively and have an audience understand it? Can a student now fly effectively and within standards? These are examples of success in learning experiences.

Exploring a data-driven connection between astronomical movements and life events

In my study of Eastern astrology, I learned a principle that correlates planet Mercury’s movement across the zodiac with higher rates of transportation and communication breakdowns. Each year the Internet is filled with articles on this topic (Kerr, 2022; Lonely Planet, 2021; Tips for Mercury Retrograde, 2021; Travel during Mercury Retrograde, 2016). There are several books written on this subject (Boland & Farnell, 2018; McGuirk, 2016). With the exception of work by Qi, Wang, and Zhang (2022), most of this literature is not data-driven.

I am motivated to explore this correlation in the realm of flight delays and cancellations.

Question: Is there really a higher incidence of flight delays and cancellations during time periods when the planet Mercury goes into retrograde motion?

Hypothesis:

H– There is a significantly higher incidence of flight delays when planet Mercury goes into retrograde motion in its orbit around the zodiac.

H– There is not a significantly higher incidence of delays when planet Mercury goes into retrograde motion in its orbit around the zodiac.

This would be a quantitative experiment method and a non-experimental (correlational) design.

Publicly available archived flight delay and cancellation datasets should serve the data needed for this experiment. 

References:

5 Tips for a Mercury Retrograde-Proof Vacation. (2019, October 21). Expedia Travel Blog. https://www.expedia.com/stories/5-tips-for-a-mercury-retrograde-proof-vacation/Links to an external site.

Boland, Y., Farnell, K., 2018. The Mercury Retrograde Book: Turn Chaos into Creativity to Repair, Renew and Revamp Your Life. Hay House UK.

Buckley, J. (2022, April 16). Experts are predicting a summer of travel chaos. Here’s why. CNN; CNN. https://www.cnn.com/travel/article/travel-chaos-summer-2022/index.htmlLinks to an external site.

Kerr, J. (2022, January 14). Everything you need to keep calm this Mercury retrograde 2022. CNN Underscored; CNN. https://www.cnn.com/cnn-underscored/health-fitness/mercury-retrograde-2022Links to an external site.

McGuirk, L. (2016). The Power of Mercury: Understanding Mercury Retrograde and Unlocking the Astrological Secrets of Communication. United States: HarperCollins.

The dos and don’ts of traveling during Mercury Retrograde – Lonely Planet. (2021, July 7). Lonely Planet. https://www.lonelyplanet.com/articles/travel-mercury-retrogradeLinks to an external site.

‌Travel during Mercury Retrograde. (2016, January 22). AFAR Media; AFAR Media. https://www.afar.com/magazine/5-ways-to-survive-a-mercury-retrograde-while-travelingLinks to an external site.

Qi, Y., Wang, H., & Zhang, B. (2022). Long Live Hermes! Mercury Retrograde and Equity Prices. Mercury Retrograde and Equity Prices (April 4, 2022).

Flight Simulators and STEM Learning

Why do Flight Simulators Help Children Understand STEM Concepts Better

Simulators have long been used in aviation, medicine, and engineering to train professionals, but their value in education—especially for children learning STEM (Science, Technology, Engineering, and Mathematics)—is just beginning to be fully appreciated. From flight simulators to virtual robotics labs, simulations help make abstract STEM concepts real, engaging, and memorable. But why do they work so well?

1. They Make Abstract Ideas Tangible

STEM subjects often deal with invisible forces—like gravity, electricity, or air pressure—that are hard for kids to visualize. Simulators transform these abstract concepts into visible, interactive models. For instance, a flight simulator lets students see how lift and drag affect an airplane in real time, rather than just reading formulas in a textbook.

When children can manipulate variables and instantly observe the effects, they’re not just memorizing facts—they’re building intuitive, long-lasting understanding.

2. They Engage Multiple Senses and Learning Styles

Simulators are multisensory. They combine visuals, sounds, motion, and hands-on interaction to create a rich learning environment. This appeals to a wide range of learning styles—kinesthetic learners benefit from the physical interaction, visual learners from animations, and analytical thinkers from the data feedback.

This sensory integration deepens cognitive engagement and helps more students stay focused and motivated.

3. They Encourage Active, Experiential Learning

Unlike passive lectures or textbook work, simulators require students to do something—to test, try, fail, and try again. This active learning is essential for developing problem-solving skills, especially in STEM.

Simulations put learners in the driver’s seat. Want to see what happens when you increase the voltage in a circuit? Change a variable and observe. Want to test a new wing shape in a wind tunnel simulator? Do it and measure the result. This trial-and-error approach mirrors how scientists and engineers work in the real world.

4. They Foster Curiosity and Exploration

Simulators are safe spaces for experimentation. There’s no real danger or cost to making a mistake, which lowers the fear of failure and encourages curiosity. Kids are naturally inquisitive—and simulations let them play with STEM in a way that feels like exploration, not just instruction.

That sense of freedom turns learning into a game-like experience, where discovery becomes its own reward.

5. They Build Connections Between Concepts

Simulators often integrate multiple STEM disciplines at once. A simple drone flight simulator, for example, can introduce physics (forces of flight), math (trajectories and measurements), engineering (design of aircraft), and even programming (autonomous flight). This cross-disciplinary exposure helps children see how different STEM fields are connected—and how they apply to real-world challenges.

Conclusion

Simulators transform the way children learn STEM by making complex ideas interactive, visible, and exciting. They support deeper understanding through experience, trial, and play—turning passive learners into active explorers. In a world where STEM literacy is more important than ever, simulators are a powerful tool to light the spark of curiosity and build the foundation for lifelong learning.

CJ

Software Engineering – too much velocity?

Velocity – this is something we hear about almost so frequently in the software engineering world. There is an ever-increasing demand for speeding up software development, automating code engineering and testing, and, more recently, even using voice recognition to generate code automatically.

It’s about time that, as an industry, we slow down a little and ask whether we need all this velocity and how much is good enough. Moderation is a beneficial approach, applicable to all aspects of life, including software engineering. This relentless pursuit of faster software development is beginning to cause harm in multiple ways – to products and people. More often than not, it has resulted in nothing more than poor quality. While it may be fashionable to speak about digital transformation, velocity, speed, and the like, it is beneficial to pause occasionally – such a break will most likely reveal that unfettered speed in any context is mostly unnecessary, and left uncontrolled, leads to dissipated energy. 

In the context of software, this leads to wasted productivity cycles. In the name of AGILE, process is thrown to the winds, and quality suffers. There are very few – really a small percentage – of software outcomes that are AGILE. The rest of those efforts are simply following no process at all and riding their luck – and because it’s no more fashionable to call software processes anything else, we want to call it AGILE, even if we are failing to execute waterfall projects successfully. Most teams are merely cleaning up defects from a prior sprint in the next sprint, but call themselves AGILE teams because that is what sells. 

Software is incredibly pervasive… and that’s a powerful thing. However, if software engineers don’t pace themselves appropriately, this very pervasiveness could ultimately become a curse. 

CPJ

Task Management on the FlightDeck

One of the highlights of this week’s readings was the aspect of coherence (Salas & Maurino, 2010). For coherence to be effective, pilots need to have a deep understanding of the underlying logic, systems and automation impacts. The cognitive load has grown significantly over the years and continues to grow even faster today. While it is possible to acquire and display a lot more data in the form of meaningful information on extra-rich customizable displays, an important consideration would be to understand at what point this reaches practical human limits.

In the end, there is no limit on information that can be provided or assimilated by the crew. What matters is how much can be meaningfully assimilated in limited amounts of time (many times minutes or seconds) and most importantly, acted upon to achieve an outcome.

Information overload occurs frequently and very rapidly. My observation is that a few different visual and aural call-outs occurring simultaneously (example: a GPWS callout and a TCAS alert) are enough to cause overload in an otherwise quiet flightdeck. If they occur to be in conflict its worse.

With rising stress levels, saturation occurs faster (Salas & Maurino, 2010).  The ability to filter, and hone in, on important elements of information being presented is the answer to avoiding overwhelm. I believe that this ability is a function of two things – a) experience and b) personality.

CJ

References

Salas, E. & Maurino, D. (2010). Human Factors in Aviation (2nd Ed.). New York: Academic Press.