Patent ID: 12221230

DETAILED DESCRIPTION

The present disclosure describes apparatus and methods associated with functional testing of systems of aircraft and other mobile platforms. Even though various aspects the present disclosure are described in the context of aircraft, it is understood that aspects disclosed herein are also applicable to other mobile platforms (e.g., vehicles) such as trains, ships and busses for example. In various embodiments, the apparatus and methods disclosed herein can improve the operation of an aircraft flight deck and alleviate workload for the flight crew of an aircraft by facilitating (e.g., pre-flight) functional testing of aircraft systems. For example, in comparison with existing aircraft, apparatus and methods disclosed herein can help reduce an amount of time required for functional testing and also can reduce the potential for flight crew errors such as an unintended omission of a pre-flight functional test for example.

Aspects of various embodiments are described through reference to the drawings.

FIG.1shows an exemplary aircraft10(i.e., mobile platform) and a partial schematic representation of flight deck12which can be part of aircraft10. Aircraft10can be a corporate, private, commercial or any other type of aircraft. For example, aircraft10can be a fixed-wing aircraft. In some embodiments, aircraft10can be a narrow-body, twin engine jet airliner. Flight deck12can comprise additional or fewer elements than those shown and described herein. Flight deck12can comprise left portion12A intended to be used by a pilot (sometimes referred as “captain”) of aircraft10and right portion12B intended to be used by a co-pilot (sometimes referred as “first officer”) of aircraft10. Left portion12A and right portion12B can comprise functionally identical components so that at least some operational redundancy can be provided between left portion12A and right portion12B of flight deck12. As used herein, the term “flight crew” is intended to encompass one or more individuals responsible for the operation of aircraft10. Such individuals can, for example, include the pilot and/or the co-pilot.

Flight deck12can comprise one or more display devices14providing respective display areas16. In the exemplary configuration of flight deck12shown inFIG.1, left portion12A and right portion12B can each comprise two display devices14and an additional display device14can be provided in pedestal region18of flight deck12. Display device14provided in pedestal region18can be shared between the pilot and the co-pilot during normal operation of aircraft10. Display devices14can include one or more cathode-ray tubes (CRTs), liquid crystal displays (LCDs), plasma displays, light-emitting diode (LED) based displays or any type of display device suitable for use in flight deck12. Display devices14can be configured to dynamically display operational and status information about various systems of aircraft10, information related to flight/mission planning, maps and any other information that can be useful for the flight crew during the operation of aircraft10. Display devices14can facilitate dialog between the flight crew and various systems of aircraft10via suitable graphical user interfaces. Flight deck12can comprise one or more data input devices such as, for example, one or more cursor control devices20, one or more multi-function keypads22and one or more (e.g., standalone or multifunction) controllers23that permit data entry by the flight crew. In some embodiments, one or more display devices14could have touch sensitive display area(s)16to permit user input by way of the flight crew touching the applicable display area(s)16.

One or more display devices14can be used to display functional testing page16A for facilitating the execution of functional tests of various systems of aircraft10as described further below. Functional testing page16A can be displayed on any suitable display device14of flight deck12or on some other display device visible to the flight crew. In some embodiments, flight deck12can be configured to permit the selective display of functional testing page16A on one or more display device14based on input from the flight crew. In some embodiments, a single instance of functional testing page16A can be displayed on a display device14that is conveniently located to be visible by both the pilot and the co-pilot.

It is understood that functional testing page16A and the display of its contents is not limited to one or more display devices14that is part of flight deck12or that is onboard aircraft10. For example, functional testing page16A could, alternatively or in addition, be provided on a display device that is off of aircraft10. For example, functional testing page16A could be provided on a mobile device (e.g. a laptop or tablet) that is part of a flight crew's electronic flight bag, or could be a display device of a ground station that permits a ground-based operator of aircraft10or support (e.g., maintenance) personnel to execute one or more functional tests on systems of aircraft10. Even though the present disclosure refers to the interaction of a flight crew of aircraft10with functional testing page16A, it is understood that relevant information could be transmitted from aircraft10to a location remote from aircraft10(e.g., ground station) in order to be used by an individual at such location in accordance with aspects of the present disclosure.

