System and method for automatically creating aircraft maintenance records from aircraft data

Abstract

The present invention is entitled "System and method for automatically creating aircraft maintenance records through aircraft data". The present invention discloses a method implemented by a processor, which is used to automatically create aircraft maintenance records and work logs during aircraft maintenance operations. The method includes: using a processor to retrieve fault data, test data, maintenance data and status data about line replaceable units (LRUs) on the aircraft via a central maintenance computer (CMC) on the aircraft; automatically collecting data about maintenance operations performed using the remote terminal from a remote terminal on the aircraft; automatically recording the fault data, test data, maintenance data, status data and data about maintenance operations performed using the remote terminal in a maintenance database by the processor; and automatically filling in information in multiple fields in the maintenance work log using the data in the maintenance database by the processor.

Description

Technical Field

[0001] The technology described in this patent document relates generally to aircraft maintenance systems and, more particularly, to aircraft maintenance systems for automatically recording maintenance actions and creating aircraft maintenance records. Background Art

[0002] Aircraft maintenance activities need to be recorded even though the time available for maintenance personnel to record their maintenance activities may be limited. Maintenance personnel often record after returning to their office, and often do so manually. This can result in important information not being included in the maintenance records.

[0003] Therefore, it is desirable to provide a system and method for automatically recording maintenance actions.Furthermore, other desirable features and characteristics of the present disclosure will become apparent from the subsequent detailed description and the appended claims, taken in conjunction with the accompanying drawings and the foregoing technical field and background. Summary of the invention

[0004] This summary is provided to describe a series of concepts in a simplified form, which are further described in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.

[0005] A processor-implemented method is disclosed for automatically creating an aircraft maintenance record and logbook during aircraft maintenance operations. The method includes: using a processor to retrieve fault data, test data, maintenance data, and status data about line replaceable units (LRUs) on the aircraft via a central maintenance computer (CMC) on the aircraft; automatically collecting data about maintenance operations performed using the remote terminal from a remote terminal on the aircraft; automatically recording the fault data, test data, maintenance data, status data, and data about maintenance operations performed using the remote terminal by the processor in a maintenance database; and automatically populating information in multiple fields in a maintenance logbook using the data in the maintenance database by the processor.

[0006] A maintenance record creation module is disclosed, which is configured to automatically create an aircraft maintenance record and a work log during an aircraft maintenance operation. The maintenance record creation module includes one or more processors on an aircraft configured by programming instructions on a non-transitory computer readable medium. The maintenance record creation module is configured to retrieve fault data, test data, maintenance data, and status data about line replaceable units (LRUs) on the aircraft via a central maintenance computer (CMC) on the aircraft; automatically collect data about maintenance operations performed using the remote terminal from a remote terminal on the aircraft; automatically record the fault data, test data, maintenance data, status data, and data about maintenance operations performed using the remote terminal in a maintenance database; and automatically fill in information in multiple fields in a maintenance work log using the data in the maintenance database.

[0007] An aircraft equipped with a maintenance system is disclosed, the maintenance system being configured to automatically create aircraft maintenance records and logbooks during aircraft maintenance operations. The aircraft includes a plurality of line replaceable units (LRUs), a central maintenance computer (CMC), and a remote terminal on the aircraft, the CMC being configured to communicate with the LRUs via an avionics system communication bus. The remote terminal is configured to: retrieve fault data, test data, maintenance data, and status data about the LRUs via the CMC; automatically collect data about maintenance operations performed using the remote terminal; automatically record the fault data, test data, maintenance data, status data, and data about maintenance operations performed using the remote terminal in a maintenance database; automatically populate information in a plurality of fields in a maintenance logbook using data in the maintenance database; automatically generate a report identifying data recorded in the maintenance database during the performance of maintenance operations; automatically update fields in a list of life-limited parts using data in the maintenance database; and automatically alert a maintainer to complete certain predetermined fields that are not automatically populated by a processor but are mandated to be completed by an administrative agency. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Aspects of the present disclosure are best understood from the following detailed description when read in conjunction with the accompanying drawings, wherein like numerals represent like elements, and

[0009] Figure 1 is a block diagram depicting an exemplary avionics system on an exemplary aircraft according to some embodiments;

