Method and device for electronizing flight experience information

Abstract

The embodiment of the invention discloses a flight experience information electronization method and device. The specific embodiment of the method comprises the following steps: acquiring captain experience information and copilot experience information; the front end checks whether seats in the captain experience information and the copilot experience information conform to a preset rule or not; the background checks whether the experience time, the operation type and the flight stage in the captain experience information and the copilot experience information conform to preset rules or not; and submitting the verified data to an airline for auditing. According to the implementation mode, the electronic filling scheme of the pilot experience time is completed according to the operation condition. And the verification efficiency of the limitation constraint is improved, and a better feedback mode is achieved.

Description

Technical Field

[0001] The embodiments of the present disclosure relate to the field of civil aviation technology, and more particularly to a method and apparatus for electronically digitizing flight experience information. Background Art

[0002] According to the "Regulations on the Administration of Electronic Civil Aircraft Pilot Licenses" issued on October 28, 2022, the general filling requirements of Appendix 2, "Electronic Flight Record Book Filling Specifications," allow different pilot experience times to be entered according to operational conditions, such as monitoring captain (SPIC) experience time and captain establishment (U / S) experience time. At the same time, it also meets the requirements of airlines for registering cruise captain CRZ experience time and first officer F0 experience time.

[0003] Currently, most airlines have crew members fill out paper flight experience logs during flight, which are then brought back after the flight. Ground staff in the flight department manually summarize and count the records before filling them into the system. The records are neither classified according to operational conditions nor filled out electronically.

[0004] In addition, different units and upstream and downstream related systems have different requirements for the summary of crew flight experience information. One type is the latest requirement of the Civil Aviation Administration of China: to provide records of pilot experience information of different operating situations (such as SPIC time, U / S time, etc.); one type is the upstream and downstream systems (such as the pilot scheduling and attendance system, etc., which is also the previous requirement of the Civil Aviation Administration of China) for the docking data requirements of pilots' on-the-seat experience time on flights (i.e. the experience time of the left seat in the cockpit and the experience time of the right seat in the cockpit); and another type is the airline's registration of the information of pilots who actually perform the positions of captain and co-pilot when the crew performs flight missions (which can be compared with the captain and co-pilot personnel determined during scheduling for subsequent flight situation analysis). Summary of the Invention

[0005] The embodiments of the present disclosure provide a method and apparatus for electronically digitizing flight experience information.

[0006] In a first aspect, an embodiment of the present disclosure provides a method for electronicizing flight experience information, including: obtaining the captain's experience information and the co-pilot's experience information; verifying at the front end whether the seats in the captain's experience information and the co-pilot's experience information comply with preset rules; verifying at the back end whether the experience time, operation type, and flight phase in the captain's experience information and the co-pilot's experience information comply with preset rules; and submitting the verified data to the airline for review.

[0007] In some embodiments, the method further includes: if the review is passed, summarizing the captain's experience information and the co-pilot's experience information, counting the experience time of the left cockpit seat and the experience time of the right cockpit seat, and submitting them to the crew scheduling system.

[0008] In some embodiments, the method further includes: if the review is passed, summarizing the captain's experience information and the co-pilot's experience information, counting each pilot's electronic license experience time, and submitting it to the Civil Aviation Administration's cloud license system.

[0009] In some embodiments, the front-end verifies whether the seats in the captain's experience information and the co-pilot's experience information comply with preset rules, including: the system front-end program sets the operation types U / S and CRZ as single options, and only one type or neither type can be selected, and both cannot be selected at the same time; if the captain's operation type is selected as U / S or CRZ, the flight seat is automatically set to the left seat by the system front-end program, and the system front-end program sets this field to an unmodifiable state; if the captain does not check the U / S and CRZ operation types, the flight seat is also automatically set to the left seat by the system front-end program, but the system front-end program sets this field to a modifiable state, allowing the pilot to modify the seat.

[0010] In some embodiments, the front-end verifies whether the seats in the captain's experience information and the co-pilot's experience information comply with preset rules, including: the system front-end program sets the operation type SPIC and F0 as single options, and only one type or neither type can be selected, and both cannot be selected at the same time; if the co-pilot's operation type selects SPIC, the flight seat is automatically set to the left seat by the system front-end program, and the front-end program sets this field to an unmodifiable state; if the co-pilot's operation type selects F0, the flight seat is automatically set to the right seat by the system front-end program, but the front-end program sets this field to a modifiable state, allowing the pilot to modify the seat; if the co-pilot does not select SPIC and F0, the flight seat is automatically set to the right seat by the system front-end program, but the front-end program sets this field to a modifiable state, allowing the pilot to modify the seat.

[0011] In some embodiments, the front-end verifies whether the seats in the captain's experience information and the co-pilot's experience information meet preset rules, including: the system front-end program sets the operation identity in the take-off phase to a single option, and only one type can be selected or not, and both cannot be selected at the same time; the system front-end program sets the operation identity in the landing phase to a single option, and only one type can be selected or not, and both cannot be selected at the same time.

[0012] In some embodiments, the background verifies whether the experience time, operation type, and flight phase in the captain's experience information and the co-pilot's experience information comply with preset rules, including: the cloud determines whether all of the following conditions are met. If any one of them is not met, the verification fails, and a correction reminder is displayed on the page: each person's experience time will not exceed the flight time of the flight; if the captain does not perform the U / S operation type, the sum of the captain's experience time and the sum of the co-pilot's experience time are consistent, both equal to the flight time of the flight; if the captain performs the U / S operation type, the sum of the captain's experience time and the sum of the co-pilot's experience time is equal to twice the flight time of the flight.

[0013] In some embodiments, the background verifies whether the experience time, operation type, and flight phase in the captain's experience information and the co-pilot's experience information comply with preset rules, including: the cloud determines whether all of the following conditions are met. If any one of them is not met, the verification fails, and a correction reminder is displayed on the page: when the captain performs the U / S or CRZ operation type, he is in the left seat of the cockpit; the captain cannot serve as both U / S and CRZ at the same time; when the co-pilot performs the SPIC operation type, he is in the right seat of the cockpit; the co-pilot cannot serve as both SPIC and F0 at the same time.