FIG.2shows a schematic representation of an exemplary apparatus24which can be part of aircraft10and which can assist with functional testing of systems of aircraft10. Apparatus24can be integrated with flight deck12. Apparatus24can comprise one or more computers26(referred hereinafter in the singular) operatively coupled to one or more display devices14(referred hereinafter in the singular) of flight deck12. Computer26can comprise one or more data processors28(referred hereinafter in the singular) and one or more computer-readable memories30(referred hereinafter in the singular) storing machine-readable instructions32executable by data processor28and configured to cause data processor28to generate one or more outputs34(referred hereinafter in the singular). Output34can comprise one or more signals for causing display device14of aircraft10to display functional testing page16A and its contents. Output34can also comprise one or more signals for causing the initiation of functional tests of one or more systems36of aircraft10.

Computer26can receive input(s)38in the form of data or information that can be processed by data processor28based on instructions32in order to generate output34. For example, input38can comprise information (data) indicative of a condition38A of aircraft10. The number and types of pre-flight functional tests to be executed on aircraft10can differ depending on aircraft condition38A (e.g., pre-flight circumstance). For example, the number of pre-flight functional tests to be executed on aircraft10for a first condition of aircraft10can be greater than the number of pre-flight functional tests to be executed on aircraft10for a second condition of aircraft10. For example, a longer list of pre-flight functional tests can be required before a first flight of the day (i.e., 24-hour period) and a shorter list of pre-flight functional tests can be required before a subsequent flight on the same day. In some embodiments, aircraft condition38A can be indicative of whether there has been a change in flight crew for aircraft10. For example, a longer list of pre-flight functional tests can be required before a flight that immediately follows a change in flight crew for aircraft10and a shorter list of pre-flight functional tests can be required before a subsequent flight of the same flight crew for aircraft10. In some embodiments, aircraft condition38A can be indicative of whether aircraft10is being prepared for a flight that immediately follows a period of inactivity requiring a complete power-down of aircraft10. For example, a longer list of pre-flight functional tests can be required before a flight that immediately follows a cold and dark start of aircraft10.

In some embodiments, input38can additionally comprise information (data) indicative of a substantially real-time status38B of one or more systems36of aircraft10. Such system status38B can be indicative of an operational state of a corresponding system36and/or can be indicative of a state of execution of a functional test for the corresponding system36. For example, system status38B can be indicative of whether an aircraft system36is active (e.g., ON), inactive (e.g., OFF), comprises a fault or has failed. Alternatively or in addition, system status38B can be indicative of whether an aircraft system38B has passed or failed an associated functional test. With respect to the execution of a functional test, an associated system status38B can be indicative of whether the functional test is required but has not yet been conducted, is in progress or is complete.

In various embodiments, system status38B can be provided by way of input by the flight crew into apparatus24and/or can be provided automatically from the applicable system36. In various embodiments, functional testing of aircraft systems36can be automated to different extents depending on the particular aircraft system36. For example, some functional tests can be fully automated after their initiation so that no further input from the flight crew is required. Alternatively, some functional tests can require the flight crew to be in the loop so that the flight crew can remain in control of the functional testing procedure while being guided through the procedure. For example, system status38B can comprise feedback from the flight crew following a visual inspection confirming the associated system status38B. Alternatively, or in addition, system status38B can be provided from one or more sensors or built-in test equipment40integrated with a particular aircraft system36. For example, one or more aircraft systems36can each comprise built-in test equipment40that is capable of automatically performing a functional self-test and report status information. Built-in test equipment40can comprise a testing circuit that is a permanent part of the applicable aircraft system36and enables functional testing and diagnostics of aircraft system36. In other words, such built-in test equipment40can comprise test equipment configured to provide status information on the health of a particular aircraft system36of aircraft10and/or status information on the execution of a particular functional test.