[0010] Figure 2 is a block diagram depicting an exemplary maintenance system according to some embodiments;

[0011] Figure 3is a process flow diagram depicting an exemplary process for automatically creating aircraft maintenance records and work logs during aircraft maintenance operations in an aircraft maintenance system according to some embodiments; and

[0012] Figure 4 is a process flow diagram depicting an exemplary process for automatically recommending maintenance steps to maintenance personnel in an aircraft maintenance system according to some embodiments. DETAILED DESCRIPTION

[0013] The subject matter described herein discloses devices, systems, techniques, and articles for automatically creating aircraft maintenance records and work logs during aircraft maintenance operations. In addition, the subject matter described herein discloses devices, systems, techniques, and articles for recommending steps to be performed when troubleshooting a fault during a maintenance operation. The following specific embodiments are merely exemplary in nature and are not intended to limit the present invention or the application and use of the present invention. As used herein, the term "exemplary" means "used as an example, instance, or illustration". Therefore, any embodiment described herein as "exemplary" is not necessarily understood to be preferred or advantageous over other embodiments. All embodiments described herein are exemplary embodiments provided to enable a person skilled in the art to manufacture or use the present invention, without limiting the scope of the present invention as defined by the claims. In addition, it is not intended to be bound by any express or implied theory presented in the aforementioned technical field, background technology, content of the invention, or the following specific embodiments.

[0014] Figure 1 1 is a block diagram depicting an exemplary avionics system on an exemplary aircraft 100 and a maintenance system 102 configured to automatically record avionics system fault information, automatically detect and record maintenance actions taken, and automatically populate fields in a maintenance record 101, such as a logbook. The exemplary aircraft includes a plurality of line replaceable units (LRUs) 104 that can communicate status information to a central maintenance computer (CMC) 106 via a communication bus 108, such as an avionics system communication bus (ASCB). The exemplary aircraft also includes a remote terminal 110 and a data repository 112, both of which are part of the exemplary maintenance system 102. The exemplary maintenance system 102 also includes a recommendation system 114 located remotely from the aircraft.

[0015] The LRUs 104 in the exemplary aircraft 100 may include various aircraft components, such as IGV actuators, fuel modules, surge control valves, drain valves, lubricant modules, starter / generator systems, exciters, etc. The exemplary CMC 106 is configured to retrieve status information about the LRUs 104 via the ASCB 108, such as the software / hardware part number of the LRU, the serial number of the LRU, the time and date of LRU replacement, the time and date of LRU reset, and other status information.

[0016] The exemplary remote terminal 110 may be implemented using any suitable hardware platform and realized as a computer-implemented or computer-based device having the hardware, software, firmware and / or processing logic required to perform the various techniques and methods described herein. When performing maintenance actions on an avionics system (e.g., an LRU), a maintenance person may use the exemplary remote terminal 110, and the exemplary remote terminal is configured to automatically capture LRU status information from the CMC 106, automatically record the LRU status information in the data repository 112, and automatically capture and record the maintenance actions performed using the remote terminal 110 in the data repository 112.

[0017] The exemplary remote terminal 110 is also configured to automatically populate entries in maintenance records commonly used in the industry, such as the work log 101. The exemplary remote terminal is configured to automatically populate pre-existing fields (e.g., industry standard fields) in the work log 101 and automatically record on the work log 101 a detailed description of the troubleshooting steps performed by the maintenance personnel.

[0018] The exemplary remote terminal 110 is further configured to cooperate with the recommendation system 114 for providing maintenance personnel with recommendations on maintenance steps to be performed. The exemplary recommendation system 114 is configured for use by maintenance personnel to troubleshoot avionics equipment failures and includes a ground-based terminal that can be implemented using any suitable hardware platform. In this regard, the ground-based terminal can be implemented in any common form factor, including but not limited to: a desktop computer; a mobile computer (e.g., a tablet, laptop, or netbook computer); a smart phone; a video game device; a digital media player; a home entertainment device; a digital camera or camcorder; a wearable computing device (e.g., a smart watch, smart glasses, smart clothing), etc. Each ground-based terminal supported by the recommendation system 114 is implemented as a computer-implemented or computer-based device having the hardware, software, firmware, and / or processing logic required to perform the various techniques and methods described herein.