[0014] In some embodiments, the background verification of whether the experience time, operation type, and flight phase in the captain's experience information and the co-pilot's experience information comply with preset rules includes: the cloud determines whether all of the following conditions are met. If any one of them is not met, the verification fails, and a correction reminder is displayed on the page: the takeoff or landing phase can only be one of the PF operator or the PM operator; there can only be one pair of PF operator and PM operator for takeoff, and one pair of PF operator and PM operator for landing.

[0015] In a second aspect, an embodiment of the present disclosure provides an electronic device for flight experience information, including: an acquisition unit, configured to acquire the captain's experience information and the co-pilot's experience information; a front-end verification unit, configured to perform front-end verification of whether the seats in the captain's experience information and the co-pilot's experience information comply with preset rules; a back-end verification unit, configured to perform back-end verification of whether the experience time, operation type, and flight phase in the captain's experience information and the co-pilot's experience information comply with preset rules; and a submission unit, configured to submit the verified data to the airline for review.

[0016] In some embodiments, the device also includes a summarizing unit, which is configured to: if the review is passed, summarize the captain's experience information and the co-pilot's experience information, count the experience time of the left cockpit seat and the experience time of the right cockpit seat, and submit them to the crew scheduling system.

[0017] In some embodiments, the device also includes a summarizing unit, which is configured to: if the review is passed, summarize the captain's experience information and the co-pilot's experience information, count the electronic license experience time of each pilot, and submit it to the Civil Aviation Administration of China's cloud license system.

[0018] In some embodiments, the front-end verification unit is further configured as follows: the system front-end program sets the operation type U / S and CRZ as single options, and only one type or neither type can be selected, and both cannot be selected at the same time; if the captain's operation type is selected as U / S or CRZ, the flight seat is automatically set to the left seat by the system front-end program, and the system front-end program sets this field to an unmodifiable state; if the captain does not check both the U / S and CRZ operation types, the flight seat is also automatically set to the left seat by the system front-end program, but the system front-end program sets this field to a modifiable state, allowing the pilot to modify the seat.

[0019] In some embodiments, the front-end verification unit is further configured as follows: the system front-end program sets the operation type SPIC and F0 as single options, and only one type or neither type can be selected, and both cannot be selected at the same time; if the co-pilot's operation type is SPIC, the flight seat is automatically set to the left seat by the system front-end program, and the front-end program sets this field to an unmodifiable state; if the co-pilot's operation type is F0, the flight seat is automatically set to the right seat by the system front-end program, but the front-end program sets this field to a modifiable state, allowing the pilot to modify the seat; if the co-pilot does not select either SPIC or F0, the flight seat is automatically set to the right seat by the system front-end program, but the front-end program sets this field to a modifiable state, allowing the pilot to modify the seat.

[0020] In some embodiments, the front-end verification unit is further configured as follows: the system front-end program sets the operation identity of the take-off phase as a single option, and only one type can be selected or not selected, and both cannot be selected at the same time; the system front-end program sets the operation identity of the landing phase as a single option, and only one type can be selected or not selected, and both cannot be selected at the same time.

[0021] In some embodiments, the background verification unit is further configured to: determine by the cloud whether all of the following conditions are met; if any one of them is not met, the verification fails, and a correction reminder is displayed on the page: each person's experience time will not exceed the flight time of the flight; if the captain does not perform the U / S operation type, the sum of the captain's experience time and the sum of the co-pilot's experience time are the same, both equal to the flight time of the flight; if the captain performs the U / S operation type, the sum of the captain's experience time and the sum of the co-pilot's experience time is equal to twice the flight time of the flight.

[0022] In some embodiments, the background verification unit is further configured to: determine by the cloud whether all of the following conditions are met; if any one of them is not met, the verification fails, and a correction reminder is displayed on the page: when the captain performs the U / S or CRZ operation type, he is in the left seat of the cockpit; the captain cannot serve as both the U / S and CRZ at the same time; when the co-pilot performs the SPIC operation type, he is in the right seat of the cockpit; the co-pilot cannot serve as both the SPIC and F0 at the same time.

[0023] In some embodiments, the background verification unit is further configured to: determine by the cloud whether all of the following conditions are met; if any one of them is not met, the verification fails, and a correction reminder is displayed on the page: during the takeoff or landing phase, there can only be one of the PF operator or the PM operator; there can only be one pair of PF operator and PM operator for takeoff, and one pair of PF operator and PM operator for landing.

[0024] In a third aspect, an embodiment of the present disclosure provides an electronic device for electronicizing flight experience information, comprising: one or more processors; a storage device on which one or more computer programs are stored, and when the one or more computer programs are executed by the one or more processors, the one or more processors implement the method as described in any one of the first aspects.

[0025] In a fourth aspect, an embodiment of the present disclosure provides a computer-readable medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the method as described in any one of the first aspects is implemented.

[0026] The disclosed embodiments provide a method and apparatus for electronically recording flight experience information, based on the "Regulations on the Administration of Electronic Civil Aircraft Pilot Licenses." This method and apparatus implements a method for electronically recording pilot experience time based on operational conditions. Each crew's flight experience has different constraints for different operational types, making it complex to determine. This technical solution optimizes the design, improves the efficiency of constraint verification, and provides a more efficient feedback mechanism. This design allows processing of flight experience data from different units through a single entry.

[0027] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present disclosure, nor are they intended to limit the scope of the present disclosure. Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Other features, objects and advantages of the present disclosure will become more apparent from a reading of the detailed description of non-limiting embodiments made with reference to the following drawings:

[0029] Figure 1is an exemplary system architecture diagram in which an embodiment of the present disclosure may be applied;

[0030] Figure 2 is a flow chart of an embodiment of a method for electronically digitizing flight experience information according to the present disclosure;

[0031] Figure 3 is a schematic diagram of an application scenario of the method for electronically digitizing flight experience information according to the present disclosure;

[0032] Figures 4a-4f Instructions for filling out the captain's experience information and the co-pilot's experience information according to the electronic flight experience information method disclosed herein;

[0033] Figure 5 is a schematic structural diagram of an embodiment of a device for electronically storing flight experience information according to the present disclosure;

