Method and system for generating fault records in leg logs

Abstract

The invention discloses a method and a system for generating a fault record in a leg log. In one embodiment, the method for generating the fault record in the leg log can comprise the steps that multiple events are obtained in a leg to generate an event list, and the multiple events comprise all triggered alarms, all alarm processing historical records and events manually recorded by a unit; respectively determining whether each event in the plurality of events meets a recording rule or not; in response to determining that one event includes that the recording rule is not met, removing the event from the event list; and generating a final fault record. The method provided by the invention can accurately record events required by each process and visually display the events. In addition, the method provided by the invention can transmit the fault record in the flight segment log to the ground maintenance equipment and / or the portable electronic flight log book, improves the maintenance efficiency, ensures that the unit can accurately sense the subsequent abnormal condition, and improves the flight safety.

Description

Technical Field

[0001] The present disclosure relates to the field of avionics systems, and more particularly to a method and system for generating fault records in a flight segment log. Background Art

[0002] According to the relevant requirements of the civil aviation, the flight logbook should record flight information, defects and abnormal conditions found during the flight, and maintenance work performed; operational information related to flight safety, data that the crew and maintenance personnel need to know; any defects and retention conditions that affect airworthiness and safe operation, maintenance items, maintenance status records, releases, etc. Usually, the flight logbook is completed by the crew and maintenance personnel. The crew is responsible for recording the problems found during the flight after the flight, while the maintenance personnel are responsible for recording related information such as maintenance and releases.

[0003] Under normal circumstances, there are few abnormal situations during flight. For alarms that are still activated, they can be viewed through the onboard alarm system. For other situations, the crew can manually complete the filling of relevant items in the flight logbook. However, people's judgment varies from person to person, and there is no uniform standard for filling. In addition, people's memory also varies from person to person and is easily interfered by external factors, which may cause incorrect filling, missing filling, and over-filling. For example, when the alarm condition exists briefly and then disappears, the alarm is associated with multiple derivative faults, there is too much alarm information, etc., the crew may not be able to fully record the abnormal situation, resulting in the subsequent crew being unable to accurately know the abnormal situation of the previous flight, and the maintenance personnel are unable to accurately perform the necessary inspections and maintenance on the aircraft, thereby posing a hidden danger to flight safety.

[0004] Therefore, there is an urgent need for a method that can generate a complete and unified automatic generation of segment fault history applicable to a flight log to achieve efficient maintenance of an aircraft. Summary of the invention

[0005] A brief summary of one or more aspects is given below to provide a basic understanding of such aspects. This summary is not an exhaustive overview of all conceived aspects, and is neither intended to identify the key or critical elements of all aspects nor to define the scope of any or all aspects. Its only purpose is to give some concepts of one or more aspects in a simplified form as a prelude to a more detailed description that will be given later.

[0006] In order to solve some of the above existing problems, the present disclosure proposes a method and system for generating fault records in a flight segment log. The method provided by the present disclosure can accurately record the events required for each process and intuitively display these events. In addition, the method provided by the present disclosure can transmit the fault records in the flight segment log to ground maintenance equipment and / or a portable electronic flight log, thereby improving the efficiency of aircraft maintenance, ensuring that the crew can accurately perceive subsequent abnormal situations, and improving flight safety.

[0007] A first aspect of the present disclosure provides a method for generating a fault record in a flight segment log. The method may include: obtaining multiple events in a flight segment to generate an event list, wherein the multiple events include: all triggered alarms, all alarm handling history records, and events manually recorded by the crew; determining whether each of the multiple events meets the recording rule; in response to determining that there is an event that does not meet the recording rule, removing the event from the event list; and generating a final fault record.

[0008] In one embodiment, optionally, the event may further include information indicating: the occurrence time, flight stage, and current status of each of all triggered alarms; the handling method and completion time of all handled alarms; or the order, recording time, and flight stage of each of the events manually recorded by the crew members.

[0009] In one embodiment, optionally, the current state includes whether the trigger condition is still activated, or has been released and the release time.

[0010] In one embodiment, optionally, the plurality of events may include three display areas, wherein the first display area displays events that are still activated, the second display area displays events that have been resolved after being processed, and the third display area displays events that have not been processed but have been resolved.

[0011] In one embodiment, optionally, the recording rules may include: in response to determining that one of all triggered alarms belongs to an operational alarm, a flight envelope alarm, an operational feedback alarm or a derivative failure alarm, removing events corresponding to the alarm and events related to the alarm handling history.