[0019] The exemplary recommendation system 114 is configured to assist maintenance personnel in troubleshooting avionics failures by making recommendations based on stored LRU status information and stored information about performed maintenance actions stored in the data repository 112. The exemplary recommendation system 114 may incorporate various machine learning techniques and algorithms to form maintenance action recommendations for maintenance personnel.

[0020] Figure 2 is a block diagram depicting an exemplary maintenance system 200. The exemplary maintenance system 200 includes a recommendation system 204 and a maintenance record creation module 202 in a remote terminal 203 on an aircraft. The exemplary maintenance record creation module 202 includes: a plurality of modules configured to capture and store information about various avionics systems in a maintenance database 206; and a plurality of modules configured to retrieve information from the maintenance database 206 to automatically populate fields in various documents and reports. The exemplary maintenance record creation module 202 is configured to automatically create aircraft maintenance records and work logs during aircraft maintenance operations.

[0021] The exemplary maintenance record creation module 202 can be implemented using a controller in an aircraft remote terminal. The controller includes at least one processor and a computer-readable storage device or a medium encoded with programming instructions for configuring the controller. The processor can be any custom or commercially available processor, a central processing unit (CPU), a graphics processing unit (GPU), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), an auxiliary processor of several processors associated with the controller, a semiconductor-based microprocessor (in the form of a microchip or chipset), any combination thereof, or any device generally used to execute instructions.

[0022] Computer readable storage devices or media may include volatile and non-volatile storage devices such as read-only memory (ROM), random access memory (RAM), and keep-alive memory (KAM). KAM is a persistent or non-volatile memory that can be used to store various operating variables when the processor is powered off. Computer readable storage devices or media can be implemented using any of a number of known memory devices, such as PROM (programmable read-only memory), EPROM (electrical PROM), EEPROM (electrically erasable PROM), flash memory, or any other electrical, magnetic, optical, or combination memory device capable of storing data, some of which represent executable programming instructions used by the controller.

[0023] The exemplary maintenance record creation module 202 is configured to facilitate comprehensive recording of maintenance actions performed using the remote terminal 203. In an exemplary operation scenario, when a maintainer (e.g., a maintenance personnel) begins a maintenance operation, the maintainer switches the aircraft to a maintenance mode via a cockpit switch. The exemplary maintenance record creation module 202 is configured to record each action performed by the maintainer via the remote terminal 203 as the maintainer navigates through different pages in the remote terminal while troubleshooting an avionics failure. An exemplary operation flow followed by a maintainer using the remote terminal 203 includes the following: (a) the maintainer accesses an active fault page (for active fault messages); (b) the maintainer views the details of the fault; (c) the maintainer views the member (e.g., LRU) system status of the member experiencing the fault; and (d) the maintainer initiates a built-in test / system test for the member experiencing the fault. The exemplary maintenance record creation module 202 is configured to capture and record received messages and actions taken by the maintainer. After maintenance is completed, the example maintenance record creation module 202 may automatically generate a report detailing recorded aircraft data regarding the maintenance operations performed on the avionics unit.

[0024] The exemplary maintenance record creation module 202 is also configured to capture maintenance actions performed by inspecting aircraft data via the aircraft bus. Exemplary maintenance actions that may be captured include the following: (1) replacing an LRU, which may be identified by inspecting configuration data retrieved by the CMC; (2) identifying a module reset, which may be identified by monitoring the aircraft data for circuit breaker switch states or monitoring AC / DC bus status parameters, as power cycles are associated with module resets; (3) identification of CMC tests performed and results of CMC tests may be retrieved directly from the CMC, as the CMC may maintain a history of CMC tests performed and save the test results in CMC persistent storage; (4) identification and results received from electronic checks performed (e.g., short circuit tests) may be retrieved from the avionics system; and (5) identification and results received from status tests performed may be retrieved from the avionics system.