[0034] Figure 6 It is a schematic diagram of the structure of a computer system of an electronic device suitable for implementing the embodiments of the present disclosure. DETAILED DESCRIPTION

[0035] The present disclosure will be further described in detail below with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are intended only to illustrate the relevant invention and are not intended to limit the invention. It should also be noted that, for ease of description, only portions relevant to the relevant invention are shown in the accompanying drawings.

[0036] It should be noted that, in the absence of conflict, the embodiments and features of the embodiments in the present disclosure may be combined with each other. The present disclosure will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0037] Figure 1 An exemplary system architecture 100 is shown to which an embodiment of the method or device for electronically digitizing flight experience information disclosed herein may be applied.

[0038] like Figure 1 As shown, system architecture 100 may include terminal devices 101, 102, 103, a network 104, and a server 105. Network 104 is a medium for providing communication links between terminal devices 101, 102, 103 and server 105. Network 104 may include various connection types, such as wired or wireless communication links or fiber optic cables.

[0039] Users can use terminal devices 101, 102, and 103 to interact with server 105 via network 104 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 101, 102, and 103, such as flight program applications, web browser applications, shopping applications, search applications, instant messaging tools, email clients, social platform software, etc.

[0040] Terminal devices 101, 102, and 103 can be hardware or software. When terminal devices 101, 102, and 103 are hardware, they can be various electronic devices with display screens and support web browsing, including but not limited to smart phones, tablet computers, e-book readers, MP3 players (Moving Picture Experts Group Audio Layer III, Moving Picture Experts Group Audio Layer 3), MP4 (Moving Picture Experts Group Audio Layer IV, Moving Picture Experts Group Audio Layer 4) players, laptop computers, and desktop computers, etc. When terminal devices 101, 102, and 103 are software, they can be installed in the electronic devices listed above. It can be implemented as multiple software or software modules (for example, to provide distributed services), or it can be implemented as a single software or software module. No specific limitation is made here.

[0041] Server 105 may be a server that provides various services, such as a background verification and statistics server that supports the flight experience information filling page displayed on terminal devices 101, 102, and 103. The background verification and statistics server may verify and compile data such as the captain's experience information and the co-pilot's experience information, and then provide the data to relevant departments.

[0042] It should be noted that a server can be either hardware or software. When a server is hardware, it can be implemented as a distributed server cluster consisting of multiple servers, or as a single server. When a server is software, it can be implemented as multiple software programs or software modules (for example, multiple software programs or software modules used to provide distributed services), or as a single software program or software module. This is not specifically limited here. The server can also be a server in a distributed system, or a server integrated with blockchain. The server can also be a cloud server, or an intelligent cloud computing server or intelligent cloud host with artificial intelligence technology.

[0043] It should be noted that in the method for electronically digitizing flight experience information provided in the embodiments of the present disclosure, front-end processing is performed by terminal devices 101, 102, and 103, while back-end processing is performed by server 105. Accordingly, the electronic flight experience information device can be provided in terminal devices 101, 102, and 103, or in server 105. This is not specifically limited herein.

[0044] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is merely illustrative. Any number of terminal devices, networks and servers may be provided as required.

[0045] The following are the definitions of the terms used in this article:

[0046] Flight Log: Broadly speaking, this refers to the "China Civil Aviation Flight Log: CCAR-121 Transport Airlines Version," which consists of four sections: Daily Flight Missions, Simulation Training, Flight Training, and Flight Check Logs. This article will only cover Daily Flight Missions and Flight Training.

[0047] Crew members: Aviation personnel performing tasks on board an aircraft during flight, including flight crew members and cabin crew.

[0048] Pilot-in-Chief: A pilot who has obtained an Airline Transport Pilot License in accordance with China's Civil Aviation Regulations and is employed as a pilot-in-chief by an air transport company, as defined in my country's "Duties and Responsibilities of a Civil Aviation Transport Pilot-in-Chief." This term refers to a pilot who has been employed as a captain by the company and assigned to the position of pilot-in-chief on flights operated by the company.

[0049] First Officer: A pilot who assists the captain in flying the aircraft, conducting air-to-ground and air-to-air communications, and reading landing checklists. In this context, this refers to the pilot assigned to the first officer position on a flight.

[0050] Captain established experience U / S: Holding an airline transport pilot license, operating experience established in the left seat under the supervision of an instructor or inspector.

[0051] Cruise Captain Experience (CRZ): Operational experience gained while performing captain responsibilities during the cruise phase.

[0052] Surveillance Pilot in Command (SPIC): Operational experience gained while holding a commercial pilot license and operating in the left seat under the supervision of an instructor or inspector.

[0053] Co-pilot F0: A stage of co-pilot, in which one can only fly in a team with an instructor and perform flight missions as an F0 co-pilot.

[0054] Continue to refer Figure 2, shows a process 200 of an embodiment of a method for electronically digitizing flight experience information according to the present disclosure. The method for electronically digitizing flight experience information includes the following steps:

[0055] Step 201: Obtain captain's experience information and co-pilot's experience information.