[0012] In one embodiment, optionally, the method may further include: transmitting a final fault record to a ground maintenance device and / or a portable electronic flight logbook after the flight of the flight segment ends.

[0013] In one embodiment, optionally, the ground maintenance equipment may store the finally generated flight segment log and the route information and crew information corresponding to the flight segment in a database.

[0014] In one embodiment, optionally, the ground maintenance equipment may call previously stored flight segment logs that are the same or similar to the route information and crew information from the database to search for recurring events.

[0015] A second aspect of the present disclosure provides a system for generating a fault record in a flight segment log. The system may further include: a memory and a processor coupled to the memory. The processor may be configured to execute the above method.

[0016] A third aspect of the present disclosure provides a non-transitory computer-readable storage medium having stored thereon instructions for generating a fault record in a flight segment log, the instructions being executable by a processor to perform the above method.

[0017] The present disclosure is provided to introduce some concepts in a simplified form, which will be further described in the following specific embodiments. The present disclosure is not intended to identify the key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. Other aspects, features and / or advantages of each embodiment will be set forth in part in the following description, and will be apparent in part from the description, or can be learned through the practice of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to understand in detail the manner in which the above-stated features of the present disclosure are employed, a more particular description of the content briefly summarized above may be made with reference to various aspects, some of which are illustrated in the accompanying drawings. It should be noted, however, that the accompanying drawings illustrate only certain typical aspects of the present disclosure and are not to be considered limiting of its scope, as the description may admit to other equally effective aspects. In the drawings:

[0019] Figure 1 A flow chart of a method for generating a fault record in a flight segment log according to an embodiment of the present disclosure is shown.

[0020] Figures 2A-2D Examples of various types of events according to an embodiment of the present disclosure are shown.

[0021] Figure 3 A logical block diagram of a recording rule according to an embodiment of the present disclosure is shown.

[0022] Figure 4 An example of displaying a flight segment log according to an embodiment of the present disclosure is shown.

[0023] Figure 5 A block diagram of a device including a system for generating a fault record in a flight segment log according to one embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0024] The specific embodiments described below in conjunction with the accompanying drawings are intended as descriptions of various configurations and are not intended to represent the only configurations in which the concepts described herein may be practiced. This specific embodiment includes specific details to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details.

[0025] Based on this teaching, it will be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects described can be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods practiced using other structures, functionality, or structures and functionality that are supplementary to or different from the various aspects of the present disclosure described.

[0026] Although specific aspects are described herein, numerous variations and permutations of these aspects fall within the scope of the present disclosure. Although some benefits and advantages of preferred aspects are mentioned, the scope of the present disclosure is not intended to be limited to specific benefits, uses or objectives. The specific embodiments and the accompanying drawings merely illustrate the present disclosure rather than limit the present disclosure, and the scope of the present disclosure is defined by the attached claims and their equivalent technical solutions.

[0027] The relevant requirements of civil aviation clearly stipulate that the flight logbook should record relevant information during the flight, such as warnings, abnormal situations, etc. The flight logbook is usually completed by the crew and the maintenance staff. The crew is responsible for recording the problems found during the flight after the flight, while the maintenance staff is responsible for recording relevant information such as maintenance and release. Under normal circumstances, there are few abnormal situations during the flight. For warnings that are still activated, they can be accessed through the onboard warning system. For other situations, the crew can manually complete the filling of relevant items in the flight logbook. However, people's judgments vary from person to person, and there is no uniform standard for filling. In addition, people's memory also varies from person to person and is easily interfered by external factors, which may cause incorrect filling, missing filling, and over-filling. For example, when the warning condition exists briefly and then disappears, the warning is associated with multiple derivative faults, there are too many warning messages, etc., the crew may not be able to fully record the abnormal situation, resulting in the subsequent crew being unable to accurately know the abnormal situation of the previous flight, and the maintenance personnel being unable to accurately perform the necessary inspection and maintenance on the aircraft, thus bringing hidden dangers to flight safety.

[0028] In order to solve some of the above-mentioned existing problems, the present disclosure proposes a method and system for generating a flight log (e.g., a flight segment log). The method provided by the present disclosure can accurately record the events required for each process and intuitively display these events. In addition, the method provided by the present disclosure can transmit fault records in the flight segment log to ground maintenance equipment and / or a portable electronic flight log, thereby improving maintenance efficiency, ensuring that the crew can accurately perceive subsequent abnormal situations, and improving flight safety. The present disclosure is further described below in conjunction with specific embodiments and drawings, but the scope of protection of the present disclosure should not be limited thereby.