[0025] The exemplary maintenance record creation module 202 is also configured to automatically fill in certain fields in the maintenance record. For example, the FAA form 337 is used to record major repairs and major changes to aircraft avionics or their component parts. The personnel who perform or supervise major repairs or major changes must prepare the FAA form 337. The exemplary maintenance record creation module 202 is configured to automatically fill in certain fields in the FAA form 337. The exemplary maintenance record creation module 202 is also configured to automatically fill in certain fields in other maintenance records such as work logs. Exemplary fields that can be automatically filled include: part number, serial number, description, and service time. The exemplary maintenance record creation module 202 is configured to record the part number and serial number information retrieved from the CMC on the maintenance record, and is configured to automatically fill in the description field using actions performed by the maintainer at the remote terminal and captured by the module. The exemplary maintenance record creation module 202 is further configured to retrieve information about the service time of the LRU from the CMC, which tracks the service time of each LRU.

[0026] The example maintenance record creation module 202 is also configured to update fields in the life-limited parts list. Many operators / owners keep a separate record of life-limited parts that identifies the part name, part number, serial number, installation date, total service time, removal date, signature, and certification number of the person who performed the fault diagnosis. The example maintenance record creation module 202 is configured to automatically update the life-limited parts list using data from the work log.

[0027] The example maintenance record creation module 202 is also configured to generate a user warning to warn the user to manually fill in certain mandatory fields (e.g., FAA mandatory fields) required to complete the work log. The example maintenance record creation module 202 can then provide a report that can be used as an official work log related to the avionics equipment failure troubleshooting.

[0028] The exemplary maintenance record creation module 202 includes an aircraft data retrieval module 208, a remote terminal maintenance action tracker module 210, and a recorder module 212. The aircraft data retrieval module 208 is configured to retrieve fault data, LRU replacement data, LRU reset data, CMC test data, electronic inspection data, and LRU status data about LRUs on the aircraft via the CMC 214. The remote terminal maintenance action tracker module 210 is configured to track and collect data about maintenance actions performed by a maintainer using the remote terminal 203. The recorder module 212 is configured to record the data retrieved by the aircraft data retrieval module 208 and the data collected by the remote terminal maintenance action tracker module 210 in the maintenance database 206.

[0029] The exemplary maintenance record creation module 202 also includes a report generator module 216, a logbook field filling module 218, a maintenance report field filling module 220, and a maintainer warning module 222. The report generator module 216 is configured to automatically generate an aircraft data report 217 of aircraft data collected and recorded in a maintenance database during a maintenance operation. The logbook field filling module 218 is configured to automatically fill in information in a plurality of fields in a maintenance logbook 219 using data in the maintenance database. The maintenance report field filling module 220 is configured to automatically update fields in a maintenance report 221, such as a list of life-limited parts, using data in the maintenance database. The maintainer warning module 222 is configured to automatically warn the maintainer via a user interface 223 to complete certain predetermined fields that are not automatically filled in by the maintenance record creation module 202 but are mandated to be completed by an administrative agency.

[0030] The recommendation system 204 can be implemented using a controller in an aircraft remote terminal, configured to be used by maintenance personnel to troubleshoot avionics failures, and includes a ground-based terminal that can be implemented using any suitable hardware platform. The exemplary recommendation system 204 is configured to help maintenance personnel troubleshoot avionics failures by making recommendations based on stored LRU status information and stored information about the maintenance actions performed stored in the maintenance database 206. The exemplary recommendation system 204 can combine various machine learning techniques and / or algorithms to form maintenance action recommendations for maintenance personnel. Maintenance data collected over time can also be used to prepare a complete avionics maintenance profile for an aircraft. In addition, maintenance personnel can receive insights about ways to solve the failure, which may not be seen by viewing the maintenance manual. Since the exemplary maintenance record creation module 202 is configured to record each action performed by the maintainer when troubleshooting the avionics system, the exemplary recommendation system can access the recorded steps and warn the maintainer of the steps that may be missing in the maintenance manual.

[0031] Figure 3 1 is a process flow diagram depicting an exemplary process 300 for automatically creating aircraft maintenance records and work logs during aircraft maintenance operations in an aircraft maintenance system. The order of operations within the process is not limited to the following. Figure 3 Rather, the sequences shown are not intended to be performed in the order shown, but may be performed in one or more altered sequences as applicable and in accordance with the present disclosure.