[0056] In this embodiment, the user uses the execution subject (eg Figure 1 Launch the app on a terminal device (as shown), enter the flight number, and enter the experience information page, where the user can fill in the captain's and co-pilot's experience information. This information can be completed by the captain and co-pilot separately, or by one person and confirmed by the others. Each pilot's experience information includes name, flight time, night flight time, seat flown, flight phase, and operation type.

[0057] Step 202: The front end verifies whether the seats in the captain's experience information and the co-pilot's experience information meet the preset rules.

[0058] In this embodiment, the terminal device can directly verify whether the seat selection is correct. There are strict regulations on the seats that pilots sit in when performing different operations. If it does not meet the preset regulations, the verification will fail and a correction reminder will be displayed on the page. For example, if the user selects U / S or CRZ as the captain's operation type, and fills in the right seat as the flying seat, it does not meet the preset rules. If the user selects SPIC as the co-pilot's operation type, and fills in the right seat as the flying seat, it does not meet the preset rules. If the user selects F0 as the co-pilot's operation type, and fills in the left seat as the flying seat, it does not meet the preset rules.

[0059] In some optional implementations of this embodiment, the front-end verifies whether the seats in the captain's experience information and the co-pilot's experience information comply with preset rules, including: the system front-end program sets the operation types U / S and CRZ as single options, and only one type or neither type can be selected, and both cannot be selected at the same time; if the captain's operation type is selected as U / S or CRZ, the flight seat is automatically set to the left seat by the system front-end program, and the system front-end program sets this field to an unmodifiable state; if the captain does not check both the U / S and CRZ operation types, the flight seat is also automatically set to the left seat by the system front-end program, but the system front-end program sets this field to a modifiable state, allowing the pilot to modify the seat.

[0060] In some optional implementations of this embodiment, the front-end verifies whether the seats in the captain's experience information and the co-pilot's experience information comply with preset rules, including: the system front-end program sets the operation type SPIC and F0 as single options, and only one type or neither type can be selected, and both cannot be selected at the same time; if the co-pilot's operation type is SPIC, the flight seat is automatically set to the left seat by the system front-end program, and the front-end program sets this field to an unmodifiable state; if the co-pilot's operation type is F0, the flight seat is automatically set to the right seat by the system front-end program, but the front-end program sets this field to a modifiable state, allowing the pilot to modify the seat; if the co-pilot does not select either SPIC or F0, the flight seat is automatically set to the right seat by the system front-end program, but the front-end program sets this field to a modifiable state, allowing the pilot to modify the seat.

[0061] In some optional implementations of this embodiment, the front-end verifies whether the seats in the captain's experience information and the co-pilot's experience information comply with preset rules, including: the system front-end program sets the operation identity in the take-off phase as a single option, and only one type can be selected or not, and both cannot be selected at the same time; the system front-end program sets the operation identity in the landing phase as a single option, and only one type can be selected or not, and both cannot be selected at the same time.

[0062] Step 203: The background checks whether the experience time, operation type, and flight phase in the captain's experience information and the co-pilot's experience information comply with preset rules.

[0063] In this embodiment, the captain's experience information and the co-pilot's experience information may be sent to a server, and the server backend may perform information verification.

[0064] First, we will introduce the verification and processing logic of the flight experience time record, and then explain how the system is designed for classification verification and judgment.

[0065] The calculation and verification requirements for pilot experience time include the following three aspects:

[0066] 1) Elapsed time calculation and verification logic:

[0067] On the same flight, the flight crew members, whether serving as captain or co-pilot, will not have a total experience exceeding the flight time of the flight.

[0068] Generally speaking, the sum of the experience time of pilots serving as captains on the same flight is the same as the sum of the experience time of pilots serving as co-pilots, and both are equal to the flight time of the flight.

[0069] Unless a captain on the aircraft performs U / S operations, the sum of the pilot's experience may differ from the sum of the first officer's experience, but the sum of these two categories equals twice the flight time for the flight. This is related to the Civil Aviation Administration's definition of captain and first officer experience. For a detailed explanation, please refer to the general requirements for filling out the "Electronic Flight Experience Logbook."

[0070] 2) Operation type verification logic:

[0071] If you are a captain, you must perform U / S or CRZ maneuvers from the left seat of the cockpit. Other captain roles are not differentiated on the electronic license and have no seat restrictions. Furthermore, U / S and CRZ are mutually exclusive; a pilot cannot perform both simultaneously.

[0072] If you're a co-pilot, you must perform SPIC operations from the right seat in the cockpit. F0 operations are not differentiated from other co-pilot licenses, and there are no seat restrictions. Furthermore, SPIC and F0 are mutually exclusive; a pilot cannot hold both positions simultaneously.

[0073] For the entire flight, the combination of pilot and the type of operation performed can only appear once and cannot appear multiple times.

[0074] 3) Identity verification logic during takeoff and landing:

[0075] During takeoff and landing, the pilot is required to operate the joystick. The pilot performing the operation is recorded as the PF operating pilot (Pilot FLY), and the pilot monitoring the operation of the joystick on the other side of the cockpit is recorded as the PM monitoring pilot (Pilot Monitor).

[0076] Therefore, a pilot can only be either a PF operator or a PM operator during takeoff or landing, but not both.

[0077] In addition, there is only one takeoff and one landing during a flight mission, that is, there will be a pair of takeoff PF and PM, and a pair of landing PF and PM. (The takeoff and landing situation of this training is not subject to this restriction, and multiple takeoffs and landings are possible)

[0078] After passing multiple levels of approval within the airline, different statistical data will be required for the summary of flight experience based on different needs. For example, the civil aviation electronic license requires the captain's experience time, while the crew scheduling system requires the left and right cockpit seat experience time. The requirements for pilot experience time summary statistics are as follows:

[0079] 4) Electronic license experience time summary logic

[0080] a) Pilot-in-command experience: The sum of the pilot's experience as a pilot-in-command who performed operations other than U / S or CRZ.

[0081] b) First Officer Experience Time: As a pilot who actually performed the first officer position, all types of operations when flying, and as a captain, the type of operation when flying was U / S

[0082] Or CRZ, the sum of the experienced times.

[0083] 5) Cockpit left and right seat experience time summary logic

[0084] The sum of the time a pilot spent in the left seat of the cockpit is the pilot's time in the left seat of the cockpit; similarly, the sum of the time a pilot spent in the right seat of the cockpit is the pilot's time in the right seat of the cockpit.

[0085] Based on the aforementioned calculation and verification logic requirements for pilot experience time, the requirements can be divided into those that can be directly verified for individual pilot operations, such as the relationship between operation type and seat, and the PF and PM identities of takeoff and landing, which constitute the majority of the verification logic in 2) and 3). Calculation and verification must be performed based on the overall flight situation, such as the calculation of experience time and the calculation of takeoff and landing phases, which constitute the entire calculation and verification of 1), as well as verification of some situations in 2) and 3) (constrained by the conditions of the entire flight).

[0086] Therefore, if the operation status of a single pilot can be directly verified, it can be directly verified through the front-end program when filling in the page; if the situation of the entire flight needs to be calculated and verified, it can be calculated and judged through the background program when the page is completed and submitted.

[0087] Step 204: Submit the verified data to the airline for review.

[0088] In this embodiment, after the pilot completes and successfully submits the form, it will be submitted to the airline for multi-level review. If the review fails, it will be sent back for modification.

