Local Area Networks (LANs) in Aircraft - FTP Directory Listing - FAA
Local Area Networks (LANs) in Aircraft - FTP Directory Listing - FAA
Local Area Networks (LANs) in Aircraft - FTP Directory Listing - FAA
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
c. Major: Failure conditions which would reduce the capability of the aircraft or<br />
the ability of the crew to cope with adverse operat<strong>in</strong>g conditions to the extent<br />
that there would be, for example, a significant reduction <strong>in</strong> safety marg<strong>in</strong>s or<br />
functional capabilities, a significant <strong>in</strong>crease <strong>in</strong> crew workload or <strong>in</strong><br />
conditions impair<strong>in</strong>g crew efficiency, or discomfort to occupants, possibly<br />
<strong>in</strong>clud<strong>in</strong>g <strong>in</strong>juries.<br />
d. M<strong>in</strong>or: Failure conditions which would not significantly reduce aircraft<br />
safety, and which would <strong>in</strong>volve crew actions that are well with<strong>in</strong> their<br />
capabilities. M<strong>in</strong>or failure conditions may <strong>in</strong>clude, for example, a slight<br />
reduction <strong>in</strong> safety marg<strong>in</strong>s or functional capabilities, a slight <strong>in</strong>crease <strong>in</strong> crew<br />
workload, such as, rout<strong>in</strong>e flight plan changes, or some <strong>in</strong>convenience to<br />
occupants.<br />
e. No Effect: Failure conditions which do not affect the operational capability of<br />
the aircraft or <strong>in</strong>crease crew workload.” (Quoted from Section 2.2.1 of<br />
reference 5.)<br />
In addition to the safety def<strong>in</strong>itions, all software <strong>in</strong>volved <strong>in</strong> civil aircraft systems is also<br />
assigned a level, depend<strong>in</strong>g upon the software caus<strong>in</strong>g or contribut<strong>in</strong>g to potential failure<br />
conditions as determ<strong>in</strong>ed by the system safety assessment process (e.g., ARP 4754 and ARP<br />
4761).<br />
“The software level implies that the level of effort required to show compliance<br />
with certification requirements varies with the failure condition category. The<br />
software level def<strong>in</strong>itions are:<br />
a. Level A: Software whose anomalous behavior, as shown by the system safety<br />
assessment process, would cause or contribute to a failure of system function<br />
result<strong>in</strong>g <strong>in</strong> a catastrophic failure condition for the aircraft.<br />
b. Level B: Software whose anomalous behavior, as shown by the system safety<br />
assessment process, would cause or contribute to a failure of system function<br />
result<strong>in</strong>g <strong>in</strong> a hazardous/severe-major failure condition for the aircraft.<br />
c. Level C: Software whose anomalous behavior, as shown by the system safety<br />
assessment process, would cause or contribute to a failure of system function<br />
result<strong>in</strong>g <strong>in</strong> a major failure condition for the aircraft.<br />
d. Level D: Software whose anomalous behavior, as shown by the system safety<br />
assessment process, would cause or contribute to a failure of system function<br />
result<strong>in</strong>g <strong>in</strong> a m<strong>in</strong>or failure condition for the aircraft.<br />
e. Level E: Software whose anomalous behavior, as shown by the system safety<br />
assessment process, would cause or contribute to a failure of system function<br />
with no effect on aircraft operational capability or pilot workload. Once<br />
84