In some embodiments, input38can include or be indicative of sensed signals acquired via one or more (e.g., pressure, position, acceleration, temperature or other) sensors associated with one or more aircraft systems36. Accordingly, input38can comprise one or more sensed parameters indicative of one or more system status38B of aircraft system(s)36and/or of one or more aircraft conditions38A. As described further below, computer26can, based on input38, generate output34for causing display device14to display a plurality of test objects associated with functional tests of aircraft systems36and visually identify one or more of the test objects associated with respective one or more functional tests selected based on aircraft condition38A in order to assist the flight crew with the execution of the applicable functional tests.

Computer26can be part of an avionics suite of aircraft10or can otherwise be operatively integrated with avionic components of aircraft10. For example, in some embodiments, computer26can be configured to carry out additional functions than those described herein including the management of one or more graphic user interfaces of flight deck12and/or other part(s) of aircraft10. In various embodiments, computer26can comprise more than one computer or data processor where the methods disclosed herein (or part(s) thereof) could be performed using a plurality of computers or data processors, or, alternatively, be performed entirely using a single computer or data processor. In some embodiments, computer26could be physically integrated with (e.g., embedded in) display device14.

Data processor28can comprise any suitable device(s) configured to cause a series of steps to be performed by computer26so as to implement a computer-implemented process such that instructions32, when executed by computer26or other programmable apparatus, can cause the functions/acts specified in the methods described herein to be executed. Data processor28can comprise, for example, any type of general-purpose microprocessor or microcontroller, a digital signal processing (DSP) processor, an integrated circuit, a field programmable gate array (FPGA), a reconfigurable processor, other suitably programmed or programmable logic circuits, or any combination thereof.

Memory30can comprise any suitable known or other machine-readable storage medium. Memory30can comprise non-transitory computer readable storage medium such as, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Memory30can include a suitable combination of any type of computer memory that is located either internally or externally to computer26. Memory30can comprise any storage means (e.g. devices) suitable for retrievably storing machine-readable instructions32executable by data processor28.

Various aspects of the present disclosure can be embodied as apparatus, devices, methods and/or computer program products. Accordingly, aspects of the present disclosure can take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects. Furthermore, aspects of the present disclosure can take the form of a computer program product embodied in one or more non-transitory computer readable medium(ia) (e.g., memory30) having computer readable program code (e.g., instructions32) embodied thereon. The computer program product can, for example, be executed by computer26to cause the execution of one or more methods disclosed herein in entirety or in part.

Computer program code for carrying out operations for aspects of the present disclosure in accordance with instructions32can be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or other programming languages. Such program code can be executed entirely or in part by computer26or other data processing device(s). It is understood that, based on the present disclosure, one skilled in the relevant arts could readily write computer program code for implementing the methods disclosed herein.

Memory30can contain functional test data41indicative of (e.g., pre-flight) functional tests associated with aircraft systems36. Functional test data41can also comprise information indicative of which functional tests being applicable to which aircraft condition38A. Accordingly, functional test data41can be used by computer26to select applicable functional tests based on aircraft condition38A.

Memory30can also contain testing order data42indicative of a predetermined testing order for the pre-flight functional tests to be conducted. Testing order data42can be used by computer26to generate functional testing page16A on display device14and further assist (e.g., guide) the flight crew in conducting the applicable functional tests in the recommended testing order. Alternatively or in addition, testing order data42can be used by computer26to cause the automated initiation of the functional tests according to the predetermined testing order.

