Major Plane Crashes Are Always Technology Failures, Not Human Error

Reading Time: 2 minutes

There have been a number of plane crashes in the United States this year. While traveling by air has never been safer, what types of technology can help prevent the catastrophes when things go wrong? Following every crash, the National Transportation Safety Board (NTSB) conducts an investigation to learn more and improve airplane safety procedures and policies. What the NTSB learns from an investigation will detail what events occurred or failed to take place. Total system integration is vital in taking dispersed data sets from different systems in the air (information from the black box) correlated with support systems on the ground (traffic control data) to improve processes dealing with critical and routine events.

Recognize Events

Events such as overheated engines or wing malfunctions are bound to occur, considering the vast number of flights a day. These are simple for data systems to register and then have technicians automatically repair based on workflow software. A system not reporting is usually just as important, but not as easily tracked. A gauge or alert not working properly is much more difficult to spot and test for, and, because of that, more likely to cause serious problems. When tragedies such as plane crashes occur, we always ask: What happened? In some cases it’s just as important to ask: What didn’t happen?

Event-Enabled Customer Service

Event-processing software is crucial in situations like plane crashes. A highly integrated enterprise service bus (ESB) correlates the many events that take place. Without a well-integrated ESB, it will take much longer to ensure all data systems are in sync and accurately reporting information. Imagine if planes had to call databases to find information for each system, while in flight, and then correlate point-to-point for all logistical and route changes with ground control.

Ensure your company is well-equipped to deal with any type of event, from tragedy to routine. Check out our Integration Maturity Model to learn more.