feat(dissertation): improve on checklist section in background

This commit is contained in:
Anthony Berg 2024-05-19 20:00:04 +01:00
parent c7bcecf552
commit 120a7c2413
5 changed files with 52 additions and 15 deletions

View File

@ -24,15 +24,32 @@
% - Safety procedures being added
% - Rates of accidents
\begin{itemize}
\item 70-80\% of aviation accidents are attributed to human factors~\cite{faa-reasons}
\item 70-80\% of aviation accidents are attributed to human factors~\cite{faa:reasons}
\end{itemize}
\subsection{Checklists}
\begin{itemize}
\item Checklists have been shown to aid in minimizing human errors~\cite{manifesto}
\item However, checklists can be misleading and compromise the safety of the aircraft
due to them being either too confusing or taking too long to complete~\cite{nasa-design}
\item However, according to the Civil Aviation Authority (CAA), the UK's aviation regulator:
\begin{itemize}
\item Checklists can be misleading and compromise the safety of the aircraft
due to them being either too confusing or taking too long to complete~\cite{nasa:design}
\item Other problems may include the crew skipping a step either unintentionally or by interruption,
or just failing to complete the checklist outright
\item The crew may also not be alerted to performance issues within the aircraft,
that running the checklist may cause~\cite{caa:design}
\end{itemize}
\item That is why testing checklists are important to avoid these situations
\item However, it is important to note that checklists does not prevent the human
factor of failure to use a checklist, like in the case of Northwest Airlines
Flight 255, where the National Transportation Safety Board (NTSB), an investigatory board
for aviation accidents in the United States, determined that
\enquote{the probable cause of the accident was the flight crew's failure
to use the taxi checklist to ensure that the flaps and slats were extended for takeoff.}~\cite{ntsb:NWA255}
\end{itemize}

View File

@ -4,7 +4,7 @@
\section{Scene}
\begin{itemize}
\item Designing Emergency Checklists is difficult
\item Procedures in checklists must be tested in simulators~\cite{nasa-design},
\item Procedures in checklists must be tested in simulators~\cite{nasa:design},
which usually means trained pilots test it, as the tests need
to work consistently~\cite{manifesto} (making sure it's not lengthy,
concise and gets critical procedures)
@ -14,16 +14,16 @@
\section{Motivation}
\begin{itemize}
\item Testing procedures in checklists are often neglected~\cite{nasa-design}
\item Testing procedures in checklists are often neglected~\cite{nasa:design}
\item There are some checklists that may not be fit
for certain scenarios - e.g. ditching (water landing)
checklist for US Airways Flight 1549 assumed at least one engine
was running~\cite{AWE1549}, but in this scenario, there were none
was running~\cite{ntsb:AWE1549}, but in this scenario, there were none
\item Some checklists may make pilots \enquote{stuck}
- not widely implemented, could be fixed with \enquote{opt out} points.
e.g. US Airways 1549, plane below 3000ft, could have skip to
later in the checklist to something like turn on APU, otherwise plane
will have limited control~\cite{AWE1549}.
will have limited control~\cite{ntsb:AWE1549}.
\item Checklists may take too long to carry out - Swissair 111
\end{itemize}

Binary file not shown.

View File

@ -1 +1 @@
4624
4751

View File

@ -1,4 +1,4 @@
@report{AWE1549,
@report{ntsb:AWE1549,
author = {{National Tranportation Safety Board}},
shortauthor = {NTSB},
number = {PB2010-910403},
@ -6,13 +6,23 @@
and Subsequent Ditching on the Hudson River},
type = {Technical Report},
institution = {},
date = {2010},
year = {2010},
month = {5},
day = {3},
url = {https://www.ntsb.gov/investigations/Pages/DCA09MA026.aspx},
}
@article{nasa-checklist,
@report{ntsb:NWA255,
author = {{National Tranportation Safety Board}},
shortauthor = {NTSB},
number = {PB88-910406},
title = {Aircraft Accident Report Northwest Airlines, Inc\. McDonnell Douglas DC-9-82, N312RC, Detroit Metropolitan Wayne County Airport Romulus, Michigan},
year = {1987},
month = {08},
url = {https://www.ntsb.gov/investigations/AccidentReports/Reports/AAR8805.pdf},
}
@article{nasa:checklist,
author = {Burian, Barbara},
year = {2006},
month = {10},
@ -24,7 +34,7 @@
doi = {10.1177/154193120605000123},
}
@book{nasa-design,
@book{nasa:design,
year = {2016},
month = {11},
title = {Designing Flightdeck Procedures},
@ -66,16 +76,26 @@
},
}
@manual{caa-emergency,
@manual{caa:emergency,
author = {Civil Aviation Authority},
title = {Aircraft Emergencies: Considerations for air traffic controllers},
number = {CAP745},
number = {CAP 745},
year = {2005},
month = {3},
url = {https://www.caa.co.uk/cap745},
}
@techreport{faa-reasons,
@manual{caa:design,
author = {Civil Aviation Authority},
title = {Guidance on the Design, Presentation and Use
of Emergency and Abnormal Checklists},
number = {CAP 676},
year = {2006},
month = {08},
url = {https://www.caa.co.uk/cap745},
}
@techreport{faa:reasons,
author = {Knecht, William R. and Lenz, Michael},
title = {Causes of General Aviation Weather-Related, Non-Fatal Incidents:
Analysis Using NASA Aviation Safety Reporting System Data},