[0029] Figure 1 A flowchart 100 of a method 100 for generating a fault record in a segment log according to an embodiment of the present disclosure is shown. In some cases, the method 100 for generating a fault record in a segment log may be performed by a system such as a system for generating a fault record in a segment log. In one example, the system for generating a fault record in a segment log may include a memory and a processor coupled to the memory, wherein the processor may be configured to execute the method 100 for generating a fault record in a segment log. In some cases, the system for generating a fault record in a segment log may be an independent system. In some alternative cases, the system for generating a fault record in a segment log may be inherited in an onboard flight control system.

[0030] In this embodiment, the method 100 for generating a fault record in a flight segment log may include the following steps.

[0031] In step 105, the system may obtain multiple events within a flight segment to generate an event list. In one example, the multiple events include: all triggered alarms, all alarm handling history records, and events manually recorded by the crew. In an optional example, all triggered alarm messages may be obtained from the crew display and alarm system. In an optional example, the event manually recorded by the crew may be an event input by the crew via a human-computer interaction interface, such as triggered by pressing a specific physical key. In an optional example, the event further includes information indicating the following: the occurrence time, flight phase, and current status of each of all triggered alarms; the handling method and completion time of all handled alarms, including such as the completion status of the checklist, the completion status of each operation item, and the handling status of the override or branch options, etc.; or the order, recording time, and flight phase of each event manually recorded by the crew. In some cases, the current status includes whether the triggering condition is still activated, or has been released and the release time. For example, the system can usually obtain alarm and alarm handling related information from the crew display and alarm system (FDAS system). As another example, the system may typically obtain manually recorded events from a recording system (eg, a recording system associated with a flight recorder). Figures 2A-2D Examples of various types of events are shown. For example, Figure 2A Some examples of triggered alarms are shown. Figure 2A As shown, the triggered alarms may include FD MODE CHG (flight director mode change), AUTOTHROTTLE FAULT (autothrottle fault), and L WSHLDHEAT FAULT (left windshield heating fault). For another example, Figure 2B An example of a history list of alarm handling is shown. Figure 2C shows a specific example of a handling record of an alarm, and Figure 2D Some examples of events manually recorded by the crew are shown.

[0032] In step 110, the system may determine whether each of the multiple events satisfies the recording rule. In one example, the recording rule may include: in response to determining that one of all triggered alarms belongs to an operational alarm, a flight envelope alarm, an operational feedback alarm, or a derivative failure alarm, removing the event corresponding to the alarm. In addition, for the removed alarm, the historical record of the handling method of the corresponding alarm (if any) may also be removed.

[0033] During the flight, when the warning conditions are met, the onboard system (e.g., the flight control system) can trigger an alert to the crew. According to the type of the alert, these alerts can be divided into: operational event alerts, such as ground proximity alerts, weather wind shear alerts, and traffic collision avoidance system (TCAS) traffic collision avoidance alerts; flight envelope alerts, such as overspeed alerts and stall alerts; operational feedback alerts, such as alerts triggered by the crew's operation (e.g., putting a switch in an abnormal position), such as AURAL CANCEL function activation alerts; system failure alerts, such as engine failure alerts; equipment or system status out-of-limit alerts, such as engine overheat alerts and oil overtemperature alerts; smoke and fire alerts, such as engine fire alerts and cabin smoke alerts. Operational alarms, flight envelope alarms, and operational feedback alarms are mainly related to the crew's operations. They do not require maintenance intervention, so there is no need for post-flight records, that is, they do not need to be recorded in the flight segment log. Therefore, after these alarms are triggered, these alarms are removed according to the recording rules and are not stored in the memory. In addition, during the flight, derivative fault alarms may also be triggered. For example, the occurrence of certain root fault alarms may lead to derivative fault alarms, and only the root fault alarms are recorded at this time. For example, when the emergency power supply alarm, which is the root fault alarm, is triggered, related derivative fault alarms, such as the autopilot fault alarm and the co-pilot side IDU fault alarm, are triggered at the same time. However, these derivative fault alarms are caused by the root fault alarms and are not recorded for the time being, because recording all of them in the flight segment log will significantly increase the workload of the crew and maintenance personnel.

