Human Factors in Aviation by Omar KuzbariOmar Kuzbari
Case study on Human Factors in Aviation based on the Air Ontario Flight 1363 Fokker F-28 at Dryden from March 10, 1989 (Ontario) prepared by Omar Kuzbari in 2018.
Guide to Unmanned Aircraft Systems (UAS)Graeme Cross
Unmanned Aircraft Systems (UAS) usage is expected to dramatically increase over the next five years. After the passing of the FAA Modernization and Reform Act of 2012, the FAA, under the direction of the Secretary of Transportation, gained authorization to begin integration of civil Unmanned Aircraft Systems into the National Air Space (NAS). In conjunction with the US Congress and state and local agencies, the FAA is working to create regulations on recreational and commercial applications that allow more streamlined access of unmanned aircraft to American businesses and institutions*. It is important to keep current with UAS regulations and news by following updates from the FAA, your aviation legal counsel, and your insurance broker.
This is seminar report of ageing of aircraft.this useful for those student who want to give seminar on designing area of aircraft.In this report you will find brief introduction of ageing of aircraft.
NTSB Senior Air Safety Investigator, Kristi Dunks, talks about aeronautical decision making when a pilot plans a flight.
This presentation is part of the release of the NTSB General Aviation Safety Series at the FAA Safety forums during Sun 'N Fun 2012 in Lakeland FL.
Use one paragraph to answer the question of which of the two.pdfabithmobiles
Use one paragraph to answer the question of which of the two aircraft breaches is more
dangerous: 1) the breach of ACARS described in this case or 2) the breach created by the hacker
(described earlier) who took control of a planes throttle briefly through the entertainment system
and then tweeted about it? Why? (HINT: Be sure to choose only one of the breaches described as
most dangerous. Do not say both.)
Case Study 7-1 The Aircraft Communications Addressing and Reporting System (ACARS) On
June 22, 2015, LOT, the state-owned Polish airline, had to ground at least 10 national and
international flights because hackers breached the network at Warsaw's Chopin airport and
intercepted the flight plans that pilots need before taking off. The grounding affected about 1,400
passengers and lasted over five hours before the problem was solved. A month earlier, United
Airlines was reported to have experienced the same problem in the United States, and pilots
reported bogus flight plans repeatedly popping up on the system. A consultant explained that the
radio network that carried flight plans did not need authentication and was designed to trust the
communications. A committee was then set up to develop a proposed standard for flight plan
security. Fortunately, the flight plan did not control the plane, and a pilot had to accept and enter
the plan. A strange result, such as heading to a distant city in the wrong direction, would not be
entered or accepted. Even if the bogus plan were entered and accepted by the pilot, there was no
danger of collision or crash because of the fraudulent plans. Any changes received to the plan
while in flight had to be confirmed with air traffic controllers, who analyzed the new plan for safety.
Alarms would also indicate a possible collision..
Accidents and Liabilities by ALIAS ConsortiumALIAS Network
If you are interested in the topic please register to the ALIAS network:
http://network.aliasnetwork.eu/
to download other materials and get information about the ALIAS project (www.aliasnetwork.eu).
Human Factors in Aviation by Omar KuzbariOmar Kuzbari
Case study on Human Factors in Aviation based on the Air Ontario Flight 1363 Fokker F-28 at Dryden from March 10, 1989 (Ontario) prepared by Omar Kuzbari in 2018.
Guide to Unmanned Aircraft Systems (UAS)Graeme Cross
Unmanned Aircraft Systems (UAS) usage is expected to dramatically increase over the next five years. After the passing of the FAA Modernization and Reform Act of 2012, the FAA, under the direction of the Secretary of Transportation, gained authorization to begin integration of civil Unmanned Aircraft Systems into the National Air Space (NAS). In conjunction with the US Congress and state and local agencies, the FAA is working to create regulations on recreational and commercial applications that allow more streamlined access of unmanned aircraft to American businesses and institutions*. It is important to keep current with UAS regulations and news by following updates from the FAA, your aviation legal counsel, and your insurance broker.
This is seminar report of ageing of aircraft.this useful for those student who want to give seminar on designing area of aircraft.In this report you will find brief introduction of ageing of aircraft.
NTSB Senior Air Safety Investigator, Kristi Dunks, talks about aeronautical decision making when a pilot plans a flight.
This presentation is part of the release of the NTSB General Aviation Safety Series at the FAA Safety forums during Sun 'N Fun 2012 in Lakeland FL.
Use one paragraph to answer the question of which of the two.pdfabithmobiles
Use one paragraph to answer the question of which of the two aircraft breaches is more
dangerous: 1) the breach of ACARS described in this case or 2) the breach created by the hacker
(described earlier) who took control of a planes throttle briefly through the entertainment system
and then tweeted about it? Why? (HINT: Be sure to choose only one of the breaches described as
most dangerous. Do not say both.)
Case Study 7-1 The Aircraft Communications Addressing and Reporting System (ACARS) On
June 22, 2015, LOT, the state-owned Polish airline, had to ground at least 10 national and
international flights because hackers breached the network at Warsaw's Chopin airport and
intercepted the flight plans that pilots need before taking off. The grounding affected about 1,400
passengers and lasted over five hours before the problem was solved. A month earlier, United
Airlines was reported to have experienced the same problem in the United States, and pilots
reported bogus flight plans repeatedly popping up on the system. A consultant explained that the
radio network that carried flight plans did not need authentication and was designed to trust the
communications. A committee was then set up to develop a proposed standard for flight plan
security. Fortunately, the flight plan did not control the plane, and a pilot had to accept and enter
the plan. A strange result, such as heading to a distant city in the wrong direction, would not be
entered or accepted. Even if the bogus plan were entered and accepted by the pilot, there was no
danger of collision or crash because of the fraudulent plans. Any changes received to the plan
while in flight had to be confirmed with air traffic controllers, who analyzed the new plan for safety.
Alarms would also indicate a possible collision..
Accidents and Liabilities by ALIAS ConsortiumALIAS Network
If you are interested in the topic please register to the ALIAS network:
http://network.aliasnetwork.eu/
to download other materials and get information about the ALIAS project (www.aliasnetwork.eu).
Mahmoud Alhujayri Professor WesemannAV 4720 03172017.docxsmile790243
Mahmoud Alhujayri
Professor Wesemann
AV 4720
03/17/2017
Article Analysis 3
The article titled Safety Regulation: Crackdown on Fatigue authored and published by Flight Safety Foundation on its website on 7th April 2011 describes one of the flight safety rules established by the U.S. Federal Aviation Administration (FAA) recently. As explained in the article, the FAA established the rule in response to recommendations made by the National Transportation Safety Board (NTSB) after the Aloha airline flight 243 incident. The incident, which occurred on April 28, 1988, involved Boeing 737-200 that was operated and owned by Aloha Airlines Inc. The aircraft was heading to Honolulu from Hilo in Hawaii when it experienced structural failure and explosive decompression. Consequently, the aircraft made an emergency landing on the ground. On board were six crew members and 89 passengers (Flight Safety Foundation, 2011). Although the aircraft was damaged, only one crew member died. Seven passengers and one crew member sustained serious injuries. After investigations, it was noted that accident was caused by the failure by the aircraft's maintenance program to detect fatigue. Eventually, the fatigue led to widespread fatigue damage (WFD). As explained in the article authored by the flight safety foundation, the NTSB made a recommendation to the FAA to ensure that aircraft have effective maintenance programs and to make continuous surveillance of those programs. In response, the FAA made a rule that requiring the establishment of an inspection program for airplanes of transport category (Flight Safety Foundation, 2011). The program was meant to determine the probability of WFD occurring before “limit of validity” (LOV). The article also contains brief information about other aircrafts that have been damaged by WFD and an explanation of how LOV would be determined.
The content of the article is related to the topic of flight safety since it concentrates on the step that was taken by FAA to enhance aviation safety through conducting a thorough inspection of aircrafts to determine whether they are at the risk of getting damaged by WFD before the end of their LOV. Applying the rule would help to reduce accidents that are caused by WFD. Despite the fact that the article is very relevant, it does not cover many things related to flight safety. For instance, the issue of flight safety when landing is very paramount. Another important issue relates likelihood of carrying passengers with communicable diseases, such as avian influenza. Safety from attack by terrorists is still a major issue that affects the aviation industry today. Other important issues that influence flight safety include weather situation awareness, airspace infringement, fuel management and cabin crew fatigue. Questions related to the topics mentioned above ought to be covered. Despite not covering those issues, the article will be very useful. The content of the article will be used as an e ...
How Did A Flyable Plane Crash in Just Over Four Minutes?Bob Mayer
How does a flyable plane go from 30,000 feet to crash into the ocean in just over 4 minutes? Do not read this if you're getting ready to take a flight. A cascade of events, of which human error played a big role. The key is to learn from such an event so the lives lost were not in vain.
How Did A Flyable Plane Crash in Just Over Four Minutes?Bob Mayer
How does a flyable plane go from 30,000 feet to crash into the ocean in just over 4 minutes? Do not read this if you're getting ready to take a flight. A cascade of events, of which human error played a big role. The key is to learn from such an event so the lives lost were not in vain.
Paola Tomasello - Liabilities of Remotely Piloted Aircraft Systems (RPAS): th...ALIAS Network
Drones (namely RPAS) have been chosen as case study to test the Legal Case, the novel methodology, developed by the ALIAS Project, to proactively address liability of new aviation technologies. This presentation shows how the methodology has been applied to address liability issues of drones. It presents the step 1 of the Legal Case process, dealing with the human factors analysis of drones. This intends to define task allocation between the remote pilot and the drone in order to derive task responsibilities of all actors involved in drones operations.
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...SOFTTECHHUB
The choice of an operating system plays a pivotal role in shaping our computing experience. For decades, Microsoft's Windows has dominated the market, offering a familiar and widely adopted platform for personal and professional use. However, as technological advancements continue to push the boundaries of innovation, alternative operating systems have emerged, challenging the status quo and offering users a fresh perspective on computing.
One such alternative that has garnered significant attention and acclaim is Nitrux Linux 3.5.0, a sleek, powerful, and user-friendly Linux distribution that promises to redefine the way we interact with our devices. With its focus on performance, security, and customization, Nitrux Linux presents a compelling case for those seeking to break free from the constraints of proprietary software and embrace the freedom and flexibility of open-source computing.
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
UiPath Test Automation using UiPath Test Suite series, part 6DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
A tale of scale & speed: How the US Navy is enabling software delivery from l...sonjaschweigert1
Rapid and secure feature delivery is a goal across every application team and every branch of the DoD. The Navy’s DevSecOps platform, Party Barge, has achieved:
- Reduction in onboarding time from 5 weeks to 1 day
- Improved developer experience and productivity through actionable findings and reduction of false positives
- Maintenance of superior security standards and inherent policy enforcement with Authorization to Operate (ATO)
Development teams can ship efficiently and ensure applications are cyber ready for Navy Authorizing Officials (AOs). In this webinar, Sigma Defense and Anchore will give attendees a look behind the scenes and demo secure pipeline automation and security artifacts that speed up application ATO and time to production.
We will cover:
- How to remove silos in DevSecOps
- How to build efficient development pipeline roles and component templates
- How to deliver security artifacts that matter for ATO’s (SBOMs, vulnerability reports, and policy evidence)
- How to streamline operations with automated policy checks on container images
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024Neo4j
Neha Bajwa, Vice President of Product Marketing, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
GridMate - End to end testing is a critical piece to ensure quality and avoid...ThomasParaiso2
End to end testing is a critical piece to ensure quality and avoid regressions. In this session, we share our journey building an E2E testing pipeline for GridMate components (LWC and Aura) using Cypress, JSForce, FakerJS…
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
Sudheer Mechineni, Head of Application Frameworks, Standard Chartered Bank
Discover how Standard Chartered Bank harnessed the power of Neo4j to transform complex data access challenges into a dynamic, scalable graph database solution. This keynote will cover their journey from initial adoption to deploying a fully automated, enterprise-grade causal cluster, highlighting key strategies for modelling organisational changes and ensuring robust disaster recovery. Learn how these innovations have not only enhanced Standard Chartered Bank’s data infrastructure but also positioned them as pioneers in the banking sector’s adoption of graph technology.
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024
LIABILITY AND ALLOCATION OF BURDEN INVOLVING AUTOMATED SYSTEMS IN AVIATION: RECENT ITALIAN CASE LAW by Pierpaolo Gori
1.
2. Pierpaolo Gori, Court of Milan
LIABILITY AND ALLOCATION OF BURDEN
INVOLVING AUTOMATED SYSTEMS IN
AVIATION: RECENT ITALIAN CASE LAW
3. Failure of automated systems and human errors are often enchained
and the same conduct can produce criminal and civil liabilities
QUICK OVERVIEW OF CASE LAW UNDER THE CRIMINAL CORNER
case a) Linate disaster: enchained faults, with a prevalence of lack of organization
(Court of Cassation, judgment delivered on 5 June 2008 n.22614/08)
case b) Tuninter air crash: concurring factors, with overconfidence on automated instrumentation as key factor
(Court of Cassation, judgment delivered on 14 June 2013 n.26239/13)
UNDER THE CIVIL CORNER (lawsuits for damage compensation)
case c) Bird strikes and ineffective remote monitoring: “operating an airport is a dangerous activity”
(Court of Genoa, judgment delivered on 19.2.2007)
case d) Aircraft technical defects of the airplane and inadequate information (failures non detected by automated alarms)
(Court of Milan, judgment delivered on 11.3.2012)
case e) Lack of maintenance of the airport's infrastructure (organizational failures)
(Court of Venice, judgment delivered on 25.7.2008)
4. a) Linate disaster: enchained faults, with a prevalence of lack of organization
(Court of Cassation, judgment delivered on 5.6.2008 No.22614)
Facts:
The accident occurred on 8 October 2001 in the city airport of Milan, Linate, when under low visibility conditions (between 50 and 100 meters),
high traffic volume, lack of adequate visual aids and of a ground radar, an airliner MD-87 collided on take-off with a Cessna business jet crossing
the lane without specific clearance. 118 persons died, in the Country's worst air disaster.
Main provision applicable:
Article 449 § 2 Criminal code (multiple aeronautic manslaughter, culpable conduct).
Burden of proof:
Under Article 40§ 2 Criminal Code, Criminal (and Civil) liability may depend not only upon an action but, under specific obligations, upon a failure
to take an action if necessary to avoid the harmful fact. Following a process of mental elimination, a causal nexus between action and harmful
event is established if it’s possible to answer “no” to the question: “would the event have occurred without such action?” .
Evidence results:
The evidence underlined a chain of situations, procedures, and instruments that failed to ensure the safety of the flight;
• the former head of air traffic control authority ENAV and the former ENAV general manager were held liable for negligent behavior
concerning replacement of the ground radar, out of service from November 1999 and not yet repaired or replaced at the moment of the
disaster, almost 2 years later;
• two former officials with the Airport operator (SEA) were held accountable for facts regarding the maintenance of the markings, which were
considered also the result of protracted negligence, as well as for the general bad management of flight infrastructures, which also continued
over time;
• the air traffic controller, as the last and, therefore, weakest link if there is a lack of adequate support destined to limit the risk of error, was
author of a serious error, his failure to stop the Cessna, but took place in a few seconds, and therefore was judged less harshly than those who
had greater opportunities to ensure flight safety.
Ruling:
Court of Cassation upheld a 7 July 2006 Milan Court of appeal's finding of multiple aeronautic manslaughter as well as negligent disaster, namely:
• for the greater responsibility and related authority, the former head of air traffic control authority ENAV and the former ENAV general
manager were convicted for multiple manslaughter and sentenced respectively to 6 and half years prison and to 4 years 4 months prison;
• the two former officials with the Airport operator were convicted to three years prison each;
• the air traffic controller was sentenced to three-year prison.
• Each convicted was held liable for civil damages (compensation), to be quantified in civil proceedings. However, these proceedings ended with
a settlement.
5. b) Tuninter air crash: concurring factors, with overconfidence on automated instrumentation as key
factor (Court of Cassation, judgment delivered on 5.6.2008 No.22614)
Facts:
A Tuninter airliner ATR-72 on 6 August 2005 ditched into the Tyrrhenian See close to Capo Gallo, 23 nautical miles from Palermo. The aircraft broke into
three sections upon impact and, as result, 18 out of the 39 persons on board died in the air crash.
Main provision applicable:
Article 449 § 2 Criminal code (multiple aeronautic manslaughter, culpable conduct).
Burden of proof:
Under a consistent interpretation of Article 40 § 2 Criminal code, to assess if a non-action establishes a causal nexus with the harmful event, the judge
should make resort to a process of mental elimination, by wondering “would the event have occurred with the prescribed action?” . Such link is anyway
interrupted by unforeseen subsequent circumstances that alone are sufficient to generate the harmful event (Article 41§ 2 Criminal code).
Evidence results:
According to the Court consultant’s technical report, to flight simulation results and to witnesses, several enchained factors lead to the accident:
• Firstly, for a human mistake the relevant fuel quantity indicator on the ATR-72 was incorrectly replaced with a similar but different tool intended for a
smaller aircraft, with smaller tankers, the ATR-42. The correct replacement part was not found, because Tuninter permitted the mechanical foreman to
query parts using software without license, without specific training and adequate IPC’s manual knowledge. As result of this lack of organization, the
inventory database wrongly reported that the ATR-42 part could be used even on ATR-72 airliner. The mechanic incorrectly replaced the fuel indicator
provided by the foreman, without the specific check of suitability prescribed by the manual.
• Secondly, due to the fault indicator device, in Bari airport the aircraft was insufficiently fuelled. The tanks were filled to up to a level where the wrong
indicator showed 2.700 kilograms, but a correct part would have told there were just 1.150 kilograms when the airliner departed. Such amount was
largely insufficient to reach the final destination of Djerba. The pilot and co-pilot overconfidently relied on the fault automated indicator, failing to
check personally the exact amount of the fuel stored. Such operation consisted in asking for the prescribed fuel receipt (not requested in the specific
case), and confronting the receipt data with the indicator data, showing different amounts of fuel.
• Thirdly, after the engines’ stall because of fuel exhaustion, the crew failed to follow the emergency procedures prescribed, namely, feather propellers to
reduce the drag on the curved blades, so the aircraft could be better sustained by updrafts, and plane towards the closest airport, Palermo. Simulation
results showed that, optimally handled the aircraft was still in conditions to land on the standard runaway of Palermo airport. By contrast, witnesses and
voice records acknowledged that both the pilot and the co-pilot succumbed to panic, continuously tried to restart engines, and then began to pray loud
and prepare to ditch close to a ship seeking help. Such, concurring, human error was decisive for the air crash.
Ruling:
• the pilot was sentenced to 6 years 8 months (human error, overconfidence on automated indicator);
• the general manager of the Air company and the company’s top technical manager were held criminally liable for lack of organization and sentenced to 6
years jail each, as well as the co-pilot (lack of organization);
• The head of the maintenance department, the mechanical foreman and the mechanic to 5 years 8 months (organizational and human error).
6. c) Bird strikes and ineffective remote monitoring: “operating an airport is a dangerous activity”
(Court of Genoa, judgment delivered on 19.2.2007)
Facts:
An four-engined Antonov An-124 “Ruslan” transportation aircraft carrying industrial turbines was taking off from the coastal airport of Genoa, scheduled to
reach Karachi, when collided with a storm of sea-gulls (bird strike). This lead to an engine stall and a subsequent emergency landing, with serious
damages to the heavy aircraft.
Main provision applicable:
2050 Civil Code (Civil liability for dangerous activity).
Burden of proof:
Operating an airport can be defined as a dangerous activity, and in the case of a coastal airport close to a landfill the danger is considerably increased. In
such activities, article 2050 Civil code requires the adoption of all suitable methods for preventing incidents, and a just “ordinary” or “average” behavior is
not enough. By contrast, it is required to go beyond normal diligence to be freed of charges.
Evidence results:
The Court expert assessed that the Italian Government had set up a Bird Strike Committee, adopting many actions in respect of airport operators. Given
that the airport is located on the sea and has a very close landfill, elements that increase the risk of a bird strike, at the time of the facts, Genoa airport
was equipped with some of the best dispersal devices and remote detectors for bird strike prevention in use in international airports, with the possible
exception of infra-red detection systems. According to the consultant's conclusions, the impact was to be considered “substantially accidental”.
Ruling:
The Court disregarded its expert's technical report finding that no accidental event occurred. The facts were considered consequence of a lack of
organization and of over-dependence on automated devices. Besides automated resources, to avoid bird strikes upon a coastal airport close to a
landfill it requires first of all a human monitoring. Airport operators therefore have to fill the organizational gap testing and experiencing a joint use of
technical and human remedies, adding to the existing automated tools, human armed patrols close to the runaway (E.g. Copenhagen Airport Kastrup has
a specific patrolling guard for prevention of bird strikes). More, signals of general warning are not enough: controllers need to be instructed and effectively
monitored to look at possible wildlife interferences with aeronautical activities, that could not be detected by remote controllers. Therefore the Court held:
• The Airport Operator responsible for 35% of damage compensation under Article 2050 Civil code, because it failed to adopt suitable harassment
tools, over-relying on automated devices, remote monitoring included, and adopting non effective remedies, like signals of general warning;
• ENAV (Italian ATS Agency) responsible for 35% of damage compensation under Article 2050 Civil code, for not having complied to its duties
concerning flight safety, in particular for not having instructed and effectively monitored its controllers to look at possible wildlife interferences
with aeronautical activities;
• Ministry of Transport responsible for 22.5 % of damage compensation under 2043 Civil code, because of lack of control over its peripheral
structures (Airport Authorities) and subsequent negligent control by these in respect of the Airport Operator and ATS: 22.5 %;
• (- Under 1218, 2043 and 2050 Civil Code, the former Airport Operator responsible for 7.5 % of damage compensation, due to a concurring minor
liability, because sub-contracting an airport by one company to another does not remove from liability in safety issues).
7. d) Aircraft technical defects of the airplane and inadequate information (failures non detected by
automated alarms) (Court of Milan, judgment delivered on 11.3.2012)
Facts:
A two-engined Cessna business jet owned by a Milanese aero-club crashed because of an engine failure, due to lack of fuel. The pilot
survived, but a passenger died.
Main provisions applicable:
The relatives of the victim lodged civil proceedings against both the pilot and the aero-club association under Articles 942 and 947 Navigation
code (contractual liability) and under Article 2043 Civil code (non-contractual liability).
Burden of proof:
According to the line of reasoning of the Court, no contract under Articles 1678 Civil code and 940 Navigation code was signed between the
aircraft owner and the victim, and so there was no room for any contractual liability. Since there was no air carrier in the specific case,
provisions form the Warsaw Convention and the Montreal Convention were not applicable too.
More, the aircraft's owner, an aero-club, was not accountable even under Article 2049 Civil code, since the plane was given in free loan to the
pilot under Article 1803 Civil code and Article 874 Navigation Code, and was under his full control and therefore exclusive responsibility.
Accordingly, there was room for non-contractual liability of the pilot only, with significant additional burden of proof.
Namely, it was upon the damaged applicants to give evidence of any fault on the pilot’s part, of the causal nexus between action and
harmful event and of the measure of the damages.
Evidence results:
The Court expert, in a parallel Criminal proceeding, after a scientific analysis of the wreck confirmed the existence of a technical defect of the
airplane, since the engines below a certain altitude could not be fuelled by the auxiliary tankers. No alarm in the cockpit monitored and
warned the problem, and such failure lead to the stall and fall of the aircraft. Similar accidents for the same defect occurred in 12 cases
worldwide, and in dozens of cases malfunctioning of the fuelling system was reported to Cessna for the interested model of aircraft.
Witnesses underlined that the auxiliary tanks contained a significant quantity of fuel at the moment of the air crash, and that the pilot reacted
promptly and with diligence, finding room for an emergency landing even in a sub-urban and highly populated area.
Ruling:
Pilot free of charges. The Court was not satisfied with the effort of the applicants (relatives of the victim) to give evidence of a culpable
conduct of the pilot, and to establish a causal nexus with the air crash. By contrast there was evidence of a fact interrupting the link between
conduct and event, whereas a serious negligence in the design of the aircraft, because the fuel system of the aircraft was unsafe, and in
the wording used in the accompanying instructions. No specific recommendations in the aircraft’s manual prohibited to use auxiliary tankers
below a certain altitude. The designer and the manufacturer of the aircraft were not part of the proceedings.
8. e) Damages coming from lack of maintenance of the airport's infrastructure
(Court of Venice, judgment delivered on 25.7.2008)
Facts:
The accident took place in Treviso airport, when an airliner was taxiing on the step-way, and part of the surface of the runaway,
under pressure from the landing gears, hit the body of the aircraft. The damage consisted in repairing the airliner for 17 days of
technical stop, and in compensation for many flights that had to be cancelled, and travelers and tour operators indemnified as well.
Main provision applicable:
Article 2051 Civil code (liability for lack of custody), applicable even towards Administrative authorities.
Burden of proof:
It's upon the damaged to give evidence of the fact involving the object in custody, namely the harmful even. If the Court is satisfied
with this burden, it's upon the subject charged of the custody, in the specific case of the whole airport, to show that an unforeseen
occurred by chance, or the accident was due to fault of the damaged itself.
Evidence results:
Wrong horizontal markings lead pilots to believe that the airliner was in a proper position for the back-track; such mistake happened
even due to other concurring reasons, namely the runway surface in poor conditions and reduced visibility for foggy weather. In the
specific case, the general bad management of airport infrastructures was due to negligence of two different operators.
Ruling:
Non-contractual liability of the Ministry of the Defence and of the private Airport Operator, both charged of the custody of the runway
and makings, the first according to the law and the latter in force of a specific contract signed with Administrative authorities
9. CONCLUSIONS
• A Case-law overview shows that failures of automated systems and human errors in aviation accidents and incidents are
often enchained;
• Operating an airport and an aircraft is a complex and dangerous activity, involving a wide number of subjects with different
roles, and this can lead to concurring liabilities;
• Organizational procedures and effective supervisory activity have to provide reliable and adequate support of the final
operators, to limit the risk of human errors from them;
• A relevant conduct, normally a culpable one, is usually not excluded by automation failures and may drive to both civil and
criminal liabilities;
• A causal nexus between conduct and event may involve the chain of command that failed to organize adequately safety
procedures and controls, following a process of “mental elimination” (condicio sine qua non); the nexus is interrupted by
subsequent exclusive circumstances that, alone, generated the event;
• Under the criminal corner, liability is consequence of:
a) law provisions that consider relevant for crimes even culpable conducts (e.g. multiple aeronautic manslaughter, negligent
disaster…)
b) consistent interpretations of causal nexus provisions (Articles 40 and 41 Criminal code) that give relevance to actions, and,
under specific obligations, to non-actions as well; such positive obligations are extensive in air transport regulations
• Under the civil corner, liability is consequence of:
a) contracts were is easy to find un-fulfilled obligations (e.g. Article 942 Navigation code, Conventions of Warsaw and Montreal)
b) non-contractual obligations established under moderate burden due to specific provisions (e.g. Articles 2050 Civil code “for
dangerous activity” and 2051 Civil code “for lack of custody”)