[0032] The exemplary process 300 includes retrieving fault data, test data, maintenance data, and status data about LRUs on the aircraft via a processor on the aircraft via a CMC on the aircraft (operation 302). The fault data may include fault information about the LRU on the ASCB retrieved by the CMC. The test data may include the identification of any diagnostic tests performed on the LRU and the results of the diagnostic tests performed. The identification of the diagnostic tests performed may include the identification of the ASCB parameters investigated. The test data may also include the identification of the electronic inspections performed and the results thereof. The electronic inspection may include performing short circuit tests by monitoring the intelligent LRU configuration and the non-intelligent LRU configuration. The maintenance data may include data identifying changes to the configuration of the aircraft avionics system during the maintenance operation (e.g., whether the LRU was replaced during the maintenance operation), data identifying whether the LRU was reset during the maintenance operation, and the identification of the maintenance manual used for fault diagnosis. The status data may include data indicating the operating state of the LRU and configuration information about the LRU, wherein the configuration information may include the software and hardware configuration of the LRU and its associated non-intelligent LRU.

[0033] Exemplary process 300 also includes automatically collecting maintenance data from the remote terminal on the aircraft regarding maintenance operations performed by the maintainer using the remote terminal (operation 304). The maintenance data may include a record of each action performed by the maintainer while using the remote terminal as the maintainer navigates through different pages presented at the remote terminal while troubleshooting avionics equipment failures. Automatic performance of operations 302 and 304 may reduce human error and reduce the workload of recording when recording maintenance actions.

[0034] The exemplary process 300 includes automatically recording in a maintenance database the fault data, test data, maintenance data, and status data retrieved from the CMC and the maintenance data collected from the remote terminal during the maintenance operation (operation 306). After the maintenance operation is completed, a report identifying the data recorded in the maintenance database during the performance of the maintenance operation can be automatically generated (operation 308).

[0035] Exemplary process 300 includes automatically populating information in a plurality of fields in a maintenance log (operation 310). The plurality of fields in the maintenance log may include a part number field, a serial number field associated with the part number field, a description field associated with the part number field, and a service time field associated with the part number field, wherein the information populated in the description field includes a description of an action performed by an aircraft maintainer on an avionics system of the aircraft.

[0036] The exemplary process 300 includes automatically updating fields in the list of life-limited parts (operation 312). The life-limited parts fields may include the name of the part, a part number associated with the part, a serial number associated with the part, an installation date of the part, a total service time of the part, a date the part was removed, and a signature and certification number of a person who performed fault diagnosis on the associated part.

[0037] The exemplary process 300 includes automatically alerting the maintenance personnel to complete certain predetermined fields that are not automatically populated by the processor but are mandatory by the management agency (operation 314). The alert may include using an audible alert, a visual alert on a display screen, or a combination of audible and visual alerts.

[0038] Figure 4 4 is a process flow diagram depicting an exemplary process 400 for automatically recommending maintenance steps to maintenance personnel in an aircraft maintenance system. The order of operations within the process is not limited to the following. Figure 4 Rather, the sequences shown are not intended to be performed in the order shown, but may be performed in one or more altered sequences as applicable and in accordance with the present disclosure.

[0039] The exemplary process 400 includes retrieving fault data, test data, maintenance data, and status data about LRUs on the aircraft via a processor on the aircraft via a CMC on the aircraft (operation 402). The fault data may include fault information about the LRU on the ASCB retrieved by the CMC. The test data may include the identification of any diagnostic tests performed on the LRU and the results of the diagnostic tests performed. The identification of the diagnostic tests performed may include the identification of the ASCB parameters studied. The test data may also include the identification of the electronic inspections performed and their results. The electronic inspection may include short circuit tests performed by monitoring the configuration of smart and non-intelligent LRUs. The maintenance data may include data identifying changes to the configuration of the aircraft avionics system during the maintenance operation (e.g., whether the LRU was replaced during the maintenance operation), data identifying whether the LRU was reset during the maintenance operation, and the identification of the maintenance manual used for fault diagnosis. The status data may include data indicating the operating state of the LRU and configuration information about the LRU, wherein the configuration information may include the software and hardware configuration of the LRU and its associated non-intelligent LRU.

[0040] Exemplary process 400 also includes automatically collecting maintenance data from the remote terminal on the aircraft regarding maintenance operations performed by the maintainer using the remote terminal, operation 404. The maintenance data may include a record of each action performed by the maintainer while using the remote terminal as the maintainer navigates through different pages presented at the remote terminal while troubleshooting an avionics fault.