[0034] Figure 3 A logic block diagram 300 of a recording rule according to an embodiment of the present disclosure is shown. After the alarm is triggered in box 305, it can be determined in box 310 whether the alarm belongs to an operational event alarm. If so, the alarm is removed in box 315. If not, it can be determined in box 320 whether the alarm belongs to a flight envelope alarm. For example, according to the recording rule, the overspeed alarm shown in FIG. 2 belongs to a flight envelope alarm and can be removed. If so, the alarm is removed in box 315. If not, it can be determined in box 325 whether the alarm belongs to an operation feedback alarm. If so, the alarm is removed in box 315. If not, it can be determined in box 330 whether the alarm belongs to a derivative fault alarm. If so, the alarm is removed in box 315. If not, the alarm can be stored in a memory.

[0035] In step 115, the system may remove the event from the event list in response to determining that there is an event that does not satisfy the recording rule. As an optional example, the plurality of events include three display areas, wherein the first display area displays events that are still activated, the second display area displays events that have been resolved after being processed, and the third display area displays events that have not been processed but have been resolved. Figure 4An example of displaying a flight segment log according to an embodiment of the present disclosure is shown. Figure 4 As shown, the first display area can display the still activated alarms FD MOD CHG (flight director mode change) and AUTOTHROTTLE FAULT (autothrottle fault); the second display area can display the alarm L WSHLD HEAT FAULT (left windshield heating fault) that has been resolved after being handled; and the third display area can display the alarm L ENG OIL TEMP HI (left engine oil temperature is too high) that has not been handled but has been resolved. Figure 4 As shown in history It is a shortcut key used to access the historical disposal records of the corresponding alarm.

[0036] In step 120, the system may generate a final fault record. In some cases, during the ground phase, after reviewing and recording, the crew / maintenance can manually clear the event by operating the ACKNOWLEDGE and RESET buttons. For example, the crew / maintenance can clear the events that have been cleared (e.g., the alarms that have been cleared) and retain the events (e.g., the alarms that are still activated or the front row related messages). In some cases, if the crew / maintenance does not manually clear the events, before the start of the next flight segment, for example, after the crew resets all normal checklists (RESET ALL), the events of the previous flight segment can be automatically cleared.

[0037] In one example, the method 100 for generating a fault record in a flight segment log may optionally include: in step 125, after the flight of the flight segment ends, the system may transmit the final fault record to the ground maintenance equipment and / or the portable electronic flight log. In an optional example, the ground maintenance equipment stores the final generated flight segment log and the route information and crew information corresponding to the flight segment in a database. In subsequent maintenance, the ground maintenance equipment calls the previously stored flight segment log that is the same or similar to the route information and crew information from the database to find repeated events. In some cases, the maintenance personnel may store the flight segment logs of different routes of various models at different times (daytime or nighttime flights) in the database for subsequent maintenance analysis. In an optional example, the crew / maintenance personnel may use a portable electronic flight log (e.g., a tablet computer) to browse the relevant information. The method provided by the present disclosure can accurately record the events required for each process and intuitively display these events. In addition, the method provided by the present disclosure can transmit the fault records in the flight segment log to the ground maintenance equipment and / or the portable electronic flight log, improve the maintenance efficiency, ensure that the crew can accurately perceive the subsequent abnormal situation, and improve the flight safety.

[0038] Figure 5A block diagram of a device 500 including a system for generating a fault record in a flight segment log according to one embodiment of the present disclosure is shown. The device illustrates a general hardware environment in which the present disclosure may be applied according to exemplary embodiments of the present disclosure.

[0039] Now refer to Figure 5 Device 500 is described, which is an exemplary embodiment of a hardware device that can be applied to various aspects of the present disclosure. Device 500 can be any machine configured to perform processing and / or computing, and can be, but is not limited to, a workstation, a server, a desktop computer, a laptop computer, a tablet computer, or any combination thereof. The above system can be implemented in whole or in part by device 500 or similar devices or systems.

[0040] Device 500 may include elements that may be connected to or in communication with bus 502 via one or more interfaces. For example, device 500 may include bus 502, one or more input devices 505, one or more output devices 510, one or more processors 515, and one or more memories 520, among others.