FIG.3shows an exemplary functional testing page16A that can be displayed on display device14of apparatus24. As explained above, functional testing page16A and its contents can be generated based on machine-readable instructions32via computer26of apparatus24. Functional testing page16A can contain a plurality of test objects44where each test object44is associated with a functional test of an aircraft system36of aircraft10. As illustrated inFIG.3, examples of aircraft systems36can include an aural warning system (AURAL), a lighting system (LAMP), a traffic collision avoidance system (TCAS), a weather radar (WRX), a terrain awareness and warning system (TAWS), an ice protection system (WING A/ICE), an ice detection system (ICE DETECT), a fire protection system (FIRE), a flight control system (FLT CTRL) and a stick shaker (SHAKER). In order to assist the flight crew with the execution of the applicable functional tests, functional testing page16A can also visually identify one or more of the test objects44associated with respective one or more functional tests selected based on aircraft condition38A.

Functional testing page16A can provide status information to the flight crew about the execution of the functional tests whether or not the functional tests are initiated automatically or based on input from the flight crew. In embodiments where the initiation of the functional tests is controlled by the flight crew, functional testing page16A can be configured to serve as a graphic user interface via which input from the flight crew can be received. For example, one or more of test objects44can be responsive to user input. Test objects44can comprise interactive and/or non-interactive widgets. For example, test object44can include buttons, icons, radio buttons, check boxes, editable data fields, lists of selectable items, pull-down menus, display-only text and/or graphic fields and/or any other objects suitable for use in graphical user interfaces. The flight crew's interaction with functional testing page16A can be achieved through the use of cursor46that can be movable over some or all of functional testing page16A. The movement of cursor46can be controlled by the flight crew via cursor control device20and/or directional movement keys provided on multi-function keypads22for example. It is understood that other means (e.g., touchscreen) to permit user input by the flight crew can also be suitable.

In the embodiment illustrated inFIG.3, test objects44can be graphical push buttons that can be actuated through the use of cursor46to thereby cause the initiation of an associated functional test. For example, instructions32can be configured to, in response to an actuation of one or more test objects44, cause processor28to generate output34for causing initiation of the respective one or more functional tests associated with the one or more of test objects44.

In some embodiments, functional testing page16A can assist the flight crew by providing a single common interface and location that facilitates the execution of a plurality of functional tests in order to reduce or eliminate the need for the flight crew to interface with controls and display devices scattered throughout the flight deck12. In some embodiments, the use of functional testing page16A can reduce the potential for error during pre-flight functional testing of applicable aircraft systems36.

By way of the displayed test objects44, functional testing page16A can provide a list of available (e.g., pre-flight) functional tests and identify one or more of the displayed test objects44associated with the respective one or more functional tests that are selected based on aircraft condition38A. The selected functional tests can comprise a subset of the list of available functional tests and hence represent a shorter list of functional tests that are specifically applicable (e.g., recommended or required) to aircraft condition38A.

In some embodiments, some non-identified test objects44associated with functional tests that are not specifically selected based on aircraft condition38A can still be displayed on functional testing page16A so as to remain available for selection by the flight crew. For example, the flight crew can still have access to some functional tests that are not specifically selected based on aircraft condition38A but that can optionally be initiated if desired.

The identification of the applicable test objects44to the flight crew can be achieved by visually distinguishing the one or more identified test objects44from any non-identified test objects44. In the embodiment ofFIG.3, the visual distinction is achieved by highlighting the identified test objects44. Such highlighting can comprise using a border48shown only around the respective identified test objects44. It is understood that the visual distinction of the identified test objects44can be achieved in any suitable manner including changing an appearance (e.g., color, brightness) of the identified test objects44and/or of the non-identified test objects44for example.

Testing order data42can be used by computer26to determine the layout of functional testing page16A. In some embodiments, testing order data42can be contextual and dependent on aircraft condition38A. Testing order data42can represent a predefined or mandated order of execution of the functional tests. For example, the execution of one functional test can require the prior execution of another functional test. For example, some functional tests may need to be executed serially and some functional tests may be executed simultaneously in parallel.