[0089] In some optional implementations of this embodiment, the method further includes: if the review is passed, the captain's experience information and the co-pilot's experience information are summarized, the experience time of the left cockpit seat and the experience time of the right cockpit seat are counted, and submitted to the crew scheduling system.

[0090] In some optional implementations of this embodiment, the method further includes: if the review is passed, summarizing the captain's experience information and the co-pilot's experience information, counting the electronic license experience time of each pilot, and submitting it to the Civil Aviation Administration of China's cloud license system.

[0091] As analyzed above, after the pilot completes and successfully submits the form, and after it passes multiple levels of internal review by the airline, the system's backend program will summarize the experience time of each pilot on this flight mission. The system program design for the summary calculation is as follows:

[0092] (i.e., 4) electronic license experience time summary logic in step 203, and 5) cockpit left and right seat experience time summary logic)

[0093] (1) Calculation and design of the summary of each pilot's electronic license experience time, i.e., step 4 in step 203)

[0094] When the final approval process is passed, the system's background program calculates the following elapsed time information for each pilot on the entire flight:

[0095] Pilot's captain's U / S experience time = the experience time filled in when selecting captain and checking U / S;

[0096] The pilot's cruise captain's CRZ time = the time filled in when selecting captain and checking CRZ;

[0097] The pilot's monitoring captain's SPIC experience time = the experience time filled in when selecting the first officer and checking SPIC;

[0098] Pilot's responsible captain experience time = the experience time filled in when selecting captain and unchecking U / S and CRZ;

[0099] A pilot's co-pilot experience time = SUM (Captain's U / S experience time + Cruise Captain's CRZ experience time + Surveillance Captain's SPIC experience time) + (Experience time filled in when co-pilot is selected and F0 is checked) + (Experience time filled in when co-pilot is selected and SPIC and F0 are not checked)

[0100] (2) Calculate and design the sum of the time each pilot has spent in the left and right cockpit seats, i.e., step 5 in step 203)

[0101] When the final approval process is passed, the system's background program calculates the following elapsed time information for each pilot on the entire flight:

[0102] Pilot's left cockpit seat experience time = (the sum of all experience time entered when captain was selected and the flight seat was "left seat") + (the sum of all experience time entered when co-pilot was selected and the flight seat was "left seat");

[0103] The pilot's cockpit right seat experience time = (the sum of all experience time filled in when the captain is selected and the flight seat is "right seat") + (the sum of all experience time filled in when the co-pilot is selected and the flight seat is "right seat")

[0104] Continue to see Figure 3 , Figure 3 This is a schematic diagram of an application scenario of the method for electronically digitizing flight experience information according to this embodiment. Figure 3 In the application scenario, steps 3, 4, 5, and 6 in the figure are judged, calculated, and verified by the system, while steps 1, 2, and 7 require manual triggering. Step 3 is verified and judged by the system's front-end program; steps 4 and 6 are calculated, verified, and processed by the system's back-end program. These three steps are the key technical designs of this article and will be explained in detail below. Step 5 is based on the approval process set by the system. After the airline has reviewed and approved the completed flight experience record information, the system can compile and output the flight experience record information. The approval process is not explained in this article.

[0105] The following will explain in detail the calculation and processing logic of the system in the front-end program and the back-end program, as well as the design logic of the back-end program for summarizing the elapsed time statistics after approval.

[0106] 1. Instructions for filling in the system's main page

[0107] After analyzing the calculation and verification logic requirements of the pilot's experience time in step 203, the filling page is designed as follows (see Figure 4a ): It is divided into the captain's experience information filling area and the co-pilot's experience information filling area. Both areas have 6 filling contents including name, experience time, night flight time, operation type, flight seat, and flight stage.

[0108] You can add captain and co-pilot filling pages by clicking the "+" on the right side of the two areas, see Figure 4b You can click to enter the personnel who are scheduled for the flight. Non-scheduled personnel cannot add experience time.

[0109] 2. System front-end program verification design description

[0110] As analyzed above, when the pilot fills in the form, the system's front-end program designs the following verification logic for the individual pilot's operation type and take-off and landing phases:

[0111] (i.e., the verification logic for a single pilot in the operation type in step 203, and the verification logic for a single pilot's stick operation identity in the takeoff and landing phase in step 203)

[0112] (1) Verification design of operation type and flight seat in the captain experience information filling area

[0113] like Figure 4cAs shown, the system front-end program sets the operation type U / S and CRZ as single options. You can only select one type or neither type, and you cannot select both at the same time.

[0114] If the captain selects U / S or CRZ as the operation type, the flight seat is automatically set to the left seat by the system front-end program, and the system front-end program sets this field to an unmodifiable state;

[0115] If the captain does not check the U / S and CRZ operation types, the flight seat will be automatically set to the left seat by the system front-end program, but the system front-end program sets this field to a modifiable state, allowing the pilot to modify the seat.

[0116] (2) Verification design of operation type and flight seat in the co-pilot experience information filling area

[0117] like Figure 4d As shown, the system front-end program sets the operation type SPIC and F0 as single options. You can only select one type or neither type, and you cannot select both at the same time.

[0118] If the co-pilot's operation type is SPIC, the flight seat is automatically set to the left seat by the system front-end program, and the front-end program sets this field to an unmodifiable state;

[0119] If the co-pilot's operation type is F0, the flight seat is automatically set to the right seat by the system front-end program, but the front-end program sets this field to be editable, allowing the pilot to change the seat;

[0120] If the co-pilot does not select either SPIC or F0, the flight seat is automatically set to the right seat by the system front-end program, but the front-end program sets this field to a modifiable state, allowing the pilot to change the seat.

[0121] (3) Verification design of the take-off and landing phase operation identity in the captain and co-pilot experience information filling area

[0122] like Figure 4e As shown, the system front-end program sets the takeoff phase operation identity: Takeoff PF, Takeoff PM as a single option. Only one type can be selected or not, and both cannot be selected at the same time.

[0123] The system front-end program sets the landing phase operation identity: Landing PF, Landing PM as a single option. You can only select one type or neither, and you cannot select both at the same time.

[0124] 3. System background program calculation and verification design description

[0125] As analyzed above, when the pilot fills in the form, if verification statistics are required based on the entire flight, the system's background program will perform calculations and verification logic. The system design is as follows:

[0126] (i.e., all calculations and verifications of step 1) in step 203 and verifications of parts 2) and 3) based on the entire flight situation)