[0041] The processor 515 may be any type of processor and may include, but is not limited to, a general purpose processor and / or a dedicated processor (e.g., a special processing chip), an intelligent hardware device (e.g., a general purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 515 may be configured to operate a memory array using a memory controller. In other cases, a memory controller (not shown) may be integrated into the processor 515. The processor 515 may be configured to execute computer readable instructions stored in the memory to perform the various functions described herein.

[0042] The memory 520 may be any storage device that enables data storage. The memory 520 may include, but is not limited to, a disk drive, an optical storage device, a solid-state memory, a floppy disk, a floppy disk, a hard disk, a magnetic tape or any other magnetic medium, an optical disk or any other optical medium, a ROM (read-only memory), a RAM (random access memory), a cache memory, and / or any other memory chip or cartridge, and / or any other medium from which a computer can read data, instructions, and / or code. The memory 520 may store computer executable software 525 including computer readable instructions that, when executed, cause the processor to perform the various functions described herein. The memory 520 may have various data / instructions / codes for implementing the various functions described herein.

[0043] The software 525 may be stored in the memory 520, including but not limited to an operating system, one or more applications, drivers and / or other data and codes. Instructions for performing the various functions described herein may be included in one or more applications, and the various units of the above-mentioned device 500 may be implemented by the processor 515 reading and executing the instructions of one or more applications. In some cases, the software 525 may not be directly executable by the processor, but may (for example, when compiled and executed) enable the computer to perform the various functions described herein.

[0044] Input device 505 may be any type of device that can input information into a computing device.

[0045] Output device 510 may be any type of output device that can output information. In one embodiment, output device 510 may be any type of image output device that can display information.

[0046] It will be clear to those skilled in the art from the above embodiments that the present disclosure can be implemented by software with necessary hardware or by hardware, firmware, etc. Based on such an understanding, the embodiments of the present disclosure can be implemented in part in the form of software. Computer software can be stored in a readable storage medium, such as a floppy disk, a hard disk, an optical disk, or a flash memory of a computer. Computer software includes a series of instructions to enable a computer (e.g., a personal computer, a service station, or a network terminal) to perform a method or a portion thereof according to various embodiments of the present disclosure.

[0047] The word “exemplary” is used herein to mean “serving as an example, example, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects.

[0048] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the universal principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but should be granted the full scope consistent with the claims in language, wherein the singular reference to the elements is not intended to mean "there is and only one", but "one or more", unless otherwise specifically stated. Unless otherwise specifically stated, the term "some" refers to one or more. The elements of the various aspects described throughout this disclosure are all structurally and functionally equivalent schemes currently or hereafter known to those of ordinary skill in the art and are expressly incorporated herein by reference, and are intended to be covered by the claims.

Claims

1. A method for generating a fault record in a flight segment log, comprising: Acquire multiple events in a flight segment to generate an event list, wherein the multiple events include: all triggered alarms, all alarm handling history records, and events manually recorded by the crew; Determining whether each of the plurality of events satisfies a recording rule; In response to determining that there is an event that does not satisfy a recording rule, removing the event from the event list; and Generate a final fault record.

2. The method according to claim 1, characterized in that The event further includes information indicating: The occurrence time, flight phase and current status of each of the triggered alerts; The handling method and completion time of all handled alarms; or The order, time of recording and phase of flight for each of the events manually recorded by the crew members.

3. The method according to claim 2, characterized in that The current state includes whether the trigger condition is still activated or has been released and the release time.

4. The method according to claim 3, characterized in that The multiple events include three display areas, wherein the first display area displays events that are still activated, the second display area displays events that have been released after being processed, and the third display area displays events that have not been processed but have been released.

5. The method according to claim 1, characterized in that The recording rules include: In response to determining that one of all the triggered alarms is an operational alarm, a flight envelope alarm, an operational feedback alarm, or a derived failure alarm, an event corresponding to the alarm is removed.

6. The method according to claim 1, characterized in that Further including: After the flight of the flight segment is completed, the final fault record is transmitted to ground maintenance equipment and / or a portable electronic flight logbook.

7. The method according to claim 6, characterized in that The ground maintenance equipment stores the finally generated flight segment log and the route information and crew information corresponding to the flight segment in a database.

8. The method according to claim 7, characterized in that The ground maintenance equipment calls up previously stored flight segment logs that are the same as or similar to the route information and crew information from the database to search for recurring events.

9. A system for generating a fault record in a flight segment log, comprising: Memory; and A processor is coupled to the memory and configured to execute the method according to any one of claims 1-8.

10. A non-transitory computer-readable storage medium having stored thereon instructions for generating a fault record in a flight segment log, the instructions being executable by a processor to perform the method of any one of claims 1-8.

Images