In some embodiments, the arrangement of test objects44on functional testing page16A can be in accordance with testing order data42. For example, test objects44can be arranged in rows/columns that serve to visually guide the flight crew in initiating the functional tests in the order defined by testing order data42. For example, test objects44can be arranged in one or more rows where the sequential left to right positioning of test objects44in each row is defined by testing order data42. Similarly, test objects44can be arranged in one or more columns where the sequential vertical positioning of test objects44in each column is defined by testing order data42.

In some embodiments, instead of relying on the flight crew to select test objects44in the predefined order using cursor46based on the layout of functional testing page16A, instructions32can be configured to, in the case of multiple functional tests having been selected for execution by the flight crew, automatically adjust the order of execution of the functional tests based on testing order data42irrespective of the order of the flight crew's selection of the functional tests. For example, the flight crew could select some or all of the identified test objects44(and optionally one or more non-identified test objects44) in any order and computer26can then, based on instructions32, cause the initiation of the selected functional tests according to testing order data42. In this embodiment, the predefined testing order can be achieved without necessarily having to configure the layout of functional testing page16A based on testing order data42.

Testing order data42can also contain information as to which functional tests can be conducted simultaneously in parallel and which functional tests must be conducted at separate times. Accordingly, computer26can, based on instructions32and testing order data42, cause the automated initiation of some functional tests simultaneously in parallel and cause the automated sequencing of other functional tests in an optimized fashion so as to reduce the overall time required to functionally test the applicable systems36of aircraft10. In some embodiments, the selection of multiple functional tests by the flight crew can also permit the computer26to optimize the execution of some functional tests without requiring the flight crew to wait for one functional test to finish before manually initiating another functional test. In other words, once multiple functional tests have been selected for execution by the flight crew, the computer26can initiate their execution automatically according to a sequence and timing that optimizes the completion of the set of functional tests that have been selected for execution.

In some embodiments, instructions32can be configured to cause display device14to display one or more status indicators50. Status indicators50can provide system status information associated with one or more test objects44. The information provided by status indicators50can be based on system status38B described above.

FIG.4shows another exemplary functional testing page16A that can be displayed on display device14of apparatus24. The embodiment ofFIG.4shows another method of identifying test objects44associated with the functional tests selected based on aircraft condition38A. Instead of changing the appearance of the identified test objects44, the identified test objects44can be grouped together using a single enclosure52that surrounds the identified test objects44. Enclosure52can comprise a line at least partially surrounding the identified test objects44. In various embodiments, enclosure52can be represented by a solid or stippled line for example.

FIG.5shows another exemplary functional testing page16A that can be displayed on display device14of apparatus24. The embodiment ofFIG.5shows another method of identifying test objects44associated with the functional tests selected based on aircraft condition38A. Instead of identifying test objects44that are dispersed within a larger group of test objects44, the layout of test objects44can be rearranged so that the identified test objects44are grouped together in one region of functional testing page16A and the non-identified test objects44are grouped together in another region of functional testing page16A. In the example shown inFIG.5, the identified test objects44are grouped together in one column labeled as “REQUIRED” and the non-identified test objects44are grouped together in another column labeled as “OPTIONAL”.

FIG.6shows another exemplary functional testing page16A that can be displayed on display device14of apparatus24. The embodiment ofFIG.6includes condition object54being displayed on testing page16A. Condition object54can be configured to provide an indication of the condition (e.g., pre-flight circumstance) of aircraft10and can be based on aircraft condition38A (seeFIG.2). In some embodiments, condition object54can be responsive to user input so that the flight crew can input the condition of the aircraft10that will be used to select the required functional tests. For example, condition object54can include buttons, icons, radio buttons, check boxes, editable data field, list of selectable items, pull-down menu, display-only text and/or graphic fields and/or any other object(s) suitable for use in graphical user interfaces.

In some embodiments, condition object54can be automatically populated with a default value based on a condition of aircraft10that has been automatically determined by computer26or otherwise where the default value can be either accepted or changed by the flight crew. Alternatively, condition object54could be configured to be automatically populated and only serve to communicate the relevant information to the flight crew.