[0041] The example process 400 also includes automatically recording in a maintenance database the fault data, test data, maintenance data, and status data retrieved from the CMC and the maintenance data collected from the remote terminal during the maintenance operation (operation 406).

[0042] The exemplary process 400 includes retrieving stored data from a maintenance database (operation 408) and analyzing the retrieved data to generate a recommended maintenance action (operation 410). Various machine learning techniques and / or algorithms may be used to analyze the data from the maintenance database to form maintenance action recommendations for maintenance personnel. Finally, the exemplary process 400 includes recommending a recommended maintenance action to a maintenance personnel based on the analysis of the data from the maintenance database (operation 412).

[0043] Techniques described herein may allow for recording each maintenance action performed by a maintainer on an avionics system on an aircraft by comprehensively recording the maintenance actions performed by the maintainer when troubleshooting an avionics fault using a remote terminal and by viewing the maintenance actions performed by the aircraft data capture on an aircraft bus. Techniques in an aircraft maintenance system are also described herein for automatically creating aircraft maintenance records and work logs during aircraft maintenance operations. Additionally, techniques in an aircraft maintenance system are described herein for recommending to a maintainer a suggested maintenance step for troubleshooting a fault.

[0044] In one embodiment, a processor-implemented method for automatically creating aircraft maintenance records and logbooks during aircraft maintenance operations is disclosed. The method includes: using a processor to retrieve fault data, test data, maintenance data, and status data about line replaceable units (LRUs) on the aircraft via a central maintenance computer (CMC) on the aircraft; automatically collecting data about maintenance operations performed using the remote terminal from a remote terminal on the aircraft; automatically recording the fault data, test data, maintenance data, status data, and data about maintenance operations performed using the remote terminal by the processor in a maintenance database; and automatically populating information in multiple fields in a maintenance logbook using data in the maintenance database by the processor.

[0045] These aspects and other embodiments may include one or more of the following features. The method may also include automatically generating, by the processor, a report identifying data recorded in a maintenance database during the execution of a maintenance operation. The method may also include automatically updating, by the processor, fields in a list of life-limited components using data in the maintenance database. The method may also include automatically alerting a maintainer to complete certain predetermined fields that are not automatically filled by the processor but are forced to be completed by an administrative agency. The method may also include analyzing data from the maintenance database to generate a suggested maintenance action and recommending the suggested maintenance action to the maintainer. Fault data may include fault information about at least one LRU retrieved by the CMC. Test data may include an identification of any diagnostic test performed on at least one LRU and results from the performed diagnostic test. The identification of the performed diagnostic test may include an identification of an ASCB (avionics system communication bus) parameter under investigation. Test data may include data identifying an electronic check performed and its results, wherein the electronic check includes a short circuit test performed by monitoring an intelligent LRU configuration and a non-intelligent LRU configuration. The maintenance data may include data identifying changes to the configuration of the aircraft avionics system made during the maintenance operation; data identifying whether the LRU was reset during the maintenance operation; and data identifying a maintenance manual for fault diagnosis. The status data may include data indicating the operating status of at least one of the LRUs and configuration information about at least one of the LRUs, wherein the configuration information includes the software and hardware configuration of the LRU and its associated non-intelligent LRU. The data about maintenance operations performed using the remote terminal may include a record of each action performed by the maintainer using the remote terminal as the maintainer traverses different pages presented at the remote terminal when troubleshooting avionics equipment failures. The multiple fields in the maintenance work log may include a part number field, a serial number field related to the part number field, a description field related to the part number field, and a service time field related to the part number field, wherein the information populated in the description field includes a description of the actions performed by the aircraft maintenance personnel on the avionics system of the aircraft. The limited life part field may include the name of the part, the part number associated with the part, the serial number associated with the part, the date the part was installed, the total service time of the part, the date the part was removed, and the signature and certification number of the person who performed the fault diagnosis on the relevant part.