[0127] (1) The restriction constraint judgment of the operation type of the entire flight, that is, the situation where the part 2) in step 203 is constrained by the entire flight, see Figure 4c and 4d Fill in the area

[0128] At the time of submission, the system's background program calculates the flight experience record for the entire flight:

[0129] i. Each pilot can only appear once in any of the following situations: "Captain" + "U / S, CRZ, or neither";

[0130] ii. Each pilot can only be selected once for any of the following scenarios: "Co-pilot" + "SPIC, F0, or neither";

[0131] If any of the above conditions are not met, the application will be prompted with the content of the unsatisfactory information and the submission will be failed.

[0132] (2) The constraint judgment of the take-off and landing phase operation of the entire flight, i.e., the logical verification of the take-off and landing phase operation in step 203, see Figure 4e Fill in the area

[0133] At the time of submission, the system's background program calculates the flight experience record for the entire flight:

[0134] i. Determine that the sum of the number of check marks for all pilots' takeoff PFs is 1, and takeoff

[0135] The sum of PM's checkboxes = 1

[0136] ii. Determine that the sum of the number of ticks for Landing PF for all pilots = 1, and the sum of the number of ticks for Landing PM = 1

[0137] If any of the above conditions are not met, the application will be prompted with the content of the unsatisfactory information and the submission will be failed.

[0138] (3) Calculation of the pilot's experience time during the entire flight and determination of the constraints, i.e., step 1) in step 203, see Figure 4f Fill in the area.

[0139] At the time of submission, the system's background program calculates the flight experience record for the entire flight:

[0140] i. Check whether the captain has checked U / S in the operation type. If neither is checked,

[0141] a) SUM (the total time filled in the captain area of ​​the entire flight) = the flight time of the flight,

[0142] b) SUM (time spent in all co-pilot areas of the entire flight) =

[0143] The flight time of the flight

[0144] If any of the above conditions are not met, the system will display the information that the condition is not met and indicate that the submission failed.

[0145] ii. If the operator selects the U / S operation type,

[0146] a) SUM (the total time filled in by all captains in the entire flight) +

[0147] SUM (the experience time filled in by all co-pilot areas of the entire flight) = 2 * the flight time of the flight,

[0148] If not, the system will prompt the content of the unsatisfied information and indicate that the submission failed.

[0149] 4. System background program statistics

[0150] As analyzed above, after the pilot completes and successfully submits the form, and after it passes multiple levels of internal review by the airline, the system's backend program will summarize the experience time of each pilot on this flight mission. The system program design for the summary calculation is as follows:

[0151] (i.e., step 4) electronic license experience time summary logic, and step 5) cockpit left and right seat experience time summary logic in step 203)

[0152] (1) The calculation and design of each pilot's electronic license experience time summary, i.e., step 4 in step 203)

[0153] When the final approval process is passed, the system's background program calculates the following elapsed time information for each pilot on the entire flight:

[0154] i. Pilot's captain's U / S experience time = the experience time entered when selecting captain and checking U / S;

[0155] ii. Pilot's Cruise Captain Experience CRZ Time = Select Captain and check

[0156] The experience time filled in during CRZ;

[0157] iii. Pilot's monitoring captain's SPIC time = Select first officer and check

[0158] The experience time filled in during SPIC;

[0159] iv. Pilot's experience as pilot-in-command = the experience entered when selecting pilot-in-command and unchecking U / S and CRZ;

[0160] v. Pilot's co-pilot experience time = SUM (Captain's U / S experience time + Cruise Captain's CRZ experience time + Surveillance Captain's SPIC experience time) + (Experience time filled in when co-pilot is selected and F0 is checked) + (Experience time filled in when co-pilot is selected and SPIC and F0 are not checked)

[0161] (2) The calculation and design of the total time spent in the left and right seats of each pilot in the cockpit, i.e., step 5 in step 203)

[0162] When the final approval process is passed, the system's background program calculates the following elapsed time information for each pilot on the entire flight:

[0163] i. Pilot's left cockpit seat experience time = (the sum of all experience time entered when the captain is selected and the flight seat is "left seat") + (the sum of all experience time entered when the co-pilot is selected and the flight seat is "left seat");

[0164] The pilot's cockpit right seat experience time = (the sum of all experience time filled in when the captain is selected and the flight seat is "right seat") + (the sum of all experience time filled in when the co-pilot is selected and the flight seat is "right seat")

[0165] Further references Figure 5 As an implementation of the methods shown in the above figures, the present disclosure provides an embodiment of a device for electronically storing flight experience information. Figure 2 Corresponding to the method embodiment shown, the device can be specifically applied to various electronic devices.

[0166] like Figure 5 As shown, the electronic flight experience information device 500 of this embodiment includes: an acquisition unit 501, a front-end verification unit 502, a back-end verification unit 503, and a submission unit 504. The acquisition unit 501 is configured to acquire the captain's experience information and the co-pilot's experience information; the front-end verification unit 502 is configured to front-end verify whether the seats in the captain's experience information and the co-pilot's experience information meet preset rules; the back-end verification unit 503 is configured to back-end verify whether the experience time, operation type, and flight phase in the captain's experience information and the co-pilot's experience information meet preset rules; and the submission unit 504 is configured to submit the verified data to the airline for review.

[0167] In this embodiment, the specific processing of the acquisition unit 501, the front-end verification unit 502, the back-end verification unit 503 and the submission unit 504 of the flight experience information electronic device 500 can be referred to. Figure 2 These correspond to steps 201, 202, 203, and 204 in the embodiment.

[0168] In some optional implementations of this embodiment, the device also includes a summarizing unit (not shown in the accompanying drawings), which is configured to: if the review is passed, summarize the captain's experience information and the co-pilot's experience information, count the experience time of the left cockpit seat and the experience time of the right cockpit seat, and submit them to the crew scheduling system.