In various embodiments, aircraft condition38A could be input by the flight crew or could be determined by computer26based on data available to computer26with or without input from the flight crew. For example, a determination of whether the aircraft10is about to conduct a first flight or a subsequent flight within a 24-hour period could be determined based on a sequence of detected weight-on-wheels (WOW) and/or weight-off-wheels (WOFFW) signals, or, a sequence of detected aircraft door openings/closings within that 24-hour period as being indicative of the number flights that the aircraft10has conducted in that same period.

In the exemplary embodiment ofFIG.6, condition object54indicates “FIRST FLIGHT” which corresponds to all functional tests being selected. The identification of the applicable test objects44is achieved by enclosure52surrounding all of test objects44but it is understood that other identification methods could be used. Condition object54can be a pull-down menu with which the flight crew can select the applicable aircraft condition38A (seeFIG.2) using cursor46. Upon selection of the applicable aircraft condition38A, enclosure52can be adjusted to surround and identify test objects44that are associated with the functional tests that are selected based on aircraft condition38A. The selection of the applicable functional tests can be performed by computer26using functional test data41(seeFIG.2) for example.

In some embodiments, the initiation of the selected functional tests can be triggered automatically based on aircraft condition38A and without input from the flight crew. Alternatively, the initiation of the selected functional tests can be triggered based on input from the flight crew. In some embodiments, display area16A can include execution object56(e.g., RUN button) that is responsive to user input and that is configured to permit the flight crew to trigger an automatic initiation of some (e.g., a plurality) or all of the selected functional tests. For example, execution object56can include a button, icon and/or any other objects suitable for use in graphical user interfaces. In some embodiments, execution object56can be actuated by the flight crew using cursor46in order to trigger the initiation of the functional tests that have been selected based on aircraft condition38A. After triggering, the initiation of the applicable selected functional tests can be performed automatically or semi-automatically based on testing order data42. Depending on the nature of the selected functional tests, some selected functional tests may be executed in parallel while other selected functional tests may need to be executed serially as defined in testing order data42. The initiation of the selected functional tests according to testing order data42can be performed by computer26so that the flight crew does not have to be preoccupied with proper sequencing of the selected functional tests. Functional testing page16A shown inFIG.6shows three selected functional tests, namely WXR, TAWS and WING A/ICE, being executed simultaneously in parallel. The simultaneous execution of the three selected functional tests is indicated by status indicators50indicating “IN PROG”.

FIG.7shows another exemplary functional testing page16A that can be displayed on display device14of apparatus24. The operation of functional testing page16A ofFIG.7can be similar to that ofFIG.6. However, in contrast with the embodiment ofFIG.6, the embodiment ofFIG.7includes condition object54indicating “OTHER FLIGHT” which corresponds to an aircraft condition38A that requires a reduced number of functional tests. The identification of the applicable test objects44is achieved by enclosure52surrounding a reduced number of identified test objects44.

The identified test objects44can be a subset of all test objects44displayed on functional testing page16A. Even though the identified test objects44can be associated with the selected functional tests applicable to aircraft condition38A, the non-identified test objects44can also be displayed on functional testing page16A and the associated non-selected functional tests can nevertheless be available to the flight crew. In the embodiment shown inFIG.7, the actuation of execution object56using cursor46can trigger the automated initiation of the selected functional tests associated with identified test objects44surrounded by enclosure52. However, the flight crew can still initiate one or more non-selected functional tests by actuating the associated non-identified test objects44using cursor56if desired.

Functional testing page16A shown inFIG.7shows two selected functional tests (WXR and ICE DETECT) being executed simultaneously in parallel together with a non-selected functional test (FIRE) that was separately initiated by the flight crew via the FIRE test object44. The simultaneous execution of the three functional tests is indicated by status indicators50indicating “IN PROG”.