[0046] In another embodiment, a maintenance record creation module is disclosed, which is configured to automatically create aircraft maintenance records and work logs during aircraft maintenance operations. The maintenance record creation module includes one or more processors on the aircraft configured by programming instructions on a non-transitory computer readable medium. The maintenance record creation module is configured to retrieve fault data, test data, maintenance data, and status data about line replaceable units (LRUs) on the aircraft via a central maintenance computer (CMC) on the aircraft; automatically collect data about maintenance operations performed using the remote terminal from a remote terminal on the aircraft; automatically record fault data, test data, maintenance data, status data, and data about maintenance operations performed using the remote terminal in a maintenance database; and use the data in the maintenance database to automatically fill in information in multiple fields in the maintenance work log.

[0047] These aspects and other embodiments may include one or more of the following features. The maintenance record creation module may be further configured to automatically generate a report identifying data recorded in the maintenance database during the performance of the maintenance operation. The maintenance record creation module may be further configured to automatically update fields in the list of life-limited components using data in the maintenance database. The maintenance record creation module may be further configured to automatically alert the maintainer to complete certain predetermined fields that are not automatically populated by the processor but are mandated by an administrative agency.

[0048] In another embodiment, an aircraft equipped with a maintenance system is disclosed, the maintenance system being configured to automatically create aircraft maintenance records and work logs during aircraft maintenance operations. The aircraft includes a plurality of line replaceable units (LRUs), a central maintenance computer (CMC) configured to communicate with the LRUs via an avionics system communication bus, and a remote terminal on the aircraft. The remote terminal is configured to: retrieve fault data, test data, maintenance data, and status data about the LRUs via the CMC; automatically collect data about maintenance operations performed using the remote terminal; automatically record fault data, test data, maintenance data, status data, and data about maintenance operations performed using the remote terminal in a maintenance database; automatically populate information in a plurality of fields in a maintenance work log using data in the maintenance database; automatically generate a report identifying data recorded in the maintenance database during the performance of maintenance operations; automatically update fields in a list of life-limited parts using data in the maintenance database; and automatically alert a maintainer to complete certain predetermined fields that are not automatically populated by a processor but are mandated to be completed by an administrative agency.

[0049] These aspects and other embodiments may include one or more of the following features.The remote terminal may be further configured to analyze data from the maintenance database to generate suggested maintenance actions and recommend the suggested maintenance actions to maintenance personnel.

[0050] It will be understood by those skilled in the art that the various exemplary logic boxes, modules, circuits and algorithm steps described in conjunction with the embodiments disclosed herein can be implemented as electronic hardware, computer software or a combination of the two. Some embodiments and implementations are described above in terms of functions and / or logic box components (or modules) and various processing steps. However, it should be understood that such box components (or modules) can be implemented by any number of hardware, software and / or firmware components configured to perform a specified function. In order to clearly illustrate this interchangeability of hardware and software, various illustrative components, boxes, modules, circuits and steps have been generally described above with respect to their functions. Whether such functions are implemented as hardware or software depends on the specific application and the design constraints imposed on the entire system. The technician can implement the described functions in different ways for each specific application, but such implementation decisions should not be interpreted as causing deviations from the scope of the present invention. For example, the implementation of a system or component can use various integrated circuit components, such as memory elements, digital signal processing elements, logic elements, lookup tables, etc., which can perform multiple functions under the control of one or more microprocessors or other control devices. In addition, it will be understood by those skilled in the art that the embodiments described herein are only exemplary embodiments.

[0051] The various exemplary logic blocks, modules, and circuits described in conjunction with the embodiments disclosed herein may be implemented or performed using a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0052] The steps of the methods and algorithms described in conjunction with the embodiments disclosed herein may be directly embodied in hardware, software modules executed by a processor, or a combination of the two. The software module may reside in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. In an alternative, the storage medium may be integrated into the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In an alternative, the processor and the storage medium may reside in a user terminal as discrete components.

[0053] In this document, relational terms, such as first and second, etc., may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Unless expressly limited by the claim language, numerical ordinals, such as "first," "second," "third," etc., merely represent different individuals among a plurality of individuals and do not imply any order or sequence. Unless expressly limited by the claim language, the sequence of text in any claim does not imply that processing steps must be performed in a temporal or logical order according to such sequence. Processing steps may be interchanged in any order if such interchange does not contradict the claim language and is not logically absurd without departing from the scope of the invention.