[0169] In some optional implementations of this embodiment, the device also includes a summarizing unit, which is configured to: if the review is passed, summarize the captain's experience information and the co-pilot's experience information, count the electronic license experience time of each pilot, and submit it to the Civil Aviation Administration of China's cloud license system.

[0170] In some optional implementations of this embodiment, the front-end verification unit 202 is further configured as follows: the system front-end program sets the operation types U / S and CRZ as single options, and only one type or neither type can be selected, and both cannot be selected at the same time; if the captain's operation type is selected as U / S or CRZ, the flight seat is automatically set to the left seat by the system front-end program, and the system front-end program sets this field to an unmodifiable state; if the captain does not check both the U / S and CRZ operation types, the flight seat is also automatically set to the left seat by the system front-end program, but the system front-end program sets this field to a modifiable state, allowing the pilot to modify the seat.

[0171] In some optional implementations of this embodiment, the front-end verification unit 202 is further configured as follows: the system front-end program sets the operation type SPIC and F0 as single options, and only one type or neither type can be selected, and both types cannot be selected at the same time; if the co-pilot selects SPIC as the operation type, the flight seat is automatically set to the left seat by the system front-end program, and the front-end program sets this field to an unmodifiable state; if the co-pilot selects F0 as the operation type, the flight seat is automatically set to the right seat by the system front-end program, but the front-end program sets this field to a modifiable state, allowing the pilot to modify the seat; if the co-pilot does not select either SPIC or F0, the flight seat is automatically set to the right seat by the system front-end program, but the front-end program sets this field to a modifiable state, allowing the pilot to modify the seat.

[0172] In some optional implementations of this embodiment, the front-end verification unit 202 is further configured as follows: the system front-end program sets the operation identity of the take-off phase as a single option, and only one type can be selected or not selected, and both cannot be selected at the same time; the system front-end program sets the operation identity of the landing phase as a single option, and only one type can be selected or not selected, and both cannot be selected at the same time.

[0173] In some optional implementations of this embodiment, the background verification unit 203 is further configured to: determine by the cloud whether all of the following conditions are met; if any one of them is not met, the verification fails, and a correction reminder is displayed on the page: the experience time of each person will not exceed the flight time of the flight; if the captain does not perform the U / S operation type, the sum of the captain's experience time and the sum of the co-pilot's experience time are consistent, both equal to the flight time of the flight; if the captain performs the U / S operation type, the sum of the captain's experience time and the sum of the co-pilot's experience time is equal to twice the flight time of the flight.

[0174] In some optional implementations of this embodiment, the background verification unit 203 is further configured to: determine by the cloud whether all the following conditions are met; if any one of them is not met, the verification fails, and a correction reminder is displayed on the page: when the captain performs the U / S or CRZ operation type, he is in the left seat of the cockpit; the captain cannot serve as both the U / S and CRZ at the same time; when the co-pilot performs the SPIC operation type, he is in the right seat of the cockpit; the co-pilot cannot serve as both the SPIC and F0 at the same time.

[0175] In some optional implementations of this embodiment, the background verification unit 203 is further configured to: determine by the cloud whether all the following conditions are met; if any one of them is not met, the verification fails, and a correction reminder is displayed on the page: only one of the PF operator or the PM operator can be in the takeoff or landing phase; there can be only one pair of PF operator and PM operator for takeoff, and one pair of PF operator and PM operator for landing.

[0176] It should be noted that the collection, collection, updating, analysis, processing, use, transmission, and storage of user personal information involved in the technical solutions disclosed herein all comply with relevant laws and regulations, are used for legitimate purposes, and do not violate public order and good morals. Necessary measures are taken with respect to user personal information to prevent unauthorized access to user personal information data and to safeguard the security of user personal information, network security, and national security.

[0177] According to an embodiment of the present disclosure, the present disclosure further provides an electronic device and a readable storage medium.

[0178] An electronic device comprises: one or more processors; a storage device on which one or more computer programs are stored, and when the one or more computer programs are executed by the one or more processors, the one or more processors implement the method described in process 200 or 400.

[0179] A computer-readable medium stores a computer program thereon, wherein the computer program implements the method described in process 200 or 400 when executed by a processor.

[0180] Figure 6 A schematic block diagram of an example electronic device 600 that can be used to implement embodiments of the present disclosure is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are provided as examples only and are not intended to limit the implementation of the present disclosure described and / or claimed herein.

[0181] like Figure 6 As shown, the device 600 includes a computing unit 601, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 602 or a computer program loaded from a storage unit 608 into a random access memory (RAM) 603. Various programs and data required for the operation of the device 600 can also be stored in the RAM 603. The computing unit 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0182] Various components in device 600 are connected to I / O interface 605, including an input unit 606, such as a keyboard, mouse, etc.; an output unit 607, such as various types of displays, speakers, etc.; a storage unit 608, such as a magnetic disk, optical disk, etc.; and a communication unit 609, such as a network card, modem, wireless communication transceiver, etc. The communication unit 609 allows device 600 to exchange information / data with other devices via a computer network such as the Internet and / or various telecommunication networks.

[0183] Computing unit 601 can be any general-purpose and / or specialized processing component with processing and computing capabilities. Some examples of computing unit 601 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various specialized artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Computing unit 601 performs the various methods and processes described above, such as the method for electronically digitizing flight experience information. For example, in some embodiments, the method for electronically digitizing flight experience information can be implemented as a computer software program tangibly embodied in a machine-readable medium, such as storage unit 608. In some embodiments, part or all of the computer program can be loaded and / or installed onto device 600 via ROM 602 and / or communication unit 609. When the computer program is loaded into RAM 603 and executed by computing unit 601, one or more steps of the method for electronically digitizing flight experience information described above can be performed. Alternatively, in other embodiments, computing unit 601 can be configured to perform the method for electronically digitizing flight experience information by any other suitable means (e.g., via firmware).

[0184] Various embodiments of the systems and techniques described herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), system-on-chip systems (SOCs), programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments can include being implemented in one or more computer programs that are executable and / or interpreted on a programmable system that includes at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0185] The program code for implementing the method of the present disclosure can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device so that when the program code is executed by the processor or controller, the functions / operations specified in the flow chart and / or block diagram are implemented. The program code can be executed entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0186] In the context of the present disclosure, a machine-readable medium can be a tangible medium that can contain or store a program for use by or in conjunction with an instruction execution system, device or equipment. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium can include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0187] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0188] The systems and techniques described herein can be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network (LAN), a wide area network (WAN), and the Internet.