FIG.8is a flowchart illustrating an exemplary method100for assisting with functional testing of systems36of aircraft10. Method100can be performed using apparatus24as described above or using another apparatus. In various embodiments, method100can comprise:receiving data indicative of condition38A of aircraft10(see block102);causing display device14to display a plurality of test objects44respectively associated with a plurality of functional tests of respective systems36of aircraft10(see block104);using the data indicative of condition38A of aircraft10, selecting one or more selected functional tests from the plurality of functional tests based on condition38A of aircraft10(see block106); andcausing display device14to identify one or more identified test objects44from the plurality of test objects44, the one or more identified test objects44being respectively associated with the one or more selected functional tests (see block108).

Method100can comprise causing display device14to display the identified test objects44according to a predetermined testing order (e.g., based on testing order data42). Method100can comprise initiating a plurality of the selected functional tests according to the predetermined testing order.

Method100can comprise causing display device14to display condition object54indicating aircraft condition38A. Condition object54can be responsive to user input indicative of aircraft condition38A.

Method100can comprise causing display device14to display execution object56configured to trigger an automated initiation of some (e.g. a plurality) or all of the selected functional tests in response to user input. Method100can comprise causing the execution of two or more of the selected functional tests in parallel.

Method100can comprise causing display device14to display status information (e.g., see status indicators50) associated with one or more of the test objects44.

Identifying the one or more test objects44can comprise visually distinguishing the one or more identified test objects44from any non-identified test objects44. In some embodiments, identifying the one or more test objects44can comprise causing display device14to display enclosure52that surrounds all identified test objects44.

One or more of test objects44can be responsive to respective user input using cursor46for example. Method100can comprise, in response to respective user input received at one or more test objects44, initiate respective one or more functional tests associated with the one or more test objects44.

In various embodiments, the functional tests of method100can be pre-flight functional tests. The data indicative of aircraft condition38A can be indicative of any of the following: whether a next flight of aircraft10is a first flight of a day; whether the next flight of aircraft10immediately follows a change in flight crew; and whether the next flight of aircraft10immediately follows a cold and dark start of aircraft10.

FIG.9is a flowchart illustrating an exemplary method200for assisting with functional testing of systems of aircraft10. Method200can be performed using apparatus24as described above or using another apparatus. In various embodiments, method200can comprise:receiving data indicative of condition38A of aircraft10(see block202);selecting, based on the data indicative of condition38A of aircraft10, two or more selected functional tests of respective two or more systems36of aircraft10(see block204); andinitiating the two or more selected functional tests (see block206).

Method200can comprise initiating the two or more selected functional tests according to a predetermined testing order (e.g., based on testing order data42).

Method200can comprise causing display device14to display execution object56configured to trigger an automated initiation of some (e.g., a plurality) or all of the selected functional tests in response to user input.

Method200can comprise causing display device14to display condition object54indicating aircraft condition38A. Condition object54can be responsive to user input that indicative of aircraft condition38A.

Method200can comprise causing an execution of at least two of the selected functional tests in parallel.

In various embodiments, the functional tests of method200can be pre-flight functional tests. The data indicative of aircraft condition38A can be indicative of any of the following: whether a next flight of aircraft10is a first flight of a day; whether the next flight of aircraft10immediately follows a change in flight crew; and whether the next flight of aircraft10immediately follows a cold and dark start of aircraft10.

The above description is meant to be exemplary only, and one skilled in the relevant arts will recognize that changes may be made to the embodiments described without departing from the scope of the invention disclosed. The present disclosure may be embodied in other specific forms without departing from the subject matter of the claims. The present disclosure is intended to cover and embrace all suitable changes in technology. Modifications which fall within the scope of the present invention will be apparent to those skilled in the art, in light of a review of this disclosure, and such modifications are intended to fall within the appended claims. Also, the scope of the claims should not be limited by the preferred embodiments set forth in the examples, but should be given the broadest interpretation consistent with the description as a whole.