[0054] In addition, depending on the context, words such as "connected" or "coupled to" used when describing the relationship between different elements do not imply that a direct physical connection must be made between these elements. For example, two elements may be connected to each other physically, electronically, logically, or in any other way through one or more additional elements.

[0055] Although at least one exemplary embodiment has been presented in the aforementioned specific embodiments of the present invention, it should be understood that there are a large number of variations. For example, in other embodiments, exemplary processes 200, 300, 400 and 500 can be performed by a communication module equipped with an engine. It should also be understood that one or more exemplary embodiments are only examples and are not intended to limit the scope, applicability or configuration of the present invention in any way. On the contrary, the aforementioned specific embodiments will provide a convenient roadmap for realizing the exemplary embodiments of the present invention for those skilled in the art. It should be understood that, without departing from the scope of the present invention as set forth in the appended claims, various changes can be made to the function and arrangement of the elements described in the exemplary embodiments.

Claims

1. A processor-implemented method for automatically creating aircraft maintenance records and logbooks during aircraft maintenance operations, the method comprising: retrieving, via a central maintenance computer (CMC) on the aircraft, fault data, test data, maintenance data, and status data on a line replaceable unit (LRU) on the aircraft using a processor; automatically collecting, from a remote terminal onboard the aircraft, data regarding maintenance operations performed using the remote terminal, wherein the data regarding maintenance operations performed includes a record of actions performed using the remote terminal to troubleshoot avionics equipment failures; automatically recording, by the processor in a maintenance database, (1) the fault data, test data, maintenance data, and status data retrieved from the CMC of the aircraft, and (2) data regarding maintenance operations performed using the remote terminal; using, by the processor, the data in the maintenance database to automatically populate a plurality of fields in a maintenance work log with automatically collected data regarding the actions performed using the remote terminal to troubleshoot an avionics equipment fault; as well as Alert maintainers to missing steps in maintenance manuals.

2. The method according to claim 1, further comprising: A report is automatically generated by the processor, the report identifying data recorded in the maintenance database during the aircraft maintenance operation.

3. The method according to claim 1, further comprising: Fields in the list of life-limited components are automatically updated by the processor using data in the maintenance database.

4. The method according to claim 1, further comprising: The maintainer is automatically alerted to complete certain predetermined fields that are not automatically populated by the processor but are mandated by an administrative agency.

5. The method according to claim 1, further comprising: analyzing data from the maintenance database to generate recommended maintenance actions; as well as The suggested maintenance action is recommended to maintenance personnel.

6. A maintenance record creation module, the maintenance record creation module configured to automatically create an aircraft maintenance record and a work log during an aircraft maintenance operation, the maintenance record creation module comprising one or more processors on an aircraft configured by programming instructions on a non-transitory computer readable medium, the maintenance record creation module configured to: retrieving, via a central maintenance computer (CMC) on the aircraft, fault data, test data, maintenance data, and status data regarding line replaceable units (LRUs) on the aircraft; automatically collecting, from a remote terminal onboard the aircraft, data regarding maintenance operations performed using the remote terminal, wherein the data regarding maintenance operations performed includes a record of actions performed using the remote terminal to troubleshoot avionics equipment failures; automatically recording in a maintenance database (1) the fault data, test data, maintenance data, and status data retrieved from the CMC of the aircraft, and (2) data regarding maintenance operations performed using the remote terminal; as well as using data in the maintenance database to automatically populate a plurality of fields in a maintenance work log with automatically collected data regarding the maintenance operations performed using the remote terminal; as well as Alert maintainers to missing steps in maintenance manuals.

7. The maintenance record creation module according to claim 6, further configured to: A report is automatically generated that identifies data recorded in the maintenance database during the aircraft maintenance operation.

8. The maintenance record creation module according to claim 6, further configured to: Fields in a list of life-limited components are automatically updated using the data in the maintenance database.

9. The maintenance record creation module according to claim 6, further configured to: The maintainer is automatically alerted to complete certain predetermined fields that are not automatically populated by the processor but are mandated by an administrative agency.

10. The maintenance record creation module according to claim 6, further configured to: analyzing data from the maintenance database to generate recommended maintenance actions; and The suggested maintenance action is recommended to maintenance personnel.

Images