[0189] A computer system may include a client and a server. The client and server are generally remote from each other and typically interact via a communication network. The client-server relationship arises through computer programs running on the respective computers and having a client-server relationship with each other. The server may be a server in a distributed system or a server integrated with blockchain. The server may also be a cloud server, or an intelligent cloud computing server or intelligent cloud host with artificial intelligence technology. The server may be a server in a distributed system or a server integrated with blockchain. The server may also be a cloud server, or an intelligent cloud computing server or intelligent cloud host with artificial intelligence technology.

[0190] It should be understood that the various forms of the processes shown above can be used to reorder, add, or delete steps. For example, the steps described in this disclosure can be performed in parallel, sequentially, or in a different order, as long as the desired results of the technical solutions disclosed in this disclosure can be achieved. This is not a limitation herein.

[0191] The above specific embodiments do not constitute a limitation on the scope of protection of this disclosure. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions may be made based on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this disclosure shall be included within the scope of protection of this disclosure.

Claims

1. A method for electronically digitizing flight experience information, comprising: Obtain captain's experience information and co-pilot's experience information; The front end verifies whether the seats in the captain's experience information and the co-pilot's experience information meet the preset rules; The background checks whether the experience time, operation type, and flight phase in the captain's experience information and the co-pilot's experience information conform to the preset rules; The verified data will be submitted to the airline for review.

2. The method according to claim 1, further comprising: If the review is passed, the captain's experience information and the co-pilot's experience information will be summarized, and the experience time of the left cockpit seat and the experience time of the right cockpit seat will be counted and submitted to the crew scheduling system.

3. The method according to claim 1, further comprising: If the review is passed, the captain's experience information and the co-pilot's experience information will be summarized, and the electronic license experience time of each pilot will be counted and submitted to the Civil Aviation Administration's cloud license system.

4. The method according to claim 1, wherein the front-end verifies whether the seats in the captain's experience information and the co-pilot's experience information meet preset rules, comprising: The system front-end program sets the operation type U / S and CRZ as single options. You can only select one type or neither type, and you cannot select both at the same time. If the captain selects U / S or CRZ as the operation type, the flight seat is automatically set to the left seat by the system front-end program, and the system front-end program sets this field to an unmodifiable state; If the captain does not check the U / S and CRZ operation types, the flight seat is automatically set to the left seat by the system front-end program, but the system front-end program sets this field to a modifiable state, allowing the pilot to modify the seat.

5. The method according to claim 1, wherein the front-end verifies whether the seats in the captain's experience information and the co-pilot's experience information meet preset rules, comprising: The system front-end program sets the operation types SPIC and F0 as single options. You can only select one type or neither type, and you cannot select both at the same time. If the co-pilot's operation type is SPIC, the flight seat is automatically set to the left seat by the system front-end program, and the front-end program sets this field to an unmodifiable state; If the co-pilot's operation type is F0, the flight seat is automatically set to the right seat by the system front-end program, but the front-end program sets this field to be editable, allowing the pilot to change the seat; If the co-pilot does not select either SPIC or F0, the flight seat is automatically set to the right seat by the system front-end program, but the front-end program sets this field to a modifiable state, allowing the pilot to change the seat.

6. The method according to claim 1, wherein the front-end verifies whether the seats in the captain's experience information and the co-pilot's experience information meet preset rules, comprising: The system front-end program sets the takeoff phase operation identity as a single option. You can only select one type or neither type, and you cannot select both at the same time. The system front-end program sets the landing phase operation identity as a single option. You can only select one type or neither, and you cannot select both at the same time.

7. The method according to claim 1, wherein the background verification of whether the experience time, operation type, and flight phase in the captain's experience information and the co-pilot's experience information conform to preset rules comprises: The cloud checks whether all of the following conditions are met. If any one of them is not met, the verification fails and a correction prompt is displayed on the page: Each person's experience will not exceed the flight time; If the captain did not perform a U / S maneuver, the captain's total experience time is the same as the first officer's total experience time, and both are equal to the flight time. If the captain performs a U / S type of operation, the sum of the captain's experience time and the first officer's experience time is equal to twice the flight time of the flight.

8. The method according to claim 1, wherein the background verification of whether the experience time, operation type, and flight phase in the captain's experience information and the co-pilot's experience information conform to preset rules comprises: The cloud checks whether all of the following conditions are met. If any one of them is not met, the verification fails and a correction prompt is displayed on the page: The captain is in the left seat of the cockpit when performing U / S or CRZ type operations; The captain cannot be both U / S and CRZ at the same time; The first officer is in the right seat of the cockpit when performing SPIC type of operations; The co-pilot cannot serve as both SPIC and F0 at the same time.

9. The method according to claim 1, wherein the background verification of whether the experience time, operation type, and flight phase in the captain's experience information and the co-pilot's experience information conform to preset rules comprises: The cloud checks whether all of the following conditions are met. If any one of them is not met, the verification fails and a correction prompt is displayed on the page: During takeoff or landing, only one operator can be a PF operator or a PM operator; There is only one pair of PF operators and PM operators for takeoff, and one pair of PF operators and PM operators for landing.

10. A device for electronically recording flight experience information, comprising: an acquiring unit configured to acquire captain experience information and co-pilot experience information; A front-end verification unit is configured to verify whether the seats in the captain's experience information and the co-pilot's experience information comply with preset rules; A background verification unit is configured to verify whether the experience time, operation type, and flight phase in the captain's experience information and the co-pilot's experience information comply with preset rules; The submission unit is configured to submit the verified data to the airline for review.

11. An electronic device for electronically recording flight experience information, comprising: one or more processors; a storage device having one or more computer programs stored thereon, When the one or more computer programs are executed by the one or more processors, the one or more processors are caused to implement the method according to any one of claims 1 to 9.

12. A computer-readable medium having a computer program stored thereon, wherein: When the computer program is executed by a processor, the method according to any one of claims 1 to 9 is implemented.

Images